Method and apparatus for registering data retrieval

Abstract

Embodiments of the present disclosure provide methods and apparatuses for registration data retrieval. A method performed by a network function service consumer entity includes sending, to a data management entity, a request for retrieving at least two registration data sets related to a user equipment. The request includes two or more corresponding registration data set names. The method further includes receiving, from the data management entity, a response. The response includes the at least two requested registration data sets related to the user equipment.

Description

TECHNICAL FIELD

[0001] The non-limiting and exemplary embodiments of the present disclosure generally relate to the field of communication technology, and in particular to methods and apparatus for registration data retrieval. BACKGROUND

[0002] This section introduces various aspects that can be helpful in achieving a better understanding of the present disclosure. As such, the statements of this section are to be read in that light, and are not to be understood as an acknowledgement that what is in the prior art or what is not in the prior art.

[0003] In a communication network, registration data related to a specific UE (User Equipment) can be retrieved by various network functional entities such as Network Data Analytics Function (NWDAF), Home Subscriber Server (HSS), etc.

[0004] For example, data collection from network functions (NFs) can be used by the NWDAF to subscribe / unsubscribe at any NF to be notified about a set of events. Data collection from NFs can be based on the NF’s service, e.g. AMF (Access and Mobility Management Function), SMF (Session Management Function), UDM (Unified Data Management), PCF (Policy Control Function), NRF (NF Repository Function), and AF (Application Function) (which can be through NEF (Network Exposure Function)). This data collection service can be used directly in order to retrieve behavior data for a single UE or a group of UEs (e.g. UE reachability), as well as to retrieve global UE information (e.g. number of UEs present in a geographical area). Table 1 shows the services for data collection consumed by the NWDAF. The disclosure of 3rd Generation Partnership Project (3GPP) TS 23.288 V16.2.0 is incorporated by reference in its entirety.

[0005] Table 1: Services for data collection consumed by the NWDAF

[0006]

[0007] In order to retrieve data related to a specific UE, the NWDAF should first determine which NF instances are serving the UE, as described in Table 2, unless the NWDAF has already obtained this information due to a recent operation related to the UE.

[0008] Table 2: NF services consumed by the NWDAF to determine which NF instances are serving a UE

[0009]

[0010] The request to UDM providing SUPI (Subscription Permanent Identifier) or group identity can be used to determine the AMF, SMF instance. To determine the SMF serving the PDU (Protocol Data Unit) session, the NWDAF can additionally provide the DNN (Data Network Name) and S-NSSAI (Single Network Slice Selection Assistance Information) of the PDU session; otherwise, the NWDAF will get a list of possible SMFs (e.g. one SMF per PDU session).

[0011] Figure 1a Interactions are shown when an SMS-GMSC (Short Message Service - Gateway Mobile Switching Centre) retrieves routing information for MT-SMS (Mobile Terminating - Short Message Service) delivery from the HSS.

[0012] In step 1, the HSS receives a request for routing information from the SMS-GMSC via MAP (Mobile Application Part) or S6c.

[0013] In step 2, the HSS queries the EPS-UDR via Ud to read the registered MME (Mobile Management Entity) / MSC (Mobile Services Center), the registered SGSN (Serving GPRS (General Packet Radio Service) Support Node), the UE not reachable flags for MME / MSC, SGSN, 3GppSMSF (3GPP Short Message Service Function) and Non3GppSMSF and the SMSF registration notification flag.

[0014] In step 3, if the UE not reachable flags for 3GppSMSF, Non3GppSMSF and the SMSF registration notification flag are not set and unless it is known that the user is not registered in 5GC (5th Generation Core Network), the HSS retrieves the registered SMSF address (if any) from the UDM.

[0015] In steps 4-5, the UDM retrieves the requested information from the 5GS-UDR (5th Generation System Unified Data Repository).

[0016] In step 6, the UDM forwards the retrieved address to the HSS (if any).

[0017] Step 7, the HSS returns the relevant MT-SMS target node addresses registered in the HSS and / or UDM to the SMS-GMSC and the procedure ends.

[0018] Otherwise, if the MT-SMS target node addresses are not registered in both the HSS and the UDM, a negative response (user SM does not exist) is sent to the SMS-GMSC and the procedure continues with steps 8 to 11.

[0019] At step 8, the HSS includes the SMSC address in the Message Waiting Data (MWD) stored in the EPS-UDR (Evolved Packet System - UDR) and notifies the SMSC in the way defined in 3GPP TS 23.040 V15.3.0, the disclosure of which is incorporated by reference herein in its entirety. The relevant UE Not Reachable flag and SMSF Registration Notification flag are set in the EPS-UDR.

[0020] At step 9, the HSS subscribes in the UDM to be notified when the UE registers for SMS service in the 5GC (i.e. when the SMSF is registered in the UDM) by using the Nudm_EE_Subscribe service operation (SUPI, SMSF Registration Notification event) as defined in 3GPP TS 23.502 V16.3.0.

[0021] In this case, the HSS subscribes to the SMSF Registration Notification event in the UDM instead of the UE Reachability Notification because the UE will not be ready for SMS within the 5GC until the SMSF for that UE is registered in the UDM, even if the UE is reachable in the AMF.

[0022] At step 10, the UDM stores the SMSF Registration Notification flag in the 5GS-UDR.

[0023] At step 11, the UDM confirms this subscription to the HSS.

[0024] The messages shown in Figure 1 are the same as the corresponding messages described in 3GPP TS 23.632 V16.0.0, the disclosure of which is incorporated by reference herein in its entirety.

[0025] Figure 2 The UDM UECM (UE Context Management) resource is shown, which is a copy of Table 6.2.3.1-1 of 3GPP 29.503 V16.2.0, the disclosure of which is incorporated by reference herein in its entirety. Figure 6

[0026] Table 3 provides an overview of the resources and applicable HTTP (Hypertext Transfer Protocol) methods, which is a copy of Table 6.2.3.1-1 of 3GPP 29.503 V16.2.0.

[0027] Table 3: Overview of resources and methods

[0028] SUMMARY

[0029] ​The following presents a simplified summary of the application in order to provide a basic understanding of selected concepts described in this disclosure. This summary is not an extensive overview of the claimed subject matter, nor is it intended to identify key or critical elements of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter as it is presented for the sole purpose of summarizing some aspects of the claimed subject matter.

[0030] As mentioned above, in order to retrieve data related to a specific UE, the NWDAF should first determine which NF instances are serving the UE, as shown in Table 2:

[0031] - For AMF instances serving the UE, the NWDAF can contact the UDM through Nudm_UECM service (Table 2, line 3);

[0032] - For SMF instances serving the UE, the NWDAF can contact the UDM through Nudm_UECM service (Table 2, line 4).

[0033] In order to retrieve the SMS service nodes related to a specific UE, the HSS should check the UDM for the serving SMSF address:

[0034] - For SMSF address serving 3GPP access, the HSS can contact the UDM through Nudm_UECM_Get service;

[0035] - For SMSF address serving non-3GPP access, the HSS can contact the UDM through Nudm_UECM_Get service.

[0036] However, the UDM only provides the UECM service to obtain one service node at a time, which can cause some problems. For example, it is not possible to retrieve multiple registration data sets (e.g., serving NF instances) through a single GET request. It is inefficient to support different use cases based on multiple registration data sets, for example:

[0037] - To obtain the AMF and SMF instances serving the UE, the NWDAF needs to send at least 3 GET requests to the resource (e.g., Amf3GppAccessRegistration, AmfNon3GppAccessRegistration, SmfRegistrations);

[0038] - To obtain the SMSF instances serving the UE, the HSS needs to send at least 2 GET requests to the resource (e.g., Smsf3GppAccessRegistration, SmsfNon3GppAccessRegistration).

[0039] To overcome or alleviate at least one of the above problems or other problems, embodiments of the present disclosure propose improved registration data retrieval solutions.

[0040] In one embodiment, for a data management entity such as UDM, a new GET method is added to the resource {ueId} / registrations as a generic registration data set retrieval method to enable the possibility to retrieve multiple registration data sets using a single GET request.

[0041] In one embodiment, for a data repository entity such as UDR, the GET method for multiple context data set retrieval is updated to enable the possibility to retrieve multiple context data sets together with session context data (e.g. SMF PDU session context data) using a single GET request.

[0042] In a first aspect of the disclosure, a method performed by a network function service consumer entity is provided. The method comprises sending, to a data management entity, a request for retrieving at least two registration data sets related to a user equipment. The request comprises two or more corresponding registration data set names. The method further comprises receiving, from the data management entity, a response. The response comprises the at least two requested registration data sets related to the user equipment.

[0043] In one embodiment, the registration data set names can comprise at least one of: a registration data set name identifying session management function registration information; a registration data set name identifying access and mobility management function (AMF) third generation partnership project (3GPP) access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function (SMSF) 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

[0044] In one embodiment, when the request comprises the registration data set name identifying session management function registration information, the request can further comprise a single network slice selection assistance information and / or a data network name.

[0045] In one embodiment, the request can be a hypertext transfer protocol (HTTP) GET request and the response can be a HTTP GET response.

[0046] In one embodiment, the HTTP GET response can comprise a response code 200 OK and a response body containing the at least two requested registration data sets related to the user equipment; or a response code 404 Not Found.

[0047] In one embodiment, the request can further comprise a user equipment identity representing the user equipment.

[0048] In one embodiment, the user equipment identity can be a subscription permanent identifier (SUPI) or a general public subscription identifier (GPSI).

[0049] In one embodiment, the network function service consumer entity can be a network data analytics function (NWDAF) entity or a home subscriber server (HSS); and / or the data management entity can be a unified data management (UDM) entity.

[0050] In a second aspect of the disclosure, a method performed by a data management entity is provided. The method comprises receiving, from a network function service consumer entity, a request for retrieving at least two registration data sets related to a user equipment. The request comprises two or more corresponding registration data set names. The method further comprises sending, to the network function service consumer entity, a response. The response comprises the at least two requested registration data sets related to the user equipment.

[0051] In one embodiment, the method according to the second aspect of the disclosure can further comprise sending, to a data repository entity, a query request for retrieving at least two registration data sets related to the user equipment. The query request comprises two or more corresponding registration data set names. The method further comprises receiving, from the data repository entity, a query response. The query response comprises the at least two requested registration data sets related to the user equipment.

[0052] In one embodiment, the data repository entity can be a unified data repository (UDR) entity.

[0053] In a third aspect of the disclosure, a method performed by a data repository entity is provided. The method comprises receiving, from a data management entity, a query request for retrieving at least two registration data sets related to a user equipment. The query request comprises two or more corresponding registration data set names. The method further comprises sending, to the data management entity, a query response. The query response comprises the at least two requested registration data sets related to the user equipment.

[0054] In one embodiment, the registration data set names further comprise at least one of: a registration data set name identifying session management function registration information; a registration data set name identifying access and mobility management function (AMF) third generation partnership project (3GPP) access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function (SMSF) 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

[0055] In one embodiment, the query request can be a hypertext transfer protocol (HTTP) GET request and the query response can be a HTTP GET response.

[0056] In one embodiment, the data management entity can be a unified data management, UDM, entity and the data repository entity can be a unified data repository, UDR, entity.

[0057] In one embodiment, when the query request includes a registration data set name identifying session management function registration information, the query request further includes a single network slice selection assistance information and / or a data network name.

[0058] In a fourth aspect of the disclosure, a network function service consumer entity is provided. The network function service consumer entity comprises a processor; a memory coupled with the processor, the memory storing instructions executable by the processor, whereby the network function service consumer entity is operable to send, to a data management entity, a request to retrieve at least two registration data sets related to a user equipment. The request includes two or more corresponding registration data set names. The network function service consumer entity is further operable to receive, from the data management entity, a response. The response includes the at least two requested registration data sets related to the user equipment.

[0059] In a fifth aspect of the disclosure, a data management entity is provided. The data management entity comprises a processor; a memory coupled with the processor, the memory storing instructions executable by the processor, whereby the data management entity is operable to receive, from a network function service consumer entity, a request to retrieve at least two registration data sets related to a user equipment. The request includes two or more corresponding registration data set names. The network function service consumer entity is further operable to send, to the network function service consumer entity, a response. The response includes the at least two requested registration data sets related to the user equipment.

[0060] In a sixth aspect of the disclosure, a data repository entity is provided. The data repository entity comprises a processor; and a memory coupled to the processor, the memory storing instructions executable by the processor, whereby the data repository entity is operable to receive, from a data management entity, a query request to retrieve at least two registration data sets related to a user equipment. The query request includes two or more corresponding registration data set names. The data repository entity is operable to send, to the data management entity, a query response. The query response includes the at least two requested registration data sets related to the user equipment.

[0061] In a seventh aspect of the disclosure, a network function service consumer entity is provided. The network function service consumer entity comprises a sending module and a receiving module. The sending module can be configured to send, to a data management entity, a request to retrieve at least two registration data sets related to a user equipment. The request comprises two or more corresponding registration data set names. The receiving module can be configured to receive, from the data management entity, a response. The response comprises the at least two requested registration data sets related to the user equipment.

[0062] In an eighth aspect of the disclosure, a data management entity is provided. The data management entity comprises a receiving module and a sending module. The receiving module can be configured to receive, from a network function service consumer entity, a request to retrieve at least two registration data sets related to a user equipment. The request comprises two or more corresponding registration data set names. The sending module can be configured to send, to the network function service consumer entity, a response. The response comprises the at least two requested registration data sets related to the user equipment.

[0063] In a ninth aspect of the disclosure, a data repository entity is provided. The data repository entity comprises a receiving module and a sending module. The receiving module can be configured to receive, from a data management entity, a query request to retrieve at least one registration data set related to a user equipment. The query request comprises one or more registration data set names, the registration data set names comprising a registration data set name identifying session management function registration information. The sending module can be configured to send, to the data management entity, a query response.

[0064] In a tenth aspect of the disclosure, a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to the first aspect of the disclosure is provided.

[0065] In an eleventh aspect of the disclosure, a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to the second aspect of the disclosure is provided.

[0066] In a twelfth aspect of the disclosure, a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to the third aspect of the disclosure is provided.

[0067] In a thirteenth aspect of the disclosure, a computer-readable storage medium storing instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the first aspect of the disclosure is provided.

[0068] In a fourteenth aspect of the present disclosure, a computer-readable storage medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the method according to the second aspect of the present application is provided.

[0069] In a fifteenth aspect of the present disclosure, a computer-readable storage medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the method according to the third aspect of the present application is provided.

[0070] Embodiments herein provide a number of advantages, the following is a non-exhaustive list of examples of advantages. In some embodiments herein, for a data management entity such as UDM, a new GET method is introduced on the resource {ueId} / registrations as a generic registration data set retrieval method to enable the possibility of retrieving multiple registration data sets using a single GET request. Thus, the proposed method provided by the data management entity supports use cases that have been identified to benefit from retrieving multiple registration data sets using a single GET request. In some embodiments herein, for a data repository entity such as UDR, the GET method for multiple context data set retrieval is updated to enable the possibility of retrieving multiple context data sets together with session context data (e.g. SMF PDU session context data) using a single GET request. Thus, the proposed method provided by the data repository entity supports use cases that have been identified to benefit from retrieving multiple registration data sets including session context data using a single GET request. In some embodiments herein, from an operational perspective, unnecessary signaling traffic is avoided and network efficiency is improved, which means OPEX (operational expenditure) is reduced. Embodiments herein are not limited to the above-mentioned features and advantages. Additional features and advantages will be recognized by those skilled in the art upon reading the following detailed description in conjunction with the drawings. BRIEF DESCRIPTION OF DRAWINGS

[0071] The above and other aspects, features, and benefits of various embodiments of the present disclosure will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which like reference characters or numerals designate similar or equivalent elements throughout the drawings. The figures of the drawing are intended to be illustrative and not restrictive, wherein:

[0072] Figure 1a Interactions are shown when an SMS-GMSC retrieves routing information for an MT-SMS delivery from a HSS;

[0073] Figure 1b An advanced architecture in a next generation network is schematically illustrated;

[0074] Figure 1c A data collection architecture from any NF is schematically illustrated;

[0075] Figure 1d An open architecture for network data analytics is illustrated schematically;

[0076] Figure 1e An architecture for supporting SMS (Short Message Service) over NAS is illustrated schematically using reference points;

[0077] Figure 1f A non-roaming architecture for supporting SMS over NAS is illustrated schematically using reference points;

[0078] Figure 1g A roaming architecture for supporting SMS over NAS is illustrated schematically using service-based interfaces within the control plane;

[0079] Figure 1h A roaming architecture for supporting SMS over NAS is illustrated schematically using reference points;

[0080] Figure 1i A data storage architecture is illustrated schematically;

[0081] Figure 2 UDM UECM resources are illustrated;

[0082] Figure 3 UE registration in a 5GC with 3GPP access and non-3GPP access according to embodiments of the disclosure is illustrated;

[0083] Figure 4 UE initiated PDU session establishment for 3GPP access and non-3GPP access according to embodiments of the disclosure is illustrated;

[0084] Figure 5 A flow diagram of a method according to embodiments of the disclosure is illustrated;

[0085] Figure 6 A flow diagram of a method according to another embodiment of the disclosure is illustrated;

[0086] Figure 7 A flow diagram of a method according to another embodiment of the disclosure is illustrated;

[0087] Figure 8 A flow diagram of a method of retrieval of multiple UE registration data sets according to another embodiment of the disclosure is illustrated;

[0088] Figure 9 A flow diagram of some example use cases for retrieving multiple registration data sets in a single request according to another embodiment of the disclosure is illustrated;

[0089] Figure 10a flow diagram illustrating a NWDAF related use case for retrieving multiple registered data sets in a single request according to another embodiment of the disclosure is shown;

[0090] Figure 11 a flow diagram illustrating a HSS related use case for retrieving multiple registered data sets in a single request according to another embodiment of the disclosure is shown;

[0091] Figure 12 is a block diagram illustrating an apparatus suitable for implementing some embodiments of the disclosure;

[0092] Figure 13 is a block diagram illustrating a network function service consumer entity according to embodiments of the disclosure;

[0093] Figure 14 is a block diagram illustrating a data management entity according to embodiments of the disclosure; and

[0094] Figure 15 is a block diagram illustrating a data repository entity according to embodiments of the disclosure. DETAILED DESCRIPTION

[0095] Embodiments of the disclosure are discussed in detail below. It should be appreciated that these embodiments are discussed only for the purposes of enabling those skilled in the art to better understand and thus realize the present disclosure and are not intended to limit the scope of the disclosure. Reference throughout this specification to features, advantages or similar language does not imply that all of the features and advantages that can be realized with the present disclosure should be or are in

[0096] As used herein, the term “network” or “communication network” refers to a network that follows any suitable (wireless or wired) communication standard. For example, the wireless communication standards can include: New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA). A CDMA network can implement a radio technology such as Universal Terrestrial Radio Access (UTRA). UTRA includes WCDMA and other variants of CDMA. A TDMA network can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad hoc networks, Wireless Sensor Networks, etc. In the following description, the terms “network” and “system” can be used interchangeably. Also, the communication between two devices in a network can be performed according to any suitable communication protocol, including but not limited to a wireless communication protocol or a wired communication protocol defined by a standards organization such as the Third Generation Partnership Project (3GPP). For example, the wireless communication protocol can include a first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocol, and / or any other protocol currently known or developed in the future.

[0097] The term “entity” used herein refers to a network device or a network node or a network function in a communication network. For example, in a wireless communication network such as a 3GPP type cellular network, a core network device can provide a variety of services to customers interconnected through access network devices. Each access network device can be connected to the core network device through a wired or wireless connection.

[0098] The term “network function (NF)” refers to any suitable function that can be implemented in a network node (physical or virtual) of a communication network. For example, a 5G system (5GS) can comprise a plurality of NFs, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function), and NRF (Network Repository Function), (R)AN ((Radio) Access Network), SCP (Service Communication Proxy), NWDAF (Network Data Analytics Function), etc. In other embodiments, for example depending on the specific type of network, the network functions can comprise different types of NFs (HSS, SMS-GMSC, EPS-UDR, etc.).

[0099] The term “terminal device” refers to any end device that can access and receive services from a wireless communication network. By way of example but not limitation, a terminal device refers to a mobile terminal, user equipment (UE), or other suitable device. A UE can be, for example, a subscriber station (SS), a portable user station, a mobile station (MS), or an access terminal (AT). A terminal device can include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smartphone, a Voice over Internet Protocol (VoIP) phone, a wireless local loop phone, a tablet, a wearable terminal device, a Personal Digital Assistant (PDA), a portable computer, a desktop computer, a wearable device, a car-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), etc. In the following description, the terms “terminal device,” “terminal,” “user equipment,” and “UE” can be used interchangeably. As one example, a terminal device can represent a UE configured for communication in accordance with one or more communication standards promulgated by 3GPP, such as a LTE standard or a NR standard by 3GPP. As used herein, a “user equipment” or “UE” can not necessarily have a “user” in the sense of a human user that owns and / or operates the relevant device. In some embodiments, a terminal device can be configured to transmit and / or receive information without direct human interaction. For example, a terminal device can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from a communication network. Alternatively, a UE can represent a device that is intended for sale to, or operation by, a human user but that is not initially associated with a specific human user, such as when it is brand new or when it is a replacement for a device previously associated with a user.

[0100] As another example, in an Internet of Things (IOT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurements and sends results of such monitoring and / or measurements to another terminal device and / or a network equipment. In this case, the terminal device can be a machine-to-machine (M2M) device, which in a 3GPP context can be referred to as a machine-type communications (MTC) device. As one particular example, the terminal device can be a terminal device implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices (for example, power meters), industrial machinery, or home or personal appliances (for example, refrigerators, televisions), personal wearable devices (for example, watches), etc. In other cases, a terminal device can represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0101] Reference in the specification to “one embodiment”, “an embodiment”, “example embodiment” etc. indicates that the embodiment described can include a particular feature, structure, or characteristic, but every embodiment can not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0102] It should be understood that, although terms “first” and “second” etc. can be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element without departing from the scope of the example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0103] As used herein, the phrase “at least one of A and B” should be construed to mean “A alone, B alone, or A and B together.” The phrase “A and / or B” should be construed to mean “A alone, B alone, or A and B together.”

[0104] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "includes" and / or "including", when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0105] It should be noted that the terms used herein are only used for the convenience of description and differentiation of nodes, devices or networks, etc. With the development of technology, other terms with similar / same meanings can also be used.

[0106] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0107] It should be noted that some embodiments of the present disclosure are described mainly in relation to 5G or NR specifications used as non-limiting examples for certain example network configurations and system deployments. Thus, the description of the example embodiments given herein refers specifically to the terminology directly related thereto. Such terminology is used only in the context of the presented non-limiting examples and embodiments, and naturally does not limit the present disclosure in any way. On the contrary, as long as the example embodiments described herein are applicable, any other system configuration or radio technology can equally be used.

[0108] For simplicity, Figures 1b-1i The system architecture of FIG. 1 depicts only some example elements. In practice, a communication system can also include any additional elements as appropriate for supporting communication between terminal devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). The communication system can provide communication and various types of services to one or more terminal devices to facilitate the terminal devices' access to and / or use of the services provided by or via the communication system.

[0109] Figure 1b An advanced architecture in next generation networks such as 5G is schematically illustrated. Figure 1b The system architecture of FIG. 1 can include some example elements, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application), NEF (Network Exposure Function), UPF (User Plane Function), and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Proxy), etc.

[0110] According to exemplary embodiments, as Figure 1b illustrated, a UE can establish a signaling connection with an AMF through reference point N1. This signaling connection can enable NAS (non-access stratum) signaling exchange between the UE and the core network, which includes a signaling connection between the UE and the (R)AN and an N2 connection between the (R)AN and the AMF for this UE. The (R)AN can communicate with a UPF through reference point N3. The UE can establish a protocol data unit (PDU) session to a DN (data network, e.g., an operator network or the Internet) through the UPF through reference point N6.

[0111] As Figure 1b further illustrated, the exemplary system architecture also includes service-based interfaces exhibited by NFs such as NRF, NEF, AUSF, UDM, PCF, AMF, and SMF, e.g., Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, and Nsmf. In addition, Figure 1b Some reference points are also illustrated, e.g., N1, N2, N3, N4, N6, and N9, which can support interactions between NF services in NFs. For example, these reference points can be implemented through respective NF service-based interfaces and by specifying some NF service consumers and providers and their interactions to perform specific system procedures.

[0112] Figure 1c A data collection architecture from any NF is schematically illustrated. As Figure 1c illustrated, the 5G system architecture allows the NWDAF to collect data from any NF. The NWDAF can belong to the same PLMN (public land mobile network) in which the network function that is notifying the data is located.

[0113] The Nnf interface is defined for the NWDAF to request a subscription for data delivery for a specific context, to cancel a subscription for data delivery, and to request a specific report of data for a specific context.

[0114] Figure 1d A network data analytics exposure architecture is schematically illustrated. As Figure 1d illustrated, the 5G system architecture allows any NF to request network analytics information from the NWDAF. The NWDAF belongs to the same PLMN in which the network function that is consuming the analytics information is located. The Nnwdaf interface is defined for network functions to request a subscription for network analytics delivery for a specific context, to cancel a subscription for network analytics delivery, and to request a specific report of network analytics for a specific context.

[0115] Figure 1e An architecture to support SMS over NAS is schematically illustrated.Figure 1f A non-roaming architecture supporting SMS over NAS is schematically illustrated using reference points.

[0116] The SMS function (SMSF) can be connected to the SMS-GMSC / IWMSC (Interworking MSC) / SMS-Router over one of the standardized interfaces as shown in 3GPP TS 23.040. The UDM can be connected to the SMS-GMSC / IWMSC / SMS-Router over one of the standardized interfaces as shown in 3GPP TS 23.040. When a serving AMF is reassigned for a given UE, the source AMF includes the SMSF identifier as part of the UE context transferred to the target AMF. If the target AMF detects that no SMSF has been selected in the serving PLMN, e.g. in case of inter-PLMN mobility, the AMF performs SMSF selection.

[0117] Figure 1g A roaming architecture supporting SMS over NAS is schematically illustrated using service-based interfaces within the control plane. Figure 1h A roaming architecture supporting SMS over NAS is schematically illustrated using reference points.

[0118] Reference points for SMS over NAS

[0119] N1 : Reference point for SMS transport over NAS between a UE and an AMF.

[0120] The following reference points are implemented by service-based interfaces:

[0121] N8: Reference point for SMS subscription data retrieval between an AMF and a UDM.

[0122] N20: Reference point for SMS transport between an AMF and an SMS function.

[0123] N21 : Reference point for SMS function address registration management and SMS management subscription data retrieval between an SMS function and a UDM.

[0124] Figure 1i A data storage architecture is schematically illustrated. As shown in Figure 1i The 5G system architecture allows the UDM, PCF and NEF to store data in the UDR, including subscription data and policy data for the UDM and PCF, structured data for exposure and application data for the NEF, which includes packet flow descriptions (PFDs) for application detection, AF request information for multiple UEs. The UDR can be deployed in each PLMN, and it can provide different functions as follows:

[0125] - The UDR accessed by the NEF belongs to the same PLMN where the NEF is located.

[0126] - If the UDM supports a split architecture, the UDR accessed by the UDM belongs to the same PLMN where the UDM is located.

[0127] - The UDR accessed by the PCF belongs to the same PLMN where the PCF is located.

[0128] The UDR deployed in each PLMN can store application data for roaming users. There can be multiple UDRs deployed in the network, each of which can host different data sets or subsets (e.g. subscription data, subscription policy data, data for exposure, application data) and / or serve different NFs. The UDR serves a single NF and stores its data and therefore it is possible that the deployment can be integrated with that NF.

[0129] The internal structure of the UDR is shown for information purposes only.

[0130] The Nudr interface is defined for network functions (i.e. NF service consumers), such as the UDM, PCF and NEF, to access specific data sets stored and read, update (including add, modify), delete related data changes in the UDR, and subscribe to notifications of related data changes in the UDR.

[0131] Each NF service consumer accessing the UDR through the Nudr shall be able to only add, modify, update or delete data for which it is authorized to change. This authorization shall be performed by the UDR on a per data set and NF service consumer basis, and potentially on a per UE subscription granularity.

[0132] The following data in the UDR set exposed and stored through the Nudr to individual NF service consumers shall be standardized:

[0133] - subscription data,

[0134] - policy data,

[0135] - structured data for exposure,

[0136] - application data: packet flow description (PFD) for application detection and AF request information for multiple UEs.

[0137] The service-based Nudr interface defines the content and format / encoding of the information elements defined by 3GPP that are exposed by the data sets.

[0138] In addition, the NF service consumers can access from the UDR operator specific data sets and operator specific data for each data set.

[0139] The content and format / encoding of the operator specific data and operator specific data sets are not subject to standardization.

[0140] The organization of different data stored in the UDR is not standardized.

[0141] The various NFs shown in Figures 1b-1g may be responsible for functions such as session management, mobility management, authentication, security, etc. AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, SMSF, NWDAF, etc. can include, for example, functions as defined in 3GPP TS 23.501 V16.3.0 or other 3GPP specifications.

[0142] Figure 3 UE registration in 5GC with 3GPP access and non-3GPP access is shown according to embodiments of the disclosure. Figure 3 The scenario is described where the UE is registered in the 5GC network from both 3GPP access and non-3GPP access, and the 3GPP access and non-3GPP access belong to different PLMNs (Public Land Mobile Networks). Thus the access networks (ANs) are different, in Figure 3 are denoted accordingly as AN(3GPP) and AN(Non-3GPP). The AMFs are also different, in Figure 3 are denoted accordingly as AMF(3GPP) and AMF(Non-3GPP). The SMSFs are also different, in Figure 3 are denoted accordingly as SMSF(3GPP) and SMSF(Non-3GPP).

[0143] In step 302, the UE sends a registration request to the AMF(3GPP) from the 3GPP access network through the AN(3GPP), and indicates its capability of supporting SMS (non-access stratum) over NAS by setting "SMS supported" to true.

[0144] In step 304, the AMF initiates the UE registration procedure, which can optionally perform a basic authentication procedure, which is not shown in Figure 3 for simplicity reasons. The AMF registers to the UDM through Nudm_UECM_Registration for 3GPP access service operation.

[0145] In step 306, the UDM creates the AMF registration context into the UDR through Nudr-Dr Create service operation, thus the AMF serving node for the UE 3GPP access is stored as context data in the UDR.

[0146] At step 308, the UDM sends the Nudm_UECM_Registration response to the AMF for the 3GPP access registration result.

[0147] At step 310, when "SMS is supported" is indicated in step 302, the AMF (3GPP) activates the SMS service through the Nsmsf_SMService_Activate service operation for 3GPP access towards the SMSF (3GPP).

[0148] At step 312, the SMSF (3GPP) initiates the SMSF (3GPP) registration into the UDM through the Nudm_UECM_Registration service operation for 3GPP access.

[0149] At step 314, the UDM creates the SMSF (3GPP) registration context into the UDR through the Nudr-Dr create service operation, thus the SMSF service node for UE 3GPP access is stored in the UDR as SMSF context data.

[0150] At step 316, the UDM sends the Nudm_UECM_Registration response to the SMSF for the 3GPP access registration result.

[0151] At step 318, the SMSF sends the Nsmsf_SMService_Activate response to the AMF for the 3GPP access SMS service activation result.

[0152] At step 320, the AMF (3GPP) sends the registration accept message to the UE through the 3GPP access network and indicates "SMS is allowed" as the SMS service registration result.

[0153] At step 322, the UE sends the registration request through the AN (non-3GPP) from the non-3GPP access network to the AMF (non-3GPP) and indicates its capability of supporting SMS over NAS by setting "SMS is supported" to true.

[0154] At step 324, the AMF (non-3GPP) initiates the UE registration procedure, which can optionally perform the basic authentication procedure, which is not shown in Figure 3 for simplicity reasons. The AMF registers into the UDM through the Nudm_UECM_Registration service operation for non-3GPP access.

[0155] At step 326, the UDM creates the AMF (non-3GPP) registration context into the UDR by the Nudr-Dr create service operation, thus the AMF serving node for UE non-3GPP access is stored in the UDR as context data.

[0156] At step 328, the UDM sends the Nudm_UECM_Registration response for non-3GPP access registration result to the AMF.

[0157] At step 330, when “SMS is supported” is indicated in step 322, the AMF (non-3GPP) activates the SMS service for non-3GPP access towards the SMSF (non-3GPP) by the Nsmsf_SMService_Activate service operation.

[0158] At step 332, the SMSF (non-3GPP) initiates the SMSF (non-3GPP) registration into the UDM for non-3GPP access by the Nudm_UECM_Registration.

[0159] At step 334, the UDM creates the SMSF registration context into the UDR by the Nudr-Dr create service operation, thus the SMSF serving node for UE non-3GPP access is stored in the UDR as SMSF context data.

[0160] At step 336, the UDM sends the Nudm_UECM_Registration response for non-3GPP access registration result to the SMSF.

[0161] At step 338, the SMSF (Non-3GPP) sends the Nsmsf_SMService_Activate response for non-3GPP access SMS service activation result to the AMF (non-3GPP).

[0162] At step 340, the AMF (non-3GPP) sends the registration accept message to the UE over the non-3GPP access network and indicates “SMS is allowed” as the SMS registration result.

[0163] Figure 3 The illustrated messages are the same as or similar to the corresponding messages described in various 3GPP specifications such as 3GPP TS 23.501 V16.3.0, 3GPP TS 23.502 V16.3.0, etc.

[0164] Figure 4 A UE-initiated PDU session establishment for both 3GPP access and non-3GPP access is shown in accordance with an embodiment of the disclosure. Figure 4Scenarios are described where a UE initiates PDU session establishment from 3GPP access and non-3GPP access for different data networks, and the 3GPP access and non-3GPP access belong to different PLMNs. The access networks (AN) are different, denoted as AN(3GPP) and AN(Non-3GPP) accordingly in Figure 4 The access and mobility management functions (AMF) are also different, denoted as AMF(3GPP) and AMF(non-3GPP) accordingly in Figure 4 The session management functions (SMF) are also different, denoted as SMF(3GPP) and SMF(non-3GPP) accordingly in Figure 4 The data networks accessed in the 3GPP access and non-3GPP access can be different, denoted as data network name 1 (DNN1) and data network name 2 (DNN2) in step 402 and step 418 respectively in the PDU session establishment request.

[0165] In step 402, the UE initiates PDU session establishment in 3GPP access through 3GPP access network DNN1 and sends a PDU session establishment request to AMF(3GPP).

[0166] In step 404, AMF(3GPP) sends a request to SMF(3GPP) through Nsmf_PDUSession_CreateSMContext service operation for creating a new PDU session for 3GPP access and to DNN1.

[0167] In step 406, SMF(3GPP) performs PDU session establishment procedure, which includes contacting UPF for N3 / N4 session, which is not shown for simplicity reasons.

[0168] In step 408, SMF(3GPP) sends Nsmf_PDUSession_CreateSMContext response to AMF(3GPP) for the result of PDU session establishment for 3GPP access and to DNN1.

[0169] In step 410, AMF(3GPP) sends a PDU session establishment accept message to the UE through 3GPP access network for the PDU session accessing DNNl.

[0170] In step 412, the SMF registers the created PDU session to UDM, which includes the following parameters: UE identity SUPI (Subscription Permanent Identifier), DNN1, S-NSSAI, PDU session identity, SMF identity, etc.

[0171] At step 414, the UDM creates the SMF PDU Session Registration Context into the UDR by the Nudr-Dr Create Service operation, so the UE 3GPP PDU Session and the SMF service node to DNN1 are stored in the UDR as SMF PDU Session Context data.

[0172] At step 416, the UDM sends the Nudm_UECM_Registration response to the SMF (3GPP) for PDU Session 1 from 3GPP access and to DNN1.

[0173] At step 418, the UE initiates PDU Session establishment in non-3GPP access through non-3GPP access network DNN2 and sends the PDU Session Establishment Request to the AMF (non-3GPP).

[0174] At step 420, the AMF (non-3GPP) sends a request to the SMF (non-3GPP) through the Nsmf_PDUSession_CreateSMContext service operation for creating a new PDU Session for non-3GPP access and to DNN2.

[0175] At step 422, the SMF (non-3GPP) performs the PDU Session establishment procedure, which includes contacting the UPF for N3 / N4 session, the N3 / N4 session is not shown for simplicity reasons.

[0176] At step 424, the SMF (non-3GPP) sends the Nsmf_PDUSession_CreateSMContext response to the AMF (non-3GPP) for the result of the PDU Session establishment for non-3GPP access and to DNN2.

[0177] At step 426, the AMF (non-3GPP) sends the PDU Session Establishment Accept message to the UE through the non-3GPP access network for the PDU Session accessing DNN2.

[0178] At step 428, the SMF (non-3GPP) registers the created PDU Session into the UDM, which includes the following parameters: UE identity SUPI, DNN2, S-NSSAI, PDU Session identity, SMF identity, etc.

[0179] At step 430, the UDM creates the SMF PDU Session Registration Context into the UDR by the Nudr-Dr Create Service operation, so the UE non-3GPP PDU Session and the SMF service node to DNN2 are stored in the UDR as SMF PDU Session Context data.

[0180] At step 432, the UDM sends an Nudm_UECM_Registration response to the SMF (non-3GPP) for PDU Session 2 from 3GPP access and to DNN2.

[0181] Figure 4 The illustrated messages are the same as or similar to corresponding messages described in various 3GPP specifications such as 3GPP TS 23.501 V16.3.0, 3GPP TS 23.502 V16.3.0, etc.

[0182] Figure 5 A flow diagram of a method according to embodiments of the disclosure is shown, which can be performed by an apparatus implemented in / as a network function service consumer entity or communicatively coupled to a network function service consumer entity. As such, the apparatus can provide means for completing the various portions of method 500 as well as means for completing other processes in conjunction with other components. The network function service consumer entity can be a network function entity capable of retrieving at least one registration data set related to a user equipment from a data management entity. For example, the network function service consumer entity can be a NWDAF or a HSS.

[0183] At block 502, the network function service consumer entity can send a request to a data management entity for retrieving at least two registration data sets related to a user equipment. The request includes two or more corresponding registration data set names. For example, the network function service consumer entity can send a request to a data management entity for retrieving at least one registration data set related to a user equipment. The registration data set can be any suitable registration data set, such as a registration context data set. The data management entity can support various functions, such as service NF registration management for UEs (e.g., storing service AMF for UEs, storing service SMF for PDU sessions of UEs, storing service SMSF for UEs), MT-SMS delivery support, SMS subscription management, etc. The registration data set related to the user equipment can be stored in the network function service consumer entity, in which case the data management entity can need an internal user data storage. The at least one registration data set related to the user equipment can be stored in a data repository entity such as a UDR, and the data management entity can use subscription data that can be stored in a data repository entity such as a UDR, in which case the data management entity implements application logic without needing an internal user data storage, and then several different data management entities can serve the same user in different transactions. In one embodiment, the data management entity can be a UDM of a 5GC.

[0184] In one embodiment, the registration dataset name can include at least one of: a registration dataset name identifying session management function registration information; a registration dataset name identifying AMF 3GPP access registration information; a registration dataset name identifying AMF non-3GPP access registration information; a registration dataset name identifying SMSF 3GPP access registration information; and a registration dataset name identifying SMSF non-3GPP access registration information. In other embodiments, the registration dataset name can include any other suitable registration dataset name identifying other registration information.

[0185] In one embodiment, when the request includes two or more registration dataset names, two or more corresponding registration datasets related to the user equipment are requested to be retrieved.

[0186] In one embodiment, when the request does not include any registration dataset name, all registration datasets related to the user equipment are requested to be retrieved.

[0187] In one embodiment, when the request includes one registration dataset name, the one registration dataset name identifies session management function registration information and session management function (SMF) protocol data unit (PDU) session registration information related to the user equipment is requested to be retrieved.

[0188] In one embodiment, when the request includes a registration dataset name identifying session management function registration information, the request further includes a single network slice selection assistance information and / or a data network name. For example, the single network slice selection assistance information can be a SNSSAI as described in 3GPP TS 23.501 V16.3.0.

[0189] In one embodiment, the request further includes a user equipment identity representing the user equipment. For example, the user equipment identity (ueid) can represent a subscription identifier, such as a SUPI or GPSI (Generic Public Subscription Identifier) (see clause 5.9.2 of 3GPP TS 23.501 V16.3.0). A SUPI (i.e. imsi (International Mobile Subscriber Identity) or nai (Network Access Identifier)) can be used with HTTP PUT and PATCH methods; a SUPI (i.e. imsi or nai) or GPSI (i.e. msisdn (Mobile Subscriber Integrated Services Digital Network Number) or extid) can be used with GET methods. For example, the pattern can be “(imsi-[0-9]{5,15} | nai-.+ | msisdn-[0-9]{5,15} | extid-[^@]+@[^@]+ |.+)”. The term “extid” is the same as “extid” described in 3GPP 29.503 16.2.0.

[0190] At block 504, the network function service consumer entity can receive a response from the data management entity. In one embodiment, the response includes at least two requested registration data sets related to the user equipment. For example, on success, a response containing the requested at least one registration data set can be returned. On failure, an error information can be returned in the response.

[0191] In one embodiment, the request can be an HTTP GET request and the response can be an HTTP GET response. In other embodiments, the request can be other types of requests and the response can be other types of responses.

[0192] In one embodiment, the HTTP GET response can include a response code 200 OK and a response body containing the requested at least one (e.g., at least two requested) registration data set related to the user equipment or a response code 404 Not Found. For example, on failure, an appropriate HTTP status code indicating an error can be returned and appropriate additional error information can be returned in the GET response body.

[0193] Figure 6 A flowchart of a method according to another embodiment of the disclosure is shown, which can be performed by an apparatus implemented in / as or communicatively coupled to a data management entity. As such, the apparatus can provide means for accomplishing various portions of the method 600 as well as means for accomplishing other processes in conjunction with other components. The data management entity can be a network function entity capable of supporting data management functions. For example, the data management entity can be a UDM of a 5GS. For portions already described in the above embodiments, detailed description thereof is omitted here for brevity.

[0194] At block 602, the data management entity can receive a request from a network function service consumer entity for retrieving at least two registration data sets related to a user equipment. The request includes two or more corresponding registration data set names. For example, the data management entity can receive a request from a network function service consumer entity for retrieving at least one registration data set related to a user equipment. For example, the network function service consumer entity can send the request at block 502 of the above embodiment, and then the data management entity can receive the request. Figure 5

[0195] ​In one embodiment, the registration data set name can include at least one of: a registration data set name identifying session management function registration information; a registration data set name identifying AMF 3GPP access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying SMSF 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

[0196] In one embodiment, when the request includes two or more registration data set names, two or more corresponding registration data sets related to the user equipment are requested to be retrieved. For example, the data management entity can query from a data repository entity, such as a UDR, two or more corresponding registration data sets related to the user equipment.

[0197] In one embodiment, when the request does not include any registration data set name, all registration data sets related to the user equipment are requested to be retrieved. For example, the data management entity can query from a data repository entity, such as a UDR, all registration data sets related to the user equipment.

[0198] In one embodiment, when the request includes one registration data set name, the one registration data set name identifies session management function registration information, and session management function protocol data unit session registration information related to the user equipment is requested to be retrieved. For example, the data management entity can query from a data repository entity, such as a UDR, session management function protocol data unit session registration information related to the user equipment.

[0199] In one embodiment, when the request includes a registration data set name identifying session management function registration information, the request further includes a single network slice selection assistance information and / or a data network name. For example, the single network slice selection assistance information can be a SNSSAI described in 3GPP TS 23.501 V16.3.0. For example, in order to determine the SMF serving a PDU session, the NWDAF can provide the DNN and S-NSSAI of that PDU session; otherwise, the NWDAF can obtain a list of possible SMFs (e.g., one SMF per PDU session).

[0200] In one embodiment, the request further includes a user equipment identity representing the user equipment. The user equipment identity can be a SUPI or a GPSI.

[0201] At block 604 (optionally), the data management entity can send a request to the data repository entity for retrieving at least two registration data sets related to the user equipment. The request includes two or more corresponding registration data set names. For example, the data management entity can send a query request to the data repository entity for retrieving at least one registration data set related to the user equipment. The data repository entity can store various registration data sets related to the user equipment. In one embodiment, the data repository entity can be a UDR of the 5GS. The registration data set can be a registration context data set.

[0202] At block 606 (optionally), the data management entity can receive a query response from the data repository entity. For example, on success, a query response containing the requested at least one registration data set can be returned. On failure, an error message can be returned in the query response. In one embodiment, the response includes at least two requested registration data sets related to the user equipment.

[0203] In one embodiment, when the requested at least one registration data set is stored in the data management entity, the data management entity can query the requested at least one registration data by itself and blocks 604 and 606 can be omitted.

[0204] At block 608, the data management entity can send a response to the network function service consumer entity. In one embodiment, the response includes at least two requested registration data sets related to the user equipment. For example, on success, a response containing the requested at least one registration data set can be returned. On failure, an error message can be returned in the response.

[0205] In one embodiment, the request can be a HTTP GET request and the response can be a HTTP GET response. In other embodiments, the request can be other types of requests and the response can be other types of responses.

[0206] In one embodiment, the HTTP GET response can include a response code 200 OK and a response body containing the requested at least one (e.g., at least two requested) registration data set related to the user equipment or a response code 404 Not Found. For example, on failure, an appropriate HTTP status code indicating the error can be returned and appropriate additional error information can be returned in the GET response body.

[0207] Figure 7A flow diagram illustrating a method according to another embodiment of the disclosure is shown, which can be performed by an apparatus implemented in / as a data repository entity or communicatively coupled to a data repository entity. As such, the apparatus can provide means for completing portions of the method 700 as well as means for completing other processes in conjunction with other components. The data repository entity can be a network function entity capable of supporting data repository functions. For example, the data repository entity can be a UDR of a 5GS. For portions already described in the above embodiments, detailed descriptions thereof are omitted here for brevity.

[0208] At block 702, the data repository entity can receive, from the data management entity, a query request for retrieving at least two registration data sets related to the user equipment, wherein the query request comprises two or more corresponding registration data set names. For example, the data repository entity can receive, from the data management entity, a query request for retrieving at least one registration data set related to the user equipment. The registration data set can be a registration context data set. The query request comprises one or more registration data set names, the registration data set names comprising a registration data set name identifying session management function registration information. For example, the data management entity can send the query request at block 604 of FIG. 6, and then the data repository entity can receive the query request. Figure 6

[0209] At block 704, the data repository entity can send, to the data management entity, a query response. For example, the query response containing the requested at least one registration data set can be returned upon success. Upon failure, an error information can be returned in the query response. In one embodiment, the query response comprises at least two requested registration data sets related to the user equipment.

[0210] In one embodiment, the registration data set names comprise at least one of: a registration data set name identifying AMF 3GPP access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying SMSF 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

[0211] In one embodiment, the query request is an HTTP GET request and the query response is an HTTP GET response.

[0212] In one embodiment, when the query request comprises a registration data set name identifying session management function registration information, the query request further comprises a single network slice selection assistance information and / or a data network name.

[0213] Figure 8 ​A flow diagram illustrating a method of retrieving multiple UE registration data sets is shown, according to another embodiment of the disclosure. Figure 8 A scenario is depicted where a NF service consumer (e.g. NWDAF, HSS) sends a request to the UDM to receive multiple UE registration data sets. In this example scenario, a single request is used to retrieve the 3GPP AMF registration data for a UE and the non-3GPP AMF registration data for a UE. Note that any other registration data set can be retrieved using a single request. The request contains the UE's registrations ({ueId} / registrations) and a query parameter identifying the requested registration data sets (in this example:?registration-dataset-names=AMF_3GPP,AMF_NON_3GPP).

[0214] At step 802, the NF service consumer (e.g. NWDAF, HSS) sends a GET request to the resource representing the UE's registrations. The query parameter indicates the requested UE registration data set.

[0215] At step 804, the UDM responds with a "200 OK" with a message body containing the requested UE registration data set. On failure, an appropriate HTTP status code indicating the error shall be returned and appropriate additional error information can be returned in the GET response body.

[0216] In one embodiment, the above Table 3 can be added with the following registration resources:

[0217]

[0218] In one embodiment, the following can be added in 3GPP 29.503 16.2.0:

[0219] 6.2.3.X Resource: registrations

[0220] 6.2.3.X.1 Description

[0221] This resource represents the UE's registration data.

[0222] 6.2.3.X.2 Resource definition

[0223] Resource URI: {apiRoot} / nudm-uecm / v1 / {ueId} / registrations

[0224] This resource shall support the resource URI variables defined in Table 6.2.3.X.2-1.

[0225] Table 6.2.3.X.2-1: Resource URI variables for this resource

[0226]

[0227] 6.2.3.X.3 Resource Standard Methods

[0228] 6.2.3.X.3.1 GET

[0229] This method shall support the URI query parameters specified in table 6.2.3.X.3.1-1.

[0230] NOTE: Retrieval of these registration data sets can also be achieved by sending separate GET requests to the corresponding sub-resources under the {ueId} / registraions resource. When the NF service consumer needs to retrieve multiple registration data sets, it is recommended to use a single GET request with query parameters instead of issuing multiple GET requests.

[0231] Table 6.2.3.X.3.1-1: URI query parameters supported by the GET method of this resource

[0232]

[0233] This method shall support the request data structures specified in table 6.2.3.X.3.1-2 and the response data structures and response codes specified in table 6.2.3.X.3.1-3.

[0234] Table 6.2.3.X.3.1-2: Data structures supported by the body of the GET request on this resource

[0235] Data Type P Cardinality Description n / a

[0236] Table 6.2.3.X.3.1-3: Data structures supported by the body of the GET response on this resource

[0237]

[0238] The suggested data model is as follows:

[0239] 6.2.6.2.X Type: RegistrationDataSets

[0240] Table 6.2.6.2.X-1: Definition of the type RegistrationDataSets

[0241]

[0242] 6.2.6.3.X Enum: RegistrationDataSetName

[0243] Table 6.1.6.3.3-1 : Enumerated RegistrationDataSetName

[0244] Enumerated Values Description "AMF_3GPP" AMF 3GPP access registration "AMF_NON_3GPP" AMF non-3GPP access registration "SMF_PDU_SESSIONS" SMF PDU session registration "SMSF_3GPP" SMSF 3GPP access registration "SMSF_NON_3GPP" SMSF non-3GPP access registration

[0245] In one embodiment, the UDR method can be updated to support retrieval of SMF PDU session context in a request for multiple context data sets. The following are updates to the data model that can be added in 3GPP TS 29.505 16.1.0:

[0246] 5.4.2.22 Type: ContextDataSets

[0247] Table 5.4.2.22-1 : ContextDataSets

[0248]

[0249] 5.4.3.6 Enumerated: ContextDataSetName

[0250] Table 5.4.3.6-1 : Enumerated ContextDataSetName

[0251] Enumerated Values Description "AMF_3GPP" AMF 3GPP access registration "AMF_NON_3GPP" SMF non-3GPP access registration "SDM SUBSCRIPTIONS" SDM subscription "EE_SUBSCRIPTIONS" EE subscription "SMSF_3GPP" SMSF 3GPP access registration "SMSF_NON3GPP" SMSF non-3GPP access registration "SUBS_TO_NOTIFY" UDR subscription "SMF_PDU_SESSIONS" SMF registration for PDU sessions

[0252] Figure 9 A flow diagram showing some example use cases for retrieving multiple registration data sets in a single request according to another embodiment of the disclosure is shown.

[0253] Example 0: Retrieve all UE registration data sets from UDM, UDM queries all UE registration related data sets from UDR. Example 1: Retrieve all AMF registration data sets from UDM, UDM queries AMF registration related data sets from UDR. Example 2: Retrieve all SMSF registration data sets from UDM, UDM queries SMSF registration related data sets from UDR. Example 3: Retrieve all SMF PDU session registration data sets from UDM, UDM queries SMF PDU session registration related data sets from UDR. Example 4: Retrieve all AMF registration and SMF PDU session registration data sets from UDM, UDM queries SMF PDU session registration related data sets from UDR.

[0254] At step 902, the NF service consumer retrieves all UE registration data sets from UDM by GET method on resource.. / {ueId} / registrations without specifying the required registration data sets in query parameters.

[0255] At step 904, the UDM queries multiple context datasets from the UDR in one request and sets the requested context-dataset-names = AMF_3GPP, AMF_NON_3GPP, SMF_PDU_SESSIONS, SMSF_3GPP, SMSF_NON_3GPP.

[0256] At step 906, the UDM returns the results from the UDR to the NF service consumer, which can include all the required registration datasets in RegistrationDataSets: Amf3GppAccessRegistration (identified by AMF_3GPP in the request), AmfNon3GppAccessRegistration (identified by AMF_NON_3GPP in the request), SmfRegistrationInfo (identified by SMF_PDU_SESSIONS in the request, list of PDU sessions), SmsfRegistration for 3GPP access (identified by SMSF_3GPP in the request), and SmsfRegistration for non-3GPP access (identified by SMSF_NON_3GPP in the request).

[0257] At step 908, the NF service consumer gets all the UE AMF registration datasets from the UDM by a GET method on resource.. / {ueId} / registrations?registration-dataset-names=AMF_3GPP,AMF_NON_3GPP, specifying the required registration datasets in the query parameters.

[0258] At step 910, the UDM queries multiple context datasets from the UDR in one request and sets the requested context-dataset-names = AMF_3GPP, AMF_NON_3GPP.

[0259] At step 912, the UDM returns the results from the UDR to the NF service consumer, which can include all the required registration datasets in RegistrationDataSets: Amf3GppAccessRegistration (identified by AMF_3GPP in the request), AmfNon3GppAccessRegistration (identified by AMF_NON_3GPP in the request).

[0260] At step 914, the NF service consumer gets all UE SMSF registration data sets from the UDM by a GET method on resource.. / {ueId} / registrations?registration-dataset-names=SMSF_3GPP,SMSF_NON_3GPP, specifying the required registration data sets in the query parameter.

[0261] At step 916, the UDM queries multiple context data sets from the UDR in one request and sets the requested context-dataset-names = SMSF_3GPP,SMSF_NON_3GPP.

[0262] At step 918, the UDM returns the result from the UDR to the NF service consumer, which can include all required registration data sets in RegistrationDataSets: SmfRegistration for 3GPP access (identified by SMSF_3GPP in the request), SmfRegistration for non-3GPP access (identified by SMSF_NON_3GPP in the request).

[0263] At step 920, the NF service consumer gets all SMF PDU session registration data sets from the UDM by a GET method on resource resource.. / {ueId} / registrations?registration-dataset-names=SMF_PDU_SESSIONS, specifying the required registration data sets in the query parameter.

[0264] At step 922, the UDM queries multiple context data sets from the UDR in one request and sets the requested context-dataset-names = SMF_PDU_SESSIONS.

[0265] At step 924, the UDM returns the result from the UDR to the NF service consumer, which can include all required registration data sets in RegistrationDataSets: SmfRegistrationInfo (identified by SMF_PDU_SESSIONS in the request, list of PDU sessions).

[0266] At step 926, the NF service consumer gets all the UE AMF registrations and SMF PDU session registrations data sets from the UDM by a GET method on the resource.. / {ueId} / registrations?registration-dataset-names=AMF_3GPP, AMF_NON_3GPP, SMF_PDU_SEESIONS, specifying the required registration data sets in the query parameters.

[0267] At step 928, the UDM queries multiple context data sets from the UDR in one request and sets the requested context-dataset-names = AMF_3GPP, AMF_NON_3GPP, SMF_PDU_SEESIONS.

[0268] At step 930, the UDM returns the results from the UDR to the NF service consumer, which can include all the required registration data sets in RegistrationDataSets: Amf3GppAccessRegistration (identified by AMF_3GPP in the request), AmfNon3GppAccessRegistration (identified by AMF_NON_3GPP in the request), SmfRegistrationInfo (identified by SMF_PDU_SESSIONS in the request, list of PDU sessions).

[0269] As Figure 9 shown, some messages are similar to the corresponding messages described in various 3GPP specifications (e.g., 3GPP TS 23.501 V16.3.0, 3GPP TS 23.502 V16.3.0, etc.).

[0270] Figure 10 A flow diagram illustrating a NWDAF-related use case for getting multiple registration data sets in a single request according to another embodiment of the disclosure is shown. In this embodiment, the NF service consumer is a NWDAF.

[0271] At step 1002, the NWDAF service consumer subscribes to data analytics reports for a UE from the NWDAF.

[0272] The NWDAF first needs to get the current serving nodes for the UE. Therefore, the proposed method used by the NWDAF is to retrieve in a single request the serving AMF and SMF instances from the UDM. In step 1004, the NWDAF gets all the UE AMF registrations and SMF PDU session registrations datasets from the UDM by a GET method on the resource.. / {ueId} / registrations?registration-dataset-names=AMF_3GPP,AMF_NON_3GPP,SMF_PDU_SEESIONS, specifying in the query parameters the required registration datasets.

[0273] In step 1006, the UDM queries multiple context datasets from the UDR in one request and sets the requested context-dataset-names=AMF_3GPP,AMF_NON_3GPP,SMF_PDU_SEESIONS.

[0274] In step 1008, the UDM returns the results from the UDR to the NF service consumer, which can include all the registration datasets in RegistrationDataSets: Amf3GppAccessRegistration (identified by AMF_3GPP in the request), AmfNon3GppAccessRegistration (identified by AMF_NON_3GPP in the request), SmfRegistrationInfo (identified by SMF_PDU_SESSIONS in the request, list of PDU sessions).

[0275] In step 1010, the NWDAF subscribes to UE access and mobility related events from the AMF (3GPP access), obtaining the information of the AMF (3GPP access) in step 1008.

[0276] In step 1012, the NWDAF subscribes to UE access and mobility related events from the AMF (non-3GPP access), obtaining the information of the AMF (non-3GPP access) in step 1008.

[0277] In step 1014, the NWDAF subscribes to UE PDU session related events from the SMF (3GPP access), obtaining the information of the SMF (3GPP access) in step 1008.

[0278] In step 1016, the NWDAF subscribes to UE PDU session related events from the SMF (non-3GPP access), obtaining the information of the SMF (non-3GPP access) in step 1008.

[0279] At step 1018, the NWDAF responds to the NWDAF service consumer with the result of the data analytics report subscription.

[0280] In Figure 10 Some of the messages shown in FIG. 11 are similar to the corresponding messages described in various 3GPP specifications such as 3GPP TS 23.501 V16.3.0, 3GPP TS 23.502 V16.3.0, etc.

[0281] Figure 11 A flow diagram illustrating an HSS related use case for retrieving multiple registration data sets in a single request according to another embodiment of the disclosure is shown. In this embodiment, the NF service consumer is an HSS.

[0282] At step 1102, the HSS receives a request for routing information from the SMS-GMSC via MAP or S6c.

[0283] At step 1104, the HSS queries the EPS-UDR via Ud to read the registered MME / MSC, registered SGSN, UE not reachable flags for MME / MSC, SGSN, 3GppSMSF and Non3GppSMSF and SMSF registration notification flag.

[0284] At step 1106, if the UE not reachable flags for 3GppSMSF, Non3GppSMSF and SMSF registration notification flag are not set and unless it is known that the user is not registered in 5GC, the HSS retrieves the registered SMSF address (if any) from the UDM. The HSS uses the suggested method to get all UE SMSF registration data sets from the UDM by using the GET method on resource.. / {ueId} / registrations?registration-dataset-names=SMSF_3GPP,SMSF_NON_3GPP, specifying the required registration data sets in the query parameters.

[0285] At steps 1108-1110, the UDM retrieves the requested information from the 5GS-UDR. The UDM retrieves multiple context data sets in one request and sets the requested context-dataset-names=SMSF_3GPP,SMSF_NON_3GPP.

[0286] At step 1112, the UDM forwards the retrieved address(es) to the HSS, if any. The UDM returns the results from the UDR to the NF service consumer, which can include all required registration data sets in RegistrationDataSets: the SmsgfRegistration for 3GPP access (identified by SMSF_3GPP in the request), the SmsgfRegistration for non-3GPP access (identified by SMSF_NON_3GPP in the request).

[0287] At step 1114, the HSS returns the relevant MT-SMS destination node address(es) registered in the HSS and / or UDM to the SMS-GMSC, and the procedure ends. Otherwise, if there is no MT-SMS destination node address registered in the HSS and UDM, a negative response (no subscriber SM present) is sent to the SMS-GMSC, and the procedure continues with steps 1116 to 1122.

[0288] At step 1116, the HSS includes the SMSC address in the Message Waiting Data (MWD) stored in the EPS-UDR and notifies the SMSC as defined in 3GPP TS 23.040. The relevant UE not reachable flag and SMSF registration notification flag are set in the EPS-UDR.

[0289] At step 1118, the HSS subscribes in the UDM to be notified when the UE registers for SMS service in the 5GC (i.e., when the SMSF is registered in the UDM) by using the Nudm_EE_Subscribe service operation (SUPI, SMSF registration notification event) as defined in 3GPP TS 23.502. In this case, the HSS subscribes to the SMSF registration notification event in the UDM instead of the UE reachability notification because the UE will not be ready to receive SMS within the 5GC until the SMSF for the UE is registered in the UDM, even if the UE is reachable in the AMF.

[0290] At step 1120, the UDM stores the SMSF registration notification flag in the 5G-UDR.

[0291] At step 1122, the UDM confirms the subscription to the HSS.

[0292] As Figure 11 indicated, some messages are similar to the corresponding messages described in various 3GPP specifications such as 3GPP TS 23.501 V16.3.0, 3GPP TS 23.502 V16.3.0, 3GPP TS 23.632 V16.0.0, etc.

[0293] In one embodiment, since 5G is based on service-based architecture (SBA) and the interface used between network functions (NFs) is based on service-based interface (SBI), this interface can be modeled as a public API (application programming interface) and defined in a yaml file, the Nudm-UECM public API incremental update can be as follows:

[0294]

[0295] In one embodiment, the Nudr-Dr public API incremental update, especially the update on the data model, can be as follows:

[0296]

[0297]

[0298] Figure 12 is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure. For example, any of the network function service consumer entities, data management entities, and data repository entities described above can be implemented as or by the apparatus 1200.

[0299] The apparatus 1200 includes at least one processor 1221, such as a DP, and at least one memory 1222 coupled to the processor 1221. The apparatus 1220 can further include a transmitter TX and a receiver RX 1223 coupled to the processor 1221. The memory 1222 stores a program 1224. The program 1224 can include instructions which, when executed on the associated processor 1221, enable the apparatus 1220 to operate in accordance with the embodiments of the present disclosure. The combination of at least one processor 1221 and at least one memory 1222 can form a processing means 1225 suitable to implement the various embodiments of the present disclosure.

[0300] The various embodiments of the present disclosure can be implemented by a computer program executable by one or more of a processor 1221, software, firmware, hardware, or a combination thereof.

[0301] The memory 1222 can have any type suitable to the local technical environment and can be implemented using any suitable data storage technology, such as non-limiting examples semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.

[0302] The processor 1221 can be of any type such as, but not limited to, a central processing unit (CPU), a microprocessor, a microcomputer, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples.

[0303] In embodiments where the apparatus is implemented as, or at, a network function service consumer entity, the memory 1222 stores instructions executable by the processor 1221, whereby the network function service consumer entity operates according to the methods described with reference to Figure 5 In embodiments where the apparatus is implemented as, or at, a network function service consumer entity, the memory 1222 stores instructions executable by the processor 1221, whereby the network function service consumer entity operates according to the methods described with reference to

[0304] In embodiments where the apparatus is implemented as, or at, a data management entity, the memory 1222 stores instructions executable by the processor 1221, whereby the data management entity operates according to the methods described with reference to Figure 6 In embodiments where the apparatus is implemented as, or at, a data management entity, the memory 1222 stores instructions executable by the processor 1221, whereby the data management entity operates according to the methods described with reference to

[0305] In embodiments where the apparatus is implemented as, or at, a data repository entity, the memory 1222 stores instructions executable by the processor 1221, whereby the data repository entity operates according to the methods described with reference to Figure 7 In embodiments where the apparatus is implemented as, or at, a data repository entity, the memory 1222 stores instructions executable by the processor 1221, whereby the data repository entity operates according to the methods described with reference to

[0306] Figure 13 FIG. 13 is a block diagram illustrating a network function service consumer entity according to embodiments of the present disclosure. As illustrated, the network function service consumer entity 1300 includes a transmitting module 1302 and a receiving module 1304. The transmitting module 1302 can be configured to transmit, to a data management entity, a request to retrieve at least two registration data sets related to a user equipment. The request includes two or more corresponding registration data set names. The receiving module 1304 can be configured to receive, from the data management entity, a response. The response includes the at least two requested registration data sets related to the user equipment.

[0307] Figure 14 FIG. 14 is a block diagram illustrating a data management entity according to embodiments of the present disclosure. As illustrated, the data management entity 1400 includes a receiving module 1402 and a transmitting module 1404. The receiving module 1402 can be configured to receive, from a network function service consumer entity, a request to retrieve at least two registration data sets related to a user equipment. The request includes two or more corresponding registration data set names. The transmitting module 1404 can be configured to transmit, to the network function service consumer entity, a response. The response includes the at least two requested registration data sets related to the user equipment.

[0308] Figure 15is a block diagram illustrating a data repository entity according to an embodiment of the present disclosure. As shown, the data repository entity 1500 includes a receiving module 1502 and a sending module 1504. The receiving module 1502 can be configured to receive, from a data management entity, a query request for retrieving at least two registration data sets related to a user equipment, wherein the query request includes two or more corresponding registration data set names. The sending module 1504 can be configured to send, to the data management entity, a query response. The query response includes the at least two requested registration data sets related to the user equipment.

[0309] According to an aspect of the present disclosure, there is provided a computer program product tangibly stored on a computer readable storage medium and comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0310] According to an aspect of the present disclosure, there is provided a computer readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0311] The embodiments herein provide a number of advantages, the following is a non-exhaustive list of examples of advantages. In some embodiments herein, for a data management entity such as UDM, a new GET method is introduced on the resource {ueId} / registrations as a generic registration data set retrieval method to enable the possibility of retrieving multiple registration data sets using a single GET request. Thus, the proposed method provided by the data management entity supports use cases that have been identified to benefit from retrieving multiple registration data sets using a single GET request. In some embodiments herein, for a data repository entity such as UDR, the GET method for multiple context data set retrieval is updated to enable the possibility of retrieving multiple context data sets together with session context data (e.g. SMF PDU session context data) using a single GET request. Thus, the proposed method provided by the data repository entity supports use cases that have been identified to benefit from retrieving multiple registration data sets including session context data using a single GET request. In some embodiments herein, from an operational point of view, unnecessary signaling traffic is avoided and network efficiency is improved, which means that OPEX (operational expenditure) is reduced. The embodiments herein are not limited to the above-mentioned features and advantages. Additional features and advantages will be recognized by persons of skill in the art upon reading the following detailed description.

[0312] Further, the present disclosure can also provide a carrier containing the computer program as described above, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium. The computer readable storage medium can be, for example, an optical disc or an electronic storage device such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray Disc, etc.

[0313] The techniques described herein can be implemented by various means. For example, these techniques can be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For a firmware or software implementation, the

[0314] The example embodiments herein have been described above with reference to block diagrams and flowchart illustrations of methods and apparatuses. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by various means, including computer program instructions. These computer program instructions can be loaded into a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which, when executed by the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks.

[0315] Further, although operations can be depicted in a particular order, this should not be understood as requiring such order, nor that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Likewise, while several specific implementation details have been discussed, these should not be construed as limiting the scope of the subject matter described herein, but merely as describing examples of certain implementations. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments or in any suitable sub-combination.

[0316] While the specification contains many specific implementation details, these should not be construed as limiting the scope or potential applications of any embodiments, but merely as describing implementations of particular embodiments that can be readily utilized in addition, certain features that are, for clarity, described in the context of separate embodiments can also be provided in combination in a single embodiment. Conversely, various features that are, for brevity, described in the context of a single embodiment can also be provided separately or in any suitable subcombination. In addition, while the above description has been made that the features can act in the conjunction, and even originally so claimed, in some instances one or more features from a claimed combination can be removed and the claimed combination can be directed to a subcombination or variation of a subcombination.

[0317] It will be apparent to those skilled in the art that as technology advances, the concept of the application can be implemented in various ways. The above examples are given for descriptive purposes only and not intended to limit the disclosure, and it is recognized that modifications and variations of specific implementations can be made by those skilled in the art without departing from the spirit and scope of the disclosure. Such modifications and variations are considered to be within the scope of the disclosure and the appended claims. The scope of the disclosure is defined by the appended claims.

Claims

1. A method (500) performed by a network function service consumer entity, comprising: sending (502), to a data management entity, a request for retrieving at least two registration data sets related to a user equipment, wherein the request comprises two or more corresponding registration data set names; and receiving (504), from the data management entity, a response, wherein the response comprises the at least two requested registration data sets related to the user equipment, wherein the registration data set names comprise at least one of: a registration data set name identifying session management function registration information; a registration data set name identifying access and mobility management function, AMF, third generation partnership project, 3GPP, access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function, SMSF, 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

2. The method of claim 1, wherein, when the request comprises the registration data set name identifying session management function registration information, the request further comprises a single network slice selection assistance information and / or a data network name.

3. The method of claim 1, wherein, the request is a hypertext transfer protocol, HTTP, GET request and the response is an HTTP GET response.

4. The method of claim 3, wherein, the HTTP GET response comprises: a response code 200 OK and a response body containing the at least two requested registration data sets related to the user equipment; or a response code 404 Not Found.

5. The method of any one of claims 1-4, wherein, the request further comprises a user equipment identity representing the user equipment.

6. The method of claim 5, wherein, the user equipment identity is a subscription permanent identifier, SUPI, or a generic public subscription identifier, GPSI.

7. The method according to any one of claims 1-4 and 6, wherein the network function service consumer entity is a network data analytics function, NWDAF, entity or a home subscriber server, HSS; and / or the data management entity is a unified data management, UDM, entity.

8. A method (600) performed by a data management entity, comprising: receiving (602), from a network function service consumer entity, a request for retrieving at least two registration data sets related to a user equipment, wherein the request comprises two or more corresponding registration data set names; and sending (608), to the network function service consumer entity, a response, wherein the response comprises the at least two requested registration data sets related to the user equipment, wherein the registration data set names comprise at least one of: a registration data set name identifying session management function registration information; a registration data set name identifying access and mobility management function, AMF, third generation partnership project, 3GPP, access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function, SMSF, 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

9. The method of claim 8, wherein, when the request comprises a registration data set name identifying session management function registration information, the request further comprises a single network slice selection assistance information and / or a data network name.

10. The method of claim 8, wherein, the request is a hypertext transfer protocol, HTTP, GET request and the response is an HTTP GET response.

11. The method of claim 10, wherein, the HTTP GET response comprises: a response code 200 OK and a response body containing at least two requested registration data sets related to the user equipment; or a response code 404 Not Found.

12. The method of any one of claims 8-11, wherein, the request further comprises a user equipment identity representing the user equipment.

13. The method of claim 12, wherein, the user equipment identity is a subscription permanent identifier, SUPI, or a generic public subscription identifier, GPSI.

14. The method of any one of claims 8-11 and 13, wherein the network function service consumer entity is a network data analytics function, NWDAF, entity or a home subscriber server, HSS; and / or the data management entity is a unified data management, UDM, entity.

15. The method of any one of claims 8-11 and 13, further comprising: sending (604), to a data repository entity, a query request for retrieving at least two registration data sets related to a user equipment, wherein the query request comprises two or more corresponding registration data set names; and receiving (606), from the data repository entity, a query response, wherein the query response comprises at least two requested registration data sets related to the user equipment.

16. The method of claim 15, wherein, the data repository entity is a unified data repository, UDR, entity.

17. A method (700) performed by a data repository entity, comprising: receiving (702), from a data management entity, a query request for retrieving at least two registration data sets related to a user equipment, wherein the query request comprises two or more corresponding registration data set names; and sending (704), to the data management entity, a query response, wherein the query response comprises at least two requested registration data sets related to the user equipment, wherein the registration data set names further comprise at least one of: a registration data set name identifying access and mobility management function, AMF, third generation partnership project, 3GPP, access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function, SMSF, 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

18. The method of claim 17, wherein, when the query request comprises a registration data set name identifying session management function registration information, the query request further comprises a single network slice selection assistance information and / or a data network name.

19. The method of any one of claims 17-18, wherein, the query request is a hypertext transfer protocol, HTTP, GET request and the query response is an HTTP GET response.

20. The method of any one of claims 17-18, wherein the data management entity is a unified data management, UDM, entity, and the data repository entity is a unified data repository, UDR, entity.

21. A network function service consumer entity (1200), comprising: a processor (1221); and a memory (1222) coupled with the processor (1221), the memory (1222) storing instructions executable by the processor (1221), whereby the network function service consumer entity (1200) is operable to: send, to a data management entity, a request for retrieving at least two registration data sets related to a user equipment, wherein the request comprises two or more corresponding registration data set names; and receive, from the data management entity, a response, wherein the response comprises at least two requested registration data sets related to the user equipment, wherein the registration data set names comprise at least one of: a registration data set name identifying session management function registration information; a registration data set name identifying access and mobility management function, AMF, third generation partnership project, 3GPP, access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function, SMSF, 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

22. The network function service consumer entity of claim 21, wherein, The network function service consumer entity is further operable to perform the method of any one of claims 2 to 7.

23. A data management entity (1200), comprising: a processor (1221); and a memory (1222) coupled with the processor (1221), the memory (1222) storing instructions executable by the processor (1221), whereby the data management entity (1200) is operable to: receive, from a network function service consumer entity, a request for retrieving at least two registration data sets related to a user equipment, wherein the request comprises two or more corresponding registration data set names; and send, to the network function service consumer entity, a response, wherein the response comprises at least two requested registration data sets related to the user equipment, wherein the registration data set names comprise at least one of: a registration data set name identifying session management function registration information; a registration data set name identifying access and mobility management function, AMF, third generation partnership project, 3GPP, access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function, SMSF, 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

24. The data management entity of claim 23, wherein the data management entity is further operable to perform the method of any one of claims 9 to 16.

25. A data repository entity (1200), comprising: a processor (1221); and a memory (1222) coupled with the processor (1221), the memory (1222) storing instructions executable by the processor (1221), whereby the data repository entity (1200) is operable to: a memory (1222) coupled with the processor (1221), the memory (1222) storing instructions executable by the processor (1221) whereby the data repository entity (1200) is operable to: receive, from a data management entity, a query request for retrieving at least two registration data sets related to a user equipment, wherein the query request comprises two or more corresponding registration data set names; and send, to the data management entity, a query response, wherein the query response comprises at least two requested registration data sets related to the user equipment, wherein the registration data set names further comprise at least one of: a registration data set name identifying access and mobility management function, AMF, third generation partnership project, 3GPP, access registration information; a registration data set name identifying AMF non-3GPP access registration information; a registration data set name identifying short message service function, SMSF, 3GPP access registration information; and a registration data set name identifying SMSF non-3GPP access registration information.

26. The data repository entity of claim 25, wherein the data repository entity is further operable to perform the method of any one of claims 18 to 20.

27. A computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 20.

28. A computer program product comprising instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 20.

Images