WO2022228417A1 - 用户数据容灾方法、装置、网元设备及存储介质 - Google Patents
用户数据容灾方法、装置、网元设备及存储介质 Download PDFInfo
- Publication number
- WO2022228417A1 WO2022228417A1 PCT/CN2022/089197 CN2022089197W WO2022228417A1 WO 2022228417 A1 WO2022228417 A1 WO 2022228417A1 CN 2022089197 W CN2022089197 W CN 2022089197W WO 2022228417 A1 WO2022228417 A1 WO 2022228417A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network element
- udr
- message
- udm
- request
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 116
- 230000015654 memory Effects 0.000 claims description 45
- 238000004891 communication Methods 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 23
- 238000011084 recovery Methods 0.000 claims description 23
- 230000006870 function Effects 0.000 claims description 9
- 238000007726 management method Methods 0.000 claims description 9
- 238000013523 data management Methods 0.000 claims description 3
- 230000004044 response Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 230000001360 synchronised effect Effects 0.000 description 8
- 230000001960 triggered effect Effects 0.000 description 5
- 235000019800 disodium phosphate Nutrition 0.000 description 4
- 230000005291 magnetic effect Effects 0.000 description 4
- 230000002085 persistent effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000004549 pulsed laser deposition Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000005294 ferromagnetic effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
Definitions
- the present application relates to the field of communication technologies, and in particular, to a user data disaster recovery method, device, network element device, and storage medium.
- the Unified Data Repository (UDR, Unified Data Repository) network element in the 5G core network needs to maintain the synchronization of temporary user data in the related network elements.
- the unified data management (UDM, Unified Data Management) network element cannot know the failure, downtime and other conditions of the UDR network element in real time, which further causes the data synchronization of the UDR network element to be untimely.
- the embodiments of the present application provide a user data disaster recovery method, device, network element device, and storage medium.
- the embodiment of the present application provides a user data disaster tolerance method, which is applied to a UDR network element, and the method includes:
- the first message is used to notify the restart event of the UDR network element.
- the embodiment of the present application also provides a user data disaster tolerance method, which is applied to a UDM network element, and the method includes:
- the first message is used to notify the restart event of the UDR network element.
- the embodiment of the present application also provides a user data disaster recovery device, including:
- a first sending unit configured to send a first message to each UDM network element in the UDM network element set after the UDR network element is restarted;
- the first message is used to notify the restart event of the UDR network element.
- the embodiment of the present application also provides a user data disaster recovery device, including:
- a first receiving unit configured to receive the first message sent by the UDR network element
- the first message is used to notify the restart event of the UDR network element.
- the embodiment of the present application also provides a UDR network element, including: a first processor and a first communication interface; wherein,
- the first communication interface is configured to send a first message to each UDM network element in the UDM network element set after the UDR network element is restarted; the first message is used to notify the restart of the UDR network element event.
- the embodiment of the present application also provides a UDM network element, including: a second processor and a second communication interface; wherein,
- the second communication interface is configured to receive a first message sent by a UDR network element; the first message is used to notify a restart event of the UDR network element.
- the embodiment of the present application also provides a UDR network element, which is characterized by comprising: a first processor and a first memory configured to store a computer program that can be run on the processor,
- the first processor is configured to execute the steps of any method on the UDR network element side when running the computer program.
- the embodiment of the present application also provides a UDM network element, which is characterized by comprising: a second processor and a second memory configured to store a computer program that can be run on the processor,
- the second processor is configured to execute the steps of any method on the UDM network element side when running the computer program.
- An embodiment of the present application further provides a storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the computer program implements the steps of any method on the UDR network element side, or implements the UDM network element. side the steps of either method.
- the UDR network element after the UDR network element is restarted, a first message is sent to each UDM network element in the UDM set for sending a first message to the UDM network element.
- the UDR network element notifies the restart event of the UDR network element. In this way, when the UDR network element is restarted due to failure or downtime, the UDM network element can timely learn that the UDR network element has restarted. On this basis, the UDR network element can be triggered as soon as possible.
- the data synchronization process between elements and related network elements ensures the disaster tolerance of user data equipment in the 5G core network.
- FIG. 1 is a network architecture diagram related to 5G user data in the related art
- FIG. 2 is a schematic flowchart of a user data disaster tolerance method according to an embodiment of the present application
- FIG. 3 is a schematic flowchart of an implementation of sending a first message to a UDM network element by a UDR network element according to an embodiment of the present application
- FIG. 4 is a schematic diagram of an implementation process flow of implicitly creating a subscription according to an embodiment of the present application
- FIG. 5 is a schematic diagram of the implementation process of creating a subscription in an explicit manner according to an embodiment of the present application
- FIG. 6 is a schematic flowchart of a data synchronization triggering process according to an embodiment of the present application.
- FIG. 7 is a schematic flowchart of a user data disaster recovery method according to another embodiment of the present application.
- FIG. 8 is a schematic flowchart of a network structure and an IPv6 asset automatic discovery method according to an application embodiment of the present application
- FIG. 9 is a schematic structural diagram of a user data disaster recovery device according to an embodiment of the present application.
- FIG. 10 is a schematic structural diagram of another user data disaster recovery apparatus according to an embodiment of the present application.
- FIG. 11 is a schematic structural diagram of a UDR network element according to an embodiment of the present application.
- FIG. 12 is a schematic structural diagram of a URM network element according to an embodiment of the present application.
- the user data equipment of the 5G core network is used to store the relevant persistent data and temporary data of the 5G user, wherein the persistent data includes: user mobility management subscription data, session management subscription data, and policy data.
- user data equipment includes two types of equipment: UDM network element and UDR network element.
- UDR network element is used to actually store the relevant persistent data and temporary data of 5G users, which is equivalent to the background database;
- UDM network element is the core of 5G.
- Other interfaces in the network for accessing user data realize the relevant business logic of user data access, which is equivalent to the front-end access interface.
- FIG. 1 shows a network architecture related to 5G user data in the related art.
- UDR network elements During the operation of a 5G network, UDR network elements will inevitably experience failures and downtimes. In practical applications, UDR network elements usually regularly back up stored data to a backup database. When a UDR network element fails and restarts, data can be restored from the backup database. However, during the restart of the UDR network element and the data recovery process, if the temporary user data, such as the mobility management temporary data in the AMF network element, changes, the problem of inconsistency between the AMF network element and the UDR network element data will occur. Therefore, After the UDR network element fails and restarts, the relevant network elements need to be notified to trigger the process of data resynchronization.
- the temporary user data such as the mobility management temporary data in the AMF network element
- the UDM network element cannot know the failure and downtime of the UDR network element in real time, which further leads to the untimely data synchronization of the UDR network element, the disaster tolerance of the user data equipment of the 5G core network is not easy. good.
- the UDR network element after the UDR network element is restarted, a first message is sent to each UDM network element in the UDM set for sending a first message to the UDM network element.
- the network element notifies the UDR network element of the restart event.
- the UDM network element can timely learn that the UDR network element has restarted.
- the UDR network element can be triggered as soon as possible.
- the data synchronization process between network elements and related network elements ensures the disaster tolerance of user data equipment in the 5G core network.
- the embodiment of the present application provides a user data disaster tolerance method, which is applied to a UDR network element. As shown in FIG. 2 , the method includes:
- Step 201 After the UDR network element is restarted, send a first message to each UDM network element in the UDM network element set.
- the first message is used to notify the restart event of the UDR network element.
- the UDR network element can use the notification process defined in the 5G service-oriented interface protocol framework to send the first message to the relevant UDM network element to notify the UDR network element to the UDM network element.
- a restart event has occurred.
- the UDR network element sends the first message to each UDM network element in the UDM network element set, wherein the UDM network element set includes one or more UDM network elements.
- Figure 3 shows an example of the implementation process of the UDR network element sending the first message to the UDM network element, wherein the UDR network element sends a POST message to the UDM network element after restarting to notify the UDM network element that the UDR network element has a restart event, After receiving the POST message, the UDM network element returns a 200 OK message to the UDR network element.
- the first message carries at least one of the following:
- the impacted number range The impacted number range.
- the first message is a POST message.
- the UDR network element creates a subscription for one or more UDM network elements about the restart event of the UDR network element, and these UDM network elements subscribed to the restart event are grouped into the UDM network element set. After the restart, the first message can be sent to the UDM network element subscribed to the UDR network element restart event.
- the method before the sending the first message to each UDM network element in the set of UDM network elements, the method further includes:
- the first subscription information indicates that the corresponding UDM network element subscribes to the restart event of the UDR network element.
- the first subscription information includes at least an identifier of a corresponding UDM network element.
- the created first subscription information may also include the identifier of the corresponding UDM network element, which is used to mark the UDM network element subscribed to the restart event, In this way, when the UDR network element restarts, the first message may be sent to the relevant UDM network element subscribed to the restart event based on the identifier of the UDM network element.
- the creation of the first subscription information may be completed in an implicit manner or an explicit manner.
- the method includes:
- the first subscription information is created for the corresponding UDM network element based on the received first request or the second request.
- the first request represents an access request to the UDR network element;
- the second request represents a subscription request for a restart event of the UDR network element.
- the UDM network element initiates a first request to the UDR network element, requesting to access the data in the UDR network element, and the UDR network element receives the first request. After that, a response about the first request is returned to the UDM network element, and then the first subscription information is created for the UDM network element by default. In this way, the UDM network element completes the subscription to the UDR network element restart event.
- the UDM network element initiates the first request to the UDR network element, and the UDM network element receives the response about the first request returned by the UDR network element
- the UDM network element initiates a second request to the UDR network element, requesting to subscribe to the restart event of the UDR network element.
- the UDR network element After receiving the second request, the UDR network element returns a response to the second request to the UDM network element, and then defaults to the UDM network element.
- the element creates the first subscription information, so that the UDM network element completes the subscription to the restart event of the UDR network element.
- the method further includes:
- the first subscription information corresponding to the UDM network element is backed up.
- the UDR network element can periodically back up the user data to the backup database, and at the same time back up the first subscription information to the backup database, so that when the UDR network element fails and restarts, it can be restored from the backup database.
- User data and first subscription information so as to ensure that after a subsequent failure, downtime and other conditions are encountered and restarted, a notification can be sent to the UDM network element subscribed to the restart event in a correct and timely manner.
- the UDR network element sends the first message to the UDM network element based on the URI used to receive the notification message in the UDM network element.
- the URI of the notification message is a registered trademark of Cisco Systems, Inc.
- URI Uniform Resource Identifier
- NRF Network Repository Function
- the URI used to receive the notification message in the UDM network element is obtained from the first request or the second request of the UDM network element.
- the UDM network element when the UDM network element sends the second request for subscribing the restart event to the UDR network element, the URI used for receiving the notification message in the UDM network element is carried In the second request, in this way, the UDR network element can obtain the corresponding URI from the received second request.
- the UDR network element can obtain the URI for receiving the notification message in the UDM network element based on at least one of the following methods:
- the UDR network element obtains the URI used to receive the notification message in the corresponding UDM network element by querying the NRF network element;
- the UDM network element initiates the first request for requesting data access to the UDR network element
- the URI carrying the notification message in the UDM network element is added to the first request.
- the corresponding URI can be obtained in the first request.
- the method further includes:
- AMF Access and Mobility Management Function
- SMF Session Management Function
- the UDR network element after restarting, notifies the UDM network element of the corresponding restart event through the first message, and the UDM network element then notifies the corresponding AMF and/or SMF network element of the restart event based on the first message.
- the corresponding data synchronization process is triggered, and the data synchronization process is started before the AMF and/or SMF network element and the UDR network element.
- the embodiment of the present application also provides a data disaster tolerance method, which is applied to a UDM network element.
- the method includes:
- Step 701 Receive the first message sent by the UDR network element.
- the first message is used to notify the restart event of the UDR network element.
- the first message is sent to the UDM network element after the UDR network element restarts.
- the UDR network element can use the notification process defined in the 5G service-oriented interface protocol framework to send the first message to the relevant UDM network element to notify the UDR network element to the UDM network element.
- a restart event has occurred.
- the first message carries at least one of the following:
- the first message is a POST message.
- the method before the receiving the first message sent by the UDR network element, the method further includes:
- the first request represents an access request to the UDR network element.
- the first request carries a URI in the UDM network element for receiving a notification message.
- the UDM network element initiates a first request to the UDR network element, requesting to access the data in the UDR network element, and the UDR network element receives the first request. After that, a response about the first request is returned to the UDM network element, and then the first subscription information is created for the UDM network element by default. In this way, the UDM network element completes the subscription to the UDR network element restart event.
- the UDR network element may obtain the URI for receiving the notification message in the UDM network element based on at least one of the following methods:
- the UDR network element obtains the URI used to receive the notification message in the corresponding UDM network element by querying the NRF network element;
- the UDM network element initiates the first request for requesting data access to the UDR network element
- the URI carrying the notification message in the UDM network element is added to the first request.
- the corresponding URI can be obtained in the first request.
- the method further includes:
- the second request represents a subscription request for a restart event of the UDR network element.
- the second request carries a URI in the UDM network element for receiving the notification message.
- the UDM network element initiates the first request to the UDR network element, and the UDM network element receives the response about the first request returned by the UDR network element After that, the UDM network element initiates a second request to the UDR network element, requesting to subscribe to the restart event of the UDR network element. After receiving the second request, the UDR network element returns a response to the second request to the UDM network element, and then the default is this The UDM network element creates the first subscription information, so that the UDM network element completes the subscription to the restart event of the UDR network element.
- the UDM network element when the UDM network element sends the second request for subscribing the restart event to the UDR network element, the URI used for receiving the notification message in the UDM network element is carried in the second request. In this way, the UDR network element can obtain the corresponding URI from the received second request.
- the method further includes:
- the first message is sent to the AMF network element and/or the SMF network element.
- the UDR network element after restarting, notifies the UDM network element of the corresponding restart event through the first message, and the UDM network element then notifies the corresponding AMF and/or SMF network element of the restart event based on the first message.
- the corresponding data synchronization process is triggered, and the data synchronization process is started before the AMF and/or SMF network element and the UDR network element.
- FIG. 8 shows the implementation process of the user data disaster tolerance method provided by the application embodiment of the present application, including the following steps:
- Step 1 The AMF network element sends a UDM network element access request to the UDM network element.
- Step 2 The UDM network element sends a UDR network element access request to the UDR network element.
- step 1 and step 2 it is equivalent to that the AMF network element initiates a service request to the UDM network element, and the UDM network element accordingly initiates a service request to the UDR network element.
- the UDM network element may add a URI for receiving the notification message to the request.
- Step 3 The UDR network element returns a response to the UDR network element access request to the UDM network element.
- Step 4 The UDM network element returns a response to the UDM network element access request to the AMF network element.
- the UDM network element acts as an access interface between the AMF network element and the UDR network element to implement related business logic.
- step 5 the UDM network element sends a restart event subscription request to the UDR network element.
- the UDM network element may carry the URI for receiving the notification message in the request.
- step 6 the UDR network element returns a response to the restart event subscription request to the UDM network element.
- Step 7 The UDR network element creates a subscription about the restart event for the UDM network element.
- the UDR network element creates a subscription based on an explicit method
- steps 5 and 6 are not performed, the UDR network element creates a subscription based on an implicit method.
- Step 8 The UDR network element backs up the subscription data generated in Step 7.
- the UDR network element backs up the subscription data while backing up the local user data.
- Step 9 The UDR network element fails and restarts to restore data.
- the recovered data includes user data and subscription data.
- step 10 the UDR network element queries the NRF network element for the URI in the UDM network element for receiving the notification message.
- step 10 need not be performed.
- step 11 the NRF network element returns a response on the query result to the UDR network element.
- Step 12 The UDR network element sends a first message to the UDM network element, and notifies the UDM network element that the UDR network element has restarted.
- a first message is sent to each UDM network element in the UDM set, so as to notify the UDM network element of the restart event of the UDR network element,
- the UDM network element can timely learn that the UDR network element has restarted, and on this basis, the data between the UDR network element and related network elements can be triggered as soon as possible.
- the synchronization process ensures the disaster tolerance of user data equipment in the 5G core network, and can support the disaster tolerance of UDR network elements when UDM network elements and UDR network elements of different manufacturers are networked.
- the embodiment of the present application further provides a user data disaster recovery device, which is set in the UDR network element.
- the device includes:
- the first sending unit 901 is configured to send a first message to each UDM network element in the UDM network element set after the UDR network element is restarted; wherein,
- the first message is used to notify the restart event of the UDR network element.
- the first message carries at least one of the following:
- the first message is a POST message.
- the apparatus further includes:
- a subscription unit configured to create first subscription information for the UDM network element before the first message is sent to each UDM network element in the UDM network element set;
- the first subscription information indicates that the corresponding UDM network element subscribes to the restart event of the UDR network element.
- the first subscription information includes at least an identifier of a corresponding UDM network element.
- the subscription unit is configured as:
- the first subscription information is created for the corresponding UDM network element based on the received first request or second request;
- the first request represents an access request to the UDR network element; the second request represents a subscription request for a restart event of the UDR network element.
- the subscription unit is further configured to:
- the URI used to receive the notification message in the UDM network element is obtained from the first request or the second request of the UDM network element.
- the apparatus further includes:
- the backup unit is configured to backup the first subscription information corresponding to the UDM network element.
- the apparatus further includes:
- a data synchronization unit configured to perform data synchronization with the AMF network element and/or the SMF network element after the first message is sent to each UDM network element in the UDM network element set.
- the first sending unit 901 and the data synchronization unit may be implemented by a communication interface in the user data disaster recovery device; the subscription unit and the backup unit may be implemented by a processor in the user data disaster recovery device.
- the embodiment of the present application further provides a user data disaster recovery device, which is set in the UDM network element.
- the device includes:
- the first receiving unit 1001 is configured to receive the first message sent by the UDR network element; wherein,
- the first message is used to notify the restart event of the UDR network element.
- the first message carries at least one of the following:
- the first message is a POST message.
- the apparatus further includes:
- a second sending unit configured to send a first request to the UDR network element before receiving the first message sent by the UDR network element;
- the first request represents an access request to the UDR network element.
- the first request carries a URI in the UDM network element for receiving a notification message.
- the apparatus further includes:
- a third sending unit configured to send a second request to the UDR network element after the sending of the first request to the UDR network element;
- the second request represents a subscription request for a restart event of the UDR network element.
- the second request carries a URI in the UDM network element for receiving the notification message.
- the apparatus further includes:
- the fourth sending unit is configured to send the first message to the AMF network element and/or the SMF network element after receiving the first message sent by the UDR network element.
- the first receiving unit 1001 , the second sending unit, the third sending unit and the fourth sending unit may be implemented by a communication interface in the user data disaster recovery device.
- the user data disaster recovery device when the user data disaster recovery device provided in the above embodiment performs user data disaster recovery, only the division of the above program modules is used as an example for illustration. In practical applications, the above processing may be allocated to different The program module is completed, that is, the internal structure of the device is divided into different program modules to complete all or part of the above-described processing.
- the user data disaster recovery device and the user data disaster recovery method provided in the above embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
- the embodiment of the present application further provides a UDR network element.
- the UDR network element 1100 includes:
- the first processor 1102 is connected to the first communication interface 1101 to implement information exchange with other network nodes, and is configured to execute the methods provided by one or more technical solutions on the UDR network element side when running a computer program. And the computer program is stored on the first memory 1103 .
- the first communication interface 1101 is configured to send a first message to each UDM network element in the UDM network element set after the UDR network element is restarted; wherein,
- the first message is used to notify the restart event of the UDR network element.
- the first message carries at least one of the following:
- the first message is a POST message.
- the first processor 1102 is configured to, before sending the first message to each UDM network element in the set of UDM network elements, create first subscription information for the UDM network element; wherein,
- the first subscription information indicates that the corresponding UDM network element subscribes to the restart event of the UDR network element.
- the first subscription information includes at least an identifier of a corresponding UDM network element.
- the first processor 1102 is configured to:
- the first subscription information is created for the corresponding UDM network element based on the received first request or second request;
- the first request represents an access request to the UDR network element; the second request represents a subscription request for a restart event of the UDR network element.
- the first processor 1102 is configured to:
- the URI used to receive the notification message in the UDM network element is obtained from the first request or the second request of the UDM network element.
- the first processor 1102 is further configured to:
- the first subscription information corresponding to the UDM network element is backed up.
- the first communication interface 1101 is further configured as:
- bus system 1104 various components in the UDR network element 1100 are coupled together through the bus system 1104 .
- bus system 1104 is configured to enable connection communication between these components.
- the bus system 1104 also includes a power bus, a control bus, and a status signal bus.
- the various buses are labeled as bus system 1104 in FIG. 11 .
- the first memory 1103 in this embodiment of the present application is configured to store various types of data to support the operation of the UDR network element 1100 .
- Examples of such data include: any computer program configured to operate on the UDR network element 1100 .
- the methods disclosed in the above embodiments of the present application may be applied to the first processor 1102 or implemented by the first processor 1102 .
- the first processor 1102 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the first processor 1102 or an instruction in the form of software.
- the above-mentioned first processor 1102 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
- the first processor 1102 may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of this application.
- a general purpose processor may be a microprocessor or any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
- the software module may be located in a storage medium, and the storage medium is located in the first memory 1103, the first processor 1102 reads the information in the first memory 1103, and completes the steps of the foregoing method in combination with its hardware.
- the UDR network element 1100 may be implemented by one or more Application Specific Integrated Circuit (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array), general-purpose processor, controller, microcontroller (MCU, Micro Controller Unit), microprocessor (Microprocessor), or other Electronic components are implemented for carrying out the aforementioned method.
- ASIC Application Specific Integrated Circuit
- DSP Programmable Logic Device
- PLD Programmable Logic Device
- CPLD Complex Programmable Logic Device
- FPGA Field Programmable Gate Array
- MCU microcontroller
- Microcontroller Micro Controller Unit
- Microprocessor Microprocessor
- the embodiment of the present application further provides a UDM network element.
- the UDM network element 1200 includes:
- the second communication interface 1201 is capable of information interaction with other network nodes
- the second processor 1202 is connected to the second communication interface 1201 to implement information exchange with other network nodes, and is configured to execute the methods provided by one or more technical solutions on the UDM network element side when running a computer program. And the computer program is stored on the second memory 1203 .
- the second communication interface 1201 is configured as:
- the first message is used to notify the restart event of the UDR network element.
- the first message carries at least one of the following:
- the first message is a POST message.
- the second communication interface 1201 is further configured as:
- the first request represents an access request to the UDR network element.
- the first request carries a URI in the UDM network element for receiving a notification message.
- the second communication interface 1201 is further configured as:
- the second request represents a subscription request for a restart event of the UDR network element.
- the second request carries a URI in the UDM network element for receiving the notification message.
- the second communication interface 1201 is further configured as:
- the first message After receiving the first message sent by the UDR network element, the first message is sent to the AMF network element and/or the SMF network element.
- bus system 1204 is configured to enable connection communication between these components.
- bus system 1204 also includes a power bus, a control bus, and a status signal bus.
- the various buses are labeled as bus system 1204 in FIG. 13 .
- the second memory 1203 in this embodiment of the present application is configured to store various types of data to support the operation of the UDM network element 1200 .
- Examples of such data include: any computer program configured to operate on the UDM network element 1200.
- the methods disclosed in the above embodiments of the present application may be applied to the second processor 1202 or implemented by the second processor 1202 .
- the second processor 1202 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method may be completed by an integrated logic circuit of hardware in the second processor 1202 or an instruction in the form of software.
- the above-mentioned second processor 1202 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
- the second processor 1202 may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of this application.
- a general purpose processor may be a microprocessor or any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
- the software module may be located in a storage medium, the storage medium is located in the second memory 1203, the second processor 1202 reads the information in the second memory 1203, and completes the steps of the foregoing method in combination with its hardware.
- the UDM network element 1200 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components for performing the aforementioned methods.
- the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memory.
- the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-only memory) Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , CD-ROM, or CD-ROM (Compact Disc Read-Only Memory); magnetic surface memory can be disk memory or tape memory.
- RAM Random Access Memory
- SRAM Static Random Access Memory
- SSRAM Synchronous Static Random Access Memory
- DRAM Dynamic Random Access Memory
- SDRAM Synchronous Dynamic Random Access Memory
- DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
- ESDRAM Enhanced Type Synchronous Dynamic Random Access Memory
- SLDRAM Synchronous Link Dynamic Random Access Memory
- DRRAM Direct Rambus Random Access Memory
- an embodiment of the present application further provides a storage medium, that is, a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 1103 that stores a computer program, and the above-mentioned computer program can be stored by a UDR network element
- the first processor 1102 of 1100 executes the steps described in the foregoing UDR network element side method.
- Another example includes the second memory 1203 storing a computer program.
- the computer program can be executed by the second processor 1202 of the UDM network element 1200 to complete the steps of the UDM network element side method.
- the computer-readable storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Computer And Data Communications (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (24)
- 一种用户数据容灾方法,应用于统一数据仓库UDR网元,所述方法包括:在所述UDR网元重启后,向统一数据管理UDM网元集合中的每个UDM网元发送第一消息;其中,所述第一消息用于通知所述UDR网元的重启事件。
- 根据权利要求1所述的方法,其中,所述第一消息携带以下至少之一:所述UDR网元的重启时间;受影响的号码范围。
- 根据权利要求1所述的方法,其中,所述第一消息为POST消息。
- 根据权利要求1所述的方法,其中,在所述向UDM网元集合中的每个UDM网元发送第一消息之前,所述方法还包括:为UDM网元创建第一订阅信息;其中,所述第一订阅信息表征对应的UDM网元订阅所述UDR网元的重启事件。
- 根据权利要求4所述的方法,其中,所述第一订阅信息至少包括对应的UDM网元的标识。
- 根据权利要求4所述的方法,其中,在所述为UDM网元创建第一订阅信息时,所述方法包括:基于接收到的第一请求或第二请求为对应的UDM网元创建所述第一订阅信息;其中,所述第一请求表征对所述UDR网元的访问请求;所述第二请求表征对所述UDR网元的重启事件的订阅请求。
- 根据权利要求6所述的方法,其中,所述方法还包括:通过查询网络存储功能NRF网元,获取UDM网元中用于接收通知消息的统一资源标识符URI;和/或,从UDM网元的第一请求或第二请求中获取UDM网元中用于接收通知消息的URI。
- 根据权利要求4所述的方法,其中,所述方法还包括:备份UDM网元对应的第一订阅信息。
- 根据权利要求1至8任一项所述的方法,其中,在所述向UDM网元集合中的每个UDM网元发送第一消息之后,所述方法还包括:与接入和移动管理功能AMF网元和/或会话管理功能SMF网元进行数据同步。
- 一种用户数据容灾方法,应用于UDM网元,所述方法包括:接收UDR网元发送的第一消息;其中,所述第一消息用于通知所述UDR网元的重启事件。
- 根据权利要求10所述的方法,其中,所述第一消息携带以下至少之 一:所述UDR网元的重启时间;受影响的号码范围。
- 根据权利要求10所述的方法,其中,所述第一消息为POST消息。
- 根据权利要求10所述的方法,其中,在所述接收UDR网元发送的第一消息之前,所述方法还包括:向所述UDR网元发送第一请求;其中,所述第一请求表征对所述UDR网元的访问请求。
- 根据权利要求13所述的方法,其中,所述第一请求中携带有所述UDM网元中用于接收通知消息的URI。
- 根据权利要求13所述的方法,其中,在所述向所述UDR网元发送第一请求之后,所述方法还包括:向所述UDR网元发送第二请求;其中,所述第二请求表征对所述UDR网元的重启事件的订阅请求。
- 根据权利要求15所述的方法,其中,所述第二请求中携带有所述UDM网元中用于接收通知消息的URI。
- 根据权利要求10至16任一项所述的方法,其中,在所述接收UDR网元发送的第一消息之后,所述方法还包括:向AMF网元和/或SMF网元发送所述第一消息。
- 一种用户数据容灾装置,包括:第一发送单元,配置为在所述UDR网元重启后,向UDM网元集合中的每个UDM网元发送第一消息;其中,所述第一消息用于通知所述UDR网元的重启事件。
- 一种用户数据容灾装置,包括:第一接收单元,配置为接收UDR网元发送的第一消息;其中,所述第一消息用于通知所述UDR网元的重启事件。
- 一种UDR网元,包括:第一处理器及第一通信接口;其中,所述第一通信接口,配置为在所述UDR网元重启后,向UDM网元集合中的每个UDM网元发送第一消息;所述第一消息用于通知所述UDR网元的重启事件。
- 一种UDM网元,包括:第二处理器及第二通信接口;其中,所述第二通信接口,配置为接收UDR网元发送的第一消息;所述第一消息用于通知所述UDR网元的重启事件。
- 一种UDR网元,包括:第一处理器和配置为存储能够在处理器上运行的计算机程序的第一存储器,其中,所述第一处理器配置为运行所述计算机程序时,执行权利要求1至9任一项所述方法的步骤。
- 一种UDM网元,包括:第二处理器和配置为存储能够在处理器上运行的计算机程序的第二存储器,其中,所述第二处理器配置为运行所述计算机程序时,执行权利要求10至17任一项所述方法的步骤。
- 一种存储介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现权利要求1至9任一项所述方法的步骤,或者实现权利要求10至17任一项所述方法的步骤。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023565431A JP2024518771A (ja) | 2021-04-26 | 2022-04-26 | ユーザデータのディザスタリカバリ方法、装置、ネットワークエレメント機器及び記憶媒体 |
EP22794887.4A EP4333469A1 (en) | 2021-04-26 | 2022-04-26 | User data disaster tolerance method and apparatus, network element device, and storage medium |
US18/556,543 US20240195893A1 (en) | 2021-04-26 | 2022-04-26 | User data disaster tolerance method, device, network element device and storage medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110455937.8 | 2021-04-26 | ||
CN202110455937.8A CN115250466A (zh) | 2021-04-26 | 2021-04-26 | 用户数据容灾方法、装置、网元设备及存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022228417A1 true WO2022228417A1 (zh) | 2022-11-03 |
Family
ID=83697039
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/089197 WO2022228417A1 (zh) | 2021-04-26 | 2022-04-26 | 用户数据容灾方法、装置、网元设备及存储介质 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20240195893A1 (zh) |
EP (1) | EP4333469A1 (zh) |
JP (1) | JP2024518771A (zh) |
CN (1) | CN115250466A (zh) |
WO (1) | WO2022228417A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110351111A (zh) * | 2018-04-04 | 2019-10-18 | 中国移动通信有限公司研究院 | 一种订阅处理方法、网络节点及用户数据库 |
CN110830422A (zh) * | 2018-08-10 | 2020-02-21 | 中国移动通信有限公司研究院 | 一种终端行为数据处理方法及设备 |
CN111200848A (zh) * | 2018-11-19 | 2020-05-26 | 华为技术有限公司 | 一种通信方法及装置 |
WO2020225296A1 (en) * | 2019-05-06 | 2020-11-12 | Ntt Docomo, Inc. | Mobile communication core network device and method for managing wireless communications after insertion of an intermediate-session management function |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110399573A (zh) * | 2018-04-16 | 2019-11-01 | 中国移动通信有限公司研究院 | 一种信息处理方法、装置、设备及计算机可读存储介质 |
CN112312418A (zh) * | 2019-07-26 | 2021-02-02 | 华为技术有限公司 | 一种用户面数据的获取方法、装置及存储介质 |
CN112584369B (zh) * | 2019-09-27 | 2024-01-05 | 维沃移动通信有限公司 | 位置服务配置方法及设备 |
CN112637819B (zh) * | 2020-12-15 | 2023-10-03 | 中国联合网络通信集团有限公司 | 一种融合网络中的业务开通方法及装置 |
-
2021
- 2021-04-26 CN CN202110455937.8A patent/CN115250466A/zh active Pending
-
2022
- 2022-04-26 JP JP2023565431A patent/JP2024518771A/ja active Pending
- 2022-04-26 EP EP22794887.4A patent/EP4333469A1/en active Pending
- 2022-04-26 US US18/556,543 patent/US20240195893A1/en active Pending
- 2022-04-26 WO PCT/CN2022/089197 patent/WO2022228417A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110351111A (zh) * | 2018-04-04 | 2019-10-18 | 中国移动通信有限公司研究院 | 一种订阅处理方法、网络节点及用户数据库 |
CN110830422A (zh) * | 2018-08-10 | 2020-02-21 | 中国移动通信有限公司研究院 | 一种终端行为数据处理方法及设备 |
CN111200848A (zh) * | 2018-11-19 | 2020-05-26 | 华为技术有限公司 | 一种通信方法及装置 |
WO2020225296A1 (en) * | 2019-05-06 | 2020-11-12 | Ntt Docomo, Inc. | Mobile communication core network device and method for managing wireless communications after insertion of an intermediate-session management function |
Non-Patent Citations (3)
Title |
---|
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study on Restoration of Profiles related to UDR (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 29.821, vol. CT WG4, no. V0.2.0, 12 March 2021 (2021-03-12), pages 1 - 26, XP051999314 * |
ERICSSON: "UDR Subscriptions", 3GPP DRAFT; C4-190172-UDR-SUBSCRIPTIONS-29505, vol. CT WG4, 15 February 2019 (2019-02-15), Montreal, Canada, pages 1 - 7, XP051598681 * |
HUAWEI: "Discussion on Subscription to notifications Notifications for Nudr", 3GPP DRAFT; C4-183220_DISCUSSION NUDR SUBSCRIPTION TO NOTIFICATION, vol. CT WG4, 15 April 2018 (2018-04-15), KunMing, P.R. China, pages 1 - 5, XP051425754 * |
Also Published As
Publication number | Publication date |
---|---|
JP2024518771A (ja) | 2024-05-02 |
CN115250466A (zh) | 2022-10-28 |
EP4333469A1 (en) | 2024-03-06 |
US20240195893A1 (en) | 2024-06-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9934107B1 (en) | Designating backup nodes and backing up in parallel in a high-availability environment | |
TWI777935B (zh) | 業務處理方法、裝置及系統 | |
JP4570312B2 (ja) | コンピュータシステムにおいてボリュームスナップショット依存関係を提供する方法および装置 | |
US8533171B2 (en) | Method and system for restarting file lock services at an adoptive node during a network filesystem server migration or failover | |
WO2016070375A1 (zh) | 一种分布式存储复制系统和方法 | |
CN110825420A (zh) | 分布式集群的配置参数更新方法、装置、设备及存储介质 | |
JP6225262B2 (ja) | 分散データグリッドにおいてデータを同期させるためにパーティションレベルジャーナリングをサポートするためのシステムおよび方法 | |
WO2010015143A1 (zh) | 一种分布式文件系统及其数据块一致性管理的方法 | |
JP2002091938A (ja) | フェールオーバを処理するシステムおよび方法 | |
WO2019020081A1 (zh) | 分布式系统及其故障恢复方法、装置、产品和存储介质 | |
CN111131399A (zh) | 一种区块链中共识节点动态增加方法及装置 | |
WO2012171349A1 (zh) | 一种分布式自增计数的实现方法、装置及系统 | |
US20190386875A1 (en) | Methods for managing storage virtual machine configuration changes in a distributed storage system and devices thereof | |
US8612799B2 (en) | Method and apparatus of backing up subversion repository | |
WO2024103594A1 (zh) | 容器容灾方法、系统、装置、设备及计算机可读存储介质 | |
US11500812B2 (en) | Intermediate file processing method, client, server, and system | |
WO2018157605A1 (zh) | 一种集群文件系统中消息传输的方法及装置 | |
EP3896571B1 (en) | Data backup method, apparatus and system | |
WO2022228417A1 (zh) | 用户数据容灾方法、装置、网元设备及存储介质 | |
CN111226200B (zh) | 为分布式应用创建一致性快照的方法、装置和分布式系统 | |
WO2022227719A1 (zh) | 数据备份方法、系统及相关设备 | |
CN114090545A (zh) | 分布式数据库的维护方法、装置、存储介质及程序产品 | |
TW201828087A (zh) | 分布式儲存系統的服務節點切換方法及裝置 | |
CN117667509A (zh) | 一种快照数据备份方法、装置、电子设备及存储介质 | |
CN115495282A (zh) | 一种远程复制源卷到多目标卷的方法、服务器及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22794887 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18556543 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023565431 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022794887 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022794887 Country of ref document: EP Effective date: 20231127 |