Monitoring method and device for terminal testing equipment and electronic equipment

Abstract

The present disclosure provides a terminal test equipment monitoring method and device and electronic equipment, wherein the monitoring method comprises: detecting remote network availability of a terminal test equipment and a remote control terminal; performing first heartbeat monitoring on a hardware physical link of the terminal test equipment through a monitoring system; performing first alarm and / or restart on the terminal test equipment through an MCU central control system according to first feedback information of the first heartbeat monitoring; performing second heartbeat monitoring on a process link of the terminal test equipment through the monitoring system; and performing second alarm and / or restart on the terminal test equipment through the MCU central control system according to second feedback information of the second heartbeat monitoring. Through the above monitoring method, real-time network, application running and various types of system and performance logs can be provided for off-site testing and walk-through of the remote terminal test equipment, and problems can be quickly solved by timely processing when the remote terminal test equipment has problems.

Description

Technical Field

[0001] This disclosure relates to the field of monitoring, and in particular to a monitoring method, apparatus and electronic equipment for a terminal testing device. Background Technology

[0002] Typically, when mobile phones or other terminals malfunction and require testing, it can be inconvenient if the testing equipment is located in a different area. Furthermore, general remote terminal testing equipment often lacks real-time capabilities and cannot resolve issues such as system crashes or network connectivity problems on the device itself.

[0003] In the testing of international products, due to significant differences between overseas and domestic usage environments, factors such as network standards, network quality, carriers, device models, and regions must be considered, making it difficult to comprehensively cover the overseas user experience using domestic testing methods. The typical testing process for mobile apps on terminal devices includes manual testing, automated testing, performance testing, and online business walkthroughs. For testing related to specialized applications, to ensure effectiveness, it is usually necessary for relevant personnel to travel to the site for on-site testing or to hire local technical personnel for testing. Both of these testing methods typically involve higher labor costs, and the real-time detection and localization of problems are also relatively poor. Summary of the Invention

[0004] This summary section is provided to briefly introduce the concepts, which will be described in detail in the detailed description section below. This summary section is not intended to identify key or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] To address the aforementioned technical problems and improve the accuracy and effectiveness of remote terminal testing equipment, the present disclosure proposes the following technical solutions.

[0006] In a first aspect, embodiments of this disclosure provide a monitoring method for a terminal testing device, wherein the terminal testing device uses an MCU central control system as the monitoring core, and the monitoring system monitors the terminal testing device. The monitoring method includes:

[0007] The remote network availability between the terminal testing device and the remote control terminal is detected;

[0008] The monitoring system performs first heartbeat monitoring on the hardware physical link of the terminal test equipment.

[0009] Based on the first feedback information from the first heartbeat monitoring, the terminal testing device is triggered by the MCU central control system to issue a first alarm and / or restart.

[0010] The monitoring system performs second heartbeat monitoring on the process link of the terminal test device.

[0011] Based on the second feedback information from the second heartbeat monitoring, the terminal test device is triggered by the MCU central control system to issue a second alarm and / or restart.

[0012] Furthermore, the detection of the remote network availability between the terminal testing device and the remote control terminal includes:

[0013] The availability of the remote network of the terminal test device is detected by the ping command;

[0014] If unavailable, restart the remote network of the terminal test device.

[0015] Furthermore, the step of monitoring the hardware physical link of the terminal test device through the monitoring system to perform the first heartbeat monitoring includes:

[0016] Perform network heartbeat monitoring on the interfaces between the network module and other modules in the physical hardware link; and

[0017] Serial heartbeat communication is performed between the various modules in the hardware physical link.

[0018] Furthermore, the step of triggering a first alarm and / or restarting the terminal testing device via the MCU central control system based on the first feedback information from the first heartbeat monitoring includes:

[0019] If the first feedback information is not received within a first fixed time, or if the first feedback information is empty, then a first alarm signal is issued.

[0020] If the duration of the first alarm signal reaches the first time threshold, the remote terminal testing device will be restarted.

[0021] Furthermore, the second heartbeat monitoring of the process link of the terminal test device through the monitoring system includes:

[0022] A second heartbeat is sent to each of the service processes, and the service processes reply with the second feedback information based on the second heartbeat.

[0023] Furthermore, the step of triggering a second alarm and / or restarting the terminal test device via the MCU central control system based on the second feedback information from the second heartbeat monitoring includes:

[0024] Heartbeats are sent to each of the service processes via socket interface commands at a second fixed time interval;

[0025] If the second feedback information is not received within the second fixed time period, or if the second feedback information is empty, a second alarm signal is issued.

[0026] When the duration of the second alarm signal reaches the second time threshold, the terminal testing device is restarted.

[0027] Furthermore, the method also includes:

[0028] Risk parameters on the terminal testing equipment are collected periodically;

[0029] Extract each risk value from the risk parameters;

[0030] Determine whether each of the risk values ​​exceeds the corresponding risk threshold;

[0031] If any of the aforementioned risk values ​​exceeds the corresponding risk threshold, an alarm signal will be issued or a restart will be initiated.

[0032] Furthermore, the risk parameters are the remote terminal's CPU utilization rate, memory utilization rate, CPU operating temperature, program running lag time, program running response time and / or network connection timeout time.

[0033] Furthermore, the method also includes:

[0034] Monitoring the interactive experience of remote terminals specifically includes:

[0035] The display interface of the remote terminal is displayed synchronously;

[0036] Task scheduling is performed on the applications of the remote terminal;

[0037] Logs of the modules in the system and the terminal itself in the remote terminal are collected, monitored, and reported.

[0038] Secondly, embodiments of this disclosure provide a monitoring device for a terminal testing device, wherein the terminal testing device uses an MCU central control system as the monitoring core, and the monitoring system monitors the terminal testing device. The monitoring device includes:

[0039] The detection module is used to detect the remote network availability between the terminal testing device and the remote control terminal;

[0040] The first monitoring module is used to perform first heartbeat monitoring on the hardware physical link of the terminal test device through the monitoring system.

[0041] The first processing module is used to trigger a first alarm and / or restart the terminal test device through the MCU central control system based on the first feedback information from the first heartbeat monitoring.

[0042] The second monitoring module is used to perform second heartbeat monitoring on the process link of the terminal test device through the monitoring system.

[0043] The second processing module is used to issue a second alarm and / or restart the terminal test device through the MCU central control system based on the second feedback information from the second heartbeat monitoring.

[0044] Furthermore, the device also includes:

[0045] The collection module is used to periodically collect risk parameters on the terminal test equipment;

[0046] The extraction module is used to extract each risk value from the risk parameters;

[0047] The judgment module is used to determine whether each risk value exceeds the corresponding risk threshold.

[0048] An alarm processing module is used to issue an alarm signal or perform system processing when any of the aforementioned risk values ​​exceeds the corresponding risk threshold. The system processing includes issuing an alarm signal and / or restarting the system.

[0049] Furthermore, the device also includes:

[0050] The experience monitoring module is used to monitor the interactive experience of remote terminals.

[0051] Furthermore, the device also includes:

[0052] A synchronization module is used to synchronize the display interface of the remote terminal.

[0053] The task scheduling module is used to schedule tasks for the applications on the remote terminal.

[0054] The remote monitoring module is used to collect, monitor, and report logs of the modules in the system of the remote terminal and the terminal itself.

[0055] Thirdly, embodiments of this disclosure provide an electronic device, including:

[0056] Memory, used to store computer-readable instructions; and

[0057] A processor for executing the computer-readable instructions, causing the electronic device to implement the method according to any one of the first aspects above.

[0058] Fourthly, embodiments of this disclosure provide a non-transitory computer-readable storage medium for storing computer-readable instructions that, when executed by a computer, cause the computer to implement the method described in any one of the first aspects above.

[0059] This disclosure provides a monitoring method for a terminal testing device. The terminal testing device uses an MCU central control system as its monitoring core. The monitoring system monitors the terminal testing device, and the monitoring method includes: detecting the remote network availability between the terminal testing device and a remote control terminal; performing a first heartbeat monitoring on the hardware physical link of the terminal testing device through the monitoring system; issuing a first alarm and / or restarting the terminal testing device through the MCU central control system based on the first feedback information from the first heartbeat monitoring; performing a second heartbeat monitoring on the process link of the terminal testing device through the monitoring system; and issuing a second alarm and / or restarting the terminal testing device through the MCU central control system based on the second feedback information from the second heartbeat monitoring. Through this monitoring method, real-time network and application operation logs, as well as various system and performance logs, can be provided for remote testing and inspection of remote terminal testing devices. It offers a low-cost, highly available, highly stable, and real-time product and solution, and allows for timely handling and rapid resolution of problems when they occur in the remote terminal testing device.

[0060] The above description is merely an overview of the technical solution disclosed herein. In order to better understand the technical means of this disclosure and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0061] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0062] Figure 1 A schematic flowchart of a monitoring method for a terminal testing device provided in an embodiment of this disclosure;

[0063] Figure 2 This is a schematic diagram of a mid-end upper-edge service system in a terminal testing device provided in an embodiment of this disclosure;

[0064] Figure 3 A schematic diagram of the hardware system and service monitoring system of a terminal testing device provided in an embodiment of this disclosure;

[0065] Figure 4 A schematic diagram of the monitoring device for a terminal testing equipment provided in another embodiment of this disclosure;

[0066] Figure 5 A schematic diagram of the structure of an electronic device provided in another embodiment of this disclosure. Detailed Implementation

[0067] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0068] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0069] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0070] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0071] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0072] Figure 1 This is a flowchart illustrating an embodiment of a monitoring method for a terminal testing device provided in this disclosure. The monitoring method can be executed by a monitoring device for the terminal testing device. This monitoring device can be implemented as software or as a combination of software and hardware. The monitoring device can be integrated into a specific device within the monitoring device, such as a terminal device. Figure 1 As shown, the method includes the following steps:

[0073] Step S101: Detect the remote network availability between the terminal testing device and the remote control terminal (hereinafter referred to as the control terminal).

[0074] In step S101, test data and monitoring video are transmitted over the network, allowing usability testing to move beyond the laboratory and into real-world user environments. This improves the authenticity of the test data and reduces time and space constraints. Remote network usability testing achieves distributed data storage and collection by transforming the test machine and the tested machine into a server and client architecture. Remote network usability testing requires the terminal test equipment to be set up according to the remote control terminal's format, collecting complete data and feeding it back to the remote control terminal, enabling simultaneous testing across multiple terminals. Remote network testing has two modes: synchronous and asynchronous. Synchronous mode means the tested terminal and the monitor are located in different geographical locations but maintain consistency in time, i.e., monitoring is real-time. Asynchronous mode means the tested terminal and the monitor are geographically and temporally dispersed, i.e., monitoring is not real-time.

[0075] In this embodiment, synchronous remote network testing is employed. External network availability is detected via a remote ping command. If unavailable, the OpenWRT network service is restarted. Specifically, network connectivity is determined by pinging Baidu's DNS server 8.8.8.8. If n consecutive (e.g., 5) ping attempts fail with a certain time interval (e.g., 10 seconds), a network fault is identified. After confirming the fault, the OpenWRT router is restarted. A subsequent restart using the network service restores connectivity. A log file is also included to record the fault, restart time, and number of restarts. Since the OpenWRT router's solid-state drive capacity is very small, typically only around 2MB, the log file size must be limited. Therefore, some unnecessary log entries have been commented out. The test script's execution interval should not be too short; otherwise, the network service will continuously restart without a network connection, making it impossible to log in and modify settings. For example, a 5-minute interval is sufficient for logging in, modifying settings, and stopping the script. This interval can be adjusted as needed. This test script automatically detects multiple faults and automatically restarts the terminal test device's network service, which is much more convenient than manual handling.

[0076] Step S102: Perform first heartbeat monitoring on the hardware physical link of the terminal test device.

[0077] In step S102, to ensure the reachability of each hardware unit within the system, a first heartbeat monitoring is performed on the hardware physical link of the terminal test device. This includes: performing network heartbeat monitoring on the interface between the network module and other modules in the hardware physical link; and performing serial port heartbeat communication between the modules in the hardware physical link. This embodiment uses the Socket interface as the primary communication method. The Socket interface is a long-lived connection by default. To determine whether the Client and Server connections are normal, both the ClientSocket and ServerSocket used in this embodiment have a heartbeat thread. This thread is mainly used to detect whether the Client and Server are connected normally. The normal connection between the Client and Server is primarily ensured using a ping-pang heartbeat monitoring process.

[0078] Specifically, in this embodiment, the MCU central control system uses the network (WIFI) module group and the industrial control computer in the system to perform network ping-pang heartbeat monitoring of remote terminals via an RJ45 interface. This ping-pang heartbeat monitoring is timer-based, and the parameters can be set to any value within the range of 0-255. Simultaneously, the WIFI module group and the MCU, as well as the MCU and the industrial control computer, communicate via UART using serial ping-pang heartbeat communication.

[0079] In this embodiment, heartbeat monitoring is used for communication monitoring of the terminal test equipment. The heartbeat packet is the data communication structure between the terminal test equipment and the remote control terminal to notify each other of their survival.

[0080] There are several reasons why heart rate packets are periodically sent to the control unit:

[0081] The control terminal is notified of the remote terminal test device's liveness status. If the control terminal detects that it has not received a heartbeat packet from the remote terminal test device for a certain period of time, it will release all resources previously allocated to this terminal, such as the socket connection. The IP mapping table of the remote network is refreshed periodically to prevent the Yancheng network router from removing the mapping table, which could cause the connection between the remote terminal test device and the control terminal to be interrupted.

[0082] A simple implementation involves periodically sending heartbeat packets to the control terminal. However, this raises the question of what the appropriate time interval should be. Due to different network topologies, remote networks are assigned to different network routes, and different network nodes have different strategies for handling mapping tables. If the remote network finds that an IP address in a mapping table has no uplink or downlink data for a certain period of time, it will remove that IP from the mapping table, causing the connection to be interrupted. For remote terminal testing devices using instant messaging, this means they cannot receive push notifications in a timely manner.

[0083] Another issue is that sending heartbeat packets at short intervals can lead to excessive power and data consumption on remote terminal testing devices, especially mobile devices. Based on these considerations, we will design an intelligent heartbeat mechanism that can automatically adjust the heartbeat sending interval according to different network conditions to solve the aforementioned problems.

[0084] The design of a smart heartbeat requires the control unit to support the receipt of a special type of heartbeat packet. This special heartbeat packet differs from a normal heartbeat in that the control unit does not need to receive a receipt for a normal heartbeat packet. This allows us to dynamically adjust the heartbeat period until the ideal heartbeat period is achieved.

[0085] The basic algorithm for Pingpang's heartbeat monitoring is as follows:

[0086] 1. Upon successful connection, the ping-pang heartbeat thread is started. The initial heartbeat period is the last adjusted heartbeat period. If this is the first time, the heartbeat period is set to the default period.

[0087] 2. Sending a ping-pang data packet to the server means that the client sends a heartbeat ping -> the server waits for the reply -> receiving the pang reply is considered a successful ping-pang;

[0088] 3. If ping-pang does not return within the specified time, send -> several more times;

[0089] 3.1 If step 2 is received repeatedly, repeat it several times ->;

[0090] 3.11 Success -> Increase heartbeat cycle -> Go to step 2;

[0091] Version 3.12 failed -> proceed to version 3.2;

[0092] 3.2 If it fails, reduce the heartbeat cycle -> go to step 2;

[0093] 4. Stop ping-pong until a suitable heartbeat packet equal to the last successful heartbeat cycle is found;

[0094] 5. Starting the ping heartbeat thread means that the server does not need to send a response, reducing server load.

[0095] Step S103: Based on the first feedback information from the first heartbeat monitoring, the terminal test device is given a first alarm and / or restarted through the MCU central control system.

[0096] In step S103, after the first heartbeat monitoring, the terminal test device needs to be processed based on the feedback information of the first heartbeat. Specifically, the terminal test device undergoes a first system processing based on the first feedback information from the first heartbeat monitoring. This first system processing includes a first alarm and / or restart. This step includes: if no first feedback information is received within a first fixed time period, or if the first feedback information is empty, a first alarm signal is issued; if the duration of the first alarm signal reaches a first time threshold, the remote terminal is restarted. The network (WIFI) module group and the industrial control computer in the system perform network ping-pang heartbeat monitoring via an RJ45 interface. Simultaneously, the WIFI module group and the MCU, and the MCU and the industrial control computer, perform serial port ping-pang heartbeat communication via UART. If the control terminal does not receive a heartbeat signal from the remote terminal testing device within a first fixed time period (e.g., 2 seconds, 5 seconds, 10 seconds, etc.), it will issue a first alarm signal, such as a breathing light (e.g., a red light) flashing rapidly. If the first alarm signal is not received after the duration reaches a first time threshold (e.g., 60 seconds, 100 seconds, 120 seconds, 200 seconds, 300 seconds, etc.), the system will be restarted. Here, the first time threshold is an integer multiple of the first fixed time period.

[0097] Step S104: Perform a second heartbeat monitoring on the process link of the terminal test device through the monitoring system.

[0098] In step S104, in this embodiment, in addition to performing a first heartbeat monitoring on the hardware link of the remote terminal testing device, it is also necessary to perform heartbeat monitoring on the process link of the remote terminal testing device to ensure the availability of the service processes, that is, to perform a second heartbeat monitoring on the process link of the remote terminal testing device. The second heartbeat monitoring on the process link of the remote terminal testing device includes: sending a second heartbeat to each of the service processes, and the service processes replying with the second feedback information based on the second heartbeat.

[0099] Specifically, the process link monitoring of the remote terminal test equipment includes: the industrial control computer at the control end sends a heartbeat through the socket interface at a second fixed time interval, and the service process of the remote terminal test equipment replies to the industrial control computer through the socket interface. If the control end does not receive feedback from the service process within the second fixed time interval, or if the feedback signal is empty, a second alarm signal will be issued.

[0100] In this embodiment, the process chain of the remote terminal testing device has multiple applications running. The industrial control computer at the control end monitors the heartbeat of the multiple application processes of the remote terminal. If the control end does not receive feedback from the application processes of the terminal testing device within a second fixed time interval, or if the feedback signal is empty, a second alarm signal will be issued.

[0101] The Socket interface is based on the TCP / IP network API (Application Programming Interface) and defines many functions or routines. In this embodiment, the application process on the remote terminal test device is monitored for heartbeat through this interface.

[0102] The principle behind Socket-based heartbeat monitoring in control and remote terminal testing equipment is as follows:

[0103] On the control side, the ServerSocket interface is used to listen on a specified port. The port can be specified arbitrarily (since ports below 1024 are usually reserved ports and cannot be used arbitrarily in some operating systems, it is recommended to use a port greater than 1024). Heartbeat packets are sent through the specified port, and the system waits for the remote terminal to reply with heartbeat feedback information. Once the terminal test device is confirmed to be connected, a session is established; after the session is completed, the connection is closed.

[0104] The remote terminal testing device uses a Socket interface to send heartbeat packets to a specific port on a control terminal on the network. The connection request is confirmed through the heartbeat feedback. Once the connection is successful, a session is opened; after the session ends, the Socket is closed. The terminal testing device does not need to specify the open port; typically, a port above 1024 is temporarily and dynamically allocated.

[0105] Step S105: Based on the second feedback information from the second heartbeat monitoring, the terminal test device is given a second alarm and / or restarted via the MCU central control system.

[0106] In step S105, after the first heartbeat monitoring, the terminal test device needs to be processed according to the feedback information of the first heartbeat, that is, the terminal test device needs to be processed according to the second feedback information of the second heartbeat monitoring. The second system processing includes a second alarm and / or restart. This step includes: sending heartbeats to each of the service processes through a socket interface instruction at a second fixed time interval; if the second feedback information is not received within the second fixed time, or the second feedback information is empty, then issuing a second alarm signal; when the time of the second alarm signal reaches a second time threshold, restarting the remote terminal test device.

[0107] The industrial control computer at the control end sends a heartbeat via a socket interface at a second fixed time interval. The service process of the remote terminal test device replies to the industrial control computer via the socket interface. If the control end does not receive feedback from the service process within the second fixed time interval, or if the feedback signal is empty, a second alarm signal will be issued. Specifically, if the control end does not receive feedback from the service process within the second fixed time interval, or if the feedback signal is empty, a second alarm signal will be issued. The second fixed time interval can be, for example, 5 seconds, 10 seconds, 15 seconds, 20 seconds, 30 seconds, etc. For example, with 15 seconds, if no feedback is received from the service process within 15 seconds, a second alarm signal will be issued after 15 or 30 seconds, for example, the IPC light (yellow light) will flash slowly. The second alarm signal's duration reaches a second time threshold, for example, this second time threshold can be 100 seconds, 150 seconds, 200 seconds, 300 seconds, etc., and the second time threshold is an integer multiple of the second fixed time interval. For example, with 300 seconds, the system will be restarted after 300 seconds. In addition, the process of monitoring the process, the processing procedure, and abnormal information can be written to the system log before the system restarts.

[0108] According to an embodiment of this disclosure, the remote terminal testing method further includes: periodically collecting risk parameters on the terminal testing device, extracting each risk value from the risk parameters, determining whether each risk value exceeds a corresponding risk threshold, and issuing an alarm signal or performing system processing if any of the risk values ​​exceeds the corresponding risk threshold. The risk parameters include the remote terminal's CPU utilization rate, memory utilization rate, CPU operating temperature, program execution lag time, program execution response time, and / or network connection timeout time.

[0109] According to embodiments of this disclosure, the monitoring method for terminal testing equipment further includes: monitoring the interactive experience of a remote terminal. This interactive experience monitoring includes: synchronously displaying the display interface of the remote terminal, scheduling tasks for applications on the remote terminal, and collecting, monitoring, and reporting logs from modules in the remote terminal's system and the terminal itself. The interactive experience monitoring includes network proxy monitoring, task scheduling monitoring, device proxy monitoring, and / or application performance management system monitoring, etc., and is not limited to these. For example, it may also include the opening of various applications, the display of virtual connections, the allocation of system resources, alarm information, etc.

[0110] like Figure 2The diagram illustrates a schematic of the edge service system of a terminal testing device according to an embodiment of this disclosure. This edge service system is responsible for experience testing. As shown in the diagram, the edge service system includes a network proxy, a test task scheduler, a device proxy, and an APM system. The network proxy, test task scheduler, device proxy, and APM system are used for network connection management of the terminal testing device and for monitoring and controlling the terminal testing device. The network proxy primarily manages the dedicated network line between the central computer room and edge nodes, including content encryption, port forward and reverse proxy, and congestion control. The test task scheduler is mainly responsible for issuing real user tasks and coordinating device resources for running tasks. The device proxy acts as an interaction bridge with the device, responsible for converting user operations into task instructions for execution on the device, thereby completing certain functional operations on the device, such as installing / uninstalling an app, operating the phone interface, and taking screenshots. The APM system is responsible for collecting, monitoring, and reporting logs from other modules in the edge system and the device itself, and for promptly identifying problems in the service system.

[0111] Figure 3 This diagram illustrates the hardware system and service monitoring system of a terminal testing device according to an embodiment of this disclosure. The hardware system of the terminal testing device includes a router, a Wi-Fi module, an industrial control computer, and an MCU central control unit. The MCU central control unit in this service terminal testing hardware system is connected to the terminal device via a UART interface. The terminal device has a monitoring device for monitoring the service availability of the terminal testing device. This monitoring device typically uses a specific interface to connect to a remote terminal for monitoring. This interface can be a USB interface, HDMI interface, Type-C interface, etc., or it can use wireless connections such as Bluetooth or Wi-Fi. The remote terminal device can be a mobile phone, laptop, desktop computer, tablet, handheld device, PSP, etc., or other smart devices such as robots, vending machines, ticket vending machines, cars, etc.

[0112] The MCU central control unit adopts a foreground / background architecture. The main function is an infinite loop that sequentially calls various task functions to complete their respective tasks and handle events. This is a background structure. These task functions belong to the same process, and only one can run at a time. If a process is blocked by a function, other functions cannot run. Interrupt service routines are used to handle asynchronous events in the system. These asynchronous events cannot be described or predicted using a sequential structure in the main loop. For example, serial port data reception is random and unplanned, so interrupt handling is used for event response, which is a foreground structure. Interrupts + main loop = foreground / background architecture. Some global variables are also used, which can be used by various functions to complete communication between functions. In short, the overall framework is built from various interface functions, several global variables, and interrupt handling functions. Real-time event response and polling are used for event processing. The serial port interrupt only handles the enqueueing of the receive data queue FIFO; data processing is completed in a task function within the main loop. The task-level response latency is within 10ms, consuming few resources. The Timer only increments the global variable every 1ms during the interrupt handling.

[0113] In this embodiment of the disclosure, the monitoring of the terminal testing equipment includes system-side availability monitoring and service-side availability monitoring.

[0114] System-side availability monitoring includes network module monitoring, hardware physical link monitoring, and process link monitoring, as detailed below:

[0115] (1) Network module monitoring: Check the availability of the external network using the ping command. If it is unavailable, restart the OpenWRT network service.

[0116] (2) Hardware physical link monitoring: Ensure the reachability of each hardware unit in the system: The WIFI module group and the industrial control computer are monitored by ping pong heartbeat through the RJ45 interface. At the same time, the WIFI module group and the MCU, and the MCU and the industrial control computer are communicated by serial port ping pong through UART. If no heartbeat is received from the TCP Server within 10 seconds, the breathing light (red light) will flash rapidly. If no heartbeat is received after 300 seconds, the system will be restarted.

[0117] (3) Process Link Monitoring: To ensure the availability of the service process, the industrial control computer sends heartbeats at fixed time intervals via socket. The service process replies to the industrial control computer with heartbeats via the socket interface. If no feedback is received from the service process within 15 seconds, the IPC light (yellow light) will flash slowly after 30 seconds. If more than 300 seconds have passed, the system will be restarted.

[0118] Business-side availability monitoring includes device availability monitoring and app monitoring, as detailed below:

[0119] (1) Equipment Availability Monitoring: This mainly includes monitoring the connection of equipment to the system, which can be directly connected to the system through debugging tools such as adb debug bridge. Regularly collect data on the CPU / memory / temperature of the corresponding equipment, and issue alarms in the cloud for equipment that exceeds the risk threshold.

[0120] (2) App Monitoring: This mainly involves monitoring specific applications and reviving them when they are unavailable to ensure their continuous operation. It also includes proactively testing certain network requests within the app to ensure the success rate and availability of network access.

[0121] For details, please refer to Figure 3 The diagram illustrates exemplary monitoring of service availability on terminal testing devices, including device connectivity monitoring, device CPU / memory / temperature performance data acquisition, App availability monitoring, and App network link monitoring. For device connectivity monitoring, if network disconnections or delays occur, the device itself or the network port application needs to be restarted. If high CPU or memory usage, or excessive temperature, causes system lag, an alarm signal is sent to the cloud to notify the remote control terminal. If App availability on the terminal testing device is problematic, the App needs to be reactivated using an activation program. If App network link issues occur, link repair needs to be performed through network testing.

[0122] The hardware system and service monitoring system of this terminal testing equipment are mainly responsible for monitoring and maintaining the hardware, software, and network modules of the terminal testing equipment. This ensures that the terminal testing equipment can automatically monitor and handle faults, thereby ensuring the continuous and stable operation of the system, equipment, and applications.

[0123] Figure 4 This is a schematic diagram of a remote terminal testing device provided in another embodiment of this disclosure. Figure 4 As shown, the device 400 includes: a detection module 401, a first monitoring module 402, a first processing module 403, a second monitoring module 404, and a second processing module 405. Wherein:

[0124] The detection module 401 is used to detect the remote network availability of the terminal testing equipment and the remote control terminal. By transmitting test data and monitoring video over the network, availability testing can move beyond the laboratory and be conducted in the user's real-world environment, improving the authenticity of the test data and reducing time and space constraints. Remote network availability testing achieves distributed data storage and collection by transforming the host and tested machines into server and client machines. Remote network availability testing only requires the client machine to be configured according to the format of the remote control terminal to collect complete data, enabling simultaneous testing across multiple terminals.

[0125] The first monitoring module 402 is used to perform a first heartbeat monitoring on the hardware physical link of the terminal test device through the monitoring system. This first heartbeat monitoring specifically includes: network heartbeat monitoring of the interface between the network module and other modules in the hardware physical link of the terminal test device; and serial port heartbeat communication between the various modules in the hardware physical link. This embodiment uses the Socket interface as the primary communication method. The Socket interface is a long-lived connection by default. To determine whether the Client and Server connections are normal, both the ClientSocket and ServerSocket used in this embodiment have a heartbeat thread. This thread is mainly used to detect whether the Client and Server are connected normally. The normal connection between the Client and Server is mainly ensured by the ping-pang heartbeat monitoring process.

[0126] The first processing module 403 is used to perform a first system processing on the terminal test device based on the first feedback information from the first heartbeat monitoring. The first system processing includes a first alarm and / or restart. After the first heartbeat monitoring, the terminal needs to be processed based on the feedback information from the first heartbeat, that is, the terminal test device needs to be processed based on the first feedback information from the first heartbeat monitoring. This includes: if the first feedback information is not received within a first fixed time, or if the first feedback information is empty, then a first alarm signal is issued; if the duration of the first alarm signal reaches a first time threshold, the terminal test device is restarted. The network (WIFI) module group and the industrial control computer in the system perform network ping-pang heartbeat monitoring through the RJ45 interface. At the same time, the WIFI module group and the MCU, and the MCU and the industrial control computer perform serial port ping-pang heartbeat communication through UART. If the control terminal does not receive the heartbeat signal sent back by the terminal test device within a first fixed time, then a first alarm signal is issued, such as a breathing light (e.g., a red light) flashing rapidly. If the duration of the first alarm signal reaches the first time threshold and is still not received, then the system is restarted. Here, the first time threshold is an integer multiple of the first fixed time.

[0127] The second monitoring module 404 is used to perform a second heartbeat monitoring on the process link of the terminal test device through the monitoring system. Specifically, this includes sending a second heartbeat to each of the service processes, and the service processes replying with the second feedback information based on the second heartbeat. Specifically, the process link monitoring of the terminal test device includes: the industrial control computer at the control end sending a heartbeat at a second fixed time interval via a socket interface; the service processes of the terminal test device replying to the industrial control computer via a socket interface; if the control end does not receive feedback from the service processes within the second fixed time interval, or the feedback signal is empty, a second alarm signal will be issued. In this case, multiple applications are running in the process link of the remote terminal. The industrial control computer at the control end monitors the heartbeats of these multiple application processes of the terminal test device. If the control end does not receive feedback from the application processes of the terminal test device within the second fixed time interval, or the feedback signal is empty, a second alarm signal will be issued.

[0128] The second processing module 405 is used to perform second system processing on the terminal test device based on the second feedback information from the second heartbeat monitoring. This second system processing includes a second alarm and / or restart. After the first heartbeat monitoring, the terminal test device needs to be processed based on the feedback information from the first heartbeat, i.e., the terminal test device needs to be processed based on the second feedback information from the second heartbeat monitoring. This includes: sending heartbeats to each of the service processes via a socket interface command at a second fixed time interval; if no second feedback information is received within the second fixed time interval, or if the second feedback information is empty, issuing a second alarm signal; and restarting the terminal test device when the duration of the second alarm signal reaches a second time threshold.

[0129] The industrial control computer at the control end sends a heartbeat via a socket interface at a second fixed time interval. The service process of the terminal test device replies to the industrial control computer via the socket interface. If the control end does not receive feedback from the service process within the second fixed time interval, or if the feedback signal is empty, a second alarm signal will be issued. Specifically, if the control end does not receive feedback from the service process within the second fixed time interval, or if the feedback signal is empty, a second alarm signal will be issued, for example, the IPC light (yellow light) will flash slowly. When the duration of the second alarm signal reaches a second time threshold, the system will be restarted. Additionally, before the system restarts, the monitoring process, processing procedures, and abnormal information can be written to the system log.

[0130] According to an embodiment of this disclosure, the remote terminal testing device further includes:

[0131] The experience monitoring module is used to monitor the interactive experience of the remote terminal. This interactive experience monitoring includes: synchronously displaying the remote terminal's interface, scheduling tasks for applications on the remote terminal, and collecting, monitoring, and reporting logs from modules within the remote terminal's system and the terminal itself. The interactive experience monitoring includes network proxy monitoring, task scheduling monitoring, device proxy monitoring, and / or application performance management system monitoring, etc., and is not limited to these. For example, it may also include the opening of various applications, the display of virtual connections, the allocation of system resources, alarm information, etc.

[0132] According to an embodiment of this disclosure, the remote terminal testing device further includes:

[0133] A synchronization module is used to synchronize the display interface of the remote terminal.

[0134] The task scheduling module is used to schedule tasks for the applications on the remote terminal.

[0135] The remote monitoring module is used to collect, monitor, and report logs of the modules in the system of the remote terminal and the terminal itself.

[0136] Figure 4 The device shown can perform Figure 1 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 1 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 1 The descriptions in the illustrated embodiments will not be repeated here.

[0137] The following is for reference. Figure 5 This illustration shows a structural schematic of an electronic device 500 suitable for implementing another embodiment of the present disclosure. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0138] like Figure 5As shown, electronic device 500 may include a processing unit (e.g., central processing unit, graphics processor, etc.) 501, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 502 or a program loaded from storage device 508 into random access memory (RAM) 503. RAM 503 also stores various programs and data required for the operation of electronic device 500. Processing unit 501, ROM 502, and RAM 503 are interconnected via communication line 504. Input / output (I / O) interface 505 is also connected to communication line 504.

[0139] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0140] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processing device 501, it performs the functions defined in the methods of embodiments of this disclosure.

[0141] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0142] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0143] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0144] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the test method described in the above embodiments.

[0145] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0146] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0147] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units are not, in some cases, intended to limit the specific unit.

[0148] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0149] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0150] According to one or more embodiments of the present disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform any of the test methods described in the first aspect above.

[0151] According to one or more embodiments of the present disclosure, a non-transitory computer-readable storage medium is provided, characterized in that the non-transitory computer-readable storage medium stores computer instructions for causing a computer to perform any of the test methods described in the first aspect above.

[0152] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

Claims

1. A monitoring method of a terminal test apparatus, characterized by, The terminal testing equipment uses an MCU central control system as its monitoring core. The monitoring system monitors the terminal testing equipment, which includes the MCU central control system and terminal devices. The monitoring method includes: The remote network availability between the terminal testing device and the remote control terminal is detected; The monitoring system performs first heartbeat monitoring on the hardware physical link of the terminal test equipment. Based on the first feedback information from the first heartbeat monitoring, the terminal testing device is triggered by the MCU central control system to issue a first alarm and / or restart. The monitoring system performs second heartbeat monitoring on the process link of the terminal test device. Based on the second feedback information from the second heartbeat monitoring, the terminal testing device is triggered by the MCU central control system to issue a second alarm and / or restart. The step of monitoring the hardware physical link of the terminal test device through the monitoring system to perform the first heartbeat monitoring includes: Perform network heartbeat monitoring on the interfaces between the network module and other modules in the physical hardware link; and Serial heartbeat communication is performed between the various modules in the hardware physical link.

2. The monitoring method according to claim 1, characterized in that, The detection of the remote network availability between the terminal testing device and the remote control terminal includes: The availability of the remote network for the terminal testing device is detected using the ping command. If unavailable, restart the remote network of the terminal test device.

3. The monitoring method of claim 1, wherein, The step of triggering a first alarm and / or restarting the terminal testing device via the MCU central control system based on the first feedback information from the first heartbeat monitoring includes: If the first feedback information is not received within a first fixed time, or if the first feedback information is empty, then a first alarm signal is issued. If the duration of the first alarm signal reaches the first time threshold, the terminal testing device will be restarted.

4. The monitoring method of claim 1, wherein, The second heartbeat monitoring of the process link of the terminal test device through the monitoring system includes: A second heartbeat is sent to each service process, and the service process replies with the second feedback information based on the second heartbeat.

5. The monitoring method according to claim 4, characterized in that, The step of triggering a second alarm and / or restarting the terminal testing device via the MCU central control system based on the second feedback information from the second heartbeat monitoring includes: Heartbeats are sent to each of the service processes via socket interface commands at a second fixed time interval; If the second feedback information is not received within the second fixed time period, or if the second feedback information is empty, a second alarm signal is issued. When the duration of the second alarm signal reaches the second time threshold, the terminal testing device is restarted.

6. The monitoring method according to claim 1, characterized in that, The method further includes: Risk parameters on the terminal testing equipment are collected periodically; Extract each risk value from the risk parameters; Determine whether each of the risk values ​​exceeds the corresponding risk threshold; If any of the aforementioned risk values ​​exceeds the corresponding risk threshold, an alarm signal will be issued or a restart will be initiated.

7. The monitoring method according to claim 6, characterized in that, The risk parameters are the CPU utilization rate, memory utilization rate, CPU operating temperature, program lag time, program response time and / or network connection timeout time of the terminal test device.

8. The monitoring method according to claim 1, characterized in that, The method further includes: Monitoring the interactive experience of remote terminals specifically includes: The display interface of the remote terminal is displayed synchronously; Task scheduling is performed on the applications of the remote terminal; Logs of the modules in the system and the terminal itself in the remote terminal are collected, monitored, and reported.

9. A monitoring device for a terminal testing equipment, characterized in that, The terminal testing equipment uses an MCU central control system as its monitoring core. The monitoring system monitors the terminal testing equipment, which includes the MCU central control system and terminal devices. The monitoring device includes: The detection module is used to detect the remote network availability between the terminal testing device and the remote control terminal; The first monitoring module is used to perform first heartbeat monitoring on the hardware physical link of the terminal test device through the monitoring system. The first processing module is used to trigger a first alarm and / or restart the terminal test device through the MCU central control system based on the first feedback information from the first heartbeat monitoring. The second monitoring module is used to perform second heartbeat monitoring on the process link of the terminal test device through the monitoring system. The second processing module is used to issue a second alarm and / or restart the terminal test device through the MCU central control system based on the second feedback information from the second heartbeat monitoring. The step of monitoring the hardware physical link of the terminal test device through the monitoring system to perform the first heartbeat monitoring includes: Perform network heartbeat monitoring on the interfaces between the network module and other modules in the physical hardware link; and Serial heartbeat communication is performed between the various modules in the hardware physical link.

10. An electronic device, comprising: Memory, used to store computer-readable instructions; as well as A processor for executing the computer-readable instructions, causing the electronic device to perform the method according to any one of claims 1-8.

Images