Communication method, first function, second function and storage medium
By sending the authorized access list of ADRF to MTLF in 5G communication technology, the logical contradiction between the SA2 and SA3 standard solutions is solved, and the consistency of permission judgment obtained by the ML model and the security of ADRF are realized.
Patent Information
- Application Number
- CN202310975341.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-03
- Publication Date
- 2025-02-14
- Estimated Expiration
- 2043-08-03
AI Technical Summary
In 5G communication technology, there is a logical contradiction between the SA2 and SA3 standard solutions of the Third Generation Partnership Program (3GPP), which leads to inconsistent access permission processing methods obtained by ML models, affecting the permission judgment of network function consumers and the acquisition of ML models. Way.
By sending the authorized access to NF or supplier list of ADRF to MTLF, MTLF understands the permissions of ADRF, and when receiving the ML model acquisition request of NFc, it determines whether NFc has permission to access ADRF based on the authorization list, thereby determining the acquisition of NFc The way of ML model.
It resolves the logical contradiction between the SA2 and SA3 standard solutions, ensures the consistency of permission judgment obtained by the ML model, ensures the security of ADRF, and avoids information leakage.
Smart Images

Figure CN119449632A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to but is not limited to the field of communications, and in particular to a communication method, a first function, a second function, and a computer-readable storage medium. Background Art
[0002] In the field of communications, machine learning (ML) models combined with network data analytics functions (NWDAF) can provide predictive services in different scenarios.
[0003] Under the existing technical solution of the 5th generation mobile communication technology (5G), the ML model acquisition method based on NWDAF is defined in the 3rd Generation Partnership Project (3GPP) Standalone (SA) 2 standard solution, that is, the consumer (Consumer) sends an ML model acquisition request to the NWDAF including the Model Training Logic Function (MTLF); then, MTLF determines whether the Consumer directly obtains the ML model from the Analytic Data Repository Function (ADRF) or indirectly obtains the ML model based on MTLF. Here, indirect acquisition means that ADRF first transmits the ML model to MTLF, and then MTLF transmits it to Consumer. Finally, after MTLF makes a judgment, ADRF returns the ML model directly or indirectly to Consumer. It should be noted that since some consumers do not have direct access to certain ADRFs, SA2 hopes that MTLF will determine which consumers can access ADRF.
[0004] However, currently, 3GPP SA3 has proposed an access rights processing method for ML model acquisition based on NWDAF. In this method, ADRF will update the ADRF local access list based on the received MTLF local list. As a result, the ADRF list will not work, and all network function consumers (NFc) that are determined by MTLF to have access to the ML model can directly obtain the ML model from ADRF. Obviously, the method currently described in SA3 is logically inconsistent with the method defined in the SA2 standard solution. Therefore, there is an urgent need to provide a new solution to resolve the contradiction between the SA2 and SA3 solutions. Summary of the invention
[0005] The embodiments of the present application provide a communication method, a first function, a second function, and a computer-readable storage medium, and provide a new method for obtaining and judging an ML model based on NWDAF.
[0006] In a first aspect, an embodiment of the present application provides a communication method, which is applied to a first function, including:
[0007] Receiving first information sent by a second function; wherein the first information includes relevant information of at least one network function service consumer or provider authorized to access the second function;
[0008] According to the first information, a method for the first network function service consumer to obtain the target model is determined.
[0009] In a second aspect, an embodiment of the present application provides a communication method, which is applied to a second function, including:
[0010] Sending first information to the first function; wherein the first information includes relevant information of at least one network function service consumer or provider who is authorized to access the second function.
[0011] In a third aspect, a first function is provided, wherein the first function includes:
[0012] A first receiving module, configured to receive first information sent by a second function; wherein the first information includes relevant information of at least one network function service consumer or provider authorized to access the second function;
[0013] The first processing module is used to determine a method for the first network function service consumer to obtain a target model according to the first information.
[0014] In a fourth aspect, a second function is provided, wherein the second function includes:
[0015] The second sending module is used to send first information to the first function; wherein the first information includes relevant information of at least one network function service consumer or provider authorized to access the second function.
[0016] A fifth aspect, a first function, wherein the first function includes:
[0017] A first memory, used to store executable instructions;
[0018] The first processor is used to implement the above communication method when executing the executable instructions stored in the first memory.
[0019] A sixth aspect, a second function, wherein the second function includes:
[0020] A second memory, used for storing executable instructions;
[0021] The second processor is used to implement the above communication method when executing the executable instructions stored in the second memory.
[0022] In the seventh aspect, an embodiment of the present application provides a chip for implementing the above-mentioned communication method; the chip includes: a processor, for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned communication method.
[0023] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute the above-mentioned communication method.
[0024] In a ninth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the above-mentioned communication method.
[0025] In a tenth aspect, an embodiment of the present application provides a computer program which, when executed on a computer, enables the computer to execute the above-mentioned communication method.
[0026] This application enables MTLF to understand the authority of ADRF by sending the first information of the second function, i.e., the authorized access to NF or supplier list, to the first function, i.e., MTLF, so that after MTLF determines that the first NFc has the authority to access the ML model, for the subsequent ML model acquisition request sent by the first NFc received by MTLF, MTLF can compare the information corresponding to the first NFc with the NF or supplier list to confirm whether the first NFc has the authority to access ADRF, and then determine whether the first NFc directly obtains the ML model or indirectly obtains the ML model. In this way, the problem of logical contradiction between the method proposed by SA3 and the method defined in the SA2 standard scheme mentioned in the related art is solved. At the same time, in this application, the solution in which MTLF determines whether the first NFc directly obtains the ML model or indirectly obtains the ML model based on the authorized access to NF or supplier list is compared with the solution proposed by SA3 in which MTLF determines that NFcs that can access the ML model can directly obtain the ML model from ADRF. This can ensure the security of some ADRFs that need to hide their own addresses and avoid the problem of information leakage caused by the mutual access of functions corresponding to different manufacturers. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] Figure 1 is a schematic diagram of a network architecture applicable to embodiments of the present application;
[0028] Figure 2 This is a schematic diagram of the process of obtaining the ML model method provided by the relevant technology Figure 1 ;
[0029] Figure 3 This is a schematic diagram of the process of obtaining the ML model method provided by the relevant technology Figure 2 ;
[0030] Figure 4 Schematic diagram of the communication method provided in the embodiment of the present application Figure 1 ;
[0031] Figure 5 Schematic diagram of the communication method provided in the embodiment of the present application Figure 2 ;
[0032] Figure 6 A schematic block diagram of a first function provided in an embodiment of the present application;
[0033] Figure 7 A schematic block diagram of a second function provided in an embodiment of the present application;
[0034] Figure 8 A schematic structural diagram of a communication device provided in an embodiment of the present application;
[0035] Fig. 9 A schematic structural diagram of a chip provided in an embodiment of the present application;
[0036] Fig.10 A schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0037] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0038] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: 5G system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions of the embodiments of the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication system or other communication systems.
[0039] For the convenience of description, the 5G network will be used as an example in the embodiments of the present application.
[0040] Figure 1 Schematic diagram of a network architecture 100 applicable to an embodiment of the present application. Figure 1 As shown, the network architecture may specifically include three parts, namely, the terminal equipment part, the data network (DN) and the operator network public land mobile network (PLMN) part. The functions of the network elements of each part are briefly described below.
[0041] The terminal equipment part may include a terminal device 110, which may also be referred to as a user equipment (UE). The terminal device 110 in the present application is a device with wireless transceiver functions, which may communicate with one or more core network (CN) devices via an access network device (or may also be referred to as an access device) in a radio access network (RAN). The terminal device 110 may also be referred to as an access terminal, a terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a user agent or a user device, etc. The terminal device 110 may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it may also be deployed on the water (e.g., a ship, etc.); it may also be deployed in the air (e.g., on an airplane, a balloon, and a satellite, etc.). The terminal device 110 may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), etc. Alternatively, the terminal device 110 may also be a handheld device with wireless communication function, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device or a terminal in the Internet of Things or the Internet of Vehicles, a terminal in any form in a 5G network and future networks, a relay user device or a terminal in a future evolved 6G network, etc. Among them, the relay user device may be, for example, a 5G residential gateway (RG). For example, the terminal device 110 can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The terminal device here refers to a 3GPP terminal. The embodiments of the present application do not limit the type or category of the terminal device. For ease of explanation, the present application will be described later using UE as an example to refer to the terminal device.
[0042] The operator network PLMN part may include but is not limited to the (radio) access network ((R)AN) 120 and the core network (CN) part.
[0043] (R)AN 120 can be regarded as a sub-network of the operator network, and is an implementation system between the service nodes in the operator network and the terminal device 110. To access the operator network, the terminal device 110 first passes through (R)AN 120, and then can connect to the service nodes of the operator network through (R)AN 120. The access network device (RAN device) in the embodiment of the present application is a device that provides wireless communication functions for the terminal device 110, and can also be called a network device. The RAN device includes but is not limited to: the next generation node base station (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (for example, home evolved node B, or home node B, HNB), the base band unit (BBU), the transmission point (TRP), the transmitting point (TP), the small base station device, the mobile switching center, or the network device in the future network. In systems using different wireless access technologies, the names of the devices with access network device functions may be different. For the convenience of description, in all embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 110 are collectively referred to as access network devices or RAN or AN for short. It should be understood that this document does not limit the specific type of access network equipment.
[0044] The CN part may include but is not limited to the following network functions (NF): user plane function (UPF), access and mobility management function (AMF), session management function (SMF), NWDAF, unified data management function (UDM), and network function repository function (NRF).
[0045] Data Network (DN) 130, also known as packet data network (PDN), is usually a network outside the operator network, such as a third-party network. Of course, in some implementations, DN can also be deployed by the operator, that is, DN is part of the PLMN. This application does not limit whether DN belongs to the PLMN. The operator network PLMN can access multiple DNs 130, and multiple services can be deployed on DN 130, which can provide data and / or voice services for the terminal device 110. For example, DN 130 can be a private network of a smart factory, and the sensors installed in the workshop of the smart factory can be terminal devices 110. The control server of the sensor is deployed in DN 130, and the control server can provide services for the sensor. The sensor can communicate with the control server, obtain the instructions of the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, DN 130 can be the internal office network of a company, and the mobile phone or computer of the company's employees can be the terminal device 110, and the employee's mobile phone or computer can access the information, data resources, etc. on the company's internal office network. The terminal device 110 can establish a connection with the operator network through an interface (such as N1, etc.) provided by the operator network, and use data and / or voice services provided by the operator network. The terminal device 110 can also access the DN 130 through the operator network, and use the operator services deployed on the DN 130, and / or services provided by a third party.
[0046] The following is a brief description of the NF functions included in CN.
[0047] UPF is a gateway provided by the operator and is the gateway for the operator network to communicate with DN 130. UPF includes user plane related functions such as packet routing and transmission, packet detection, service usage reporting, quality of service (QoS) processing, legal monitoring, uplink packet detection, and downlink packet storage.
[0048] AMF is a control plane network function provided by the operator network, responsible for access control and mobility management of the terminal device 110 accessing the operator network, including, for example, mobility status management, allocation of user temporary identity, authentication and authorization of users, and other functions.
[0049] SMF is a control plane network function provided by the operator network, responsible for managing the protocol data unit (PDU) session of the terminal device 110. A PDU session is a channel for transmitting PDUs, and the terminal device needs to transmit PDUs to and from the DN 130 through the PDU session. The SMF is responsible for establishing, maintaining, and deleting PDU sessions. SMF includes session management (such as session establishment, modification, and release, including tunnel maintenance between the user plane function (UPF) and the (R)AN 120), UPF selection and control, service and session continuity (SSC) mode selection, roaming, and other session-related functions.
[0050] NRF is a control plane function provided by the operator, which can be used to maintain real-time information of network functions and services in the network. For example, it supports network service discovery, maintains the services supported by the NF profile of the NF instance, supports service discovery of the service communication proxy (SCP), maintains the SCP profile of the SCP instance, sends notifications about newly registered, unregistered, and updated NFs and SCPs, and maintains the health status of NF and SCP operations.
[0051] UDM is a control plane function provided by the operator, which is responsible for storing the subscriber permanent identifier (SUPI) of the subscriber in the operator network, the generic public subscription identifier (GPSI) of the subscriber, the credential and other information. Among them, SUPI will be encrypted first during the transmission process, and the encrypted SUPI is called the hidden user subscription identifier (SUCI). The information stored in UDM can be used for the authentication and authorization of the terminal device 110 to access the operator network. Among them, the subscribers of the above-mentioned operator network can specifically be users who use the services provided by the operator network, such as users who use China Telecom's mobile phone core card (subscriber identity module, SIM) card, or users who use China Mobile's mobile phone core card. The credential of the above-mentioned subscriber can be a small file storing long-term keys stored in the mobile phone core card or information related to the encryption of the mobile phone core card, which is used for authentication and / or authorization. It should be noted that the permanent identifier, credential, security context, authentication data (cookie), and token are equivalent to verification / authentication and authorization related information. In the embodiment of the present application, no distinction or restriction is made for the convenience of description.
[0052] NWDAF is a control plane function provided by operators. Its main function is to collect data from NF, external application function (AF) and operation, administration and maintenance (OAM) system, and provide NWDAF service registration, data opening and data analysis for NF and AF.
[0053] Specifically, NWDAF can include the following logical functions:
[0054] Analytical Logical Function (AnLF): A logical function in NWDAF that is used to perform inference, derive analytical information (i.e., derive statistics and / or predictions based on analytical consumer requests), and expose analytical services.
[0055] Model Training Logical Function (MTLF): A logical function in NWDAF that trains a machine learning (ML) model and exposes new training services, e.g., serving trained ML models.
[0056] It should be understood that NWDAF can contain MTLF or AnLF or both logical functions. Wherein, NWDAF containing AnLF is locally configured with the NWDAF identity document (ID) containing MTLF and the analysis ID(s) supported by each NWDAF containing MTLF to retrieve the trained ML model. If necessary, NWDAF containing AnLF uses NWDAF discovery for NWDAF containing MTLF in the configuration ID set of NWDAF containing MTLF.
[0057] It should be understood that in order to ensure the accuracy of the analysis output of the analysis ID, based on the UE abnormal behavior analysis from itself or other NWDAFs, including the abnormal UE list and the observed time window, the NWDAF is used to detect and can delete the input data from the abnormal UE, and then a new ML model and / or analysis output can be generated for the analysis ID during the observed time window without the input data related to the abnormal UE list, and then the ML model information and / or analysis output is sent / updated to the subscribed NWDAF service consumers.
[0058] To support NF to discover and select an NWDAF instance containing MTLF, AnLF or both that is able to provide the required services for the required type of analytics (e.g. analytics exposure or ML model provisioning), each NWDAF instance, when registering with NRF, should provide a list of supported analytics IDs (perhaps one for each supported service) along with other NRF registration elements of the NF profile. A NF that needs to discover an NWDAF instance that provides support for some specific services for a specific type of analytics can query the NRF for NWDAFs that support the required services and the required analytics IDs.
[0059] The NWDAF architecture allows multiple NWDAF instances to be arranged in a hierarchy / tree with a flexible number of layers / branches. The number and organization of hierarchy layers and the functionality of each NWDAF instance remains a deployment choice.
[0060] In a hierarchical deployment, when a data collection coordination function (DCCF) network element is not present in the network, the NWDAF can provide data collection exposure capabilities for generating analytics based on data collected by other NWDAFs.
[0061] In order to make NWDAF discoverable in certain network deployments, NWDAF can be configured (e.g. for UE mobility profiling) to register the UEs it serves and the associated profiling IDs in UDM (Nudm_UECM_Register service operation). Registration in UDM should be done when NWDAF starts serving a UE or collecting data for a UE. Deregistration in UDM occurs when NWDAF deletes the profiling context of the UE for the associated profiling ID.
[0062] In future communication systems, the network data analysis function network element may still be an NWDAF network element, or may have other names, which is not limited in this application.
[0063] Optionally, the network architecture may also include a DCCF network element and an analytics data repository function (ADRF) network element. Among them, ADRF provides consumers with storage and retrieval services for data and analysis. Exemplarily, the consumer sends a data management storage request (NadrfDataManagementStorageRequest) containing the data or analysis to be stored to ADRF; or, the consumer sends a data management storage subscription request (NadrfDataManagementStorageSubscriptionRequest) to ADRF, requesting ADRF to subscribe to receive data or analysis for storage, and then ADRF subscribes to NWDAF or DCCF to obtain data or analysis, and provides the ADRF notification address (or notification association ID). The analysis or data is then provided as a notification using the DCCF data management (NdccfDataManagement) service, the NWDAF data management (NnwdafDataManagement) service, or the MFAF data management (Nmfaf_3caDataManagement) service.
[0064] Exemplarily, a consumer sends a data management retrieval request (NadrfDataManagementRetrievalRequest) to ADRF to retrieve data or analysis for a specified data or analysis collection time window. ADRF determines the availability of data or analysis in its repository and sends the data or analysis, or instructions for obtaining data or analysis, to the consumer in response; alternatively, a consumer sends a data management retrieval subscription request (NadrfDataManagementRetrievalSubscribe) to ADRF to retrieve data or analysis for a specified data or analysis collection time window. If the time window includes the future and ADRF has subscribed to receive data or analysis, subsequent notifications received by ADRF will be sent by ADRF to the notification endpoint. ADRF determines the availability of data or analysis and sends a success / failure indication to the consumer in response. ADRF then sends one or more notifications to the notification address (or notification association ID) specified by the consumer using a data management retrieval notification (NadrfDataManagementRetrievalNotify). The notification provides data or analysis, or provides instructions to the endpoint to obtain data or analysis using a data management retrieval request (NadrfDataManagementRetrievalRequest).
[0065] It is understandable that the above network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualized functions instantiated on a shared platform (e.g., a cloud platform). In short, an NF can be implemented by hardware or software.
[0066] Figure 1 Where Nudm, Nnwdaf, Nausf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. For example, the meaning of the above interface serial numbers can refer to the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above interface serial numbers. It should be noted that, Figure 1 The interface name between the various network functions in the system architecture is only an example. In a specific implementation, the interface name of the system architecture may also be other names, which are not limited in this application. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.
[0067] It should be noted that the interfaces between the control plane network elements may also be point-to-point interfaces, which will not be described in detail here.
[0068] It should be understood that the above-mentioned network architecture applicable to the embodiments of the present application is only an exemplary description, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.
[0069] It should also be understood that Figure 1 The NRF, UDM, etc. shown can be understood as network elements for implementing different functions, for example, they can be combined into network slices as needed. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network elements.
[0070] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other names.
[0071] It should also be understood that Figure 1 The interface name between each network element is only an example. The name of the interface in the specific implementation may be other names, and this application does not specifically limit this. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the message itself.
[0072] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0073] In the 5G service-oriented system architecture, the two parties communicating based on the service-oriented interface are respectively called service consumers and service providers. Among them, the party requesting the service is called service consumer, and the party providing the service is called service producer. Service consumers can also be called consumers, consumer network elements, users, requesters or requesters, or service consumer network elements. Service providers can also be called providing network elements, service providing network elements, providers, producers or responders, etc., which are not limited in this application.
[0074] Before explaining the present application, the ML model acquisition method in the related art is described here: the solution in the 3GPP technical specification (TS) 23.288 standard, and the current NWDAF-based ML model acquisition method is defined by 3GPP SA2. Figure 2 This is a flowchart of a method for obtaining an ML model provided by the related technology. Figure 2 As shown, the method comprises the following steps:
[0075] S201. The consumer sends a machine learning model provision request (Nnwdaf_MLModelProvision Request) of a network data analysis function to the NWDAF including the MTLF function.
[0076] S202, the NWDAF including the MTLF function determines whether the machine learning model is to be retrieved from the ADRF (NWDAFdetermines whether ML model is to be retrieved from ADRF). Further, S203 is executed, or S206 is executed.
[0077] S203. If MTLF decides to obtain indirectly from MTLF, NWDAF including MTLF function sends a model management retrieval request (Nadrf_MLModelManagement_Retrieve Request) of the analysis data storage function_machine learning to ADRF.
[0078] S204. ADRF sends the analysis data storage function_machine learning model management retrieval response (Nadrf_MLModelManagement_Retrieve Response) to the NWDAF including the MTLF function.
[0079] S205. The NWDAF including the MTLF function sends a machine learning model provision response (Nnwdaf_MLModelProvision Response) of the network data analysis function to the consumer.
[0080] S206. If MTLF decides to obtain data directly or indirectly from ADRF, the consumer sends a Nadrf_MLModelManagement_Retrieve Request to ADRF.
[0081] S207. ADRF sends the analytical data storage function_machine learning model management retrieval response (Nadrf_MLModelManagement_Retrieve Response) to the consumer.
[0082] It should be noted that the current NWDAF-based ML model acquisition method defined by SA2 does not clearly define how MTLF decides whether to acquire directly or indirectly.
[0083] It should be noted that the solution proposed by 3GPP SA3 solves the issue of permissions for NWDAF-based ML model acquisition. Figure 3 FIG. 1 is a flowchart of another method for obtaining an ML model provided by the related art. Figure 3 As shown, the method comprises the following steps:
[0084] S301. The network function service provider (NF service producer, NFp) (for example, NWDAF MTLF) sends an analysis data storage function_machine learning model management_storage request (Nadrf_MLModelManagement_Storage Request) to ADRF.
[0085] The Nadrf_MLModelManagement_Storage Request includes the MTLF ID, the model ID, the model address in the model training logic function, for example, the Uniform Resource Locator (URL) 1, and the allowed NFc list.
[0086] It should be noted that before executing step 301, the following steps are also included:
[0087] NFp (for example, NWDAF MTLF) is registered in NRF, namely Register NWDAF / MTLF; during registration, the registration request includes an Analytics ID and an Interoperability ID.
[0088] NFc (eg, NWDAF AnLF) is registered in NRF, namely Register NWDAF / AnLF; during registration, the registration request includes Analytics ID and vendor ID.
[0089] NFp optionally encrypts the ML model (Conditionally encrypt the ML model).
[0090] S302. ADRF sends a response (Response) to NFp.
[0091] The response includes the Model ID and the model address in the analysis data storage function (Model Address in ADRF), for example, URL2.
[0092] S303, NFc Discovery of MTLF in NRF.
[0093] Here, the MTLF can be discovered based on the Analytics ID.
[0094] S304. NFc sends a network storage function_access token acquisition request (Nnrf_AccessToken_GetRequest) to NRF.
[0095] The Nnrf_AccessToken_Get Request includes information of the analysis ID, the vendor ID, and the target NF, for example, ADRF.
[0096] S305. NRF sends a network storage function_access token_get response (Nnrf_AccessToken_GetResponse) to NFc.
[0097] Among them, Nnrf_AccessToken_Get Response includes relevant information of token 1.
[0098] S306. NFc sends a model acquisition request (Nnwdaf_MLModelProvision Request) of the machine learning network data analysis function to NFp.
[0099] Among them, Nnwdaf_MLModelProvision Request includes relevant information of analysis ID, supplier ID, and token 1.
[0100] S307: NRF and NFp authorize NFc and store NFc ID (Authorize NFc and Store NFcID).
[0101] S308. NFp sends the analysis data storage function_machine learning model management storage update (Nadrf_MLModelManagement_Storage Update) to ADRF.
[0102] Among them, Nadrf_MLModelManagement_Storage Update includes MTLF ID, Model ID, and allowed NFc list.
[0103] S309. ADRF sends a response (Response) to NFp.
[0104] The response includes the Model ID.
[0105] S310. NFp sends a machine learning model provision response (Nnwdaf_MLModelProvision Response) of a network data analysis function to NFc.
[0106] Among them, Nnwdaf_MLModelProvision Response includes Model ID, model address (Modeladdress), [ADRFID, storage transaction (Storage Transaction) ID].
[0107] It should be noted that if the ML model is to be retrieved from ADRF, the following S311 to S315 are executed.
[0108] S311. NFc sends Nnrf_AccessToken_Get to NRF.
[0109] Among them, Nnrf_AccessToken_Get includes identification information related to the target NF (ADRF).
[0110] S312. NRF sends a network storage function_access token_get response (Nnrf_AccessToken_GetResponse) to NFc.
[0111] Among them, Nnrf_AccessToken_Get Response includes token 2.
[0112] S313. NFc sends an analytical data storage function_machine learning model management_retrieval request (Nadrf_MLModelManagement_Retrieval Request) to ADRF.
[0113] Among them, Nadrf_MLModelManagement_Retrieval Request includes Analytics ID and token2.
[0114] S314. ADRF sends an analytical data storage function_machine learning model management_retrieval response (Nadrf_MLModelManagement_Retrieval Response) to NFc.
[0115] Among them, Nadrf_MLModelManagement_Retrieval Response) includes the model address in ADRF (Model Address in ADRF).
[0116] S315. NFc optionally decrypts the ML model (Conditionally decrypt the ML model).
[0117] It should be noted that the current SA3-defined access rights processing method for ML model acquisition based on NWDAF, after MTLF verifies the token and determines that NFc has the authority to obtain the model, it will store the NFc ID and pass the NFc list that MTLF allows to access locally to ADRF. After receiving it, ADRF will update the ADRF local access list according to the NFc ID allowed by MTLF. Then, the ADRF information will be passed to NFc, so that NFc can directly obtain the model from ADRF.
[0118] Figure 4 A flow chart of a communication method provided in an embodiment of the present application is shown as follows: Figure 4 As shown, this method is applied to Figure 1 The network architecture 100 shown, the method includes:
[0119] Step 401: The second function sends first information to the first function.
[0120] The first information includes relevant information of at least one network function service consumer or provider who is authorized to access the second function.
[0121] In the embodiment of the present application, the first function may be MTLF; or NWDAF including MTLF; obviously, in the present application, the first function belongs to the network function service provider (NFp).
[0122] In the embodiment of the present application, the second function may be ADRF.
[0123] In the embodiment of the present application, the relevant information of at least one network function service consumer includes but is not limited to at least one NF instance ID (NF Instance Id(s) of the NF service consumer) of the NFc, at least one NFc ID, at least one Analytics ID corresponding to the NFc, and at least one Vendor ID corresponding to the NFc.
[0124] In the implementation of this application, the relevant information of at least one supplier includes a supplier ID, which is used to indicate the supplier of the NF and can be the supplier's ID or the supplier's internal implementation.
[0125] In the embodiment of the present application, the first information is sent in the following ways: in-band, out-of-band, media, signaling, data, message, control plane, user plane, etc. Among them, the first information can be sent through the existing media channel to better be compatible with the existing system and reduce the cost of system transformation. In addition, when the first function is multi-party, the established media plane communication channel is a one-to-many multicast / broadcast communication channel, so that the first information is sent only once through the established multicast / broadcast communication channel, and other first functions can receive it, effectively reducing the number of information sent.
[0126] In the embodiment of the present application, the relevant information of at least one network function service consumer or supplier authorized to access the second function includes a list of NFcs or Vendors allowed to access the second function. That is, the first information can be implemented in the form of a list.
[0127] In the embodiment of the present application, the first function and the second function may be a functional network element, which may be a physical entity in a hardware device, a software instance running on dedicated hardware, or a virtualized function instantiated on a platform. In short, an NF may be implemented by hardware or software.
[0128] Step 402: The first function receives the first information sent by the second function.
[0129] Step 403: The first function determines a method for the first network function service consumer to obtain the target model based on the first information.
[0130] In the embodiment of the present application, the first network function service consumer (NFc) may include the NWDAF of AnLF.
[0131] In the embodiments of the present application, the target includes but is not limited to an ML model and an artificial intelligence (AL) model.
[0132] In the embodiment of the present application, the manner in which the first NFc obtains the target model includes that the first NFc directly obtains the target model from ADRF, and the first NFc indirectly obtains the target model from ADRF through MTLF.
[0133] It should be noted that this implementation is applicable to the case where NFc and NFp belong to the same operator, and is also applicable to the case where NFc and NFp belong to different operators, and this application does not make any specific limitation.
[0134] The embodiment of the present application provides a communication method, which includes: the second function sends a first message to the first function; wherein the first message includes relevant information of at least one network function service consumer or supplier authorized to access the second function; the first function receives the first message sent by the second function; the first function determines the way in which the first network function service consumer obtains the target model according to the first message. That is to say, the present application enables MTLF to understand the authority of ADRF by sending the first information of the second function, i.e., ADRF, i.e., the authorized access NF or supplier list to the first function, i.e., MTLF, so that after MTLF determines that the first NFc has the authority to access the ML model, for the ML model acquisition request subsequently received by MTLF from the first NFc, MTLF can compare the information corresponding to the first NFc with the NF or supplier list, confirm whether the first NFc has the authority to access ADRF, and then determine whether the first NFc directly obtains the ML model or indirectly obtains the ML model, thus solving the problem mentioned in the related art that the method proposed in SA3 and the method defined in the SA2 standard scheme are logically inconsistent. At the same time, in this application, MTLF determines whether the first NFc directly obtains the ML model or indirectly obtains the ML model based on the authorized access NF or supplier list. Compared with the solution proposed by SA3, in which MTLF determines that NFc that can access the ML model can directly obtain the ML model from ADRF, it can ensure the security of some ADRFs that need to hide their own addresses and avoid the problem of information leakage caused by the corresponding functions of different manufacturers being able to access each other.
[0135] In some embodiments, step 401, the second function sends the first information to the first function, and step 402, the first function receives the first information sent by the second function, can be implemented by the following steps:
[0136] Step A1: The first function sends a model storage request to the second function.
[0137] In some embodiments, the model storage request (e.g., Nadrf_MLModelManagement_StorgeRequest) may include relevant information of at least one network function service consumer or supplier authorized to access the first function; of course, the model storage request may not include relevant information of at least one network function service consumer or supplier authorized to access the first function.
[0138] In an embodiment of the present application, the relevant information of at least one network function service consumer or supplier authorized to access the first function includes a list of NFcs or Vendors allowed to access the MTLF. That is, the relevant information of at least one network function service consumer or supplier authorized to access the first function can be implemented in the form of a list.
[0139] In the embodiments of the present application, the methods of sending the model storage request include: in-band, out-of-band, media, signaling, data, message, control plane, user plane, etc.
[0140] Step A2: The second function receives the model storage request sent by the first function.
[0141] In some embodiments, when the second function is registered, the second function configures the first information in the third function; that is, when the ADRF is registered, it is necessary to configure the NFc or Vendor list that can access it in the NRF.
[0142] In the embodiment of the present application, after the second function, i.e., ADRF, receives relevant information of at least one network function service consumer or supplier authorized to access the first function, i.e., the NFc or Vendor list allowed to access MTLF, ADRF locally queries whether the list is the same as the first information, i.e., the NFc or Vendor list allowed to access ADRF. After comparison, ADRF can locally decide whether to update the NFc or Vendor list allowed to access ADRF based on the NFc or Vendor list allowed to access MTLF, and then pass the NFc or Vendor list allowed to access ADRF to MTLF.
[0143] Step A3: The second function sends a model storage response to the first function.
[0144] The model storage response includes first information.
[0145] In the embodiment of the present application, the model storage response (Nadrf_MLModelManagement_StorgeResponse) includes a list of NFcs or Vendors that are allowed to access ADRF.
[0146] Step A4: The first function receives the model storage response sent by the second function.
[0147] In some embodiments, step 403, the first function determines the way in which the first network function service consumer obtains the target model according to the first information, which can be implemented by the following steps:
[0148] Step B1: The first function receives second information sent by the first network function service consumer.
[0149] The second information is used to request the target model; the second information includes identification information of the first network function service consumer.
[0150] In the embodiment of the present application, the first network function service consumer sends a model acquisition request (Nadrf_MLModelManagement_Retrieve Request) carrying the second information to the first function. The first function receives the model acquisition request and analyzes the target model that the first network function service consumer expects to obtain.
[0151] Here, the second information includes identification information of the first network function service consumer and identification information of the target model. Each network function service consumer and each model has unique identification information. In some embodiments, the identification information includes color identification, graphic identification, text identification, digital identification, location identification, etc. Different network function service consumers and different models can use the same type of identification information; of course, the types of identification information of each network function service consumer and each model may not be exactly the same, or the types of identification information of each network function service consumer and each model may be completely different.
[0152] In some embodiments, the identification information includes at least one of the following: a supplier identification of the first network function consumer; a network function instance identification of the first network function consumer; and an analysis identification corresponding to the first network function consumer.
[0153] In some embodiments, the analytical ID can indicate the type of target model that the NFc desires to access.
[0154] Step B2: The first function determines a method for the first network function consumer to obtain the target model based on the identification information and the first information.
[0155] In some embodiments, if the identification information matches the first information, it is determined that the first network function consumer acquires the target model in the first way; if the identification information does not match the first information, it is determined that the first network function consumer acquires the target model in the second way.
[0156] It should be noted that the match indicates a complete match or a partial match; for example, if the identification information completely matches a certain sub-information in the first information, that is, they are exactly the same, then it means that the identification information matches the first information; or if the identification information partially matches a certain type of sub-information in the first information, that is, they partially overlap, then it means that the identification information matches the first information. It should be noted that if the identification information is not the same as any sub-information in the first information, or the identification information does not overlap with any type of sub-information in the first information, then it means that the identification information does not match the first information.
[0157] Exemplarily, the first function compares the first supplier identifier corresponding to the first network function service consumer, the first analysis identifier corresponding to the first network function service consumer, the analysis identifier corresponding to each network function consumer in the first information, and the supplier identifier of each network function consumer in the first information, or compares the first network function instance identifier corresponding to the first network function service consumer, the first analysis identifier corresponding to the first network function service consumer, the analysis identifier corresponding to each network function consumer, and the network function instance identifier of each network function consumer to obtain a comparison result. If the comparison result indicates that the first supplier identifier and the first analysis identifier are in the first information, or the first network function instance identifier and the first analysis identifier are in the first information, it is determined that the first network function consumer adopts the first method to obtain the target model; if the comparison result indicates that the first supplier identifier and the first analysis identifier are not in the first information, or the first network function instance identifier and the first analysis identifier are not in the first information, it is determined that the first network function consumer adopts the second method to obtain the target model.
[0158] It should be noted that, when the first network function consumer adopts the first method to obtain the target model, the first function sends the identifier of the second function to the first network function service consumer; the first network function service consumer sends the third information to the second function; wherein the third information is used to request to obtain the information of the target model; the second function receives the third information; the second function sends the information of the target model to the first network function service consumer; and the first network function service consumer receives the information of the target model.
[0159] It should be noted that, when the first network function consumer adopts the second method to obtain the target model, the first function sends the third information to the second function; wherein the third information is used to request to obtain the information of the target model; the second function receives the third information; the second function sends the information of the target model to the first function; the first function receives the information of the target model; the first function sends the information of the target model to the first network function consumer; and the first network function service consumer receives the information of the target model.
[0160] In the embodiment of the present application, the information of the target model includes one or more of the target model identifier or the address of the target model or the hash value of the target model address; wherein the address of the model may be a URL or a fully qualified domain name (Fully Qualified Domain Name, FQDN). Correspondingly, the hash value of the model address may be a hash value of the URL or FQDN.
[0161] It should be noted that the third information sent by the first function to the second function is different information carried by different messages compared to the third information sent by the first network function service consumer to the second function, but these two different information are both used to request the second function to obtain the target model.
[0162] In the embodiment of the present application, the identification of the second function includes but is not limited to the ID of the second function and the address of the second function. In some embodiments, the second function has a unique identification; the identification includes a color identification, a graphic identification, a text identification, a digital identification, a location identification, etc.
[0163] This proposal proposes a new ML model acquisition judgment method based on NWDAF. ADRF configures the NFc list authorized to access in NRF in advance, and returns the NFc list authorized to access to MTLF when MTLF stores the model in ADRF. When MTLF receives a model acquisition request, it can compare the list with NFc to confirm whether NFc has the authority to access ADRF, and then determine the ML model acquisition method (directly or indirectly).
[0164] In this application, "communication" can also be described as "data transmission", "information transmission", "data processing", etc. "Transmission" includes "sending" and "receiving".
[0165] In the present application, "first", "second" and various numerical references are used to distinguish for the convenience of description and are not used to limit the scope of the embodiments of the present application. For example, different messages are distinguished, rather than used to describe a specific order or sequence. It should be understood that the objects described in this way can be interchanged where appropriate so as to be able to describe solutions other than the embodiments of the present application.
[0166] Figure 5 is a flow chart of a communication method provided in an embodiment of the present application. Figure 5 As shown, the method comprises the following steps:
[0167] S501. NFp (eg, NWDAF MTLF) initiates a model storage request (Nadrf_MLModelManagement_StorgeRequest) to ADRF.
[0168] Among them, Nadrf_MLModelManagement_StorgeRequest carries the Model ID and Modeladdress; that is, MTLF brings the Model ID and Modeladdress to ADRF through Nadrf_MLModelManagement_StorgeRequest.
[0169] It should be noted that before executing step 501, the following steps are also included:
[0170] Register NWDAF / MTLF. When registering, the registration request includes AnalyticsID and Interoperability ID, and the interoperability indicator of the model needs to be configured in NRF in advance according to the Analytics ID to indicate the Vendor or NF that can obtain the above model.
[0171] It should be understood that the interoperability identity is a list of vendor IDs of NWDAFs that are allowed to obtain ML models from NFp.
[0172] Register NWDAF / AnLF. When registering AnLF, the registration request includes the Vendor ID 、 Analytics ID.
[0173] Register ADRF in NRF. When registering ADRF, the registration request includes Analytics ID and the NFc list that ADRF is allowed to access (ADRF allowed NFc list). Furthermore, ADRF can access the NFc or Vendor list of ADRF in NRF configuration; it should be noted that the NFc or Vendor list is determined by the Analytics ID.
[0174] If MTLF and ADRF are not devices from the same manufacturer, the model needs to be encrypted and integrity protected before transmission, that is, NFp optionally encrypts the ML model (Conditionally encrypt the ML model).
[0175] S502. ADRF sends a model storage response (Nadrf_MLModelManagement_StorgeResponse) to NFc.
[0176] In some embodiments, after receiving the Model address, ADRF can selectively decide whether to download the model to the local storage ADRF; and ADRF informs NFc through Nadrf_MLModelManagement_StorgeResponse that the model has been stored, and provides the NFc or Vendor list that allows access to this ADRF to MTLF.
[0177] It should be noted that the NFc or Vendor list can be configured based on the Analytics ID and the Vendor ID.
[0178] S503. NFc (eg, NWDAF AnLF) discovers MTLF according to Analytics ID.
[0179] S504. NFc sends a token request (Nnrf_AccessToken_Get Request) to NRF.
[0180] Among them, AnLF initiates a token request for MTLF to NRF, and the request should include Vendor ID and Analytics ID.
[0181] S505, NRF uses the interoperability indicator to verify the analysis ID, vendor ID and target MTLF
[0182] It should be noted that the NRF compares and verifies the received Analytics ID, Vendor ID with the configured MTLF Interoperability indicator (NRF checks the Analytics ID, Vendor ID and Target MTLF with Interoperability indicator). Further, if the verification passes, a token is issued and S506 is executed.
[0183] S506. NRF sends a token response (Nnrf_AccessToken_Get Response) to NFc.
[0184] It should be noted that NRF returns the token to AnLF.
[0185] S507: NFc initiates a model acquisition request (Nnwdaf_MLModelProvision Request) to NFp.
[0186] In the embodiment of the present application, in addition to the token, the Nnwdaf_MLModelProvision Request also needs to carry the Vendor ID and the Analytics ID.
[0187] S508. NFp (e.g., NWDAF MTLF) compares the Analytic ID and Vendor ID with the list provided by ADRF (MTLF checks the Analytic ID and Vendor ID with the allowed NFc list of ADRF), or compares the Analytic ID and NF instance ID of AnLF with the list provided by ADRF.
[0188] If this NFc is in the list provided by ADRF, the MTLF determines that this AnLF can directly access ADRF to obtain the model (If ML Model needs to be retrieved from ADRF directly), and then executes S511 to S515.
[0189] If this NFc is not in the list provided by ADRF, MTLF decides that this AnLF cannot directly access ADRF to obtain the model. Since the ML model needs to be retrieved from ADRF and NFc does not know where the ML model is stored (If ML Model needs to be retrieved from ADRF and the NF consumer is agnostic to where the ML model is stored), it is necessary to obtain the model through MTLF, and execute S509 to S511 and S515.
[0190] S509 , NFp requests an ML model acquisition request (Nadrf_MLModelManagement_RetrieveRequest) from ADRF.
[0191] Here, the Nadrf_MLModelManagement_Retrieve Request includes Analytics ID(s), Storage Transaction Identifier, and ML model ID.
[0192] S510. ADRF sends an ML model acquisition response (Nadrf_MLModelManagement_RetrieveResponse) to NFp; that is, ADRF returns the model address to MTLF.
[0193] S511. NFp sends an ML model configuration response (Nnwdaf_MLModelProvision Response) to NFc.
[0194] It should be noted that in S511, MTLF returns the model-related information to AnLF. The model-related information can be the model address or ADRFID, either one. And only when MTLF determines in S508 that AnLF can directly obtain the model from ADRF, will ADRFID be provided in this step.
[0195] S512, NFc and NRF perform token request and response.
[0196] S513. NFc sends an ML model acquisition request (Nadrf_MLModelManagement_RetrieveRequest) to ADRF.
[0197] Among them, Analytics ID(s), Storage Transaction Identifier, Model ID in Nadrf_MLModelManagement_Retrieve Request.
[0198] S514. ADRF sends an ML model acquisition response (Nadrf_MLModelManagement_RetrieveResponse) to NFc, that is, ADRF directly returns the model address to AnLF.
[0199] S515. NFc optionally decrypts the ML model (Conditionally decrypt the ML model).
[0200] The embodiment of the present application provides a first function, which can be used to implement Figure 4 A communication method provided by a corresponding embodiment, referring to Figure 6 As shown, the first function 60 includes:
[0201] The first receiving module 601 is used to receive first information sent by the second function; wherein the first information includes relevant information of at least one network function service consumer or provider authorized to access the second function;
[0202] The first processing module 602 is used to determine a method for the first network function service consumer to obtain a target model according to the first information.
[0203] In other embodiments of the present application, the first receiving module 601 is used to receive second information sent by the first network function service consumer; wherein the second information is used to request to obtain the target model; the second information includes identification information of the first network function service consumer;
[0204] The first processing module 602 is used to determine a method for the first network function consumer to obtain a target model based on the identification information and the first information.
[0205] In other embodiments of the present application, the first processing module 602 is used to determine that the first network function consumer uses the first method to obtain the target model if the identification information matches the first information.
[0206] In other embodiments of the present application, the first processing module 602 is used to determine that the first network function consumer adopts the second method to obtain the target model if the identification information does not match the first information.
[0207] In other embodiments of the present application, the identification information includes at least one of the following: a supplier identification of the first network function consumer; a network function instance identification of the first network function consumer; and an analysis identification corresponding to the first network function consumer.
[0208] In other embodiments of the present application, the first sending module 603 is used to send the identifier of the second function to the first network function service consumer when the first network function consumer adopts the first method to obtain the target model.
[0209] In other embodiments of the present application, the first sending module 603 is used to send third information to the second function when the first network function consumer adopts the second method to obtain the target model; wherein the third information is used to request to obtain information of the target model;
[0210] The first receiving module 601 is used to receive the information of the target model sent by the second function;
[0211] The first sending module 603 is used to send information of the target model to the first network function service consumer.
[0212] In other embodiments of the present application, the first sending module 603 is used to send a model storage request to the second function;
[0213] The first receiving module 601 is used to receive a model storage response sent by the second function; wherein the model storage response includes first information.
[0214] In other embodiments of the present application, the model storage request includes relevant information of at least one network function service consumer or provider authorized to access the first function.
[0215] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.
[0216] It should be noted that in the embodiments of the present application, if the above-mentioned communication method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including a number of instructions for a terminal device to execute all or part of the methods of each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a magnetic disk or an optical disk. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.
[0217] The embodiment of the present application provides a second function, which can be used to implement Figure 4 A communication method provided by a corresponding embodiment, referring to Figure 7 As shown, the second function 70 includes:
[0218] The second sending module 701 is used to send first information to the first function; wherein the first information includes relevant information of at least one network function service consumer or provider authorized to access the second function.
[0219] In other embodiments of the present application, the second receiving module 702 is used to receive a model storage request sent by the first function;
[0220] The second sending module 701 is used to send a model storage response to the first function; wherein the model storage response includes first information.
[0221] In other embodiments of the present application, the model storage request includes relevant information of at least one network function service consumer or provider authorized to access the first function.
[0222] In other embodiments of the present application, the second processing module 703 is used to configure the first information in the third function when the second function is registered.
[0223] In other embodiments of the present application, the second receiving module 702 is used to receive third information sent by the first network function service consumer when the first network function consumer obtains the target model in the first manner; wherein the third information is used to request to obtain information of the target model;
[0224] The second sending module 701 is used to send information of the target model to the first network function service consumer
[0225] In other embodiments of the present application, the second receiving module 702 is used to receive the third information sent by the first function when the first network function consumer adopts the second method to obtain the target model; wherein the third information is used to request to obtain the information of the target model;
[0226] The second sending module 701 is used to send information of the target model to the first function.
[0227] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.
[0228] It should be noted that in the embodiments of the present application, if the above-mentioned communication method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including a number of instructions for a terminal device to execute all or part of the methods of each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a magnetic disk or an optical disk. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.
[0229] Figure 8 800 is a schematic structural diagram of a communication device 800 provided in an embodiment of the present application. The communication device can have a first function or a second function. Figure 8 The communication device 800 shown includes a first processor 810, and the first processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0230] Alternatively, if Figure 8 As shown, the communication device 800 may further include a first memory 820. The first processor 810 may call and run a computer program from the first memory 820 to implement the method in the embodiment of the present application.
[0231] The first memory 820 may be a separate device independent of the first processor 810 , or may be integrated into the first processor 810 .
[0232] Alternatively, if Figure 8 As shown, the communication device 800 may further include a transceiver 830, and the first processor 810 may control the transceiver 830 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
[0233] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of the antennas may be one or more.
[0234] Optionally, the communication device 800 may specifically be the first function / second function of the embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the first function / second function in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0235] Fig. 9 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig. 9 The chip 900 shown includes a second processor 910, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0236] Alternatively, if Fig. 9 As shown, the chip 900 may further include a second memory 920. The second processor 910 may call and run a computer program from the second memory 920 to implement the method in the embodiment of the present application.
[0237] The second memory 920 may be a separate device independent of the second processor 910 , or may be integrated into the second processor 910 .
[0238] Optionally, the chip 900 may further include an input interface 930. The second processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0239] Optionally, the chip 900 may further include an output interface 940. The second processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0240] Optionally, the chip can be applied to the first function / second function in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the first function / second function in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0241] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0242] Fig.10 1 is a schematic block diagram of a communication system 1000 provided in an embodiment of the present application. Fig.10 As shown, the communication system 1000 includes a first function 60 and a second function 70 .
[0243] Among them, the first function 60 can be used to implement the corresponding function implemented by the first function in the above method, and the second function 70 can be used to implement the corresponding function implemented by the second function in the above method. For the sake of brevity, they are not repeated here.
[0244] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0245] As an embodiment, the processor may include one or more general-purpose central processing units (CPUs). Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer execution instructions).
[0246] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a ROM, a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0247] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
[0248] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
[0249] Optionally, the computer-readable storage medium can be applied to the first function / second function in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the first function / second function in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0250] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.
[0251] The computer program product includes one or more computer instructions. When loading and executing the computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server, a data center, etc. that includes one or more available media integration. Available media can be magnetic media, (e.g., floppy disk, hard disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid-state hard disk (SSD)), etc.
[0252] The communication method, the first function, the second function and the storage medium provided in the embodiments of the present application are introduced in detail above. The principles and implementation methods of the present application are described in detail using specific examples herein. The description of the above embodiments is only used to help understand the method and core idea of the present application. At the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present application.
[0253] It should be understood that the "one embodiment" or "an embodiment" or "an embodiment of the present application" or "the aforementioned embodiment" or "some implementations" or "some embodiments" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" or "an embodiment of the present application" or "the aforementioned embodiment" or "some implementations" or "some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The above-mentioned sequence numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.
[0254] In the absence of special instructions, the first function / second function performs any step in the embodiment of the present application, and the processor of the first function / second function may perform the step. Unless otherwise specified, the embodiment of the present application does not limit the order in which the first function / second function performs the following steps. In addition, the methods used to process data in different embodiments may be the same method or different methods.
[0255] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.
[0256] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0257] In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be a separate unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.
[0258] The methods disclosed in several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.
[0259] The features disclosed in several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.
[0260] The features disclosed in several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.
[0261] A person of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, magnetic disks or optical disks.
[0262] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer storage medium. Based on such an understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.
[0263] As used in the embodiments of the present application and the appended claims, the singular forms "a," "an," "said," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
[0264] It should be noted that in each embodiment involved in the present application, all steps may be executed or part of the steps may be executed as long as a complete technical solution can be formed.
[0265] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A communication method, characterized in that: Applied to the first function, the method comprises: Receiving first information sent by a second function; wherein the first information includes relevant information of at least one network function service consumer or provider authorized to access the second function; According to the first information, a method for the first network function service consumer to obtain the target model is determined.
2. The method according to claim 1, characterized in that The determining, according to the first information, a way for the first network function service consumer to obtain the target model includes: Receiving second information sent by the first network function service consumer; wherein the second information is used to request to obtain the target model; the second information includes identification information of the first network function service consumer; Based on the identification information and the first information, a manner in which the first network function consumer acquires a target model is determined.
3. The method according to claim 2, characterized in that The determining, based on the identification information and the first information, a manner in which the first network function consumer acquires the target model includes: If the identification information matches the first information, it is determined that the first network function consumer acquires the target model in a first manner.
4. The method according to claim 2, characterized in that: The determining, based on the identification information and the first information, a manner in which the first network function consumer acquires the target model includes: If the identification information does not match the first information, it is determined that the first network function consumer acquires the target model in a second manner.
5. The method according to claim 2, characterized in that: The identification information includes at least one of the following: an identifier of a supplier of the first network function consumer; a network function instance identifier of the first network function consumer; The analysis identifier corresponding to the first network function consumer.
6. The method according to claim 3, characterized in that The method further comprises: In a case where the first network function consumer acquires the target model in the first manner, an identifier of the second function is sent to the first network function service consumer.
7. The method according to claim 4, characterized in that The method further comprises: When the first network function consumer obtains the target model in the second manner, sending third information to the second function; wherein the third information is used to request to obtain information of the target model; receiving information of the target model sent by the second function; The target model information is sent to the first network function service consumer.
8. The method according to any one of claims 1 to 7, characterized in that The receiving the first information sent by the second function includes: Sending a model storage request to the second function; Receive a model storage response sent by the second function; wherein the model storage response includes the first information.
9. The method according to claim 8, characterized in that The model storage request includes relevant information of at least one network function service consumer or provider who is authorized to access the first function.
10. A communication method, characterized in that: Applied to the second function, the method comprises: Sending first information to the first function; wherein the first information includes relevant information of at least one network function service consumer or provider who is authorized to access the second function.
11. The method according to claim 10, characterized in that The sending the first information to the first function includes: Receive a model storage request sent by the first function; A model storage response is sent to the first function; wherein the model storage response includes the first information.
12. The method according to claim 11, characterized in that The model storage request includes relevant information of at least one network function service consumer or provider who is authorized to access the first function.
13. The method according to claim 10, characterized in that The method further comprises: When the second function is registered, the first information is configured in the third function.
14. The method according to any one of claims 10 to 13, characterized in that The method further comprises: In the case where the first network function consumer acquires the target model in the first manner, receiving third information sent by the first network function service consumer; wherein the third information is used to request acquisition of information of the target model; The target model information is sent to the first network function service consumer.
15. The method according to any one of claims 10 to 13, characterized in that The method further comprises: In the case where the first network function consumer adopts the second method to obtain the target model, receiving third information sent by the first function; wherein the third information is used to request to obtain information of the target model; The target model information is sent to the first function.
16. A first function, characterized in that, The first function includes: A first receiving module, configured to receive first information sent by a second function; wherein the first information includes relevant information of at least one network function service consumer or provider authorized to access the second function; The first processing module is used to determine a method for the first network function service consumer to obtain a target model according to the first information.
17. A second function, characterized in that, The second function includes: A second sending module, used for sending first information to the first function; The first information includes relevant information of at least one network function service consumer or provider who is authorized to access the second function.
18. A first function, characterized in that, The first function includes: A first memory, used to store executable instructions; The first processor is configured to implement the communication method according to any one of claims 1 to 9 when executing the executable instructions stored in the first memory.
19. A second function, characterized in that, The second function includes: A second memory, used for storing executable instructions; The second processor is configured to implement the communication method according to any one of claims 10 to 15 when executing the executable instructions stored in the second memory.
20. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the communication method according to any one of claims 1 to 9, or the communication method according to any one of claims 10 to 15.
Citation Information
Patent Citations
Authority control method and network equipment
CN111385262A
Authorization in communication network
CN114339760A
Machine learning (ML) model retraining in 5g core network
WO2023057849A1