Method, device and system for failure handling for core network

Abstract

The present disclosure relates to a fault processing method, device and system for a core network, and a computer storage medium, and relates to the technical field of communication. The fault processing method comprises: in the case that a home core network of a user equipment is invalid, in response to receiving a registration request message of the user equipment registering to the home core network, sending the registration request message to a second access and mobility management function (AMF) network element located in a visited core network according to a pre-configured corresponding relationship between a first AMF network element located in the home core network and the second AMF network element, wherein the home core network and the visited core network share a base station, and the home core network is invalid in the case that a unified data management function (UDM) network element, a unified data repository function (UDR) network element and an authentication server function (AUSF) network element of the home core network are not invalid and other core network elements are invalid; and receiving and sending a registration accept message from the second AMF network element to the user equipment.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to fault handling methods, apparatus and systems for core networks, and computer-storable media. Background Technology

[0002] In 5G systems, abnormal shutdowns of core network elements may occur due to natural disasters, equipment failures, or human-caused damage, leading to core network failure and thus an inability to provide services to users.

[0003] In related technologies, if the home core network of a user equipment fails and cannot provide services, the base station will prevent the user equipment from accessing the failed home core network. Summary of the Invention

[0004] In related technologies, if there are no other available networks within the coverage area of ​​a base station, user equipment will be unable to obtain communication services, resulting in service interruption.

[0005] To address the aforementioned technical issues, this disclosure proposes a solution to reduce service interruption time caused by core network failure.

[0006] According to a first aspect of this disclosure, a fault handling method for a core network is provided, comprising: in the event that the home core network of a user equipment (UE) fails, in response to receiving a registration request message from the UE registering to the home core network, sending the registration request message to the second AMF network element according to a pre-configured correspondence between a first Access and Mobility Management Function (AMF) network element located in the home core network and a second AMF network element located in the visited core network, wherein the home core network and the visited core network share a base station, and the home core network fails when the Unified Data Management Function (UDM) network element, Unified Data Repository Function (UDR) network element, and Authentication Service Function (AUSF) network element of the home core network are not failed and other core network elements are failed; receiving and sending a registration acceptance message from the second AMF network element to the UE.

[0007] In some embodiments, the fault handling method further includes: receiving the correspondence from a first AMF network element or a second AMF network element, wherein the correspondence is determined based on a preset protocol, the preset protocol being used to describe one or more AMF network element groups that synchronize configuration data, wherein the first AMF network element and the second AMF network element in the same AMF network element group synchronize configuration data, and the first AMF network element and the second AMF network element in different AMF network element groups do not synchronize configuration data.

[0008] In some embodiments, the correspondence and configuration data include the globally unique AMF identifier (GUAMI) of the first AMF network element and its corresponding second AMF network element.

[0009] In some embodiments, sending the registration request message to the second AMF network element according to the pre-configured correspondence between a first AMF network element located in the home core network and a second AMF network element located in the visited core network includes: if the registration request message includes a globally unique AMF identifier (GUAMI) or a 5G short temporary mobile subscription identifier (5G-S-TMSI) for mapping to the first AMF network element, determining the second AMF network element corresponding to the first AMF network element as the target AMF network element according to the correspondence; and sending the registration request message to the target AMF network element.

[0010] In some embodiments, sending the registration request message to the second AMF network element according to the pre-configured correspondence between the first AMF network element located in the home core network and the second AMF network element located in the visited core network includes: if the registration request does not include a globally unique AMF identifier (GUAMI) or a 5G short temporary mobile subscription identifier (5G-S-TMSI) for mapping to the first AMF network element, selecting one of the second AMF network elements in the correspondence as the target AMF network element; and sending the registration request message to the target AMF network element.

[0011] In some embodiments, the fault handling method further includes: determining that the home core network has failed upon receiving a failure notification message from the home core network; or determining that the home core network has failed if no heartbeat message is received from the home core network within a preset time.

[0012] In some embodiments, the registration request message is used to trigger the second AMF network element to assign an identity identifier based on the first AMF network element to the user equipment, and the registration acceptance message includes the identity identifier.

[0013] In some embodiments, the fault handling method is performed by the base station.

[0014] According to a second aspect of this disclosure, a fault handling apparatus for a core network is provided, comprising: a first sending module configured to, in the event that the home core network of a user equipment (UE) fails, respond to receiving a registration request message from the UE registering to the home core network, and send the registration request message to a second AMF network element according to a pre-configured correspondence between a first Access and Mobility Management Function (AMF) network element located in the home core network and a second AMF network element located in the visited core network, wherein the home core network and the visited core network share a base station, and the home core network fails when the Unified Data Management Function (UDM) network element, Unified Data Repository Function (UDR) network element, and Authentication Service Function (AUSF) network element of the home core network are not failed and other core network elements are failed; a receiving module configured to receive a registration acceptance message from the second AMF network element; and a second sending module configured to send the registration acceptance message to the UE.

[0015] According to a third aspect of this disclosure, a fault handling apparatus for a core network is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute the fault handling method described in any of the above embodiments based on instructions stored in the memory.

[0016] According to a fourth aspect of this disclosure, a fault handling system for a core network is provided, comprising: the fault handling apparatus described in any of the above embodiments.

[0017] In some embodiments, the fault handling system further includes: a second AMF network element, located in the visited core network, configured to assign an identity identifier based on the first AMF network element to the user equipment according to a registration request message from the fault handling device, and generate and send a registration acceptance message including the identity identifier to the fault handling device.

[0018] In some embodiments, the second AMF network element is further configured to: determine whether the user equipment is in a roaming state based on the registration request message from the fault handling device; if the user equipment is in a roaming state, authenticate the user equipment with the unified data management function UDM network element, unified data storage function UDR network element, and authentication service function AUSF network element located in the home core network of the user equipment through roaming mode, and generate the identity identifier of the user equipment based on the first AMF network element.

[0019] In some embodiments, the fault handling system further includes: a first AMF network element located in the home core network of the user equipment, configured to synchronize configuration data with a second AMF network element located in the visited core network based on a preset protocol to obtain a correspondence between the first AMF network element and the second AMF network element, wherein the preset protocol is used to describe one or more AMF network element groups that synchronize configuration data, the first AMF network element and the second AMF network element in the same AMF network element group synchronize configuration data, and the first AMF network element and the second AMF network element in different AMF network element groups do not synchronize configuration data.

[0020] According to a fifth aspect of this disclosure, a computer-storeable medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the fault handling method described in any of the above embodiments.

[0021] In the above embodiments, the service interruption time due to core network failure is reduced. Attached Figure Description

[0022] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.

[0023] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description, wherein:

[0024] Figure 1 This is a flowchart illustrating a fault handling method for a core network according to some embodiments of the present disclosure;

[0025] Figure 2 This is a block diagram illustrating a fault handling apparatus for a core network according to some embodiments of the present disclosure;

[0026] Figure 3 This is a block diagram illustrating a fault handling apparatus for a core network according to other embodiments of the present disclosure;

[0027] Figure 4 This is a block diagram illustrating a fault handling system for a core network according to some embodiments of the present disclosure;

[0028] Figure 5 This is a signaling diagram illustrating a fault handling method for a core network according to some embodiments of the present disclosure;

[0029] Figure 6 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure. Detailed Implementation

[0030] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0031] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0032] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0033] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0034] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0035] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0036] Figure 1 This is a flowchart illustrating a fault handling method for a core network according to some embodiments of the present disclosure.

[0037] like Figure 1 As shown, the fault handling method for the core network includes steps S110-S130. In some embodiments, the fault handling method is performed by the base station.

[0038] In step S110, if the home core network of the user equipment (UE) fails, in response to receiving a registration request message from the UE registering to the home core network, a registration request message is sent to the second AMF network element according to the pre-configured correspondence between the first AMF (Access and Mobility Management Function) network element in the home core network and the second AMF network element in the visited core network. The home core network and the visited core network share a base station. The home core network fails if the UDM (Unified Data Management) network element, UDR (Unified Data Repository) network element, and ASF (Authentication Server Function) network element in the home core network are not failed, and other core network elements fail. In some embodiments, the base station is a RAN (Radio Access Network) node.

[0039] In some embodiments, step S110 can be implemented in the following manner.

[0040] First, if the registration request message includes a GUAMI (Globally Unique AMF Identifier) ​​or 5G-S-TMSI (5G-Shortened-Temporary Mobile Subscriber Identity) for mapping to the first AMF network element, the second AMF network element corresponding to the first AMF network element is determined as the target AMF network element based on the correspondence. In this case, the base station can map the GUAMI or 5G-S-TMSI of the first AMF network element to a valid first AMF network element.

[0041] Then, a registration request message is sent to the target AMF network element.

[0042] In some embodiments, step S110 can also be implemented in the following manner.

[0043] First, if the registration request does not include a GUAMI or 5G-S-TMSI for mapping to the first AMF network element, a second AMF network element from the corresponding relationship is selected as the target AMF network element. In this case, the base station cannot be effectively mapped to the first AMF network element.

[0044] Then, a registration request message is sent to the target AMF network element.

[0045] In some embodiments, the home core network is determined to be faulty upon receiving a failure notification message from the home core network; or the home core network is determined to be faulty if no heartbeat message is received from the home core network within a preset time.

[0046] In some embodiments, the registration request message is used to trigger the second AMF network element to assign an identity identifier based on the first AMF network element to the user equipment, and the registration acceptance message includes the identity identifier. For example, the GUAMI of the first AMF network element can be used to generate a 5G-GUTI for the user equipment. In this way, the continuity of the user equipment identity data can be guaranteed.

[0047] In step S120, a registration acceptance message is received from the second AMF network element.

[0048] In step S130, a registration acceptance message from the second AMF network element is sent to the user equipment.

[0049] In the above embodiments, by pre-configuring the correspondence between the first AMF network element located in the home core network and the second AMF network element located in the visited core network, the second AMF network element in the correspondence can be used to assist in completing the registration process of the user equipment when the home core network of the user equipment fails, thereby reducing the service interruption time caused by the failure of the home core network.

[0050] In some embodiments, the aforementioned correspondence can be received from either a first AMF network element or a second AMF network element. This correspondence is determined based on a preset protocol, which describes one or more AMF network element groups for synchronizing configuration data. Configuration data synchronization occurs between the first and second AMF network elements within the same AMF network element group, but not between the first and second AMF network elements in different AMF network element groups. For example, the preset protocol may be an inter-operator disaster recovery protocol.

[0051] In some embodiments, the above correspondence and configuration data include the GUAMI of the first AMF network element and its corresponding second AMF network element.

[0052] In the above embodiments, by synchronizing configuration data between AMFs across operators and allowing two AMF configurations to run simultaneously, the continuity of UE identity data is ensured, minimizing the impact of core network failures on the UE. Furthermore, by utilizing the existing network architecture that allows shared base stations to simultaneously access multiple operator core networks, the problem of UEs being unable to obtain service during core network failures is solved, reducing service interruption time caused by network failures. Additionally, disaster recovery is achieved through base stations and the core network, eliminating the need for the UE to be aware of core network failures and the disaster recovery process, thus improving the user experience.

[0053] Figure 2 This is a block diagram illustrating a fault handling apparatus for a core network according to some embodiments of the present disclosure.

[0054] like Figure 2 As shown, the fault handling device 21 for the core network includes a first transmitting module 211, a receiving module 212, and a second transmitting module 213.

[0055] The first sending module 211 is configured to, in the event of a failure of the user equipment's home core network, respond to receiving a registration request message from the user equipment to register with the home core network, and according to a pre-configured correspondence between a first AMF network element located in the home core network and a second AMF network element located in the visited core network, send a registration request message to the second AMF network element, for example, by performing the following: Figure 1 Step S110 is shown. The home core network and the visited core network share a base station. If the UDM, UDR, and AUSF network elements of the home core network are not invalid and other core network elements are invalid, the home core network becomes invalid.

[0056] The receiving module 212 is configured to receive a registration acceptance message from the second AMF network element, for example, by performing the following: Figure 1 The step S120 shown.

[0057] The second sending module 213 is configured to send a registration and acceptance message to the user equipment, for example, by performing the following: Figure 1 The step S130 shown.

[0058] Figure 3 This is a block diagram illustrating a fault handling apparatus for a core network according to other embodiments of the present disclosure.

[0059] like Figure 3 As shown, the fault handling apparatus 31 for the core network includes a memory 311 and a processor 312 coupled to the memory 311. The memory 311 is used to store instructions for executing embodiments of fault handling methods for the core network. The processor 312 is configured to execute fault handling methods for the core network in any of the embodiments of this disclosure based on the instructions stored in the memory 311.

[0060] Figure 4 This is a block diagram illustrating a fault handling system for a core network according to some embodiments of the present disclosure.

[0061] like Figure 4As shown, the fault handling system 4 for the core network includes a fault handling device 41 for the core network. The fault handling device 41 is configured to perform fault handling methods for the core network as described in any of the embodiments of this disclosure. For example, the fault handling device 41 is structurally or functionally similar to fault handling devices 21 and 31. In some embodiments, the fault handling device 41 is deployed at a base station.

[0062] In some embodiments, the fault handling system 4 further includes a second AMF network element 42. The second AMF network element is located in the visited core network of the user equipment. The second AMF network element 42 is configured to assign an identity identifier based on the first AMF network element to the user equipment according to a registration request message from the fault handling device 41, and generate and send a registration acceptance message including the identity identifier to the fault handling device 41.

[0063] In some embodiments, the second AMF network element 42 is further configured to determine whether the user equipment is in a roaming state based on the registration request message from the fault handling device 41; if the user equipment is determined to be in a roaming state, the user equipment is authenticated by the UDM network element, UDR network element, and AUSF network element located in the user equipment's home core network using a roaming method, and an identity identifier of the user equipment based on the first AMF network element is generated. For example, the user equipment's roaming state can be determined based on the ID of the selected PLMN (Public Land Mobile Network) in the registration request message.

[0064] In some embodiments, the fault handling system 4 further includes a first AMF network element 43. The first AMF network element 43 is located in the home core network of the user equipment and is configured to synchronize configuration data with a second AMF network element located in the visited core network based on a preset protocol, thereby establishing a correspondence between the first and second AMF network elements. The preset protocol describes one or more AMF network element groups for synchronizing configuration data. Configuration data synchronization occurs between the first and second AMF network elements within the same AMF network element group, but not between the first and second AMF network elements in different AMF network element groups.

[0065] Figure 5 This is a signaling diagram illustrating a fault handling method for a core network according to some embodiments of the present disclosure.

[0066] like Figure 5 As shown, the fault handling method for the core network includes steps S501-S509.

[0067] In step S501, the V-AMF (Visited AMF) network element and the H-AMF (Home AMF) network element synchronize configuration data based on a preset protocol to obtain the correspondence between V-AMF network elements and H-AMF network elements. The V-AMF network element is the AMF network element located in the visited core network of the user equipment, such as the second AMF network element mentioned above. The H-AMF network element is the AMF network element located in the home core network of the user equipment, such as the first AMF network element mentioned above. The preset protocol is used to describe one or more AMF network element groups that synchronize configuration data. Within the same AMF network element group, H-AMF network elements and V-AMF network elements synchronize configuration data; however, H-AMF network elements and V-AMF network elements in different AMF network element groups do not synchronize configuration data.

[0068] In step S502a, the V-AMF network element sends the corresponding relationship to the base station.

[0069] In step S502b, the H-AMF network element sends the corresponding relationship to the base station.

[0070] Of the above steps S502a and S502b, one can be performed, or both can be performed.

[0071] In step S503, the base station determines whether the home core network has failed. If the home core network is determined to be failed, steps S504-S509 are executed.

[0072] In step S504, the user equipment sends a registration request message to the base station.

[0073] In step S505, the base station selects a V-AMF network element from the visited core network as the target AMF network element. In some embodiments, both the home core network and the visited core network include multiple AMF network elements.

[0074] In step S506, the base station sends a registration request message to the selected V-AMF network element.

[0075] In step S507, the selected V-AMF network element authenticates the user equipment with the H-UDM (HomeUDM), H-UDR (Home UDR), and H-AUSF (Home AUSF) network elements located in the user equipment's home core network, and generates the user equipment's identity identifier based on the H-AMF network element.

[0076] In step S508, the selected V-AMF network element sends a registration acceptance message to the base station.

[0077] In step S509, the base station sends a registration acceptance message to the user equipment.

[0078] Through the above steps, user equipment sessions can be conducted between the base station and the visited core network. Figure 5 Similar descriptions of the various steps can be found in other embodiments, and will not be repeated here.

[0079] Figure 6 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure.

[0080] like Figure 6 As shown, the computer system 60 can be represented in the form of a general computing device. The computer system 60 includes a memory 610, a processor 620, and a bus 600 connecting different system components.

[0081] The memory 610 may include, for example, system memory, non-volatile storage media, etc. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs. The system memory may include volatile storage media, such as random access memory (RAM) and / or cache memory. The non-volatile storage media may store, for example, instructions for executing corresponding embodiments of the fault handling method. Non-volatile storage media include, but are not limited to, disk storage, optical storage, flash memory, etc.

[0082] The processor 620 can be implemented using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete hardware components such as discrete gates or transistors. Accordingly, each module, such as the decision module and the determination module, can be implemented by executing instructions in the central processing unit (CPU) memory to perform the corresponding steps, or by implementing dedicated circuitry to perform the corresponding steps.

[0083] Bus 600 can use any of the various bus architectures. For example, bus architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, and Peripheral Component Interconnect (PCI) bus.

[0084] The computer system 60 may also include an input / output interface 630, a network interface 640, and a storage interface 650. These interfaces 630, 640, and 650, as well as the memory 610 and processor 620, can be connected via a bus 600. The input / output interface 630 provides a connection interface for input / output devices such as a monitor, mouse, and keyboard. The network interface 640 provides a connection interface for various networked devices. The storage interface 650 provides a connection interface for external storage devices such as floppy disks, USB flash drives, and SD cards.

[0085] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations thereof, can be implemented by computer-readable program instructions.

[0086] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, such that execution of the instructions by the processor produces means for implementing the functions specified in one or more boxes of the flowchart and / or block diagram.

[0087] These computer-readable program instructions may also be stored in a computer-readable storage medium. These instructions cause a computer to work in a particular manner to produce an article of manufacture, including instructions that implement the functions specified in one or more boxes in a flowchart and / or block diagram.

[0088] This disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0089] The fault handling method, apparatus, system, and computer storage medium for the core network described in the above embodiments reduce the service interruption time caused by core network failure.

[0090] This concludes the detailed description of the fault handling method, apparatus, system, and computer-storable medium for the core network according to this disclosure. To avoid obscuring the concept of this disclosure, some details known in the art have not been described. Those skilled in the art can fully understand how to implement the technical solutions disclosed herein based on the above description.

Claims

1. A fault handling method for a core network, executed by a base station, comprising: In the event of a failure of the home core network of a user equipment (UE), in response to receiving a registration request message from the UE to register with the home core network, the UE sends the registration request message to the second AMF network element according to a pre-configured correspondence between the first AMF network element located in the home core network and the second AMF network element located in the visited core network. The home core network and the visited core network share a base station. The home core network fails when the unified data management function (UDM) network element, unified data warehousing function (UDR) network element, and authentication service function (AUSF) network element of the home core network are not failed, but other core network elements are failed. Receive and send a registration acceptance message from the second AMF network element to the user equipment.

2. The fault handling method according to claim 1 further includes: The correspondence is received from the first AMF network element or the second AMF network element, wherein the correspondence is determined based on a preset protocol, the preset protocol being used to describe one or more AMF network element groups that synchronize configuration data, wherein the first AMF network element and the second AMF network element in the same AMF network element group synchronize configuration data, and the first AMF network element and the second AMF network element in different AMF network element groups do not synchronize configuration data.

3. The fault handling method according to claim 2, wherein, The correspondence and configuration data include the globally unique AMF identifier (GUAMI) of the first AMF network element and its corresponding second AMF network element.

4. The fault handling method according to claim 1, wherein, Sending the registration request message to the second AMF network element according to the pre-configured correspondence between the first AMF network element located in the home core network and the second AMF network element located in the visited core network includes: If the registration request message includes a globally unique AMF identifier (GUAMI) or a 5G short temporary mobile subscription identifier (5G-S-TMSI) for mapping to the first AMF network element, the second AMF network element corresponding to the first AMF network element is determined as the target AMF network element according to the correspondence. Send the registration request message to the target AMF network element.

5. The fault handling method according to claim 1, wherein, Sending the registration request message to the second AMF network element according to the pre-configured correspondence between the first AMF network element located in the home core network and the second AMF network element located in the visited core network includes: If the registration request does not include a globally unique AMF identifier (GUAMI) or a 5G short temporary mobile subscription identifier (5G-S-TMSI) for mapping to the first AMF network element, select a second AMF network element from the correspondence as the target AMF network element. Send the registration request message to the target AMF network element.

6. The fault handling method according to claim 1 further includes: Upon receiving a failure notification message from the home core network, it is determined that the home core network has failed. or If no heartbeat message is received from the home core network within a preset time, the home core network is determined to be faulty.

7. The fault handling method according to claim 1, wherein, The registration request message is used to trigger the second AMF network element to allocate an identity identifier based on the first AMF network element to the user equipment, and the registration acceptance message includes the identity identifier.

8. A fault handling device for a core network, the fault handling device being deployed at a base station, comprising: The first sending module is configured to, in the event that the home core network of a user equipment fails, respond to receiving a registration request message from the user equipment registering to the home core network, and send the registration request message to the second AMF network element according to a pre-configured correspondence between a first Access and Mobility Management Function (AMF) network element located in the home core network and a second AMF network element located in the visited core network. The home core network and the visited core network share a base station. The home core network fails when the Unified Data Management Function (UDM) network element, Unified Data Repository Function (UDR) network element, and Authentication Service Function (AUSF) network element of the home core network are not failed, but other core network elements are failed. The receiving module is configured to receive a registration acceptance message from the second AMF network element; The second sending module is configured to send the registration acceptance message to the user equipment.

9. A fault handling device for a core network, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute the fault handling method as described in any one of claims 1 to 7 based on instructions stored in the memory.

10. A fault handling system for a core network, comprising: The fault handling apparatus as described in claim 8 or 9.

11. The fault handling system according to claim 10, further comprising: The second AMF network element, located in the visitor core network, is configured to assign an identity identifier based on the first AMF network element to the user equipment according to a registration request message from the fault handling device, and generate and send a registration acceptance message including the identity identifier to the fault handling device.

12. The fault handling system according to claim 11, wherein, The second AMF network element is also configured as follows: Based on the registration request message from the fault handling device, determine whether the user equipment is in a roaming state; If it is determined that the user equipment is in a roaming state, the user equipment is authenticated by the Unified Data Management Function (UDM), Unified Data Repository Function (UDR), and Authentication Service Function (AUSF) network elements located in the home core network of the user equipment through roaming mode, and an identity identifier of the user equipment based on the first AMF network element is generated.

13. The fault handling system according to any one of claims 10-12, further comprising: The first AMF network element, located in the home core network of the user equipment, is configured to synchronize configuration data with the second AMF network element located in the visited core network based on a preset protocol, thereby obtaining the correspondence between the first AMF network element and the second AMF network element. The preset protocol is used to describe one or more AMF network element groups that synchronize configuration data. The first AMF network element and the second AMF network element in the same AMF network element group synchronize configuration data, while the first AMF network element and the second AMF network element in different AMF network element groups do not synchronize configuration data.

14. A computer-storeable medium having stored thereon computer program instructions that, when executed by a processor, implement the fault handling method as described in any one of claims 1 to 7.

Images