Fault warning method, device, equipment and computer-readable storage medium

By constructing and operating simulation microservices and target test tasks on the test network elements in the 5G core network, the problem of low timeliness of fault warning caused by lack of initiative in monitoring and maintenance in the existing technology is solved, and efficient early warning of network failures is achieved.

CN115278739BActive Publication Date: 2025-06-03CHINA MOBILE GROUP ZHEJIANG +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202110478525.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-04-29
Publication Date
2025-06-03
Estimated Expiration
2041-04-29

AI Technical Summary

Technical Problem

The existing monitoring and maintenance methods lack initiative, cannot provide timely warnings, and it is difficult to adapt to the fault warning requirements in the 5G core network environment, resulting in low alarm timeliness.

Method used

By determining all test network elements in the network to be tested, and simulating microservices for each test network element, we can obtain the microservices corresponding to each test network element, and then build the target test task based on each microservice, and run the target test task, and output the fault alarm information when the test results and preset test conditions do not match.

Benefits of technology

Active simulation test of network failures is realized, problems are discovered in advance and fault alarm information is output, thereby improving the timeliness of network failure warning.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115278739B_ABST
    Figure CN115278739B_ABST
Patent Text Reader

Abstract

The present invention discloses a fault warning method, device, equipment and computer-readable storage medium. The fault warning method includes: determining all test network elements in the network to be tested, and performing simulation microservices on each of the test network elements to obtain microservices corresponding to each of the test network elements; constructing a target test task according to each of the microservices, and performing a running test on the target test task; if the test result of the running test does not match a preset test condition, outputting a fault warning message. The present invention improves the timeliness of network fault warning.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of communication testing, and in particular, to a fault warning method, device, equipment, and computer-readable storage medium. Background Art

[0002] With the rapid development of communication networks, early warning of communication networks has become increasingly important. For example, the current 5G core network has strict requirements for fault warning. Among them, the 5G core network is built based on the NFV (Network Functions Virtualization) cloud network and adopts a C (Control plane) / U (User plane) separated architecture. At the same time, the 5G core network has the characteristics of a service-based architecture. Therefore, from the perspective of core network operation and maintenance, it is not only necessary to support operation and maintenance under the traditional reference point model, but also to monitor and maintain the interfaces and protocol processes of the 5G service-based architecture. However, the existing monitoring and maintenance mainly focus on device network management, which only collects data and conducts post-event analysis, lacking initiative, unable to give early warnings in a timely manner, difficult to meet the fault warning requirements in the 5G core network environment, and unable to achieve rapid early warning. Summary of the Invention

[0003] The main purpose of the present invention is to provide a fault warning method, device, equipment, and computer-readable storage medium, aiming to solve the technical problem of how to improve the timeliness of network fault warning.

[0004] To achieve the above purpose, the present invention provides a fault warning method, including the following steps:

[0005] Determine all test network elements in the network to be tested, and perform simulation microservices on each of the test network elements to obtain microservices corresponding to each of the test network elements;

[0006] Construct a target test task according to each of the microservices, and perform a running test on the target test task;

[0007] If the test result of the running test does not match the preset test condition, output a fault warning message.

[0008] Optionally, the step of performing simulation microservices on each of the test network elements to obtain microservices corresponding to each of the test network elements includes:

[0009] Traverse each of the test network elements to determine all network element interfaces corresponding to the traversed test network elements;

[0010] Perform simulation microservices on each of the network element interfaces to obtain microservices corresponding to the traversed test network elements.

[0011] Optionally, the step of performing simulation microservices on each of the network element interfaces to obtain the microservices corresponding to the traversed test network elements includes:

[0012] Traverse each of the network element interfaces, determine the protocol model corresponding to the traversed network element interface, and perform interface simulation on the traversed network element interface according to the protocol model to obtain a simulated interface;

[0013] Perform microservice encapsulation on the simulated interfaces corresponding to each of the network element interfaces to obtain the microservices corresponding to the traversed test network elements.

[0014] Optionally, the microservices include gNodeB simulation microservices, AMF simulation microservices, and SMF simulation microservices.

[0015] Optionally, the step of constructing a target test task according to each of the microservices includes:

[0016] Determine the test content corresponding to each of the test network elements, and traverse each of the test contents to determine the test process corresponding to the traversed test content;

[0017] Obtain the microservice controls corresponding to each of the microservices, and perform orchestration connection processing on each of the microservice controls according to the test process to obtain the test task corresponding to the traversed test content;

[0018] Determine the target test task among each of the test tasks according to the input selection instruction.

[0019] Optionally, the step of performing orchestration connection processing on each of the microservice controls according to the test process to obtain the test task corresponding to the traversed test content includes:

[0020] Obtain the drag trajectory received by the terminal display interface corresponding to the network under test, and drag all the target microservice controls in each of the microservice controls from a preset area to be orchestrated to the process template area corresponding to the test process according to the drag trajectory;

[0021] Perform connection processing on all the target microservice controls in the process template area according to the test process to obtain the test task corresponding to the traversed test content.

[0022] Optionally, the step of outputting a fault warning message if the test result of the running test does not match the preset test conditions includes:

[0023] Determine whether the microservice corresponding to the target test task is successfully executed according to the test result of the running test;

[0024] If it is not successfully executed, determine that the test result does not match the preset test conditions, and output a fault warning message.

[0025] In addition, to achieve the above object, the present invention further provides a fault warning device, including:

[0026] A microservice module, configured to determine all test network elements in the network to be tested, and perform simulation microservices on each of the test network elements to obtain microservices corresponding to each of the test network elements;

[0027] A test module, configured to construct a target test task according to each of the microservices, and perform a running test on the target test task;

[0028] An output module, configured to output a fault warning message if the test result of the running test does not match a preset test condition.

[0029] In addition, to achieve the above object, the present invention further provides a fault warning device. The fault warning device includes a memory, a processor, and a fault warning program stored on the memory and executable on the processor. When the fault warning program is executed by the processor, the steps of the above-mentioned fault warning method are implemented.

[0030] In addition, to achieve the above object, the present invention further provides a computer-readable storage medium. A fault warning program is stored on the computer-readable storage medium. When the fault warning program is executed by the processor, the steps of the above-mentioned fault warning method are implemented.

[0031] The present invention first determines all test network elements in the network to be tested, performs simulation microservices on each test network element to obtain microservices corresponding to each test network element, then constructs a target test task according to each microservice, and performs a running test on the target test task. When the test result does not match the preset test condition, a fault warning message is output, thereby avoiding the phenomenon in the prior art that data collection needs to be performed and post-analysis is carried out, resulting in untimely discovery of fault information and low warning timeliness. By actively simulating and testing each test network element, a fault warning message can be output in advance when a problem is found, thereby improving the timeliness of network fault warning. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a schematic structural diagram of a terminal / device of the hardware operating environment related to the embodiment solution of the present invention;

[0033] Figure 2 It is a schematic flowchart of the first embodiment of the fault warning method of the present invention;

[0034] Figure 3 It is a schematic diagram of the device units of the fault warning device of the present invention;

[0035] Figure 4Schematic diagram of the separation architecture of the core network in the fault warning method of the present invention;

[0036] Figure 5 Schematic diagram of the principle of service orchestration in the fault warning method of the present invention;

[0037] Figure 6 Schematic diagram of task dispatching and processing in the fault warning method of the present invention;

[0038] Figure 7 Schematic diagram of the architecture of the fault warning system in the fault warning method of the present invention;

[0039] Figure 8 Schematic diagram of network element simulation in the fault warning method of the present invention;

[0040] Figure 9 Schematic diagram of the SBI interface protocol in the fault warning method of the present invention.

[0041] The realization of the object, functional features and advantages of the present invention will be further described with reference to the embodiments and the accompanying drawings. Detailed implementation manners

[0042] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0043] As Figure 1 shown, Figure 1 is a schematic diagram of the terminal structure of the hardware operating environment involved in the embodiment solution of the present invention.

[0044] The terminal in the embodiment of the present invention is a fault warning device.

[0045] As Figure 1 shown, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard). Optionally, the user interface 1003 may further include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0046] Optionally, the terminal may further include a camera, an RF (Radio Frequency) circuit, sensors, an audio circuit, a WiFi module, etc. Among them, the sensors such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. Among them, the ambient light sensor can adjust the brightness of the display screen according to the brightness of the ambient light, and the proximity sensor can turn off the display screen and / or the backlight when the terminal device is moved to the ear. Of course, the terminal device may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be elaborated here.

[0047] Those skilled in the art can understand that Figure 1 the terminal structure shown in does not constitute a limitation on the terminal, and may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0048] Such as Figure 1 As shown, in the memory 1005 as a computer storage medium, an operating system, a network communication module, a user interface module, and a fault warning program may be included.

[0049] In Figure 1 the terminal shown, the network interface 1004 is mainly used to connect to the background server and communicate with the background server for data; the user interface 1003 is mainly used to connect to the client (user side) and communicate with the client for data; and the processor 1001 can be used to call the fault warning program stored in the memory 1005 and perform the following operations:

[0050] Referring to Figure 2 , the present invention provides a fault warning method. In the first embodiment of the fault warning method, the fault warning method includes the following steps:

[0051] Step S10, determine all test network elements in the network to be tested, and perform simulation microservices on each of the test network elements to obtain microservices corresponding to each of the test network elements;

[0052] Since the current network (such as a 5G network) lacks an active warning function. Therefore, in this embodiment, by simulating 5G users to establish 5G service bearer monitoring, combining services to establish a multi-path and full-coverage fault detection process, realizing service bearer network quality monitoring, and achieving the function of fault warning. Therefore, in this embodiment, before performing fault warning on the network to be tested (i.e., the network to be tested, such as a 5G network), it is necessary to first perform network deployment, that is, a distributed network can be formed using the basic architecture of C (Controlplane) / U (User plane) separation, and the architecture of its network model can be as Figure 4As shown in the figure, it includes the 5G core network in the large region, the AMF (Access and Mobile Management Function) network element, the SMF (Session Management Function) network element, and the UDM (Unit Deployment Manager) network element. In the resource pool of Province A in the access province area, there are Web (World Wide Web) servers, databases, data processing servers, and 5G core network fault warnings, and the 5G core network fault warning is connected to the IP (Internet Protocol) bearer network of Province A. The IP bearer network of Province A is connected to the SPN (Slicing Packet Network) from City 1 to City n. And in this architecture, there are also UPF (User Plane Function) network elements and gNodeB (base station) simulation network elements. It should be noted that the C-plane network element simulation and system platform are deployed in a centralized manner on the cloud resource pool and are connected to the 5G SA (Standalone) C-plane network element. Since the 5G SA U-plane network element UPF is deployed in each city of each province and communicates with the C-plane through the SPN and IP bearer network for data interaction, the deployment location of the simulated gNodeB is the same as that of the actual gNodeB. The simulated gNodeB is deployed in a city-sinking manner and is deployed on a virtual machine or physical server and accesses the local SPN / PTN (Packet Transport Network) through the IP method. By adopting the networking method of the C / U separation architecture, the service test path and the actual user service path can be realized, the authenticity of the test can be guaranteed, and the accuracy of the fault warning can be improved.

[0053] Therefore, in this embodiment, after the networking deployment of the network under test is completed, it is necessary to determine the key network elements in the network under test and use them as test network elements. And the interfaces of each test network element will be simulated with microservices. For example, the gNodeB, AMF, and SMF interface simulations are carried out in the form of single-point access of the simulation module, and network elements such as AMF, UPF, and SMF under 5G C are specified to realize real-time fault warnings for the 5G SA core network, network elements, and services. That is, in this embodiment, the interfaces N1, N2, N3 of gNodeB, the interfaces N11, N8, N15 of AMF, and the interfaces N10, N7 of SMF can be respectively simulated and designed, and then microservice encapsulation is carried out to obtain the microservices corresponding to each test network element, such as the microservice corresponding to the gNodeB network element, the microservice corresponding to the AMF network element, and the microservice corresponding to the SMF network element. Among them, a microservice is a way of constructing an application program as a group of loosely coupled services.

[0054] And in this embodiment, the microservices include gNodeB simulation microservice, AMF simulation microservice, and SMF simulation microservice. The construction of the gNodeB simulation microservice can be to first determine the corresponding interfaces N1, N2, N3 (i.e., network element interfaces) of the test network element, and then perform simulation according to the 5G standard protocol model published by 3GPP (3rd Generation Partnership Project). For example, simulate the 5G NAS protocol (N1 interface) according to TS 24.501 to implement operations such as simulating user registration management, connection management, activation and deactivation of the user plane connection. Simulate the N2 interface according to the NG-AP protocol defined in 38.413 and the SCTP (Stream Control Transmission Protocol) protocol defined in RFC 4960, and simulate the N3 interface according to the GTP-U (GPRS Tunneling Protocol, an IP-based high-layer protocol) protocol defined in TS29.281. And after completing the simulation of N1, N2, and N3, perform microservice encapsulation to obtain the gNodeB simulation microservice. Among them, N1 is the interface between the UE and the AMF. N2 is the interface between the AMF and the (R)AN. N3 is the interface between the UPF and the (R)AN.

[0055] The construction of the AMF simulation microservice can be to first determine the corresponding interfaces N11, N8, N15 (i.e., network element interfaces) of the test network element, and then perform simulation. For example, use the HTTP (Hypertext Transfer Protocol) / TCP (Transmission Control Protocol) protocol to simulate the N8 interface, use the HTTP2 protocol to simulate the N11 interface, and use the HTTP / TCP protocol to simulate the N15 interface. Among them, the N8 interface is the interface between the AMF and the UDM. N11 is the interface between the AMF and the SMF. N15 is the interface between the AMF and the PCF. And in this embodiment, the N11, N8, N15 interfaces all refer to the Figure 9 SBI interface model for simulation. Among them, the SBI (Serial Bus Interface) interface model includes Application, HTTP / 2, TCP, IP, L1, L2.

[0056] The construction of the SMF simulation microservice can be to first determine the corresponding interfaces N7, N10 (i.e., network element interfaces) of the test network element, and then perform simulation. The HTTP / TCP protocol can be used to simulate the N7 and N10 interfaces. Among them, N7 is the interface between the SMF and the PCF. N10 is the interface between the SMF and the UDM.

[0057] Step S20: Construct a target test task according to each of the microservices, and perform a running test on the target test task;

[0058] After determining the microservices corresponding to each test network element, the microservice controls corresponding to each microservice (such as microservice controls for service processes such as obtaining numbers, making outgoing calls, and receiving calls) can be dragged and designed in a graphical and drag-and-drop and orchestratable manner to design each test task, and each test task is used to complete the test of the test functions of each service process of the network under test (such as a 5G network), so as to achieve early warning of faults and service quality monitoring. The simulation network elements and test network elements corresponding to the test tasks are as described in Table 1 below.

[0059]

[0060] Table 1

[0061] And in this embodiment, the test task can be designed according to a visual service orchestrator, and the principle of the service orchestrator can be as Figure 5 shown. The service test process orchestrator realizes the drag-and-drop orchestration of the service test process template through the visual drag-and-drop service process orchestration B / S interface at the front end. The user drags as needed according to the WEB interface controls and connects the controls to realize the drag-and-drop orchestration of the service test process template. And after completing the service process orchestration, it is saved as the corresponding service test process template, such as service test process template 1, service test process template 2, service test process template 3, and service test process template n, etc. Moreover, through service test process management, functions such as adding, modifying, deleting, and querying of each service test process template can be realized. The service test process execution engine can realize the process of loading, analyzing, interpreting, and executing the service test process template.

[0062] After designing each test task, select the test task that needs to be executed from them, and use it as the target test task, and then execute the target test task. The execution process of the target test task can be as Figure 6 shown. Receive the requirements of the customized test task input by the user, and the task dispatching and task management interface sends the task information corresponding to the requirements of the test task to the service orchestrator execution engine. Through the service orchestrator execution engine, the corresponding service test process templates (such as service test process template 1, service test process template 2, service test process template n, etc.) are loaded, analyzed, interpreted, and then executed. And the service orchestrator execution engine will call the microservice interface of the microservice group during the execution of the service test process template, and realize signaling interaction with the in-network network elements and services through the simulation test protocol stack.

[0063] Step S30: If the test result of the running test does not match the preset test conditions, output a fault warning message.

[0064] After obtaining the test result of the running test for the target test task, it is necessary to detect the test result to determine whether the test result matches the preset test conditions. That is, during the execution of the target test task, a microservice call record will be generated by the microservice, and based on this call record, it is determined whether this microservice is executed successfully. For example, in an HTTP test, there is a DNS (Domain Name System) resolution process. If the DNS resolution microservice fails, the system will display that the test fails and the DNS resolution microservice fails. If the microservice fails, it is directly determined that the test result does not match the preset test conditions. If the test is successful, it is also necessary to determine whether the test result exceeds the threshold set by the system. If it exceeds, it is determined that the test result does not match the preset test conditions. The threshold here is the threshold of the business metric, such as the success rate being lower than 99.5%. And when it is determined that the test result of the running test does not match the preset test conditions, the system will output the corresponding fault warning message to remind the user.

[0065] In addition, to assist in understanding the fault warning of the network under test in this embodiment and the understanding of the fault warning system architecture model, the following is an example for illustration.

[0066] For example, as Figure 7 shown, the 5GC fault detection and measurement system includes a presentation layer, an interface layer, a service orchestration and analysis layer, a service implementation layer, and a simulation protocol layer. The interface layer is connected to the OSS network management interface, and the simulation protocol layer is connected to the 5G SA core network. Among them, the presentation layer includes a Web management module, test management, business KPI monitoring management, fault warning management, and data analysis. And the presentation layer generates various test tasks through web customization, including immediate tasks, loop tasks, and scheduled tasks, etc., and sends various test tasks to the business orchestration execution engine of the service orchestration layer as required through the interface layer. The interface layer includes a management API interface, an alarm and statistical analysis API interface, and a third-party API interface. And the interface layer can achieve decoupling between the task layer and the service orchestration layer. The service orchestration and analysis layer includes service orchestration management, a service orchestrator execution engine, and Flink big data call record analysis. The service orchestration and analysis layer can achieve visual and drag-and-drop business test process orchestration. The service implementation layer includes business microservice management, a distributed business microservice group, and business call record storage. The service implementation layer can achieve microservice encapsulation and implementation of various test service atomic functions. The simulation protocol layer includes protocol stack management, gNB (i.e., gNodeB) simulation (N1 / N2 / N3), AMF simulation, SMF simulation, and other 5G network element simulations.

[0067] Moreover, in this embodiment, it is possible to achieve traversal testing of each network element and service in the network under test (such as a 5G network) for a preset duration, set fault warnings for the test network elements in the network under test according to the target network elements specified by the user, and achieve specified testing and fault boundary location of the network under test through multi-network element simulation; real-time monitoring and warning of 5G service quality, etc. are achieved through specific service testing. Moreover, in this embodiment, each microservice generates a microservice call record, and this microservice call record supports the presentation of test failure information, so that users can deduce the faulty network element or the cause of the fault. Moreover, the fault warning solution in this embodiment can be applied to unit testing of the 5GC service architecture, and has the advantages of fast warning, rapid iteration of new services, and avoiding repeated development.

[0068] In this embodiment, first, all the test network elements in the network under test are determined, and simulation microservices are performed on each test network element to obtain the microservices corresponding to each test network element. Then, a target test task is constructed based on each microservice, and the target test task is run for testing. When the test result does not match the preset test conditions, a fault warning message is output, thus avoiding the phenomenon in the prior art where data collection needs to be carried out and post-event analysis is performed, resulting in untimely discovery of fault information and low warning timeliness. By actively simulating the testing of each test network element, a fault warning message can be output in advance when a problem is found, thereby improving the timeliness of network fault warning.

[0069] Furthermore, based on the first embodiment of the present invention above, a second embodiment of the fault warning method of the present invention is proposed. In this embodiment, step S10 in the above embodiment, the step of performing simulation microservices on each of the test network elements to obtain the microservices corresponding to each of the test network elements is refined as follows:

[0070] Step a, traverse each of the test network elements and determine all the network element interfaces corresponding to the traversed test network elements;

[0071] In this embodiment, after determining multiple test network elements, each test network element can be traversed, and all the network element interfaces corresponding to the traversed test network elements can be determined. For example, the network element interfaces N1, N2, N3 of gNodeB, the network element interfaces N11, N8, N15 of AMF, and the network element interfaces N10, N7 of SMF, etc.

[0072] Step b, perform simulation microservices on each of the network element interfaces to obtain the microservices corresponding to the traversed test network elements.

[0073] Then, each network element interface is simulated in turn, and microservices are encapsulated to obtain the microservices corresponding to the traversed test network elements. In this embodiment, the microservices include gNodeB simulation microservices, AMF simulation microservices, and SMF simulation microservices. Therefore, the overall simulation model in this embodiment can be as follows: Figure 8 5G simulation dialing includes simulation of AMF (network element interfaces Namf, N8, N15, N22), simulation of SMF (network element interfaces Namf, N10, N7), 5GgNodeB signaling processing (N2) interface simulation, 5GgNodeB media processing (N3) interface simulation, and 5G user UE (N1 interface) simulation. And through the network element interfaces N1, N2, N3, N4, N6, N7, N8, N10, N15, N22 and Namf, the testing of each network element is realized, such as network element (R)AN ((Radio)Access Network), UPF (User plane Function), DN (Datanetwork, operator service), AUSF (Authentication Server Function), AMF (Access and Mobility Management Function), SMF (Session Management Function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (NF Repository Function), PCF (Policy Control function), UDM (Unified Data Management) and AF (Application Function), etc.

[0074] For example, by simulating the N1, N2, and N3 interfaces, a gNodeB simulation microservice (one of the microservices) is constructed to simulate 5G UEs and 5G (R) ANs. When simulating the interfaces, the 5G standard protocol model published by 3GP can be referred to. For example, the 5G NAS protocol (N1 interface) is simulated according to TS 24.501 to implement operations such as simulating user registration management, connection management, activation, and deactivation of the user plane connection. Similarly, the AMF simulation microservice and the SMF simulation microservice can be carried out in the same way. The AMF simulation microservice includes the interface simulation functions of N8, N10, N11, and N15. The SMF simulation microservice includes the interface simulation functions of N7 and N10.

[0075] In this embodiment, by traversing each test network element and performing microservices on all the network element interfaces corresponding to the traversed test network elements, the microservices corresponding to the traversed test network elements are obtained, thus ensuring the accuracy of the obtained microservices.

[0076] Specifically, the steps of performing microservices on each of the network element interfaces to obtain the microservices corresponding to the traversed test network elements include:

[0077] Step c: Traverse each of the network element interfaces, determine the protocol model corresponding to the traversed network element interface, and perform interface simulation on the traversed network element interface according to the protocol model to obtain a simulated interface;

[0078] In this embodiment, after determining each network element interface, such as network element interfaces N1, N2, N3, etc., each network element interface can be traversed, and the protocol model corresponding to each network element interface, that is, the protocol model corresponding to the traversed network element interface, needs to be determined, so as to perform interface simulation on the traversed network element interface according to the protocol model corresponding to the traversed network element interface to obtain a simulated interface. For example, the N1 interface is simulated using the 5G NAS protocol model, and the N3 interface is simulated using the GTP-U protocol model, etc. The protocol model corresponding to each network element interface may be different.

[0079] Step d: Perform microservice encapsulation on the simulated interfaces corresponding to each of the network element interfaces to obtain the microservices corresponding to the traversed test network elements.

[0080] After determining the simulated interfaces corresponding to each network element interface, it is necessary to perform microservice encapsulation operations on each simulated interface to obtain the microservice model corresponding to the traversed test network element, that is, the microservice. And in this embodiment, each test network element corresponds to its own microservice.

[0081] In this embodiment, by traversing each network element interface and performing interface simulation on the traversed network element interface according to the protocol model corresponding to the traversed network element interface to obtain a simulated interface, and then performing microservice encapsulation on each simulated interface to obtain the microservices corresponding to the traversed test network elements, the accuracy of the obtained microservices is guaranteed.

[0082] Further, the steps of constructing a target test task according to each of the microservices include:

[0083] Step e, determining the test content corresponding to each of the test network elements, traversing each of the test content, and determining the test process corresponding to the traversed test content;

[0084] In this embodiment, after constructing each microservice and forming the microservice controls (i.e., the display icons corresponding to the microservices) of each microservice, the test content corresponding to each test network element can be determined first, and the test content can be set according to the user's needs. If there are multiple test contents, each of the test content can be traversed, and the test process corresponding to the traversed test content can be determined.

[0085] Step f, obtaining the microservice controls corresponding to each of the microservices, and performing arrangement and connection processing on each of the microservice controls according to the test process to obtain the test task corresponding to the traversed test content;

[0086] After determining the test process, a test case creation page can be opened according to the received test task creation instruction, and information such as the number and name of the test case can be determined according to the parameter information input by the user. Then, a case arrangement interface is opened, and case arrangement design is performed according to the business process (i.e., the test process). That is, the required microservice controls can be selected from each microservice control according to the test process for drag-and-drop processing, and then each of the dragged microservice controls is connected according to the test process, and corresponding parameter settings are performed to obtain the test case corresponding to the traversed test content, and this test case is used as the test task.

[0087] Step g, determining the target test task in each of the test tasks according to the input selection instruction.

[0088] After constructing each test task, the test task to be tested can be selected from each test task according to the selection instruction input by the user and used as the target test task.

[0089] In this embodiment, by traversing the test content corresponding to each test network element, determining the test process corresponding to the traversed test content, performing arrangement and connection processing on the microservice controls corresponding to each microservice according to the test process to obtain the test task, and determining the target test task in each test task according to the selection instruction, the effectiveness of the obtained target test task is guaranteed.

[0090] Specifically, the step of performing an orchestration connection process on each of the microservice controls according to the test process to obtain a test task corresponding to the traversed test content includes:

[0091] Step h, obtaining a drag trajectory received by a terminal display interface corresponding to the network under test, and dragging all target microservice controls in each of the microservice controls from a preset area to be orchestrated to a process template area corresponding to the test process according to the drag trajectory;

[0092] In this embodiment, when creating a test task, the user can directly drag each microservice control to construct a test task. That is, the system receives a drag instruction input by the user, and determines a display screen for constructing a test task in the display interface of the machine terminal corresponding to the network under test. The display screen includes an area to be orchestrated and a process template area. And the system receives the drag trajectory of the user in the display screen in the display interface, that is, the drag trajectory, and then drags the target microservice controls corresponding to the drag instruction in each of the microservice controls from a preset area to be orchestrated (all unused microservice controls are placed in this area) to a process template area corresponding to the test process (a test task can be constructed in this area).

[0093] Step k, performing a connection process on all target microservice controls in the process template area according to the test process to obtain a test task corresponding to the traversed test content.

[0094] And after the dragging of each microservice control is completed, all the existing target microservice controls in the process template area can be sequentially connected according to the test process to obtain a corresponding test example, and this test example is used as a test task corresponding to the traversed test content.

[0095] In this embodiment, by dragging all target microservice controls from the area to be orchestrated to the process template area according to the input drag instruction and performing a connection process, a test task corresponding to the traversed test content is obtained, thereby ensuring the effectiveness of the obtained test task.

[0096] Further, the step of outputting a fault warning message if the test result of the running test does not match the preset test condition includes:

[0097] Step m, determining whether the microservice corresponding to the target test task is successfully executed according to the test result of the running test;

[0098] In this embodiment, when running a test on a target test task and after obtaining the test result of the running test, it is necessary to determine the microservices corresponding to the target test task, that is, the microservices applied during the execution of the target test task, and determine whether each microservice is successfully executed according to the microservice call records generated by these microservices during the test process of the target test task.

[0099] Step n, if the execution is not successful, it is determined that the test result does not match the preset test conditions, and a fault warning message is output.

[0100] When it is found through judgment that if all the microservices corresponding to the target test task are not successfully executed, it is determined that the structure of the running test does not match the preset test conditions, and a corresponding fault warning message will be output to inform the user which test network elements corresponding to the microservices have faults.

[0101] In this embodiment, by determining that the microservices corresponding to the target test task are not successfully executed according to the test result of the running test, it is determined that the test result does not match the preset test conditions, and a fault warning message is output, thereby ensuring the effective output of the fault warning message.

[0102] In addition, referring to Figure 3 , the embodiment of the present invention also provides a fault warning device, including:

[0103] Microservice module A10, configured to determine all test network elements in the network to be tested, and perform simulation microservices on each of the test network elements to obtain the microservices corresponding to each of the test network elements;

[0104] Test module A20, configured to construct a target test task according to each of the microservices, and perform a running test on the target test task;

[0105] Output module A30, configured to output a fault warning message if the test result of the running test does not match the preset test conditions.

[0106] Optionally, the microservice module A10 is configured to:

[0107] Traverse each of the test network elements to determine all network element interfaces corresponding to the traversed test network elements;

[0108] Perform simulation microservices on each of the network element interfaces to obtain the microservices corresponding to the traversed test network elements.

[0109] Optionally, the microservice module A10 is configured to:

[0110] Traverse each of the network element interfaces to determine the protocol model corresponding to the traversed network element interfaces, and perform interface simulation on the traversed network element interfaces according to the protocol model to obtain simulation interfaces;

[0111] Microservice encapsulation is performed on the simulation interfaces corresponding to each of the network element interfaces to obtain the microservices corresponding to the traversed test network elements.

[0112] Optionally, the microservice module A10 is used for:

[0113] The microservices include gNodeB simulation microservices, AMF simulation microservices, and SMF simulation microservices.

[0114] Optionally, the test module A20 is used for:

[0115] Determine the test content corresponding to each of the test network elements, traverse each of the test contents, and determine the test process corresponding to the traversed test content;

[0116] Obtain the microservice controls corresponding to each of the microservices, and perform orchestration connection processing on each of the microservice controls according to the test process to obtain the test tasks corresponding to the traversed test content;

[0117] Determine the target test tasks among each of the test tasks according to the input selection instruction.

[0118] Optionally, the test module A20 is used for:

[0119] Obtain the dragging trajectory received by the terminal display interface corresponding to the network to be tested, and drag all the target microservice controls in each of the microservice controls from the preset area to be orchestrated to the process template area corresponding to the test process according to the dragging trajectory;

[0120] Perform connection processing on all the target microservice controls in the process template area according to the test process to obtain the test tasks corresponding to the traversed test content.

[0121] Optionally, the output module A30 is used for:

[0122] Determine whether the microservices corresponding to the target test tasks are successfully executed according to the test results of the running test;

[0123] If not successfully executed, determine that the test results do not match the preset test conditions, and output a fault warning message.

[0124] Wherein, the steps implemented by each functional module of the fault warning device can refer to the respective embodiments of the fault warning method of the present invention, which will not be elaborated here.

[0125] In addition, the present invention also provides a fault warning device, and the terminal includes: a memory, a processor, a communication bus, and a fault warning program stored on the memory:

[0126] The communication bus is used to implement the connection and communication between the processor and the memory;

[0127] The processor is used to execute the fault warning program to implement the steps of the above-mentioned fault warning method in various embodiments.

[0128] The present invention also provides a computer-readable storage medium, which stores one or more programs, and the one or more programs can also be executed by one or more processors to implement the steps of the above-mentioned fault warning method in various embodiments.

[0129] The specific implementation manner of the computer-readable storage medium of the present invention is basically the same as that of the above-mentioned fault warning method in various embodiments, and will not be elaborated herein.

[0130] It should be noted that in this article, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or system. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of another identical element in the process, method, article or system including that element.

[0131] The serial numbers of the above-mentioned embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0132] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions for causing a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in various embodiments of the present invention.

[0133] The above are only the preferred embodiments of the present invention, and do not limit the patent scope of the present invention accordingly. Any equivalent structure or equivalent process transformation made by using the specification and drawings of the present invention, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present invention.

Claims

1. A fault warning method, characterized in that, the fault warning method comprises the following steps: Determine all test network elements in the network to be tested, and perform simulation microservices on each of the test network elements to obtain microservices corresponding to each of the test network elements; wherein, perform interface simulation microservices on the network elements gNodeB, AMF, and SMF of the control plane 5GC of the 5G network, and access the test network elements under 5GC in a single-point access mode of the simulation module, wherein the test network elements include AMF, UPF, and SMF, and the network to be tested includes a 5G network; Construct a target test task according to each of the microservices, and perform a running test on the target test task; If the test result of the running test does not match the preset test conditions, output a fault warning message; wherein, the microservices include gNodeB simulation microservices, AMF simulation microservices, and SMF simulation microservices; The construction process of the gNodeB simulation microservice includes simulating the 5G NAS protocol of the N1 interface according to TS24.501, implementing the simulation of the N2 interface according to the NG-AP protocol defined in 38.413 and the SCTP protocol defined in RFC4960, and simulating the N3 interface according to the GTP-U protocol defined in TS29.281; the N1 interface is the interface between the UE and the AMF, the N2 interface is the interface between the AMF and the AN or RAN, and the N3 interface is the interface between the UPF and the AN or RAN; The construction process of the AMF simulation microservice includes simulating the N8 interface using the HTTP / TCP protocol, simulating the N11 interface using the HTTP2 protocol, and simulating the N15 interface using the HTTP / TCP protocol; the N8 interface is the interface between the AMF and the UDM, the N11 interface is the interface between the AMF and the SMF, and the N15 interface is the interface between the AMF and the PCF; The construction process of the SMF simulation microservice includes simulating the N10 and N7 interfaces using the HTTP / TCP protocol; the N10 interface is the interface between the SMF and the UDM, and the N7 interface is the interface between the SMF and the PCF.

2. The fault warning method according to claim 1, characterized in that, the step of performing simulation microservices on each of the test network elements to obtain microservices corresponding to each of the test network elements includes: Traverse each of the test network elements to determine all network element interfaces corresponding to the traversed test network element; Perform simulation microservices on each of the network element interfaces to obtain microservices corresponding to the traversed test network element.

3. The fault warning method according to claim 2, characterized in that, the step of performing simulation microservices on each of the network element interfaces to obtain microservices corresponding to the traversed test network element includes: Traverse each of the network element interfaces to determine the protocol model corresponding to the traversed network element interface, and perform interface simulation on the traversed network element interface according to the protocol model to obtain a simulation interface; Perform microservice encapsulation on the simulation interfaces corresponding to each of the network element interfaces to obtain microservices corresponding to the traversed test network element.

4. The fault warning method according to claim 1, characterized in that, The step of constructing a target test task according to each of the microservices includes: Determine the test content corresponding to each of the test network elements, traverse each of the test contents, and determine the test process corresponding to the traversed test content; Obtain the microservice controls corresponding to each of the microservices, and perform an orchestration connection process on each of the microservice controls according to the test process to obtain a test task corresponding to the traversed test content; Determine the target test task in each of the test tasks according to the input selection instruction.

5. The fault warning method according to claim 4, characterized in that The step of performing an orchestration connection process on each of the microservice controls according to the test process to obtain a test task corresponding to the traversed test content includes: Obtain the dragging trajectory received by the terminal display interface corresponding to the network to be tested, and drag all the target microservice controls in each of the microservice controls from a preset area to be orchestrated to the process template area corresponding to the test process according to the dragging trajectory; Perform a connection process on all the target microservice controls in the process template area according to the test process to obtain a test task corresponding to the traversed test content.

6. The fault warning method according to claim 1, characterized in that The step of outputting a fault warning message if the test result of the running test does not match the preset test condition includes: Determine whether the microservice corresponding to the target test task is successfully executed according to the test result of the running test; If it is not successfully executed, determine that the test result does not match the preset test condition, and output a fault warning message.

7. A fault warning device, characterized in that The fault warning device includes: A microservice module is used to determine all test network elements in the network to be tested, and perform simulation microservices on each of the test network elements to obtain the microservices corresponding to each of the test network elements. Among them, interface simulation microservices are performed on the network elements gNodeB, AMF, and SMF of the control plane 5GC of the 5G network, and the test network elements under 5GC are accessed in a single-point access mode of the simulation module. The test network elements include AMF, UPF, and SMF, and the network to be tested includes the 5G network. Among them, the microservices include gNodeB simulation microservice, AMF simulation microservice, and SMF simulation microservice. The construction process of the gNodeB simulation microservice includes simulating the 5G NAS protocol of the N1 interface according to TS24.501, implementing the simulation of the N2 interface according to the NG-AP protocol defined in 38.413 and the SCTP protocol defined in RFC4960, and simulating the N3 interface according to the GTP-U protocol defined in TS29.

281. The N1 interface is the interface between the UE and the AMF, the N2 interface is the interface between the AMF and the AN or RAN, and the N3 interface is the interface between the UPF and the AN or RAN. The construction process of the AMF simulation microservice includes simulating the N8 interface using the HTTP / TCP protocol, simulating the N11 interface using the HTTP2 protocol, and simulating the N15 interface using the HTTP / TCP protocol. The N8 interface is the interface between the AMF and the UDM, the N11 interface is the interface between the AMF and the SMF, and the N15 interface is the interface between the AMF and the PCF. The construction process of the SMF simulation microservice includes simulating the N10 and N7 interfaces using the HTTP / TCP protocol. The N10 interface is the interface between the SMF and the UDM, and the N7 interface is the interface between the SMF and the PCF. A test module is used to construct a target test task according to each of the microservices and perform a running test on the target test task. An output module is used to output a fault warning message if the test result of the running test does not match the preset test conditions.

8. A fault warning device Characterized in that The fault warning device includes: a memory, a processor, and a fault warning program stored on the memory and executable on the processor. When the fault warning program is executed by the processor, the steps of the fault warning method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium Characterized in that The computer-readable storage medium stores a fault warning program, and when the fault warning program is executed by a processor, the steps of the fault warning method according to any one of claims 1 to 6 are implemented.

Citation Information

Patent Citations

  • Automatic testing method, device and system for LTE core network

    CN104135735A

  • Test system and method for 5G core network micro-service architecture

    CN111147322A