Disaster recovery method and system for 5GC remote deployment and storage medium
By configuring backup mechanisms and data sharing structures for AMF and NRF in the 5G core network, the business interruption and signaling storm problems during disaster recovery switching are solved, and data sharing and service recovery between UDR and UDSF are realized between dual DCs, improving the User experience and network stability.
Patent Information
- Application Number
- CN202411381561.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2024-11-15
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In the 5G core network, when user context data and contract data are shared between dual DCs, disaster recovery and replacement can easily lead to service interruption and signaling storm impacts, affecting network stability and user experience.
Through the NRF registration function, each main AMF is configured to back up AMF, and a 1+1 dual active backup mechanism is adopted to replace the main NRF and AMF when judging failures by heartbeat detection to ensure service recovery; at the same time, the clock is synchronized using the NTP protocol. , realize clock consistency between AMF and NRF; for UDR, one master and multiple slave structure is adopted, binary logs are transmitted in real time and confirmed and collected to ensure data sharing and recovery.
It realizes data sharing between UDR and UDSF between dual DCs, avoids business interruptions, improves user experience and the security and reliability of core network equipment, is suitable for key business scenarios, and improves the high availability of the network.
Smart Images

Figure CN118972887A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technology, and in particular to a disaster recovery method, system and storage medium for 5GC remote deployment. Background Art
[0002] The existing core network equipment supply basically follows the POOL method of network element pool group in the 3GPP standard. When the same type of network element fails, the terminal selects other network elements in the same pool group to re-bear the service. However, after the failure causes the timer to time out, AMF usually transmits NAS messages to notify the terminal to re-establish the session and request other network elements in the pool group to allocate resources. In this way, there is a process of rebuilding the chain between the background application and the terminal. For some critical services that require very high service continuity, such as train control data transmission, re-establishing the session will cause service interruption and require the train to slow down or stop. Therefore, it is necessary to optimize the design under the premise of following the 3GPP protocol. In addition, if the terminal re-establishes the session during DC switching, when the service load is high, a large number of establishment requests will be released in a very short time, which will cause a signaling storm impact on the signaling plane, which is not conducive to the stable operation of the network and also brings challenges to the complexity of daily maintenance. Summary of the invention
[0003] In view of the above-mentioned technical deficiencies, the technical problem to be solved by the present invention is to provide a disaster recovery method, system and storage medium for 5GC remote deployment. It aims to solve the problem of sharing user context data and contract data between dual DCs, discontinuous business interruption during disaster recovery switching, and the problem of signaling storms that easily impact equipment load when business is restored in large business scenarios.
[0004] In order to solve the above technical problems, the present invention adopts the following technical solution: The present invention provides a disaster recovery method for 5GC remote deployment, including: Through the registration function of NRF, each active AMF is configured with its backup AMF. The active AMF performs heartbeat detection with the NRF so that the NRF can determine whether the current active AMF is faulty. If the current active AMF is faulty, the other control plane NFs except AMF will send the traffic to the backup AMF for service recovery. Among them, the NRF adopts 1+1 active-active backup, and the NF client determines whether the current active NRF is faulty through heartbeat detection. If the current active NRF is faulty, the backup NRF will replace the active NRF to continue the registration, deregistration and discovery process; at the same time, the NTP protocol is also used to synchronize the clocks between the active NRF and the backup NRF.
[0005] Furthermore, both the active AMF and the backup AMF establish an SCTP link with the same RAN and are registered on the same NRF; the other control plane NFs obtain the backup relationship between the AMFs through the NRF; the active AMF, while interacting with other control plane NFs, carries the information of its backup AMF to other control plane NFs through interactive signaling.
[0006] Furthermore, in the registration process of the NRF, the NF client detects whether the current active NRF is faulty through heartbeat. If the current active NRF is faulty, the NF client initiates an update request to the corresponding mutual backup NRF, and the mutual backup NRF obtains the information of the NF client; If the request fails, the NF client re-sends a registration request to the corresponding mutual backup NRF; if the request succeeds, the NF client does not perform any operation.
[0007] Further, when the active NRF receives a deregistration message from the NF client, or the internal timer of the active NRF expires, a deletion command is sent to the UDSF; The UDSF initiates a change notification broadcast to all connected and subscribed UDSF clients. After receiving the broadcast, the mutual backup NRF uses the Key value carried in the broadcast to search for and delete the information of the NF client in the memory.
[0008] Further, when the internal timer of the mutual backup NRF expires, the NF client notifies the active NRF to delete the information; Among them, NRF sets the timer and the number of retries. When the NF client registers with NRF, in addition to the NF client actively deregistering, NRF also regularly sends heartbeat messages to the NF client to detect its status; if the heartbeat message sent by NRF to the NF client exceeds the preset time and no response is received, and this situation is repeated for a set number of times, the NF client is judged to be faulty and deregistered; at the same time, the backup NRF is notified to synchronize the registration data; if the NRF itself fails, all NF clients will query the mutual backup NRF to discover and subscribe to other NF information.
[0009] Furthermore, when the active NRF fails, the NF client determines whether the active NRF is available through heartbeat detection; If it is determined that the active NRF is unavailable, a discovery process is initiated to the backup NRF.
[0010] Furthermore, the mutual standby NRF directly executes the discovery process inside it according to the information of other NF clients held in the registration process, and returns a response to the NF client.
[0011] Furthermore, for the user data storage function UDR, a one-master-multiple-slave UDR structure is adopted, including: the master UDR generates a binary log bin log through the DUMP thread, and transmits it to each slave Slave UDR node in real time; at the same time, it includes an independent confirmation collection thread, and the confirmation collection thread is used to receive replication completion confirmation feedback from all slave Slave UDR nodes.
[0012] A 5GC remotely deployed disaster recovery system includes: AMF backup configuration module, used to configure the backup AMF for each active AMF through the registration function of NRF; An AMF status monitoring module is used to perform heartbeat detection between the active AMF and the NRF so that the NRF can determine whether the current active AMF is faulty. If the current active AMF is faulty, the other control plane NFs except the AMF will send the traffic to the backup AMF for service recovery; NRF1+1 dual-active backup management module, used to implement the 1+1 dual-active backup mechanism of the NRF. The NF client determines whether the current active NRF is faulty through heartbeat detection. If the current active NRF is faulty, the backup NRF replaces the active NRF to continue the registration, deregistration and discovery process; The NRF time synchronization module is used to synchronize clocks between the active NRF and the standby NRF using the NTP protocol.
[0013] A computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement a disaster recovery method for 5GC off-site deployment.
[0014] The beneficial effects of the present invention are: 1. The present invention ensures data sharing between UDR and UDSF between dual DCs, and does not interrupt services in case of failure or maintenance, thus improving user experience and being particularly suitable for critical service scenarios; 2. The present invention can manually control the switching process and sequence according to the needs of equipment maintenance and overhaul, which is convenient for arranging the verification of the maintenance operation effect and can flexibly select a specific operation plan according to maintenance needs; 3. The present invention improves the user experience of end users, increases the security, reliability and high availability of core network equipment, and is more suitable for engineering design of key business bearers. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0016] Figure 1 A logical networking diagram of a 5GC off-site deployment disaster recovery method provided in an embodiment of the present invention.
[0017] Figure 2 This is a diagram of the dual NRF registration mechanism in Example 1.
[0018] Figure 3 This is a flow chart of the one-way static synchronization method of UDR data in Example 1.
[0019] Figure 4 This is a flow chart of the UDSF bidirectional dynamic synchronization method in Example 1.
[0020] Figure 5 A schematic diagram of service processing after each primary AMF in Example 1 is configured with its backup AMF.
[0021] Figure 6 This is the registration flow chart in Example 1.
[0022] Figure 7 This is the cancellation flow chart in Example 1.
[0023] Figure 8 This is a flow chart of the discovery process in Example 1.
[0024] Description in the figure: RAN: Radio Access Network, NF: Network Function, UDM: Unified Data Management Platform, PCF: Policy Control Function, AUSF: Authentication Service Function, SMSF: Short Message Service Function, UPF: User Plane Function, SMF: Session Management Function, AMF: Access and Mobility Management Function, NRF: Network Warehousing Function, CHF: Billing Function, 5GC: 5G Core Network, NSSF: Network Slice Selection Function, STP: Information Transfer Node, UDR: Unified Data Warehouse, UDSF: Unstructured Data Storage Function. DETAILED DESCRIPTION
[0025] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0026] Example 1 like Figures 1 to 8 As shown, the present invention provides a disaster recovery method for 5GC remote deployment, including: like Figure 1 As shown, the backup AMF is configured for each active AMF through the registration function of NRF, and heartbeat detection is performed between the active AMF and NRF so that NRF can determine whether the current active AMF is faulty. If the current active AMF is faulty, other control plane NFs except AMF will send the traffic to the backup AMF for service recovery. The N before the functional module in the figure refers to the service-oriented interface, which is a standard interface in HTTP mode. The interface related to the short message service function SMSF is Nsmsf, and the same applies to others.
[0027] Among them, NRF adopts 1+1 active-active backup. The NF client determines whether the current active NRF is faulty through heartbeat detection. If the current active NRF is faulty, the backup NRF will replace the active NRF to continue the registration, deregistration and discovery process. The NTP protocol is also used to synchronize the clocks between the active NRF and the backup NRF to ensure that the timing logic of the two is consistent when performing NF client status judgment and management operations.
[0028] like Figure 2 As shown, this embodiment adopts a dual NRF registration mechanism: in dual DCs, NRF uses a distributed database to synchronize NF service PROFILE data, and each service network element in the control plane can complete the service request and discovery process under the coordination of any NRF. When the main NRF fails, the server's NF PROFILE change is received by another NRF and an update notification is sent to the consumer NF; NRF adopts 1+1 active-active backup, which is characterized by the fact that both NRFs are connected to the NF client, thereby avoiding the need to rebuild the link when switching between the two backups; the main NRF and the backup NRF are configured and listen to different IP addresses; the NF client needs to configure the address of the main NRF and the address of the backup NRF at the same time, and give priority to the main NRF. There is no direct link between the two NRFs, but data is shared through UDSF. The NTP protocol needs to be used to ensure the clock synchronization of the main NRF and the backup NRF to avoid problems caused by timeout release.
[0029] In order to achieve more refined management and optimization in 5G networks, especially in multi-region and multi-DC deployment scenarios, to ensure efficient use of network resources and user service quality, a network element selection principle is provided: in addition to selecting network elements according to protocol standards, the following IEs are added, as shown in Table 1.
[0030] Table 1: Network element selection table.
[0031]
[0032] When this switch is turned on, you can set the preference for network elements in the same area or in different areas, and the relevant parameter configurations of the same type of network elements between two DCs remain consistent.
[0033] like Figure 3 As shown in the figure, for the storage and management of structured user data and network configuration data, a one-way static synchronization method of UDR data is adopted, that is, a one-master-multiple-slave UDR architecture, semi-synchronous replication is enabled, the DUMP thread transmits the binary log bin log to the SLAVE UDR, and an independent confirmation collection thread is generated to receive feedback information from the SLAVE UDR. Specifically, for the user data storage function UDR, a one-master-multiple-slave architecture design is adopted to implement a semi-synchronous replication strategy for data to enhance data backup and recovery capabilities; in specific implementation, the master UDR generates a binary log bin log through the DUMP thread and transmits it to each slave Slave UDR node in real time; in addition, the design includes an independent confirmation collection thread, which is responsible for monitoring and collecting replication completion confirmation feedback from all Slave UDRs to ensure the integrity and consistency of the data replication process; this mechanism ensures that even if the master UDR fails, it can quickly switch to any ready Slave UDR to maintain the continuity of data services, further strengthening the disaster recovery system of the entire 5GC system.
[0034] like Figure 4 As shown in the figure, the UDSF bidirectional dynamic synchronization method is used to store and manage unstructured data, that is, the context data consistent hash is modulo 2^32, and the UDSF Cluster is modulo 2^14, that is, 16384; the UDSF Cluster divides itself into 16384 slots. The hash value calculated by the CRC16 algorithm is modulo 16384, and the value obtained after the modulo is the corresponding slot, and then each UDSF node will be responsible for processing a part of the slots. Each UDSF instance maintains a mapping relationship between Slot and UDSF NODE. If a key is set on Node A, but the slot calculated by CRC16 is maintained by Node B, then a prompt will appear indicating that the operation needs to be performed on Node B.
[0035] When a master node holding a slot goes offline, the cluster will select a slave node from the slave nodes to replace it. The UDSF cluster uses an election-voting algorithm to select slave nodes. A slave node must obtain votes from the majority of master nodes, including the failed master node, before it can be promoted to a master node. Assuming the cluster scale is 3 masters and 3 slaves, at least 2 master nodes must survive to perform fault recovery. If 2 master nodes are deployed on the same server during deployment, the cluster cannot perform fault recovery after the server unfortunately goes down.
[0036] If a master node in a UDSF cluster is unavailable, it will only affect access to the data in the relevant slots it is responsible for, and will not affect access to other nodes.
[0037] like Figure 5 As shown, both the active AMF and the backup AMF establish SCTP links with the same RAN and are registered on the same NRF; other control plane NFs obtain the backup relationship between AMFs through NRF; the active AMF, while interacting with other control plane NFs, also carries the information of its backup AMF to other control plane NFs through interactive signaling.
[0038] It should be noted that: Under normal circumstances, during the normal operation of the active AMF, the user identification and location information such as SUPI / TAList / 5G-GUTI need to be synchronized to the backup AMF. When the active AMF fails, the backup AMF can perform subsequent business processes for the user through the user backup data. Therefore, in order to complete the user data backup, it is necessary to configure the backup AMF for each active AMF.
[0039] Specifically, the active AMF needs to register the backup relationship with the NRF through the NRF registration function, so that other control plane NFs such as SMF can obtain the backup AMF information through the service discovery function, that is, all network elements inform the backup network element information when registering with the NRF. In this way, if the network element of the active AMF fails during communication, other network elements will query the backup AMF from the NRF and communicate with the backup AMF instead, so that the service can continue. The specific steps are as follows: S1, the active AMF and the backup AMF register with NRF respectively, and carry the active AMF and backup AMF information related to them. The backup AMF registers its backup relationship with the active AMF in NRF at the same time. Other NFs can obtain the backup relationship between the two AMFs through NRF. At the same time, the active AMF will also carry the information of its backup AMF to CPNF through interactive signaling when interacting with CPNF such as SMF.
[0040] S2. Heartbeat detection is performed between the active AMF and NRF. When NRF detects that the heartbeat message between the current AMF and NRF is abnormal, the active AMF is determined to be abnormal and its status is updated.
[0041] S3. When other NFs subscribe to the status of the primary AMF, when an abnormality occurs in the primary AMF, NRF will actively push the abnormal status information of the primary AMF to the subscriber; at the same time, when other control plane NFs such as SMF / PCF / UDM obtain the primary AMF through NRF, NRF will not return the primary AMF information of the current abnormal status, but will return its backup AMF information.
[0042] S4, other control plane NFs such as SMF / PCF / UDM, etc. reselect their backup AMF and interact with the backup AMF after the active AMF fails; the active AMF needs to bring the backup AMF information to the base station through the NG SETUP process so that the base station can continue the business process through the backup AMF when it receives the AMF status notification message or detects that the link is unreachable.
[0043] Through the processing of steps S1 to S4, after a main AMF fails, for the uplink process initiated by the (R)AN, the (R)AN selects the backup AMF to process the service; for the downlink process initiated by other control plane NFs such as SMF, the NF selects the backup AMF of the failed main AMF, and the backup AMF continues to process the service according to the user backup data.
[0044] like Figure 6 As shown, in the NRF registration process, the NF client detects whether the current active NRF is faulty through heartbeat. If the current active NRF is faulty, the NF client initiates an update request to the corresponding standby NRF, and the standby NRF obtains the information of the NF client. If the request fails, the NF client re-sends a registration request to the corresponding mutual backup NRF; if the request succeeds, the NF client does not perform any operation.
[0045] It should be noted that: when NRF is powered on, it connects to UDSF according to its own UDSF address configuration and sends a subscription request PROFILE SUBSCRIBE to UDSF; under normal circumstances, the NF client initiates a registration process to the primary NRF, and the primary NRF serializes its own memory that stores the client information, and then sends a backup message to UDSF, including the storage HSET of the registration information and the change notification PUBLISH; UDSF initiates a change notification PUBLISH to all connected and subscribed Redis clients. After receiving the broadcast, the mutual backup NRF initiates a data acquisition request HGETALL to UDSF, and deserializes the acquired data and stores it in its own memory; and when the primary NRF has abnormal conditions such as program crash, machine power failure, network disconnection, etc., the NF client finds that the primary NRF is no longer available through heartbeat detection, and then initiates an update request to the mutual backup NRF; if the request fails, the NF client needs to re-initiate a registration request to the mutual backup NRF; if the request is successful, the NF client does not need to do any more operations.
[0046] like Figure 7 As shown in the figure, when the active NRF receives the deregistration message from the NF client, or the internal timer of the active NRF expires, it sends a delete command to the UDSF; at this time, the UDSF initiates a change notification broadcast to all connected and subscribed UDSF clients. After receiving the broadcast, the standby NRF uses the Key value carried in the broadcast to find and delete the NF client information in the memory.
[0047] When the internal timer of the mutual backup NRF expires, a similar process is executed, and the main NRF is notified to delete the information in turn. Therefore, the NTP protocol is needed to ensure the clock synchronization of the two NRFs; among them, the NRF sets the timer and the number of retries. The number of retries is the heartbeat timeout and no response is received. It will be re-initiated. If no response is received for more than a certain number of consecutive times, it will be considered invalid. When the NF client registers with the NRF, in addition to the NF client actively deregistering, the NRF also regularly sends heartbeat messages to the NF client to detect its status; if the heartbeat message sent by the NRF to the NF client exceeds the preset time and no response is received, and this situation is repeated for the set number of times, the NF client is judged to be faulty and deregistered; at the same time, the backup NRF is notified to synchronize the registration data; if the NRF itself fails, all NF clients will query the mutual backup NRF to discover and subscribe to other NF information.
[0048] like Figure 8As shown, when the active NRF fails, the NF client determines whether the active NRF is available through heartbeat detection; if it is determined that the active NRF is unavailable, the discovery process is initiated to the backup NRF; the backup NRF directly executes the discovery process within itself based on the information of other NF clients held in the registration process, and returns a response to the NF client.
[0049] It should be noted that: Under normal circumstances, the NF client initiates a discovery process to the primary NRF, and the NRF returns a response; according to the communication protocol standard, for example, when the AMF receives a network access request from a mobile phone through a base station, the next step is to authenticate the mobile phone, which requires querying from UDM / AUSF. The address and port of UDM / AUSF can be configured in advance in the AMF, or the address and port of UDM / AUSF can be queried from the NRF. The professional term for the query process is discovery, i.e. NF DISCOVERY.
[0050] When the main NRF crashes, the machine loses power, the network is disconnected, and other abnormal situations occur, the NF client finds that the main NRF is no longer available through heartbeat detection, and then initiates a discovery process to the backup NRF. Since the backup NRF already holds the information of other NF clients in the registration process, it can directly execute the discovery process internally and return a response to the NF client, thereby ensuring business continuity.
[0051] According to laboratory tests, this disaster recovery solution can realize data sharing between UDR and UDSF between dual DCs, and application services are not interrupted when some network elements of the core network are switched. In addition, the switching process and sequence can be manually controlled according to the needs of equipment maintenance and overhaul, which is convenient for arranging the verification of the maintenance operation effect, and specific operation plans can be flexibly selected according to maintenance needs. It improves the user experience of end users, increases the security, reliability and high availability of core network equipment, and is more suitable for engineering design of key business bearers.
[0052] Example 2 Based on Example 1, this embodiment also provides a disaster recovery system for 5GC remote deployment, including: an AMF backup configuration module, used to configure a backup AMF for each active AMF through the registration function of NRF; The AMF status monitoring module is used to perform heartbeat detection between the active AMF and the NRF so that the NRF can determine whether the current active AMF is faulty. If the current active AMF is faulty, the other control plane NFs except the AMF will send the traffic to the backup AMF for service recovery; NRF1+1 active-active backup management module is used to implement the 1+1 active-active backup mechanism of NRF. The NF client determines whether the current active NRF is faulty through heartbeat detection. If the current active NRF is faulty, the backup NRF will replace the active NRF to continue the registration, deregistration and discovery process. The NRF time synchronization module is used to synchronize the clocks between the active NRF and the standby NRF using the NTP protocol.
[0053] Example 3 This embodiment also provides a storage medium on which a computer program is stored. When the program is executed by a processor, a disaster recovery method for 5GC remote deployment as proposed in the above embodiment is implemented. The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein by equivalents. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A disaster recovery method for 5GC remote deployment, characterized in that: include: Through the registration function of NRF, each active AMF is configured with its backup AMF. The active AMF performs heartbeat detection with the NRF so that the NRF can determine whether the current active AMF is faulty. If the current active AMF is faulty, the other control plane NFs except AMF will send the traffic to the backup AMF for service recovery. Among them, the NRF adopts 1+1 active-active backup, and the NF client determines whether the current active NRF is faulty through heartbeat detection. If the current active NRF is faulty, the backup NRF will replace the active NRF to continue the registration, deregistration and discovery process; at the same time, the NTP protocol is also used to synchronize the clocks between the active NRF and the backup NRF.
2. A disaster recovery method for 5GC remote deployment as claimed in claim 1, characterized in that: Both the active AMF and the backup AMF establish an SCTP link with the same RAN and are registered on the same NRF; the other control plane NF obtains the backup relationship between the AMFs through the NRF; The active AMF, while interacting with other control plane NFs, carries the information of its backup AMF to other control plane NFs through interactive signaling.
3. A disaster recovery method for 5GC remote deployment as claimed in claim 1, characterized in that: In the registration process of the NRF, the NF client detects whether the current active NRF is faulty through heartbeat. If the current active NRF is faulty, the NF client initiates an update request to the corresponding standby NRF, and the standby NRF obtains the information of the NF client; If the request fails, the NF client re-sends a registration request to the corresponding mutual backup NRF; if the request succeeds, the NF client does not perform any operation.
4. A disaster recovery method for 5GC remote deployment as claimed in claim 1, characterized in that: When the active NRF receives a deregistration message from the NF client, or the internal timer of the active NRF expires, it sends a deletion command to the UDSF; The UDSF initiates a change notification broadcast to all connected and subscribed UDSF clients. After receiving the broadcast, the mutual backup NRF uses the Key value carried in the broadcast to search for and delete the information of the NF client in the memory.
5. A disaster recovery method for 5GC remote deployment as claimed in claim 1, characterized in that: When the internal timer of the backup NRF expires, the NF client notifies the active NRF to delete the information; Among them, NRF sets the timer and the number of retries. When the NF client registers with NRF, in addition to the NF client actively deregistering, NRF also regularly sends heartbeat messages to the NF client to detect its status; if the heartbeat message sent by NRF to the NF client exceeds the preset time and no response is received, and this situation is repeated for a set number of times, the NF client is judged to be faulty and deregistered; at the same time, the backup NRF is notified to synchronize the registration data; if the NRF itself fails, all NF clients will query the mutual backup NRF to discover and subscribe to other NF information.
6. A disaster recovery method for 5GC remote deployment as claimed in claim 1, characterized in that: When the active NRF fails, the NF client determines whether the active NRF is available through heartbeat detection; If it is determined that the active NRF is unavailable, a discovery process is initiated to the backup NRF.
7. A disaster recovery method for 5GC remote deployment as described in any one of claim 6, characterized in that: The mutual standby NRF directly executes the discovery process inside it according to the information of other NF clients held in the registration process, and returns a response to the NF client.
8. A disaster recovery method for 5GC remote deployment as described in any one of claim 1, characterized in that: For the user data storage function UDR, a one-master-multiple-slave UDR structure is adopted, including: the master UDR generates a binary log bin log through the DUMP thread and transmits it to each slave Slave UDR node in real time; at the same time, it includes an independent confirmation collection thread, which is used to receive replication completion confirmation feedback from all slave Slave UDR nodes.
9. A system based on a 5GC remote deployment disaster recovery method as described in any one of claims 1 to 8, characterized in that: include: AMF backup configuration module, used to configure the backup AMF for each active AMF through the registration function of NRF; An AMF status monitoring module is used to perform heartbeat detection between the active AMF and the NRF so that the NRF can determine whether the current active AMF is faulty. If the current active AMF is faulty, the other control plane NFs except the AMF will send the traffic to the backup AMF for service recovery; NRF1+1 dual-active backup management module, used to implement the 1+1 dual-active backup mechanism of the NRF. The NF client determines whether the current active NRF is faulty through heartbeat detection. If the current active NRF is faulty, the backup NRF replaces the active NRF to continue the registration, deregistration and discovery process; The NRF time synchronization module is used to synchronize clocks between the active NRF and the standby NRF using the NTP protocol.
10. A computer-readable storage medium storing computer-executable instructions, characterized in that: When the computer executable instructions are executed by the processor, the steps of a disaster recovery method for 5GC off-site deployment as described in any one of claims 1 to 8 are implemented.
Citation Information
Patent Citations
Method and equipment for realizing NF (Network Function) nearby selection and storage medium
CN110876154A
Method and system for backing up AMF in 5G core network
CN111417151A
Data caching method and device
CN112788085A
Information processing method, network element, storage medium and program product
CN113993147A
Implementation method of NRF dual-computer selection strategy for ensuring connection stability
CN116208989A
Cited By
Service request forwarding method and device, electronic equipment and program product
CN121262069A
