Mobile terminal group control method and device for department and wound education

Abstract

The invention discloses a mobile terminal group control method and device for department and wound education. The method comprises the following steps: identifying mobile equipment, and registering the identified mobile equipment in a mobile equipment group control platform based on Web; and carrying out group control operation on the identified mobile equipment through the mobile equipment group control platform based on the web. According to the method and the device, the technical problem of poor cross-platform operation capability due to the fact that group control software is a desktop client in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of science and technology education, and in particular to a mobile terminal group control method and device for science and technology education. Background Art

[0002] Currently, mobile application development faces complex compatibility testing issues, especially in scenarios with multiple devices and multiple operating systems (such as application compatibility testing for Android and iOS devices). Traditional methods rely on manual operations and single-device testing, which is not only inefficient but also prone to missing key issues.

[0003] Most of the existing group control software is based on desktop clients, which limits cross-platform operation capabilities and lacks specialized functions for development and testing. Common problems include: 1) complex operation, high learning cost, especially unfriendly to non-technical personnel; 2) poor scalability, difficult to flexibly adapt to rapidly changing test needs; 3) insufficient device support, unable to be compatible with both Android and iOS devices; 4) limited automation capabilities, difficult to complete complex test tasks.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a mobile terminal group control method and device for science and technology education, so as to at least solve the technical problem that the group control software in the prior art has poor cross-platform operation capability due to being a desktop client.

[0006] According to one aspect of an embodiment of the present invention, a method for group control of mobile devices for science and technology education is provided, comprising: identifying mobile devices and registering the identified mobile devices in a Web-based mobile device group control platform; and performing group control operations on the identified mobile devices through the web-based mobile device group control platform.

[0007] According to another aspect of an embodiment of the present invention, a mobile device group control device for science and technology education is also provided, including: an identification module, configured to identify mobile devices and register the identified mobile devices in a Web-based mobile device group control platform; a group control module, configured to perform group control operations on the identified mobile devices through the web-based mobile device group control platform.

[0008] In an embodiment of the present invention, a mobile device is identified and registered in a mobile device group control platform based on a Web; and a group control operation is performed on the identified mobile device through the mobile device group control platform based on a Web. The above solution solves the technical problem that the group control software in the prior art has poor cross-platform operation capability due to being a desktop client. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0010] Figure 1 is a flow chart of a mobile device group control method for scientific and technological innovation education according to an embodiment of the present invention;

[0011] Figure 2 is a system architecture diagram of a Web-based mobile phone group control platform according to an embodiment of the present invention;

[0012] Figure 3 It is a workflow diagram of a system architecture of a Web-based mobile phone group control platform according to an embodiment of the present invention;

[0013] Figure 4 is a flow chart of a Web-based mobile phone group control method according to an embodiment of the present invention;

[0014] Figure 5 is an architecture diagram of a mobile device group control device for science and technology education according to an embodiment of the present invention;

[0015] Figure 6 A schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present disclosure is shown. DETAILED DESCRIPTION

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

[0017] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0018] According to an embodiment of the present invention, a method embodiment of a mobile device group control method for scientific and technological education is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0019] Figure 1 is a flow chart of a mobile device group control method for science and technology education according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0020] Step S102: identifying a mobile device and registering the identified mobile device in a web-based mobile device group control platform.

[0021] It is detected that a user accesses the mobile device group control platform through a front-end Web (browser) interface, wherein the access method includes at least one of the following: USB, Wi-Fi, and Bluetooth; then, the mobile device is identified, for example, at least one of the following of the mobile device: model, operating system version, and status is identified. Then, the identified mobile device is registered in the Web-based mobile device group control platform.

[0022] Step S104: performing group control operations on the identified mobile devices through the web-based mobile device group control platform.

[0023] For example, the task selected by the user is obtained through the web-based mobile device group control platform, and the selected task is distributed to the identified mobile device to perform group control operations on the identified mobile device. After receiving the distributed task, the identified mobile device executes the distributed task. Among them, distributing the selected task to the identified mobile device includes at least one of the following: pushing a configuration file or instruction to the identified mobile device; pushing an instruction to install and / or uninstall applications in batches with one click to the identified mobile device; pushing an instruction to perform a compatibility test to the identified mobile device, for example, simulating different network conditions and / or power status to instruct the identified mobile device to perform the compatibility test; pushing an instruction to perform an automated test to the identified mobile device; pushing an instruction to perform a multi-device synchronous test to the identified mobile device. For example, the identified mobile devices are instructed to perform automated execution of the test process simultaneously through programming.

[0024] Among them, group control operation is the operation of controlling and managing multiple mobile devices at the same time through the group control platform. Group control operation includes at least one of the following: centralized management, batch operation and real-time monitoring. Centralized management is the unified management of all devices through a central platform. Batch operation is to perform a task on multiple devices at the same time, such as batch installation or uninstallation of applications. Real-time monitoring is to monitor the status and execution progress of the device to ensure that the task is executed as expected.

[0025] Afterwards, task execution information of the identified mobile device executing the distributed task is obtained, and the task execution information is displayed in real time.

[0026] The embodiment of the present invention also provides a Web-based mobile phone group control platform that integrates Android and iOS device management capabilities to provide efficient solutions for application development, compatibility testing, automated testing, etc. Through a unified Web platform, users can achieve centralized management, batch operation, and real-time monitoring of multiple devices.

[0027] The Web-based mobile group control platform is a software system that centrally manages and controls multiple mobile devices and supports remote batch operations. The Web is a browser-based application system that can be run without installing a client. Its system architecture is as follows: Figure 2 As shown, it includes a front end 22, a back end 24, a communication module 26 and a database 28. Among them, the front end uses Vue.js to build a user interface, which supports real-time status display and multi-task operation. The back end is based on the microservice architecture of Spring Boot, providing core functions such as device management, task scheduling, and data storage. The communication module uses the WebSocket protocol to achieve real-time communication between the front and back ends and synchronization of multi-device status. The database uses MongoDB to store device information, task data, and logs.

[0028] The web-based mobile phone group control platform is mainly used for: 1) device access, supporting device access via USB, Wi-Fi and Bluetooth; 2) automatic identification of device model, operating system version and status; 3) batch management: one-click batch installation and uninstallation of applications. 4) remote push of configuration files or instructions. 5) compatibility testing: simulating different network conditions and power status. 6) supporting differentiated test tasks across devices. 7) automated testing: automated execution of the test process through programming, test scripts can be written in Python and Java. 8) synchronized testing of multiple devices, collect results and display them in a unified manner. 9) data visualization: real-time display of device status and test results. 10) log query and export functions are provided.

[0029] The following describes the workflow of the system architecture of the Web-based mobile phone group control platform. Figure 3 As shown, the workflow includes the following steps:

[0030] Step S302: The user logs into the platform through the Web interface.

[0031] Mobile devices are connected to the mobile group control platform. For example, mobile devices can be connected to the platform by wire or wireless. Specifically, users use a browser that supports HTML5 to access the login page of the platform. The platform can use the HTTPS protocol to encrypt all data transmissions to ensure the security of user credentials and other sensitive information. The front end uses a single-page application (SPA) based on Vue.js, and uses Ajax technology to submit the user's input account and password (encrypted by the front end or transmitted through TLS) to the back-end authentication module. The back end uses the Spring Boot framework and verifies the user credentials through the Spring Security component, using encryption algorithms such as BCrypt for password comparison. After successful verification, the back end generates a JWT (JSON Web Token) or creates a session through the Session mechanism, and then returns the token or session information to the front end. After receiving the successful authentication response, the front end saves the token in the browser's LocalStorage or Cookie, and immediately initializes the WebSocket long connection for subsequent real-time data interaction. This long connection has an automatic reconnection mechanism after establishment, ensuring that communication can be restored as soon as possible when the network fluctuates, ensuring the high reliability of the system.

[0032] Step S304: Detect device access.

[0033] The device can be connected to the host through the USB interface, or wireless access can be used, such as Wi-Fi and Bluetooth. Users can achieve wireless binding by entering the device IP address or scanning the QR code. The platform uses network detection technology (such as Ping detection and port scanning) to confirm whether the device is online, and uses TLS or other security authentication mechanisms to verify the device identity to prevent unauthorized device access. After the wireless device is connected, a lightweight message channel based on WebSocket or MQTT will be established in the background to ensure the real-time distribution of subsequent tasks and status updates.

[0034] Step S306: device registration and identification.

[0035] For Android devices, the system automatically calls the ADB (Android Debug Bridge) tool to identify the device's serial number, model, system version, and other information by executing the adb devices command. For iOS devices, tool libraries such as libimobiledevice are called to read device information, including UDID, model, and iOS version. When connected by wire, the platform pre-installs the corresponding driver to ensure that the device can be correctly identified and debugged.

[0036] All collected device information will be formatted and stored in the MongoDB database in JSON format, using an index structure for quick subsequent queries. In addition, the platform will also record the device access time, access method (wired or wireless), current power information, network environment and other parameters to facilitate subsequent task scheduling and status monitoring. To ensure the real-time nature of device data, the device management module will also synchronize device status at regular intervals, such as using WebSocket to push device status updates to the front-end interface in real time to achieve real-time monitoring of the device's online status.

[0037] Step S308: The user selects a task.

[0038] The user selects the operation type, such as installing an application or running a script. Specifically, the front end uses Vue.js to build an intuitive task selection interface, where users can select predefined task types (such as application installation, uninstallation, configuration file push, running automated test scripts, etc.) through drop-down menus, radio buttons, or check boxes. For different task types, the interface will dynamically load the corresponding configuration options. For example, when selecting an automated test task, the user can upload or edit the test script, set the timeout, the number of retries, and specify the test environment parameters. Before the user submits the task, the front end performs a parameter validity check to ensure that all required items have been filled in and the format is correct to avoid task failure due to input errors. The system can also provide a task preview function to display the final configuration summary before the task is issued. After the user confirms, click the "Send Task" button, and the task information is submitted to the backend task scheduling service in standard JSON format.

[0039] Step S310, distribute tasks to devices.

[0040] The backend task scheduling system distributes tasks to each device. Specifically, the backend task scheduling module developed based on Spring Boot will first parse the task request submitted by the frontend and generate a unique task identifier (Task ID). The task request is placed in a message queue (such as RabbitMQ or Kafka) and distributed to each target device using asynchronous messaging. During distribution, the system selects the optimal device list through a load balancing algorithm based on the current load, online status, and historical task execution status of the device. The task message sent to the device uses the standard JSON format, and the content includes the task ID, device ID, task type, operation parameters, and the sending timestamp. Task distribution mainly relies on WebSocket to achieve real-time push; in some cases, HTTP long connection or MQTT protocol can also be used to ensure the timeliness and reliability of message transmission. If some devices do not respond to the task sending information in time, the system will trigger the resend mechanism and record relevant logs for subsequent analysis. At the same time, the front-end interface will display the dynamic changes of the task status.

[0041] Step S312: the device executes the task.

[0042] The mobile device receives the task messages sent by the backend in real time through a pre-established WebSocket connection or a dedicated message channel (such as MQTT). The mobile device has a built-in task manager that is responsible for parsing task parameters and determining the task type (for example: application installation, automated test script execution, file push, etc.).

[0043] For automated testing tasks, the mobile device will preload and start the test framework (such as Appium, UIAutomator, or XCUITest for iOS). At the same time, according to the task parameters, the corresponding test environment is configured, such as setting environment variables, adjusting the device screen orientation, and starting necessary background services.

[0044] Mobile devices call system-level interfaces or command-line tools to complete specific tasks. For example, application installation tasks call Android's Package Manager or iOS's related installation interfaces to achieve silent installation; automated test scripts are executed through the built-in interpreter, while monitoring error messages and timeouts during execution.

[0045] During the task execution process, the mobile device is equipped with an exception capture mechanism to automatically retry or record error logs for timeouts, command failures, network interruptions, etc. Each device will generate a task execution log locally, including the execution start time, end time, success flag, error code, and detailed error description. After the task is completed, the log information will be uniformly packaged and uploaded to the backend log server for subsequent troubleshooting and data statistics.

[0046] Step S314, collect and display the results.

[0047] Collect results and update them to the Web interface in real time. Specifically, after the task is executed, the mobile device encapsulates the execution status (success, failure), return data (such as execution logs, screenshots, status codes, etc.), and task completion time into a standard JSON format message. These result data are sent to the back-end server in real time through WebSocket or HTTP POST request. To ensure the reliability of data transmission, the system supports a data retransmission mechanism, and the result data will be cached on the mobile device before receiving a confirmation response. After receiving the task execution result, the back-end task scheduling module will update the task status, store the relevant data in the MongoDB database, and call the data visualization module to process the data. The front-end uses WebSocket to subscribe to the back-end data push service and update the task status dashboard in real time. The page intuitively displays the execution progress, success rate, and device status of each task through charts, lists, progress bars, etc., and supports log detailed query, data filtering, and export functions. If an abnormal situation is found during the task execution, the system can issue a real-time alarm through SMS, email, or Web pop-up window to ensure that users can take corresponding measures in the first time.

[0048] The platform provided in the embodiment of the present application supports cross-platform operation. Users can access it through any device without installing the client. It is compatible with both Android and iOS devices, covering more test scenarios. The platform has batch operation and multi-device synchronization capabilities, which significantly improves test efficiency, and reduces the usage threshold by optimizing the user interface, making operation easier.

[0049] The embodiment of the present invention also provides a mobile phone group control method based on Web, such as Figure 4 As shown, the method includes:

[0050] Step S402: user login and identity authentication.

[0051] Users access the login page of the mobile group control platform through any terminal that supports a browser (PC, tablet, mobile phone, etc.). The page uses the HTTPS protocol to ensure data transmission security.

[0052] The user enters the account and password on the login interface. The front-end page encapsulates the input data into JSON format and submits it to the back-end authentication API through an Ajax request. The back-end service uses the Spring Security framework to retrieve user information from the database and uses encryption algorithms such as BCrypt to verify the input password. After successful verification, the system generates a JWT token or Session ID to maintain the subsequent session status.

[0053] After the front-end receives the response of successful authentication, it saves the returned token and immediately establishes a long WebSocket connection with the back-end to receive device status and task execution feedback information in real time.

[0054] The embodiment of the present application ensures data security and access control through HTTPS and token mechanism. The WebSocket connection needs to be automatically initialized after the page is loaded, and a disconnection reconnection mechanism is provided to ensure that the system can automatically restore communication when the network is unstable.

[0055] Step S404: device access and automatic identification.

[0056] 1) Select the device access method.

[0057] In the device management interface, the user clicks the "Add Device" button and selects wired (USB) or wireless (Wi-Fi, Bluetooth) access method according to needs.

[0058] In some embodiments, wired device access can be used. After connecting the mobile device to the PC via USB, the system calls the local driver and ADB (for Android devices) or related iOS debugging tools to automatically identify the device information. For example, for Android devices, execute the adb devices command to obtain the device serial number, model, system version and other information; for iOS devices, call the libimobiledevice tool library to obtain the device UDID, model and iOS version. The device information is automatically encapsulated as JSON data through the back-end service and stored in MongoDB, and displayed in real time in the Web front-end device list.

[0059] In some other embodiments, wireless device access can be used. The user enters the device IP address or scans the QR code to bind the device, and the system confirms the device's online status by detecting the device's open debugging port or related services. The back-end service confirms whether the device is online through network detection (such as Ping or port scanning); at the same time, the wireless device is securely authenticated to prevent illegal device access. After the wireless device is connected, the device information, access method, online time and other data are automatically registered, and the status information is updated in the device status monitoring module. After the device is successfully connected, the system automatically starts the device information collection module, periodically collects the device's operating status (such as power, network status, memory usage, etc.) and updates it to the database; the front end subscribes to real-time data through WebSocket to ensure that users can intuitively understand the current status of each device. For example, multi-threading and asynchronous processing technology are used to achieve timely update of the status information of each device when batch devices are connected; corresponding identification tools are called for different device platforms (Android and iOS) to ensure data consistency and integrity.

[0060] Step S406: issuing the task selected by the user.

[0061] The user selects one or more connected devices in the device management interface and clicks the "Task Operation" button to enter the task configuration page. The operation types mainly include: application installation / uninstallation, configuration file push, automated test tasks (support Python and Java scripts), system status detection, etc.

[0062] In the task configuration page, users set the corresponding task parameters according to the selected operation type, such as: For automated testing: upload or edit the test script file, set the test parameters (such as delay, number of retries, log save path) For application installation: select the installation package file, specify the installation options (such as silent installation, background installation). For configuration file push: select the configuration file, set the target path and permission parameters.

[0063] After the user confirms the task configuration, he clicks "Submit Task". The front-end encapsulates the task parameters into standard JSON format data and submits it to the back-end task scheduling service; the back-end task scheduling service parses the task request, generates a unique task ID, and performs distributed task scheduling based on the device's online status, load conditions, etc. The system uses a message queue (such as RabbitMQ or Kafka) to send task messages to each mobile device. The message contains information such as the task ID, device ID list, operation type, specific parameters, and issuance time. For example, the task issuance process uses an asynchronous processing mechanism to ensure that the system responds quickly to high-concurrency task requests; the task message format uses JSON, and the field content is unified to facilitate subsequent mobile device parsing; to prevent conflicts when the same device receives multiple tasks, the system uses a distributed lock or status marking mechanism to ensure that a single device only executes one task at the same time.

[0064] Step S408, mobile device task execution.

[0065] First, the task is received and parsed. The mobile device receives the task message sent by the backend in real time through the established communication connection (such as WebSocket or dedicated message channel); the mobile device starts the local task management module, parses the task message, and determines the task type and parameters.

[0066] Next, the mobile device executes the task. For example, for an automated testing task, the specific process of the mobile device is as follows:

[0067] 1) Initialize the test environment.

[0068] The mobile device is pre-installed with an automated testing framework (such as Appium, UIAutomator, etc.), which automatically loads the test environment after receiving a task. It starts the corresponding interpreter or virtual machine environment according to the task parameters (supports Python and Java scripts).

[0069] 2) Script execution and operation simulation.

[0070] After the test script is loaded, operations are performed in sequence according to pre-set steps, such as simulating user input, clicks, sliding, interface jumps, etc.; during the execution process, the system has built-in breakpoint resumption and exception capture mechanisms to ensure that errors are recorded in time and necessary retries are performed when operations are abnormal.

[0071] 3) Data collection and log recording. During the test, the mobile device collects key status data (such as screenshots, control response time, system resource usage, etc.) in real time and temporarily stores the results in the local cache. The logs, error messages, execution time and other detailed data generated during the execution are recorded and packaged and uploaded to the backend server at the end of the task.

[0072] For other tasks such as application installation, uninstallation, and configuration file push, the mobile device calls the corresponding system interface or tool program to perform operations based on the task parameters. For example, in an application installation task, the mobile device calls the system installation interface for silent installation and returns a status code indicating success or failure of the installation; for configuration file push, the mobile device saves the file to the specified path, verifies the integrity of the file, and then feeds back the result. After the task is completed, the mobile device encapsulates the task execution results and related log information into a JSON format feedback message and sends it back to the backend task scheduling module through the WebSocket channel; after receiving the task feedback, the backend updates the task status and displays the execution results in real time on the task monitoring interface of the Web frontend.

[0073] In this embodiment, the automated test script supports parameterization and dynamic adjustment to ensure flexible operation on different devices; the task execution results are transmitted between the mobile device and the backend in a standardized data format to ensure data consistency; in addition, the exception capture and retry mechanism can greatly reduce the task failure rate caused by temporary network and device exceptions.

[0074] Step S410: real-time monitoring, data visualization and log management.

[0075] The front-end interface uses WebSocket to subscribe to the device status, task progress and test result data pushed by the back-end to achieve real-time refresh. The back-end periodically collects device status data and heartbeat detection mechanism to ensure that the status can be updated in time when the device is disconnected or the network is abnormal. The front-end uses data visualization components such as ECharts and D3.js to intuitively display key indicators such as device online rate, task completion rate, and test success rate in the form of charts, curves, and dashboards. At the same time, users can query, filter, and sort historical task logs in the Web interface, and support exporting data to CSV, Excel and other formats for subsequent analysis. In addition, the back-end log service records the operation logs and exception information of each module, including task ID, device ID, operation time, error code, exception description, etc.; the log data stored in the database supports full-text retrieval and multi-condition query, and achieves efficient query by optimizing indexing technology; the system supports regular log archiving to ensure stable database performance under long-term operation.

[0076] The front and back ends of the embodiment of the present application implement real-time data updates through WebSocket, ensuring that users can obtain timely feedback during the operation process; data visualization not only intuitively displays the test results, but also provides data support for subsequent troubleshooting; the log management module adopts a strategy that combines centralized storage with distributed query to ensure that the query speed still meets the requirements when processing massive data.

[0077] Step S412, exception handling.

[0078] The system has a built-in heartbeat detection mechanism to monitor the online status of each device in real time. Once it detects that a device is unresponsive or offline for a long time, the task status of the device is immediately updated to "abnormal", and the user is notified through an alarm on the front-end interface. For temporary network or device problems, the system has an automatic retry mechanism to automatically reissue tasks until the preset number of retries is reached or the task ultimately fails.

[0079] During the task issuance and execution process, if a task execution exception occurs (such as execution timeout, operation failure, script error), the mobile device will record detailed error information and attach the error code and exception description in the task feedback; after receiving the exception feedback, the back-end task scheduling module will update the task status and record relevant information through the log service for user query and subsequent debugging by technical personnel. For critical tasks, the system can set a manual intervention flag and re-issue the task after user confirmation to ensure the integrity and accuracy of the task data.

[0080] Both the front-end and back-end adopt redundant designs, such as WebSocket disconnection reconnection and persistent storage of message queues, to ensure that the overall system is not affected when a local failure occurs; the database adopts master-slave replication and distributed storage technology to ensure that data remains highly available during high-concurrency writing; the modules interact through standardized interfaces, and when an abnormality occurs, the faulty module can be quickly located and switched or restored.

[0081] In the embodiment of the present application, exception handling is used to ensure that any exception occurring in any link during device access, task issuance and execution can be captured and handled in a timely manner; the system's fault tolerance and stability are effectively improved through automatic retry mechanism, heartbeat detection and manual intervention mechanism.

[0082] The present application also provides a mobile device group control device for science and technology education, such as Figure 5 As shown, it includes: an identification module 52, which is configured to identify mobile devices and register the identified mobile devices in a web-based mobile device group control platform; a group control module 54, which is configured to perform group control operations on the identified mobile devices through the web-based mobile device group control platform.

[0083] It should be noted that the mobile device group control device for science and innovation education provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the mobile device group control device for science and innovation education provided in the above embodiment and the mobile device group control method embodiment for science and innovation education belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0084] The embodiment of the present invention also provides another method for controlling mobile phone groups based on Web. The difference from the above embodiment is that the automated test task adopts a graphical representation method, and the relationship between automated test operations is represented by a directed graph. Each operation will generate a corresponding node, and the order relationship between operations is connected by edges. Suppose the operation sequence is O={o 1 ,o 2 ,…,o n}, each operation o i Generate a node V i , and for every pair of operations o i and j , if o i In o j If it is executed before, the edge E is generated. i,j ={(V i ,V j)}, thus forming a complete automated test flowchart. All generated operation data flows and corresponding guidance configurations will be stored in the database for subsequent retrieval and application. The data will be saved in a structured format, including the task ID and the corresponding data flow. Each data flow consists of nodes and edges. The nodes describe the operation type and content, and the edges represent the sequential relationship of the operations. Finally, cluster analysis and association rule learning can also be used to optimize the operation data and optimize the guidance configuration. Specifically, through cluster analysis, the distance between operations in each cluster can be minimized to form a more efficient automated test. For example, the following clustering objective function can be used:

[0085]

[0086] Among them, Z represents the optimal result of clustering, that is, the optimal cluster division, K is the number of clusters, C k represents the kth cluster, which contains all the data points classified into this cluster, μ k represents the center of the kth cluster, which is the mean of all data points in the cluster, x represents the data point, α k is the cluster size penalty factor. This parameter controls the size of the cluster to prevent some clusters from being too large or too small, thus affecting the clustering effect. If |Ck| (cluster size) is too large, the penalty term will be increased, thereby prompting the algorithm to automatically adjust the cluster division. Βk is the diversity reward factor. This parameter encourages the diversity of data points within each cluster, which is determined by measuring the degree of similarity within the cluster. If the similarity of a cluster is too high (that is, the data points are too similar), the penalty will be increased, prompting the algorithm to disperse the data points into different clusters. Diversity can be calculated by the following formula:

[0087]

[0088] Among them, Sim(x i ,x j ) is the data point x i and x j The similarity measurement between them can use cosine similarity or other similarity calculation methods suitable for data features.

[0089] Figure 6 FIG. 1 shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiment of the present disclosure. It should be noted that: Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0090] like Figure 6As shown, the electronic device includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for system operation are also stored. The CPU 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0091] The following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage section 1008 as needed.

[0092] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A mobile device group control method for scientific and technological education, characterized in that: include: Identify the mobile device and register the identified mobile device in the web-based mobile device group control platform; The identified mobile devices are group controlled by the web-based mobile device group control platform.

2. The method according to claim 1, characterized in that: The group control operation includes at least one of the following operations: centralized management, batch operation and real-time monitoring.

3. The method according to claim 2, characterized in that The identified mobile devices are group-controlled by the web-based mobile device group control platform, including: obtaining a task selected by a user by the web-based mobile device group control platform, and distributing the selected task to the identified mobile devices to perform group control on the identified mobile devices, wherein the identified mobile devices execute the distributed task; After distributing the selected task to the identified mobile device, the method further includes: acquiring task execution information of the identified mobile device executing the distributed task, and displaying the task execution information in real time.

4. The method according to claim 3, characterized in that Before identifying the mobile device, the method further includes: detecting that a user accesses the mobile device group control platform through a front-end Web interface, wherein the access method includes at least one of the following: USB, Wi-Fi, and Bluetooth; Identifying a mobile device includes identifying at least one of the following of the mobile device: model, operating system version, and status.

5. The method according to claim 3, characterized in that: Distributing the selected task to the identified mobile device includes at least one of the following: pushing a configuration file or instruction to the identified mobile device; pushing an instruction to install and / or uninstall applications in batches with one click to the identified mobile device; pushing an instruction to perform compatibility testing to the identified mobile device; pushing an instruction to perform automated testing to the identified mobile device; pushing an instruction to perform multi-device synchronization testing to the identified mobile device.

6. The method according to claim 5, characterized in that Pushing an instruction to perform a compatibility test to the identified mobile device, including: simulating different network conditions and / or power states to instruct the identified mobile device to perform the compatibility test; and / or Pushing instructions for performing multi-device synchronous testing to the identified mobile devices includes: programming to instruct the identified mobile devices to automatically execute the testing process simultaneously.

7. A mobile device group control device for scientific and technological education, characterized in that: include: an identification module configured to identify the mobile device and register the identified mobile device in the web-based mobile device group control platform; The group control module is configured to perform group control operations on the identified mobile devices through the web-based mobile device group control platform.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. A computer device, characterized in that: include: Memory and processor, The memory stores a computer program; The processor is used to execute the computer program stored in the memory, and when the computer program is run, the processor is enabled to execute the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images