System and method for smart device near and far field collaborative communication

Abstract

The application discloses a kind of system and method for near field and far field collaborative communication of intelligent equipment, and the collaborative communication method comprises the following steps: S1, virtual device creation and master standby control device marking;S2, group formation and master standby control device grouping;S3, cross-device communication control.The application multiplexes existing dual-mode intelligent equipment as a communication node, without additional deployment of gateway, single device has both "forwarding and control" functions, improves device utilization and system integration;"Master control device forced same group" ensures the basic access of near field devices, and the transparent instruction forwarding and data synchronization mechanism makes users not need to pay attention to the protocol type and physical location of the device, and the control of physical device can be realized through virtual device, which improves the usability of the system.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) communication technology, and in particular to a system and method for near-field and far-field cooperative communication of intelligent devices. Background Technology

[0002] With the development of IoT technology, various smart devices are widely used in smart factories, industrial monitoring, smart parks, and other scenarios. Due to application scenarios and cost limitations, these devices employ heterogeneous communication protocols: some devices only support near-field communication protocols (such as Bluetooth, ZigBee, and StarFlash) for short-range data transmission (such as workshop sensors); some devices support far-field communication protocols (such as Wi-Fi and Industrial Ethernet) and can be directly connected to cloud platforms (such as workshop controllers); and some devices have dual-mode communication capabilities, supporting both near-field and far-field protocols simultaneously (such as smart gateway machine tools and motor controllers with communication functions).

[0003] Currently, solutions for heterogeneous device communication in the Internet of Things (IoT) field mainly focus on three directions: First, enabling communication between devices using different protocols through protocol conversion gateways, such as the "A Protocol Conversion Gateway for Interoperability between IoT Devices and Its Deployment Method" disclosed in patent CN120416349A. Its core is to optimize the gateway's own structure and deployment efficiency, but it does not involve platform-side device virtualization and group collaboration. Second, constructing simulated images through device virtualization technology, such as the "An IoT Performance Testing Method and System" disclosed in patent CN113079061B. Its virtual devices are only used for performance testing and do not form real-time command interaction and data synchronization with physical devices. Third, optimizing device networking efficiency through group management technology, such as the "Networking Method, Device and System" disclosed in patent CN120916224A. It only optimizes the networking process for physical devices with the same protocol and does not support mixed group management of virtual devices and physical devices.

[0004] Therefore, the existing technology has the following shortcomings: Limited access for single-protocol near-field devices: Devices that only support near-field protocols such as Bluetooth (such as low-cost sensors) cannot be directly connected to the far-field platform and need to rely on gateway forwarding. However, existing gateway solutions only realize data pass-through and do not build a virtual mapping of the device on the platform side, which makes it impossible for the platform to manage and control such devices in a unified manner.

[0005] Insufficient heterogeneous device collaboration capability: Existing group management solutions only support networking of physical devices with the same protocol, and cannot include single-protocol near-field devices, dual-mode relay devices and far-field devices in the same group, resulting in obstacles to direct interoperability between cross-protocol devices. For example, Wi-Fi-enabled devices cannot directly send commands to Bluetooth-only devices.

[0006] Low operational transparency: In existing protocol conversion solutions, the platform's operation of near-field devices requires secondary configuration through the gateway, and users need to manually adapt the protocol format, which cannot achieve an operational experience of "no difference between virtual devices and physical devices", increasing the complexity of use. Summary of the Invention

[0007] To address the aforementioned issues, the present invention aims to provide an IoT heterogeneous device cross-protocol access and group interoperability system, which solves the problems of far-field access for single-protocol near-field devices, group collaboration and transparent operation of heterogeneous devices, and realizes a closed-loop process of "single-protocol device - dual-mode relay - platform virtual mirror - group interoperability".

[0008] This invention is implemented as follows: This invention provides a system for near-field and long-field collaborative communication of intelligent devices, comprising a physical device layer, a protocol conversion and control layer, a platform service layer, and a platform user interaction layer connected sequentially. The physical device layer provides the protocol conversion and control layer with single-protocol near-field devices, single-protocol far-field devices, and dual-mode intelligent devices for association and binding. The protocol conversion and control layer is integrated within the dual-mode intelligent device and includes a protocol conversion module, a local control module, a data caching and synchronization module, and an identifier binding module, respectively used to complete cross-protocol bidirectional conversion, local service control, data cache recovery in case of connection failure, and association binding between single-protocol near-field devices and dual-mode intelligent devices. The platform service layer includes a virtual device management module, a group management module, an instruction scheduling module, a data synchronization module, and a binding relationship management module, respectively used to complete virtual device management, hybrid group creation, intelligent instruction scheduling, cross-layer data synchronization, and device binding relationship maintenance. The platform user interaction layer provides a visual operation interface, receives user group creation, device addition, and instruction issuance operations, displays device status, and achieves seamless operation between virtual and physical devices.

[0009] The single-protocol near-field device has a built-in unique hardware identifier, and the dual-mode smart device supports both near-field and far-field protocols, possessing communication capabilities and local service execution capabilities.

[0010] The protocol conversion module is used to realize bidirectional protocol conversion between far-field and near-field protocols; the local control module is used to receive instructions issued by the platform or local trigger instructions to drive the dual-mode intelligent device to perform business actions; the data caching and synchronization module is used to cache the data of the single-protocol near-field device and the local operation log when the link is interrupted, and synchronize the cached data to the platform service layer after the link is restored; the identifier binding module is used to collect the unique hardware identifier of the single-protocol near-field device and the device identifier of the dual-mode intelligent device after establishing a connection with the single-protocol near-field device, generate an association relationship and upload it to the platform service layer.

[0011] The binding relationship management module is used to receive and store the binding association between single-protocol near-field devices and dual-mode smart devices; the virtual device management module is used to create a unique virtual device based on the unique hardware identifier of the single-protocol near-field device; the group management module is used to build a hybrid group; the instruction scheduling module is used to intelligently distribute instructions after receiving them from the user; and the data synchronization module is used to complete data synchronization between the virtual device and the corresponding physical device, synchronization of local operation logs of the dual-mode smart device, and synchronization of primary and backup status.

[0012] The present invention also discloses a method for near-field and far-field collaborative communication of intelligent devices, comprising the following steps: S1, virtual device creation and primary / backup control device marking; S2, group formation and primary / backup control device grouping; S3, cross-device communication control.

[0013] Step S1 specifically includes the following steps: S101: After the dual-mode smart device is powered on, it scans the surrounding single-protocol near-field devices through the near-field protocol. The identification binding module collects the unique hardware identifier of the single-protocol near-field device and its own device identifier, and uploads its own business capability information at the same time. S102: Dual-mode smart devices upload the association data of the unique hardware identifier of single-protocol near-field devices and their own device identifier to the platform service layer through the far-field protocol; S103: The platform service layer binding relationship management module receives the associated data and verifies whether the unique hardware identifier of the single protocol near-field device already exists. If it does not exist, the virtual device management module creates a unique virtual image based on the unique hardware identifier. If it already exists, the current dual-mode smart device identifier is associated with the existing virtual image. S104: The virtual device management module marks the primary and backup identities of associated dual-mode smart devices and displays the device type, primary / backup identifier, and business capabilities in the device list.

[0014] Step S2 specifically includes the following steps: S201: The user initiates a group creation request through the platform's user interaction layer, entering the group name and initial device; S202: The group management module queries the binding relationship management module for binding relationships; S203: Automatically add virtual devices and main control devices to the group, display the status and service capabilities of backup control devices, and allow users to choose whether to add backup control devices to the group; S204: Verify other devices added by the user, then create a group and send the group ID and all group member information to each group member. The platform user interaction layer distinguishes between primary and backup control devices through icons.

[0015] In step S203, the virtual image and the main control device are forced to be in the same group and cannot be deleted separately.

[0016] Step S3 specifically includes the following steps: S301: The user sends two commands to the group; S302: Instruction scheduling module splits instructions; S303: Dual-mode intelligent devices receive dual commands. The protocol conversion module forwards the commands to single-protocol near-field devices, or the local control module executes business actions and records operation logs. S304: The single-protocol near-field device returns data to the dual-mode smart device and uploads it to the platform. The data synchronization module of the platform service layer updates the virtual device data and the status of the dual-mode smart device. S305: The platform's user interaction layer displays the execution results.

[0017] In step S302, if the target of the instruction is a virtual device, the main control device is selected to forward the instruction; if the target of the instruction is a dual-mode smart device, the local control instruction is directly issued.

[0018] The beneficial effects of this invention are: (1) Equipment integration and cost optimization: Reuse existing dual-mode smart devices as communication nodes, eliminating the need for additional gateway deployment and reducing hardware investment; a single device has both "forwarding and control" functions, improving equipment utilization and system integration.

[0019] (2) Improved reliability and flexibility of control: "Forced grouping of main control equipment" ensures basic access of near-field equipment, and "optional backup control equipment" adapts to different coverage requirements; the local control and forwarding functions of dual-mode intelligent equipment are independent, and the failure of one function does not affect the operation of the other function. For example, if the forwarding fails, local dimming can still be performed.

[0020] (3) Reduce user operation complexity: The transparent instruction forwarding and data synchronization mechanism allows users to control physical devices through virtual devices without having to pay attention to the protocol type and physical location of the devices, thus improving the ease of use of the system.

[0021] (4) Enhance system reliability: The data caching function of the dual-mode relay device can protect data from loss when the link is interrupted and automatically synchronize after recovery, thus improving the system reliability in complex network environments. Attached Figure Description

[0022] Figure 1 This is a flowchart of the process of the present invention. Detailed Implementation

[0023] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Many specific details are set forth in the following description to provide a thorough understanding of the present invention. However, the present invention may also be implemented in other ways different from those described herein. Those skilled in the art can make similar extensions without departing from the spirit of the present invention. Therefore, the present invention is not limited to the specific embodiments disclosed below.

[0024] This invention provides a system for near-field and far-field collaborative communication of intelligent devices, comprising a physical device layer, a protocol conversion and control layer, a platform service layer, and a platform user interaction layer that are sequentially connected.

[0025] The physical device layer provides devices for association and binding to the protocol conversion and control layer. The physical device layer includes three types of devices: single-protocol near-field devices, single-protocol far-field devices, and dual-mode intelligent devices. Single-protocol near-field devices only support near-field protocols, such as Bluetooth, ZigBee, and StarFlash terminal sensing devices. Single-protocol near-field devices have a built-in unique hardware identifier, such as a Bluetooth MAC address or a unique device code, used for unique identification in scenarios with multiple dual-mode intelligent devices. Single-protocol far-field devices only support far-field protocols, such as Wi-Fi and industrial Ethernet remote interaction devices. Dual-mode intelligent devices are relay control devices that simultaneously support both near-field and far-field protocols, such as dual-mode intelligent device A and dual-mode intelligent device D. Among them, the dual-mode intelligent device is the core execution unit, possessing dual core capabilities: firstly, communication capabilities, integrating near-field protocol modules and far-field protocol modules, which can simultaneously establish near-field connections with single-protocol near-field devices and far-field connections with far-field platforms; secondly, business capabilities, with its own local operation control module, such as device start-up and shutdown, parameter adjustment and other execution functions, which can independently execute local commands or forward platform commands.

[0026] The protocol conversion and control layer is integrated into the dual-mode smart device, serving as a fusion layer of "communication forwarding + local control." It comprises four core modules: a protocol conversion module, a local control module, a data caching and synchronization module, and an identifier binding module. These modules are responsible for bidirectional cross-protocol conversion, local service control, data cache recovery in case of link failure, and association binding between single-protocol near-field devices and dual-mode smart devices. Specifically, the protocol conversion module enables bidirectional protocol conversion between far-field and near-field protocols (e.g., far-field protocol commands to near-field protocols, near-field device data to far-field protocols), facilitating cross-protocol interaction. The local control module receives commands from the platform or locally triggered control commands, directly driving the dual-mode smart device to perform actions without relying on forwarding. Examples include platform commands to adjust dual-mode smart device parameters from the far-field perspective and commands from single-protocol near-field devices to trigger actions in the dual-mode smart device. The data caching and synchronization module caches single-protocol near-field device data and local operation logs when the link between the dual-mode smart device and the far-field platform is interrupted. Once the link is restored, the cached data is synchronized to the platform service layer. The identifier binding module is used to collect the unique hardware identifier of the single-protocol near-field device and the device identifier of the dual-mode smart device after establishing a connection with the single-protocol near-field device, generate the association relationship and upload it to the platform service layer to establish the binding relationship between the "single-protocol near-field device and the dual-mode smart device".

[0027] The platform service layer includes a virtual device management module, a group management module, a command scheduling module, a data synchronization module, and a binding relationship management module. These modules are used to manage virtual devices, create hybrid groups, intelligently schedule commands, synchronize data across layers, and maintain device binding relationships, respectively. The virtual device management module creates a unique virtual image (also known as a virtual device, corresponding one-to-one with a physical device) based on the unique hardware identifier of a single-protocol near-field device. It associates all bound dual-mode smart devices and marks them as "primary control device" and "backup control device." The device bound first is the default primary control device, and manual switching between primary and backup control devices is supported to avoid virtual device duplication issues caused by multiple dual-mode smart device connections. The group management module creates hybrid groups, supporting the inclusion of dual-mode smart devices (physical), single-protocol far-field devices (physical), and single-protocol near-field devices (virtual devices) in the same group. It forces virtual devices to be in the same group as their "primary control device," ensuring the basic control link. "Backup control devices" can be manually selected to join or leave the group. The command scheduling module intelligently distributes user commands. If the target of the instruction is a virtual device, the instruction is forwarded through the main control device first; if the target of the instruction is a dual-mode intelligent device, the local control instruction is directly issued to the dual-mode intelligent device. The data synchronization module is used to complete data synchronization between virtual devices and their corresponding physical devices, as well as the synchronization of local operation logs and primary / backup status for dual-mode intelligent devices. The binding relationship management module is used to store the "single-protocol near-field device - primary control device / backup control device" relationship, supporting primary / backup control device switching and providing data support for group management.

[0028] The platform's user interaction layer provides a visual operation interface, through which users can create groups, add devices (physical or virtual), issue operation commands, and view device status, achieving seamless operation of both virtual and physical devices.

[0029] like Figure 1 As shown, the present invention also provides a method for intelligent device far-field and near-field cooperative communication, applied to the aforementioned system, including the following steps: S1, virtual device creation and primary / backup control device marking; S2, group formation and primary / backup control device grouping; S3, cross-device communication control. Each step is described in detail below.

[0030] S1. Virtual device creation and primary / standby control device marking, specifically including the following steps: S101: After the dual-mode intelligent device (A / D) is powered on, it scans the surrounding single-protocol near-field devices C through the near-field protocol. After establishing a stable connection, the identification binding module collects the unique hardware identifier of the single-protocol near-field device C and its own device identifier (such as A_001, D_001), and uploads its own business capability information (such as the local control functions supported by A_001). S102: The dual-mode intelligent device (A / D) uploads the associated data of "the unique hardware identifier of the single-protocol near-field device C and its own device identifier" to the platform service layer through the far-field protocol; S103: The binding relationship management module of the platform service layer receives the associated data and verifies whether the unique hardware identifier of the single protocol near-field device C already exists. If it does not exist, the virtual device management module creates a unique virtual image C_virtual based on the unique identifier and assigns a unique virtual device ID. If it already exists, the current dual-mode smart device identifier is directly associated with the existing virtual image C_virtual, without creating a virtual device again. S104: The virtual device management module initializes the virtual image C_virtual to "online", marks the primary and backup identities of the associated dual-mode smart devices, and defaults to "primary control device" for the first binding and "backup control device" thereafter. The device list displays "device type, primary / backup identifier and business capabilities", and supports manual switching between primary and backup.

[0031] S2. Group setup and primary / backup control device grouping, specifically including the following steps: S201: Users initiate a group creation request through the platform's user interaction layer, enter the group name and initial device, and can choose a virtual device or a main control device with a single protocol near-field device. S202: The group management module queries the binding relationship management module for binding relationships. If a virtual device is selected, the main control device and the backup control device are found; if the main control device is selected, the corresponding virtual image and the backup control device are found. S203: Automatically add "virtual device and main control device" to the group. Both are forced to be in the same group and cannot be deleted separately. A "standby control device selection window" pops up, displaying the status (signal strength, load rate) and service capabilities of the standby control device. Users can choose whether to add the standby control device to the group. S204: Verify other devices added by the user, such as single-protocol far-field devices, then create a group and send the group ID and all group member information (including virtual devices) to each group member; the platform user interaction layer distinguishes between primary and backup control devices using icons. In the platform user interaction interface, primary and backup control devices are visually distinguished using different icons. This embodiment uses a dedicated style to identify the two types of devices: the primary control device is marked with a red border and the text "Primary Control"; the backup control device is marked with a blue border and the text "Backup Control". At the same time, the interface provides permission prompts, clarifying that the primary control device and the virtual device are forcibly bound to the same group and do not support individual deletion operations. After completing the above configuration, the device group can be successfully created.

[0032] S3. Cross-device communication control, taking "platform control of single-protocol near-field device data acquisition and adjustment of main control device local parameters" as an example, specifically includes the following steps: S301: The user sends two commands to the group through the platform's user interaction layer: ① Sends the "Data Acquisition Parameter Setting" command to the virtual device (the actual device is C); ② Sends the "Local Parameter Adjustment" command to the main control device A; S302: Command scheduling module splits commands: If the command target is a virtual device, it queries the main control device A (strong signal, low load) and the backup control device D, and selects the main control device A to forward the command; if the command target is a dual-mode intelligent device, it directly issues the local control command. S303: The main control device A receives dual commands: it converts the "collection parameter command" into a near-field protocol format through the protocol conversion module and forwards it to the single-protocol near-field device C; or it executes parameter adjustment actions through the local control module and records the operation log. S304: Single-protocol near-field device C performs data acquisition and returns the acquired data to the main control device A. The main control device A uploads the acquired data and its own parameter adjustment log of single-protocol near-field device C to the platform through the far-field protocol. The data synchronization module of the platform service layer updates the virtual device data and the status of the main control device A. S305: The platform user interaction layer displays "Virtual device parameters have been updated, and the parameters of the main control device A have been adjusted." It indicates that the device currently controlling the single-protocol near-field device is the main control device A. If the main control device A fails, it will automatically switch to the backup control device D to forward the instructions / data of the single-protocol near-field device. At the same time, the backup control device D can still perform local control functions without affecting the system operation.

[0033] The invention will now be described in detail with specific embodiments, using the "Smart Factory Workshop No. 1 Monitoring and Control Scenario" as an example. The scenario requires a machine tool vibration sensor C and a motor temperature sensor E that only support Bluetooth communication. The machine tool vibration sensor C is deployed on the body of machine tool No. 1, and the motor temperature sensor E is deployed on the motor end of machine tool No. 1. Both the machine tool vibration sensor C and the motor temperature sensor E are single-protocol near-field devices and need to be connected to the workshop's industrial Ethernet platform. The workshop also deploys a workshop monitoring host B located in the central control room, a Wi-Fi + Bluetooth dual-mode intelligent controller A for machine tool No. 1, and a Wi-Fi + Bluetooth dual-mode intelligent motor driver D for machine tool No. 2 to achieve group collaborative management.

[0034] This embodiment aims to achieve collaborative management of the aforementioned heterogeneous devices, with the following expected technical effects: The administrator can query vibration data from machine tool vibration sensor C and temperature data from motor temperature sensor E through the workshop monitoring host B, and can issue control commands to dual-mode intelligent device A to adjust the machine tool speed; when dual-mode intelligent device A malfunctions, dual-mode intelligent device D automatically takes over the communication forwarding between machine tool vibration sensor C and motor temperature sensor E, and dual-mode intelligent device D itself can still independently execute the start / stop control of the second machine tool motor without the need for additional industrial gateway equipment. The specific implementation steps are detailed below: (1) Device access and virtual device creation: Step 1: Power on dual-mode intelligent devices A (machine tool controller No. 1) and D (machine tool driver No. 2), connect to the workshop Ethernet, and report their unique device identifiers and their own business capability information. Dual-mode intelligent device A has speed regulation capabilities, and dual-mode intelligent device D has motor start / stop capabilities.

[0035] Step 2: The dual-mode intelligent device A scans and establishes a connection with the machine tool vibration sensor C and the motor temperature sensor E, and collects the MAC address of the machine tool vibration sensor C, the code of the motor temperature sensor E and its own identifier and uploads them to the platform service layer.

[0036] Step 3: The platform service layer receives the associated reported data, creates a virtual mirror device C_V001 corresponding to the MAC address of the machine tool vibration sensor C, and a virtual mirror device E_V001 corresponding to the device code of the motor temperature sensor E. The dual-mode intelligent device A is then marked as the master control device for both virtual devices. After a 10-second interval, the dual-mode intelligent device D scans and detects the machine tool vibration sensor C and the motor temperature sensor E, completing the connection. It also reports the device association information to the platform. The platform does not create virtual mirrors again, but only marks the dual-mode intelligent device D as the backup control device corresponding to C_V001 and E_V001.

[0037] After completing the above process, the device association status displayed in the platform device list is as follows: C_V001 (online), associated with A_001 (main control - machine tool controller) and D_001 (standby control - driver); E_V001 (online), associated with A_001 (main control) and D_001 (standby control).

[0038] (2) Group formation: Step 1: The administrator logs into the platform's web interface, creates the "Machine Tool Group No. 1 Monitoring Group", and selects virtual devices C_V001 and E_V001 as the initial members of the group.

[0039] Step 2: According to the rule that virtual devices must be in the same group as the main control device, automatically add the main control device A_001 to the group; at the same time, a backup control device selection window pops up on the interface, showing the device status and service capabilities of the backup control device D_001. After the administrator confirms, the backup control device D_001 is added to the group.

[0040] Step 3: The administrator continues to add workshop monitoring host B_001. After the platform verification is passed, the group creation is completed.

[0041] The final group members include virtual device C_V001, virtual device E_V001, physical device A_001, physical device D_001, and physical device B_001. The interface is marked with primary and backup identifiers, and it also prompts that A_001 is the primary control device that is forcibly bound to the virtual device and cannot be deleted from the group individually.

[0042] (3) Cross-device communication and hybrid control: Normal working scenario: The administrator issues two parallel commands: the first command sets the sampling period of machine tool vibration sensor C to 1 second, and the second command sets the output speed of dual-mode intelligent device A to 2000 rpm. The command scheduling module of the platform service layer processes these commands separately: for the sampling command pointing to virtual device C_V001, the command scheduling module queries and finds that the current main control device is A_001, and sends the command to A_001 for forwarding; for the speed adjustment command pointing to physical device A_001, the local control command is directly sent to A_001.

[0043] After receiving two commands, the dual-mode intelligent device A firstly calls the local control module to execute the speed adjustment action, and secondly sends the sampling cycle command to the machine tool vibration sensor C. The machine tool vibration sensor C and the motor temperature sensor E collect the monitoring data and transmit it back to the dual-mode intelligent device A. The dual-mode intelligent device A then uploads the data collected by the single-protocol near-field device, along with its own operation log, to the platform via the far-field protocol. The platform's data synchronization module updates the virtual device's data status, and the web interface renders and displays the vibration and temperature monitoring curves in real time.

[0044] When the vibration data reported by the machine tool vibration sensor C reaches the 0.6g threshold, an over-limit judgment is triggered. The platform automatically sends a control command to the dual-mode intelligent device A to stop operation, and at the same time outputs an alarm message on the platform side.

[0045] Equipment Failure Scenario: When the power supply to the dual-mode intelligent device A is disconnected, the platform detects a timeout in the A_001 heartbeat within 5 seconds, determining a device failure. The platform automatically switches the backup control device D_001 to become the new primary control device. The backup control device D_001 then handles the command forwarding and data transmission for the machine tool vibration sensor C and the motor temperature sensor E. During this period, the administrator can still issue start / stop commands for the second machine tool motor to the backup control device D_001. These commands are directly sent to the local control module of the backup control device D_001 for execution. The motor control functions of the dual-mode intelligent device D operate independently and will not interfere with the data monitoring and forwarding links of the machine tool vibration sensor C and the motor temperature sensor E.

[0046] This invention adopts a dual-mode intelligent device "communication + control" fusion mechanism: the dual-mode intelligent device has both near-field / far-field communication capabilities and local control capabilities, and can realize the dual functions of "data forwarding and service execution" without the need for an additional gateway, solving the redundancy problem of traditional relays that can only forward data and require supporting control equipment; by associating multiple dual-mode devices with primary and backup identifiers, it not only ensures the reliability of near-field device access, but also realizes the independent scheduling of the dual-mode device's own control functions.

[0047] This invention uses a hierarchical binding and group management technology for primary and backup control devices: the binding relationship management module marks "primary / backup control devices", the group management module only forces virtual devices to be in the same group as the primary control device (ensuring basic access and control links), and the backup control device can be added as needed, taking into account both reliability and flexibility; the binding relationship and group permissions are automatically synchronized when switching between primary and backup, which is different from the limitation of traditional solutions that can only forward to a single device.

[0048] This invention employs a transparent command forwarding and data synchronization mechanism: near-field devices are displayed as virtual devices on the platform, and the platform automatically completes the protocol conversion and relay forwarding of commands. Commands issued by users to the virtual devices can be directly synchronized to the physical devices, and the data of the physical devices can also be updated to the virtual devices in real time, achieving an operational experience where "virtual devices and physical devices are indistinguishable".

[0049] While the present invention discloses preferred embodiments to achieve the above objectives, these are not intended to limit the structural features of the invention. Anyone skilled in the art should know that any easily conceived variations or modifications are possible within the technical spirit of the present invention and are all covered by the claims of the present invention.

Claims

1. A system for near-field and long-field cooperative communication of intelligent devices, characterized in that, It includes the physical device layer, protocol conversion and control layer, platform service layer, and platform user interaction layer, which are connected sequentially; The physical device layer is used to provide the protocol conversion and control layer with single-protocol near-field devices, single-protocol far-field devices, and dual-mode smart devices for association and binding; The protocol conversion and control layer is integrated inside the dual-mode smart device, including a protocol conversion module, a local control module, a data caching and synchronization module, and an identifier binding module, which are respectively used to complete cross-protocol bidirectional conversion, local business control, data cache recovery after disconnection, and association binding between single-protocol near-field device and dual-mode smart device; The platform service layer includes a virtual device management module, a group management module, an instruction scheduling module, a data synchronization module, and a binding relationship management module, which are respectively used to complete virtual device management, hybrid group creation, intelligent instruction scheduling, cross-layer data synchronization, and device binding relationship maintenance; The platform's user interaction layer provides a visual operation interface, receives user group creation, device addition, and command issuance operations, displays device status, and enables seamless operation of virtual and physical devices.

2. The system for intelligent device far-field and near-field cooperative communication according to claim 1, characterized in that, The single-protocol near-field device has a built-in unique hardware identifier, and the dual-mode smart device supports both near-field and far-field protocols, possessing communication capabilities and local service execution capabilities.

3. The system for intelligent device far-field and near-field cooperative communication according to claim 1, characterized in that, The protocol conversion module is used to realize bidirectional protocol conversion between far-field and near-field protocols; the local control module is used to receive instructions issued by the platform or local trigger instructions to drive the dual-mode intelligent device to perform business actions; the data caching and synchronization module is used to cache single-protocol near-field device data and local operation logs when the link is interrupted, and synchronize the cached data to the platform service layer after the link is restored; the identifier binding module is used to collect the unique hardware identifier of the single-protocol near-field device and the device identifier of the dual-mode intelligent device after establishing a connection with the single-protocol near-field device, generate an association relationship and upload it to the platform service layer.

4. The system for intelligent device far-field and near-field cooperative communication according to claim 1, characterized in that, The binding relationship management module is used to receive and store the binding association between single-protocol near-field devices and dual-mode smart devices; the virtual device management module is used to create a unique virtual device based on the unique hardware identifier of the single-protocol near-field device; the group management module is used to construct a hybrid group. The instruction scheduling module is used to intelligently distribute user instructions; the data synchronization module is used to complete data synchronization between virtual devices and corresponding physical devices, synchronization of local operation logs of dual-mode intelligent devices, and synchronization of primary and backup status.

5. A method for near-field and far-field cooperative communication of intelligent devices, based on the system for near-field and far-field cooperative communication of intelligent devices according to any one of claims 1-4, characterized in that, Includes the following steps: S1. Virtual device creation and primary / backup control device marking; S2, Group formation and primary / backup control device grouping; S3, Cross-device communication control.

6. The method for near-field and far-field cooperative communication of intelligent devices according to claim 5, characterized in that, Step S1 specifically includes the following steps: S101: After the dual-mode smart device is powered on, it scans the surrounding single-protocol near-field devices through the near-field protocol. The identification binding module collects the unique hardware identifier of the single-protocol near-field device and its own device identifier, and uploads its own business capability information at the same time. S102: Dual-mode smart devices upload the association data of the unique hardware identifier of single-protocol near-field devices and their own device identifier to the platform service layer through the far-field protocol; S103: The binding relationship management module of the platform service layer receives the associated data and verifies whether the unique hardware identifier of the single protocol near-field device already exists. If it does not exist, the virtual device management module creates a unique virtual image based on the unique hardware identifier. If it already exists, the current dual-mode smart device identifier is associated with the existing virtual image. S104: The virtual device management module marks the primary and backup identities of associated dual-mode smart devices and displays the device type, primary / backup identifier, and business capabilities in the device list.

7. The method for near-field and far-field cooperative communication of intelligent devices according to claim 5, characterized in that, Step S2 specifically includes the following steps: S201: The user initiates a group creation request through the platform's user interaction layer, entering the group name and initial device; S202: The group management module queries the binding relationship management module for binding relationships; S203: Automatically add virtual devices and main control devices to the group, display the status and service capabilities of backup control devices, and allow users to choose whether to add backup control devices to the group; S204: Verify other devices added by the user, then create a group and send the group ID and all group member information to each group member. The platform user interaction layer distinguishes between primary and backup control devices through icons.

8. The method for near-field and far-field cooperative communication of intelligent devices according to claim 7, characterized in that, In step S203, the virtual image and the main control device are forced to be in the same group and cannot be deleted separately.

9. The method for near-field and far-field cooperative communication of intelligent devices according to claim 5, characterized in that, Step S3 specifically includes the following steps: S301: The user sends two commands to the group; S302: Instruction scheduling module splits instructions; S303: Dual-mode intelligent devices receive dual commands. The protocol conversion module forwards the commands to single-protocol near-field devices, or the local control module executes business actions and records operation logs. S304: The single-protocol near-field device returns data to the dual-mode smart device and uploads it to the platform. The data synchronization module of the platform service layer updates the virtual device data and the status of the dual-mode smart device. S305: The platform's user interaction layer displays the execution results.

10. The method for near-field and far-field cooperative communication of intelligent devices according to claim 9, characterized in that, In step S302, if the target of the instruction is a virtual device, the main control device is selected to forward the instruction; if the target of the instruction is a dual-mode smart device, the local control instruction is directly issued.

Images