Patent ID: 12245116

DETAILED DESCRIPTION

The following describes currently preferred embodiments of apparatuses and methods to evolve the centralized 5G UDR in a traditional layered architecture into multiple different SBA services, each one providing access to a specific, independent and limited set of data (implementing a kind of “data custodian” pattern for that data), that is only accessible by same service operations. In this way, constrains identified above for the development of UDR and its consumers are either overcome or minimized, and these new SBA services fits perfectly in a CNA.

For illustrative purposes, this document focusses on Subscription data required for existing 5G data consumers: AMF, SMF and SMSF, all via UDM. Same analysis can be applicable to Subscription data required for other Nudr consumers (e.g. PCF, NEF) or to other Data Sets stored in UDR.

The AMF, SMF and SMSF access to data, with Nudm_SDM service, via UDM that retrieves data, with Nudr_DM service, from UDR. In this respect, Nudm_SDM service performs some logic on top of data retrieved from UDR, like feature support, data access authorization enforcement, etc.

Data currently retrieved by AMF, SMF and SMSF, with Nudm_SDM service via UDM, is disclosed in 3GPP TS 23.502 clause 5.2.3.3.1, organized in so called Subscription Data Types, i.e. group of data that is retrieved at once, as shown in the Table I below.

TABLE INudm_SDM Subscription Data TypesSubscription datatypeFieldDescriptionAccess andSUPIKeyMobilityGPSI ListList of the GPSI (Generic PublicSubscription dataSubscription Identifier) used both inside(data needed forand outside of the 3GPP system toUE Registrationaddress a 3GPP subscription.and MobilityInternal Group ID-listList of the subscribed internal group(s) thatManagement)the UE belongs to.Subscribed-UE-AMBRThe Maximum Aggregated uplink anddownlink MBRs to be shared across allNon-GBR QoS Flows according to thesubscription of the user.Subscribed S-NSSAlsThe Network Slices that the UE subscribes to.Default S-NSSAIsThe Subscribed S-NSSAls marked asdefault S-NSSAI.UE Usage TypeAs defined in TS 23.501 [2],clause 5.15.7.2.RAT restriction3GPP Radio Access Technology(ies) notallowed the UE to access.Forbidden areaDefines areas in which the UE is notpermitted to initiate any communicationwith the network.Service Area RestrictionIndicates Allowed areas in which the UE ispermitted to initiate communication withthe network, and Non-allowed areas inwhich the UE and the network are notallowed to initiate Service Request or SMsignalling to obtain user services.Core Network typeDefines whether UE is allowed to connectrestrictionto 5GC for this PLMN.RFSP IndexAn index to specific RRM configuration inthe NG-RAN.Subscribed PeriodicIndicates a subscribed PeriodicRegistration TimerRegistration Timer value.Priority ServicesIndicates the user is subscribed topriority.service (MPS) as indicated inTS 23.501 [2], clause 5.16.5.Slice SelectionSUPIKeySubscription dataSubscribed S-NSSAIsThe Network Slices that the UE subscribes(data needed forto. In roaming case, it indicates theSlice Selection assubscribed network slices applicable to thedescribed inserving PLMN.clause 4.2.2.2.3)UE context in AMFSUPIKeydataAMFAllocated AMF for the registered UE.Include AMF address and AMF NF Id.Access Type3GPP or non-3GPP access through this AMFSMF SelectionSUPIKeySubscription dataSubscribed DNN listList of the subscribed DNNs for the UE.(data needed forDefault DNNThe default DNN if the UE does notSMF Selection asprovide a valid DNN.described inLBO Roaming InformationIndicates whether LBO roaming is allowedclause 6.3.2 ofper DNN, or per (S-NSSAI, subscribedTS 23.501 [2])DNN)UE context in SMFSUPIKeydataPDU Session Id(s)List of PDU Session Id(s) for the UEFor each PDU Session Id:DNNDNN for the PDU Session.SMFAllocated SMF for the PDU Session.Includes SMF IP Address and SMF NF Id.SMS ManagementSUPIKeySubscription dataSMS parametersIndicates SMS parameters subscribed for(data needed bySMS service such as SMS teleservice,SMSF for SMSFSMS barring listRegistration)SMS SubscriptionSUPIKeydataSMS SupportedIndicates whether the UE supports SMS(data needed indelivery over NAS via 3GPP access, or viaAMF)non-3GPP access, or via both the 3GPPand non-3GPP access.SMSF addressIndicates SMSF address subscribed forSMS service.SessionSUPIKeyManagementSession Management Subscription data contains one or more S-Subscription dataNSSAI level subscription data:(data needed forS-NSSAIIndicates the value of the S-NSSAI.PDU SessionSubscribed DNN listList of the subscribed DNNs for the S-Establishment)NSSAI.For each DNN in S-NSSAI level subscription data:UE AddressIndicates the subscribed static IPaddress(es) for the IPV4 or IPv6 or IPv4v6type PDU Sessions accessing the DNN, S-NSSAI.Allowed PDU SessionIndicates the allowed PDU Session TypesTypes(IPv4, IPv6, IPv4v6, Ethernet, andUnstructured) for the DNN, S-NSSAI.Default PDU Session TypeIndicates the default PDU Session Typefor the DNN, S-NSSAI.Allowed SSC modesIndicates the allowed SSC modes for theDNN, S-NSSAI.Default SSC modeIndicate the default SSC mode for theDNN, S-NSSAI.5GS Subscribed QoSThe QoS Flow level QoS parameter valuesprofile(5QI and ARP) for the DNN, S-NSSAI (seeclause 5.7.2.7 of TS 23.501 [2]).Charging CharacteristicsThis information is defined inTS 32.240 [34]; it may e.g. containinformation on how to contact the ChargingFunction. This information, when providedshall override any correspondingpredefined information at the SMFSubscribed-Session-AMBRThe maximum aggregated uplink anddownlink MBRs to be shared across allNon-GBR QoS Flows in each PDUSession, which are established for theDNN, S-NSSAI.Static IP address/prefixIndicate the static IP address/prefix for theDNN, S-NSSAI.User Plane Security PolicyIndicates the security policy for integrityprotection and encryption for the userplane.IdentifierGPSIGeneric Public Subscription Identifier usedtranslationinside and outside of the 3GPP system toaddress a 3GPP subscription. Used as theKey for translation to the correspondingSUPI (and optionally correspondingMSISDN).SUPICorresponding SUPI for input GPSI(Optional) MSISDNCorresponding GPSI (MSISDN) for inputGPSI (External Identifier). This is optionallyprovided for legacy SMS infrastructure notsupporting MSISDN-less SMS. Thepresence of an MSISDN should beinterpreted as an indication to the NEF thatMSISDN shall be used to identify the UEwhen sending the SMS to the SMS-SC via T4.

These Subscription Data Types are retrieved by UDM from UDR as a whole. However, 3GPP TS 23.502 clause 5.2.12.2.1 discloses a different data structure for Nudr, wherein a Data Set Subscription Data corresponds to the complete Table I disclosed above (as disclosed in clause 5.2.3.3.1), and wherein this Data Set is associated with a plurality of so-called Data Subsets, as disclosed inFIG.6.

Regarding the definition of SBA services, which aims the present specification, multiple options are possible, depending on the granularity of the functionality to be provided, what identifies the data owned by each service.

In this specification, the following SBA services20, as illustrated inFIG.7, are discussed:

Access and Mobility subscription data mng (AccessMobilitySubsData)20a, which owns following Data Subsets: Access and Mobility Subscription data, Slice Selection Subscription data, UE context in AMF data. It also owns data provided at AMF (or similar future new consumer) registration.

Session subscription data mng (SessionSubsData)20b, which owns following Data Subsets: SMF Selection Subscription data, UE context in SMF data, Session Management Subscription data. It also owns data provided at SMF (or similar future new consumer) registration.

SMS subscription data mng (SMSSubsData)20c, which owns following Data Subsets: SMS Management Subscription data, SMS Subscription data. It also owns data provided at SMSF (or similar future new consumer) registration.

For all new SBA services20, Query, Update, Subscribe, Unsubscribe and Notify Service Operations26are defined; and, for each Service Operation, the Operation Semantics27is also defined, as also shown inFIG.7.

With the splitting of a previous Data Set into a plurality of different and specific SBA services, the AMF, SMF and SMSF (as defined in 3GPP TS 23.502 call flows) can keep on requesting Subscription Data Types10afrom UDM that, instead of getting corresponding data from UDR via Nudr_DM for each corresponding Data Subsets12, it can access corresponding specific information thanks to a query operation on the corresponding new proposed SBA service20a,20bor20c, as the case may be.

For example, in an embodiment illustrated inFIG.8, the UDM4may determine that for a request for Subscription Data Types10areceived from the AMF7, the UDM4retrieves Access and Mobility subscription data mng20afrom the UDR1; whereas for a request for Subscription Data Types10areceived from the SMF8, the UDM4retrieves Session subscription data mng20b.

A further improvement of defining the SBA services is discussed with reference to the exemplary registration procedure call flow disclosed in 3GPP TS 23.502 clause 4.2.2.2.2. Interactions between UDM and UDR are not shown, for the shake of simplicity, in the figure for this call flow, but are reflected in the corresponding text for actions14a,14b,14cand14d.

With the definition of the new SBA services, as discussed above, the actions14a,14b,14cand14din clause 4.2.2.2.2 of 3GPP TS 23.502 require some modifications discussed in the following.

Action14a-b. If the AMF has changed since the last Registration procedure, or if the UE provides a SUPI which doesn't refer to a valid context in the AMF, or if the UE registers to the same AMF it has already registered to a non-3GPP access (i.e. the UE is registered over a non-3GPP access and initiates this Registration procedure to add a 3GPP access), the new AMF registers with the UDM using Nudm_UECM_Registration and subscribes to be notified when the UDM deregisters this AMF. The UDM stores the AMF identity associated to the Access Type and does not remove the AMF identity associated to the other Access Type. The UDM stores information provided at registration in AccessMobilitySubsData service, by Update operation.

The AMF retrieves the Access and Mobility Subscription data, SMF Selection Subscription data and UE context in SMF data using Nudm_SDM_Get. This requires that UDM retrieves this information from AccessMobilitySubsData and SessionSubsData services by Query operations. After a successful response is received, the AMF subscribes to be notified using Nudm_SDM_Subscribe when the data requested is modified, UDM subscribes to AccessMobilitySubsData and SessionSubsData services by Subscribe operations. The GPSI is provided to the AMF in the Access and Mobility Subscription data from the UDM if the GPSI is available in the UE subscription data.

The new AMF provides the Access Type it serves for the UE to the UDM and the Access Type is set to “3GPP access”. The UDM stores the associated Access Type together with the serving AMF in AccessMobilitySubsData by Update operation.

The new AMF creates an MM context for the UE after getting the Access and Mobility Subscription data from the UDM.

For an Emergency Registration in which the UE was not successfully authenticated, the AMF shall not register with the UDM.

For an Emergency Registration, the AMF shall not check for access restrictions, regional restrictions or subscription restrictions. For an Emergency Registration, the AMF shall ignore any unsuccessful registration response from UDM and continue with the Registration procedure.

Action14c. When the UDM stores the associated Access Type (e.g. 3GPP) together with the serving AMF as indicated in step14a, it will cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2) to the old AMF corresponding to the same (e.g. 3GPP) access, if one exists. The old AMF removes the MM context of the UE. If the serving NF removal reason indicated by the UDM is Initial Registration, then, as described in clause 4.2.2.3.2, the old AMF invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMF(s) of the UE to notify that the UE is deregistered from old AMF. The SMF(s) shall release the PDU Session on getting this notification.

Action14d. The Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe.

That is, the access to the whole Data Set Subscription Data10bin the UDR1, is replaced by the access to a particular SBA service20a,20bor20cdepending on the required data in each case.

An advantage of this proposal is that such solution fits into 3GPP Rel-16, where it is expected that Services are deployed independently from any NF, that is, Services need to be independent. Therefore, there is not a need to define any new NF, or to keep existing UDR, but on the contrary, the new proposed services are used independently of any NF.

There is thus provided, in the present specification, a method for accessing data in a UDR1, the method carried out at the UDR.

In accordance with an embodiment illustrated inFIG.11, this method comprises a step S-1110of splitting a Data Set10b, which is provided in the UDR for a plurality of NF service consumers11, into a plurality of SBA services20, wherein each SBA service e.g.20ais associated with one or more Data Subsets e.g.22a,23a,24a,25a, amongst a plurality of Data Subsets12associated with the Data Set10b, and wherein each SBA service e.g.20ais provided for one or more NF service consumer21amongst the plurality of NF service consumers11.

In this embodiment, the method also comprises a step S-1120of registering, toward an NRF2, identifiers for the plurality of SBA services e.g.20a,20b,20chandled at the UDR and an identifier of the UDR; a step S-1130of receiving, from an NF service consumer3, a service request for an SBA service e.g.20a; and a step S-1140of transmitting, toward the NF service consumer3, information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a.

In accordance with another embodiment illustrated inFIG.12, this method comprises a step S-1210of storing, for a Data Set10bprovided in the UDR for a plurality of NF service consumers11, a plurality of SBA services20, wherein each SBA service e.g.20ais associated with one or more Data Subsets e.g.22a,23a,24a,25a, amongst a plurality of Data Subsets12associated with the Data Set10b, and wherein each SBA service e.g.20ais provided for one or more NF service consumer21amongst the plurality of NF service consumers11.

In this another embodiment, the method also comprises a step S-1220of registering, toward an NRF2, identifiers for the plurality of SBA services e.g.20a,20b,20chandled at the UDR and an identifier of the UDR; a step S-1230of receiving, from an NF service consumer3, a service request for an SBA service e.g.20a; and a step S-1240of transmitting, toward the NF service consumer3, information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a.

There is also provided, in the present specification, a method for accessing data in a UDR1, the method carried out at an NF service customer node3or4.

In accordance with an embodiment illustrated inFIG.13, this method comprises a step S-1310of transmitting, toward a NRF2, a service discovery request with an identifier of an SBA service e.g.20a; a step S-1320of receiving, from the NRF2, an identifier of the UDR1instance handling the SBA service20a; a step S-1330of transmitting, toward the UDR1identified by the identifier of the UDR instance, a service request for the SBA service20a; and a step S-1340of receiving, from the UDR1, information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service20a.

In a sub-embodiment illustrated inFIG.14, for the embodiment discussed above with reference toFIG.13, and in the case where the NF service customer node is a UDM4, this method may also comprise a step S-1410of receiving, from a further network node (such as an AMF node7or an SMF node8may be), an NF service10arequest for a Data Set10bprovided in the UDR1for a plurality of NF service consumers11; and a step S-1420of determining, based on the further network node e.g.7or8, an SBA service20afor which the service request is transmitted toward the UDR1.

When this is the case, upon receiving from the UDR1, during the step S-1340commented above, the information data relating to the one or more Data Subsets (e.g.22a,23a,24a,25a) associated with the SBA service e.g.20a, this method further comprises a step S-1430of transmitting, toward the further network node7or8, an NF service10aresponse in accordance with the information data relating to the one or more Data Subsets (e.g.22a,23a,24a,25a).

In order to carry out these methods discussed with reference toFIG.11andFIG.12, different embodiments of the UDR1or60are illustrated inFIG.9andFIG.15.

In accordance with an embodiment illustrated inFIG.9, the UDR60or1may comprise at least one processor620, and at least one memory610that stores processor-executable instructions614. In this UDR, the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the UDR is operable to perform the actions disclosed in the following.

This UDR illustrated inFIG.9, in an embodiment, may thus be operable to split a Data Set10b, which is provided in the UDR for a plurality of NF service consumers11, into a plurality of SBA services20, wherein each SBA service e.g.20ais associated with one or more Data Subsets e.g.22a,23a,24a,25a, amongst a plurality of Data Subsets12associated with the Data Set10b, and wherein each SBA service e.g.20ais provided for one or more NF service consumer21amongst the plurality of NF service consumers11. In a sub-embodiment, a service handler627running in a processor620may split the Data Set into the plurality of SBA services.

This UDR illustrated inFIG.9, in another embodiment, may be operable to store, for a Data Set10bprovided in the UDR for a plurality of NF service consumers11, a plurality of SBA services20, wherein each SBA service e.g.20ais associated with one or more Data Subsets e.g.22a,23a,24a,25a, amongst a plurality of Data Subsets12associated with the Data Set10b, and wherein each SBA service e.g.20ais provided for one or more NF service consumer21amongst the plurality of NF service consumers11. In a sub-embodiment, a service handler627running in a processor620may store, for the Data Set, the plurality of SBA services.

In both embodiments, this UDR illustrated inFIG.9may also be operable to register, toward an NRF2via transmitter640, identifiers for the plurality of SBA services20a,20b,20chandled at the UDR and an identifier of the UDR; receive, from an NF service consumer3via receiver630, a service request for an SBA service e.g.20a; and transmit, toward the NF service consumer3via the transmitter640, information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a.

In sub-embodiments for both embodiments, the service handler627running in the processor620may handle the logic related to the SBA services, such as the registration and fetching the data relating to the one or more Data associated with the SBA service, whereas a protocol handler627running in a processor620may control the transmitter640and receiver630for transmission and reception of messages.

If required at all, the UDR60or1, illustrated inFIG.9, may be complemented with a data section618in memory to store the SBA services and respective Data subsets along with NF service consumers for each SBA service.

The UDR illustrated inFIG.9may thus comprise the at least one processor620and the at least one memory610, both in communication with each other, with the protocol handler624, the service handler627, the receiver630and the transmitter640, and with other elements or units of the UDR. The at least one memory610may comprise volatile and/or non-volatile memory. In particular, the at least one memory610may have a computer program614and data618stored therein. The computer program614may be loaded in the at least one memory610from a computer program product650, such as any non-transitory computer readable medium, in which the computer program is stored. The data618may comprise the SBA services and respective Data subsets along with NF service consumers for each SBA service. The at least one processor620may be configured to carry out the functions of the protocol handler624and the service handler627.

In accordance with another embodiment illustrated inFIG.15, the UDR60or1, in an embodiment, may be operable to split a Data Set10b, which is provided in the UDR for a plurality of NF service consumers11, into a plurality of SBA services20, wherein each SBA service e.g.20ais associated with one or more Data Subsets e.g.22a,23a,24a,25a, amongst a plurality of Data Subsets12associated with the Data Set10b, and wherein each SBA service e.g.20ais provided for one or more NF service consumer21amongst the plurality of NF service consumers11. In a sub-embodiment, a service handler627running in a processor620may split the Data Set into the plurality of SBA services.

This UDR illustrated inFIG.15, in another embodiment, may be operable to store, for a Data Set10bprovided in the UDR for a plurality of NF service consumers11, a plurality of SBA services20, wherein each SBA service e.g.20ais associated with one or more Data Subsets e.g.22a,23a,24a,25a, amongst a plurality of Data Subsets12associated with the Data Set10b, and wherein each SBA service e.g.20ais provided for one or more NF service consumer21amongst the plurality of NF service consumers11. In a sub-embodiment, a service handler627running in a processor620may store, for the Data Set, the plurality of SBA services.

In both embodiments, this UDR illustrated inFIG.15may also be operable to register, toward an NRF2via transmitter640, identifiers for the plurality of SBA services20a,20b,20chandled at the UDR and an identifier of the UDR; receive, from an NF service consumer3via receiver630, a service request for an SBA service e.g.20a; and transmit, toward the NF service consumer3via the transmitter640, information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a.

In sub-embodiments for both embodiments discussed above with reference toFIG.15, the UDR may comprise a service handler627operable to handle the logic related to the SBA services, such as the registration and fetching the data relating to the one or more Data associated with the SBA service, and a protocol handler627operable to control the transmitter640and receiver630for transmission and reception of messages.

In order to carry out these methods discussed above with reference toFIG.13andFIG.14, different embodiments of the NF service consumer node70,3or4are illustrated inFIG.10andFIG.16.

In accordance with an embodiment illustrated inFIG.10, the NF service consumer node70,3or4may comprise at least one processor720, and at least one memory710that stores processor-executable instructions714. In this NF service consumer node, the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the NF service consumer node is operable to perform the actions disclosed in the following.

This NF service consumer node, illustrated inFIG.10, may thus be operable to transmit, toward an NRF2via transmitter740, a service discovery request with an identifier of an SBA service e.g.20a; receive, from the NRF2via receiver730, an identifier of the UDR1instance handling the SBA service e.g.20a; transmit, toward the UDR1identified by the identifier of the UDR instance via the transmitter740, a service request for the SBA service (20a); and receive, from the UDR1via the receiver730, information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a.

This NF service consumer node illustrated inFIG.10, in an embodiment wherein the NF service consumer node implements a UDM4, may further be operable to receive, from a further network node, such as an AMF node7or an SMF node8might be, via the receiver730, an NF service10arequest for a Data Set10bprovided in the UDR1for a plurality of NF service consumers11; determine, based on the further network node, an SBA service e.g.20afor which the service request is transmitted toward the UDR1; and, upon receiving, from the UDR1, the information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a, transmit, toward the further network node via the transmitter740, an NF service10aresponse in accordance with the information data relating to the one or more Data Subsets e.g.22a,23a,24a,25a.

In sub-embodiments, the NF service consumer node illustrated inFIG.10may comprise a service handler728running in the processor720configured to handle the logic related to the SBA services, such as SBA service discovery and fetching the data relating to the one or more Data associated with the SBA service, and a UDR protocol handler726running in a processor720configured to control the transmitter740and receiver730for transmission and reception of messages.

In the embodiment where the NF service consumer node70implements a UDM4, the NF service consumer node illustrated inFIG.10may comprise a UDM protocol handler724running in a processor720configured to control the transmitter740and receiver730for transmission and reception of messages to and from the further network node, such as an AMF node7or an SMF node8might be.

If required at all, the NF service consumer node70,3or4, as illustrated inFIG.10, may be complemented with a data section718in memory to store the SBA services and respective Data subsets for each SBA service.

The NF service consumer node illustrated inFIG.10may thus comprise the at least one processor720and the at least one memory710, both in communication with each other, with the UDM protocol handler724(if provided), the UDR protocol handler726, the service handler728, the receiver730and the transmitter740, and with other elements or units of the NF service consumer node. The at least one memory710may comprise volatile and/or non-volatile memory. In particular, the at least one memory710may have a computer program714and data718stored therein. The computer program714may be loaded in the at least one memory710from a computer program product750, such as any non-transitory computer readable medium, in which the computer program is stored. The data718may comprise the SBA services and respective Data subsets for each SBA service. The at least one processor720may be configured to carry out the functions of the UDM protocol handler724(if provided), the UDR protocol handler726and the service handler728.

In accordance with another embodiment illustrated inFIG.16, the NF service consumer node70,3or4may be operable to transmit, toward an NRF2via transmitter740, a service discovery request with an identifier of an SBA service e.g.20a; receive, from the NRF2via receiver730, an identifier of the UDR1instance handling the SBA service e.g.20a; transmit, toward the UDR1identified by the identifier of the UDR instance via the transmitter740, a service request for the SBA service (20a); and receive, from the UDR1via the receiver730, information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a.

This NF service consumer node illustrated inFIG.16, in an embodiment wherein the NF service consumer node implements a UDM4, may further be operable to receive, from a further network node, such as an AMF node7or an SMF node8might be, via the receiver730, an NF service10arequest for a Data Set10bprovided in the UDR1for a plurality of NF service consumers11; determine, based on the further network node, an SBA service e.g.20afor which the service request is transmitted toward the UDR1; and, upon receiving, from the UDR1, the information data relating to the one or more Data Subsets e.g.22a,23a,24a,25aassociated with the SBA service e.g.20a, transmit, toward the further network node via the transmitter740, an NF service10aresponse in accordance with the information data relating to the one or more Data Subsets e.g.22a,23a,24a,25a.

In sub-embodiments, the NF service consumer node illustrated inFIG.16may comprise a service handler728configured to handle the logic related to the SBA services, such as SBA service discovery and fetching the data relating to the one or more Data associated with the SBA service, and a UDR protocol handler726configured to control the transmitter740and receiver730for transmission and reception of messages.

In the embodiment where the NF service consumer node70implements a UDM4, the NF service consumer node illustrated inFIG.16may comprise a UDM protocol handler724configured to control the transmitter740and receiver730for transmission and reception of messages to and from the further network node, such as an AMF node7or an SMF node8might be.

On the other hand,FIG.17illustrates a method in accordance with 3GPP TS 23.501 and TS 23.502.

In this method, actions S-1710to S-1730may be performed in any order. Each UDR registers its NF profile. We have as an example 3 different UDRs, each storing a different set of data. In this respect, TS 23.501 clause 6.2.6 discloses the NF profile contents of NF instances maintained in an NRF. Each Nudr_DM service, for each UDR NF, has to provide corresponding “Identification of stored data/information”, that is, the means to identify whether it is UDR-1, UDR-2or UDR-3, and which data is stored in each one, allowing the consumer to select which one to use.

Action S-1740. The UDR consumer, i.e. the consumer of the Nudr_DM service (in this example UDM) needs to indicate the NF and service name to be discovered (i.e. Nudr_DM) and it will get back, Action S-1750, the information for each the Nudr_DM that are registered, with the NF profile information, what identifies the set of data that is stored in each one.

Consequently, a method for service execution and selecting storage, as illustrated inFIG.18, can be followed so that an UDM Front End (UDM-FE) is able to distinguish the destination UDR depending on required data, as is described in following figure, at selection of destination provider service. As illustrated inFIG.18:

Action S-1810. As an exemplary use case, we can consider when AMF needs to get access to one UE subscriber data. It requests that information from UDM-FE, using Nudm_SubsDataMng_Get operation, for one specific UE identify (e.g. SUPIx).

Action S-1820. UDM-FE needs to identify which Nudr service needs to use to access corresponding data. It needs to check provided information at registration and as well some local configuration may be required. In our example, we consider only one UDR stores subscription data.

Action S-1830. UDM-FE executes Nudr service that is registered by UDR-1(i.e. using provided IP address or FQDN).

This method illustrated inFIG.18requires, as the one described with reference toFIG.17, some information to be provided at registration, to be stored in the NRF, and then be provided at discovery to the service consumer. In addition, the service consumer needs to store this information and check it every time for selection of the right instance.

That is, Nudr_DM Service as defined in existing TSs, requires knowledge of the internals of UDR, i.e. knowledge of different Data Sets stored, and even about possible subscription partitions. This knowledge is required not only by the Nudr_DM but by any of its consumers, and the NRF. Apart from that, this information is required to be stored in both the NRF and any consumer.

All this requires managing data, storage needs, and increases service consumer and producer complexity.

However, in accordance with an embodiment of the present specification, there is provided a new method for service registration and discovery as illustrated inFIG.19. This method, based on the distribution of internal data sets or even subsets into different services (rather than using only one Nudr_DM service), is based on a data-agnostic (and application-agnostic) registration, discovery and selection. As illustrated inFIG.19:

Actions S-1910to S-1930. Each set of data is accessible via a different new service, e.g. NewServiceSubsData, NewServiceApplicationData, NewServiceExpData. Then, each service is registered, without the need to provide anything else.

Action S-1940. At discovery, the UDR consumer (in this example, UDM), discovers the service that requires. In this case, it is NewServiceSubsData, since it requires to access Subscription data.

The invention may also be practised by a computer program, loadable into an internal memory of a computer with input and output units as well as with a processing unit. This computer program comprises to this end executable code adapted to carry out the above method steps when running in the computer. In particular, the executable code may be recorded in a carrier readable means in a computer.

Further advantages of this solution are discussed in the following.

A first advantage is that UDR complexity is limited and even decreased compared to pre-5G UDR. Instead of storing “all” data under the same Nudr service, new independent and smaller services are defined. Each one has a smaller amount of data and a limited set of use cases to model. Mapping from Nudr standard data structure to internal data model is more affordable and less complex.

A second advantage is that Nudr standard data structure limitations are decreased and Provisioning coupling may be reduced. Still Nudr aims for basic CRUD (Create-Read-Update-Delete) operations. But a simple search, or modification of a single data attribute may be more affordable and potentially feasible to be standardized in 3GPP, since the complexity of the data to manage/access may be very much reduced. In this way, still provisioning applications will be couple to internal data models, but the coupling may be limited, based on the possibility to enrich Nudr standard access.

A third advantage is that Application-logic is not required for Nudr service registration, discovery and selection. Different services are registered, discovered and/or selected. This follows some operators' view that services should be simplified, excluding any logic (like addressing) that is not required to perform the functionality they offer. This simplifies service providers and consumers logic and hence development and updating.

A fourth advantage is that Subscriber Data partition may not be required (it depends on each implementation solution for the new proposed services). Different independent services are defined to access smaller sets of data, this implies that the amount of data that is required to be access by each service is smaller. As new data is standardized, this would not be placed in an ever-growing UDR, but new services would be defined to provide correct access to that data. Therefore, it is possible to avoid reaching the maximum limits of scalability, although this depends on every specific implementation solution, since scalability limits are not only due to the maximum amount of data stored, but it depends as well e.g. on the number of subscribers and traffic model. But for the same requirements (traffic model, number of subscribers, etc.), having smaller services (with much less data than the big Nudr service) makes the scalability limits much further to be reached. Therefore, when Subscriber data partitions are not required, this simplifies network deployments. Apart from that, application-logic is not required for Nudr service (and its consumers: Nudm, Nausf, Npcf, Nnef) registration, discovery and selection.

The invention is described above in connection with various embodiments that are intended to be illustrative and non-restrictive. It is expected that those of ordinary skill in this art may modify these embodiments. The scope of the invention is defined by the claims in conjunction with the description and drawings, and all modifications that fall within the scope of the claims are intended to be included therein.

In this respect, some preliminary embodiments are listed in the following.

Embodiments:

1. A method for accessing data in a Unified Data Repository (1), UDR, the method comprising:splitting a Data Set (10b), which is provided in a UDR for a plurality of Network Function, NF, service consumers (11), into a plurality of Service Based Architecture, SBA, services (20), wherein each SBA service (20a) is associated with one or more Data Subsets (22a,23a,24a,25a), amongst a plurality of Data Subsets (12) associated with the Data Set (10b), and wherein each SBA service (20a) is provided for one or more NF service consumer (21) amongst the plurality of NF service consumers (11);registering, from the UDR toward a Network Repository Function (2), NRF, identifiers for the plurality of SBA services (20a,20b,20c) handled at the UDR and an identifier of the UDR;receiving, at the NRF (2) from an NF service consumer (3), a service discovery request with an identifier of an SBA service (20a);determining, at the NRF (2), an UDR instance handling the SBA service (20a);transmitting, from the NRF (2) toward the NF service consumer (3), an identifier of the UDR instance handling the SBA service (20a);transmitting, from the NF service consumer (3) toward the UDR (1) identified by the identifier of the UDR instance, a service request for the SBA service (20a); andreceiving, at the NF service consumer (3) from the UDR (1), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).2. A method for accessing data in a Unified Data Repository (1), UDR, the method comprising:storing, for a Data Set (10b) provided in a UDR for a plurality of Network Function, NF, service consumers (11), a plurality of Service Based Architecture, SBA, services (20), wherein each SBA service (20a) is associated with one or more Data Subsets (22a,23a,24a,25a), amongst a plurality of Data Subsets (12) associated with the Data Set (10b), and wherein each SBA service (20a) is provided for one or more NF service consumer (21) amongst the plurality of NF service consumers (11);registering, from the UDR toward a Network Repository Function (2), NRF, identifiers for the plurality of SBA services (20a,20b,20c) handled at the UDR and an identifier of the UDR;receiving, at the NRF (2) from an NF service consumer (3), a service discovery request with an identifier of an SBA service (20a);determining, at the NRF (2), an UDR instance handling the SBA service (20a);transmitting, from the NRF (2) toward the NF service consumer (3), an identifier of the UDR instance handling the SBA service (20a);transmitting, from the NF service consumer (3) toward the UDR (1) identified by the identifier of the UDR instance, a service request for the SBA service (20a); andreceiving, at the NF service consumer (3) from the UDR (1), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).3. A method for accessing data in a Unified Data Repository (1), UDR, the method carried out at the UDR (1) and comprising:splitting (S-1110) a Data Set (10b), which is provided in the UDR for a plurality of Network Function, NF, service consumers (11), into a plurality of Service Based Architecture, SBA, services (20), wherein each SBA service (20a) is associated with one or more Data Subsets (22a,23a,24a,25a), amongst a plurality of Data Subsets (12) associated with the Data Set (10b), and wherein each SBA service (20a) is provided for one or more NF service consumer (21) amongst the plurality of NF service consumers (11);registering (S-1120), toward a Network Repository Function (2), NRF, identifiers for the plurality of SBA services (20a,20b,20c) handled at the UDR and an identifier of the UDR;receiving (S-1130), from an NF service consumer (3), a service request for an SBA service (20a); andtransmitting (S-1140), toward the NF service consumer (3), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).4. A method for accessing data in a Unified Data Repository (1), UDR, the method carried out at the UDR (1) and comprising:storing (S-1210), for a Data Set (10b) provided in the UDR for a plurality of Network Function, NF, service consumers (11), a plurality of Service Based Architecture, SBA, services (20), wherein each SBA service (20a) is associated with one or more Data Subsets (22a,23a,24a,25a), amongst a plurality of Data Subsets (12) associated with the Data Set (10b), and wherein each SBA service (20a) is provided for one or more NF service consumer (21) amongst the plurality of NF service consumers (11);registering (S-1220), toward a Network Repository Function (2), NRF, identifiers for the plurality of SBA services (20a,20b,20c) handled at the UDR and an identifier of the UDR;receiving (S-1230), from an NF service consumer (3), a service request for an SBA service (20a); andtransmitting (S-1240), toward the NF service consumer (3), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).5. The method of any one of embodiments 1 or 4, wherein registering identifiers for the plurality of SBA services (20a,20b,20c) comprises registering, for each SBA service (20a), identifiers for the associated one or more Data Subsets (22a,23a,24a,25a).6. The method of any one of embodiments 1 to 5, wherein the Data Set (10b) corresponds to a so-called Data Management, DM, NF service (10a).7. The method of any one of embodiments 1 to 5, wherein the Data Set (10b) corresponds to a Subscription Data set.8. The method of any one of embodiments 1 to 7, wherein an SBA service (20) corresponds to an Access and Mobility subscription data management (20a) and its associated one or more Data Subsets (22a,23a,24a,25a) comprises any one of: Access and Mobility Subscription data, Slice Selection Subscription data, UE context in AMF data and AMF registration data.9. The method of any one of embodiments 1 to 8, wherein an SBA service (20) corresponds to a Session subscription data management (20b) and its associated one or more Data Subsets (22b,23b,24b,25b) comprises any one of: SMF Selection Subscription data, UE context in SMF data, Session Management Subscription data and SMF registration data.10. The method of any one of embodiments 1 to 9, wherein an SBA service (20) corresponds to an SMS subscription data management (20c) and its associated one or more Data Subsets (22c,23c,24c) comprises any one of: SMS Management Subscription data, SMS Subscription data and SMSF registration data.11. The method of any one of embodiments 1 to 10, wherein different set of values for the one or more Data Subsets (22a,23a,24a,25a), which are associated with each SBA service (20a), are stored per user or user equipment, UE, basis.12. The method of any one of embodiments 1 to 11, wherein Query, Update, Subscribe, Unsubscribe and Notify operations are defined for each SBA service and usable by the one or more NF service consumer.13. The method of embodiments 11 and 12, wherein each Query, Update, Subscribe, Unsubscribe and Notify operation is usable by the one or more NF service consumer per user or UE basis.14. A Unified Data Repository (60,1), UDR, configured to:split a Data Set (10b), which is provided in the UDR for a plurality of Network Function, NF, service consumers (11), into a plurality of Service Based Architecture, SBA, services (20), wherein each SBA service (20a) is associated with one or more Data Subsets (22a,23a,24a,25a), amongst a plurality of Data Subsets (12) associated with the Data Set (10b), and wherein each SBA service (20a) is provided for one or more NF service consumer (21) amongst the plurality of NF service consumers (11);register, toward a Network Repository Function (2), NRF, via a transmitter (640), identifiers for the plurality of SBA services (20a,20b,20c) handled at the UDR and an identifier of the UDR;receive, from an NF service consumer (3) via receiver (630), a service request for an SBA service (20a); andtransmit, toward the NF service consumer (3) via the transmitter (640), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).15. A Unified Data Repository (60,1), UDR, configured to:store, for a Data Set (10b) provided in the UDR for a plurality of Network Function, NF, service consumers (11), a plurality of Service Based Architecture, SBA, services (20), wherein each SBA service (20a) is associated with one or more Data Subsets (22a,23a,24a,25a), amongst a plurality of Data Subsets (12) associated with the Data Set (10b), and wherein each SBA service (20a) is provided for one or more NF service consumer (21) amongst the plurality of NF service consumers (11);register, toward a Network Repository Function (2), NRF, via a transmitter (640), identifiers for the plurality of SBA services (20a,20b,20c) handled at the UDR and an identifier of the UDR;receive, from an NF service consumer (3) via receiver (630), a service request for an SBA service (20a); andtransmit, toward the NF service consumer (3) via the transmitter (640), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).16. The UDR of any one of embodiments 14 or 15, further configured to perform a method according to any one of embodiments 1 to 13.17. A method for accessing data in a Unified Data Repository (1), UDR, the method carried out at a Network Function, NF, service consumer (70,3,4) node and comprising:transmitting (S-1310), toward a Network Repository Function (2), NRF, a service discovery request with an identifier of a Service Based Architecture, SBA, service (20a);receiving (S-1320), from the NRF (2), an identifier of the UDR (1) instance handling the SBA service (20a);transmitting (S-1330), toward the UDR (1) identified by the identifier of the UDR instance, a service request for the SBA service (20a); andreceiving (S-1340), from the UDR (1), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).18. The method of embodiment 17, further comprising:receiving (S-1410), from a further network node (7,8), an NF service (10a) request for a Data Set (10b) provided in the UDR (1) for a plurality of NF service consumers (11);determining (S-1420), based on the further network node (7,8), an SBA service (20a) for which the service request is transmitted toward the UDR (1); andupon receiving (S-1340), from the UDR (1), the information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a), transmitting (S-1430), toward the further network node (7,8), an NF service (10a) response in accordance with the information data relating to the one or more Data Subsets (22a,23a,24a,25a).19. A Network Function, NF, service consumer (70,3,4) node configured to:transmit, toward a Network Repository Function (2), NRF, via transmitter (740), a service discovery request with an identifier of a Service Based Architecture, SBA, service (20a);receive, from the NRF (2) via receiver (730), an identifier of the UDR (1) instance handling the SBA service (20a);transmit, toward the UDR (1) identified by the identifier of the UDR instance via the transmitter (740), a service request for the SBA service (20a); andreceive, from the UDR (1) via the receiver (730), information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a).20. The NF service consumer (70,4) node of embodiment 19, further configured to:receive, from a further network node (7,8) via the receiver (730), an NF service (10a) request for a Data Set (10b) provided in the UDR (1) for a plurality of NF service consumers (11);determine, based on the further network node (7,8), an SBA service (20a) for which the service request is transmitted toward the UDR (1); andupon receiving (S-1340), from the UDR (1), the information data relating to the one or more Data Subsets (22a,23a,24a,25a) associated with the SBA service (20a), transmit, toward the further network node (7,8) via the transmitter (740), an NF service (10a) response in accordance with the information data relating to the one or more Data Subsets (22a,23a,24a,25a).21. A computer program (614), comprising instructions which, when executed on at least one processor (620), cause the at least one processor to carry out the method according to any one of embodiments 1 to 13.22. A computer program (714), comprising instructions which, when executed on at least one processor (720), cause the at least one processor to carry out the method according to any one of embodiments 17 to 18.23. A computer program product (650,750) comprising the computer program of embodiment 21 and/or 22.