Data restoration for unified data management (UDM) consumers in a unified data repository (UDR) of a mobile network
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-02-06
- Publication Date
- 2026-08-13
Smart Images
Figure EP2026053183_13082026_PF_FP_ABST
Abstract
Description
[0001] Data restoration for Unified Data Management (UDM) consumers in a Unified Data Repository (UDR) of a mobile network
[0002] Technical field
[0003] The present disclosure relates to a method of data restoration in a mobile network. More specifically, the present disclosure relates to a method of data restoration for a first data management consumer in a mobile network, a network node comprising such first data management consumer, an Access and Mobility Management Function (AMF) for use in a mobile network, a method of data restoration for a second data management consumer in a mobile network, a network node comprising such second data management consumer, a Session Management Function (SMF) for use in a mobile network, a method of data restoration in a mobile network, a mobile network, a computer program for executing said methods, and a computer-readable storage medium comprising instructions for executing said methods.
[0004] Background
[0005] During operation of a Public Land Mobile Network (PLMN), it is a common task to have to re-allocate subscriber's data records across subscriber servers / databases, due to multiple reasons such as, e.g., network re-dimensioning I scaling-out, replacement I swap of legacy databases (e.g., 4G User Data Convergence (UDC) systems), and etcetera.
[0006] In those scenarios the subscription data is moved from origin to target database system including both provisioned static data (user profiles) and temporary data (context data), which is to be available for traffic in the new database as soon as possible to avoid disturbances in the end user experience and network services. Additionally, network traffic is to be properly moved to the target systems database handling the new subscriptions, i.e., Unified Data Repository (UDR) affecting in many cases the traffic from 5G Core (5GC) to database front-ends, i.e., Unified Data Management (UDM) / Policy Control Function (PCF).The procedures followed to enable this network deployment change (subscriber reallocation) may be referred to as data migration service which may include both recovery of temporary data and traffic switch.
[0007] In order to support the migration of subscriber data and the users’ traffic steering to, e.g., a new UDC system (e.g., Home Subscriber Server - Front End (HSS-FE) I UDR), in previous network architectures the subscriber server (Home Location Register (HLR) in 2G / 3G, HSS in 4G) could rely on sending a "reset" command to the access nodes, to inform that the dynamic data for users migrated needs to be restored.
[0008] This was widely used since users were extracted from the old database and reprovisioning was performed in the new database. Permanent subscription data was then restored, but dynamic data (e.g. context data) was not migrated and the migration process was relying on the existing Evolved Packet Core (EPC) reset mechanism in order to speed up the process of restoring consistency between the serving nodes and the database, so that serving nodes (e.g., Mobility Management Entity (MME)) were in charge of that.
[0009] Traffic steering related to the affected users was then performed by Subscription Locator Function (SLF) I Diameter Routing Agent (DRA) via proper configuration of the routing tables.
[0010] There is a similar procedure that can be used in 5GC to trigger restoration of the temporary data from UDM consumers to target UDM / UDR using UDR restoration procedures. It should be noted that these restoration procedures were originally meant to be triggered upon a potential data-loss event at UDR, but they are equally applicable to other scenarios where a similar reaction is expected by the Network Functions (NFs) receiving a restoration notification (i.e., to restore dynamic data at the UDR).
[0011] In the 5GC, in addition to AMF (which performs similar functions as MME in EPC), there are more NFs storing context data (e.g., registration data, or subscriptions to events) in UDM / UDR, e.g., SMF, Short Message Service Function (SMSF), Network Exposure Function (NEF) and AKMA Anchor Function (AANF), increasing the risk that temporary data is not restored in a consistent manner.
[0012] Additionally, 5GC provides a specific mechanism for traffic routing based in Network Repository Function (NRF) functions. When subscription data is distributed in different databases in the PLMN, there are some NF profile specific parameters providing information used for traffic routing, such as: UDR groupld, UDM groupld andPCF group Id. Each of these identities are mapped to specific set of users based on Subscription Permanent Identifier (SUPI) series or Generic Public Subscription Identifier (GPSI) series. The mapping between NF groupld and corresponding user id can be managed in different ways: a) Configured in the corresponding NF profile; b) configured in the NRF; c) provisioned in UDR and retrieved by NRF. In case a), the mapping is also available in NF profile updates, i.e., when NF profile is changed by UDR, UDM or PCF. However, in cases b) and c) the mapping is only available upon specific user discovery, but it is not updated in the consumers since the information is not stored in the user profile.
[0013] Therefore, UDR consumers (UDM and PCF) and UDM / PCF consumers discover the relation between a user identity and a given NF groupld during NF discovery, in which case, especially for stateful NFs, the consumers can store this information as part of internal User Equipment (UE) context, to be used in the next NF interactions. In the case of AMF, this information is distributed towards other UDM / PCF consumers such as AMF, SMF and SMSF upon UE context transfer, Protocol Data Unit (PDU) session establishment or SMSF registration.
[0014] When there is a change in the mapping between a given user and NF groupld, UDR / UDM / PCF consumers storing NF group Id information stored in the UE context may not be able to detect this change, leading to wrong UDR / UDM / PCF may be contacted if they use an obsolete NF Groupld to find UDR / UDM / PCF.
[0015] This affects restoration traffic, i.e., it is not always guaranteed that restoration traffic will reach the target UDM / UDR, since they are usually based on the stored Groupld of the UDM (as part of UE context), so they may attempt to restore the context / dynamic data by reusing the stored Groupld which is still pointing to the origin system in case of UDM reallocation.
[0016] Summary
[0017] A summary of aspects of certain examples disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects and / or a combination of aspects that may not be set forth.The present disclosure aims to overcome the drawbacks identified in the background section. In particular, the solution of the present disclosure enables reliable data restoration in a mobile core network, such as for data migration procedures in a 5GC network, by presenting improvements to the current UDR restoration procedures.
[0018] According to an aspect of the present disclosure, a method of data restoration for a first data management consumer in a mobile network is presented. The method may include receiving, in the first data management consumer, a notification that a data restoration is to be performed for a UE, resulting in the UE being marked for data restoration with the first data management consumer . The method may further include checking, in the first data management consumer, if the UE is marked for data restoration before performing the data restoration. If the UE is marked for data restoration, the method may continue with the following steps. The method may include performing, in the first data management consumer, the data restoration for the UE, resulting in storing of new UE data for the first data management consumer in a data repository. The method may further include sending, from the first data management consumer, an indication to a second data management consumer, the indication comprising data indicating that the data restoration is performed or is going to be performed for the first data management consumer. The indication may be sent from the first data management consumer to the second data management consumer to trigger the second management consumer to check if the UE is marked for data restoration with the second data management consumer.
[0019] In an embodiment, the new UE data for the first data management consumer may be stored in the data repository via an intermediary re-creation or synchronization of data to a data management function.
[0020] In an embodiment, the data repository may be a UDR. The data management function may be a UDM data-base front-end. The first data management consumer may be one of: an AMF; an SMF; an SMSF; or an NEF.
[0021] In an embodiment, the first data management consumer may be the AMF. The new data for the AMF stored in the UDR may include AMF context data for the UE.
[0022] According to an aspect of the present disclosure, a network node including a first data management consumer is presented. The first data management consumer maybe configured to perform the above-described method of data restoration for a first data management consumer in a mobile network.
[0023] According to an aspect of the present disclosure, an AMF for use in a mobile network is presented. The AMF may be a first data management consumer that is configured to perform the above-described method of data restoration for a first data management consumer in a mobile network.
[0024] According to an aspect of the present disclosure, a method of data restoration for a second data management consumer in a mobile network is presented. The method may include receiving, in the second data management consumer, a notification that a data restoration is to be performed for a UE, resulting in the UE being marked for data restoration with the second data management consumer. The method may further include receiving, in the second data management consumer from a first data management consumer, an indication comprising data indicating that data restoration is performed or is going to be performed for the first data management consumer. The method may further include checking, in the second data management consumer, if the UE is marked for data restoration before performing. If the UE is marked for data restoration, the method may continue with the following steps. The method may further include performing, in the second data management consumer, the data restoration for the UE, resulting in storing of new UE data for the second data management consumer in a data repository.
[0025] In an embodiment, the new UE data for the second data management consumer may be stored in the data repository via an intermediary re-creation or synchronization of data to a data management function.
[0026] In an embodiment, the data repository may be a UDR. The data management function may be a UDM data-base front-end. The second data management consumer may be one of: an AMF; an SMF; an SMSF; or an NEF.
[0027] In an embodiment, the second data management consumer may be the SMF. The new data for the SMF stored in the UDR may include SMF context data for the UE.
[0028] According to an aspect of the present disclosure, a network node including a second data management consumer is presented. The second data management consumer may be configured to perform the above-described method of data restoration for a second data management consumer in a mobile network.According to an aspect of the present disclosure, an SMF for use in a mobile network is presented. The SMF may be a second data management consumer configured to perform the above-described method of data restoration for a second data management consumer in a mobile network.
[0029] According to an aspect of the present disclosure, a method of data restoration in a mobile network is presented. The mobile network may include a data repository, a data management function and at least two data management consumers of the data management function. The method may include receiving, in a first data management consumer of the at least two data management consumers, a notification that a first data restoration is to be performed for a UE, resulting in the UE being marked for data restoration with the first data management consumer. The method may further include receiving, in a second data management consumer of the at least two data management consumers, a notification that a second data restoration is to be performed for the UE resulting in the UE being marked for data restoration with the second data management consumer. The method may further include checking, in the first data management consumer, if the UE is marked for the first data restoration before performing the first data restoration. If the UE is marked for the first data restoration, the method may continue with the following steps. The method may further include performing, in the first data management consumer, the first data restoration for the UE, resulting in storing of new UE data for the first data management consumer in a data repository. The method may further include sending, from the first data management consumer, an indication to a second data management consumer, the indication comprising data indicating that the first data restoration is performed or is going to be performed for the first data management consumer, the indication triggering the second management consumer to check if the UE is marked for data restoration with the second data management consumer. The method may further include checking, in the second data management consumer, if the UE is marked for the second data restoration before performing the second data restoration. If the UE is marked for the second data restoration, the method may continue with the following steps. The method may further include performing, in the second data management consumer, the second data restoration for the UE, resulting in storing of new UE data for the second data management consumer in a data repository.In an embodiment, the new UE data for the first data management consumer and the new UE data for the second data management consumer may be stored in the data repository via an intermediary re-creation or synchronization of data to the data management function.
[0030] In an embodiment, data repository may be a UDR. The data management function may be a UDM data-base front-end. The data management consumers may include at least two of: an AMF; an SMF; an SMSF; and an NEF.
[0031] In an embodiment, the first data management consumer may be the AMF and the second data management consumer may be the SMF.
[0032] In an embodiment, the new data for the AMF stored in the UDR may include AMF context data for the UE, and the new data for the SMF stored in the UDR may include context data for the UE.
[0033] In an embodiment, the mobile network may be a 5GC network.
[0034] According to an aspect of the present disclosure, a mobile network is presented, which mobile network is arranged to perform any one of the above-described methods.
[0035] According to an aspect of the present disclosure, a computer program is presented that includes instruction which, when the program is executed by one or more processors, cause the one or more processors to carry out any one of the abovedescribed methods.
[0036] According to an aspect of the present disclosure, a computer-readable storage medium is presented that includes instructions which, when executed by one or more processors, cause the one or more processors to carry out any one of the abovedescribed methods.
[0037] Brief description of the Drawings
[0038] Embodiments of the present disclosure will now be described, byway of example only, with reference to the accompanying schematic drawings in which corresponding reference symbol indicate corresponding parts, in which:
[0039] Fig. 1 shows a 5G System Architecture of a mobile network, according to an aspect of the present disclosure;
[0040] Fig. 2 shows a UDR of a 5G System Architecture as may be used in embodiments of the present disclosure;Fig. 3 shows a time-sequence diagrams of a known UDR-related data restoration process;
[0041] Fig. 4 shows another time-sequence diagrams of a known UDR-related data restoration process;
[0042] Fig. 5 shows a time-sequence diagram of an improved UDR-related restoration processes, according to an aspect of the present disclosure;
[0043] Fig. 6 shows another time-sequence diagram of an improved UDR-related restoration processes, according to an aspect of the present disclosure;
[0044] Fig. 7 shows an example embodiment of a method of data restoration for a first data management consumer in a mobile network, according to an aspect of the present disclosure;
[0045] Fig. 8 shows an example embodiment of a method of data restoration for a second data management consumer in a mobile network, according to an aspect of the present disclosure;
[0046] Fig. 9A shows an example embodiment of a method of data restoration in a mobile network, according to an aspect of the present disclosure;
[0047] Fig. 9B is a continuation of the method of Fig. 9A; and
[0048] Fig. 10 shows an example embodiment of a computing system for implementing certain aspects of the present technology.
[0049] The figures are intended for illustrative purposes only, and do not serve as restriction of the scope of the protection as laid down by the claims.
[0050] Detailed description
[0051] It will be readily understood that the components of the embodiments as generally described herein and illustrated in the appended figures could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of various embodiments, as represented in the figures, is not intended to limit the scope of the present disclosure but is merely representative of various embodiments. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the present disclosure is, therefore, indicated by the appended claims rather than by this detailed description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
[0052] Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single example of the present disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Thus, discussions of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same example.
[0053] Furthermore, the described features, advantages, and characteristics of the present disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize, in light of the description herein, that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present disclosure. Reference throughout this specification to "one embodiment", "an embodiment", or similar language means that a particular feature, structure, or characteristic described in connection with the indicated embodiment is included in at least one embodiment of the present disclosure. Thus, the phrases "in one embodiment”, "in an embodiment", and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0054] In the following examples, reference is made to a 3GPP 5G System Architecture, i.e., the system architecture of a 5G mobile network. The solution of the present disclosure if not limited to such 5G System Architecture and may be applied to other mobile networks that are based on similar or evolved system architectures. The solution of the present disclosure may advantageously be used to improve existing 3GPP 5G System Architectures.The present disclosure presents improvements to the UDR restoration procedures in a mobile core network, such as a 5GC network. Fig. 1 shows a nonlimiting example of a 5G System Architecture 100 including such 5GC network, in this example that of a non-roaming 5G System Architecture in accordance with the 3GPP Standard. The 5G System Architecture 100 typically includes one or more of the following NFs (not all are shown in Fig. 1): an authentication Server Function (AUSF); an AMF, i.e., an example of a UDM consumer 122,124; a Data Network (DN), e.g. operator services, Internet access or 3rd party services; an Unstructured Data Storage Function (UDSF); a NEF; a NRF 130; a Network Slice Admission Control Function (NSACF); a Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF); a Network Slice Selection Function (NSSF); a PCF; a SMF, i.e., another example of a UDM consumer 122,124; a UDM 120; a UDR 110; a User Plane Function (UPF); a UE radio Capability Management Function (UCMF); an Application Function (AF); User Equipment (UE); a (Radio) Access Network ((R)AN); a 5G-Equipment Identity Register (5G-EIR); a Network Data Analytics Function (NWDAF); a Charging Function (CHF); a Time Sensitive Networking AF (TSN AF); a Time Sensitive Communication and Time Synchronization Function (TSCTSF); a Data Collection Coordination Function (DCCF); a Analytics Data Repository Function (ADRF); a Messaging Framework Adaptor Function (MFAF); a Non-Seamless WLAN Offload Function (NSWOF); an Edge Application Server Discovery Function (EASDF). The 5G System Architecture 100 may further include one or more of the following network entities: a Service Communication Proxy (SCP); a Security Edge Protection Proxy (SEPP).
[0055] Also shown in Fig. 1 are the interface identifiers as used in the 3GPP Standard for referring to the various interfaces of NFs and network entities. For example, Nudr, Nudm, Nnrf, Namf and Nsmf are service-based interfaces exhibited by UDR 110, UDM 120, NRF 130, AMF 122, 124 and SMF 122, 124, respectively. Reference points between NFs are depicted in Fig. 1 as N1, N2, N3, N4, N6 and N9.
[0056] With reference to Fig. 2, the 5G System Architecture 100 allows NFs, such as the UDM 120, PCF and NEF, to store data 112 in the UDR 110. Such data 112 may include subscription data and policy data by UDM 120 and PCF, structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs) by the NEF. There maybe multiple UDRs 110 deployed in the network, each of which may accommodate different data sets or subsets (e.g. subscription data, subscription policy data, data for exposure, application data) and / or serve different sets of NFs. Deployments where a UDR 110 serves a single NF and stores its data and, thus, can be integrated with this NF, are possible.
[0057] The Nudr interface is defined for the network functions (i.e., NF Service Consumers), such as UDM 120, PCF and NEF, to access a particular set of the data 112 stored and to read, update (including add, modify), delete and subscribe to notification of relevant data changes in the UDR 110. For example, the UDM 120 may store and retrieve Subscription Data from the UDM 110. The following data in the UDR 110 sets are typically exposed via Nudr to the respective NF service consumer and stored in the date 112: Subscription Data; Policy Data; Structured Data for exposure; Application data: PFDs for application detection and AF request information for multiple UEs.
[0058] Within the 5G Core Network, the UDM 120 may offer services to one or more of the AMF 122, 124, SMF 122, 124, SMSF, NEF, Gateway Mobile Location Centre (GMLC), NWDAF, AUSF, Home Subscriber Server (HSS), Generic Bootstrapping Architecture’s Binding Support Function (GBA's BSF), Short Message Service -Gateway Mobile Switching Center (SMS-GMSC), Data Collection Coordination Function (DCCF), 5G Direct Discovery Name Management Function (5G DDNMF), PCI Anonymization Function (PAnF), Location Management Function (LMF) and / or 5G ProSe Key Management Function (5G PKMF) via the Nudm service-based interface.
[0059] The UDM 120 may include support for one or more of the following functionalities: generation of 3GPP AKA Authentication Credentials; User Identification Handling (e.g. storage and management of SUPI for each subscriber in the 5G system); support of de-concealment of privacy-protected subscription identifier (SUCI); Access authorization based on subscription data (e.g. roaming restrictions); UE's Serving NF Registration Management (e.g. storing serving AMF for UE, storing serving SMF for UE's PDU Session); support to service / session continuity e.g. by keeping SMF / Data Network Name (DNN) assignment of ongoing sessions; Mobile-Terminated Short Message Service (MT-SMS) delivery support; Lawful Intercept (LI) Functionality (especially in outbound roaming case where UDM 120 is the only point of contact for LI); subscription management; SMS management; 5G-Virtual Network (VN) groupmanagement handling; support of external parameter provisioning (expected UE behavior parameters or Network Configuration parameters); support for the Disaster Roaming; support for the control of time synchronization service based on subscription data.
[0060] To provide this functionality, the UDM 120 may use subscription data (including authentication data) that may be stored in UDR 110, in which case a UDM 120 may implement the application logic and does not require an internal user data storage and then several different UDMs may serve the same user in different transactions.
[0061] The AMF is an example of a UDM consumer 122, 124. The AMF 122, 124 manages UE registration, mobility, authentication and security. It ensures that devices can access the network securely and maintain seamless communication as they move between different cells or access points. Key functions of the AMF 122, 124 may include one or more of: Registration Management of UEs to the 5G network; Mobility Management of UEs; UE Authentication and Security; Session Management (basic support in addition to the SMF); interworking with Non-3GPP Access Networks, such as Wi-Fi or fixed broadband networks; Paging and Reachability of UEs; interfacing with other NFs.
[0062] The SMF is another example of a UDM consumer 122, 124. The SMF 122, 124 handles the lifecycle of user data sessions, including bearer management, traffic routing, and Quality of Service (QoS). It works in close coordination with other core network functions to ensure that user data is transmitted efficiently and securely across the 5G network. Key functions of the SMF 122, 124 may include one or more of: Session Establishment; modification and release of user plane sessions.
[0063] The NRF 130 serves as a central repository and discovery function that facilitates the registration, discovery, and communication between various NFs. It ensures that network functions can find each other, scale efficiently, and maintain high availability and redundancy. Its primary role is to register and store the profiles of various NFs and to enable the discovery of these functions for inter-NF communication. Key functions of the NRF 130 may include one or more of: NF Registration, allowing NFs, such as AMF 122, 124, SMF 122, 124 and PCF, to register their capabilities and other relevant information with the NRF when they come online or after a restart; NF Discovery; Load Balancing and Redundancy control; Service Discovery andManagement; interfacing with other core functions, such as AMF, SMF, PCF, UPF, AUSF.
[0064] In the context of the UDR 110, data restoration functionality provides the means when the UDR 110 has lost data, to inform UDR consumers and / or UDM consumers 122, 124 about the need to re-create data in the UDR 110 where the data was lost. Once the UDM 120 is informed by the UDR 110 about this data loss, the UDM 120 may do the same to its own consumers 122, 124 (e.g., AMF, SMF, SMSF, and / or any other UDM consumer 122, 124), by sending a notification. According to the 3GPP Standard, this notification is sent towards a Default Subscription Notification (in 3GPP: DATA_RESTORATION_NOTIFICATION) that is part of the UDM consumer 122, 124 (e.g., AMF) profile in NRF 130. This Subscription may include a reference (in 3GPP: CallbackURI) where the Notification may be received. Therefore, according to the 3GPP Standard, when the UDR 110 informs about data loss or trigger by command for subscription data migration, the UDM 120 may send the DATA_RESTORATION_NOTIFICATION to the UDM consumer 122, 214 referenced by CallbackURI as included in the UDM consumer NRF profile. The UDM consumers 122, 124, once the Restoration Notification is received, may perform the Restoration process. Particularly, when re-synchronization is required, the UDM consumers 122, 124 may start procedures to re-create the indicated data in the UDM 120 (e.g., according to the 3GPP Standard, AMF and SMF may perform Nudm_UECM_Registration and Nudm_SDM_Get respectively for each UE that needs restoration.
[0065] A time-sequence diagram of a known data restoration process in a 5G Core Network in accordance with the 3GPP Standard is shown in Fig. 3. In step 0, UDR consumers and UDM consumers define callbackUri for data restoration in the NF profile registered in NRF. In step 1 , UDR consumers store temporary data in UDR. The UDR consumers may set its identity in the request to UDR, when accessing it for the first time. The UDR stores the received identity and creates for the UDR consumer a subscription on notification for the potential UDR data inconsistency. The UDR may provide to the UDR consumer the Reset-ID if assigned by the UDR for the temporary data stored in UDR. The UDM stores temporary data in UDR as requested by its consumers. UDM consumers may set dataRestorationCallbackUri in the request of their registration to UDM. In this case, the UDM stores the dataRestorationCallbackUrilocally and creates for the UDM consumer a subscription on notification for the potential UDR data inconsistency. If received from UDR, the UDM also provides the Reset-ID assigned by the UDR to UDM consumers. When an NF other than UDM creates or updates a resource directly or via UDM in UDR, the NF sets or stores lastSynchronizationTime in a relevant profile. If the NF receives a Reset-ID directly or via UDM from UDR, the NF stores it in the profile. In step 2, UDR detects corruption, loss, or inconsistency in temporary data caused due to certain scenarios (e.g. failure and restart of the UDR, or migration of the data from an old UDR to a new UDR). In step 3, UDR queries NRF based on the identity stored in step 1 and discovers callbackUri for data restoration in UDR consumers' NF profiles. If no UDR consumer impacted by the restoration event provided its identity in step 1 , the UDR discovers via NRF the callbackUri of one suitable UDR consumer instance to send the notification to. The UDR sends Nudr_DR_Notification request to the callbackUri to notify potential UDR data inconsistency. The Nudr_DR_Notification request may contain temporary data identifier(s) (e.g. Reset-IDs) and an impacted period (i.e. lastReplicationTime and recoveryTime). In step 4, if UDR consumer is UDM, the UDM forwards the notification to UDM consumers. The UDM finds callbackUri for data restoration for UDM consumers within its PLMN in UDM consumers' NF profiles through querying NRF. Optionally, the UDM may find callbackUri for data restoration for UDM consumers (especially UDM consumers outside its PLMN) if provided by the UDM consumer during UDM consumer registration in UDM and locally stored in UDM in step 1. In step 5, when a UDR consumer other than UDM (e.g. PCF, NEF) or a UDM consumer (e.g. AMF, SMF, SMSF) finds that a stored profile is affected by the potential loss or corruption of data, and that the last synchronization time of the profile falls into the impacted period in the notification, then the NF judges that the profile requires resynchronization. In step 6, the UDR consumers and UDM consumers locally adjusts invocation timing of each of those procedures, in order not to cause congestion in the system. The NF invokes necessary procedures. If the data to be restored was requested for an individual UE, the UDM consumers and UDR consumers should invoke the procedure immediately. UDM consumers select a UDM instance to send the re-synchronization signaling. This is, the UDM consumer may not send the resynchronization signaling to the UDM instance from which the UDM consumer received the notification. In step 7, if UDM receives Nudm_UECM_Registrationrequest containing the "udrRestartlnd" flag, the UDM overwrites the related profile in the UDR, or creates it if not available. If the registration request includes a lastSynchronizationTime, the related profile in UDR is overwritten only if the lastsynchronization time received from the UDM consumer is not older than the registration time stored in UDR before resynchronization. In this case, if the UDM replaces or creates the related profile in UDR, the UDM sets the registration time to the current time. If UDM receives Nudm_SDM_Subscribe request containing the "udrRestartlnd" flag the UDM sends a corresponding request to UDR, the UDR overwrites the related profile in the UDR or creates it if not available in UDR. If UDM receives Nudm_UEAuthentication_ResultConfirmation request containing the "udrRestartlnd" flag, the UDM sends a corresponding request to UDR, the UDR overwrites the related profile in the UDR or creates it if not available in UDR. If UDM receives Nudm_EE_ModifySubscription request containing the "udrRestartlnd" flag, the UDM sends a corresponding request to UDR, the UDR overwrites the related profile in the UDR or creates it if not available in UDR.
[0066] Fig. 4 shows another time-sequence diagram of a known data restoration process in a 5G Core Network in accordance with the 3GPP Standard, wherein the UDM and two UDM consumers, in this example AMF and SMF, are shown in more detail. In the example of Fig. 4, no UDR consumers are shown, although these may be included in the data restoration process as well.
[0067] In the time-sequence diagram of Fig. 4, there is a precondition that the AMF and SMF (as UDM consumers) have registered its NF profile in the NRF, including a Default Subscription for the Data Restoration Notification. Note that Fig. 4 covers the case of AMF and SMF as UDM consumers, but it may generically be applied to any UDM consumer that may need to re-synchronize data to the UDM / UDR, e.g. SMSF, NEF, etcetera. In step 1, the UDM is informed about the need to re-create data. This could be as a result of data loss by the UDR (then the UDR would have informed UDM with the Data Restoration Notification), or the trigger could be an O&M command to the UDM directly due to subscription data migration. The UDM is informed about the SUPI range (individual UE, short list of UEs, all UEs, anyUE) that are affected by the restoration process. Furthermore, for the identified problem the UDM is informed that re-synchronization is to be performed. In step 2, the UDM identifies the endpoint to where the Data Restoration Notification is to be sent, to inform the UDM consumers(AMF and SMF) that re-synchronization is required. This endpoint (dataRestorationCallbackUri) is provided as part of the Default Subscription configured in the UDM consumer NRF profile. Therefore, the UDM may get this information from the NRF. In steps 3a and 3b, the UDM sends the Data Restoration Notif to the dataRestorationCallbackUri for the UDM consumers. In steps 4a and 4b, the UDM consumers then perform data re-synchronization for the UEs indicated in the Data Restoration Notif received. Then, they mark all those UEs as “to be restored”. In step 5, after some time, there may be UE activity for a UE1 (e.g., for the AMF it may occur as well that the periodic Tracking Area Unit (TAU) -timer is expired, what is an indirect indication of required UE activity). In step 6, the AMF UDM consumer checks if the UE1 is marked as “to be restored”. If so, following steps apply. In step 7, the AMF UDM consumer performs re-creation I re-synchronization of data to the UDM (e.g., AMF sends Nudm_UECM_Registration and Nudm_SDM_Registration for the UE1). In step 8, the UDM as a result of the re-creation requests from a UDM consumer, stores new UE1 data in the UDR, achieving UE1 data re-creation for the AMF context (in this example as UDM consumer).
[0068] Disadvantageously, the known data restoration process as shown in Fig. 3 and Fig. 4 may result in the UDR data, e.g., UE context, to be only partially restored. Le., the UE context of one UDM consumer may be restored while the UE context of another UDM consumer is not restored. For example, AMF context (as per steps 7, 8 in Fig. 4) may be re-created, while other UE contexts may take very long to be re-created (e.g., that of SMF, SMSF). Consider that some UDM consumers may not receive UE activity for very long time, like SMSF, or even SMF, therefore the partly re-creation may last a long time, potentially causing unexpected behavior in the network.
[0069] It is observed that the way data restoration was done in 4G was different, since the UE context was migrated at once (since it was owned by the Mobile Management Entity (MME) as a whole). With the separation of Session Management from the Access and Mobility Management in 5G, as well from SMS management, there are at least three NFs involved (AMF, SMF, SMSF) for the basic UE context, compared to just one MME in 4G. In 4G migration, considering migration for the UE was at once, then the operators count on that (e.g., counters to measure the migration rate with a single update in 4G UDR; for a successful migration the UE context in the UDR shall be complete), but in 5G this is changed (e.g., there are signaling from different NFs torestore the same UE; the UE context may be partly restored in the UDR and this is not an indication of an erroneous migration; and etcetera). The problem of the UE context not being restored for multiple UDM consumers was therefore not considered when defining the 5G Standard.
[0070] The following example scenario illustrates a potential problem with the known UDR related data restoration process. In this scenario there is SMF context (e.g., PDU sessions) recreated for a UE1 while AMF context (e.g., access and mobility context) is not recreated. The UE1 may switch off at some point in time, e.g., at night (or even during the maintenance window). Does this deregistration work fine when there is not a context in UDR to be deleted? May it happen that deregistration fails? The answer to these questions is uncertain and there can be occasions where the context of one of the UDM consumers, e.g., AMF, is not recreated.
[0071] In another example scenario, there is UE handover from Wi-Fi to 5G access. The SMF needs to perform the resynchronization (i.e., re-registration to UDM so that the AMF selects the right SMF after the handover to 5G). But if the AMF context is not restored, then the handover would fail.
[0072] In another example scenario, there is an event subscription that may work, but if the App does not receive anything when the UE moves from AMF, then the AMF context can’t be recovered.
[0073] The present disclosure presents a solution to the above-identified problems and ensures that UDR-related data 112 is restored for all UDM consumers 122, 124 in at least all of the above-described example scenarios.
[0074] The solution of the present disclosure includes a first UDM consumer performing a resynchronization or re-creation of data for a UE in response to a Data Restoration Request from an UDR, the first UDM consumer then informing a second UDM consumer that it performed or is going to perform the resynchronization / re-creation of the data, which triggers the second UDM consumer to check if the UE is marked for data restoration with the second UDM consumer, and if so, also perform a resynchronization / re-creation of the data for the UE In an embodiment, the first UDM consumer is an AMF and the second UDM consumer is a SMF.
[0075] Fig. 5 shows a time-sequence diagram of an improved data restoration process of an embodiment of the present disclosure, in this example for use in a 5G Core Network. Steps 1-8 shown in Fig. 5 may be the same as steps 1-8 shown in Fig. 4.In step 9 of Fig. 5, the AMF, i.e., one of the UDM consumers 122, 124, may send an indication to the SMF, i.e., another one of the UDM consumers 122, 124, that AMF context data for UE1 is resynched. This indication may be included in an existing PDU Session Update.
[0076] In step 10 of Fig. 5, the SMF may check if the UE1 is marked as “to be restored”. If so, following steps apply.
[0077] In step 11 of Fig. 5, the SMF may perform re-creation I re-synchronization of data to the UDM 120. For example, SMF may send Nudm_UECM_Registration and Nudm_SDM_Registration for the UE1.
[0078] In step 12 of Fig. 5, the UDM 120, as a result of the re-creation requests from the SMF, may store new UE1 data in the UDR 110, achieving UE1 data re-creation for the SMF context.
[0079] Advantageously, both AMF and SMF contexts are thus re-created.
[0080] Fig. 5 covers a case where resynchronization occurs at the AMF before the SMF, for example because the AMF receives UE activity / expiration of timers before the SMF. This is the most common case since the UE activity is normally quite frequent in the AMF, and the AMF includes UE activity timers that may expire triggering the resynchronization. However, it is possible that the resynchronization may occur at the SMF before the AMF, for example in case of a UE handover from Wi-Fi to 5G access. The SMF then performs the resynchronization first, in this example re-registration to UDM 120 so that the AMF selects the right SMF after the handover from Wi-Fi to 5G. The solution of the present disclosure may be applied with the SMF and AMF performing the data restoration in the other order, resulting in an indication, such as “smfResynched”, from the SMF to the AMF in step 9, mimicking what is being described in Fig. 5.
[0081] Generally, any UDM consumer may be triggered to perform a data restoration process, followed by this UDM consumer sending an indication to another UDM consumer that a data restoration is or is going to be performed triggering the other UDM consumer check if the UE is marked for data restoration and, if so, to also perform a data restoration process. This has been illustrated in Fig. 6, which shows a method 1000 presented as a time-sequence diagram.
[0082] In the embodiment of Fig. 6, a first UDM consumer 122 and a second UDM consumer 124 receive 1002, 1004 a notification that a data restoration is to beperformed for one or more UEs. Hereto, e.g., a UDM 120 may send a Data Restoration Notif to the dataRestorationCallbackUri obtained from the NRF 130, as explained in steps 3a and 3b of Fig. 4. The first UDM consumer 122 and the second UDM consumer mark all those UEs as “to be restored”.
[0083] After some time, there may be UE activity for a particular UE (herein also referred to as UE1) (e.g., for the AMF it may occur as well that the periodic Tracking Area Unit (TAU) -timer is expired, what is an indirect indication of required UE activity). The first UDM consumer 122 then checks in step 1006 if the particular UE is marked as “to be restored”. If so, following steps 1010 (including steps 1012 and 1014) apply.
[0084] In step 1012, the first UDM consumer 122 performs a data restoration, e.g., by re-creation / re-synchronization of data to the UDM 120. In step 1014, the UDM 120, as a result of the re-creation requests from the first UDM consumer 122, stores new UE data in the UDR 110, achieving UE data re-creation for the context of first UDM consumer 122.
[0085] In step 1020, the first UDM consumer 122 sends an indication (typically in the form of some binary data) to the second UDM consumer 124 that data restoration for the particular UE is performed is going to be performed, e.g., by resynching context data for the particular UE with the first UDM consumer 122. The indication may be included in an existing PDU Session Update.
[0086] In step 1022, the second UDM consumer 124 checks if the particular UE is marked as “to be restored”. If so, following steps 1030 (including steps 1032 and 1034) apply.
[0087] In step 1032, the second UDM consumer 124 performs a data restoration, e.g., by re-creation I re-synchronization of data to the UDM 120. In step 1034, the UDM 120, as a result of the re-creation requests from the second UDM consumer 124, stores new UE data in the UDR 110, achieving UE data re-creation for the context of the second UDM consumer 124.
[0088] In the embodiment of Fig. 6, two UDM consumers are shown, but there may be more than two UDM consumers involved in the data restoration process. The process of step 1010 may be repeated for any number of UDM consumers. Non-limiting examples of UDM consumers are AMF, SMF, SMSF and NEF.
[0089] The solution of the present disclosure may advantageously be applied to the 3GPP Standard, and in particularto 3GPP TS 29.502 and 3GPP TS 23.527, to improvethe 3GPP Standard. In the following, example embodiments of improvements to the 3GPP Standard are presented that may be implemented to improve UDR restoration procedures.
[0090] In a first improvement, updates to the Restoration Notification mechanism may be implemented to inform the receiving node whether a new discovery is needed due to NF Group Id - user id mapping is changed for a given user or set of users identified in the restoration notification. In case UDR group Id - user identity mapping has been changed, UDR consumers, e.g., UDM 120, PCF or NEF supporting this feature, are informed. UDR consumers use this information to discard previous routing information stored, if any, before the next UDM / PFC interaction and use user id to discover UDR serving an affected user, either using mapping information if that is available in updated UDR NF profile (UDR info), or by sending a new discovery request to NRF to get latest UDR information. In case UDM group Id - user identity mapping has been changed, UDM consumers 122, 124, e.g., AMF, SMF, SMSF, NEF supporting this feature, are informed. UDM consumers 122, 124 use this information to discard previous routing information stored, if any, before the next UDM / PFC interaction and use user id to discover UDR serving an affected user, either using mapping information if that is available in updated UDM NF profile (UDM info), or by sending a new discovery request to NRF and getting latest UDM selection information. AMF may additionally update UDM group Id information in other NFs in case that information is changed in the UE context as a result of UDM selection.
[0091] In a second improvement, updates to the Restoration Notification mechanism may be implemented to ensure temporary data is restored in a given time minimizing service impact. UDM / PCF consumers supporting UDR restoration with Time Based restoration restore the context data for all the indicated users in a given period of time which may be indicated in the UDR restoration notification. Default value can be configured by the customer. Still, restoration shall be done in a way that does not compromise the traffic characteristics. UDM / PCF consumers may perform immediate restoration of context data whenever UDR restoration notification affects one single user.
[0092] In a third improvement, updates to the Restoration Notification mechanism may be implemented, specifically using AMF as main trigger point of restoration towards other NFs under AMF control, to assure temporary data is restored at the same timeas in AMF for those NFs, therefore assuring data is consistently and minimizing risk of temporary data not restored in those NFs receiving low user interactions, e.g. SMSF. When AMF initiates restoration of context data for a given user, and determines this user has active context in other NF (e.g., SMF, SMSF), AMF may send a UDR restoration order to that NF.
[0093] Note that the above-described first, second and third improvement may be combined in any combination.
[0094] If the SMF receives an indication from the UDM to perform Data Restoration for a SUPI range based on UE activity, it may take long time until the SMF receives such UE activity. In addition, the resynchronization of subscription data should be performed for the same UE as close in time as possible. For example, for the same UE if AMF registration data is resynchronized, but SMF registration data is not, during the interim time it takes to get whole UE data resynchronized, unexpected behavior may occur.
[0095] To avoid this unexpected behavior, in an embodiment, when the AMF performs resynchronization 1012, 1014 for a UE (either based on UE activity or time-based), the AMF may provide 1020 an indication to the SMF, so to allow that if this UE was expected to be resynchronized (as a result of the reception of the Data Restoration notification directly from the UDM), the SMF performs 1030 this UE resynchronization at that moment.
[0096] More specifically, if the SMF receives an indication from the UDM 120 to perform Data Restoration based on UE activity, it may take long time until the SMF receives such UE activity and therefore the SMF context may not be restored for a long time. On the contrary, the UE activity at the AMF is normally more frequent and in addition the AMF counts with the periodic TAU timers that would expire in a limited amount of time. Therefore, when the UDM 120 sends the Data Restoration Notification to both AMF and SMF, the AMF may synchronize its corresponding subscription data based on UE activity quite soon while the SMF may not receive any UE activity for a much longer time, and then the UE is partly resynchronized. Therefore, once the AMF has initiated resynchronization for a UE, in this embodiment the AMF may provide 1020 an indication to the SMF(s) with established PDU Session(s), so to allow that if this UE was expected to be resynchronized (as a result of the reception of the Data Restoration notification to perform resynchronization directly from the UDM), the SMF performs this UE resynchronization at that moment.In an embodiment the indication provided by the AMF in step 1020 may be in the form of a POST request containing an amfResynchedlnd for the affected UE. The SMF may check 1022 if for the received UE there is a Data Restoration resynchronization pending (as per former reception of Data Restoration Notification from the UDM without the indication that resynchronization is not required). If a Data Restoration resynchronization is pending for the received UE, the SMF may perform 1030 this UE resynchronization at that moment. Otherwise, if a Data Restoration resynchronization is not pending, the SMF may ignore this request.
[0097] In an embodiment, the amfResynchedlnd attribute name may have a Boolean value. This information element (IE) may be present if the AMF has initiated data resynchronization 1012, 1014 for the corresponding UE, as a result of the processing of the Data Restoration Notification received from the UDM 120. A presence of this IE with the value false may be prohibited.
[0098] The SMF may check if for the received UE there is a Data Restoration resynchronization pending (as per former reception of Data Restoration Notification from the UDM without the indication that resynchronization is not required). If a Data Restoration resynchronization is pending for the received UE, the SMF may perform this UE resynchronization at that moment. Otherwise, if a Data Restoration resynchronization is not pending, the SMF may ignore the "amfResynchedlnd" indication contained in the request.
[0099] In an embodiment, an AMF-SYNCHED feature may be used to indicate compatibility with the amfResynchedlnd information element. The SMF and the NF consumer (e.g., AMF) supporting this feature may support Data Restoration resynchronization functions with AMF indication of AMF Data Restoration resynchronization is initiated 1020.
[0100] If the AMF has initiated resynchronization for a UE, the AMF may provide an indication to the SMF(s) with established PDU Session(s) to allow that, if this UE was expected to be resynchronized (as a result of the reception of the Data Restoration notification to perform resynchronization directly from the UDM), the SMF shall perform this UE resynchronization at that moment. Note that this is particularly useful in scenarios where the SMF receives an indication from the UDM to perform Data Restoration based on UE activity, and it takes a long time until the SMF receives such UE activity; during that time, the SMF context is not restored. However, the UE activityat the AMF could be more frequent since the AMF counts with the periodic TAU timers that would expire in a limited amount of time. Therefore, when the UDM sends the Data Restoration Notification to both AMF and SMF, the AMF can synchronize its corresponding subscription data based on UE activity quite soon while the SMF might not receive any UE activity for a much longer time, leaving the UE partly resynchronized.
[0101] Fig. 7 shows an example embodiment of a method of data restoration for a first data management consumer 122 in a mobile network. In step 1004, a notification that a data restoration is to be performed for a UE is received in the first data management consumer 122, resulting in the UE being marked for data restoration with the first data management consumer 122. In step 1006, it is checked, in the first data management consumer 122, if the UE is marked for data restoration before performing the data restoration in steps 1010, 1012, 1014. If the UE is marked for data restoration, the method continues with steps 1010, 1012, 1014, where the data restoration for the UE is performed in the first data management consumer 122, resulting in storing of new UE data for the first data management consumer 122 in a data repository UDR, 110. In step 1020, an indication is sent from the first data management consumer 122 to a second data management consumer 124, the indication comprising data indicating that the data restoration is performed or is going to be performed for the first data management consumer 122. The indication may be sent 1020 from the first data management consumer 122 to the second data management consumer 124 to trigger the second management consumer 124 to check if the UE is marked for data restoration with the second data management consumer 124.
[0102] Fig. 8 shows an example embodiment of a method of data restoration for a second data management consumer 124 in a mobile network. In step 1002, a notification that a data restoration is to be performed for a UE is received in the second data management consumer 124, resulting in the UE being marked for data restoration with the second data management consumer 124. In step 1020, an indication is received in the second data management consumer 124 from a first data management consumer 122, the indication comprising data indicating that data restoration is performed or is going to be performed for the first data management consumer 122. In step 1022, it is checked, in the second data management consumer 124, if the UE is marked for data restoration before performing the data restoration in steps 1030,1032, 1034. If the UE is marked for data restoration, the method continues with steps 1030, 1032, 1034, where the data restoration for the UE is performed in the second data management consumer 124, resulting in storing of new UE data for the second data management consumer 124 in a data repository UDR, 110.
[0103] Fig. 9A, which continues in Fig. 9B, shows an example embodiment of a method of data restoration in a mobile network comprising a data repository UDR, 110, a data management function UDM, 120 and at least two data management consumers AMF, SMF, 122, 124 of the data management function UDM, 120. In step 1004, a notification that a first data restoration is to be performed for a UE is received in a first data management consumer 122 of the at least two data management consumers, resulting in the UE being marked for data restoration with the first data management consumer 122. In step 1002, a notification that a second data restoration is to be performed for the UE is received in a second data management consumer 124 of the at least two data management consumers resulting in the UE being marked for data restoration with the second data management consumer 124. Note that steps 1002 and 1004 may be performed in any order or simultaneously. In step 1006, it is checked, in the first data management consumer 122, if the UE is marked for the first data restoration before performing the first data restoration in steps 1010, 1012, 1014. If the UE is marked for the first data restoration, the method continues with steps 1010, 1012, 1014, where the first data restoration for the UE is performed in the first data management consumer 122, resulting in storing of new UE data for the first data management consumer 122 in a data repository UDR, 110. In step 1020, an indication is sent from the first data management consumer 122 to a second data management consumer 124, the indication comprising data indicating that the first data restoration is performed or is going to be performed for the first data management consumer 122, and the indication triggering the second management consumer 124 to check if the UE is marked for data restoration with the second data management consumer 124. In step 1022, it is checked, in the second data management consumer 124, if the UE is marked for the second data restoration before performing the second data restoration in steps 1030, 1032, 1034. If the UE is marked for the second data restoration, the method continues with steps 1030, 1032, 1034, where the second data restoration for the UE is performed in the second data management consumer 124,resulting in storing of new UE data for the second data management consumer 124 in a data repository UDR, 110.
[0104] Fig. 10 shows an example embodiment of a computing system 200 for implementing certain aspects of the present technology. In various examples, the computing system 200 may be any computing device making up the elements of figures 1-6, any part of the system architecture 100, such as UDR 110, UDM 120, the first UDM consumer 122 and the second UDM consumer 124, any part of the system architecture of Fig. 5, such as AMF or SMF, or any other computing system described herein.
[0105] In some implementations, a computing system 200 may implement the methods described herein, such as the methods presented in the time-sequence diagram of Fig. 5 or Fig. 6 of the present disclosure.
[0106] In some implementations, a computing system 200 may implement one or more functions described herein, such as one or more of the NF shown in Fig. 1.
[0107] The computing system 200 may include any component of a computing system described herein, which components may be in communication with each other using connection 205. The connection 205 may be a physical connection via a bus, or a direct connection into processor 210, such as in a chipset architecture. The connection 205 may also be a virtual connection, networked connection, or logical connection.
[0108] In some implementations, the computing system 200 may be a distributed system in which the functions described in this disclosure may be distributed within a datacenter, multiple datacenters, a peer network, etc. In some embodiments, one or more of the described system components represents many such components each performing some or all of the functions for which the component is described. In some embodiments, the components may be physical or virtual devices.
[0109] The example system 200 includes at least one processing unit (CPU or processor) 210 and a connection 205 that couples various system components including system memory 215, such as read-only memory (ROM) 220 and randomaccess memory (RAM) 225 to processor 210. The computing system 200 may include a cache of high-speed memory 212 connected directly with, in close proximity to, or integrated as part of the processor 210.
[0110] The processor 210 may include any general-purpose processor and a hardware service or software service, such as services 232, 234, and 236 stored in storagedevice 230, configured to control the processor 210 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 210 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.
[0111] To enable user interaction, the computing system 200 may include an input device 245, which may represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. The computing system 200 may also include an output device 235, which may be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems may enable a user to provide multiple types of input / output to communicate with the computing system 200.
[0112] The computing system 200 may include a communications interface 240, which may include a receiver, a transmitter and / or a transceiver for communication with other computing systems.
[0113] There is no restriction on operating on any particular hardware arrangement, and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
[0114] A storage device 230 may be a non-volatile memory device and may be a hard disk or other types of computer readable media which may store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs), read-only memory (ROM), and / or some combination of these devices.
[0115] The storage device 230 may include software services, servers, services, etc., that, when the code that defines such software is executed by the processor 210, causes the system to perform a function, such as any of the NFs described herein, including, but not limited to, the functions performed by UDR 110, UDM 120, UDM customer 122, 124 (e.g., AMF orSMF) or NRF 130. In some embodiments, a hardware service that performs a particular function may include a software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 210, connection 205, output device 235, etc., to carry out the function.Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure and the appended claims. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. Any reference signs in the claims should not be construed as limiting the scope thereof.
Claims
28CLAIMS1. A method of data restoration for a first data management consumer (122) in a mobile network, the method comprising:receiving (1004), in the first data management consumer (122), a notification that a data restoration is to be performed for a user equipment, UE, resulting in the UE being marked for data restoration with the first data management consumer (122); checking (1006), in the first data management consumer (122), if the UE is marked for data restoration before performing (1010, 1012, 1014) the data restoration;if the UE is marked for data restoration:performing (1010, 1012, 1014), in the first data management consumer (122), the data restoration for the UE, resulting in storing of new UE data for the first data management consumer (122) in a data repository (UDR, 110); andsending (1020), from the first data management consumer (122), an indication to a second data management consumer (124), the indication comprising data indicating that the data restoration is performed or is going to be performed for the first data management consumer (122),wherein the indication is sent (1020) from the first data management consumer (122) to the second data management consumer (124) to trigger the second management consumer (124) to check if the UE is marked for data restoration with the second data management consumer (124).
2. The method according to claim 2,wherein the new UE data for the first data management consumer (122) is stored (1014) in the data repository (UDR, 110) via an intermediary re-creation or synchronization of data (1012) to a data management function (UDM, 120).
3. The method according to claim 2,wherein the data repository is a Unified Data Repositors, UDR (UDR, 110), wherein the data management function is a Unified Data Management, UDM (UDM, 120), data-base front-end,and wherein the first data management consumer is one of: an Access and Mobility Management Function, AMF (AMF); a Session Management Function, SMF (SMF); a Short Message Service Function, SMSF; a Network Exposure Function, NEF.
4. The method according to claim 3,wherein the first data management consumer (122) is the AMF (AMF), and wherein the new data for the AMF stored in the UDR comprises AMF context data for the UE.
5. A network node (200) comprising a first data management consumer (122) configured to perform the method according to any one of the claims 1-4.
6. An Access and Mobility Management Function, AMF (AMF) for use in a mobile network, wherein the AMF is a first data management consumer (122) configured to perform the method according to any one of the claims 1-4.
7. A method of data restoration for a second data management consumer (124) in a mobile network, the method comprising:receiving (1002), in the second data management consumer (124), a notification that a data restoration is to be performed for a user equipment, UE, resulting in the UE being marked for data restoration with the second data management consumer (124);receiving (1020), in the second data management consumer (124) from a first data management consumer (122), an indication comprising data indicating that data restoration is performed or is going to be performed for the first data management consumer (122);checking (1022), in the second data management consumer (124), if the UE is marked for data restoration before performing (1030, 1032, 1034) the data restoration;if the UE is marked for data restoration:performing (1030, 1032, 1034), in the second data management consumer (124), the data restoration for the UE, resulting in storing of new UE data for the second data management consumer (124) in a data repository (UDR, 110).
8. The method according to claim 7,wherein the new UE data for the second data management consumer (124) is stored (1034) in the data repository (UDR, 110) via an intermediary re-creation or synchronization of data (1032) to a data management function (UDM, 120).
9. The method according to claim 8,wherein the data repository is a Unified Data Repositors, UDR (UDR, 110), wherein the data management function is a Unified Data Management, UDM (UDM, 120), data-base front-end,and wherein the second data management consumer is one of: an Access and Mobility Management Function, AMF (AMF); a Session Management Function, SMF (SMF); a Short Message Service Function, SMSF; a Network Exposure Function, NEF.
10. The method according to claim 9,wherein the second data management consumer (124) is the SMF (SMF), and wherein the new data for the SMF stored in the UDR comprises SMF context data for the UE.
11. A network node (200) comprising a second data management consumer (124) configured to perform the method according to any one of the claims 7-10.
12. A Session Management Function, SMF (SMF) for use in a mobile network, wherein the SMF is a second data management consumer (124) configured to perform the method according to any one of the claims 7-10.
13. A method of data restoration in a mobile network comprising a data repository (UDR, 110), a data management function (UDM, 120) and at least two data management consumers (AMF, SMF, 122, 124) of the data management function (UDM, 120), the method comprising:receiving (1004), in a first data management consumer (122) of the at least two data management consumers, a notification that a first data restoration is to be performed for a user equipment, UE, resulting in the UE being marked for data restoration with the first data management consumer (122);receiving (1002), in a second data management consumer (124) of the at least two data management consumers, a notification that a second data restoration is to be performed for the UE resulting in the UE being marked for data restoration with the second data management consumer (124);checking (1006), in the first data management consumer (122), if the UE is marked forthe first data restoration before performing (1010, 1012, 1014) the first data restoration, and if the UE is marked for the first data restoration:performing (1010, 1012, 1014), in the first data management consumer (122), the first data restoration for the UE, resulting in storing of new UE data for the first data management consumer (122) in a data repository (UDR, 110); andsending (1020), from the first data management consumer (122), an indication to a second data management consumer (124), the indication comprising data indicating that the first data restoration is performed or is going to be performed for the first data management consumer (122), the indication triggering the second management consumer (124) to check if the UE is marked for data restoration with the second data management consumer (124);checking (1022), in the second data management consumer (124), if the UE is marked for the second data restoration before performing (1030, 1032, 1034) the second data restoration, and if the UE is marked for the second data restoration: performing (1030, 1032, 1034), in the second data management consumer (124), the second data restoration for the UE, resulting in storing of new UE data for the second data management consumer (124) in a data repository (UDR, 110).
14. The method according to claim 13,wherein the new UE data for the first data management consumer (122) and the new UE data for the second data management consumer (124) are stored (1014) in the data repository (UDR, 110) via an intermediary re-creation or synchronization of data (1012) to the data management function (UDM, 120).
15. The method according to claim 13 or claim 14,wherein the data repository is a Unified Data Repositors, UDR (UDR, 110), wherein the data management function is a Unified Data Management, UDM (UDM, 120), data-base front-end,32and wherein the data management consumers (122, 124) include at least two of: an Access and Mobility Management Function, AMF; a Session Management Function, SMF; a Short Message Service Function, SMSF; a Network Exposure Function, NEF.
16. The method according to claim 15,wherein the first data management consumer (122) is the AMF (AMF), and wherein the second data management consumer (124) is the SMF (SMF).
17. The method according to claim 16,wherein the new data for the AMF stored in the UDR comprises AMF context data for the UE,and wherein the new data for the SMF stored in the UDR comprises context data for the UE.
18. The method according to any one of the claims 13-17, wherein the mobile network is a 5G Core, 5GC, network.
19. A mobile network arranged to perform the method according to any one of the claims 13-18.
20. A computer program comprising instruction which, when the program is executed by one or more processors, cause the one or more processors to carry out the method according to any one of the claims 1-4 or any one of the claims 7-10.
21. A computer-readable storage medium comprising instructions which, when executed by one or more processors, cause the one or more processors to carry out the method according to any one of the claims 1-4 or any one of the claims 7-10.