Method and apparatus for testing core network service, and communication device

Abstract

Provided in the embodiments of the present application are a method and apparatus for testing a core network service, and a communication device. The method can be applied to a terminal, and comprises: acquiring a test task, wherein the test task is used for testing a core network service on the basis of the terminal; and when it is determined that a test trigger condition is met, executing the test task.

Description

Core network service testing method, device and communication equipment Technical Field

[0001] The present application relates to service testing technology in the communications field, and in particular to a testing method, device and communication equipment for core network services. Background Art

[0002] Core network products often use converged networking, meaning a single core network provides 2G, 3G, 4G, and 5G services simultaneously. Whenever maintenance personnel modify network configurations, expand capacity, or upgrade, they must perform core network service testing to verify the success of these operations.

[0003] Among the related technologies of remote testing, core network service testing is mainly performed using third-party remote software. That is, the terminal installed with the third-party remote software is deployed in the test area and connected to the remote software server via the Internet; then the testers in the operation and maintenance center remotely log in through the third-party remote software; the testers perform core network service testing through remote operations, such as sending and receiving text messages, surfing the Internet, etc.

[0004] However, third-party remote software only provides a remote access method. After remote access, starting the test task still requires testers to perform it manually, which reduces the test efficiency.

[0005] Summary of the Invention

[0006] The purpose of the embodiments of the present application is to provide a method, apparatus and communication equipment for testing core network services, which can solve the problem of low efficiency in core network service testing.

[0007] In a first aspect, an embodiment of the present application provides a method for testing core network services, which is applied to a terminal, including: obtaining a test task, wherein the test task is used to test the core network services based on the terminal; and executing the test task when it is determined that the test trigger conditions are met.

[0008] On the second aspect, an embodiment of the present application provides a method for testing core network services, which is applied to the server side, including: creating a test task, wherein the test task uses a terminal to test the core network service; wherein the test task includes a test trigger condition, and the test trigger condition is used for the terminal to automatically execute the test task.

[0009] On the third aspect, an embodiment of the present application provides a testing method for core network services, which is applied to core network equipment, including: determining the number of service requests and the number of service successes corresponding to the core network service, wherein the core network service is triggered by the terminal based on a test task; when it is determined that the number of service requests is equal to the number of service successes, determining that the test result of the core network service is a successful test; and outputting the test result.

[0010] In the fourth aspect, an embodiment of the present application provides a testing device for core network services, which is applied to a terminal and includes: an acquisition module for acquiring a test task, wherein the test task is used to test the core network service based on the terminal; and a task execution module for executing the test task when it is determined that the test trigger conditions are met.

[0011] In the fifth aspect, an embodiment of the present application provides a testing device for core network services, which is applied to the server side and includes: a task creation module for creating a test task, wherein the test task uses a terminal to test the core network service; wherein the test task includes a test trigger condition, and the test trigger condition is used for the terminal to automatically execute the test task.

[0012] In the sixth aspect, an embodiment of the present application provides a testing device for core network services, which is applied to core network equipment, including: a statistical module for determining the number of service requests and the number of service successes corresponding to the core network service, wherein the core network service is triggered by the terminal based on a test task; a determination module for determining that the test result of the core network service is a successful test when it is determined that the number of service requests is equal to the number of service successes; and an output module for outputting the test result.

[0013] In the seventh aspect, an embodiment of the present application provides a communication device, comprising: a memory, a processor, and computer-executable instructions stored on the memory and executable on the processor, wherein the computer-executable instructions, when executed by the processor, implement the steps of executing the method described in the first aspect, the second aspect, or the third aspect.

[0014] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store computer-executable instructions. When the computer-executable instructions are executed by a processor, the steps of the method described in the first aspect, the second aspect or the third aspect are implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0016] FIG1 is a schematic diagram showing a flow chart of a method for testing a core network service according to an embodiment of the present application;

[0017] FIG2 shows a flow chart of a method for testing a core network service according to an embodiment of the present application;

[0018] FIG3 shows a flow chart of a method for testing a core network service according to an embodiment of the present application;

[0019] FIG4 shows a schematic diagram of an application environment of a core network service testing method of the prior art;

[0020] FIG5 is a schematic diagram showing an application environment of a method for testing core network services provided in an embodiment of the present application;

[0021] FIG6 shows a schematic diagram of a test network environment involved in a core network service testing method provided in an embodiment of the present application;

[0022] FIG7 is a schematic diagram showing a terminal enabling a periodic synchronization function of a test task in a method for testing a core network service according to an embodiment of the present application;

[0023] FIG8 is a schematic diagram showing a terminal entering an automatic test mode in a method for testing a core network service according to an embodiment of the present application;

[0024] FIG9 shows a schematic diagram of a service process statistics task based on a single test user created by a core network MME network manager according to an embodiment of the present application;

[0025] FIG10 shows a schematic diagram of a service process statistics workflow of a core network MME network management based on a single test user according to an embodiment of the present application;

[0026] FIG11 is a schematic diagram showing a test task with an automatic execution tag and a number of repetitions created by a server in an embodiment of the present application;

[0027] FIG12 shows a flowchart of the automatic synchronization and automatic execution of test tasks according to an embodiment of the present application;

[0028] FIG13 shows a schematic diagram of determining the core network MME network management test results according to an embodiment of the present application;

[0029] FIG14 shows a schematic structural diagram of a testing device for core network services provided in an embodiment of the present application;

[0030] FIG15 is a schematic structural diagram of a testing device for core network services provided in an embodiment of the present application;

[0031] FIG16 shows a schematic structural diagram of a testing device for core network services provided in an embodiment of the present application;

[0032] Figure 17 is a schematic diagram of the hardware structure of a communication device that executes the testing method for core network services provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0034] Figure 1 shows a flow chart of a method for testing a core network service provided by an embodiment of the present application. The method can be executed by a terminal, in other words, the method can be executed by software or hardware installed in the terminal. As shown in Figure 1, the method can include the following steps.

[0035] S102: Acquire a test task, where the test task is used to test a core network service based on the terminal.

[0036] The terminal in this step may also be referred to as a test terminal, and the terminal may be deployed within the service range of the core network to be tested.

[0037] In this step, the terminal can obtain the test task from the server, and the server can be used to create the test task, set the test trigger conditions, etc.

[0038] The test tasks in this embodiment are used to test core network services based on terminals. Different test tasks may be used for different access modes. In a specific example, the test tasks are shown in Table 1 below:

[0039] Table 1 Test task examples under different access modes

[0040] S104: When it is determined that the test triggering condition is met, the test task is executed.

[0041] The test trigger condition in this step can be carried by the test task, and the test trigger condition can be set by the server.

[0042] Optionally, the determining whether the test trigger condition is satisfied includes at least one of the following: 1) determining that the test task carries an automatic execution tag; 2) determining that the remaining number of repeated executions of the test task is greater than zero.

[0043] This embodiment can realize the automatic running of the test task. For example, after the terminal client downloads the test task, it determines the automatic execution tag and the remaining number of repeated executions. If the test task carries the automatic execution tag and the remaining number of repeated executions of the test task is greater than zero, the script file in the test task is automatically executed to trigger the core network service test.

[0044] In this step, the terminal performs a test task. For example, for a 5G test task, the terminal performs a registration task or an Internet browsing task, etc. Whether the test task is executed successfully or failed can be determined by the core network device.

[0045] In the core network service testing method provided in the embodiments of the present application, a terminal acquires a test task for testing the core network service based on the terminal and executes the test task upon determining that a test trigger condition has been met. Because the terminal can automatically acquire and execute the test task, no on-site intervention by a tester is required. This method is suitable for remote automated service testing and is more efficient and intelligent.

[0046] The testing method for core network services provided in the embodiment of the present application only requires deploying the test terminal at a test location that meets physical security requirements (such as a customer area business hall) to achieve remote automated testing of core network services in a specified area, without the need to send test personnel to the site for testing, thus saving manpower.

[0047] Related art methods for third-party remote software testing also suffer from limitations on test items. For example, when a terminal performs testing tasks such as turning on airplane mode or reactivating a session, it may lose network connectivity, leading to remote testing being interrupted and unable to resume. The present embodiment avoids this issue by removing test item limitations.

[0048] The core network service testing method provided in the embodiments of the present application can realize automation and remote testing of core network service, that is, realize remote automated testing of core network service, and can meet the service testing requirements of the following scenarios:

[0049] 1) For service testing in a core network multi-pool networking scenario, please refer to the detailed implementation description below.

[0050] 2) Testing in remote areas: For example, in a scenario with wide coverage on an island, a terminal with a test application (iTest APP) can be deployed and installed on a designated island. When the mobile network is configured and adjusted, the method provided in the embodiment of this application can be used to verify the operation results without arranging a test engineer to arrive on site for test verification.

[0051] 3) VIP site assurance: By deploying terminals with the iTest app installed in the VIP site coverage area, periodic core network service automatic testing is performed (for example, attach, SMS sending and receiving, VoLTE service calling and receiving, etc., performed every 5 minutes). The service status of the site can be observed in real time through the network management single-user performance statistics of the core network equipment, eliminating the need to arrange test engineers to perform service testing assurance on-site.

[0052] Optionally, the terminal obtaining the test task mentioned in each of the above embodiments may include: the terminal obtaining the test task from the server based on periodic task synchronization. In this embodiment, the terminal can automatically obtain and execute the test task without the need for on-site intervention by the tester, making the testing method more efficient and intelligent.

[0053] Optionally, obtaining the test task from the server includes: obtaining the test task from the server when a new test task is found, the test task carries an automatic execution tag, and the number of repeated executions of the test task is greater than zero.

[0054] In this embodiment, the server can create a test task (including a test script) with an auto-execution tag and set the number of repetitions for the test task. The terminal acts as the iTest app client and the server acts as the iTest app server. The terminal iTest app executes periodic test task synchronization. If a new test task is found with an auto-execution tag and a repetition count greater than zero, the test task is downloaded from the server.

[0055] Optionally, after the terminal executes the test task, the method further includes: the terminal updating the remaining number of repetitions of the test task to the server. In this embodiment, the server may also update the remaining number of repetitions of the test task.

[0056] Optionally, the execution of the test task mentioned in each embodiment of the present application includes: sending a service request message corresponding to the test task to the core network device; receiving a service response message sent by the core network device, and the service response message is used to indicate the success or failure of the core network service execution.

[0057] The above describes in detail the method for testing core network services according to an embodiment of the present application in conjunction with Figure 1. The following describes in detail the method for testing core network services according to another embodiment of the present application in conjunction with Figure 2. It will be understood that the interaction between the server and the terminal described from the server side is the same as or corresponds to the description of the terminal side in the method shown in Figure 1. To avoid repetition, the relevant description is appropriately omitted.

[0058] FIG2 is a flow chart of a method for testing a core network service according to an embodiment of the present invention, which can be applied on a server side. As shown in FIG2 , the method 200 includes the following steps.

[0059] S202: Create a test task, where the test task uses a terminal to test a core network service; wherein the test task includes a test trigger condition, where the test trigger condition is used for the terminal to automatically execute the test task.

[0060] In the core network service testing method provided by the embodiments of the present application, a server creates a test task that uses a terminal to test the core network service. The test task includes a test trigger condition that causes the terminal to automatically execute the test task. This allows the terminal to automatically execute the test task without the need for on-site tester intervention, making it suitable for remote automated service testing and more efficient and intelligent.

[0061] Optionally, the test triggering condition includes at least one of the following: 1) the test task carries an automatic execution tag; 2) the remaining number of repeated executions of the test task is greater than zero.

[0062] Optionally, the method further comprises: upon receiving a periodic task synchronization request from the terminal, sending the test task to the terminal. In this embodiment, the terminal can automatically obtain and execute the test task without the need for on-site intervention by a tester, making the testing method more efficient and intelligent.

[0063] In this embodiment, the server can create a test task (including a test script) with an auto-execution tag and set the number of test task repetitions. The terminal acts as the iTest app client and the server acts as the iTest app server. The terminal iTest app executes periodic test task synchronization. If a new test task is found with an auto-execution tag and a repetition count greater than zero, the test task is downloaded from the server.

[0064] Figure 3 is a schematic diagram of a core network service testing method according to an embodiment of the present application, which can be applied to core network devices. It should be understood that the interaction between the core network device and the terminal described from the core network device perspective is identical or corresponding to the terminal-side description of the method shown in Figure 1 . To avoid repetition, the relevant description is omitted. As shown in Figure 3 , method 300 includes the following steps.

[0065] S302: Determine the number of service requests and the number of service successes corresponding to a core network service, where the core network service is triggered by the terminal based on a test task.

[0066] In this embodiment, the number of service requests can be the number of service requests by the same terminal (or user) for the same core network service. Similarly, the number of service successes in this embodiment can be the number of service successes by the same terminal for the same core network service. For core network devices, different terminals can be distinguished by different International Mobile Subscriber Identity (IMSI).

[0067] The core network service corresponds to the test tasks in the previous embodiments, and can be referred to the test tasks in Table 1, for example, including EPC attachment, CSFB calling and receiving, VoLTE active and standby calling, etc.

[0068] S304: When it is determined that the number of service requests is equal to the number of service successes, the test result of the core network service is determined to be a test success.

[0069] For example, for the EPC attach process of the same terminal (eg, IMSI=502181163998814), the number of service requests is 3 and the number of service successes is also 3, then the test result of the EPC attach process is determined to be a success.

[0070] In other embodiments, when it is determined that the number of service requests is not equal to (such as greater than) the number of service successes, the test result of the core network service is determined to be a test failure.

[0071] S306: Output the test result.

[0072] The core network service testing method provided in the embodiment of the present application is suitable for remote automated service testing, and can realize remote automated testing of core network services with high efficiency.

[0073] The core network service testing method provided in the embodiment of the present application has the test results automatically determined by the core network equipment, does not require uploading signaling to the server, does not involve cross-border transfer of personal data, and is easy to promote internationally.

[0074] Optionally, before determining the number of service requests and the number of service successes corresponding to the core network service, the method further includes: starting a service process statistics task related to the terminal, and the service process statistics task is used to determine the number of service requests and the number of service successes.

[0075] Optionally, the starting the service process statistics task related to the terminal includes: starting the service process statistics task related to the International Mobile Subscriber Identity (IMSI) of the terminal based on the IMSI.

[0076] In this embodiment, the core network device provides a service process statistics task based on a single test terminal (15-digit IMSI), counting the number of service requests and the number of service successes, respectively, and accumulating them into different counters. If the value of the service success counter is equal to the service request counter, the test result is determined to be successful.

[0077] To illustrate in detail the testing method for the core network service provided in the embodiment of the present application, the following will be described in combination with specific application scenarios and specific embodiments.

[0078] Some operators, due to substandard intercity link transmission quality, are unable to establish a network-wide pool and are forced to divide the network into two or more pools. In this networking scenario, as shown in Figure 4, if the maintenance team in Pool 1's coverage area needs to modify, expand, or upgrade the core network elements in Pool 2, they must dispatch test engineers to Pool 2's wireless area to complete service testing, which is inefficient.

[0079] In order to solve the above problems, the technical solution provided in the embodiment of the present application only requires deploying a terminal with the iTest APP software installed in the Pool2 wireless coverage area to realize remote automated service testing of the core network service, as shown in Figure 5.

[0080] The technical solution provided by the embodiment of the present application can save one tester each time Pool2 network operation and maintenance is performed.

[0081] As shown in Figure 6, the testing method for the core network service provided in the embodiment of the present application is briefly described as follows: ① The iTest server creates a test task with an automatic test label and the remaining number of repeated executions; ② The test terminal obtains new test tasks through periodic task synchronization, and automatically executes the test script in the test task package to trigger the test service; ③ The tester judges the test results by viewing the single-user performance statistics function provided by the core network equipment.

[0082] The technical solution adopted in the embodiment of the present application includes the following steps:

[0083] Step 1: Deploy the test terminal (including SIM card) in a test area that is physically secure and has access to a power source. To prevent battery overheating caused by prolonged charging of the terminal (e.g., a mobile phone), connect the terminal to a power source via a timer-equipped outlet. Charge the terminal twice daily, between 00:00 and 06:00 and again between 12:00 and 18:00.

[0084] Step 2: Launch the iTest test app on the test terminal, log in using the tester's account, connect to the server, and enable the periodic test task synchronization function.

[0085] Step 3: After the tester clicks "Start", it will automatically jump to the automatic execution interface, as shown in Figure 7 and Figure 8.

[0086] Step 4: The core network MME creates a service process statistics task for a single user (15-digit IMSI number), as shown in Figure 9.

[0087] The MME initiates service flow statistics based on a single IMSI, as shown in Figure 10. Specifically, the MME initiates service flow statistics based on a single IMSI, for example, the attach procedure for IMSI = 502181163998814. ① The MME receives an Attach Request. If the IMSI matches successfully, the counter "C465420027: Times of Combined Attach Request" increments by one for the measurement object IMSI = 502181163998814. The MME sends an Attach Accept. If the IMSI matches successfully, the counter "C465420028: Times of success for Combined Attach procedure" increments by one for the measurement object IMSI = 502181163998814.

[0088] Step 5: The tester logs in to the iTest APP server using the same account, creates a test task with the Auto-execution tag, and sets the remaining number of repetitions, as shown in Figure 11.

[0089] Step 6: The test APP client obtains the test task, selects the test task with a pending execution count greater than 0, and automatically starts the test task to trigger service tests such as EPC attachment, CSFB calling and receiving, and VoLTE active and standby calling. After the test is completed, the pending execution count of the task is updated to the server (the pending execution count minus one). The detailed process is shown in Figure 12.

[0090] Step 7: The tester queries the core network single-user performance statistics, as shown in Figure 13. When the number of service requests equals the number of service successes, the test is considered successful.

[0091] For example, for the 4G attachment process, the test success rate = 100*C465420028: Times of success for Combined Attach procedure / C465420027: Times of Combined Attach Request. That is, when C465420028: Times of success for Combined Attach procedure is equal to C465420027: Times of Combined Attach Request, the attachment process test success rate of the test user IMSI = 502181163998814 is 100%.

[0092] It should be noted that steps 1, 2, and 3 only need to be performed when the test terminal is deployed for the first time; after the test terminal is deployed, remote service testing only needs to perform steps 4 to 7.

[0093] The embodiments of the present application implement automated and remote testing of core network services. The key invention points are as follows:

[0094] 1) Automatic download of test tasks

[0095] The server creates a test task (including a test script) with an automatic execution tag and sets the number of repetitions for the test task.

[0096] The test terminal acts as the iTest app client, and the test server acts as the iTest app server. The iTest app on the test terminal executes periodic test task synchronization. If a new test task is found with the automatic execution tag and a repeat test count greater than 0, the test task package is downloaded.

[0097] 2) Test tasks run automatically

[0098] After the test terminal downloads the test task package as the iTest APP client, it determines the automatic execution tag and the remaining number of repetitions. If the conditions are met, it automatically executes the script in the test task package to trigger the core network service test.

[0099] 3) Automatic judgment of test results

[0100] The core network management system provides performance statistics for a single test user (15-digit IMSI). This task counts service requests and service successes, accumulating them into separate counters. If the service success counter equals the service request counter, the test is considered successful.

[0101] Core network service testing is automated through automatic downloading and execution of test tasks, as well as automated evaluation of test results. The core network management system's single-user performance statistics function allows for localized evaluation of test results, preventing the cross-border transfer of personal data. These technologies enable remote testing of core network services, saving network maintenance manpower and reducing network maintenance costs.

[0102] FIG14 shows a schematic structural diagram of a core network service testing device 1400 provided in an embodiment of the present application. The device 1400 is applied to a terminal and includes the following modules.

[0103] The acquisition module 1402 is used to acquire a test task, where the test task is used to test a core network service based on the terminal.

[0104] The task execution module 1404 is configured to execute the test task if it is determined that the test triggering condition is met.

[0105] In this embodiment of the present application, a terminal acquires a test task, which is used to test core network services based on the terminal. Upon determining that a test trigger condition is met, the test task is executed. Because the terminal can automatically acquire and execute test tasks, no on-site intervention by a tester is required. This makes the test method suitable for remote automated service testing more efficient and intelligent.

[0106] Optionally, as an embodiment, the satisfying of the test triggering condition includes at least one of the following: the test task carries an automatic execution tag; the remaining number of repeated executions of the test task is greater than zero.

[0107] Optionally, as an embodiment, the acquisition module 1402 is configured to acquire the test task from the server based on a periodic task synchronization method.

[0108] Optionally, as an embodiment, the acquisition module 1402 is configured to acquire a new test task from a server when a new test task is discovered, the test task carries an automatic execution tag, and the number of repeated executions of the test task is greater than zero.

[0109] Optionally, as an embodiment, the task execution module 1404 is further configured to update the remaining number of repetitions of the test task to the server.

[0110] Optionally, as an embodiment, the task execution module 1404 is used to send a service request message corresponding to the test task to the core network device; receive a service response message sent by the core network device, and the service response message is used to indicate whether the core network service is executed successfully or failed.

[0111] The device 1400 provided in the embodiment of the present application can execute the various methods described in the terminal-side method embodiment above, and realize the functions and beneficial effects of the various methods described in the method embodiment above, which will not be repeated here.

[0112] FIG15 shows a schematic structural diagram of a core network service testing device 1500 provided in an embodiment of the present application. The device 1500 is applied to a server and includes the following modules.

[0113] The task creation module 1502 is used to create a test task, where the test task uses a terminal to test a core network service; wherein the test task includes a test trigger condition, where the test trigger condition is used for the terminal to automatically execute the test task.

[0114] Optionally, the device 1500 further includes a communication module.

[0115] In this embodiment of the application, a server creates a test task that uses a terminal to test core network services. The test task includes a test trigger condition that causes the terminal to automatically execute the test task. This allows the terminal to automatically execute the test task without the need for on-site tester intervention, making it suitable for remote automated service testing and providing a more efficient and intelligent testing method.

[0116] Optionally, as an embodiment, the test triggering condition includes at least one of the following: the test task carries an automatic execution tag; the remaining number of repeated executions of the test task is greater than zero.

[0117] Optionally, as an embodiment, the apparatus 1500 further includes a communication module, configured to send the test task to the terminal upon receiving a periodic task synchronization request from the terminal.

[0118] The device 1500 provided in the embodiment of the present application can execute the various methods described in the above server-side method embodiments and realize the functions and beneficial effects of the various methods described in the above method embodiments, which will not be repeated here.

[0119] FIG16 shows a schematic structural diagram of a core network service testing device 1600 provided in an embodiment of the present application. The device 1600 is applied to a core network device and includes the following modules.

[0120] The statistics module 1602 is used to determine the number of service requests and the number of service successes corresponding to the core network service, where the core network service is triggered by the terminal based on the test task.

[0121] The determination module 1604 is configured to determine that the test result of the core network service is a test success when it is determined that the number of service requests is equal to the number of service successes.

[0122] The output module 1606 is configured to output the test result.

[0123] This embodiment of the application is suitable for remote automated service testing and can achieve remote automated testing of core network services with high efficiency. In this embodiment of the application, the test results are automatically determined by the core network equipment, without uploading signaling to the server, and without involving cross-border transfer of personal data, which is easy to promote internationally.

[0124] Optionally, as an embodiment, the apparatus 1600 further includes a starting module for starting a business process statistics task related to the terminal, wherein the business process statistics task is used to determine the number of business requests and the number of business successes.

[0125] Optionally, as an embodiment, the starting module is used to start a service process statistics task related to the IMSI based on the IMSI of the terminal.

[0126] The device 1600 provided in the embodiment of the present application can execute the various methods described in the above core network device side method embodiment, and realize the functions and beneficial effects of the various methods described in the above method embodiment, which will not be repeated here.

[0127] FIG17 shows a schematic diagram of the hardware structure of a communication device provided by an embodiment of the present application. Referring to the figure, at the hardware level, the communication device includes a processor, and optionally, an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the communication device may also include hardware required for other services.

[0128] The processor, network interface, and memory can be interconnected via an internal bus, such as an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. These buses can be classified as address buses, data buses, and control buses. For ease of illustration, the figure uses only one bidirectional arrow, but this does not imply that there is only one bus or only one type of bus.

[0129] The memory is used to store programs. Specifically, the program may include program code, which includes computer operating instructions. The memory may include internal memory and non-volatile memory, and provides instructions and data to the processor.

[0130] The processor reads the corresponding computer program from the non-volatile memory into the internal memory and then runs it, logically forming a device for locating the target user. The processor executes the program stored in the memory and is specifically configured to perform the methods disclosed in the embodiments shown in Figures 1-13 and to achieve the functions and benefits of the various methods described in the preceding method embodiments, which will not be further described here.

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

[0132] The communication device can also execute the methods described in the above method embodiments and realize the functions and beneficial effects of the methods described in the above method embodiments, which will not be repeated here.

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

[0134] An embodiment of the present application also proposes a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by a communication device including multiple application programs, the communication device executes the method disclosed in the embodiments shown in Figures 1-13 and realizes the functions and beneficial effects of the various methods described in the previous method embodiments, which will not be repeated here.

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

[0136] Furthermore, an embodiment of the present application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the following process is implemented: the method disclosed in the embodiment shown in Figures 1-13 and the functions and beneficial effects of each method described in the previous method embodiment are implemented, which will not be repeated here.

[0137] In short, the above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

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

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

[0140] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0141] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

Claims

1. A core network service testing method, applied to a terminal, comprising: Acquire a test task, where the test task is used to test a core network service based on the terminal; When it is determined that the test triggering condition is met, the test task is executed.

2. The method according to claim 1, wherein: Determining that the test trigger condition is satisfied includes at least one of the following: Determining that the test task carries an automatic execution tag; Determine whether the remaining number of repetitions of the test task is greater than zero.

3. The method according to claim 1 or 2, wherein: The acquisition test task includes: Based on the periodic task synchronization method, the test task is obtained from the server.

4. The method according to claim 3, wherein: The obtaining of the test task from the server includes: When a new test task is found, and the test task carries an automatic execution tag and the number of repeated executions of the test task is greater than zero, the test task is obtained from the server.

5. The method according to claim 4, wherein: After executing the test task, the method further includes: The remaining number of repetitions of the test task is updated to the server.

6. The method according to any one of claims 1 to 5, wherein: The performing of the test task comprises: Sending a service request message corresponding to the test task to the core network device; Receive a service response message sent by the core network device, where the service response message is used to indicate whether the core network service is executed successfully or failed.

7. A core network service testing method, applied to a server, comprising: Creating a test task, wherein the test task uses a terminal to test a core network service; The test task includes a test trigger condition, which is used to The terminal automatically executes the test task.

8. The method according to claim 7, wherein: The test triggering condition includes at least one of the following: The test task carries an automatic execution tag; The remaining number of repetitions of the test task is greater than zero.

9. The method according to claim 7 or 8, wherein: The method further comprises: In case of receiving the periodic task synchronization request of the terminal, sending the test task to the terminal.

10. A method for testing a core network service, applied to a core network device, comprising: Determine the number of service requests and the number of service successes corresponding to a core network service, wherein the core network service is triggered by the terminal based on the test task; In the case where it is determined that the number of service requests is equal to the number of service successes, determining that the test result of the core network service is a test success; The test result is output.

11. The method according to claim 10, wherein: Before determining the number of service requests and the number of service successes corresponding to the core network service, the method further includes: A business process statistics task related to the terminal is started, where the business process statistics task is used to determine the number of business requests and the number of business successes.

12. The method according to claim 11, wherein: The starting of the business process statistics task related to the terminal includes: Based on the international mobile subscriber identity IMSI of the terminal, a service process statistics task related to the IMSI is started.

13. A core network service testing device, applied to a terminal, comprising: An acquisition module, used for acquiring a test task, where the test task is used for testing a core network service based on the terminal; The task execution module is used to execute the task when the test trigger condition is met. Test task.

14. A core network service testing device, applied to a server, comprising: A task creation module, used to create a test task, wherein the test task uses a terminal to test a core network service; The test task includes a test trigger condition, and the test trigger condition is used for the terminal to automatically execute the test task.

15. A core network service testing device, applied to a core network device, comprising: A statistics module, used to determine the number of service requests and the number of service successes corresponding to a core network service, wherein the core network service is triggered by the terminal based on the test task; A determination module, configured to determine that the test result of the core network service is a test success when it is determined that the number of service requests is equal to the number of service successes; An output module is used to output the test result.

16. A communication device comprising: processor; as well as A memory arranged to store computer executable instructions which, when executed, cause the processor to perform the steps of the method of any one of claims 1 to 12.

17. A computer-readable medium storing one or more programs, which, when executed by a communication device including a plurality of application programs, cause the communication device to perform the steps of the method according to any one of claims 1 to 12.

Images