Mobile test equipment use condition management method and related product

Abstract

The invention discloses a mobile test equipment use condition management method and a related product. According to the scheme, application duration data of current mobile test equipment are obtained; and based on the application duration data, managing the use condition of the current mobile test equipment according to a preset rule. Compared with the prior art that only the process management and control of the mobile test equipment from purchasing and warehousing, application and use to scrap disposal can be realized, the management efficiency is low, and a remarkable blank exists in the fine management level of the use process of the mobile test equipment, the method has obvious advantages.

Description

Technical Field

[0001] This application relates to the field of financial technology, and in particular to a method for managing the usage of mobile testing equipment and related products. Background Technology

[0002] With the deep penetration of fintech, mobile financial services have become a key battleground for banks' digital transformation. Banks and other financial institutions need to use mobile testing equipment on a large scale to develop and test various financial applications such as mobile banking, covering complex aspects such as function debugging, performance stress testing, and compatibility adaptation.

[0003] Currently, to ensure the orderly management of mobile testing equipment, financial institutions have established a full lifecycle management system for mobile testing equipment, achieving process-oriented control from procurement and warehousing to application and disposal. However, the management efficiency is low, and there are significant gaps in the refined management of mobile testing equipment usage. For example, when testers perform financial application testing tasks, mobile testing equipment often runs various non-test-related applications in parallel, such as entertainment media and social chat software. These unrelated applications not only consume the device's CPU and memory resources, causing the test software to lag and malfunction, interfering with the test progress, but may also contain hidden attack code, becoming a breakthrough point for test data leakage.

[0004] How to achieve refined and automated management of the usage of mobile testing equipment is a technical problem that urgently needs to be solved. Summary of the Invention

[0005] To address the aforementioned issues, this application provides a method and related products for managing the usage of mobile testing equipment, with the aim of achieving refined and automated management of the usage of mobile testing equipment.

[0006] The embodiments of this application disclose the following technical solutions:

[0007] The first aspect of this application provides a method for managing the usage of mobile testing equipment, the method comprising:

[0008] Obtain application duration data for the current mobile testing device;

[0009] Based on the application duration data, the usage of the current mobile testing device is managed according to preset rules.

[0010] Optionally, the management of the current usage of the mobile testing device based on the application duration data and according to preset rules includes:

[0011] Based on the application duration data, the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist are calculated respectively in the current mobile testing device; the preset blacklist includes applications that are unrelated to the actual testing process; the preset whitelist includes applications used in the actual testing process; the application duration data includes application name, timestamp, and application usage time;

[0012] Based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist on the current mobile test device, the current mobile test device is managed according to preset rules.

[0013] Optionally, the step of managing the current mobile testing device according to preset rules based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist includes:

[0014] If the average usage time of applications included in the preset blacklist in the current mobile test device is greater than or equal to the first preset threshold, an alarm mechanism is triggered and an alarm message is sent to the user; if the average usage time of applications included in the preset blacklist in the current mobile test device is less than the first preset threshold, the alarm mechanism is not triggered.

[0015] If the average usage time of applications included in the preset whitelist on the current mobile test device is less than the second preset threshold, an email prompting the user to return the current mobile test device will be sent; if the average usage time of applications included in the preset whitelist on the current mobile test device is greater than or equal to the second preset threshold, the current mobile test device will continue to be used.

[0016] Optionally, the method further includes:

[0017] An application keep-alive mechanism is introduced to automatically wake up applications in the current mobile test device at preset time intervals.

[0018] Optionally, before obtaining the application duration data of the current mobile testing device, the method further includes:

[0019] The application duration data is encrypted / decrypted and protected against communication fraud.

[0020] A second aspect of this application provides a mobile testing equipment usage management device, the device comprising:

[0021] The application duration data acquisition module is used to acquire application duration data of the current mobile testing device;

[0022] The mobile testing equipment usage management module is used to manage the current usage of mobile testing equipment based on the application duration data and according to preset rules.

[0023] Optionally, the mobile testing equipment usage management module is specifically used for:

[0024] Based on the application duration data, the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist are calculated respectively in the current mobile testing device; the preset blacklist includes applications that are unrelated to the actual testing process; the preset whitelist includes applications used in the actual testing process; the application duration data includes application name, timestamp, and application usage time;

[0025] Based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist on the current mobile test device, the current mobile test device is managed according to preset rules.

[0026] Optionally, the management of the current mobile testing device based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist according to preset rules includes:

[0027] If the average usage time of applications included in the preset blacklist in the current mobile test device is greater than or equal to the first preset threshold, an alarm mechanism is triggered and an alarm message is sent to the user; if the average usage time of applications included in the preset blacklist in the current mobile test device is less than the first preset threshold, the alarm mechanism is not triggered.

[0028] If the average usage time of applications included in the preset whitelist on the current mobile test device is less than the second preset threshold, an email prompting the user to return the current mobile test device will be sent; if the average usage time of applications included in the preset whitelist on the current mobile test device is greater than or equal to the second preset threshold, the current mobile test device will continue to be used.

[0029] A third aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements a mobile testing device usage management method as provided in any implementation of the first aspect.

[0030] The fourth aspect of this application provides a processor for running a computer program that, when running, executes a mobile test device usage management method as provided in any implementation of the first aspect.

[0031] Compared with the prior art, this application has the following beneficial effects:

[0032] The mobile testing device usage management method provided in this application acquires application duration data of the current mobile testing device, enabling a comprehensive understanding of its actual usage and providing a data foundation for refined management of its usage. Based on the application duration data, the method manages the current usage of the mobile testing device according to preset rules. For example, by pre-setting blacklists and whitelists to complete application duration data analysis and alarms, the method can automatically trigger corresponding management actions based on the application duration data and preset rules, reducing manual intervention, improving management efficiency, and achieving automated and refined management of the mobile testing device. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 A flowchart illustrating a method for managing the usage of mobile testing equipment provided in this application embodiment;

[0035] Figure 2 A flowchart illustrating another method for managing the usage of mobile testing equipment provided in this application embodiment;

[0036] Figure 3 This is a schematic diagram of the data format collected by the mobile testing device provided in the embodiments of this application;

[0037] Figure 4 This is a schematic diagram of a mobile testing equipment usage management device provided in an embodiment of this application. Detailed Implementation

[0038] As described earlier, to ensure the orderly management of mobile testing equipment, financial institutions have established a full lifecycle management system for mobile testing equipment. This system achieves process-oriented control from procurement and warehousing to application and disposal. However, this system is inefficient and has significant gaps in the refined management of mobile testing equipment during its use. For example, when testers are performing financial application testing tasks, mobile testing equipment often runs various non-test-related applications in parallel, such as entertainment media and social chat software. These unrelated applications not only consume the device's CPU and memory resources, causing the test software to lag and malfunction, interfering with the test progress, but may also contain hidden attack code, becoming a breakthrough point for test data leakage.

[0039] In view of the above problems, the inventors have proposed a method and related products for managing the usage of mobile testing equipment, which obtains the application duration data of the current mobile testing equipment; and manages the usage of the current mobile testing equipment according to preset rules based on the application duration data.

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

[0041] See Figure 1 This figure is a flowchart of a method for managing the usage of mobile testing equipment provided in an embodiment of this application. Figure 1 As shown, the method includes the following steps:

[0042] S101. Obtain the application duration data of the current mobile test device.

[0043] Testers install a mobile management app on the mobile testing device as required. When the management app is opened for the first time, the user will be prompted to enable access to usage records. After the tester authorizes this permission, the app's backend can obtain a list of application processes and runtime on the current device through system-level API function calls, thereby enabling automated collection of device application usage time data.

[0044] S102. Based on the application duration data, manage the current usage of the mobile testing device according to preset rules.

[0045] Preset rules refer to predefined rules that trigger management actions. For example, by setting up blacklists and whitelists and their corresponding thresholds, the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist on the mobile testing device are calculated respectively, and compared with the corresponding thresholds to determine the corresponding management actions.

[0046] This application provides a method for managing the usage of mobile testing devices. By acquiring application duration data of the current mobile testing devices, it can comprehensively understand their actual usage and provide a data foundation for refined management. Based on the application duration data, the method manages the current usage of the mobile testing devices according to preset rules. For example, by pre-setting blacklists and whitelists to complete application duration data analysis and alerts, it can automatically trigger corresponding management actions based on the application duration data and preset rules, reducing manual intervention, improving management efficiency, and achieving automated and refined management of mobile testing devices.

[0047] To further improve the mobile testing device usage management method described in the above embodiments, the step of managing the current mobile testing device usage based on the application duration data and according to preset rules has been refined based on the above embodiments.

[0048] See Figure 2 This figure is a flowchart of another method for managing the usage of mobile testing equipment provided in an embodiment of this application. Figure 2 As shown, the method includes the following steps:

[0049] S201. Obtain the application duration data of the current mobile test device.

[0050] Testers install a mobile management app on the mobile test device as required. When the management app is opened for the first time, it prompts the user to enable access to usage records. After the user authorizes the permission, the app's backend can obtain a list of application processes and runtime on the current device through system-level API function calls, thereby achieving automated collection of application usage time data on the test device.

[0051] For example, the format of the collected data is as follows: Figure 3 As shown. Figure 3 This includes basic information about the test equipment and data acquisition, such as device ID, operating system information, operating system version, operating system kernel version, data acquisition time, data acquisition start date, data acquisition end date, and a list of application usage durations. Specifically, the device ID is a unique identifier used to distinguish different mobile test devices; the operating system information is the type of operating system running on the mobile test device, such as Android or iOS; the operating system version is the specific version number of the operating system, such as Android 12.0 or iOS 15.4; the operating system kernel version is the kernel version information of the operating system, usually associated with the operating system version; the data acquisition time is the specific timestamp of the data acquisition, indicating the point in time when the data was collected; the data acquisition start date is the start date of the data acquisition period, used to define the valid scope of the data; the data acquisition end date is the end date of the data acquisition period, which, together with the data acquisition start date, defines the time window for the data; and the application usage duration list contains usage duration records for multiple applications, stored in array form, with each record corresponding to the usage of one application.

[0052] The application usage duration list records the usage of each application within a specified time period. Among them, the APP name is the name of the application, which makes it easy to identify which application the usage data belongs to; the package name is the application's unique identifier in the system; the record date is the date corresponding to the record, indicating the application's usage on that date; and the usage duration is the total usage time of the application within the record date, usually in seconds or milliseconds.

[0053] In one feasible implementation, before acquiring the application duration data of the current mobile testing device, the method further includes:

[0054] The application duration data is encrypted / decrypted and protected against communication fraud.

[0055] The application duration data of the current mobile test device obtained by the server is obtained by passing the application duration data of the current mobile test device collected by the mobile terminal through the mobile gateway for communication anti-counterfeiting, data decryption and protocol conversion.

[0056] The mobile gateway features robust data encryption. After collecting application duration data from the mobile testing device, it performs high-strength encryption and adds a communication anti-spoofing mechanism to ensure that even if the application duration data is intercepted during transmission, it cannot be decrypted or read, effectively protecting data privacy and security. Simultaneously, the mobile gateway can also perform integrity verification on the transmitted application duration data to prevent tampering during transmission, ensuring data authenticity and reliability. Furthermore, to avoid excessive traffic, the mobile gateway forwarding service incorporates a circuit breaker and rate limiting mechanism, helping to maintain service stability and reliability.

[0057] After the mobile gateway forwarding service encrypts and decrypts the data, it forwards the data to the Internet access zone service and stores it in the background database. The Internet access zone service periodically synchronizes incremental data to the intranet server database.

[0058] The entire management process only requires one-way data transmission, effectively avoiding the risk of data exposure of the intranet server caused by two-way data transmission between the intranet server and the mobile gateway in the Internet access area.

[0059] S202. Based on the application duration data, calculate the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist in the current mobile test device.

[0060] The preset blacklist includes applications unrelated to the actual testing process; the preset whitelist includes applications used during the actual testing process; and the application duration data includes the application name, timestamp, and application usage duration.

[0061] Customize the blacklist and whitelist of apps according to the testing requirements and set usage duration thresholds. The blacklist of apps consists of applications that are not related to the testing process (such as social media and games), while the whitelist of apps consists of applications that need to be covered during the testing process.

[0062] For example, the data format is shown in Table 1:

[0063] Table 1

[0064]

[0065]

[0066] Among them, APP name is the application name; APP type is divided according to preset rules, such as blacklist, whitelist, etc.; usage time limit (hours) is the maximum daily usage time of the application, in hours; matching rule is the rule expression used to match the application, which can be package name, application name, or regular expression; matching type indicates the matching method of the matching rule, exact match means completely matching the application name or name, fuzzy match means partially matching or matching using wildcards; enabled status indicates whether the rule is enabled.

[0067] By calculating the average usage time of blacklisted (e.g., entertainment and social non-testing related applications) and whitelisted (e.g., testing tools and automated script applications) respectively, we can intuitively reflect the usage trends of mobile testing devices, identify whether there is abuse or deviation from testing tasks, and provide quantitative basis for management decisions.

[0068] S203. Based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist in the current mobile test device, manage the current mobile test device according to the preset rules.

[0069] In one feasible implementation:

[0070] If the average usage time of applications included in the preset blacklist in the current mobile test device is greater than or equal to the first preset threshold, an alarm mechanism is triggered and an alarm message is sent to the user; if the average usage time of applications included in the preset blacklist in the current mobile test device is less than the first preset threshold, the alarm mechanism is not triggered.

[0071] If the average usage time of applications included in the preset whitelist on the current mobile test device is less than the second preset threshold, an email prompting the user to return the current mobile test device will be sent; if the average usage time of applications included in the preset whitelist on the current mobile test device is greater than or equal to the second preset threshold, the current mobile test device will continue to be used.

[0072] Create a report analysis view of test device usage, analyzing it daily, weekly, and monthly. Calculate the average usage time of blacklisted and whitelisted applications on each mobile test device, thus visualizing mobile test device usage. The server-side performs intelligent data analysis and email alerts based on preset blacklist and whitelist configurations. If a tester's usage time of a blacklisted app exceeds a preset threshold, an alert mechanism is triggered, reminding the user to use the mobile test device compliantly and promptly delete applications unrelated to the testing process. If the usage time of a whitelisted app is below the preset threshold, it indicates that the user is not fully utilizing the mobile test device, and an email reminder is sent to the user to return the device promptly if there are no further testing needs, ensuring maximum utilization of device resources.

[0073] If a user reports fewer days per week than the required number, the server will automatically send a notification to the user reminding them to activate their mobile device and report device usage data.

[0074] Administrators can maintain the mobile app version on the server. Every time the mobile app is launched, it automatically sends a request to the server to obtain the latest software version information. The software update information is divided into mandatory updates and recommended updates. Mandatory updates require users to download the new version installation package and update before they can use the app. Recommended updates prompt users to update, but users can continue to use the app if they do not update.

[0075] The blacklist and whitelist-based management mechanism can detect instances where testers exceed the permitted time limits for using applications unrelated to the testing process (such as social media and games), promptly sending compliance reminders to prevent device abuse. Simultaneously, the whitelist mechanism can detect anomalies where devices are not fully utilized for testing, avoiding resource idleness or inefficient use. Furthermore, the usage time of blacklisted and whitelisted apps is analyzed daily, weekly, and monthly, providing visualization of device usage management data.

[0076] In one feasible implementation, the method further includes:

[0077] An application keep-alive mechanism is introduced to automatically wake up applications in the current mobile test device at preset time intervals.

[0078] Because Android automatically terminates background applications that haven't been running in the foreground for a long time to save power or free up computing resources and memory, a keep-alive mechanism has been added to reduce user intervention costs and ensure that background check applications are automatically woken up at preset time intervals.

[0079] For example, by setting the service running the application as a foreground service, the Android system will increase the service priority of that application, thereby increasing the application's survival time in the background. The Android system can use AlarmManager to implement scheduled task wake-up, periodically waking up background services to perform data collection operations. Delayed tasks and periodic tasks can be registered in the Android system's scheduler to wake up the application and automatically submit app usage records.

[0080] While achieving automated data collection, it also integrates an application keep-alive mechanism, realizing automated maintenance of the management APP's running status. This solves the problem of needing manual intervention to restore the software after it is interrupted in the traditional management model, greatly reducing manual management costs and improving management efficiency.

[0081] This application provides another method for managing the usage of mobile testing devices. By acquiring application duration data of the current mobile testing devices, it can comprehensively understand the actual usage of these devices, providing a data foundation for refined management. Based on the application duration data, the average usage time of applications in a preset blacklist and applications in a preset whitelist on the current mobile testing devices are calculated. This directly reflects the usage tendencies of the devices, identifies any abuse or deviation from testing tasks, and provides a quantitative basis for management decisions. Based on the average usage time of applications in the preset blacklist and whitelist on the current mobile testing devices, the system manages the devices according to preset rules. The system can automatically trigger corresponding management actions, such as alarms, restrictions, or reporting mechanisms, to promptly intervene in abnormal usage, ensure a clean testing environment, promote efficient utilization of testing resources, reduce manual intervention, improve management efficiency, and achieve automated and refined management of mobile testing devices.

[0082] Based on the mobile testing equipment usage management method described in the preceding embodiments, this application also provides a mobile testing equipment usage management device. Figure 4 This is a schematic diagram of the device. Figure 4 As shown, the mobile testing equipment usage management device includes:

[0083] The application duration data acquisition module 401 is used to acquire the application duration data of the current mobile test device.

[0084] The mobile testing device usage management module 402 is used to manage the current usage of the mobile testing device based on the application duration data and according to preset rules.

[0085] Optionally, the mobile testing equipment usage management module is specifically used for:

[0086] Based on the application duration data, the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist are calculated respectively in the current mobile testing device; the preset blacklist includes applications that are unrelated to the actual testing process; the preset whitelist includes applications used in the actual testing process; the application duration data includes application name, timestamp, and application usage time;

[0087] Based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist on the current mobile test device, the current mobile test device is managed according to preset rules.

[0088] Optionally, the management of the current mobile testing device based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist according to preset rules includes:

[0089] If the average usage time of applications included in the preset blacklist in the current mobile test device is greater than or equal to the first preset threshold, an alarm mechanism is triggered and an alarm message is sent to the user; if the average usage time of applications included in the preset blacklist in the current mobile test device is less than the first preset threshold, the alarm mechanism is not triggered.

[0090] If the average usage time of applications included in the preset whitelist on the current mobile test device is less than the second preset threshold, an email prompting the user to return the current mobile test device will be sent; if the average usage time of applications included in the preset whitelist on the current mobile test device is greater than or equal to the second preset threshold, the current mobile test device will continue to be used.

[0091] Optionally, the device further includes: an automatic wake-up module;

[0092] The automatic wake-up module is specifically used to introduce an application keep-alive mechanism to automatically wake up the applications in the current mobile test device according to a preset time interval.

[0093] Optionally, before obtaining the application duration data of the current mobile testing device, the method further includes:

[0094] The application duration data is encrypted / decrypted and protected against communication fraud.

[0095] Furthermore, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the mobile testing device usage management method as described in any of the method embodiments.

[0096] Furthermore, this application embodiment also provides a processor for running a computer program, which executes the mobile testing device usage management method as described in any of the foregoing method embodiments.

[0097] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate. The components indicated as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment solution according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0098] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for managing the usage of mobile testing equipment, characterized in that, include: Obtain application duration data for the current mobile testing device; Based on the application duration data, the usage of the current mobile testing device is managed according to preset rules.

2. The method according to claim 1, characterized in that, The management of the current mobile testing device usage based on the application duration data and according to preset rules includes: Based on the application duration data, the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist are calculated respectively in the current mobile testing device; the preset blacklist includes applications that are unrelated to the actual testing process; the preset whitelist includes applications used in the actual testing process; the application duration data includes application name, timestamp, and application usage time; Based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist on the current mobile test device, the current mobile test device is managed according to preset rules.

3. The method according to claim 2, characterized in that, The management of the current mobile testing device based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist, according to preset rules, includes: If the average usage time of applications included in the preset blacklist in the current mobile test device is greater than or equal to the first preset threshold, an alarm mechanism is triggered and an alarm message is sent to the user; if the average usage time of applications included in the preset blacklist in the current mobile test device is less than the first preset threshold, the alarm mechanism is not triggered. If the average usage time of applications included in the preset whitelist on the current mobile test device is less than the second preset threshold, an email prompting the user to return the current mobile test device will be sent; if the average usage time of applications included in the preset whitelist on the current mobile test device is greater than or equal to the second preset threshold, the current mobile test device will continue to be used.

4. The method according to claim 1, characterized in that, The method further includes: An application keep-alive mechanism is introduced to automatically wake up applications in the current mobile test device at preset time intervals.

5. The method according to claim 1, characterized in that, Before obtaining the application duration data of the current mobile testing device, the process also includes: The application duration data is encrypted / decrypted and protected against communication fraud.

6. A mobile testing equipment usage management device, characterized in that, include: The application duration data acquisition module is used to acquire application duration data of the current mobile testing device; The mobile testing equipment usage management module is used to manage the current usage of mobile testing equipment based on the application duration data and according to preset rules.

7. The apparatus according to claim 6, characterized in that, The mobile testing equipment usage management module is specifically used for: Based on the application duration data, the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist are calculated respectively in the current mobile testing device; the preset blacklist includes applications that are irrelevant to the actual testing process; The preset whitelist includes applications used in the actual testing process; The application duration data includes the application name, timestamp, and application usage duration; Based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist on the current mobile test device, the current mobile test device is managed according to preset rules.

8. The apparatus according to claim 7, characterized in that, The management of the current mobile testing device based on the average usage time of applications in the preset blacklist and the average usage time of applications in the preset whitelist, according to preset rules, includes: If the average usage time of applications included in the preset blacklist in the current mobile test device is greater than or equal to the first preset threshold, an alarm mechanism is triggered and an alarm message is sent to the user; if the average usage time of applications included in the preset blacklist in the current mobile test device is less than the first preset threshold, the alarm mechanism is not triggered. If the average usage time of applications included in the preset whitelist on the current mobile test device is less than the second preset threshold, an email prompting the user to return the current mobile test device will be sent; if the average usage time of applications included in the preset whitelist on the current mobile test device is greater than or equal to the second preset threshold, the current mobile test device will continue to be used.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the mobile testing equipment usage management method as described in any one of claims 1-5.

10. A processor, characterized in that, Used to run a computer program, which, when running, executes the mobile testing equipment usage management method as described in any one of claims 1-5.

Images