Method and device for testing user plane function network element in core network, and electronic equipment

Abstract

The invention discloses a method and a device for testing a user plane function network element in a core network, and electronic equipment. The method comprises the following steps: determining a plurality of target network elements which directly interact with a user plane function network element, and simulating the plurality of target network elements through a test instrument to obtain a plurality of simulated network elements; a plurality of simulation network elements are controlled by the test instrument to test the user plane function network element according to a plurality of different types of test forms to obtain a test result, and the plurality of different types of test forms are used for testing different levels of test requirements of the user plane function network element. And testing the user plane function network element through the plurality of test cases. The technical problem of low efficiency caused by the fact that the execution of the test case depends on manual operation when the user plane function network element is tested is solved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a testing method, apparatus, and electronic equipment for user plane functional network elements in a core network. Background Technology

[0002] In the current 5G network core architecture, the User Plane Function (UPF) network element plays an indispensable role, responsible for functions such as packet forwarding, routing, and billing. However, the UPF testing methods and technologies related to this technology face significant limitations.

[0003] Traditional testing methods often focus on functional verification, particularly in user plane services, session management, and control plane interfaces. Such testing often neglects performance evaluation, fault recovery capabilities, and behavioral verification under abnormal scenarios, lacking comprehensive testing capabilities covering performance, fault recovery, and abnormal scenarios. Test case execution, result collection, and analysis heavily rely on manual operations, requiring human intervention at certain points to continue the testing process, including dynamically modifying configurations, querying the status of the tested object, and verifying target metrics, leading to low testing efficiency.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a testing method, apparatus, and electronic device for user plane functional network elements in a core network, so as to at least solve the technical problem that the execution of test cases relies on manual operation when testing user plane functional network elements, resulting in low efficiency.

[0006] According to one aspect of the embodiments of this application, a testing method for user plane functional network elements in a core network is provided, comprising: determining multiple target network elements that directly interact with the user plane functional network elements, and simulating the multiple target network elements using a test instrument to obtain multiple simulated network elements; controlling the multiple simulated network elements to test the user plane functional network elements according to multiple different types of test forms using the test instrument to obtain test results, wherein the multiple different types of test forms are used to test the user plane functional network elements for different levels of testing requirements, and the user plane functional network elements are tested using multiple test cases.

[0007] Optionally, the user plane function network element is tested by controlling multiple simulated network elements according to multiple different types of test forms through test instruments. This includes: determining the test requirement type and the target test form corresponding to the test requirement type; controlling the simulated network element corresponding to the test requirement type through test instruments; determining all test cases required to test the user plane function network element and the number of copies required for each test case according to the target test form; creating test case copies of the corresponding number; and testing the user plane function network element by executing the test case copies.

[0008] Optionally, determining the test requirement type and the corresponding target test form includes: when the test requirement type is to verify the functional integrity of user plane functional network elements, determining the target test form corresponding to the test requirement type as an automated test form; when the test requirement type is to verify the ability of user plane functional network elements to handle high-concurrency user sessions, determining the target test form corresponding to the test requirement type as a multi-session test form; and when the test requirement type is to verify the performance of user plane functional network elements, determining the target test form corresponding to the test requirement type as a performance test form.

[0009] Optionally, each test case contains multiple steps, which are executed sequentially. Each step is an event, and the event is the smallest unit of a test case, used to simulate the interaction between network elements and user plane functional network elements.

[0010] Optionally, the event types include at least one of the following: Packet Forwarding Control Protocol (PTP) control plane message events, User Datagram Protocol / General Packet Radio Service (GPRS) Tunneling Protocol (GPRS) data plane message events, operational events, and characteristic events. Specifically, PTP control plane message events are used to simulate the interaction between session management function network elements and user plane function network elements based on PTP; GPRS data plane message events are used to simulate the uplink and downlink of user traffic and the opening and closing of data plane packets, and to verify the data processing capabilities of user plane function network elements; operational events are used to perform operations on user plane function network elements or the server where user plane function network elements reside in a preset format, and the operations include at least one of the following: querying the status of user plane function network elements, modifying the configuration information of user plane function network elements, and installing, upgrading, and uninstalling user plane function network elements; characteristic events are events set in preset test scenarios to meet preset test requirements, and are used at least to test the anomaly handling capabilities of user plane function network elements.

[0011] Optionally, test forms and test cases are stored in the form of a test case directory tree. The test case directory tree includes a first-level directory, which includes test case files and various types of test form files. The various types of test form files are used to store test forms. The test case files contain multiple second-level directories, which include a first-class directory and a second-class directory. Each second-class directory is used to store multiple test cases belonging to one type of event. The first-class directory is used to store all test cases required for a complete test process under a test requirement type, as well as the number of test case copies. The first-class directory references the second-class directory, and the various types of test form files reference the first-class directory.

[0012] Optionally, the method further includes: collecting abnormal message fragments containing the target fault process, generating a packet capture message file based on the abnormal message fragments; parsing the network fault communication data in the packet capture message file using the target script, and constructing new test cases based on the network fault communication data.

[0013] Optionally, the method further includes: during the execution of test cases, the test results of each test case are integrated into a test report, wherein the test report includes the pass rate of each test case in each test form, and the execution status of each test case.

[0014] According to another aspect of the embodiments of this application, a testing apparatus for user plane functional network elements in a core network is also provided, comprising: a determination module, configured to determine multiple target network elements that directly interact with the user plane functional network elements, and to simulate the multiple target network elements through a testing instrument to obtain multiple simulated network elements; and a testing module, configured to control the multiple simulated network elements to test the user plane functional network elements according to multiple different types of test forms through the testing instrument, and to obtain test results, wherein the multiple different types of test forms are used to test the user plane functional network elements through multiple test cases to meet the testing requirements of different levels of the user plane functional network elements.

[0015] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, wherein a program is stored in the non-volatile storage medium, and the program controls the device where the non-volatile storage medium is located to execute the above-mentioned test method for user plane functional network elements in the core network when it runs.

[0016] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, executes the above-described test method for user plane functional network elements in the core network.

[0017] According to another aspect of the embodiments of this application, a computer program product is also provided, including computer instructions, which, when executed by a processor, implement the above-described test method for user plane functional network elements in the core network.

[0018] In this embodiment, multiple target network elements that directly interact with the user plane functional network element are identified, and multiple target network elements are simulated using test instruments to obtain various simulated network elements. The test instruments control these simulated network elements to test the user plane functional network element according to various different types of test forms, and the test results are obtained. The various different types of test forms are used to address the testing requirements of different levels of the user plane functional network element. By using multiple test cases to test the user plane functional network element, the test instruments simulate multiple simulated network elements, and then the various different types of test forms test the user plane functional network element to obtain test results. This achieves the goal of automated testing of the user plane functional network element without relying on manual intervention, thereby solving the technical problem of low efficiency caused by the reliance on manual operation for test case execution when testing the user plane functional network element. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a hardware structure block diagram of a computer terminal for implementing a test method for user plane functional network elements in a core network, according to an embodiment of this application.

[0021] Figure 2 This is a flowchart of a testing method for user plane functional network elements in a core network according to an embodiment of this application;

[0022] Figure 3 This is a schematic diagram of the software module of a test instrument according to an embodiment of this application;

[0023] Figure 4 This is a schematic diagram of a simulated network element for a UPF full-coverage test instrument according to an embodiment of this application;

[0024] Figure 5 This is a reference relationship diagram between test case folders provided according to an embodiment of this application;

[0025] Figure 6 This is a schematic diagram of the instrument panel of the first type of test instrument provided according to the embodiments of this application;

[0026] Figure 7This is a schematic diagram of the instrument panel of the second type of test instrument provided according to the embodiments of this application;

[0027] Figure 8 This is a schematic diagram of the instrument panel of the third type of test instrument provided according to the embodiments of this application;

[0028] Figure 9 This is a schematic diagram of the instrument panel of the fourth type of test instrument provided according to the embodiments of this application;

[0029] Figure 10 This is a schematic diagram of the instrument panel of the fifth type of test instrument provided according to the embodiments of this application;

[0030] Figure 11 This is a schematic diagram of the instrument panel of the sixth type of test instrument provided according to the embodiments of this application;

[0031] Figure 12 This is a network topology diagram of a test method for user plane functional network elements in the core network provided in the embodiments of this application;

[0032] Figure 13 This is a schematic diagram of the structure of a test device for user plane functional network elements in a core network, according to an embodiment of this application. Detailed Implementation

[0033] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0034] The information collected in this application embodiment is information and data authorized by the user or fully authorized by all parties. The collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant regions, and necessary confidentiality measures have been taken. It does not violate public order and good morals, and provides corresponding operation entry points for users to choose to authorize or reject the automated decision results. If the user chooses to reject, the process will proceed to the expert decision-making process.

[0035] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0036] To better understand the embodiments of this application, the technical terms involved in the embodiments of this application are explained below:

[0037] Next-Generation Node B (gNB): The gNB is a base station device in the 5G Radio Access Network (RAN), responsible for wireless communication with 5G User Equipment (UE). It is a key device on the radio side of the 5G network, forming an end-to-end 5G architecture together with the 5G Core Network (5GC). The gNB supports new 5G features (such as millimeter wave, ultra-low latency, network slicing, etc.), supports the processing of radio signals, user data, and resource scheduling, and connects to the 5G Core Network (5GC).

[0038] Radio Access Network (RAN): In 5G networks, the RAN connects to the 5G core network via NG interfaces (such as NG-C and NG-U), responsible for the wireless connection between terminals (UEs, such as mobile phones and IoT devices) and the core network (5GC), handling wireless signal transmission, resource scheduling, etc. The RAN includes gNBs and 4G base stations compatible with the 5G core network (NextGeneration evolved Node B, ng-eNB, used for Non-Standalone (NSA) networking).

[0039] Data Network (DN): This is a network outside the 5G network that provides data services, such as the Internet, operator-owned services (IPTV, IMS voice core network), enterprise private networks, and cloud computing platforms. It is the external data network that 5G users ultimately access.

[0040] User Plane Function (UPF) is a fundamental component of the 5G Core infrastructure system architecture defined by 3GPP. The main function of the UPF is to implement user plane services in 5G networks, including but not limited to: acting as an interconnection point between Mobile Infrastructure (e.g., RAN) and DN; performing encapsulation and decapsulation of the General Packet Radio Service Tunneling Protocol (GTP-U) (a 3GPP-defined GPRS tunneling protocol) on the User Plane (UP); packet routing and forwarding; QoS (Quality of Service); packet inspection; traffic redirection; traffic billing; and network security.

[0041] Session Management Function (SMF): A 5G core network control plane element responsible for tunnel maintenance, IP address allocation and management, UP function selection, policy implementation and QoS control, billing data collection, roaming, etc.

[0042] Packet Forwarding Control Protocol (PFCP): The communication protocol between SMF and UPF. SMF is used to send out information such as data plane forwarding tunnel creation, billing information, and QoS information, while UPF also uses this protocol for information reporting.

[0043] Session: A carrier created by an end user in the core network to carry the flow of uplink and downlink data. An end user can create multiple sessions.

[0044] Session Identifier (SEID): Used to uniquely identify a session on the UPF.

[0045] In related technologies, test case execution, result collection, and analysis heavily rely on manual operations. Certain nodes require human intervention to continue the testing process, including dynamically modifying configurations, querying the status of the tested object, and verifying target indicators, leading to low testing efficiency. Therefore, there is a technical problem of low efficiency caused by the reliance on manual operations for test case execution when testing user plane functional network elements. To solve this problem, this application provides a related solution, which is described in detail below.

[0046] According to an embodiment of this application, an embodiment of a testing method for user plane functional network elements in a core network is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0047] The methods and embodiments provided in this application can be executed on a computer terminal or similar computing device. Figure 1 A hardware block diagram of a computer terminal for implementing a testing method for user plane functional network elements in a core network is shown. Figure 1 As shown, the computer terminal 10 may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0048] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10. As involved in the embodiments of this application, the data processing circuits serve as processor control (e.g., selection of a variable resistor termination path connected to an interface).

[0049] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the test method of the user plane functional network element in the core network in this embodiment of the application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the above-mentioned test method of the user plane functional network element in the core network. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0050] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0051] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10.

[0052] Under the above operating environment, this application provides an embodiment of a testing method for user plane functional network elements in a core network. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0053] like Figure 2 The diagram shown is a flowchart of a testing method for user plane functional network elements in a core network according to an embodiment of this application, including:

[0054] Step S202: Identify multiple target network elements that directly interact with user plane functional network elements, and simulate multiple target network elements using test instruments to obtain various simulated network elements.

[0055] In some embodiments of this application, to simplify deployment and ensure ease of use, the carrier for executing the testing methods of user plane functional network elements in the core network of this application is determined to be a UPF full-coverage test instrument (hereinafter referred to as the test instrument). The test instrument is a software system specifically designed for fully automated testing of UPF. It is software implemented using GoLang (Go or golang for short, an open-source programming language) and runs on Linux. After appropriate adaptation, it can also be applied to other operating systems. A schematic diagram of the software modules of the test instrument is shown below. Figure 3 As shown, it includes a tester configuration / test object basic configuration management module, an interface management / network element simulation module, a test case management module, a test case execution module, a data statistics / test report integration module, and a user interface / data display and browsing interface. Through the rational modularization of each functional component, it achieves a high degree of customization of test cases and automation and monitorability of the testing process.

[0056] The Test Instrument Configuration / Object-under-Test (UTP) Basic Configuration Management module is responsible for configuring the test instrument itself and managing the configuration of the UPF. It allows users to set the test instrument's operating parameters, such as connection settings, test parameters, and environment variables, and dynamically modify the UPF's configuration information, such as node ID, IP address, and port number. This ensures that testing can be performed under different configuration conditions to verify the UPF's performance and stability under various circumstances. The Interface Management / Network Element Simulation module is the core of the UPF-encompassing test instrument, simulating various network elements that directly interact with the UPF. Through these simulated network elements, the test instrument can communicate with the UPF on the control plane and data plane using standard protocols such as PFCP and GTP-U, reproducing the interaction in a real network environment. This module also manages the interfaces of these simulated network elements, ensuring that test cases can accurately send and receive messages, thereby testing the UPF's functionality and performance. The Test Case Management module is used to create, edit, and manage test cases. The modular design of test cases allows users to build complex test processes by combining different test steps and scenarios. This module provides test case storage and retrieval functions, supporting advanced search and categorization, allowing users to quickly find or create the required test cases according to their needs. The test case execution module is responsible for executing the test processes defined in the test cases. This includes, for example, control plane message events, data plane message events (such as UDP / GTP-U), operation events, and feature events. The execution module can automatically execute test cases, monitor test progress, and automatically handle any anomalies that may occur during testing, such as timeouts and failed responses. The data statistics / test report integration module collects and analyzes data during the testing process, generating detailed test reports. These reports include the execution results of the test cases, reasons for failure, and statistical metrics (such as the number of packets sent and received, packet loss rate, etc.). Furthermore, this module can integrate the results of multiple test cases, providing overall test coverage and pass rate reports to help quickly locate problems and evaluate UPF performance. The user interface / data module display and browsing interface provides an intuitive user interface, allowing users to easily configure test parameters, select test cases, start and monitor the test process, and view and analyze test results. The user-friendly interface supports real-time data display, such as graphical statistics on dashboards, and detailed log viewing, enabling technicians to quickly understand the test status and perform debugging. These modules together constitute a highly automated and user-friendly testing system capable of performing not only routine functional tests but also performance, fault recovery, and abnormal scenario tests, significantly improving the efficiency and accuracy of UPF testing.

[0057] In step S202, several target network elements that directly interact with the User Plane Function (UPF) are first identified. Specifically, based on the 5G core network architecture, network elements that directly interact with the UPF are identified. Direct interaction means that there is a direct communication link or interface between the two network elements, enabling data exchange and control information transmission without going through other intermediate network elements or processing layers. These include GNB, Evolved Node BaseStation (ENB), Session Management Function (SMF), DN, and another simulated UPF (sim-UPF, a virtual component used in the test environment to simulate UPF behavior and test UPF behavior when communicating with other UPFs in the data plane). These network elements are key points for UPF interaction under normal operation and abnormal scenarios. The identification of each network element is based on its position and function in the network architecture. Multiple target network elements are simulated using test instruments, resulting in various simulated network elements. These simulated network elements are implemented through the interface management / network element simulation module. In essence, these simulated network elements are virtual network elements created by the test instruments by simulating the functions of corresponding real network elements. Specifically, simulated network elements refer to those implemented by the test instruments in software to mimic the functions and behaviors of various physical network elements in a real network. Each simulated network element executes its own set of test steps defined in the test cases. These steps are designed for specific network functions and interactions. Each step in the test case is assigned to a specific simulated network element participating in the interaction, such as sending, receiving, and verifying custom messages. Simulated network elements can generate and send custom PFCP control plane messages or UDP / GTP-U data plane messages. These messages can be modified to include specific test data, such as specific UE identifiers, tunnel information, and QoS parameters, to trigger different behaviors of the UPF.

[0058] like Figure 4The diagram shown is a schematic of a simulated network element in a UPF full-coverage test instrument according to an embodiment of this application. The green square represents the object under test, i.e., the UPF; the yellow square represents the instrument; and the gray square represents the simulated network elements simulated by the UPF full-coverage test instrument, including GNB simulated network elements, ENB simulated network elements, SMF simulated network elements, DN simulated network elements, and sim-UPF simulated network elements. The GNB simulated network element interacts with the UPF through the N3 interface (the N3 interface is the user plane interface between the GNB and the UPF), the ENB simulated network element interacts with the UPF through the S1-u interface (the S1-u interface is the user plane interface between the ENB and the SGW), the SMF simulated network element interacts with the UPF through the N4 interface (the N4 interface is the control plane interface between the SMF and the UPF), and the DN simulated network element interacts with the UPF through the N6 interface (the N6 interface is the interface between the UPF and the data network (DN)). Through the simulation of these standardized interfaces, the UPF full-coverage test instrument can create a test environment highly similar to a real network, comprehensively testing the functionality and performance of the UPF in different scenarios. Figure 4 As shown, the test instrument also connects directly to the UPF via a REST-based application programming interface (REST API) or a Secure Shell (SSH) + bash command to perform operations such as configuration management, status query, and metric verification. This interaction is mainly used to test the management and operation functions of the UPF, as well as to obtain necessary statistical data during the test. The REST API is a network application programming interface for data exchange between clients and servers. It follows the Representational State Transfer (REST) ​​architectural principle and uses the HTTP protocol for communication. The REST API is used for direct interaction between the test instrument and the UPF to implement operations such as configuration management, status query, and metric verification. SSH is a network protocol used for secure remote management of connections and services. It allows users to securely transfer commands and files between computers over insecure networks. Bash is one of the most common shells (command line interpreters) in Unix and Linux operating systems, used to execute user-input commands, read and execute scripts, and provide an interactive command-line environment. When using SSH and bash together, the test instrument can connect to the server running UPF via the SSH (same as SSH) protocol, and then execute specific commands or scripts through the bash shell on the server to perform deeper configuration modifications, system operations, and log analysis.

[0059] Step S204: Using test instruments, control various analog network elements to test the user plane functional network elements according to various different types of test forms, and obtain the test results.

[0060] In the technical solution provided in step S204, various types of test forms are used to test user plane functional network elements at different levels to meet the testing requirements, and multiple test cases are used to test user plane functional network elements.

[0061] In the technical solution provided in step S204, there are multiple ways to control multiple simulated network elements to test user plane functional network elements according to multiple different types of test forms through the test case execution module of the test instrument. For example: determine the test requirement type and the target test form corresponding to the test requirement type; control the simulated network element corresponding to the test requirement type through the test instrument; determine all test cases required to test the user plane functional network element and the number of copies required for each test case according to the target test form; create test case copies with the corresponding number of copies; and test the user plane functional network element by executing the test case copies.

[0062] In the above steps, there are multiple ways to determine the test requirement type and the corresponding target test form. For example, if the test requirement type is to verify the functional integrity of user plane network elements, the target test form is an automated test form; if the test requirement type is to verify the ability of user plane network elements to handle high-concurrency user sessions, the target test form is a multi-session test form; and if the test requirement type is to verify the performance of user plane network elements, the target test form is a performance test form. These are explained in detail below.

[0063] To achieve comprehensive testing of user plane functional network elements, a comprehensive UPF test coverage system is constructed, supporting test scenarios such as smoke testing, functional integrity regression testing, and abnormal scenario testing. Different test forms are designed for different test requirement types. A test form refers to a form file that references one or more test cases sequentially or in parallel, specifying the number of replicas of each test case to enable multi-session testing. A test case, on the other hand, is a file that defines specific test steps, processes, and scenarios, typically containing only single-session scenarios. When performing comprehensive testing of user plane functional network elements, firstly, the test requirement type and the corresponding target test form are determined. Then, the simulated network element corresponding to the test requirement type is controlled by the test instrument. According to the target test form, all test cases required to test the user plane functional network element and the number of replicas required for each test case are determined, and the corresponding number of test case replicas are created. The user plane functional network element is tested by executing these test case replicas. Setting the number of test case replicas allows the test instrument to create multiple identical test instances. This means that the same test case can be executed multiple times under different conditions or in parallel, helping to check the consistency and stability of UPF when handling similar requests. This is explained in detail below.

[0064] The pre-designed test form for the test requirement type of verifying the functional integrity of user plane functional network elements is named the Automated Test Form. The Automated Test Form will reference multiple test cases serially or in parallel to implement smoke testing and functional integrity testing. The constructed Automated Test Form verifies whether the various functions of the UPF work as expected, thus achieving functional integrity testing. The constructed Automated Test Form is stored in a preset directory (e.g., the AutoTest directory). When the test requirement type is to verify the functional integrity of user plane functional network elements, the target test form corresponding to the test requirement type is determined to be the Automated Test Form. The test instrument reads the Automated Test Form from the AutoTest directory, determines all test cases required to test the user plane functional network elements using this test form, and the number of copies required for each test case. For each test case, the test instrument creates the corresponding number of test case copies and executes all test case copies. When executing each test case copy, according to the scenario described in the test case, the corresponding simulated network element interacts with the user plane functional network element. Specifically, the test instrument schedules the simulated network element to send control plane and data plane messages, and simultaneously executes the events in the test case to simulate a real scenario. During the test, the UPF response was monitored in real time to verify whether the expected results matched the actual results.

[0065] A pre-designed test form for verifying the ability of a user plane functional network element to handle high-concurrency user sessions is named an automated test form. High-concurrency user sessions refer to a situation where a large number of user sessions interact simultaneously in the network. A multi-session test form uses multiple test cases, either serially or in parallel, to test the user plane functional network element's ability to handle high-concurrency user sessions. The constructed multi-session test form is stored in a preset directory (e.g., the multiSessTest directory). When the test requirement type is to verify the ability of a user plane functional network element to handle high-concurrency user sessions, the target test form corresponding to this test requirement type is determined to be the multi-session test form. The test instrument reads the multi-session test form from the multiSessTest directory to determine all the test cases required to test the user plane functional network element using this test form, as well as the number of copies required for each test case. For each test case, the test instrument creates the corresponding number of test case copies and executes all test case copies. When executing each test case copy, based on the scenario described by the test case, it controls the corresponding simulated network element to interact with the user plane functional network element.

[0066] The pre-designed test form belonging to the test requirement type of performance verification of user plane functional network elements is named the performance test form. The performance test form will reference multiple test cases serially or in parallel to implement performance testing of the user plane functional network elements. The constructed performance test form is stored in a preset directory (e.g., a dedicated performance test directory (performanceTest)). When the test requirement type is performance verification of user plane functional network elements, the target test form corresponding to the test requirement type is determined as the performance test form. The test instrument reads the performance test form from the dedicated performance test directory (performanceTest) to determine all test cases required to test the user plane functional network elements using this test form, as well as the number of copies required for each test case. For each test case, the test instrument creates the corresponding number of test case copies and executes all test case copies. When executing each test case copy, based on the scenario described by the test case, it controls the corresponding simulated network element to interact with the user plane functional network element.

[0067] The test forms for the three test requirement types mentioned above cover comprehensive testing of user plane functional network elements. The automated test form focuses on automated testing, suitable for Continuous Integration (CI) / Continuous Delivery (CD) processes, and is used for functional integrity regression testing. This involves running all basic test cases after each software version iteration to ensure no new functional defects are introduced. It is suitable for continuous testing during the development phase, and the included test cases cover all functional points of user plane functional network elements, ensuring the correctness and completeness of the UPF function. The multi-session test form specifically emphasizes the performance of the UPF when handling a large number of simultaneous online sessions (i.e., high-concurrency user sessions). It conducts in-depth testing of concurrency processing capabilities and resource allocation efficiency. Specifically designed for multi-session scenarios, it focuses on verifying the UPF's performance under high concurrency, such as the efficiency and stability of session establishment, data transmission, and session release, ensuring that the UPF can effectively manage resources, handle data traffic, and maintain service quality when multiple users access the network simultaneously. The performance test form primarily focuses on performance metrics such as throughput and latency to evaluate the peak performance and long-term stability of the UPF, ensuring that the UPF's performance under high load conditions meets the requirements of commercial deployment. This hierarchical and functionally defined directory structure, combined with highly customizable and reusable test cases, provides a comprehensive, efficient, and scalable testing solution for 5G core network UPFs.

[0068] In some embodiments of this application, each test form has its unique application scenario. They complement each other, jointly constructing a comprehensive automated testing system capable of evaluating and optimizing the quality and performance of the UPF from different angles and depths. Multiple test forms can be used in combination or individually. Combining multiple test forms enables comprehensive testing of the UPF, and also allows users to select appropriate test forms to execute based on project stage or testing objectives. For example, in the early stages of development or during code submission, automated test forms may be prioritized for rapid smoke testing or functional regression testing to identify and fix functional issues as early as possible. When the functionality becomes stable and it is necessary to understand the UPF's ability to handle multiple sessions, performance test forms can be executed to verify the UPF's resource management and concurrent processing capabilities by simulating a large number of concurrent sessions. Finally, when the product is nearing release or requires performance optimization, performance test forms become crucial, used to identify UPF performance bottlenecks and ensure the product meets the actual needs of commercial deployment.

[0069] It is important to note that each test case contains multiple steps, which are executed sequentially. Each step is an event, and the event is the smallest unit of a test case, used to simulate the interaction between network elements and user plane functional network elements. The event types include at least one of the following: Packet Forwarding Control Protocol (PTP) control plane message events, User Datagram Protocol / General Packet Radio Service (GPRS / GRS) Tunneling Protocol (GPRS / GRS) data plane message events, operational events, and characteristic events. Specifically, PTP / GPRS control plane message events are used to simulate the interaction between session management function (SMS) network elements and user plane function (MPF) network elements based on PTP. GPRS / GPRS / GRS data plane message events are used to simulate user traffic uplink and downlink, as well as the opening and closing of data plane packets, and to verify the data processing capabilities of MPF network elements. Operational events are used to perform operations on MPF ​​network elements or the server where MPF network elements reside in a preset format. These operations include at least one of the following: querying the status of MPF network elements, modifying the configuration information of MPF network elements, and installing, upgrading, or uninstalling MPF network elements. Characteristic events are events set in preset test scenarios to meet preset test requirements and are used to test the anomaly handling capabilities of MPF network elements. Detailed explanations follow.

[0070] To achieve a high degree of customization of test cases, a modular design is adopted. Specifically, each test case contains multiple steps, which are executed sequentially. Each step is an event, and the event type must include at least one of the following: Packet Forwarding Control Protocol (PFCP) control plane message event, User Datagram Protocol / General Packet Radio Service Tunneling Protocol (UDP / GTP-U) data plane message event, operational events, and characteristic events. The PFCP control plane message event is used to simulate the interaction between the session management function network element and the user plane function network element based on the PFCP, specifically including defining the PFCP message body, whether it is received or sent, whether it is manually / automatically triggered by the user, whether there is a delay, and the content to be verified. The UDP / GTP-U data plane message event is responsible for the transmission and management of user plane data, and is used to simulate the uplink and downlink of user traffic and the opening and closing of data plane packets, verifying the data processing capabilities of the user plane function network element. Operational events are used to perform operations on user plane function network elements or the servers where user plane function network elements reside, in preset formats (restAPI / ssh+bash). These operations include at least querying the status of user plane function network elements, modifying their configuration information, installing, upgrading, and uninstalling them, as well as verifying metrics or executing specific Linux commands. Feature events are events set up in preset test scenarios to meet preset test requirements. They are used to test the exception handling capabilities of user plane function network elements, such as triggering the cessation of PFCP heartbeat message transmission in the SMF simulated network element (simulated by test instruments).

[0071] Based on this modular design, test cases are stored in a modular organization, facilitating subsequent management and meeting the requirement of high reusability. The following details the referencing of test cases: Test forms and test cases are stored in a test case directory tree. This tree includes a top-level directory containing test case files and various types of test form files. The test form files contain multiple second-level directories, including first-class and second-class directories. Each second-class directory stores multiple test cases belonging to one type of event. The first-class directory stores all test cases required for a complete test process under a specific test requirement type, along with the number of test case copies. The first-class directory references the second-class directory, and various test form files reference the first-class directory. Below is an example of a test case directory tree:

[0072] ├── autoTest ==> Stores automated test forms related to automated testing.

[0073] │ ├── Regression testing

[0074] │ │ ├──tc_testcase1.json (Test cases 1-12 are just examples. In actual definitions, the naming convention should be English with underscores, and the following principle should be followed: the naming should reflect which test cases are to be executed, the execution order, and the expected results.)

[0075] │ └──tc_testcase2.json

[0076] ├── multiSessTest ==> Stores test forms related to multi-session testing (multi-session test forms)

[0077] │ ├── tc_testcase3.json

[0078] │ ├── tc_testcase4.json

[0079] ├── performanceTest ==> Stores performance testing-related test forms (performance test forms)

[0080] │ └── tc_testcase5.json

[0081] ├── tc ==> tc refers to the directory where the smallest unit of test cases is stored, and it is also the location where the referenced test cases are stored.

[0082] │ ├── asso ==> asso indicates that test cases related to PFCP coupling are stored.

[0083] │ │ ├──Regression testing

[0084] │ │ │ ├── tc_testcase6.json

[0085] │ │ │ ├── tc_testcase7.json

[0086] │ │ ├── tc_testcase8.json

[0087] │ ├── operation ==> operation represents the test cases that store operation-type events.

[0088] │ │ ├──Regression testing

[0089] │ │ │ ├── tc_testcase9.json

[0090] │ │ ├── tc_testcase10.json

[0091] │ ├── sess_C ==> Defines test cases for a complete test flow (e.g., test cases for the PFCP control plane flow).

[0092] │ │ ├──Regression testing

[0093] │ │ │ ├── tc_testcase10.json

[0094] │ ├── sess_U ==> Stores test cases for UDP / GTP-U data plane procedures

[0095] │ │ ├──Regression testing

[0096] │ │ │ ├── tc_testcase11.json

[0097] │ └── testerFeature==> Stores test cases for feature event classes.

[0098] │ ├── tc_testcase12.json

[0099] In the test case directory tree example above, `tc` represents the test case file within the tree. It's the smallest unit for storing test cases and also the location where referenced test cases are stored. The first-level directory includes tests and various other test case files of different types (e.g., `multiSessTest`, `autoTest`, `performanceTest` in the test case directory tree example). Each test case file contains multiple second-level directories. For example, the test case file `tc` contains multiple second-level directories. The second type of directories within these second-level directories includes: `node`, used to store PFCP coupling-related test cases for PFCP control plane message events; `sess_U`, which stores test cases for PFCP control plane processes and defines test cases for data plane-related processes, belonging to the User Datagram Protocol / General Packet Radio Service Tunneling Protocol data plane message event type; `operation`, which defines test cases for operation-related processes, belonging to the operation-type event; `testerFeature`, which defines test cases for feature-related processes, belonging to the feature event type; and `sess_C`, which defines test cases for a complete test process, belonging to the first type of directory mentioned above. The objects stored in each directory and their reference relationships are shown in the table below:

[0100]

[0101] like Figure 5 The diagram shown is a reference relationship diagram between test case folders provided according to an embodiment of this application. Figure 5 As shown in the diagram, the above table is presented in red, representing test forms, including various types of test form files (e.g., multiSessTest, autoTest, and performanceTest in the test case directory tree example). Purple represents test cases, specifically test case files tc. tc contains several subdirectories: node, which stores PFCP coupling-related test cases for PFCP control plane message events; sess_U, which stores test cases for PFCP control plane procedures, defining test cases for data plane-related procedures, belonging to the User Datagram Protocol / General Packet Radio Service Tunneling Protocol data plane message event type; operation, which defines test cases for operation-related procedures, belonging to operation-type events; testerFeature, which defines test cases for feature-related procedures, belonging to feature-type events; and sess_C, which defines test cases for a complete test procedure, referencing node, operation, testerFeature, and sess_U.

[0102] To facilitate the addition of test cases and to directly generate the core parts of test cases from abnormal packets obtained from live network faults, the test case management module uses a target script to convert packets into test case files. This target script can transform a filtered and organized packet capture packet file (pcap packet file) containing only the target abnormal process into the core content of a test case, thus obtaining a new test case. Specifically: it collects abnormal packet fragments containing the target fault process, generates packet capture packet files based on these fragments, parses the network fault communication data in the packet capture packet files using the target script, and constructs new test cases based on this data. Abnormal packet fragments containing the target fault process can be collected from the live network fault location. The live network refers to the network carrying real user services, and the live network fault location refers to the location where a network fault has occurred (e.g., a data center / base station). The collected abnormal packet fragments containing the target fault process are raw data captured from the fault location, which may contain normal service packets and irrelevant broadcasts. Generating a packet capture file from abnormal message fragments involves data cleaning of the abnormal message fragments, retaining only the parts that can reproduce the fault, and unifying them into pcap format to obtain the packet capture file. Finally, a pre-written target script reads the packet capture file, automatically extracting the message fields that could cause the fault, and converting them into structured data (e.g., JSON format) that the test framework can directly use.

[0103] During test case execution, the data statistics / test report integration module consolidates the test results of each test case into a test report. This report includes the pass rate of each test case in the test form, as well as the execution status of each test case. Specifically, as test cases are executed, the test results of each case are collected and output to the test report. After all test cases in the test form have been executed, a final test report is output. This report records the success and failure details of each test case and the final pass rate of the entire automated testing process. This test report also provides CI / CD with a way to verify the final success rate.

[0104] During testing, the user interface / data module display and browsing interface of the test instrument provides an intuitive user interface, such as... Figure 6 The image shown is a schematic diagram of the instrument panel of the first type of test instrument provided according to an embodiment of this application; as shown... Figure 6As shown, after the test instrument starts, users can select test cases and set whether to enable packet capture and the log level. Multiple test cases are displayed in the test case selection section, and users can start and execute test cases. Click "View Test Case" to view test cases. Click the "Collapse Debug" button to perform crash debugging, or click "Exit" to exit the test instrument. For example, if test case 1 is selected, a message will appear below indicating that test case 1 is selected; users can click the button in the lower right corner to proceed to the next step.

[0105] like Figure 7 The diagram shown is a schematic of the instrument panel of a second type of test instrument provided according to an embodiment of this application. It illustrates the structure of the instrument panel, which includes a navigation bar on the left. This navigation bar includes sections for overview, logs, reports, return, exit, and test case control. Test case control includes "Next" and "End," allowing users to manually control the execution of test cases. Figure 7 The corresponding panel after selecting the overview shows that it is divided into overview, N4-PFCP (N4-PFCP refers to the N4 interface that uses PFCP for communication), N4-transmission rate and data plane. The N4-PFCP is selected in the figure, which shows that the entity pair being tested using the N4 interface is SMF-UPF, that is, the test between the SMF simulates the network element and the UPF. It includes message name (messages 1-4), send, resend, receive, which refers to the number of data packets sent, resent, and received in the corresponding message. The test case execution status will be displayed below (XX test case is being executed, XX refers to the selected test case).

[0106] As shown in the figure, Figure 8 The image shown is a schematic diagram of the instrument panel of the third type of test instrument provided according to an embodiment of this application; (The last part, "select," appears to be an error and is left untranslated.) Figure 7 When a test case is selected, the panel displayed after selecting N4-Send Rate in the overview interface shows that N4-Send Rate is displayed in the form of a chart. The horizontal axis is time (one second is a sampling point) and the vertical axis is the send rate, with the unit being packets / second.

[0107] like Figure 9 The image shown is a schematic diagram of the instrument panel of the fourth type of test instrument provided according to an embodiment of this application, showing the selected... Figure 7 When a test case is selected, the panel displayed after selecting the data plane in the overview interface shows the data plane nodes and the data packets sent and received by the nodes, as well as the total number of data packets sent and received by the data plane under this test case and the historical packet loss rate.

[0108] like Figure 10 The image shown is a schematic diagram of the instrument panel of the fifth type of test instrument provided according to an embodiment of this application, showing the selected... Figure 7When a test case is selected, exit the overview interface and select the log to display a panel showing detailed log content.

[0109] like Figure 11 The image shown is a schematic diagram of the instrument panel of the sixth type of test instrument provided according to an embodiment of this application. Figure 11 This diagram illustrates the instrument panel of a testing instrument during report display, showing the selection... Figure 7 When a test case is selected, exiting the overview interface and selecting the report will display a panel showing the detailed test report, including success and failure details for each test case in each test form, specifically the number of user plane data packets sent, the number of user plane data packets received, and the packet loss rate. The report also includes the number of failed tests for each type of test form. Finally, the test summary outputs the total number of test cases, the number of successful test cases, the number of failed test cases, and the pass rate. The test instrument supports command-line triggered startup and can run silently in the background. All logs and test reports are output to local files for CI / CD to access and verify the final test results.

[0110] The network topology diagram of the testing method for user plane functional network elements in the core network in this embodiment of the application is as follows: Figure 12As shown, the UPF interacts with the Tor switch via the N4 interface (enp5s0f0, which is a network interface name used by the UPF to send and receive packets). The Tor switch is a box-type access switch placed on top of the rack, connecting the server first and then the core network. The Tor switch communicates via the N3 / N6 / N9 / S1-u interface (N9 is the data plane connection interface between the UPF and other UPFs) through the 10GE1 / 0 / 21 interface. In the 10GE1 / 0 / 21 interface, 10GE refers to the interface type as 10 Gigabit Ethernet, supporting a transmission speed of 10Gb / s. In 1 / 0 / 21, 1 represents the stack ID (or chassis number, which is 1 for a single unit), 0 represents the slot number (the box-type Tor has only one motherboard, so it is 0); 21 represents the actual port number, that is, the 21st interface on the front panel. The TOR switch interacts with the server of the bearer tester, which is the VM (virtual machine) where the UPF full-package test instrument resides. Similar to 10GE1 / 0 / 25, 10GE1 / 0 / 30, and 10GE1 / 0 / 21, in 10GE1 / 0 / 25, 10GE indicates a 10 Gigabit Ethernet interface supporting a transmission speed of 10Gb / s. In 1 / 0 / 25, 1 represents the stack ID (or chassis number, 1 for a single unit), and 0 represents the slot number (a box-type TOR has only one motherboard, hence 0); 25 represents the actual port number, i.e., the 25th interface on the front panel. Similarly, in 10GE1 / 0 / 30, 10GE indicates a 10 Gigabit Ethernet interface supporting a transmission speed of 10Gb / s. In 1 / 0 / 30, 1 represents the stack ID (or chassis number, 1 for a single unit), and 0 represents the slot number (a box-type TOR has only one motherboard, hence 0); 30 represents the actual port number, i.e., the 30th interface on the front panel.

[0111] This application also provides a schematic diagram of the structure of a testing device for user plane functional network elements in a core network, as shown in the embodiment. Figure 13 As shown, it includes:

[0112] The determination module 1302 is used to determine multiple target network elements that directly interact with user plane functional network elements, and to simulate multiple target network elements through test instruments to obtain a variety of simulated network elements.

[0113] Test module 1304 is used to control various simulated network elements to test user plane functional network elements according to various types of test forms through test instruments and obtain test results. Among them, various types of test forms are used to test user plane functional network elements at different levels according to test requirements, and user plane functional network elements are tested through multiple test cases.

[0114] It should be noted that, Figure 13The test apparatus shown is for the user plane functional network element in the core network to perform... Figure 2 The test method for user plane functional network elements in the core network shown is therefore... Figure 2 The explanations and instructions in the test methods for user plane functional network elements in the core network also apply to the test equipment for user plane functional network elements in the core network, and will not be repeated here.

[0115] It should be noted that the modules in the test device for the user plane functional network elements in the core network mentioned above can be program modules (e.g., a set of program instructions to implement a specific function) or hardware modules. For the latter, they can be in the following forms, but are not limited to these: each of the above modules is in the form of a processor, or the functions of each of the above modules are implemented by a processor.

[0116] This application also provides a non-volatile storage medium, which includes a stored program, wherein, when the program is running, it controls the device where the non-volatile storage medium is located to execute the test method of the user plane function network element in the core network of any of the above embodiments.

[0117] This application also provides an electronic device, which includes a processor for running a program, wherein the program executes a test method for user plane functional network elements in the core network of any of the above embodiments.

[0118] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements a testing method for user plane functional network elements in the core network of any of the above embodiments.

[0119] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0120] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0121] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0122] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0123] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0124] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for testing a user plane function network element in a core network, characterized in that, The method comprises the following steps: determining a plurality of target network elements directly interacting with the user plane function network element, and simulating the plurality of target network elements through a test instrument to obtain a plurality of simulated network elements; controlling the plurality of simulated network elements to test the user plane function network element according to a plurality of different types of test forms through the test instrument to obtain test results, wherein the plurality of different types of test forms are used for testing requirements of different levels of the user plane function network element, and the test of the user plane function network element is performed through a plurality of test cases.

2. The method of claim 1, wherein, controlling the plurality of simulated network elements to test the user plane function network element according to a plurality of different types of test forms through the test instrument, comprising: determining a test requirement type and a target test form corresponding to the test requirement type; controlling the simulated network element corresponding to the test requirement type through the test instrument to determine all test cases required for testing the user plane function network element according to the target test form and the number of copies required for each test case, and creating test case copies corresponding to the number of copies, and testing the user plane function network element by executing the test case copies.

3. The method of claim 2, wherein, The determination of the test requirement type and the target test form corresponding to the test requirement type comprises: in the case that the test requirement type is to verify the functional integrity of the user plane function network element, determining that the target test form corresponding to the test requirement type is an automated test form; in the case that the test requirement type is to verify the ability of the user plane function network element to process high-concurrency user sessions, determining that the target test form corresponding to the test requirement type is a multi-session test form; and in the case that the test requirement type is to verify the performance of the user plane function network element, determining that the target test form corresponding to the test requirement type is a performance test form.

4. The method of claim 1, wherein, Each test case comprises a plurality of steps, and the plurality of steps are executed in series, and each step is an event, which is the smallest unit of a test case and is used for simulating the interaction between a network element and the user plane function network element.

5. The method of claim 4, wherein, The type of the event includes at least one of a packet forwarding control protocol control plane message event, a user datagram protocol / general packet radio service tunnel protocol data plane message event, an operation type event, and a characteristic event, wherein the packet forwarding control protocol control plane message event is used to simulate a process of interaction between a session management function network element and the user plane function network element based on a packet forwarding control protocol, the user datagram protocol / general packet radio service tunnel protocol data plane message event is used to simulate uplink and downlink of user traffic, and opening and closing of data plane messages, and verify data processing capability of the user plane function network element, the operation type event is used to perform an operation in a preset form on the user plane function network element or a server where the user plane function network element is located, and the operation includes at least one of querying a state of the user plane function network element, modifying configuration information of the user plane function network element, installing, upgrading and uninstalling the user plane function network element, and the characteristic event is an event set in a preset test scenario to meet a preset test requirement, and is used to test abnormal processing capability of the user plane function network element.

6. The method of claim 5, wherein, The test form and the test case are stored in a form of a test case directory tree, wherein the test case directory tree includes a first directory, the first directory includes a test case file and a plurality of different types of test form files used to store test forms, and the test case file includes a plurality of second directories, wherein the plurality of second directories include a first type of directory and a second type of directory, each of the second type of directory is used to store a plurality of test cases belonging to one type of event, and the first type of directory is used to store all test cases required by a complete test process under one type of test requirement and a number of test case copies, wherein the first type of directory references the second type of directory, and the plurality of different types of test form files reference the first type of directory.

7. The method of claim 1, wherein, The method further includes: collecting an abnormal message segment containing a target fault process, and generating a packet capture message file according to the abnormal message segment; analyzing network fault communication data in the packet capture message file by a target script, and constructing a new test case according to the network fault communication data.

8. The method of claim 1, wherein, The method further includes: during execution of the test case, a test result of each test case is integrated into a test report, wherein the test report includes a pass rate of the test case in each test form, and execution of each test case.

9. A test apparatus for a user plane function network element in a core network, the test apparatus comprising: The method further includes: a determining module configured to determine a plurality of target network elements directly interacting with the user plane function network element, and simulate the plurality of target network elements by a test instrument to obtain a plurality of simulated network elements; The test module is configured to control the multiple analog network elements to test the UPF network element according to multiple different types of test forms, and obtain test results.

10. A non-volatile storage medium, comprising: The non-volatile storage medium stores a program, and when the program is executed, the device in which the non-volatile storage medium is located performs the test method of the UPF network element in the core network.

11. An electronic device, comprising: Comprise: The memory and the processor are configured to run the program stored in the memory, and when the program is executed, the test method of the UPF network element in the core network is executed.

12. A computer program product comprising computer instructions, characterized in that, The computer instructions are executed by the processor to implement the test method of the UPF network element in the core network.

Images