CN106899452B - Message circulation processing Internet of things terminal debugging method based on XM2M protocol - Google Patents
Message circulation processing Internet of things terminal debugging method based on XM2M protocol Download PDFInfo
- Publication number
- CN106899452B CN106899452B CN201710101437.8A CN201710101437A CN106899452B CN 106899452 B CN106899452 B CN 106899452B CN 201710101437 A CN201710101437 A CN 201710101437A CN 106899452 B CN106899452 B CN 106899452B
- Authority
- CN
- China
- Prior art keywords
- message
- protocol
- terminal
- type
- xm2m
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/14—Arrangements for monitoring or testing data switching networks using software, i.e. software packages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/18—Protocol analysers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method for debugging an Internet of things terminal based on message circulation processing of an XM2M protocol, which comprises the steps of firstly setting serial port parameters (serial port number, data bit, check bit, baud rate and stop bit) and opening serial port connection; the Internet of things debugging platform acquires a data packet sent by a terminal and then puts the data packet into a message buffer area, a platform background acquires a complete data packet from the message buffer area according to message head and tail identification, a factory mode is utilized to instantiate a message object, the message is verified and analyzed according to an XM2M protocol, the analyzed message is put into a message queue, and a platform foreground respectively displays data in a state synchronization, debugging information and parameter setting area according to the message type. The method can monitor the state of the terminal visually and quickly, change the terminal parameters quickly and accurately and achieve the aim of quickly responding to the market.
Description
Technical Field
The invention relates to the technical field of communication, in particular to an Internet of things terminal debugging method based on message circulation processing of XM2M protocol.
Background
With the continuous optimization and promotion of the ecological circle of the internet of things, the internet of things equipment is widely applied to the life and manufacturing industry, the terminals of the ecological system of the internet of things are networking equipment which can be sensed and started at different complexity degrees and are the junction for realizing the integration of industrialization and informatization, and the debugging of the terminals of the internet of things is particularly important. In the process of debugging the terminal of the internet of things of the engineering machinery, debugging personnel do not have an intuitive platform capable of checking the terminal state and various parameters, and cannot monitor the positioning state, the network communication state, the system state and the like of the terminal in real time; for each parameter of the terminal: the settings of the terminal unique number, the SIM card number, the version number, the IP, the AT instruction and the like need to learn the terminal communication protocol first, so that the learning cost is high, and the accuracy is difficult to check; the terminal debugging process cannot be recorded, and later analysis and improvement are not facilitated. How to realize intuitive, rapid and accurate debugging of the internet of things terminal to respond to the increasing market demands?
Disclosure of Invention
In view of the above problems, the present invention aims to provide a method for debugging an internet of things terminal by cyclically processing messages of an XM2M protocol, which can intuitively and quickly monitor a terminal state, quickly and accurately change terminal parameters, and achieve the purpose of quickly responding to the market.
The invention is realized according to the following technical scheme:
an Internet of things terminal debugging method based on message cycle processing of XM2M protocol comprises the following steps,
the method comprises the following steps: implementing a message parsing method;
step two: serial port configuration;
step three: receiving a message;
step four: analyzing the message;
step five: and displaying the message.
Preferably, the method comprises in particular the steps of,
the method comprises the following steps: according to XM2M protocol types, realizing message analysis method of each protocol type;
step two: setting serial port information including serial port number, data bit, check bit, baud rate and stop bit, and opening serial port connection;
step three: receiving a message sent by a lower computer and putting the message into a message buffer area;
step four: intercepting a complete message from a message buffer area according to an XM2M protocol, instantiating a message object in a factory mode, analyzing a message header and a message body of the message in the instantiation process, and putting the analyzed message object into a message queue;
step five: and dynamically displaying the analyzed message on the foreground of the platform in an asynchronous multithreading mode.
Preferably, the fourth step is specifically:
step a: storing the receiving terminal data packet into a message buffer area;
step b: acquiring a complete message from a message buffer area;
step c: splitting a message into a message header, a message body and a check bit;
step d: factory mode instantiates a message object;
step e: and analyzing the message and putting the message into a message queue.
Preferably, the step b specifically comprises: the system background obtains a complete message from the message buffer according to the message start mark and the message end mark, the start character of the protocol is 7B7B namely two braces "{ {", the end character of the protocol is 7D7D namely two braces "} }", and the start character end character and the escape character in the message are removed, so that the complete message can be obtained.
Preferably, the step c specifically comprises: the first byte to the thirteenth byte of the message are message header parts; the last byte is a check word; and removing the message header and the check word, wherein the rest part is the message body, and after the message body is obtained, the transfer character needs to be removed.
Preferably, the method for removing the transition character comprises the following steps: traversing the message body, replacing 1B1B7B7B with 7B7B, replacing 1B1B7D7D with 7D7D, and replacing 1B1B with 0000, namely the accurate message body.
Preferably, the step d specifically comprises: intercepting the first byte of the message header, interpreting according to the related concept of XM2M protocol, obtaining the message type, and instantiating the message object according to the message type.
Preferably, the step five specific method is as follows:
firstly, after a terminal is connected with a platform, the terminal can send messages to the platform according to a certain frequency, and received information texts are directly displayed in a debugging information area;
secondly, traversing the message queue to obtain the message type;
then, the message type is judged: if the data transmission type is the data transmission type, the data is displayed in the state information area; if the parameter setting type is the parameter setting type, the parameter setting type is displayed in the parameter setting area.
The invention has the beneficial effects that:
1. the Internet of things terminal debugging main body framework based on message circulation processing of the XM2M protocol is stable, when the protocol is changed, only a changed message analysis method needs to be modified, and a system main body does not need to be repeatedly modified, compiled and issued, so that the system stability is enhanced;
2. the protocol covers a plurality of setting options of common function parameters, reduces the parameter configuration difficulty of the function test, does not need to frequently modify the test program, and can even use the program of a formal version for testing;
3. and a message circulation processing mechanism is adopted, so that packet loss and message congestion are avoided.
Drawings
FIG. 1 is an overall flow chart of information processing of the present invention;
FIG. 2 is a flow chart of dynamic data parsing according to the present invention;
FIG. 3 is a foreground dynamic display flow chart of the present invention.
Detailed Description
The invention is further described by the following specific embodiments with reference to the attached drawings. Some of which are explained herein. M2M: an Internet of things communication protocol; a message buffer area: serial port data are stacked in sequence, and the serial port data can be complete messages or incomplete messages; message queue: and (4) checking the analyzed complete message through the XM2M protocol.
XM2M protocol-related concept interpretation
The protocol is mainly aimed at a lightweight protocol facing terminal management data and small data volume service data between the M2M terminal equipment and the M2M platform. The protocol comprises three parts: message header, message body and check word. The message header carries message type information, and the message types mainly include the following:
1.0X00-MESSAGEACK general message response,
2.0X01-CONN _ REQ connection request,
3.0X02-CONN _ RESP connect response,
4.0X03-PUSH _ DATA transmission,
5.0X04-ALERT reminder,
6.0X05-CMD _ REQ command request,
7.0X06-CMD _ RESP command response,
8.0X07-PING _ REQ heartbeat request,
OX07-PING _ RESP heartbeat response,
10.0X09-DISCONNECT DISCONNECTs,
11.0X0A-UPDATE upgrade notification,
12.0X0B-UPDATE-RESP upgrade response.
Message processing overall flow (as shown in figure 1)
E1. And according to the XM2M protocol type, realizing the message analysis method of each protocol type.
E2. Serial port information including serial port number, data bit, check bit, baud rate and stop bit is set, and serial port connection is opened.
E3. And receiving the message sent by the lower computer and putting the message into a message buffer area.
E4. Intercepting a complete message from a message buffer area according to an XM2M protocol, instantiating a message object in a factory mode, analyzing a message header and a message body in the instantiation process (a specific dynamic analysis scheme is shown as the third step in the specification of data dynamic analysis), and placing the analyzed message object into a message queue.
E5. And dynamically displaying the analyzed message on the foreground of the platform in an asynchronous multithreading mode (the specific dynamic display scheme is shown as the following step in the specification of 'four-foreground dynamic display').
Thirdly, the data dynamic analysis steps (as shown in fig. 2)
E1. And obtaining the message from the terminal and putting the message into a message buffer area.
E2. The system background acquires a complete message from a message buffer RecByteQueue according to a message start mark and an end mark, wherein a start character of the protocol is 7B7B namely two braces, { { ", an end character of the protocol is 7D7D namely two braces, }, and the complete message can be acquired by removing the start character end character and an escape character in the message.
E3. Splitting a message header MsgHeadData, a message body Msgbody and a check word CheckByte. The first Byte (Byte) to the thirteenth Byte (Byte) of the message are the header part of the message; the last Byte (Byte) is a check word; removing the message header and the check word, wherein the rest part is the message body, and after the message body is obtained, the transfer character ESC is removed by the method comprising the following steps: traversing the message body, replacing 1B1B7B7B with 7B7B, replacing 1B1B7D7D with 7D7D, and replacing 1B1B with 0000, namely the accurate message body.
E4. And instantiating a Message object Message through a factory class MsgController according to the Message type. Intercepting the first byte of the message header, according to the concept explanation related to the first part XM2M protocol, the message type can be obtained, and the message object is instantiated according to the message type.
E5. And analyzing the message header and the message body of the message, and putting the message into a message queue Msgbuffer after the analysis is finished.
The message header comprises a message type, a product unique number, an identification, a message serial number and residual length information.
The parsing of the message body differs according to the type of the message. The message body structure of 12 message types is as follows:
1. the message body of the general message response contains the message serial number of the responded message, the type of the responded message and the processing result.
2. The message body of the connection request message covers the protocol name, the protocol version, the connection identifier and the authentication information.
3. The message body of the connection response message covers the connection return code: connection success, connection rejected (unsupported protocol version), connection rejected (authentication failure), reserved value.
4. The data transmission message is a bidirectional general data transmission message. The message body part is a message body of a specified data structure and comprises a data type and a data content. The data type comprises a data type length and a data type, and the data content comprises a data content length and a data content. The data content includes the following:
when the data type is SS terminal basic state data synchronization, the data content is data content length, state synchronization TLV number and necessary TLV;
when the data type is uploading the working parameters of the WP device, the data content is data content length, the number of the state synchronization TLVs and necessary TLVs, and the following TLVs at least comprise one of: CAN bus data, other bus data, CAN bus data and a working time period statistical table.
And when the data type is LE terminal and the log of the equipment is transmitted, the data content is data content length, log type and log file.
And the data content is the data content length and the upgrading file when the data type is the UT upgrading file transmission.
When the data type is GT general file transmission, the data content is the data content length and the file content.
5. The message body of the reminding message comprises a reminding type and a reminding content. The reminding type comprises a reminding type length + BATTERY, and the reminding content comprises a reminding content length and a reminding content.
6. The message body of the command request message comprises a command type and command content. The command type comprises a command type length + a command type, and the command content comprises a command content length and a command content.
The command types comprise PW setting parameter commands, PR reading parameter commands, LT position tracking commands, WP inquiry/attention device current working parameter commands, QC remote control commands, LE log export commands and AT instruction pass-through commands.
7. The message body of the command response message comprises the serial number of the original message, the command type and the command response content of the response. The command type comprises a command type length and a command type, and the command response content comprises a command content length, an execution result and TLV.
The command types comprise a PW response parameter setting command, a PR response parameter reading command, an LT response position tracking command, a WP response inquiry/attention device current working parameter command, a QC response remote control command, an LE response log derivation command and an AT response instruction transparent transmission command.
8. The heartbeat request message only has a message header and is sent to the server side by the terminal.
9. The heartbeat response message only has a message header and is sent to the terminal by the server side.
10. The terminal connection message DISCONNECT is the last message sent by the client to the server. Indicating that the client is disconnected normally. The body of the message contains a disconnect reason field.
11. The upgrade notification message UPDATE is used for the server (or other equipment) to send firmware upgrade notification information to the terminal. The message body comprises the number of the upgrade target equipment (0x00 terminal, 0x01 controller, 0x02 display, 0x03 and others), TLV-100B upgrade mode (0x00 non-forced upgrade, 0x forced upgrade, local serial port forced upgrade) and a URL address TLV-1001 of the download upgrade server.
12. The message body of the upgrade response message comprises a response upgrade notification message serial number, a remote upgrade target device serial number, an upgrade state indication (0x00 notifies that the receiving is successful, the downloading is started, in the 0x01 downloading process, the 0x02 downloading is completed and the upgrading is started, the 0x03 downloading is failed, the 0x04 upgrading is completed, and the 0xFF upgrading is failed), an upgrade file downloading progress, the M2M terminal device downloading and an upgrade file failure alarm (0x00 cannot connect a downloading address, the 0x01 terminal device is insufficient in cache and cannot start downloading, the 0x02 downloading process has memory overflow, the connection is overtime in the 0x03 downloading process, the 0x04 complete download file check fails, and the 0x05 terminal device upgrade file fails).
Fourthly, foreground dynamic display concrete steps (as shown in figure 3)
E1. After the terminal is connected with the platform, the terminal can send messages to the platform according to a certain frequency, and all message texts are displayed in the debugging information area. The system background thread puts all the analyzed messages in a message queue for display;
E2. enabling a timing task by a background, traversing the message queue MsgBuffer according to a certain frequency (example 5S), if the message type is 0X03-PUSH _ DATA DATA sending message, displaying the analyzed message in a positioning state, a network communication state and a system state, and deleting the displayed message.
E3. Clicking parameter query, sending a CMD _ REQ command request message with a command type PR to the terminal by the platform, sending a CMD _ RESP command response message with a command type PR responding to a set parameter command by the terminal, analyzing the response message, then placing the analyzed response message in a message queue MsgBuffer, starting a thread, traversing the message queue, and if the message type is a command response, displaying the message on terminal parameters (including a terminal unique number, a SIM card number, a hardware version number, a software version number, a main center IP, a sub center IP and the like)
E4. Clicking the set parameters, starting a thread, assembling the terminal parameters (including a terminal unique number, a SIM card number, a hardware version number, a software version number, a main center IP, an auxiliary center IP and the like) into a message according to a CMD _ REQ command request message format with a PW command type, and sending the command request message to the terminal by the platform, wherein the sent message needs to be displayed in a debugging information area, so that debugging and analysis are facilitated.
The invention provides an Internet of things terminal debugging method based on message cycle processing of an XM2M protocol, which is used for realizing state information synchronization, parameter setting, firmware upgrading, debugging information, log file export and the like of a terminal and finally realizing the optimal configuration of the Internet of things terminal. Synchronizing state information, namely monitoring a terminal positioning state, a network communication state and a system state in real time according to a certain frequency (such as 5S); setting parameters: covering five major parameters of basic parameters, SIM cards, alarm parameters, CAN communication parameters and AT instructions, and optimizing the configuration of terminal parameters; firmware upgrading: upgrading a terminal program; debugging information: starting or closing a debugging mode, and selecting UARTO to output the following information types, MODEM related debugging information, GPS related debugging information, MCU CAN related debugging information and SYS related debugging information; log file: and exporting the terminal log file and the black box file, so that debugging and analysis are facilitated.
The invention constructs a set of M2M communication protocol message circulating system, the architecture supports core message processing mechanisms such as asynchronous multithreading, synchronous lock, message cache queue and the like, can easily respond to the M2M communication protocol with real-time, large data volume and high concurrency, and achieves high performance and no packet loss. Every time a message is received and sent, the response system is corresponding to one message, the no-response message is sent for three times continuously, and the response overtime is prompted if the no-response message is sent.
The invention solves the problems that the analysis of the existing terminal signal depends on the terminal communication protocol, when the communication protocol is changed, the analysis of the platform to the message needs to be recoded, compiled and issued, and the labor cost is higher; developers need a lot of time and energy to learn the communication protocol of the terminal, a lot of labor cost is needed, and time and energy are wasted.
Claims (1)
1. An Internet of things terminal debugging method based on message cycle processing of XM2M protocol is characterized by comprising the following steps,
the method for realizing message analysis comprises the following steps: according to XM2M protocol types, realizing message analysis method of each protocol type;
step two, serial port configuration: setting serial port information including serial port number, data bit, check bit, baud rate and stop bit, and opening serial port connection;
step three, receiving a message: receiving a message sent by a lower computer and putting the message into a message buffer area;
step four, message analysis: intercepting a complete message from a message buffer area according to an XM2M protocol, instantiating a message object in a factory mode, analyzing a message header and a message body of the message in the instantiation process, and putting the analyzed message object into a message queue;
step five, message display: dynamically displaying the analyzed message on the foreground of the platform in an asynchronous multithreading mode;
the fourth step is specifically as follows:
step a: storing the receiving terminal data packet into a message buffer area;
step b: acquiring a complete message from a message buffer area;
step c: splitting a message into a message header, a message body and a check bit;
step d: factory mode instantiates a message object;
step e: analyzing the message and putting the message into a message queue;
the step b is specifically as follows: the system background obtains a complete message from the message buffer according to the message start mark and the message end mark, the start character of the protocol is 7B7B namely two braces "{ {", the end character of the protocol is 7D7D namely two braces "} }", and the start character end character and the escape character in the message are removed, thus obtaining the complete message;
the step c is specifically as follows: the first byte to the thirteenth byte of the message are message header parts; the last byte is a check word; removing the message header and the check word, wherein the rest part is the message body, and removing the transfer character after obtaining the message body;
the method for removing the transfer character comprises the following steps: traversing the message body, replacing 1B1B7B7B with 7B7B, replacing 1B1B7D7D with 7D7D, and replacing 1B1B with 0000 to obtain the accurate message body;
the step d is specifically as follows: intercepting a first byte of a message header, interpreting according to related concepts of an XM2M protocol, acquiring a message type, and instantiating a message object according to the message type;
the concrete method of the step five comprises the following steps:
firstly, after a terminal is connected with a platform, the terminal can send messages to the platform according to a certain frequency, and received information texts are directly displayed in a debugging information area;
secondly, traversing the message queue to obtain the message type;
then, the message type is judged: if the data transmission type is the data transmission type, the data is displayed in the state information area; if the parameter setting type is the parameter setting type, the parameter setting type is displayed in the parameter setting area.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710101437.8A CN106899452B (en) | 2017-02-23 | 2017-02-23 | Message circulation processing Internet of things terminal debugging method based on XM2M protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710101437.8A CN106899452B (en) | 2017-02-23 | 2017-02-23 | Message circulation processing Internet of things terminal debugging method based on XM2M protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106899452A CN106899452A (en) | 2017-06-27 |
| CN106899452B true CN106899452B (en) | 2020-06-30 |
Family
ID=59185691
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710101437.8A Active CN106899452B (en) | 2017-02-23 | 2017-02-23 | Message circulation processing Internet of things terminal debugging method based on XM2M protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106899452B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112445868B (en) * | 2019-08-30 | 2024-04-12 | 北京京东振世信息技术有限公司 | Service message processing method and device |
| CN111537791A (en) * | 2020-07-01 | 2020-08-14 | 杭州雷甸科技有限公司 | Intelligent electric meter based on embedded operating system |
| CN113886314A (en) * | 2021-09-08 | 2022-01-04 | 江苏徐工工程机械研究院有限公司 | Method and system for receiving and analyzing serial port GPS message data |
| CN114398322B (en) * | 2021-12-07 | 2023-10-03 | 中国船舶重工集团公司第七0七研究所 | Network file management method suitable for underwater equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102158882A (en) * | 2011-05-27 | 2011-08-17 | 重庆邮电大学 | Two-channel data detection and protocol analysis meter based on 6LowPAN and method |
| CN103532998A (en) * | 2012-07-04 | 2014-01-22 | 中国科学院计算技术研究所 | Protocol/data conversion device and method |
| CN104135378A (en) * | 2013-05-03 | 2014-11-05 | 北京优联实科信息科技有限公司 | Method of management control of Internet of Things gateways and management control entity for Internet of Things gateways |
| WO2015198087A1 (en) * | 2014-06-24 | 2015-12-30 | Emad Abdulrazzak Felemban | A method, apparatus and system for enabling communication using multi-protocol gateway and virtual resource manager |
| CN105791106A (en) * | 2016-02-29 | 2016-07-20 | 重庆邮电大学 | 6LoWPAN home gateway in support of concurrent access service and realization method of the 6LoWPAN home gateway in support of concurrent access service |
-
2017
- 2017-02-23 CN CN201710101437.8A patent/CN106899452B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102158882A (en) * | 2011-05-27 | 2011-08-17 | 重庆邮电大学 | Two-channel data detection and protocol analysis meter based on 6LowPAN and method |
| CN103532998A (en) * | 2012-07-04 | 2014-01-22 | 中国科学院计算技术研究所 | Protocol/data conversion device and method |
| CN104135378A (en) * | 2013-05-03 | 2014-11-05 | 北京优联实科信息科技有限公司 | Method of management control of Internet of Things gateways and management control entity for Internet of Things gateways |
| WO2015198087A1 (en) * | 2014-06-24 | 2015-12-30 | Emad Abdulrazzak Felemban | A method, apparatus and system for enabling communication using multi-protocol gateway and virtual resource manager |
| CN105791106A (en) * | 2016-02-29 | 2016-07-20 | 重庆邮电大学 | 6LoWPAN home gateway in support of concurrent access service and realization method of the 6LoWPAN home gateway in support of concurrent access service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106899452A (en) | 2017-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106899452B (en) | Message circulation processing Internet of things terminal debugging method based on XM2M protocol | |
| CN101799751B (en) | Method for building monitoring agent software of host machine | |
| CN110933146B (en) | Data conversion method and device and server | |
| CN108062367B (en) | Data list uploading method and terminal thereof | |
| CN106407076B (en) | Software and hardware operation information monitoring method based on domestic CPU and operating system environment | |
| CN108667807A (en) | A kind of protocol self-adapting method and system based on monitoring cloud platform and gateway | |
| CN107957940B (en) | Test log processing method, system and terminal | |
| CN103441861B (en) | A kind of data record generation method and device | |
| CN108306804A (en) | A kind of Ethercat main station controllers and its communication means and system | |
| WO2013063950A1 (en) | Inspection method and system of multimode communication device | |
| CN113242534B (en) | General type multi-protocol digital instrument thing allies oneself with module based on WI-FI | |
| CN112988485A (en) | Simulation test method and device for power Internet of things equipment | |
| CN105139850A (en) | Speech interaction device, speech interaction method and speech interaction type LED asynchronous control system terminal | |
| CN113609048B (en) | Cloud edge service collaborative interaction method for electric power Internet of things | |
| CN102984258A (en) | Internet of things data transmission method and adapter | |
| CN109445384B (en) | Multi-device control system | |
| CN114172978A (en) | Multi-protocol equipment access method and related device | |
| CN112039983A (en) | Method and system for realizing Internet of things equipment connection middleware | |
| CN109788251B (en) | Video processing method, device and storage medium | |
| CN113792008A (en) | Method and device for acquiring network topology structure, electronic equipment and storage medium | |
| CN116743886A (en) | Industrial control equipment data acquisition system based on Internet of things | |
| WO2017041550A1 (en) | Device simulator communication method and system | |
| CN115700487A (en) | Method, device and equipment for processing messages in message queue and storage medium | |
| CN112445811A (en) | Data service method, device, storage medium and component based on SQL configuration | |
| US20220311644A1 (en) | Data transmission method and device, electronic apparatus and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 221000 No. 6, Keji Road, Xuzhou Economic and Technological Development Zone, Xuzhou City, Jiangsu Province Patentee after: XCMG Hanyun Technology Co.,Ltd. Address before: 221000 first floor, E1 building, software park, Xuzhou Economic and Technological Development Zone, Jiangsu Province Patentee before: JIANGSU XUGONG INFORMATION TECHNOLOGY Co.,Ltd. |
|
| CP03 | Change of name, title or address |