Core network fault positioning method and device, equipment, storage medium and program product

Abstract

The invention discloses a core network fault positioning method and device, equipment, a storage medium and a program product, and belongs to the technical field of communication. The method comprises the following steps: constructing a virtual core network based on a target core network; directionally shunting the test flow of the test network element in the target core network to the virtual core network, simulating the target business process in the virtual core network to test the test network element, and generating a test result; and sending a test result to an analysis end, and determining a fault positioning result of the target core network based on the test result through the analysis end. Through the mode, each test network element in the target core network can be independently tested, and compatibility interference between real network elements is eliminated, so that the accuracy of multi-network element fault positioning is improved.

Description

Core network fault location methods, devices, equipment, storage media and program products Technical Field

[0001] This application relates to the field of communication technology, and in particular to a core network fault location method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the expansion of mobile communication networks, the number and complexity of core network elements have increased significantly, making the monitoring of their operational status a crucial aspect of ensuring network reliability. Currently, network testing typically employs dial-up testing systems, which simulate the behavior of user terminals or base stations to verify the service processing capabilities and fault recovery efficiency of network elements.

[0003] In dial-up testing technology, high-frequency directional dial-up testing stands out due to its ability to achieve comprehensive coverage of network elements through directional routing, especially in single-fault scenarios. For example, some solutions employ a bi-path network sampling model, constructing two or more monitoring paths to probe the target network element in parallel. When a single network element fails, the fault feedback trajectories from different paths will form a unique intersection point at that network element, thus enabling rapid location of the fault source.

[0004] However, in actual network operation, concurrent failures of multiple network elements frequently occur. In this case, multiple fault trajectories will form multiple intersection points between multiple network elements, making it difficult to locate the faulty network element, which may ultimately lead to delays, misjudgments, or even failures in fault location. Summary of the Invention

[0005] This application provides a core network fault location method, apparatus, device, storage medium, and program product to at least solve the problem that high-frequency directional dialing test schemes cannot complete the fault location of multiple network elements.

[0006] To address the aforementioned technical problems, this application provides the following: Firstly, embodiments of this application offer a core network fault location method, applied to an execution end, comprising: constructing a virtual core network based on a target core network, the virtual core network including multiple virtual network elements, the virtual core network being networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements corresponding one-to-one with the types of real network elements in the target core network; redirecting test traffic from test network elements in the target core network to the virtual core network, simulating target service processes to test the test network elements in the virtual core network, and generating test results; sending the test results to an analysis end, and determining the fault location result of the target core network based on the test results through the analysis end.

[0007] Secondly, embodiments of this application provide a core network fault location method, applied at an analysis end, comprising: acquiring test results sent by an execution end; wherein the test results are generated by redirecting test traffic of test network elements in a target core network to a virtual core network, and simulating target service processes to test the test network elements in the virtual core network; the virtual core network includes multiple virtual network elements, the virtual core network is networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of real network elements in the target core network; and based on the test results, determining the fault location result of the target core network.

[0008] Thirdly, this application provides a core network fault location device applied at the execution end, comprising: a network construction module for constructing a virtual core network based on a target core network, the virtual core network including multiple virtual network elements, the virtual core network being networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements corresponding one-to-one with the types of real network elements in the target core network; a network element testing module for redirecting test traffic from test network elements in the target core network to the virtual core network, simulating target service processes to test the test network elements in the virtual core network, and generating test results; and a result sending module for sending the test results to an analysis end, through which the analysis end determines the fault location result of the target core network based on the test results.

[0009] Fourthly, this application provides a core network fault location device applied at the analysis end, comprising: a result acquisition module for acquiring test results sent by the execution end; wherein the test results are generated by directing test traffic of test network elements in the target core network to a virtual core network, and simulating target service processes to test the test network elements in the virtual core network; the virtual core network includes multiple virtual network elements, the virtual core network is networked in parallel with the target core network through a preset interface protocol, and the type of the virtual network elements corresponds one-to-one with the type of real network elements in the target core network; and a fault location module for determining the fault location result of the target core network based on the test results.

[0010] Fifthly, embodiments of this application provide an electronic device, the electronic device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the method described in the first or second aspect above.

[0011] In a sixth aspect, embodiments of this application provide a computer-readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first or second aspect above.

[0012] In a seventh aspect, embodiments of this application provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the steps of the method described in the first or second aspect above.

[0013] In this embodiment, a virtual core network is constructed based on the target core network. This virtual core network includes multiple virtual network elements. The virtual core network operates in parallel with the target core network via a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of the real network elements in the target core network. Test traffic from test network elements in the target core network is redirected to the virtual core network. The target service process is simulated in the virtual core network to test the test network elements, generating test results. These test results are then sent to an analysis terminal, which determines the fault location of the target core network based on the test results. Thus, by constructing virtual network elements corresponding to the types of real network elements in the target core network and operating in parallel with the target core network via a preset interface protocol, the target service process can be simulated in the virtual core network. Furthermore, by redirecting test traffic from test network elements in the target core network to the virtual core network, independent testing of each test network element in the target core network can be achieved, eliminating compatibility interference between real network elements and improving the accuracy of multi-element fault location.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0016] Figure 1 shows a structural schematic diagram of the bi-fork network sampling model provided in some embodiments of this application; Figure 2 shows an example diagram of a single network element fault in the bi-fork network sampling model provided in some embodiments of this application; Figure 3 shows an example diagram of a multi-network element fault in the bi-fork network sampling model provided in some embodiments of this application; Figure 4 shows a flowchart of the core network fault location method provided in some embodiments of this application; Figure 5 shows an example diagram of a virtual core network provided in some embodiments of this application; Figure 6 shows a schematic diagram of the interfaces involved in SMF packet session establishment provided in some embodiments of this application; Figure 7 shows a flowchart of the virtual core network construction method provided in some embodiments of this application; Figure 8a shows an example diagram of signaling flow tracing provided in some embodiments of this application; Figure 8b shows a schematic diagram of the virtual core network construction process provided in some embodiments of this application; Figure 9 shows a schematic diagram of network element extraction and unique... Figure 10 shows a schematic diagram of the high-frequency directional single network element simulation provided in some embodiments of this application; Figure 11 shows a schematic diagram of the high-frequency directional single network element simulation signaling flow provided in some embodiments of this application; Figure 12 shows a schematic diagram of protocol simulation multi-network element joint simulation provided in some embodiments of this application; Figure 13 shows a schematic diagram of protocol simulation multi-network element joint simulation signaling flow provided in some embodiments of this application; Figure 14 shows a schematic diagram of the core network fault location method provided in other embodiments of this application; Figure 15 shows a schematic diagram of the core network fault location system architecture provided in some embodiments of this application; Figure 16 shows one of the schematic diagrams of the core network fault location device provided in some embodiments of this application; Figure 17 shows another schematic diagram of the core network fault location device provided in some embodiments of this application; Figure 18 shows a schematic diagram of the electronic device provided in some embodiments of this application. Detailed Implementation

[0017] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0018] In dial-up testing technology, high-frequency directional dial-up testing technology typically uses directional routing to achieve full coverage of network elements in the core network. It is particularly effective in fault detection because it uses a bi-fork network sampling model that can create intersections in the fault trajectory when a single service network element fails, thereby achieving location.

[0019] Taking Figure 1 as an example: the 3-layer network AMF-SMF-UPF, the double-fork network ensures that each network element has branches upstream and downstream. For example: the downstream of AMF1 is fixed to the dial-up testing system, and the upstream is connected to SMF1 and SMF2; the downstream of SMF1 are AMF1, AMF2, and AMF3, and the upstream are UPF1, UPF3, and UPF5; the downstream of UPF1 are SMF1 and SMF2, and the upstream is fixed to the content source.

[0020] When locating a single-service network element fault, all paths related to the faulty network element will fail, and the faulty paths will intersect, thus locating the problem. As shown in Figure 2, when SMF1 fails, all paths related to it will be faulty paths. Other related network elements AMF1, AMF2, AMF3, UPF1, UPF3, and UPF5 will also have faulty paths, but normal paths will also exist. Therefore, the faulty paths will intersect at SMF1, completing the location.

[0021] When multiple service network elements fail, the fault trajectory will form multiple overlapping points in the path, and the trajectory overlap method cannot effectively locate the fault. As shown in Figure 3, when SMF1 and SMF2 fail simultaneously, all paths related to them are fault paths, and all paths of other related network elements AMF1, UPF1, and UPF3 are also fault paths, just like SMF1 and SMF2. Therefore, the fault path will form intersections in multiple network elements, making it impossible to complete the location work.

[0022] To address the issue that the aforementioned high-frequency directional testing scheme cannot effectively locate multiple network element faults in practical applications, this application provides a core network fault location method. This method constructs virtual network elements corresponding to the types of real network elements in the target core network and establishes a parallel network with the target core network through a preset interface protocol, simulating the target service process within the virtual core network. Simultaneously, by redirecting test traffic from the test network elements in the target core network to the virtual core network, independent testing of each test network element in the target core network is achieved, eliminating compatibility interference between real network elements and thus improving the accuracy of multi-network element fault location.

[0023] Please refer to Figure 4, which shows a flowchart of a core network fault location method provided in some embodiments of this application. The execution subject of this method is the execution end, which can be a terminal device or a server. The terminal device can be a device such as a personal computer, or a mobile terminal device such as a mobile phone or tablet computer. The terminal device can be a user-used terminal device. The server can be an independent server or a server cluster composed of multiple servers. Moreover, the server can be a backend server for a certain business, or a backend server for a certain platform or application (e.g., a protocol simulation test system, a data analysis platform, a performance monitoring and analysis tool, etc.). In this embodiment of the application, the execution subject is a server as an example for explanation. For the case of a terminal device, it can be handled according to the following relevant content, which will not be repeated here. As shown in Figure 4, the method 400 may include the following steps: Step 401: Construct a virtual core network based on the target core network. The virtual core network includes multiple virtual network elements. The virtual core network is networked in parallel with the target core network through a preset interface protocol, and the type of virtual network element corresponds one-to-one with the type of real network element in the target core network.

[0024] In practical implementation, the topology of the target core network can be analyzed to obtain multiple real network elements and the connection relationships between them. As shown in Figure 5, the target core network (i.e., the real network) includes four Access and Mobility Management Functions (AMFs), three Session Management Functions (SMFs), and five User Plane Functions (UPFs). Based on the types of real network elements in the target core network, a virtual core network is constructed, including one AMF, one SMF, and one UPF. The types of virtual network elements correspond one-to-one with the types of real network elements in the target core network. The virtual network elements are consistent with the real network elements in the target core network in terms of function and communication protocols, so that the virtual core network can be networked in parallel with the target core network through a preset interface protocol.

[0025] Step 402: Direct the test traffic of the test network element in the target core network to the virtual core network, simulate the target service process in the virtual core network to test the test network element, and generate test results.

[0026] In practical implementation, a virtual core network can be constructed to simulate real business processes. A test network element to be tested is selected within the target core network, for example, SMF1. Through traffic splitting technology, the test traffic for SMF1 is directed to the virtual core network, establishing a test relationship. The target business process is simulated within the virtual core network to test the test network element, generating test results. The target business process includes registration, session establishment, slice selection, interoperability, and handover, with registration and session establishment being the core processes.

[0027] Step 403: Send the test results to the analysis terminal, and determine the fault location result of the target core network based on the test results.

[0028] In practice, the execution side sends test results to the analysis end. These test results may include the identification information of the test network elements, test results, target service processes, etc. The analysis end is the core network workbench, centrally deployed and uniformly enabled. Based on the test results, the analysis end determines the fault location results of the target core network.

[0029] This application provides a core network fault location method applied to the execution end. A virtual core network is constructed based on the target core network. This virtual core network includes multiple virtual network elements. The virtual core network is networked in parallel with the target core network through a preset interface protocol, and the types of virtual network elements correspond one-to-one with the types of real network elements in the target core network. Test traffic from test network elements in the target core network is redirected to the virtual core network. The target service process is simulated in the virtual core network to test the test network elements, generating test results. The test results are sent to the analysis end, which determines the fault location result of the target core network based on the test results. Thus, by constructing virtual network elements corresponding to the types of real network elements in the target core network and networking them in parallel with the target core network through a preset interface protocol, the target service process can be simulated in the virtual core network. Simultaneously, by redirecting test traffic from test network elements in the target core network to the virtual core network, independent testing of each test network element in the target core network can be achieved, eliminating compatibility interference between real network elements, thereby improving the accuracy of multi-network element fault location.

[0030] In some embodiments, as shown in FIG7, step 401 above, constructing a virtual core network based on the target core network, includes: step 4011: determining the virtual network element type based on the network topology of the target core network.

[0031] In one exemplary embodiment, the target core network comprises numerous network elements across multiple domains, including the Evolved Packet Core (EPC), 5G Core (5GC), and IP Multimedia Subsystem (IMS). Each domain contains several types of network elements. A type of network element typically exists as a pool, with no significant differences between individual elements. When constructing the virtual core network, a virtual network element is created for each type of network element, and connections are established with upstream and downstream network elements. Taking the AMF, SMF, and UPF network elements in 5GC as an example, a virtual core network is constructed for this domain, building one AMF, one SMF, and one UPF respectively. These virtual network elements will work collaboratively with the existing simulated base stations to complete the corresponding signaling processes.

[0032] It is important to note that the scope of the virtual network should be increased accordingly depending on the testing process. For example, if testing voice-related processes is required, virtual network elements of the IMS domain can be added to the virtual network. Furthermore, virtualizing general-purpose network elements (such as User Data Manager (UDM), Policy Control Function (PCF), Domain Name System (DNS), etc.) can also help further improve testing efficiency. In practical applications, these general-purpose network elements can be added as needed, depending on the specific circumstances.

[0033] Step 4022: Based on the virtual network element type, determine the simulation interface and key business processes of the virtual network element.

[0034] Continuing with the above embodiments, the function of a network element is to complete the corresponding signaling processes and carry these processes through corresponding interfaces. Key service processes include registration, session establishment, slice selection, interoperability, and handover, among which registration and session establishment are core processes. For example, as shown in Figure 6, the SMF involves interfaces N4, N7, N10, and N11 in packet session establishment, carrying key service processes through these interfaces.

[0035] Step 4023: Allocate network resources to the simulation interface, and construct virtual signaling messages corresponding to key business processes by parsing the signaling messages of real network elements in the target core network, thereby obtaining the virtual core network.

[0036] In practical implementation, network resources are allocated to the aforementioned simulation interfaces, including interface addresses, service addresses, and service IDs, ensuring that interface addresses and service addresses are reachable between the interfaces of each virtual network element. By tracking the signaling of real network elements in the target core network, signaling source code information is obtained. By parsing the signaling source code information, signaling messages corresponding to key business processes are constructed, thereby obtaining the virtual core network.

[0037] Continuing with the above embodiment, step 4023 can be divided into the following steps: Step 40231: Allocate network resources for the simulation interface of the virtual network element; specifically, network resources represent the legitimacy of the network element in the network, including interface address, service address, and service ID, etc. In fact, from the perspective of real network elements, virtual network elements provide the same corresponding process services as other real network elements. In the above example, the virtual network elements associated with the real SMF include AMF, UPF, PCF, and UDM.

[0038] Step 40232: Network connectivity is established, and interface and service addresses are reachable. Specifically, communication between network elements requires the use of the carrier network. Therefore, virtual network elements need to communicate with the carrier network (Carrier Ethernet, CE) and publish routes to ensure the reachability of interface and service addresses. In the example above, the four virtual network elements AMF, UPF, PCF, and UDM are guaranteed to be reachable from the real SMF service address.

[0039] Step 40233: Real Network Element Signaling Tracing and Process Simulation; Specifically, the virtual core network provides testing services for a real network element, and signaling tracing can be used to learn how the real network element processes messages. First, the corresponding service test is completed in the target core network using the test number, as shown in Figure 8a. The signaling messages of the network element interaction are obtained from the signaling tracing of the interface associated with the real network element to be tested in the target core network. Then, each signaling message is decoded. Finally, the virtual network element constructs the same virtual signaling message according to the message decoded by the real network element, thus constructing a virtual core network with the same function as the real network to complete the corresponding service process, as shown in Figure 8b.

[0040] Taking the signaling message N1N2 PDUSessionRelease as an example, its signaling source code is: 0265[1001010Ic_59_n11_bH,ROAMING, TYPE.nukz 5gn11_bHINTERFACE451024131343034303634356163643065373030zc 59_n11 bd;RAT.10IAABBE61219B389F39FD8040920230D2617F3A3DC7989C7BFD8936565DFBDDB09FC06AF 2427525A866726B9F0308BF642199C105557D2EECE566CBOFAE74984017Iz_59_n11_bHKPROCEDURE TYPE404174090462588817409046258991174090462588|1740904625899Izc 59_n11 bHKPROCEDURE STATUS.1zc 5G n11bdKHTTP REO TVPE 1Iz. SG n11 bd:STATUS CODE.200Iz 59 n11 bHKFAILURE CAUSE:M10.1091833510.109.1834926040 801zc 5gn11 bd,.REQUEST CAUSE.null|zc 5g n11bd,SUB PROCEDURE TYPE.nulI5zc 5g n11 bdrDNN.cmnet|zc 5g n11bdrREQUESTTYPE.nuIIIzc 5g,n11 bd,N1N2MSG TSF CAUSE,nulllzc 5g, n11bdrNGAPIETYPE.nulIIzc 5g n11 bd*ACCESS TVPE.12c 59,n11 bdALOCATION TVPE.1!2100340(5785625810lzc 59,n11 bdN2SMINFOTVPE1460079005(99970051470142117496246717496248112025-03-0216:38: 0712025030216371X101124101715716500951193e2cc85-0631-4817-ac87-b7ee2fac78fe.

[0041] The signaling decoding is shown in the table below: Table 1. Signaling Decoding

[0042] Furthermore, the aforementioned core network fault location method also includes: Step 4024: Directed route creation and process guidance; specifically, a virtual core network is constructed through the above steps. This virtual core network can simulate real service processes. By allowing a portion of the process of the network element being evaluated to flow to the virtual network element, a test relationship is formed. For example, the virtual 5GC network element can complete registration in the NRF, thereby pointing to the virtual network element through the Tracking Area Code (TAC). After route guidance, the service process of the test number is directed to the virtual network, while the service of the real service number is still shared and processed by the POOL of the real network element, without affecting each other. As shown in Figure 9, the target core network operates with a fully interconnected structure without change. However, for the test number, the processes of SMF1, SMF2, and SMF3 are independently extracted into the virtual network and isolated from each other. The surrounding area of ​​each SMF, except for itself, is a virtual network element, that is, each network element is evaluated independently.

[0043] Step 4025: Multi-network element joint simulation; In the relevant high-frequency directional dialing method, a simulated terminal plus a base station or a certain network element probes the entire network. As shown in Figure 10, the simulated 5G base station + terminal probes other networks, involving simulated interfaces N1, N2, and N3.

[0044] From the signaling flow perspective, as shown in Figure 11, only the first signaling message between the simulated base station and the AMF (Programming Module Function) is needed as the starting point for probing. The process continues until the last downlink data packet (First Downlink Data) between the UPF and the simulated base station is received, indicating a normal flow. Numerous intermediate steps involve real network elements, which the simulation system cannot perceive. However, if any one or more of the real network elements (AMF, UPF, SMF, PCF, UDM) fail during this period, downlink data packets will not be received. In other words, while the location of the fault can be detected, the faulty network element cannot be effectively located.

[0045] In this embodiment, a virtual network composed of multiple simulated network elements such as AMF, UPF, PCF, and UDM is used to jointly probe each test network element. As shown in Figure 12, the virtual core network probes SMF1, SMF2, and SMF3 independently.

[0046] From the signaling perspective, as shown in Figure 13, the first signaling message Nsmf_PDUSession_CreateSMContext Request sent from the virtual AMF to the real SMF serves as the starting point for probing. The process continues until the virtual UPF returns an N4Session Modification Response to the real SMF, indicating that the entire process is normal. During this period, many intermediate steps do not require simulation if they are processes between simulated network elements. However, the processes between simulated network elements and the SMF (processes 3, 4, 5, 6, 7, 9, 11, 15, and 16) require simulation.

[0047] As can be seen, apart from the SMF (Single Network Element), all other signaling elements in the entire process are virtual network elements. If any interaction process (processes 3, 4, 5, 6, 7, 9, 11, 15, 16) fails, the cause of the failure directly points to the real test network element. The entire simulated network independently tests the core processes of each real network element. During the test, there is no interaction between real network elements, thus achieving precise fault location at the network element level (single network element & multiple network elements), further pinpointing which critical process of which network element has a problem, providing crucial information for subsequent fault handling.

[0048] Compared with single network element simulation represented by high-frequency directional dialing, the protocol simulation test provided in this application has at least the following changes: (1) Change in detection perspective: from service path perspective to network element perspective, the network element perspective is mainly oriented towards the process composed of interfaces, protocols and parameters; (2) Change in test content: from service test to key process test, the key process includes core processes such as registration, bearer establishment, slice selection, interoperability, and handover; (3) Change in simulation scope: from simulating base stations or a single one to fully simulating various 5GC, IMS, general network element interfaces and various protocols.

[0049] (4) Changes in analysis methods: from the analysis of signaling messages of simulated base stations and core network single interfaces to the joint analysis of network elements for multiple surrounding network elements and multiple interfaces.

[0050] It should be noted that Table 2 lists some of the interfaces and processes that need to be simulated by the protocol simulation technology of the network element under test. The protocol simulation technology provided in this application embodiment is fundamentally different from single network element simulation in that: single network element simulation simulates a network element test network, while protocol simulation simulates a network by using multiple interfaces to probe each network element.

[0051] Table 2. Simulation Interfaces and Processes of Some Network Element Protocol Simulation Technologies under Test

[0052] In some embodiments, step 402 above, which directs the test traffic of the test network element in the target core network to the virtual core network, includes: obtaining the network domain of the test network element in the target core network; and directing the test traffic of the test network element to the virtual core network according to the routing rules corresponding to the network domain.

[0053] In an exemplary embodiment, different redirection and routing methods are used in different network domains, as follows: (1) For routing in the circuit domain, the method of simulating a base station controller (BSC) can be used; (2) For routing in the EPC domain, the TAC+DNS resolution method in 4G testing can be used; (3) In routing between the circuit domain and the IMS domain, a dedicated data flow method is used; (4) For routing in the IMS domain, it can be specified directly through the Packet-Switched Business Controller (PSBC) or configured through the Call Session Control Function (CSCF), and the TAC can be implemented through a user subscription method.

[0054] (5) For routing in 5G networks, dedicated TAC and dedicated data from 5G testing can be used for routing.

[0055] Using the routing rules corresponding to the network domains mentioned above, the test traffic of the test network elements is redirected to the virtual core network.

[0056] In some embodiments, step 403 above, sending the test result to the analysis terminal, includes: determining the call detail record (CDR) based on the test result and a preset CDR format, wherein the CDR includes one or more of the following: first identification information for indicating the test network element, second identification information for indicating the test process of the test network element, third identification information for indicating the test item, start time of the test process, end time of the test process, test result, and result description; and sending the CDR to the analysis terminal.

[0057] In an exemplary embodiment, the following table is a standard call detail record (CDR) example. In this embodiment, the test network element, test process, and test item are merged into the task name. For example, SMF04_L002_0002: Test network element SMF04, Test process: Second process, Test item: Second test item.

[0058] Table 3. Standard Call Detail Record (CDR) Sample

[0059] The execution end sends the test results to the analysis end for analysis using standard call detail records (CDRs). The analysis end determines the fault location result of the target core network based on the test results.

[0060] Please refer to Figure 14, which shows a flowchart of a core network fault location method provided in some other embodiments of this application. The execution entity of this method is an analysis terminal, which can be a terminal device or a server. The terminal device can be a personal computer, a mobile terminal device such as a mobile phone or tablet, or a user-used terminal device. The server can be an independent server or a server cluster composed of multiple servers. Furthermore, the server can be a backend server for a specific service, or a backend server for a platform or application (e.g., a fault detection and location system, a core network workbench, etc.). This application uses a server as the execution entity for illustration. For the case of a terminal device, the following related content can be used for processing, which will not be elaborated here. As shown in Figure 14, the method 1400 may include the following steps: Step 1401: Obtain the test result sent by the execution end; wherein, the test result is generated by redirecting the test traffic of the test network element in the target core network to the virtual core network, and simulating the target business process to test the test network element in the virtual core network; the virtual core network includes multiple virtual network elements, and the virtual core network is networked in parallel with the target core network through a preset interface protocol, and the type of the virtual network element corresponds one-to-one with the type of the real network element in the target core network.

[0061] In an exemplary embodiment, as shown in Figure 15, in a specific application, the execution end is a protocol simulation system (i.e., a dial-up testing system), which is deployed distributed across provinces or regions. It uses the protocol simulation technology provided in this application to construct a virtual core network to independently test network elements in the core network. The test results are sent to the analysis end using standard call detail records (CDRs). The analysis end is a core network workbench that obtains the CDRs from each execution end and extracts the test results of the tested network elements in the target core network from the CDRs.

[0062] Step 1402: Based on the test results, determine the fault location results of the target core network.

[0063] Continuing with the above embodiments, the analysis end determines the fault location result of the target core network based on the test results sent by each execution end. The fault location result may include the identification information of the faulty network element, hierarchical disaster recovery operations, etc.

[0064] In some embodiments, step 1402 above, determining the fault location result of the target core network based on the test results, includes: determining the key process success rate of the test network element according to the test results of the test network element at each time point within a preset time period; and determining the fault location result of the target core network according to the identification information of the test network element if the test network element is determined to have failed based on the key process success rate.

[0065] In an exemplary embodiment, the analysis terminal can reflect the operational status of a network element by independently calculating the success rate of its key processes for each test network element. Specifically, the success rate of the key processes of the test network element is determined based on the test results of the test network element at each time point within a preset time period. For example, for each test network element, the success rate of the i-th process is the ratio of the number of successful tests of the i-th process to the total number of tests for the i-th process, and the formula is as follows: ;in, Let be the success rate of the i-th process. Let i be the number of successful processes. This represents the total number of tests performed with the i-th process.

[0066] The success rate of the critical process of the test network element is the minimum success rate of all processes within a preset time period, i.e. ,in, N represents the success rate of critical processes, and N is the total number of test processes.

[0067] It should be noted that taking the minimum value means that each critical process of a network element is independent, and damage to any process indicates that the network element is in an abnormal state.

[0068] For example, the network has three types of network elements: AMF, SMF, and UPF. There are 2 AMFs, 3 SMFs, and 4 UPFs. One test procedure is performed for AMFs, two for SMFs, and one for UPFs, for a total of 12 tests. Since the analysis uses data from the most recent 10 minutes, the analysis is performed from the 10th minute to the 12th minute, for a total of 3 analyses, illustrated in Table 4 below: Table 4. Test Example

[0069] Calculate the success rate for each network element and each process separately: For example, analyzing process 1 of 1UPF02, at the 10th minute, the last 10 attempts were counted, with 2 failures and a success rate of 80%; at the 11th minute, the last 10 attempts were counted, with 3 failures and a success rate of 70%; at the 12th minute, the last 10 attempts were counted, with 4 failures and a success rate of 60%. The final scores are as follows: Table 5. Success Rate per Network Element and per Process

[0070] Calculating the success rate of critical processes for each network element is equivalent to taking the minimum value of each process within a single network element. For example, in the above example of SMF01, processes 1 (90%, 80%, 80%) and 2 (70%, 70%, 70%) have a minimum value of (70%, 70%, 70%). The final results are shown in Table 6 below: Table 6. Success Rate of Critical Processes for Network Elements

[0071] In some possible implementations, after determining the fault location result of the target core network based on the identification information of the test network element, the method further includes: obtaining the maintenance data of the test network element, which includes at least one of the following: alarm data, key performance indicators, and log analysis data; determining the target hierarchical disaster recovery operation based on the success rate of key processes and the target status of the maintenance data; wherein the target status includes normal status and abnormal status; and controlling the target core network to execute the target hierarchical disaster recovery operation.

[0072] Continuing with the above implementation, when the success rate of critical processes at the analysis end falls below a set fixed threshold, joint alarms, key performance indicator monitoring, log analysis, and other maintenance measures will be triggered to automatically perform hierarchical disaster recovery operations on the network element. During this process, the test results of protocol simulation will serve as the primary index, exhibiting high specificity and involving only the network element under test.

[0073] Other maintenance methods include network element alarms, key performance indicators, and log analysis. The analysis of related maintenance data is currently affected by multiple factors. For example, in indicator analysis, if the success rate of a certain network element decreases, it may be difficult to determine whether the decrease is due to a failure of surrounding network elements or a problem with the network element itself. Therefore, other maintenance methods will employ correlation analysis to output normal or abnormal statuses as reference indices.

[0074] It should be noted that there are many types of association analysis methods with varying effects, and no specific restrictions are made on the selection of maintenance data here.

[0075] In some possible implementations, the above-mentioned determination of target hierarchical disaster recovery operations based on the success rate of key processes and the status of maintenance data includes: obtaining the target interval where the success rate of key processes is located from a preset number of intervals; and determining the target hierarchical disaster recovery operation corresponding to the target interval and the target status based on the correspondence between the interval, the status and the hierarchical disaster recovery operation.

[0076] Among them, the above-mentioned target hierarchical disaster recovery operation includes at least one of the following: (1) Control new additions: restrict new users from accessing the test network element; (2) Clear existing users: control target users to go offline from the test network element and migrate to other network elements in the target core network other than the test network element; (3) Hard isolation: interrupt the connection service of the test network element.

[0077] The principle of the tiered disaster recovery strategy is as follows: For minor damage to critical processes, two lossless disaster recovery methods are adopted: controlling new additions and clearing existing issues; for moderate damage to critical processes, clearing existing issues is prioritized, and if other maintenance dimensions also show anomalies, hard isolation is used; for severe damage to critical processes, regardless of whether other maintenance dimensions are abnormal, hard isolation is initiated to quickly restore business operations. The specific details are shown in Table 7 below: Table 7. Tiered Disaster Recovery Strategy

[0078] Obtain the target interval where the success rate of the key process is located from multiple preset intervals; determine the target hierarchical disaster recovery operation corresponding to the target interval and the target state based on the correspondence between the interval, state and hierarchical disaster recovery operation.

[0079] This application provides a core network fault location method applied at the analysis end to obtain test results sent by the execution end. The test results are generated by redirecting test traffic from test network elements in the target core network to a virtual core network, where the target service process is simulated to test the test network elements. The virtual core network includes multiple virtual network elements, which are networked in parallel with the target core network through a preset interface protocol. The types of virtual network elements correspond one-to-one with the types of real network elements in the target core network. Based on the test results, the fault location result of the target core network is determined. Thus, by constructing virtual network elements corresponding to the types of real network elements in the target core network and networking them in parallel with the target core network through a preset interface protocol, the target service process can be simulated in the virtual core network. Simultaneously, by redirecting test traffic from test network elements in the target core network to the virtual core network, independent testing of each test network element in the target core network can be achieved, eliminating compatibility interference between real network elements and thus improving the accuracy of multi-element fault location.

[0080] The above-mentioned core network fault location method can be applied to at least the following scenarios: (1) Real-time network monitoring: Whether it is a single network element fault or a multi-network element group fault, it has the ability to quickly discover, accurately locate, and restore in a hierarchical manner. Thus, it transforms from an "experience-driven" to a "self-intelligent self-healing" model, achieving a new breakthrough in network operation and maintenance.

[0081] (2) Change of operation scenario: On most operation days, multiple network elements operate alternately. The original testing methods cannot solve the problem of mutual interference. Usually, the network operation is observed uniformly at 5 am. Network simulation technology evaluates each network element independently, and can grasp the operation of network elements in real time. The impact of various operations on network elements is clear at a glance.

[0082] (3) Equipment access and software upgrade verification: Before and after equipment access and software upgrade, the key processes of the network element are loaded and "tested" by simulating the parameters and processes of different software versions of the surrounding network elements to ensure normal service carrying, early detection, early analysis and early resolution of problems, and avoid equipment access to the network with damage.

[0083] In an exemplary embodiment, through comparison of measured data, it is found that: compared with the existing high-frequency directional dialing test, the protocol simulation technology provided in this application embodiment reduces the single network element fault location time from 3 minutes to 1 minute, and achieves a breakthrough from 0 to 1 for multi-network element group faults, realizing early warning and location in 1 minute.

[0084] (1) Single network element fault location: Protocol simulation technology for 30 seconds location, high frequency directional dialing test technology for 3 minutes and 34 seconds location. Specifically, 1) 2024.11.21 02:09:55 Service dialing test warning; [Active monitoring warning prompt]: In the last 30 minutes, Class C 4G voice service, C001 test item failed 3 times in a row. Last file time: 202411210209 Test item route: ["AMF01","SMFO4",UDMO4"].

[0085] 2) 2024.11.21 02:10:25 AMF01 protocol simulation positioning successful; [Active monitoring and early warning prompt]: In the last 10 minutes, AMF01_L001 failed twice, more than twice, the last file time: 202411210210.

[0086] 3) At 02:13:29 on November 21, 2024, the high-frequency directional dialing of AMF01 was successfully located, as shown in Table 8.

[0087] It affects 7 types of services: C, E, F, T, U, X, and Y. The paths of each service overlap and converge to the AMF01 network element in the lower right corner.

[0088] Table 8. High-frequency directional dialing test for single network element positioning

[0089] (2) Multi-network element failure: Protocol simulation technology has a 48-second positioning capability, and high-frequency directional dialing test technology has no positioning capability. Specifically, 1) 2024.9.25 00:20:37 Multi-network element failure warning; [Active monitoring warning prompt]: In the last 30 minutes, F-class VONR voice, F112 test item failed 3 times in a row. Last file time: 202409250020 Test item route: ["UDM04","AMFO3",SMFO4",UPFO6"].

[0090] 2) 2024.9.25 00:21:25 The first network element AMF06 protocol simulation positioning was successful, and subsequent network elements completed positioning one after another; [Active monitoring and early warning prompt]: In the last 10 minutes, AMF06_L001 failed 2 times, more than 2 times, the last file time: 202409250021.

[0091] 3) High-frequency directional dialing has no positioning capability: the path has multiple intersections, but no overlap, as shown in Table 9.

[0092] Table 9. High-frequency directional dialing test without multi-network element positioning capability

[0093] This application provides a core network fault location system, employing a decoupled architecture between the execution and analysis ends. The execution ends are deployed in a distributed manner close to the production network, ensuring high practicality. By constructing a virtual core network, critical process testing is performed independently on each real network element. Independent testing of each network element not only achieves independent location of faulty network elements but also eliminates compatibility interference between real network elements, improving testing accuracy and relevance. The analysis end is centrally deployed, forming standardized capabilities that empower the entire network, saving investment. The analysis end, combined with other operational capabilities, forms a hierarchical disaster recovery capability, quickly performing "controlling new additions, clearing existing ones, and hard isolation" disaster recovery operations on faulty network elements to ensure business continuity. Furthermore, the rapid fault location of service network elements also provides important reference for cross-layer and cross-domain fault location of virtualized network elements, as shown in Table 10.

[0094] Table 10. Principles for Cross-Layer and Cross-Domain Fault Location of Virtualized Network Elements

[0095] Please refer to Figure 16, which shows one of the structural schematic diagrams of a core network fault location device provided in some embodiments of this application. This core network fault location device can implement all or part of the content shown in the embodiment of Figure 4. The core network fault location device 1600, applied at the execution end, includes: a network construction module 1610, used to construct a virtual core network based on a target core network. The virtual core network includes multiple virtual network elements, which are networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of real network elements in the target core network; a network element testing module 1620, used to direct the test traffic of the test network elements in the target core network to the virtual core network, simulate the target service process in the virtual core network to test the test network elements, and generate test results; and a result sending module 1630, used to send the test results to an analysis end, through which the analysis end determines the fault location result of the target core network based on the test results.

[0096] In some embodiments, when the network construction module 1610 is used to construct a virtual core network based on a target core network, it is specifically used to: determine the virtual network element type based on the network topology of the target core network; determine the simulation interface and key service process of the virtual network element based on the virtual network element type; allocate network resources to the simulation interface; and construct the virtual signaling message corresponding to the key service process by parsing the signaling messages of real network elements in the target core network to obtain the virtual core network.

[0097] In some embodiments, the network element testing module 1620, when used to redirect the test traffic of the test network element in the target core network to the virtual core network, is specifically used to: obtain the network domain of the test network element in the target core network; and redirect the test traffic of the test network element to the virtual core network according to the routing rules corresponding to the network domain.

[0098] In some embodiments, when sending the test results to the analysis terminal, the result sending module 1630 is specifically configured to: determine a call detail record (CDR) based on the test results and a preset CDR format, wherein the CDR includes one or more of the following: first identification information for indicating the test network element, second identification information for indicating the test process of the test network element, third identification information for indicating the test item, the start time of the test process, the end time of the test process, the test result, and the result description; and send the CDR to the analysis terminal.

[0099] This application provides a core network fault location device applied at the execution end, including a network construction module, a network element testing module, and a result sending module. The network construction module constructs a virtual core network based on the target core network. This virtual core network includes multiple virtual network elements, which are networked in parallel with the target core network through a preset interface protocol. The types of virtual network elements correspond one-to-one with the types of real network elements in the target core network. The network element testing module directs test traffic from test network elements in the target core network to the virtual core network, simulates target service processes in the virtual core network to test the test network elements, and generates test results. The result sending module sends the test results to the analysis end, which determines the fault location result of the target core network based on the test results. Thus, by constructing virtual network elements corresponding to the types of real network elements in the target core network and networking them in parallel with the target core network through a preset interface protocol, the target service process can be simulated in the virtual core network. Meanwhile, by redirecting the test traffic of the test network elements in the target core network to the virtual core network, it is possible to independently test each test network element in the target core network, eliminate compatibility interference between real network elements, and thus improve the accuracy of multi-network element fault location.

[0100] Please refer to Figure 17, which shows a second structural schematic diagram of a core network fault location device provided in some embodiments of this application. This core network fault location device can implement all or part of the content shown in the embodiment of Figure 14. The core network fault location device 1700, applied at the analysis end, includes: a result acquisition module 1710, used to acquire test results sent by the execution end; wherein the test results are generated by redirecting test traffic from test network elements in the target core network to a virtual core network, simulating target service processes to test the test network elements in the virtual core network; the virtual core network includes multiple virtual network elements, which are networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of real network elements in the target core network; and a fault location module 1720, used to determine the fault location result of the target core network based on the test results.

[0101] In some embodiments, when the fault location module 1720 is used to determine the fault location result of the target core network based on the test results, it is specifically used to: determine the key process success rate of the test network element according to the test results of the test network element at each time point within a preset time period; and when it is determined that the test network element has failed based on the key process success rate, determine the fault location result of the target core network based on the identification information of the test network element.

[0102] In some possible implementations, the fault location module 1720 is further configured to: acquire maintenance data of the test network element, wherein the maintenance data includes at least one of the following: alarm data, key performance indicators, and log analysis data; determine the target hierarchical disaster recovery operation based on the success rate of the key process and the target status of the maintenance data; wherein the target status includes a normal status and an abnormal status; and control the target core network to execute the target hierarchical disaster recovery operation.

[0103] In some possible implementations, the fault location module 1720, when determining the target hierarchical disaster recovery operation based on the success rate of the key process and the status of the maintenance data, is specifically used to: obtain the target interval where the success rate of the key process is located from a preset multiple intervals; and determine the target hierarchical disaster recovery operation corresponding to the target interval and the target status based on the correspondence between the interval, the status and the hierarchical disaster recovery operation.

[0104] The aforementioned target-level disaster recovery operations include at least one of the following: restricting new users from accessing the test network element; controlling target users to go offline from the test network element and migrate to other network elements in the target core network besides the test network element; and interrupting the connection service of the test network element.

[0105] This application provides a core network fault location device applied at the analysis end, including a result acquisition module and a fault location module. The result acquisition module acquires test results sent by the execution end. These test results are generated by redirecting test traffic from test network elements in the target core network to a virtual core network, where the target service process is simulated to test the test network elements. The virtual core network includes multiple virtual network elements, which are networked in parallel with the target core network through a preset interface protocol. The types of virtual network elements correspond one-to-one with the types of real network elements in the target core network. Based on the test results, the fault location module determines the fault location result of the target core network. Thus, by constructing virtual network elements corresponding to the types of real network elements in the target core network and networking them in parallel with the target core network through a preset interface protocol, the target service process can be simulated in the virtual core network. Simultaneously, by redirecting test traffic from test network elements in the target core network to the virtual core network, independent testing of each test network element in the target core network can be achieved, eliminating compatibility interference between real network elements and improving the accuracy of multi-element fault location.

[0106] Figure 18 shows a schematic diagram of the structure of an electronic device provided in some embodiments of this application. Referring to the figure, at the hardware level, the electronic device 1800 includes a processor 1810, and optionally includes an internal bus 1820, a network interface 1830, and a memory. The memory may include main memory 1841, such as high-speed random-access memory (RAM), and may also include non-volatile memory 1842, such as at least one disk storage device. Of course, the electronic device may also include other hardware required for other services.

[0107] The processor 1810, network interface 1830, and memory can be interconnected via an internal bus 1820. This internal bus 1820 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only a single bidirectional arrow is used in this diagram, but this does not imply that there is only one bus or one type of bus.

[0108] The memory stores programs. Specifically, the program may include program code, which includes computer operation instructions. The memory may include main memory 1841 and non-volatile memory 1842, and provides instructions and data to the processor 1810.

[0109] Processor 1810 reads the corresponding computer program from non-volatile memory 1842 into memory and then runs it, forming a device for locating the target user at the logical level. Processor 1810 executes the program stored in memory and specifically performs the method disclosed in the embodiment shown in FIG4 or FIG14, and implements the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0110] The methods disclosed in the embodiments shown in Figures 4 or 14 of this application can be applied to or implemented by the processor 1810. The processor 1810 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the hardware of the processor 1810 or by instructions in software form. The processor 1810 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0111] The computer device can also execute the methods described in the preceding method embodiments and achieve the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0112] Of course, in addition to software implementation, the electronic device of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0113] This application also proposes a computer-readable storage medium that stores one or more programs. When executed by an electronic device including multiple applications, the one or more programs cause the electronic device to perform the methods disclosed in the embodiments shown in FIG4 or FIG14 and achieve the functions and beneficial effects of the methods described in the foregoing method embodiments, which will not be repeated here.

[0114] The computer-readable storage medium mentioned above includes read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc.

[0115] Furthermore, this application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, which, when executed by a computer, implement the following process: the method disclosed in the embodiment shown in FIG4 or FIG14 and implement the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0116] The embodiments of this application can be applied to various scenarios of electronic device collaboration or interconnection, including: collaboration and interconnection between mobile phones and laptops / tablets; collaboration and interconnection between mobile terminals and smart TVs / monitors; collaboration and interconnection between mobile phones or tablets and in-vehicle entertainment systems; collaboration and interconnection between mobile terminals and smart conferencing systems, etc. This satisfies users' diverse needs in smart home, smart office, and smart travel scenarios.

[0117] In summary, the above description is merely a preferred embodiment of this application and does not limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0118] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0119] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0120] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0121] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

Claims

1. A core network fault location method, characterized in that, Applied to the execution end, the method includes: constructing a virtual core network based on the target core network, wherein the virtual core network includes multiple virtual network elements, the virtual core network is networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of real network elements in the target core network; directing the test traffic of the test network elements in the target core network to the virtual core network, simulating the target service process to test the test network elements in the virtual core network, and generating test results; sending the test results to the analysis end, and determining the fault location result of the target core network based on the test results through the analysis end.

2. The method according to claim 1, characterized in that, The construction of a virtual core network based on the target core network includes: determining the type of virtual network element based on the network topology of the target core network; determining the simulation interface and key service processes of the virtual network element based on the type of virtual network element; allocating network resources to the simulation interface; and constructing virtual signaling messages corresponding to the key service processes by parsing the signaling messages of real network elements in the target core network, thereby obtaining the virtual core network.

3. The method according to claim 1, characterized in that, The step of redirecting the test traffic of the test network element in the target core network to the virtual core network includes: obtaining the network domain of the test network element in the target core network; and redirecting the test traffic of the test network element to the virtual core network according to the routing rules corresponding to the network domain.

4. The method according to claim 1, characterized in that, Sending the test results to the analysis terminal includes: determining a call detail record (CDR) based on the test results and a preset CDR format, wherein the CDR includes one or more of the following: first identification information for indicating the test network element, second identification information for indicating the test process of the test network element, third identification information for indicating the test item, the start time of the test process, the end time of the test process, the test result, and the result description; and sending the CDR to the analysis terminal.

5. A core network fault location method, characterized in that, The method is applied to the analysis end and includes: acquiring test results sent by the execution end; wherein the test results are generated by redirecting test traffic from test network elements in the target core network to a virtual core network, and simulating target service processes to test the test network elements in the virtual core network; the virtual core network includes multiple virtual network elements, which are networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of real network elements in the target core network; based on the test results, determining the fault location result of the target core network.

6. The method according to claim 5, characterized in that, The step of determining the fault location result of the target core network based on the test results includes: determining the key process success rate of the test network element according to the test results of the test network element at each time point within a preset time period; and determining the fault location result of the target core network according to the identification information of the test network element when it is determined that the test network element has failed based on the key process success rate.

7. The method according to claim 6, characterized in that, After determining the fault location result of the target core network based on the identification information of the test network element, the method further includes: acquiring the maintenance data of the test network element, wherein the maintenance data includes at least one of the following: alarm data, key performance indicators, and log analysis data; determining the target hierarchical disaster recovery operation based on the success rate of the key process and the target status of the maintenance data; wherein the target status includes a normal status and an abnormal status; and controlling the target core network to execute the target hierarchical disaster recovery operation.

8. The method according to claim 7, characterized in that, The step of determining the target hierarchical disaster recovery operation based on the success rate of the key process and the status of the maintenance data includes: obtaining the target interval where the success rate of the key process is located from a preset multiple intervals; and determining the target hierarchical disaster recovery operation corresponding to the target interval and the target status based on the correspondence between the interval, the status and the hierarchical disaster recovery operation.

9. The method according to claim 7 or 8, characterized in that, The target hierarchical disaster recovery operation includes at least one of the following: restricting new users from accessing the test network element; controlling target users to go offline from the test network element and migrate to other network elements in the target core network other than the test network element; interrupting the connection service of the test network element.

10. A core network fault location device, characterized in that, Applied to the execution end, it includes: a network construction module for constructing a virtual core network based on the target core network, wherein the virtual core network includes multiple virtual network elements, the virtual core network is networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of real network elements in the target core network; a network element testing module for redirecting test traffic from test network elements in the target core network to the virtual core network, simulating target service processes to test the test network elements in the virtual core network, and generating test results; and a result sending module for sending the test results to an analysis end, through which the analysis end determines the fault location result of the target core network based on the test results.

11. A core network fault location device, characterized in that, The system is applied to the analysis end and includes: a result acquisition module for acquiring test results sent by the execution end; wherein the test results are generated by redirecting test traffic from test network elements in the target core network to a virtual core network, and simulating target service processes to test the test network elements in the virtual core network; the virtual core network includes multiple virtual network elements, which are networked in parallel with the target core network through a preset interface protocol, and the types of the virtual network elements correspond one-to-one with the types of real network elements in the target core network; and a fault location module for determining the fault location result of the target core network based on the test results.

12. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 9.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 9.

14. A computer program product, characterized in that, The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions that, when executed by a computer, cause the computer to perform the steps of the method as described in any one of claims 1 to 9.

Images