[go: up one dir, main page]

WO2025153666A1 - Procédé pour faciliter l'interopérabilité/l'interchangeabilité de modèle - Google Patents

Procédé pour faciliter l'interopérabilité/l'interchangeabilité de modèle

Info

Publication number
WO2025153666A1
WO2025153666A1 PCT/EP2025/051124 EP2025051124W WO2025153666A1 WO 2025153666 A1 WO2025153666 A1 WO 2025153666A1 EP 2025051124 W EP2025051124 W EP 2025051124W WO 2025153666 A1 WO2025153666 A1 WO 2025153666A1
Authority
WO
WIPO (PCT)
Prior art keywords
model
information
interoperability
nwdaf
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2025/051124
Other languages
English (en)
Inventor
Ulf Mattsson
Jing Yue
Maria Belen PANCORBO MARCOS
Magnus HALLENSTÅL
Wenliang Xu
Igor PASTUSHOK
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025153666A1 publication Critical patent/WO2025153666A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14Network analysis or design
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/16Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition

Definitions

  • a method performed by a Network Repository Function (NRF) to facilitate model interoperability includes receiving first model interoperability information from one or more AFs, and second model interoperability information from one or more NWDAFs, and then based on the first model interoperability information and the second model interoperability information, identifying an NWDAF of the one or more NWDAFs that can handle an AF.
  • the method can also include providing an NWDAF identifier of the NWDAF to the AF.
  • the first model interoperability information is received via an NEF.
  • the first model interoperability information and the second model interoperability information comprise one or more of a requested model file format; a model execution environment; label information; feature information; interlayer information; transfer learning information; and split learning information.
  • the first model interoperability information and the second model interoperability information comprise interoperability identifiers or interoperability parameters.
  • an NRF can be provided with processing circuitry configured to perform any of the methods of the embodiments described above.
  • a method can be performed by an NRF for facilitating model interoperability with the method comprising receiving a subscription to information from a Network Exposure Function (NEF) and receiving a registration from an NWDAF, the registration comprising model information, and providing the model information to the NEF.
  • NEF Network Exposure Function
  • an NRF can be provided with processing circuitry configured to perform this method.
  • a method is provided that is performed by an NEF for facilitating model interoperability, the method comprising subscribing to information from an NRF, receiving model information from the NRF associated with one or more NWDAFs, receiving model interoperability information from an AF, determining, based on the model interoperability information from the AF, and the model information associated with the one or more NWDAFs, which interoperability information to use for the AF, and providing the interoperability information to the AF.
  • the model information from the one or more NWDAFs further comprises model interoperability information.
  • the method in response to the model information not comprising model interoperability information, further comprises subscribing to information from the one or more NWDAFs.
  • an NEF is provided with processing circuitry configured to perform the method of the above embodiments.
  • a method performed by an NWDAF for facilitating model interoperability.
  • the method includes providing registration information to an NRF wherein the registration information comprises model information.
  • the method also includes receiving model interoperability information from an AF, determining, based on the model information and the model interoperability information from the AF, which interoperability information to use for the AF, and providing the interoperability information to the AF.
  • the NWDAF comprises an MTLF.
  • the registration information comprises model interoperability information associated with the NWDAF.
  • the model interoperability information from the AF is received via an NEF.
  • a method performed by an NWDAF is provided for facilitating storing or training a model. The method includes receiving a model request from an AF, registering a model associated with the model request into an NRF, performing training using the model associated with the model request according to one or more parameters from the model request, and providing the AF with at least one of a model identifier associated with the model, or the model, or a reference to the model.
  • the one or more parameters comprise a type of model, a request to store the model for future use, a request to train a model using an attachment in the model request.
  • the NWDAF is operating an MTLF. In other embodiment, the NWDAF is operating an Analytics Logical Function (AnLF).
  • AnLF Analytics Logical Function
  • Figure 2 shows another message sequence chart for another method for facilitating model interoperability according to one or more embodiments of the present disclosure
  • Figure 4 shows a message sequence chart for a method for facilitating performing model training and storing according to one or more embodiments of the present disclosure
  • Figure 5 shows another message sequence chart for another method for facilitating model combining and analytics according to one or more embodiments of the present disclosure
  • Figure 6 shows another message sequence chart for another method for facilitating model training according to one or more embodiments of the present disclosure
  • FIG. 7 illustrates a wireless communication system represented as a Fifth Generation (5G) network architecture composed of core Network Functions (NFs);
  • 5G Fifth Generation
  • NFs core Network Functions
  • Core Network Node is any type of node in a core network or any node that implements a core network function.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber Server
  • Various embodiments disclosed herein provide for a method to facilitate model interoperability between different network functions, such as an Application Function (AF) and a Network Data Analytics Function (NWDAF) or other functions in a Fifth Generation (5G) core network (5GC).
  • the handshake process disclosed herein can enabled the network functions to determine if there is model interoperability and can facilitate the sharing of models, weights, and other elements from the AF into the 5GC or vice versa.
  • the model data can be provided to a Model Training Logical Function (MTLF) or Analytics Logical Function (AnLF) being operated by an NWDAF for Federated Learning (FL) or transfer learning.
  • MTLF Model Training Logical Function
  • AnLF Analytics Logical Function
  • FL Federated Learning
  • the principles below can be applied even inside the core domain, then the AF may be replaced with another NWDAF, and the functionality of NEF is part of this NWDAF. In this case the NWDAF may be an ordinary NF with learning capabilities.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • Some of the advantages provided by the embodiment disclosed herein include: the possibility to do handshakes, the possibility for an AF to send models to 5GC, the possibility to train such model in NWDAF(MTLF), the possibility to merge two models in NWDAF, the possibility to store models from AF in ADRF for later use, sending the model instead of data from an AF, and also the possibility for an AF to send models to 5GC to an NWDAF(AnLF).
  • Figure 1 illustrates a message sequence chart for a method for facilitating model interoperability according to one or more embodiments of the present disclosure
  • a handshake can occur before the model is sent, where it is determined that the model from the AF is interoperable with the NWDAF and the model in the NWDAF before sharing models or perform FL, transfer learning, split learning or similar.
  • a message can be sent between an AF 102, an NRF 104, and an NWDAF 106, and in some embodiments, there may be an NEF between the AF 102 and the NRF 104.
  • the NWDAF 106 can include an MTLF and may be a special NWDAF(MTLF) that registers into NRF 104 the capability ToActOnModel.
  • ML Model Interoperability Information is specified in TS 23.288 as vendor-specific information that conveys, e.g., requested model file format, model execution environment, etc.
  • vendor-specific information that conveys, e.g., requested model file format, model execution environment, etc.
  • model details such as labels, features, inter-layer information can be included.
  • the registered information into NRF may be Interoperability ID or other new parameter (instead of Interoperability Information). In this case the Interoperability Information is changed to either Interoperability ID or the new parameter in the embodiments.
  • the registered information into NRF may be ML Model Interoperability Information, ML Model Interoperability identifier or other new parameter carrying the interoperability information [0040]
  • Interoperability ID the definition of Interoperability ID can be broadened to not only include list of vendors. But also include info that matches the external "vendor” that is supported! Either Interoperability ID or new parameter is used, it shall be used in a way that indicates that the MTLF can handle models from this "vendor”.
  • Example of "vendor” are developing models, phone maker, modem maker, User Equipment Operating System (UE OS) maker, or application maker.
  • Today Interoperability ID is used in the opposite direction, namely it is used for a consumer to know if it is allowed to download and can execute a model from the MTLF.
  • the method can include receiving model interoperability information from an NWDAF 106 of a group of NWDAFs (second model interoperability).
  • the method can include receiving first model interoperability information from one or more AFs 102.
  • the method can include the NRF 104 identifying an NWDAF 106 of the one or more NWDAFs that can handle an AF 102 of the AFs based on the first model interoperability information and the second model interoperability information.
  • the NRF 104 can send the identifier of the NWDAF 106 that is interoperable with the AF 102 to the AF 102.
  • the first model interoperability information and/or the second model interoperability information may comprise one or more of: a) a requested model file format; b) a model execution environment; c) label information; d) feature information; e) interlayer information; f) transfer learning information; g) split learning information; and h) other related information.
  • the first model interoperability information and/or the second model interoperability information may comprise any combination of the features a-h above, e.g. one (1), two (2), three (3), four (4), five (5), six (6), seven (7), and/or eight (8) of the features a-h above.
  • the first model interoperability information and/or the second model interoperability information comprises any one of feature a-h, or features a and b or features a, c, and g etc.
  • Figure 2 illustrates another message sequence chart for another method for facilitating model interoperability according to one or more embodiments of the present disclosure.
  • the NWDAF may include an MTLF that may be a special MTLF that registers into NRF the capability ToActOn Model.
  • the registered information into NRF may be Interoperability ID or a new parameter (instead of Interoperability Information).
  • Interoperability ID it is possible to broaden the definition in stage 3 to not only include a list of vendors but also include info that reveals what Hyperscale Cloud Providers (HCPs) that are supported, etc.
  • HCPs Hyperscale Cloud Providers
  • the NEF 202 may subscribe to information from the NRF 104.
  • NEF 202 performs a subscription to each of these NWDAFs 106 to receive model interoperability information.
  • the AF 102 can provide model interoperability information to the NEF 202.
  • the consumer starts Handshakes on Interoperability, e.g. on what format to send the model with NEF 202 including what type of Interoperability Information the AF 102 may support
  • NEF 202 decides which Interoperability Information to use.
  • the NEF 202 determines, based on the model interoperability information from the AF 102, and the model information associated with the one or more NWDAFs 106, which interoperability information to use for the AF 102.
  • Figure 3 illustrates another message sequence chart for another method for facilitating model interoperability according to one or more embodiments of the present disclosure.
  • the steps 204-208 are as described in Figure 2, but in step 302, in a Handshake request message, the AF 102 can provide top the NWDAF 106 directly the model interoperability information, and the NWDAF 106 at step 3045 can determine, based on the model information and the model interoperability information from the AF 102, which interoperability information to use for the AF 102. At step 306, the NWDAF 106 responds to the AF 102 with the selected model interoperability information.
  • Figure 4 depicts the MTLF 402 as operated by NWDAF 106, and MTLF 402 may be a special MTLF that registers into NRF the capability ToActOnModel.
  • the ToActOnModel service can be a request to StoreModel (for future use, similar to provisioning of info to 5GS) or to request to train a model and may be re-using existing Nnwdaf_MLModelTraining Service.
  • the model can directly be stored from the AF 102 into the ADRF 516.
  • AF 102 or NEF 202 (if between AF 102 and ADRF 516) makes use of same services as MTLF 402 when storing into ADRF 516.
  • the AF 102 can attach a model identifier or application identifier.
  • the AF 102 could also add which Analytics ID it would like to receive as output. This output could be, e.g., Observed Service Experience. Or the output could just be the Analytics being derived by using the referred model.
  • the AnLF 502 discovers an MTLF 402 that can handle the model the AnLF 402 needs. It could add either model ID in the request or add App ID. Today model ID is not registered into NRF 104.
  • the 5G network architecture shown in Figure 7 comprises a plurality of UEs 718 connected to either a RAN 716 or an Access Network (AN) as well as an AMF 700.
  • the R(AN) 716 comprises base stations, e.g. such as eNBs or gNBs or similar.
  • the 5GC NFs shown in Figure 7 include a NSSF 702, an AUSF 704, a UDM 706, the AMF 700, a SMF 708, a PCF 710, and an Application Function (AF) 712.
  • the N1 reference point is defined to carry signaling between the UE 718 and AMF 700.
  • the reference points for connecting between the AN 716 and AMF 700 and between the AN 716 and UPF 714 are defined as N2 and N3, respectively.
  • N4 is used by the SMF 708 and UPF 714 so that the UPF 714 can be set using the control signal generated by the SMF 708, and the UPF 714 can report its state to the SMF 708.
  • N9 is the reference point for the connection between different UPFs 714, and N14 is the reference point connecting between different AMFs 700, respectively.
  • N15 and N7 are defined since the PCF 710 applies policy to the AMF 700 and SMF 708, respectively.
  • N12 is required for the AMF 700 to perform authentication of the UE 718.
  • N8 and N10 are defined because the subscription data of the UE 718 is required for the AMF 700 and SMF 708.
  • the 5GC network aims at separating UP and CP.
  • the UP carries user traffic while the CP carries signaling in the network.
  • the UPF 714 is in the UP and all other NFs, i.e., the AMF 700, SMF 708, PCF 710, AF 712, NSSF 702, AUSF 704, and UDM 706, are in the CP.
  • Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.
  • RTT Round Trip Time
  • Modularized function design enables the 5GC network to support various services flexibly.
  • Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF.
  • a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity.
  • the UP supports interactions such as forwarding operations between different UPFs.
  • a method performed by a Network Repository Function, NRF, (104) for facilitating model interoperability comprising: receiving (204) a subscription to information from a Network Exposure Function, NEF, (202); receiving (206) a registration from a Network Data and Analytics Functions, NWDAF, (106) the registration comprising model information; and providing (208) the model information to the NEF (202).
  • NRF Network Repository Function
  • model interoperability information comprises one or more of: a requested model file format; a model execution environment; label information; feature information; interlayer information; transfer learning information; and split learning information.
  • NRF Network Repository Function
  • the NRF comprising processing circuitry configured to perform any of the methods of embodiments 6 to 8.
  • a method performed by a Network Exposure Function, NEF, (202) for facilitating model interoperability comprising: subscribing (204) to information from a Network Repository Function, NRF, (104); receiving (208) model information from the NRF (104) associated with one or more Network Data and Analytics Functions, NWDAFs, (106); receiving (210) model interoperability information from an Application Function, AF, (102); determining (212), based on the model interoperability information from the AF, and the model information associated with the one or more NWDAFs (106), which model interoperability information to use for the AF (102); and providing (214) the model interoperability information to the AF (102).
  • NEF Network Exposure Function
  • model information from the one or more NWDAFs (106) further comprises model interoperability information.
  • (106) comprising processing circuitry configured to perform any of the methods of embodiments 19 to 23.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Artificial Intelligence (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Databases & Information Systems (AREA)
  • Evolutionary Computation (AREA)
  • Medical Informatics (AREA)
  • Software Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Divers modes de réalisation de la présente invention divulguent un procédé pour faciliter l'interopérabilité de modèle entre différentes fonctions de réseau, telles qu'une fonction d'application (AF) et une fonction d'analyse de données de réseau (NWDAF) ou d'autres fonctions dans un réseau central de cinquième génération (5G) (5GC). Le processus d'établissement de liaison divulgué ici peut activer les fonctions de réseau pour déterminer s'il existe une interopérabilité de modèle et peut faciliter le partage de modèles, de poids et d'autres éléments de l'AF dans le 5GC ou inversement. Les données de modèle peuvent être fournies à une fonction logique d'entraînement de modèle (MTLF) ou à une fonction logique analytique (AnLF) qui est actionnée par une NWDAF pour un apprentissage fédéré (FL) ou un apprentissage par transfert.
PCT/EP2025/051124 2024-01-18 2025-01-17 Procédé pour faciliter l'interopérabilité/l'interchangeabilité de modèle Pending WO2025153666A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463622185P 2024-01-18 2024-01-18
US63/622,185 2024-01-18

Publications (1)

Publication Number Publication Date
WO2025153666A1 true WO2025153666A1 (fr) 2025-07-24

Family

ID=94384152

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2025/051124 Pending WO2025153666A1 (fr) 2024-01-18 2025-01-17 Procédé pour faciliter l'interopérabilité/l'interchangeabilité de modèle

Country Status (1)

Country Link
WO (1) WO2025153666A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141985A1 (fr) * 2022-01-28 2023-08-03 华为技术有限公司 Procédé et appareil de communication
EP4254895A1 (fr) * 2022-03-28 2023-10-04 Ntt Docomo, Inc. Agencement de réseau de communication et procédé pour la fourniture d'un modèle d'apprentissage par machine permettant d'effectuer une analyse de réseau de communication
WO2023215720A1 (fr) * 2022-05-02 2023-11-09 Intel Corporation Autorisation et authentification de transfert de modèle d'apprentissage automatique

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141985A1 (fr) * 2022-01-28 2023-08-03 华为技术有限公司 Procédé et appareil de communication
EP4254895A1 (fr) * 2022-03-28 2023-10-04 Ntt Docomo, Inc. Agencement de réseau de communication et procédé pour la fourniture d'un modèle d'apprentissage par machine permettant d'effectuer une analyse de réseau de communication
WO2023215720A1 (fr) * 2022-05-02 2023-11-09 Intel Corporation Autorisation et authentification de transfert de modèle d'apprentissage automatique

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHANG LIU ET AL: "draft TR 33.738 1.1.0", vol. SA WG3, no. Online; 20230417 - 20230421, 26 April 2023 (2023-04-26), XP052297115, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_SA/WG3_Security/TSGS3_110_AdHoc-e/Docs/S3-232230.zip S3-232230 TR33.738 1.1.0-cl.docx> [retrieved on 20230426] *
MEGHASHREE D KEDALAGUDDE ET AL: "Correction for alignment with TS 23.288 regarding ML Model interoperability per Analytics ID", vol. SA WG2, no. Chicago, US; 20231113 - 20231117, 20 November 2023 (2023-11-20), XP052549383, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160_Chicago_2023-11/Docs/S2-2313407.zip S2-2313407wasS2-2312501.docx> [retrieved on 20231120] *

Similar Documents

Publication Publication Date Title
EP4101188A1 (fr) Extension de npcf_eventexposure avec événement de surveillance d&#39;utilisation
US11265808B2 (en) Adaptive network slice selection
CN111615844B (zh) 用于选择服务无线通信设备的会话管理实体的方法和装置
US11797359B2 (en) Report application programming interface (API) capability change based on API filter
CN112789842A (zh) 用于在电信网络中支持事件监测的订阅和报告的服务的方法以及相关网络功能
CN115735369A (zh) 确定默认网络切片
CN114745709A (zh) 执行针对服务消费方的服务的方法以及对应的网络节点和计算机程序产品
US20250203680A1 (en) Using dnai to identify a smf supporting connection to a local dn
EP4223014A1 (fr) Garantie de commande de réseau d&#39;accès simultané à des tranches de réseau avec une sensibilité à l&#39;application
WO2022123526A1 (fr) Collecte de données sécurisée dans un système de cinquième génération (5gs)
WO2021028435A1 (fr) Mécanisme de découverte de nef par rapport à une gestion de pfd
CN112752352A (zh) 一种中间会话管理功能i-smf确定方法和设备
WO2021028193A1 (fr) Amélioration de données d&#39;abonnement de sélection de tranche
WO2023135572A1 (fr) Extraction dynamique d&#39;informations nsac
WO2023021464A1 (fr) Exigence oauth2 par plmn à la définition du type nfservice
WO2025153666A1 (fr) Procédé pour faciliter l&#39;interopérabilité/l&#39;interchangeabilité de modèle
US20250150519A1 (en) Service Request Processing
US20220330140A1 (en) Edge computing
EP4566364A1 (fr) Suppression du re-provisionnement de toutes les politiques d&#39;ue pendant une relocalisation d&#39;amf
WO2023084444A1 (fr) Gestion de trafic de tranches
US20240292317A1 (en) Location service entity selection method and apparatus, and electronic device and readable storage medium
WO2025037264A1 (fr) Exposition d&#39;api de service nord basée sur les tranches de réseau
WO2025210596A1 (fr) Politique de transfert de données d&#39;arrière-plan pour la resélection de client d&#39;activation d&#39;ia/ml
WO2022214395A1 (fr) Amélioration de la sélection d&#39;upf par nrf
WO2025158377A1 (fr) Procédé de transport de capacités d&#39;événement de fonction de réseau à des référentiels de fonction de réseau/référentiels d&#39;abonnés

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25701403

Country of ref document: EP

Kind code of ref document: A1