Unified management method, device and system of cross-platform intelligent equipment and medium

Abstract

The embodiment of the invention discloses a unified management method, device and system for cross-platform intelligent equipment and a medium, and the method comprises the steps: constructing a platform adaptation layer which is integrated with communication protocol modules of at least two kinds of platform equipment so as to interact with the platform equipment corresponding to the communication protocol modules; periodically scanning all connected devices based on the platform adaptation layer through an independent daemon thread; analyzing the scanned original equipment information of the different platform equipment, and converting the analyzed original equipment information into a preset unified equipment information data structure; analyzing according to the scanned equipment information to obtain an equipment state change event; transmitting an equipment state change event based on a publish-subscribe mechanism; the published equipment state change event carries equipment information of a preset unified equipment information data structure. Therefore, automatic discovery, identification, monitoring and management of cross-platform intelligent equipment can be realized, and the framework is flexible and easy to expand.

Description

Unified management methods, devices, systems and media for cross-platform smart devices Technical Field

[0001] The embodiments of the present invention relate to the field of computer and device management technology, and in particular to a unified management method, device, system and medium for cross-platform intelligent devices. Background Technology

[0002] Currently, in scenarios such as mobile application testing, automated script execution, and device management, it is often necessary to manage a large number of different types of smart devices simultaneously. Current management tools are typically platform-specific; for example, ADB (Android Debug Bridge) is used to manage Android devices, while libimobiledevice or specific commercial toolkits are used to manage iOS devices. Existing smart device management solutions suffer from the following problems:

[0003] Inconsistent tools: This forces administrators to switch between different tools and interfaces, resulting in cumbersome operations and low efficiency.

[0004] Platform fragmentation: The inability to manage different types of smart devices (e.g., Android and iOS) simultaneously creates information silos and management barriers.

[0005] Low level of automation: The connection, identification and status monitoring of the equipment rely heavily on manual polling or manual operation, which cannot achieve true automated management.

[0006] Inconsistent information: Device identifiers, model information, and status information on different platforms have vastly different formats, making it difficult to present and process them uniformly within a single system.

[0007] Delayed event response: When the device status changes (such as connection or disconnection), there is a lack of an efficient event-driven mechanism to notify other parts of the system, resulting in untimely management actions.

[0008] Poor scalability: Existing solutions are difficult to integrate smoothly with new device platforms or new management functions, resulting in a rigid system architecture. Summary of the Invention

[0009] This invention provides a unified management method, system, and medium for cross-platform smart devices. It aims to achieve efficient management by actively monitoring device status and using an event-driven mechanism, while also being easily expandable and presenting information in a unified manner across different platform smart devices.

[0010] In a first aspect, embodiments of the present invention provide a unified management method for cross-platform smart devices, including:

[0011] A platform adaptation layer is constructed, which integrates communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules;

[0012] All connected devices are periodically scanned based on the platform adaptation layer via a separate daemon thread;

[0013] The raw device information of different platform devices obtained by scanning is parsed and transformed into a preset unified device information data structure.

[0014] The device status change events are obtained by analyzing the scanned device information;

[0015] The device state change event is transmitted based on a publish-subscribe mechanism; wherein the published device state change event carries device information in the preset unified device information data structure.

[0016] As one embodiment, the transmission of the device state change event based on the publish-subscribe mechanism includes:

[0017] For published device status change events, the corresponding consumer module is obtained according to the mapping table between event type and listening function, and the device status change event is pushed to the corresponding consumer module; wherein, the mapping table between event type and listening function is updated according to the subscription relationship.

[0018] As one embodiment, the step of analyzing the scanned device information to obtain device status change events includes:

[0019] The device connection disconnection event is obtained by comparing the device information obtained in the current cycle scan with the device information obtained in the previous cycle scan.

[0020] As one embodiment, the method further includes:

[0021] Provides a configuration interface for the scanning cycle of connected devices.

[0022] As one embodiment, the preset unified device information data structure includes: cross-platform device identifier, preset unified format device model information, device market name, device status, and device unique identifier.

[0023] As one embodiment, the method further includes:

[0024] When the device status change event is a new device event, the new device is added to the available resource pool, the task allocation strategy is updated, and test tasks to be executed are assigned; when the device status change event is a device disconnection event, the task status of the disconnected device is cleared, the interrupted tasks are reallocated, and the resource pool status is updated.

[0025] As one embodiment, the step of analyzing the scanned device information to obtain device status change events includes:

[0026] Equipment status change events are obtained by analyzing equipment information that has been transformed into a preset unified equipment information data structure.

[0027] Secondly, embodiments of the present invention provide a unified management device for cross-platform smart devices, comprising:

[0028] A construction module is used to build a platform adaptation layer, wherein the platform adaptation layer integrates communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules;

[0029] The scanning unit is used to periodically scan all connected devices based on the platform adaptation layer via an independent daemon thread;

[0030] The unified information abstraction module is used to parse the raw device information of different platform devices obtained by scanning, and transform the parsed raw device information into a preset unified device information data structure.

[0031] The event recognition module is used to analyze the scanned device information to obtain device status change events;

[0032] An event-driven communication module is used to transmit the device state change event based on a publish-subscribe mechanism; wherein the published device state change event carries device information with the preset unified device information data structure.

[0033] Thirdly, embodiments of the present invention provide a unified management system for cross-platform smart devices, including a memory and a processor;

[0034] The memory is used to store computer programs; the processor is used to read the computer programs in the memory and, when executing the programs, implement the unified management method for cross-platform intelligent devices as described above.

[0035] Fourthly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the unified management method for cross-platform smart devices as described in the first aspect.

[0036] Compared with the prior art, the technical solution provided by the embodiments of the present invention has at least the following positive effects:

[0037] In the technical solution of this invention, a platform adaptation layer is constructed, integrating communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules. This allows for smooth integration of new devices from different platforms and facilitates expansion. An independent daemon thread periodically scans all connected devices based on the platform adaptation layer, parses the raw device information of the scanned devices from different platforms, and transforms the parsed raw device information into a preset unified device information data structure. Device status change events are analyzed based on the scanned device information and transmitted using a publish-subscribe mechanism. The published device status change events carry device information from the preset unified device information data structure. This enables proactive monitoring of device status and efficient management of device status changes through an event-driven communication mechanism. It also unifies the presentation of device information, resulting in a more user-friendly management interface. Attached Figure Description

[0038] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 is a flowchart illustrating the unified management method for cross-platform smart devices provided in Embodiment 1 of the present invention;

[0040] Figure 2 is an interaction diagram among the constituent modules in the unified management system of cross-platform intelligent devices provided in Embodiment 1 of the present invention.

[0041] Figure 3 is a schematic diagram of the device discovery, identification, information unification, and event release process of the unified management method for cross-platform intelligent devices provided in Embodiment 1 of the present invention.

[0042] Figure 4 is a sequence diagram of the unified management system for cross-platform smart devices provided in Embodiment 1 of the present invention, which responds to device connection / disconnection events and drives the user interface module and task scheduler to update.

[0043] Figure 5 is a schematic diagram of the user interface of the unified management system for cross-platform smart devices provided in Embodiment 1 of the present invention;

[0044] Figure 6 is a schematic diagram of the structure of the unified management device for cross-platform intelligent devices provided in Embodiment 2 of the present invention; Figure 7 is a schematic diagram of the hardware architecture of the unified management method for cross-platform intelligent devices provided in Embodiment 3 of the present invention. Detailed Implementation

[0045] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0046] Figure 1 is a flowchart illustrating a unified management method for cross-platform smart devices provided in an embodiment of the present invention. This method is used for unified and efficient management of multi-platform smart devices and can be applied to scenarios such as mobile application testing, automated script execution, and device management. The method can be executed by a unified management device for cross-platform smart devices provided in this embodiment of the present invention. This device can be implemented using software and / or hardware and configured within the unified management system for cross-platform smart devices. As shown in Figure 1, the unified management method for cross-platform smart devices in this embodiment includes the following steps:

[0047] Step 101: Construct a platform adaptation layer. The platform adaptation layer integrates communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules.

[0048] Step 102: Periodically scan all connected devices based on the platform adaptation layer using a separate daemon thread;

[0049] Step 103: Parse the raw device information of different platform devices obtained by scanning, and convert the parsed raw device information into a preset unified device information data structure;

[0050] Step 104: Analyze the scanned device information to obtain device status change events;

[0051] Step 105: Transmit device status change events based on a publish-subscribe mechanism; wherein, the published device status change events carry device information with a preset unified device information data structure.

[0052] The following provides a detailed description of steps 101 to 105 of the unified management method for cross-platform smart devices in this embodiment.

[0053] Step 101: Construct a platform adaptation layer. The platform adaptation layer integrates communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules.

[0054] Different platform devices include Android and iOS devices. Android devices are interacted with by calling ADB (Android Debug Bridge) commands, while iOS devices are communicated directly through the tidevice library. The platform adaptation layer also provides a unified platform interface, which shields the differences in underlying protocols, making the architecture flexible, highly scalable, and allowing for smooth integration with new device platforms, such as those based on the HarmonyOS platform.

[0055] Step 102: Periodically scan all connected devices based on the platform adaptation layer using a separate daemon thread.

[0056] A separate daemon thread, created by the developers, periodically calls the platform's unified interface (encapsulating ADB commands and the tidevice library) to obtain a list of all currently connected Android and iOS devices and their raw information. It's worth noting that a configuration interface for the scanning cycle of connected devices is provided, allowing users to flexibly adjust the scanning cycle according to their needs.

[0057] Step 103: Parse the raw device information of different platform devices obtained by scanning, and transform the parsed raw device information into a preset unified device information data structure.

[0058] Developers construct a unified information abstraction layer. This layer parses and standardizes raw device information obtained from different platforms (such as Android's `product.model`, iOS's `ProductType` and `MarketingName`), and encapsulates it into a pre-defined unified device information data structure—the cross-platform unified `DeviceInfo` data structure. This means the raw device information is sent to the unified information abstraction layer and converted into a standard `DeviceInfo` object. The pre-defined unified device information data structure may include: cross-platform device identifier, pre-defined unified format device model information, device market name, device status, and device unique identifier, providing a consistent and standardized data view for upper-layer systems. The cross-platform device identifier serves as a standardized, universal identifier for devices on different platforms within the unified management system. The pre-defined unified format device model information unifies device model information across different platforms. Presenting the device market name improves user-friendliness for administrators. Device status can be configured as needed, such as whether the device is connected or disconnected. The device unique identifier, such as Android's `android_id` or iOS's `UDID`, is used to identify the device's unique identity.

[0059] Step 104: Analyze the scanned device information to obtain device status change events.

[0060] The device information obtained from the current scan cycle is compared with that obtained from the previous scan cycle to identify device connection / disconnection events. Based on the device information obtained from the current scan cycle, a device set for the current cycle is generated. This set is then compared with the previous cycle's set to accurately identify newly added and missing devices. The device information in the device set can be a pre-defined, unified device information data structure, but is not limited to this; it can also be the original scanned device information. It is understood that device status change events include, but are not limited to, newly added device events and device disconnection events. Scanning tasks can be configured according to business needs to obtain corresponding device status change events, such as resource utilization.

[0061] Step 105: Transmit device state change events based on the publish-subscribe mechanism.

[0062] The published device status change events carry device information with a pre-defined unified device information data structure. Specifically, for each published device status change event, the corresponding consumer module is determined based on the mapping table between event type and listener function, and the device status change event is pushed to the corresponding consumer module; the mapping table between event type and listener function is updated according to the subscription relationship.

[0063] A publish-subscribe pattern is adopted to decouple communication between modules in a unified management system for cross-platform smart devices. By maintaining a mapping table of event types and listener functions, events such as "device_connected" or "device_disconnected" are published when a device connection or disconnection is detected, carrying a unified DeviceInfo object as a parameter. Any other functional module in the system (such as the task scheduler or user interface) can register as a listener for specific events, thereby enabling real-time, asynchronous responses to device state changes.

[0064] The application of the unified management method in this embodiment can include: when a device status change event is a new device event, adding the new device to the available resource pool, updating the task allocation strategy, and assigning test tasks to be executed. When a device status change event is a device disconnection event, clearing the task status of the disconnected device, reallocating interrupted tasks, and updating the resource pool status. For example, the task scheduling and execution module listens for published device status change events. When a device connects, it can automatically add it to the available device pool and dynamically allocate tasks (such as automated test scripts, application installation, and configuration operations) to idle and qualified devices according to its own strategy (such as polling or manual selection). It can also listen for device disconnection events. Once a device disconnects, it immediately cancels all queued or running tasks on the disconnected device and releases resources, thereby achieving automated unified management of smart devices across multiple platforms.

[0065] The following describes the unified management method for cross-platform intelligent devices and its application process according to an embodiment of the present invention, using the interaction diagram of the unified management system architecture components for cross-platform intelligent devices shown in Figure 2, the flowchart of automatic device discovery, identification, monitoring and management shown in Figure 3, and the sequence diagram of the unified management system shown in Figure 4. The method includes the following steps:

[0066] Step S1: The system starts up, the unified device management module initializes its platform adaptation layer, and starts an independent daemon thread to start periodically scanning devices.

[0067] Step S2: Discovery and Identification: During each scan cycle, the daemon thread calls the ADB and tidevice interfaces through the platform adaptation layer to obtain a list of all currently connected Android and iOS devices and their original information.

[0068] Step S3: Information Unification and Status Comparison: The raw information of the scanned devices is sent to the unified information abstraction layer and converted into standard DeviceInfo objects. The device set of the current period is compared with the device set of the previous period to accurately identify newly added and missing devices. Understandably, other device states can also be monitored according to actual business needs, such as monitoring CPU and memory usage. The scanning cycle for different states can be different.

[0069] Step S4: Event Release:

[0070] For a new device event, publish a "device_connected" event, carrying the DeviceInfo object of the new device.

[0071] For device disappearance events, publish a "device_disconnected" event, carrying a DeviceInfo object of the disconnected device.

[0072] Step S5: Event Response: The event-driven communication module distributes new device events and device disconnection events to all registered listeners. For example, after receiving the event, the user interface module updates the device list display in real time.

[0073] After receiving the "device_connected" event, the task scheduling module adds the new device to the resource pool; after receiving the "device_disconnected" event, it clears all task states related to that device.

[0074] Step S6: Loop monitoring: After waiting for a configurable time interval, the daemon thread (also known as the monitoring thread) returns to step S2, forming a continuous and automated management loop.

[0075] The key technical details of the embodiments of the present invention will be described below with reference to the code.

[0076] Regarding platform adaptation and unified information abstraction:

[0077] In `device_manager.py`, the `_get_current_devices` method simultaneously calls both `adb` and `tidevice` to achieve platform adaptation for Android and iOS (a manifestation of the platform adaptation layer). The `_get_ios_devices_with_tidevice` method not only retrieves the UDID (Unique Device Identifier) ​​but also queries `ProductType` and `MarketingName` using `get_value`, enabling deep information extraction from iOS devices. Ultimately, both Android and iOS devices are constructed as instances of the `DeviceInfo` class (a manifestation of the unified information abstraction layer).

[0078] Regarding proactive status monitoring and event publishing:

[0079] The `_device_listening_loop` method is the daemon thread of the active state monitoring unit. The `_check_connected_devices` method retrieves the current device list, and the `_update_device_status` method identifies state changes by comparing `current_devices` and `self.connected_devices`, and then calls the `_handle_device_connected` or `_handle_device_disconnected` method. Within these methods, events are published via `self.event_manager.emit_event`, which is the trigger point for the entire event-driven mechanism.

[0080] Regarding the incident response:

[0081] In the `__init__` method of `gui_main.py`, the graphical user interface (GUI) module registers a listener for device events (`self.event_manager.register_listener("device_connected", self._on_device_status_changed)`). Therefore, when an event occurs, the `_on_device_status_changed` method is called, and `self.root.after` ensures the interface is safely updated on the UI thread. This demonstrates how the user interface module responds to device management events. Figure 5 shows the application interface integrated into automated calibration, illustrating automatic device discovery, identification, monitoring, and unified information abstraction management.

[0082] The unified management method for cross-platform smart devices in this invention has the following significant advantages compared with the prior art:

[0083] True cross-platform unified management: For the first time, it has achieved seamless access, identification and information abstraction for Android and iOS devices within a single system framework, breaking down platform barriers.

[0084] Highly efficient automated monitoring: Through an independent daemon thread and difference comparison algorithm, it realizes real-time and automatic discovery and response to device connection status without manual intervention.

[0085] Highly decoupled and scalable architecture: Based on the publish-subscribe event-driven pattern, the device management core is completely decoupled from upper-layer applications (such as UI and task scheduling). Adding new functional modules or supporting new device platforms (such as HarmonyOS) only requires registering events or extending the platform adaptation layer, without modifying the core architecture, resulting in extremely high system scalability.

[0086] Information standardization: The provided DeviceInfo object provides a unified and standardized view of devices for upper-layer applications, which greatly simplifies the development of multi-device applications (such as compatibility testing and batch operations).

[0087] Intelligent management: The system can automatically trigger complex management logic (such as dynamic task scheduling and resource recycling) based on equipment status events, which improves the management efficiency and reliability of the entire equipment resource pool.

[0088] The advantages of the unified management system for cross-platform smart devices in this invention compared to existing technologies are as follows:

[0089] Feature Dimension: This invention (unified management system) ADB + libimobiledevice / commercial tool system management uniformity Strong unification: a single system, a unified interface, and a unified equipment information model and status monitoring. Completely separate: two independent sets of tools and commands; inconsistent information formats and workflows; automation and real-time performance. Highly automated • Background daemon processes proactively discover and monitor • Event-driven, with real-time notifications of state changes Passive vs. Polling: • Relies on manual commands or scripts for polling • Cannot achieve real-time event response architecture and integration Decoupling and Scalability: • Publish-subscribe pattern, loosely coupled modules • Easy integration of new features or platforms Tight coupling and high integration costs; business logic and tool commands are deeply bound; adding new features requires modification of multiple scripts; level of abstraction. Highly abstract • Provides standardized DeviceInfo objects • Upper-layer applications do not need to worry about platform differences The underlying raw information needs to be directly parsed from the adb devices or idea_id output. The upper layer needs to handle platform-specific details. surface

[0090] Embodiment 2 of the present invention provides a unified management device for cross-platform smart devices, configured in a unified management system for cross-platform smart devices. As shown in Figure 6, the unified management device includes: a construction module 601, a scanning unit 602, a unified information abstraction module 603, an event recognition module 604, and an event-driven communication module 605.

[0091] Module 601 is used to build a platform adaptation layer. The platform adaptation layer integrates communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules.

[0092] The scanning unit 602 is used to periodically scan all connected devices based on the platform adaptation layer via an independent daemon thread.

[0093] The unified information abstraction module 603 is used to parse the original device information of different platform devices obtained by scanning, and to transform the parsed original device information into a preset unified device information data structure.

[0094] The event recognition module 604 is used to analyze the scanned device information to obtain device status change events.

[0095] The scanning unit 602 and the event recognition module 604 enable active status monitoring of the equipment.

[0096] The event-driven communication module 605 is used to transmit the device state change event based on a publish-subscribe mechanism. The published device state change event carries device information within the preset unified device information data structure.

[0097] Optionally, the event-driven communication module 605 is specifically used to, for published device state change events, obtain the corresponding consumer module according to the mapping table between event type and listening function, and push the device state change event to the corresponding consumer module; wherein, the mapping table between event type and listening function is updated according to the subscription relationship.

[0098] Optionally, the event recognition module 604 is specifically used to compare the device information obtained in the current cycle scan with the device information obtained in the previous cycle scan to obtain the device connection disconnection event.

[0099] Optionally, the scanning unit 602 is also used to provide a configuration interface for the scanning cycle of the connected device.

[0100] Optionally, the preset unified device information data structure includes: cross-platform device identifier, preset unified format device model information, device market name, device status, and device unique identifier.

[0101] Optionally, the unified management device may also include a task scheduling module, which is used to add the new device to the available resource pool, update the task allocation strategy, and allocate test tasks to be executed when the device status change event is a new device event; and to clear the task status of the disconnected device, reallocate the interrupted tasks, and update the resource pool status when the device status change event is a device disconnection event.

[0102] Optionally, the event recognition module 604 is specifically used to analyze the equipment status change event based on the equipment information converted into a preset unified equipment information data structure.

[0103] Compared with existing technologies, the unified management device for cross-platform smart devices in this invention constructs a platform adaptation layer. This layer integrates communication protocol modules for at least two platform devices, enabling interaction with the platform devices corresponding to these modules. This allows for smooth integration of new devices from different platforms and facilitates expansion. An independent daemon thread periodically scans all connected devices based on the platform adaptation layer, parses the raw device information from different platform devices, and transforms this information into a preset unified device information data structure. Device status change events are analyzed based on the scanned device information and transmitted using a publish-subscribe mechanism. The published device status change events carry device information within the preset unified device information data structure. This achieves proactive monitoring of device status and efficient management of device status changes through an event-driven communication mechanism. It also unifies the presentation of device information, resulting in a more user-friendly management interface.

[0104] Figure 7 is a schematic diagram of the architecture of the unified management system for cross-platform intelligent devices provided in Embodiment 3 of the present invention. The management system 70 includes a memory 71 and a processor 72;

[0105] The memory 71 is used to store computer programs; the processor 72 is used to read the computer programs stored in the memory 71 and, when executing the programs, implement the unified management method for cross-platform smart devices as described in the foregoing embodiments.

[0106] Embodiment 4 of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a computer processor, is used to perform the technical solution of any method embodiment.

[0107] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or grid device, etc.) to execute the methods described in the various embodiments of the present invention.

[0108] It is worth noting that in the embodiments of the above-mentioned device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy distinction between each other and are not used to limit the scope of protection of the present invention.

[0109] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A unified management method for cross-platform smart devices, characterized in that, include: A platform adaptation layer is constructed, which integrates communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules; A separate daemon thread periodically scans all connected devices based on the platform adaptation layer; the raw device information of the scanned devices from different platforms is parsed and transformed into a preset unified device information data structure; device status change events are obtained based on the scanned device information. The device state change event is transmitted based on a publish-subscribe mechanism; wherein the published device state change event carries device information in the preset unified device information data structure.

2. The method according to claim 1, characterized in that, The method of transmitting the device state change event based on the publish-subscribe mechanism includes: for a published device state change event, obtaining the corresponding consumer module according to the mapping table between the event type and the listening function, and pushing the device state change event to the corresponding consumer module; wherein, the mapping table between the event type and the listening function is updated according to the subscription relationship.

3. The method according to claim 1, characterized in that, The process of analyzing the scanned device information to obtain device status change events includes: comparing the device information obtained from the current cycle scan with the device information obtained from the previous cycle scan to obtain device connection disconnection events.

4. The method according to claim 1, further comprising: Provides a configuration interface for the scanning cycle of connected devices.

5. The method according to claim 1, characterized in that, The preset unified device information data structure includes: cross-platform device identifier, preset unified format device model information, device market name, device status, and device unique identifier.

6. The method according to claim 1, characterized in that, The method further includes: when the device status change event is a new device event, adding the new device to the available resource pool, updating the task allocation strategy, and allocating test tasks to be executed; when the device status change event is a device disconnection event, clearing the task status of the disconnected device, reallocating the interrupted tasks, and updating the resource pool status.

7. The method according to claim 1, characterized in that, The process of analyzing the scanned device information to obtain device status change events includes: analyzing the device information, which has been converted into a preset unified device information data structure, to obtain device status change events.

8. A unified management device for cross-platform intelligent devices, characterized in that, include: A building module is used to build a platform adaptation layer, which integrates communication protocol modules for at least two platform devices to interact with the platform devices corresponding to the communication protocol modules; a scanning unit is used to periodically scan all connected devices based on the platform adaptation layer through an independent daemon thread. The unified information abstraction module is used to parse the raw device information of different platform devices obtained by scanning, and transform the parsed raw device information into a preset unified device information data structure. The event recognition module is used to analyze the scanned device information to obtain device status change events; An event-driven communication module is used to transmit the device state change event based on a publish-subscribe mechanism; wherein the published device state change event carries device information with the preset unified device information data structure.

9. A unified management system for cross-platform intelligent devices, characterized in that, It includes a memory and a processor; the memory is used to store computer programs; the processor is used to read the computer programs in the memory and, when executing the programs, implement the unified management method for cross-platform smart devices as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements a unified management method for cross-platform smart devices as described in any one of claims 1-7.

Images