A wireless terminal transit-free platform direct connection management system and method

Abstract

The present application relates to the technical field of internet access, in particular to a wireless terminal transfer-free platform direct connection management and control system and method, comprising the following modules: a terminal access analysis module receives terminal original collection messages and analyzes them into register data, a register model management module writes the register data into units corresponding to device identification, register address and data point identification, a platform direct connection communication module uploads the register data via an MQTT protocol and receives control instructions, an instruction routing execution module generates terminal control messages, and a local cache supplement transmission module caches collection data and control instructions when MQTT connection is disconnected or confirmed to be timed out. The present application, through the cooperation of analysis, register model management, platform direct connection communication and cache supplement transmission, makes platform configuration objects correspond to gateway data points, reduces transfer link data conversion and instruction forwarding, and enables data and instructions to have recovery processing basis during network anomalies.

Description

Technical Field

[0001] This invention relates to the field of Internet access technology, and in particular to a wireless terminal direct connection management system and method without relay platforms. Background Technology

[0002] In the field of Internet access technology, data collection, protocol encapsulation, address identification, status reporting, command issuance, storage and retrieval, and remote control are carried out around the network connection between terminal devices, access gateways, servers, and application platforms. Data such as current, temperature, and switch status generated by the terminal enters the access device via a wireless link, and is then transmitted to the platform-side program for display, recording, or linkage judgment by the network protocol. Among them, the traditional wireless terminal platform access management system and method refers to the access management process for wireless terminals such as switches, sockets, and thermostats in buildings. The wireless gateway receives terminal messages and writes them into registers or local data areas. The IO Server reads the gateway data according to the device address, register number, and point mapping relationship, converts it into data points that can be called by the platform configuration software, and the platform generates query or control commands based on the configuration point status, which are then forwarded to the corresponding terminals for execution by the IO Server and gateway.

[0003] In traditional building wireless terminal access management, the wireless gateway receives messages from switches, sockets, and thermostats and writes them to registers or local data areas. The IO Server then reads and converts the data points according to the device address, register number, and point mapping relationship. Platform configuration calls and control command transmission rely on relay links. Data interpretation locations are scattered. Engineering debugging requires repeated verification between the gateway register and the platform points. The number of point mapping configurations increases with the number of terminals. When the network or relay node is abnormal, there is a risk of interruption in data recording and command processing on the platform side. Summary of the Invention

[0004] The purpose of this invention is to provide a wireless terminal direct connection management system and method without relaying to a platform, which reduces the dependence on IO Server relay links during the access management of wireless terminals in buildings, establishes a direct corresponding processing relationship between wireless terminal data collection, gateway-side register data, platform configuration data points and platform control commands, and retains the continuous basis for data collection upload and control command processing when MQTT communication is abnormal.

[0005] To achieve the above objectives, the present invention provides a wireless terminal direct connection management and control system without relay, including a terminal access parsing module, a register model management module, a platform direct connection communication module, a local cache retransmission module, and an instruction routing execution module.

[0006] The terminal access parsing module receives raw acquisition messages from at least one wireless terminal, such as a switch, socket, or thermostat. These raw acquisition messages contain terminal type, device identifier, and acquisition fields. The terminal access parsing module parses the raw acquisition messages into register data based on the terminal type and acquisition fields. Further, after receiving the raw acquisition messages, the terminal access parsing module reads the device type field and device address field. When the device type field matches a terminal type record in a preset terminal type table and the device address field matches a registered device identifier, the terminal parsing rule for the wireless terminal is determined. When either the device type field or the device address field does not meet the matching conditions, the raw acquisition message is written to an abnormal message buffer. Further, the terminal access parsing module extracts the current field, temperature field, or switch status field from the acquisition fields according to the terminal parsing rules and associates the extracted field results with the device identifier of the wireless terminal. When the extracted field results meet the field length and data position requirements for the corresponding data type, register data is generated. When the extracted field results do not meet the field length or data position requirements, the abnormal message state of the raw acquisition message is maintained.

[0007] The register model management module is used to write register data into data units corresponding to device identifiers, register addresses, and data point identifiers. Further, when writing register data into the unified register data model, the register model management module retrieves the terminal registration table according to the device identifier to obtain the register address range and data point identifier set corresponding to the device identifier. When the data type corresponding to the acquisition field is within the field range of the data point identifier set, the register data is written into the corresponding data unit; when the data type corresponding to the acquisition field is not within the field range of the data point identifier set, a point mismatch record is generated. Further, after writing the register data, the register model management module correlates and updates the data value, update time, and terminal status flag in the data unit; when the data value corresponding to the same data point identifier is inconsistent with the data value of the previous update time, a status change record is formed; when the data value corresponding to the same data point identifier is consistent with the data value of the previous update time, the update time is retained and the original status flag is maintained.

[0008] The platform direct communication module is used to directly upload register data to the self-developed integration platform via the MQTT protocol and receive control commands issued by the self-developed integration platform. Further, when uploading register data via the MQTT protocol, the platform direct communication module generates a publishing topic according to the gateway identifier, device identifier, and data point identifier, and encapsulates the register data into a message payload containing the data point identifier, data value, and update time. When the self-developed integration platform returns a message confirmation result, it records the transmission completion status corresponding to the message confirmation result. If no message confirmation result is received within a preset confirmation time, the corresponding message payload is written to the pending transmission queue.

[0009] The instruction routing execution module is used to generate a terminal control message based on the target terminal identifier or target data point identifier in the control instruction. Further, after receiving the control instruction from the self-developed integration platform, the instruction routing execution module reads the target terminal identifier and target data point identifier from the control instruction, matches the target terminal identifier with the device identifier, and matches the target data point identifier with the data point identifier. When both the target terminal identifier and the target data point identifier meet the matching conditions, a terminal control message is generated and sent to the corresponding wireless terminal. When neither the target terminal identifier nor the target data point identifier meets the matching conditions, an instruction routing failure record is generated.

[0010] The local cache retransmission module is used to cache collected data and control commands when the MQTT connection is disconnected or the message acknowledgment times out, and to retransmit the collected data or continue processing the control commands in the order of the cached time after the connection is restored. Further, when the local cache retransmission module detects that the MQTT connection is disconnected or the message acknowledgment times out, it writes the unuploaded collected data into the retransmission queue and the unsent control commands into the execution queue. When the MQTT connection is restored and there are queue records in the retransmission queue, it reads the queue records in the order of the cached time and retransmits the corresponding message payload. Further, after retransmitting the corresponding message payload, the local cache retransmission module receives the message acknowledgment result returned by the self-developed integration platform. When the message acknowledgment result is "acknowledgment complete," it deletes the corresponding queue record from the retransmission queue. If no message acknowledgment result is received within the preset acknowledgment time, it retains the corresponding queue record and continues to read other queue records in the retransmission queue in the next order of the cached time.

[0011] This invention also provides a method for direct connection management and control of wireless terminals without relay platforms. This method is used to run the aforementioned direct connection management and control system for wireless terminals without relay platforms. The method includes: a wireless gateway receiving raw acquisition messages sent by a wireless terminal, the raw acquisition messages containing terminal type, device identifier, and acquisition fields; parsing the raw acquisition messages into register data based on the terminal type and acquisition fields, and writing the register data into a unified register data model corresponding to the device identifier, register address, and data point identifier; directly uploading the register data to a self-developed integration platform via the MQTT protocol, enabling the self-developed integration platform to call the corresponding data unit according to the data point identifier; receiving control commands issued by the self-developed integration platform, and generating terminal control messages based on the target terminal identifier or target data point identifier in the control commands; when the MQTT connection is disconnected or the message confirmation times out, caching the acquisition data and control commands; when the MQTT connection is restored and the cached records exist, retransmitting the acquisition data or continuing to process the control commands in the order of the cached time.

[0012] The beneficial effects of the technical solutions provided in the embodiments of the present invention include at least the following: The wireless gateway parses the original acquisition messages based on the terminal type and acquisition fields, enabling the data generated by switches, sockets, and thermostats to form register data on the gateway side. The register model management module writes the register data into the data unit corresponding to the device identifier, register address, and data point identifier, ensuring that the platform configuration call object is consistent with the gateway data model. The platform direct communication module directly transmits register data and receives control commands via the MQTT protocol, reducing the forwarding links of the IO Server. The command routing and execution module, in conjunction with the local cache retransmission module, processes the target terminal messages and cached records during abnormal periods, providing a clear basis for the retransmission of acquisition data and the continued processing of control commands. Attached Figure Description

[0013] 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 only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is the main flowchart for the direct connection and management of the wireless terminal without relay platform of the present invention; Figure 2 This is a partial flowchart of the terminal access parsing process of the present invention; Figure 3 This is a data flow diagram of the unified register data model of the present invention; Figure 4 This is a logic diagram of direct communication and command routing on the platform of this invention; Figure 5 This is a state transition diagram for local cache retransmission in this invention. Detailed Implementation

[0015] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0016] The following describes the feasible implementation methods of the wireless terminal direct connection management system and method without relay, in conjunction with the technical solutions described in this invention. This invention is applicable to building wireless terminal network access, platform direct communication, and remote management scenarios in the field of Internet access technology, particularly for handling Internet access data interaction between multiple types of terminals and a self-developed integrated platform via a wireless gateway. In subsequent embodiments, the wireless terminal refers to at least one of switches, sockets, and thermostats connected to the building management network; the original acquisition message refers to a message sent by the wireless terminal to the wireless gateway containing the terminal type, device identifier, and acquisition fields; the acquisition fields are used to carry current fields, temperature fields, or switch status fields; register data refers to data formed by the wireless gateway after parsing the original acquisition message and can be written into a unified register data model; a data unit refers to the data carrying location corresponding to the device identifier, register address, and data point identifier; and the control command refers to the command issued by the self-developed integrated platform to the wireless gateway via the MQTT protocol for generating terminal control messages. The MQTT protocol, as a data publishing and command subscription protocol for Internet access links, is used to support direct message interaction between the wireless gateway and the self-developed integrated platform. (Added figures follow.) Figure 1 The beginning is used to explain the system operation process, module collaboration relationships, data flow relationships, instruction routing relationships, and cache retransmission status relationships.

[0017] Please see Figures 1 to 5 This embodiment provides a wireless terminal direct-connection management system without relay, including a terminal access parsing module, a register model management module, a platform direct-connection communication module, a local cache retransmission module, and an instruction routing execution module. The terminal access parsing module receives raw acquisition messages sent by the wireless terminal. The register model management module writes the parsed register data into a unified register data model. The platform direct-connection communication module directly uploads the register data to a self-developed integration platform via the MQTT protocol and receives control instructions. The instruction routing execution module generates terminal control messages based on the control instructions. The local cache retransmission module saves the acquired data and control instructions when the MQTT connection is disconnected or the message acknowledgment times out, and continues processing according to the cache time order after the MQTT connection is restored. These modules can be configured within a wireless gateway or run with the support of the wireless gateway's processor, storage area, and communication interface. The modules collaborate according to the transmission relationship of raw acquisition messages, register data, message payloads, control instructions, and cache records. This collaborative relationship enables the wireless gateway to simultaneously assume the role of a processing node for terminal access, data standardization, platform direct connection, and abnormal caching in the Internet access link.

[0018] During system operation, the terminal access parsing module serves as the data entry point between the wireless terminal and the wireless gateway. After the raw acquisition packets sent by the wireless terminal enter the terminal access parsing module, the module first reads the device type and device address fields from the raw acquisition packets. The device type field identifies which category the wireless terminal belongs to—switch, socket, or thermostat—while the device address field establishes a correspondence with a registered device identifier. The terminal access parsing module matches the device type field with the terminal type record in the preset terminal type table, and simultaneously matches the device address field with the registered device identifier. When both the device type and device address fields match, the terminal access parsing module determines the terminal parsing rule corresponding to the wireless terminal and proceeds to field extraction processing. When either the device type or device address field does not meet the matching conditions, the terminal access parsing module does not continue register writing; instead, it writes the raw acquisition packet to the abnormal packet buffer, providing a basis for subsequent verification of the abnormal packet status. This data entry point is used to interface with the Internet access front-end packets of the building's wireless terminals, ensuring that terminal-side packets have a unified identification basis before entering the platform-side management process.

[0019] After determining the terminal parsing rules, the terminal access parsing module extracts current, temperature, or switch status fields from the collected fields according to these rules. The current field corresponds to a socket or other wireless terminal requiring current status data collection; the temperature field corresponds to the temperature collection status of a thermostat; and the switch status field corresponds to the on / off status of a switch or socket. The extracted field results are associated with the wireless terminal's device identifier to form the input data required for subsequent register writing. The terminal access parsing module verifies the field length and data position of the extracted field results. When the extracted field results meet the field length and data position requirements for the corresponding data type, the terminal access parsing module generates register data; when the extracted field results do not meet the field length or data position requirements, the terminal access parsing module maintains the abnormal message state of the original collected message. Through the above processing, the terminal type, device identifier, and collected fields in the original collected message are transformed into register data that can be received by the unified register data model. This register data serves as the data foundation recognizable by the Internet access platform, enabling the collected content from different wireless terminals to enter the same data expression system.

[0020] The register model management module receives register data output from the terminal access parsing module and writes it into the unified register data model. The unified register data model maintains the correspondence between device identifiers, register addresses, data point identifiers, and data units. Before writing register data, the register model management module searches the terminal registration table according to the device identifier to obtain the register address range and data point identifier set corresponding to the device identifier. The register address range limits the data storage range of the same wireless terminal in the unified register data model, and the data point identifier set limits the data points that the same wireless terminal can call from the self-developed integration platform. The register model management module compares the data type corresponding to the collected field with the field range of the data point identifier set. When the data type corresponding to the collected field is within the field range of the data point identifier set, the register model management module writes the register data into the corresponding data unit; when the data type corresponding to the collected field is not within the field range of the data point identifier set, the register model management module generates a point mismatch record, which is used to identify abnormal matching states between register data and platform configuration call relationships. The unified register data model is also used to establish callable data point boundaries on the Internet access platform side, enabling platform configuration objects to access data units within the wireless gateway based on data point identifiers.

[0021] After writing register data, the register model management module updates the data value, update time, and terminal status flag in the data unit. The data value originates from the register data, the update time is recorded by the wireless gateway when it receives or processes the register data, and the terminal status flag indicates the status change of the wireless terminal corresponding to the data unit. For the same data point identifier, the register model management module compares the currently written data value with the data value corresponding to the previous update time. When the data value corresponding to the same data point identifier is inconsistent with the data value at the previous update time, the register model management module creates a status change record; when the data value corresponding to the same data point identifier is consistent with the data value at the previous update time, the register model management module retains the update time and maintains the original status flag. The status change record serves as one of the bases for the subsequent platform direct communication module to organize message payloads and for the self-developed integration platform to perform configuration calls. This associated update process ensures that the data transmitted on the Internet access link includes not only the collected values ​​but also the time and status flag that the platform can use to determine the data update status.

[0022] The platform direct communication module establishes MQTT communication between the wireless gateway and the self-developed integration platform. When uploading register data, the platform direct communication module generates a publishing topic based on the gateway identifier, device identifier, and data point identifier, and encapsulates the register data into a message payload. The message payload includes the data point identifier, data value, and update time. The gateway identifier distinguishes different wireless gateways, the device identifier distinguishes different wireless terminals connected to the wireless gateway, and the data point identifier distinguishes data points such as current, temperature, or switch status. The self-developed integration platform obtains the register data in the message payload through the subscription or call relationship corresponding to the publishing topic. The platform configuration object maps to data units in the unified register data model according to the data point identifier. After sending the message payload, the platform direct communication module waits for a message confirmation result from the self-developed integration platform. When the self-developed integration platform returns a message confirmation result, the platform direct communication module records the transmission completion status corresponding to the message confirmation result. If no message confirmation result is received within the preset confirmation time, the platform direct communication module writes the corresponding message payload into the pending transmission queue. The platform's direct communication module thus forms a data publishing interface for the wireless gateway to the Internet access platform, enabling register data to enter the subscription or call chain of the self-developed integration platform without going through the IO Server.

[0023] When the self-developed integration platform needs to control wireless terminals, the platform's direct communication module receives control commands issued by the platform via the MQTT protocol. These control commands include a target terminal identifier and a target data point identifier. The platform's direct communication module then transmits the control commands to the command routing execution module. The command routing execution module reads the target terminal identifier and target data point identifier from the control commands and matches the target terminal identifier with the device identifier in the unified register data model, and matches the target data point identifier with the data point identifier in the unified register data model. When both the target terminal identifier and target data point identifier meet the matching conditions, the command routing execution module generates a terminal control message and sends it to the corresponding wireless terminal. When either the target terminal identifier or the target data point identifier does not meet the matching conditions, the command routing execution module generates a command routing failure record. The terminal control message is used to instruct the corresponding wireless terminal to perform switch status adjustments, socket on / off processing, or thermostat control processing according to the control commands. The command routing failure record is used to retain the processing status when the control commands cannot match the corresponding wireless terminal or the corresponding data point identifier. This instruction routing process is used to convert control requests from the Internet access platform into control messages that can be received by the wireless terminal, forming a direct control channel from the platform to the terminal.

[0024] The local cache retransmission module works in conjunction with the platform direct communication module and the instruction routing and execution module. When the local cache retransmission module detects an MQTT connection failure or message acknowledgment timeout, it writes the incompletely uploaded collected data into the pending retransmission queue and the incompletely issued control instructions into the pending execution queue. The pending retransmission queue carries collected data for which message payloads have been generated but message acknowledgments have not yet been received, while the pending execution queue carries control instructions issued by the self-developed integration platform but for which terminal control message processing has not yet been completed. Each queue record includes the cache time, data point identifier, data value or control instruction content, and processing status. The cache time is used to determine the order of subsequent retransmissions and continuation processing, and the processing status indicates whether the queue record is in the pending retransmission, pending execution, acknowledgment complete, or reserved for retry state. When fluctuations occur in the Internet access communication link, the local cache retransmission module is used to save data and instructions that have not yet completed platform interactions, so that the gateway-side records can serve as the basis for subsequent recovery processing.

[0025] When the MQTT connection is restored and there are queue records in the queue to be retransmitted, the local cache retransmission module reads the queue records in the order of cache time and retransmits the corresponding message payload. After retransmitting the corresponding message payload, the local cache retransmission module receives the message confirmation result returned by the self-developed integration platform. When the message confirmation result is "confirmation complete," the local cache retransmission module deletes the corresponding queue record from the queue to be retransmitted; if no message confirmation result is received within the preset confirmation time, the local cache retransmission module retains the corresponding queue record and continues to read other queue records in the queue to be retransmitted in the next order of cache time. By processing according to the order of cache time, the collected data that enters the queue to be retransmitted first is re-uploaded first, and the queue records that have not received message confirmation results will not block the reading and processing of other queue records. For control commands in the queue to be executed, when the MQTT connection is restored or the target wireless terminal meets the communication processing conditions, the local cache retransmission module hands over the control commands to the command routing execution module to continue reading the target terminal identifier and target data point identifier, and generates a terminal control message or command routing failure record according to the matching result. This retransmission and continuation processing mechanism enables the data collection and uploading and platform control command processing to continue according to the cached records after the Internet access link is restored.

[0026] Based on the above system, this embodiment also provides a method for direct connection management and control of wireless terminals without relay platforms. The method operates in a communication environment formed by a wireless gateway, a self-developed integrated platform, and a wireless terminal, and uses the Internet access communication link as the data interaction channel between the wireless gateway and the self-developed integrated platform. The main steps of the method include S1 to S5.

[0027] S1, the wireless gateway receives the raw acquisition message sent by the wireless terminal. The raw acquisition message contains the terminal type, device identifier, and acquisition fields. The wireless terminal includes at least one of a switch, socket, and thermostat. After receiving the raw acquisition message through the terminal access parsing module, the wireless gateway uses the device type field and device address field in the raw acquisition message as identification input. The device type field is used to determine the meaning of the corresponding acquisition fields, and the device address field is used to determine the wireless terminal corresponding to the raw acquisition message. This step is used to establish the initial data source for the terminal-side acquisition message to enter the Internet access control process.

[0028] S111, the terminal access parsing module reads the device type field and device address field from the original collection message. The device type field is matched against the preset terminal type table, and the device address field is matched against the registered device identifier.

[0029] S112, when the device type field matches the terminal type record in the preset terminal type table and the device address field matches the registered device identifier, the terminal access resolution module determines the terminal resolution rules for the wireless terminal. The terminal resolution rules limit the position and length of the current field, temperature field, or switch status field in the data acquisition fields.

[0030] S113, when the device type field or device address field does not meet the matching conditions, the terminal access parsing module writes the original collected message into the abnormal message buffer and maintains the abnormal message status of the original collected message. The abnormal message status is used to identify messages that have not entered the register data generation process.

[0031] S2, the wireless gateway parses the original acquisition message into register data based on the terminal type and acquisition fields, and writes the register data into a unified register data model corresponding to the device identifier, register address, and data point identifier. The terminal access parsing module extracts the current field, temperature field, or switch status field from the acquisition fields according to the terminal parsing rules, and associates the field extraction results with the device identifier of the wireless terminal. When the field extraction results meet the field length and data position requirements of the corresponding data type, the terminal access parsing module generates register data; when the field extraction results do not meet the field length or data position requirements, the terminal access parsing module maintains the abnormal message state of the original acquisition message. This step is used to complete the data standardization processing before the Internet access platform calls on the wireless gateway side.

[0032] S211, the register model management module retrieves the terminal registration table according to the device identifier to obtain the register address range and data point identifier set corresponding to the device identifier. The register address range serves as the address boundary for writing register data to the data unit, and the data point identifier set serves as the comparison object for determining whether the acquired field has a corresponding data point.

[0033] S212, when the data type corresponding to the acquired field is within the field range of the data point identifier set, the register model management module writes the register data into the corresponding data unit. A correspondence is established between the data unit and the device identifier, register address, and data point identifier.

[0034] S213, when the data type corresponding to the acquired field is not within the field range of the data point identifier set, the register model management module generates a point mismatch record. The point mismatch record is used to indicate that the data type corresponding to the acquired field is not received by the data point identifier set in the unified register data model.

[0035] S214, after writing data to the register, the register model management module updates the data value, update time, and terminal status flag in the data unit. When the data value corresponding to the same data point identifier is inconsistent with the data value of the previous update time, the register model management module forms a status change record; when the data value corresponding to the same data point identifier is consistent with the data value of the previous update time, the register model management module retains the update time and maintains the original status flag.

[0036] In step S3, the wireless gateway directly uploads register data to the self-developed integration platform via the MQTT protocol, enabling the platform to access the corresponding data unit based on the data point identifier. The platform's direct communication module generates a publishing topic based on the gateway identifier, device identifier, and data point identifier, and encapsulates the register data into a message payload containing the data point identifier, data value, and update time. This message payload is sent to the self-developed integration platform via MQTT communication, and the platform retrieves the data content of the corresponding data unit based on the publishing topic and data point identifier. This step allows the gateway-side register data to be directly provided to the platform configuration object for access via the internet access link.

[0037] S311: After sending the message payload, the platform direct communication module waits for a message confirmation result from the self-developed integration platform. When the message confirmation result is returned, the platform direct communication module records the transmission completion status. The transmission completion status is associated with the data point identifier and update time in the message payload.

[0038] S312, when no message confirmation result is received within the preset confirmation time, the platform direct communication module writes the corresponding message payload into the pending transmission queue. The queue record in the pending transmission queue includes at least the buffer time, data point identifier, data value, update time, and pending transmission status.

[0039] S4, the wireless gateway receives control commands from the self-developed integrated platform and generates a terminal control message based on the target terminal identifier or target data point identifier in the control commands. After receiving the control commands, the platform direct communication module transmits them to the command routing execution module. The command routing execution module reads the target terminal identifier and target data point identifier from the control commands, matches the target terminal identifier with the device identifier, and matches the target data point identifier with the data point identifier. This step converts the control commands from the Internet access platform side into routing processing results for the target wireless terminal within the wireless gateway.

[0040] S411, when both the target terminal identifier and the target data point identifier meet the matching conditions, the instruction routing execution module generates a terminal control message and sends it to the corresponding wireless terminal. The terminal control message is adapted to the terminal type of the corresponding wireless terminal, enabling the switch, socket, or thermostat to execute the control content corresponding to the control instruction.

[0041] S412, when the target terminal identifier or target data point identifier does not meet the matching conditions, the instruction routing execution module generates an instruction routing failure record. The instruction routing failure record is associated with the control instruction, the target terminal identifier, the target data point identifier, and the matching failure status.

[0042] S5, when the MQTT connection is lost or the message acknowledgment times out, the wireless gateway caches the collected data and control commands. When the MQTT connection is restored and the cached records exist, the wireless gateway retransmits the collected data or continues processing the control commands in the order of the cached time. The local cache retransmission module, upon detecting an MQTT connection loss or message acknowledgment timeout, writes the uncompleted collected data to the retransmission queue and the uncompleted control commands to the execution queue. The retransmission queue and the execution queue respectively store the cached time and processing status of the collected data and control commands. This step is used to handle the data and command backlog status when Internet access communication is abnormal.

[0043] S511: When the MQTT connection is restored and the queue for retransmission exists, the local cache retransmission module reads the queue records in the order of cache time and retransmits the corresponding message payload. After the corresponding message payload is retransmitted, the local cache retransmission module receives the message confirmation result returned by the self-developed integration platform.

[0044] S512, when the message confirmation result is confirmation complete, the local cache retransmission module deletes the corresponding queue record in the queue to be retransmitted; when no message confirmation result is received within the preset confirmation time, the local cache retransmission module retains the corresponding queue record and continues to read other queue records in the queue to be retransmitted according to the next cache time order.

[0045] S513: When control commands exist in the queue to be executed and the communication conditions are met, the local buffer retransmission module transmits the control commands to the command routing execution module. The command routing execution module continues to perform the matching process between the target terminal identifier and the target data point identifier. If the matching conditions are met, a terminal control message is generated; if the matching conditions are not met, a command routing failure record is generated.

[0046] In this embodiment, the terminal access parsing module, register model management module, platform direct communication module, local cache retransmission module, and instruction routing execution module form a closed loop from wireless terminal data input to platform configuration invocation and platform control instruction return to the wireless terminal. The original acquisition message is processed by the terminal access parsing module to form register data. The register data is written into a unified register data model by the register model management module. Data units in the unified register data model are uploaded to the self-developed integration platform via the platform direct communication module. Control instructions issued by the self-developed integration platform enter the instruction routing execution module via the platform direct communication module. The instruction routing execution module forms a terminal control message and sends it to the corresponding wireless terminal. The local cache retransmission module records the acquisition data, control instructions, and queue status when the MQTT connection is disconnected or the message confirmation times out. After the connection is restored, it retransmits the acquisition data or continues processing control instructions according to the cache time order. In the above closed loop, the input status, processing rules, intermediate data, output objects, and feedback basis all correspond to specific modules and specific data objects within the system. Through this closed loop, the wireless gateway can act as an Internet access node to carry out terminal data uploading, platform configuration invocation, platform instruction issuance, and anomaly recovery processing.

[0047] The module division, step sequence, field status, judgment conditions, queue records, and communication interaction relationships described in the above embodiments are used to illustrate the possible implementations of the present invention and should not limit the present invention to the specific embodiments listed. Without departing from the scope of the technical solutions described in this invention, any equivalent substitutions, equivalent modifications, equivalent combinations, sequence adjustments, module-to-module replacements, equivalent changes in field names, equivalent acceptance of the execution subject, or equivalent changes in the carrier form that can be conceived by those skilled in the art should fall within the scope of protection of this patent; however, they should not be extended to unclaimed topics, nor should the substantive correspondence of technical objects be changed through name changes. For equivalent changes in Internet access communication methods, platform subscription relationships, and gateway-side data point calling relationships, the determination of the correspondence of technical objects should be based on whether the direct connection between the wireless gateway and the platform, data standardization, and cache retransmission processing chain are still maintained.

Claims

1. A wireless terminal direct connection management and control system without relay platform, characterized in that, It includes a terminal access parsing module, a register model management module, a platform direct communication module, a local cache retransmission module, and an instruction routing and execution module; The terminal access parsing module receives raw acquisition messages sent by at least one wireless terminal among switches, sockets, and thermostats. The raw acquisition messages include terminal type, device identifier, and acquisition fields. The module parses the raw acquisition messages into register data based on the terminal type and acquisition fields. The register model management module writes the register data into the data unit corresponding to the device identifier, register address, and data point identifier. The platform direct communication module directly uploads the register data to the self-developed integration platform via the MQTT protocol and receives control commands issued by the self-developed integration platform. The instruction routing execution module generates a terminal control message based on the target terminal identifier or target data point identifier in the control instruction. The local cache retransmission module caches the collected data and control commands when the MQTT connection is disconnected or the message confirmation times out, and retransmits the collected data or continues to process the control commands in the order of the cache time after the connection is restored.

2. The wireless terminal direct connection management system without relay platform according to claim 1, characterized in that, After receiving the original collection message, the terminal access parsing module first reads the device type field and device address field in the original collection message. When the device type field matches the terminal type record in the preset terminal type table and the device address field matches the registered device identifier, the terminal parsing rule of the wireless terminal is determined. When the device type field or the device address field does not meet the matching conditions, the original collection message is written to the abnormal message buffer.

3. The wireless terminal direct connection management system without relay platform according to claim 2, characterized in that, The terminal access parsing module extracts the current field, temperature field, or switch status field from the collected fields according to the terminal parsing rules, and associates the field extraction results with the device identifier of the wireless terminal. When the field extraction results meet the field length and data position requirements of the corresponding data type, the register data is generated. When the field extraction results do not meet the field length or data position requirements, the abnormal message state of the original collected message is maintained.

4. The wireless terminal direct connection management system without relay platform according to claim 1, characterized in that, When the register model management module writes the register data into the unified register data model, it retrieves the terminal registration table according to the device identifier to obtain the register address range and data point identifier set corresponding to the device identifier. When the data type corresponding to the acquisition field is within the field range of the data point identifier set, the register data is written to the corresponding data unit; when the data type corresponding to the acquisition field is not within the field range of the data point identifier set, a point mismatch record is generated.

5. The wireless terminal direct connection management system without relay platform according to claim 4, characterized in that, After writing the register data, the register model management module will update the data value, update time, and terminal status flag in the data unit accordingly. When the data value corresponding to the same data point identifier is inconsistent with the data value of the previous update time, a status change record is formed. When the data value corresponding to the same data point identifier is consistent with the data value of the previous update time, the update time is retained and the original status flag is maintained.

6. The wireless terminal direct connection management system without relay platform according to claim 1, characterized in that, When the platform direct communication module uploads the register data via the MQTT protocol, it generates a publishing topic according to the gateway identifier, the device identifier, and the data point identifier, and encapsulates the register data into a message payload containing the data point identifier, data value, and update time. When the self-developed integration platform returns a message confirmation result, it records the transmission completion status corresponding to the message confirmation result. If the message confirmation result is not received within the preset confirmation time, the corresponding message payload is written into the queue to be retransmitted.

7. The wireless terminal direct connection management system without relay platform according to claim 1, characterized in that, After receiving the control command issued by the self-developed integration platform, the instruction routing execution module reads the target terminal identifier and the target data point identifier in the control command, and matches the target terminal identifier with the device identifier and the target data point identifier with the data point identifier. When both the target terminal identifier and the target data point identifier meet the matching conditions, a terminal control message is generated and sent to the corresponding wireless terminal. When neither the target terminal identifier nor the target data point identifier meets the matching conditions, a command routing failure record is generated.

8. The wireless terminal direct connection management system without relay platform according to claim 1, characterized in that, When the local cache retransmission module detects that the MQTT connection is disconnected or the message confirmation timeout occurs, it writes the unuploaded collected data into the retransmission queue and the unissued control command into the execution queue. When the MQTT connection is restored and there are queue records in the queue to be retransmitted, the queue records are read in order of cache time and the corresponding message payload is resent.

9. The wireless terminal direct connection management system without relay platform according to claim 8, characterized in that, After retransmitting the corresponding message payload, the local cache retransmission module receives the message confirmation result returned by the self-developed integration platform. When the message confirmation result indicates that the confirmation is complete, the corresponding queue record in the queue to be retransmitted is deleted. If the message confirmation result is not received within the preset confirmation time, the corresponding queue record is retained and the remaining queue records in the queue to be retransmitted are read in the order of the next cache time.

10. A method for direct connection and management of wireless terminals without a relay platform, used to operate the direct connection and management system for wireless terminals without a relay platform as defined in any one of claims 1 to 9, characterized in that, include: The wireless gateway receives the raw acquisition messages sent by the wireless terminal. The raw acquisition messages contain the terminal type, device identifier, and acquisition fields. Based on the terminal type and the acquisition field, the original acquisition message is parsed into register data, and the register data is written into a unified register data model corresponding to the device identifier, register address, and data point identifier. The register data is directly uploaded to the self-developed integration platform via the MQTT protocol, enabling the self-developed integration platform to call the corresponding data unit according to the data point identifier. Receive control commands issued by the self-developed integration platform, and generate terminal control messages based on the target terminal identifier or target data point identifier in the control commands; When the MQTT connection is lost or the message acknowledgment times out, the collected data and control commands are cached. When the MQTT connection is restored and the cached records exist, the collected data is retransmitted in the order of the cached time or the control commands are processed.

Images