CN110324302B - IOT equipment communication method - Google Patents

IOT equipment communication method Download PDF

Info

Publication number
CN110324302B
CN110324302B CN201811302740.5A CN201811302740A CN110324302B CN 110324302 B CN110324302 B CN 110324302B CN 201811302740 A CN201811302740 A CN 201811302740A CN 110324302 B CN110324302 B CN 110324302B
Authority
CN
China
Prior art keywords
message
iot
indicates
iot equipment
hexadecimal
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
Application number
CN201811302740.5A
Other languages
Chinese (zh)
Other versions
CN110324302A (en
Inventor
高歌
汪成林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Linde China Forklift Truck Corp Ltd
Original Assignee
Linde China Forklift Truck Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Linde China Forklift Truck Corp Ltd filed Critical Linde China Forklift Truck Corp Ltd
Priority to CN201811302740.5A priority Critical patent/CN110324302B/en
Publication of CN110324302A publication Critical patent/CN110324302A/en
Application granted granted Critical
Publication of CN110324302B publication Critical patent/CN110324302B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/126—Applying verification of the received information the source of the received data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • 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
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
    • H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention discloses a communication method of IOT equipment, the IOT equipment and other equipment adopt encapsulated hexadecimal messages containing the same field to carry out message interaction; the message comprises a message header and a data field; the message header comprises control information used for indicating a message sending source and an operator type; the data field includes operation type information for indicating current message behavior; the other devices include other IOT devices, servers, or smart mobile devices. The message interaction message between the IOT device and other devices comprises a field for establishing an IoT chain and a field for indicating the current message behavior, and the integrity and the safety of message data can be ensured by combining the token verification field in the message interaction message, so that a message receiver can create multiple threads to process different message behaviors to improve the processing efficiency.

Description

IOT equipment communication method
Technical Field
The invention relates to the technical field of IOT, in particular to a communication method of IOT equipment.
Background
At present, in data transmission of the internet of things, a transmission layer protocol mainly uses a TCP (transmission control protocol) and a UDP (user datagram protocol) based on socket when information interaction is carried out between IOT equipment and other IOT equipment, between the IOT equipment and a server, between the IOT equipment and intelligent mobile equipment and the like, and an application layer protocol uses an http (hyper text transport protocol). When the TCP protocol is used for transmission, firstly, the related information such as the identity and the like is packaged through the http protocol, secondly, the connection is established with the other party through three-way handshake, and after the connection is successful, the data is packaged and transmitted through the http protocol. When the data is transmitted based on the UDP protocol, the data is directly transmitted after being packaged by the http protocol.
When http is used to encapsulate data, the following problems mainly exist:
(1) http is a hypertext transfer protocol, and data is plaintext, so that the data may be intercepted or intercepted in the transmission process;
(2) the integrity of the message cannot be proved, so that the data received by the receiver can be tampered;
(3) when the method is applied to data transmission of the Internet of things, a plurality of fields in the http protocol are not used, so that a receiving party can receive a large number of redundant fields, bandwidth is wasted, and the analysis burden is increased;
(4) the http protocol does not verify the identity of the communication party, so it is possible to encounter masquerading attacks;
(5) the lack of fields in the protocol for constructing IoT chains, and therefore, there is no guarantee that multiple IoT devices work in concert; in addition, the security of data cannot be guaranteed.
Disclosure of Invention
The main purpose of the present invention is to overcome the above-mentioned defects in the prior art, and provide a communication method for an IOT device, where a message interaction packet between the IOT device and other devices includes a field for establishing an IOT chain and a field for indicating a current message behavior, and in combination with a token verification field in the message interaction packet, the integrity and security of data can be ensured, and a message receiver can create multiple threads to process different message behaviors to improve processing efficiency.
The invention adopts the following technical scheme:
on one hand, the invention discloses a communication method of IOT equipment, the IOT equipment and other equipment adopt encapsulated hexadecimal messages comprising the same field to carry out message interaction; the message comprises a message header and a data field; the message header comprises control information used for indicating a message sending source and an operator type; the data field includes operation type information for indicating current message behavior; the other devices include other IOT devices, servers, or smart mobile devices.
Preferably, the control information includes a field indicating establishment of an IOT chain.
Preferably, before or after the IOT device and the other device perform information interaction, the IOT device and/or the other device creates multiple threads to perform processing with different threads according to the received operation type.
Preferably, the message further includes a token verification field for sender identity authentication.
Preferably, the message header further includes a message header start flag field and a message header end flag field with variable contents.
Preferably, the data field further includes a data field start flag field and a data field end flag field, the contents of which are variable.
In a second aspect, the present invention provides a method for communicating IOT devices, including:
the IOT equipment sends a hexadecimal message request to the server to establish connection with the server; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
the IOT equipment sends a hexadecimal message to a server to request basic data of the IOT equipment; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is an actual data request;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is dynamic data exchange; the data field indicates the operation type of the message as an actual data response.
Preferably, the server sends the hexadecimal packet with the same format as the request message in response to the IOT device, specifically, the server carries the Token verification field to send the hexadecimal packet with the same format as the request message in response to the IOT device.
In a third aspect, the present invention provides a method for communicating IOT devices, including:
the IOT equipment sends a hexadecimal message request to the server to establish connection with the server; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
the IOT equipment sends a hexadecimal message to a server to request address data of other IOT equipment; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is an actual data request;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is dynamic data exchange; the data field indicates the operation type of the message as an actual data response.
Preferably, the server sends the hexadecimal packet with the same format as the request message in response to the IOT device, specifically, the server carries the Token verification field to send the hexadecimal packet with the same format as the request message in response to the IOT device.
In a fourth aspect, the present invention provides a method for communicating IOT devices, including:
the IOT equipment sends a hexadecimal message to a plurality of other IOT equipment to request to establish connection; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
a plurality of other IOT devices send hexadecimal messages with the same format as the request message to respond to the IOT devices; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
the IOT equipment sends hexadecimal messages to a plurality of other IOT equipment to request the establishment of IOT chains; the message header indicates that a message sending source is an IOT device and indicates that an operator type of the message is an IOT chain; the operation type of the data field indication message is an actual data request;
the plurality of other IOT devices calculate hash codes according to the basic data of the IOT devices and send hexadecimal messages with the same format as the request message to respond to the IOT devices; the message header indicates that a message sending source is an IOT device and indicates that an operator type of the message is an IOT chain; and the operation type of the data field indication message is response hash code.
Preferably, the plurality of other IOT devices send the hexadecimal packet with the same format as the request message in response to the IOT device, specifically, the plurality of other IOT devices carry the Token verification field to send the hexadecimal packet with the same format as the request message in response to the IOT device.
As can be seen from the above description of the present invention, compared with the prior art, the present invention has the following advantages:
(1) the invention relates to a communication method of IOT equipment, wherein a sending source field in a message interaction message header can indicate which equipment the message is sent from, an operator type field in the message header can indicate that IOT chains are established among the IOT equipment, the establishment of the IOT chains can ensure that a plurality of IOT equipment can work cooperatively on one hand and can ensure the safety of message data on the other hand, if a certain IOT equipment is tampered, other equipment cannot pass verification;
(2) according to the IOT equipment communication method, the operation type information in the message interaction data domain is used for indicating the current message behavior, so that the IOT equipment and/or other equipment can create multiple threads, and different threads are adopted for processing according to the received operation types, the load of a single thread is reduced, and the processing efficiency is improved;
(3) according to the IOT equipment communication method, each message interaction authenticates a sender through the token, and the token is refreshed when the interaction is finished, so that the transmission safety can be ensured even if the token is stolen;
(4) according to the IOT equipment communication method, the head and tail identifiers in the message header are flexibly and dynamically changeable after negotiation according to the message interaction parties, so that the message transmission safety is improved;
(5) according to the IOT equipment communication method, the head and tail identifiers and the separators in the data domain are flexibly and dynamically changeable according to negotiation between the two message interaction parties, and the safety of message transmission is improved.
The above description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the description of the technical means more comprehensible.
The above and other objects, advantages and features of the present invention will become more apparent to those skilled in the art from the following detailed description of specific embodiments thereof, taken in conjunction with the accompanying drawings.
Drawings
Fig. 1 is a structural diagram of a message packet according to an embodiment of the present invention;
FIG. 2 is a message interaction diagram of IOT device communications according to an embodiment of the present invention;
fig. 3 is a first flowchart of a communication method of the IOT device according to the embodiment of the present invention;
fig. 4 is a flowchart of a second IOT device communication method according to an embodiment of the present invention;
fig. 5 is a flow chart of a communication method of the IOT device according to the embodiment of the present invention.
Detailed Description
The invention is further described below by means of specific embodiments.
On one hand, the invention discloses a communication method of IOT equipment, the IOT equipment and other equipment adopt encapsulated hexadecimal messages comprising the same field to carry out message interaction; the message comprises a message header and a data field; the message header comprises control information used for indicating a message sending source and an operator type; the data field includes operation type information for indicating current message behavior; the other devices include other IOT devices, servers, or smart mobile devices.
In this embodiment, referring to fig. 1, the packet body includes a packet header, a data field, Token, a verification bit, and a tail field. Before data transmission, data is packaged according to the structure of a message, and then the whole message is converted into a 16-system format and then transmitted.
As shown in table 1, the detailed information of each field in the message body is as follows.
TABLE 1
Figure BDA0001852809050000041
Figure BDA0001852809050000051
It can be understood that the positional relationship among the Data Domain field, Token field, and validity field in fig. 1 can be adjusted according to the need, for example, the message body may also sequentially include a message header, a Data field, a verification bit, a Token field, and a tail field, and the present invention is not limited in particular.
As shown in table 2, the detailed information of each field of the header is as follows.
TABLE 2
Figure BDA0001852809050000052
It can be understood that the positional relationship among the ctrl mark field, the Pointer field, and the Data Length field may be adjusted as needed, and the present invention is not limited in particular. In addition, what binary representation is specifically used for the transmission source type and the operator type in table 2 may be adjusted as needed, for example, a Service (server) transmission source may also be defined as 10, an IoT Device (IoT Device) transmission source may also be defined as 01, and the operator type may also be adjusted similarly, and the definition in table 2 only represents one example.
The detailed information of each field of the data field is as follows, see table 3.
TABLE 3
Figure BDA0001852809050000053
Figure BDA0001852809050000061
It can be understood that the positional relationship between the LengthOfId field and the Pointer field can be adjusted as required; the position relationship among the actionType field, the DataFrame field, and the DataLength field may be adjusted as needed, and the present invention is not limited specifically. In addition, what binary representation the operation type of the current message in table 3 specifically uses may be adjusted as needed, for example, the IOT device active connection may also be defined as 11000010, the Service active connection may also be defined as 11000001, and the definition in table 3 only represents one example.
The method for performing message interaction between the IOT device and other devices can be applied to the following aspects.
In a second aspect, referring to fig. 3, corresponding to steps 1, 2, 3 and 4 in fig. 2, the IOT device communication method of the present invention includes:
step 300, the IOT equipment sends a hexadecimal message request to a server to establish connection with the server; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
specifically, corresponding to the definitions in the above table, step 300 can be expressed as:
the IOT1 device requests to establish a connection with Service, and in the request message, ctrl mark is 10001001 (89), pointer is 00000001 (01), and actionType is 11000001 (C1).
Step 301, the server carries Token verification field to send hexadecimal message with the same format as the request message to respond to the IOT device; the message header indicates that a message sending source is a server and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
specifically, step 301 may be expressed as follows, corresponding to the definitions in the above table:
service carries Token response IOT1 device, the procedure ctrl Mark is 01001001 (49), pointer is 00000010(02), the procedure actionType is 00000000 (00), that is, connection is confirmed.
Step 302, the IOT device sends a hexadecimal message to a server to request basic data of the IOT device; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is an actual data request;
specifically, step 302 may be expressed as follows, corresponding to the definitions in the above table:
the IOT1 device requests basic data of the IOT1 itself from Service, the procedure ctrl mark is 10100001 (a1), the pointer is 00000011 (03), and the procedure actionType is 11001001 (C9).
Step 303, the server sends a hexadecimal message with the same format as the request message to respond to the IOT device; the message header indicates that a message sending source is a server and indicates that an operator type of the message is dynamic data exchange; the data field indicates the operation type of the message as an actual data response.
Specifically, step 303 may be expressed as follows, corresponding to the definitions in the above table:
service returns basic data in response to the request of the IOT1 device, and the procedure ctrl Mark is 01100001 (61), pointer is 00000100 (04), actionType is 11001001 (C9).
Referring to step 5 in FIG. 2, the IOT1 device also stores the data received from the server in its own database.
It should be noted that values of other fields of the message in the message interaction process may be customized or calculated and obtained according to descriptions in the table, and detailed descriptions are not described in the embodiment of the present invention.
In a third aspect, referring to fig. 4, corresponding to steps 1, 2, 6, and 7 in fig. 2, a method for communication of an IOT device in the present invention includes:
step 400, the IOT equipment sends a hexadecimal message request to a server to establish connection with the server; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
specifically, corresponding to the definitions in the above table, step 400 can be expressed as:
the IOT1 device requests to establish a connection with Service, and in the request message, ctrl mark is 10001001 (89), pointer is 00000001 (01), and actionType is 11000001 (C1).
Step 401, the server carries Token verification field to send hexadecimal message with the same format as the request message to respond to the IOT device; the message header indicates that a message sending source is a server and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
specifically, corresponding to the definitions in the above table, step 401 can be expressed as:
service carries Token response IOT1 device, the procedure ctrl Mark is 01001001 (49), pointer is 00000010(02), the procedure actionType is 00000000 (00), that is, connection is confirmed.
Step 402, the IOT device sends a hexadecimal message to a server to request address data of other IOT devices; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is an actual data request;
specifically, step 402 may be expressed as follows, corresponding to the definitions in the table:
the IOT1 device requests other IOT device IPs from Service with the procedure ctrl Mark being 10100001 (A1), pointer being 00000101 (05) and actionType being 11001001 (C9).
Step 403, the server sends a hexadecimal message with the same format as the request message to respond to the IOT device; the message header indicates that a message sending source is a server and indicates that an operator type of the message is dynamic data exchange; the data field indicates the operation type of the message as an actual data response.
Specifically, step 403 may be expressed as follows according to the definition in the table:
service responds to the IOT1 device with the IOT device's IP pool, with the procedure ctrl Mark of 01100001 (41), pointer of 00000110 (06), actionType of 11001001 (C9).
It should be noted that values of other fields of the message in the message interaction process may be customized or calculated and obtained according to descriptions in the table, and detailed descriptions are not described in the embodiment of the present invention.
In a fourth aspect, referring to fig. 5, corresponding to steps 8, 9, 10 and 11 in fig. 2, the IOT device communication method of the present invention includes:
step 500, an IOT device sends a hexadecimal message to a plurality of other IOT devices to request connection establishment; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
specifically, corresponding to the definitions in the above table, step 500 can be expressed as:
the IOT1 device establishes a connection with other IOT devices according to the acquired IP pools of other IOT devices, where ctrl mark is 10001001 (89), pointer is 00000111 (07), actionType is 11000001 (C1), that is, a link is requested.
Step 501, a plurality of other IOT devices carry Token verification fields to send hexadecimal messages with the same format as the request message so as to respond to the IOT devices; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
specifically, corresponding to the definitions in the above table, step 501 can be expressed as:
other IOT devices confirm connection with IOT1 device, with ctrl mark at 10001001 (89), pointer at 00001000(08), and actionType at 00000000 (00).
Step 502, the IOT device sends a hexadecimal message to a plurality of other IOT devices to request to establish an IOT chain; the message header indicates that a message sending source is an IOT device and indicates that an operator type of the message is an IOT chain; the operation type of the data field indication message is an actual data request;
specifically, step 502 may be expressed as follows, corresponding to the definitions in the above table:
the IOT1 device sends the base data to the other IOT devices in preparation for establishing IOT chains, with ctrl mark being 10011101(9C), pointer being 00001001(09), and actionType being 11001001 (C9).
Step 503, calculating hash code by a plurality of other IOT devices according to the basic data of the IOT devices, and sending a hexadecimal message with the same format as the request message to respond to the IOT devices; the message header indicates that a message sending source is an IOT device and indicates that an operator type of the message is an IOT chain; and the operation type of the data field indication message is response hash code.
Specifically, step 503 can be expressed as follows according to the definitions in the above table:
other IOT devices calculate hashcode from the IOT1 device's basic data and return to IOT1 device with procedure ctrl Mark of 10011101(9C), pointer of 00001001(0A) and actionType of 11000011 (C3).
It should be noted that values of other fields of the message in the message interaction process may be customized or calculated and obtained according to descriptions in the table, and detailed descriptions are not described in the embodiment of the present invention.
In addition, corresponding to fig. 2, the IOT device communication method according to the present invention may also include all steps from step 1 to step 11 (i.e., step 300, step 301, step 302, step 303, step 5, step 402, step 403, step 500, step 501, step 502, and step 503) in one message flow, so as to implement communication between the IOT device and other devices through the message format defined in the above table.
Further, the other devices may also be smart mobile devices, and communication between the IOT device and the smart mobile device can be realized as long as the IOT device and the smart mobile device perform message interaction according to the message format defined by the table, and a specific message flow depends on an actual application, and a detailed description is not given in the embodiment of the present invention.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (6)

1. The IOT equipment communication method is characterized in that the IOT equipment and other equipment adopt encapsulated hexadecimal messages comprising the same field to carry out message interaction; the message comprises a message header and a data field; the message header comprises control information used for indicating a message sending source and an operator type, and the operator type field comprises a field used for indicating the establishment of an IOT chain between IOT devices; the data field includes operation type information for indicating current message behavior; the other devices comprise other IOT devices, servers or intelligent mobile devices;
the message interaction method of the IOT equipment and other equipment comprises the following steps:
the IOT equipment sends a hexadecimal message request to the server to establish connection with the server; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
the IOT equipment sends a hexadecimal message to a server to request basic data of the IOT equipment; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is an actual data request;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is actual data response;
the IOT equipment sends a hexadecimal message request to the server to establish connection with the server; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
the IOT equipment sends a hexadecimal message to a server to request address data of other IOT equipment; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is an actual data request;
the server sends a hexadecimal message with the same format as the request message to respond to the IOT equipment; the message header indicates that a message sending source is a server and indicates that an operator type of the message is dynamic data exchange; the operation type of the data field indication message is actual data response;
the IOT equipment sends a hexadecimal message to a plurality of other IOT equipment to request to establish connection; the message comprises a message header and a data field; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is IOT equipment active connection;
a plurality of other IOT devices send hexadecimal messages with the same format as the request message to respond to the IOT devices; the message header indicates that a message sending source is IOT equipment and indicates that an operator type of the message is active connection; the operation type of the data field indication message is confirmation connection;
the IOT equipment sends hexadecimal messages to a plurality of other IOT equipment to request the establishment of IOT chains; the message header indicates that a message sending source is an IOT device and indicates that an operator type of the message is an IOT chain; the operation type of the data field indication message is an actual data request;
the plurality of other IOT devices calculate hash codes according to the basic data of the IOT devices and send hexadecimal messages with the same format as the request message to respond to the IOT devices; the message header indicates that a message sending source is an IOT device and indicates that an operator type of the message is an IOT chain; and the operation type of the data field indication message is response hash code.
2. The IOT device communication method of claim 1, wherein the IOT device and the other device, prior to or after interacting with information, further comprise the IOT device and/or the other device creating multiple threads to process with different threads depending on the type of operation received.
3. The IOT device communication method of claim 1, wherein the message further comprises a token verification field to perform sender identity authentication.
4. The IOT device communication method in accordance with claim 1, wherein the header further comprises a variable-content header start flag field and a header end flag field.
5. The IOT device communication method of claim 1, wherein the data field further comprises a variable content data field start flag field and a variable content data field end flag field.
6. The IOT device communication method according to claim 1, wherein the server sends a hexadecimal packet with a format same as that of the request message in response to the IOT device, and in particular, the server carries a Token authentication field to send a hexadecimal packet with a format same as that of the request message in response to the IOT device.
CN201811302740.5A 2018-11-02 2018-11-02 IOT equipment communication method Active CN110324302B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811302740.5A CN110324302B (en) 2018-11-02 2018-11-02 IOT equipment communication method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811302740.5A CN110324302B (en) 2018-11-02 2018-11-02 IOT equipment communication method

Publications (2)

Publication Number Publication Date
CN110324302A CN110324302A (en) 2019-10-11
CN110324302B true CN110324302B (en) 2022-04-19

Family

ID=68112635

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811302740.5A Active CN110324302B (en) 2018-11-02 2018-11-02 IOT equipment communication method

Country Status (1)

Country Link
CN (1) CN110324302B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111181951A (en) * 2019-12-26 2020-05-19 浙江华云信息科技有限公司 Intelligent transaction scheduling method based on Internet of things equipment
CN111865957A (en) * 2020-07-14 2020-10-30 上海挚想科技有限公司 Frame structure and method and system thereof

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330495A (en) * 2007-06-19 2008-12-24 瑞达信息安全产业股份有限公司 Control method and control system for implementing non-equity access in a computer network
CN103956177A (en) * 2014-04-17 2014-07-30 长春理工大学 Board level extendible type video-on-demand system based on Internet of Things
CN104994530A (en) * 2015-07-09 2015-10-21 乐鑫信息科技（上海）有限公司 Group gang control system and method based on group MAC (Media Access Control) address for plurality of pieces of Wi-Fi Internet of things equipment
CN105978851A (en) * 2016-04-13 2016-09-28 青岛海信传媒网络技术有限公司 System and method for controlling intelligent equipment
CN107580076A (en) * 2017-11-07 2018-01-12 山东网智物联网科技有限公司 Internet of Things communication means and device
WO2018019069A1 (en) * 2016-07-25 2018-02-01 华为技术有限公司 Resource operation method and apparatus
CN107968772A (en) * 2016-10-20 2018-04-27 中兴通讯股份有限公司 A kind of method, apparatus and relevant device for realizing Internet of Things application

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330495A (en) * 2007-06-19 2008-12-24 瑞达信息安全产业股份有限公司 Control method and control system for implementing non-equity access in a computer network
CN103956177A (en) * 2014-04-17 2014-07-30 长春理工大学 Board level extendible type video-on-demand system based on Internet of Things
CN104994530A (en) * 2015-07-09 2015-10-21 乐鑫信息科技（上海）有限公司 Group gang control system and method based on group MAC (Media Access Control) address for plurality of pieces of Wi-Fi Internet of things equipment
CN105978851A (en) * 2016-04-13 2016-09-28 青岛海信传媒网络技术有限公司 System and method for controlling intelligent equipment
WO2018019069A1 (en) * 2016-07-25 2018-02-01 华为技术有限公司 Resource operation method and apparatus
CN107968772A (en) * 2016-10-20 2018-04-27 中兴通讯股份有限公司 A kind of method, apparatus and relevant device for realizing Internet of Things application
CN107580076A (en) * 2017-11-07 2018-01-12 山东网智物联网科技有限公司 Internet of Things communication means and device

Also Published As

Publication number Publication date
CN110324302A (en) 2019-10-11

Similar Documents

Publication Publication Date Title
US10498831B2 (en) Communication sessions at a CoAP protocol layer
US7949704B2 (en) Administration of a broker-based publish/subscribe messaging system
KR102208935B1 (en) Messaging api over http protocol to establish context for data exchange
JP2018528679A (en) Device and method for establishing a connection in a load balancing system
CN101217512B (en) A client-end state maintenance method, system, client-end and application server
WO2011051028A1 (en) Method and device for securely transmitting data
CN104767742A (en) Safe communication method, gateway, network side server and system
CN110324302B (en) IOT equipment communication method
CN103108037A (en) Communication method, Web server and Web communication system
US8650313B2 (en) Endpoint discriminator in network transport protocol startup packets
CN110474922B (en) Communication method, PC system and access control router
CN106789993B (en) TCP agent method and device
US8171147B1 (en) System, method, and/or apparatus for establishing peer-to-peer communication
CN110602112A (en) MQTT (multiple quantum dots technique) secure data transmission method
CN107395582A (en) Portal authentication devices and system
US7526797B2 (en) System and method for processing callback requests included in web-based procedure calls through a firewall
US8060568B2 (en) Real time messaging framework hub to intercept and retransmit messages for a messaging facility
SUGUMAR Mqtt-a Lightweight Communication Protocol Relative Study
WO2021082945A1 (en) Remote management method and system, terminal device and server
Cohn et al. MQTT version 3.1
CN108040042A (en) A kind of safety method for being directed to CoAP agreements under multicast case
CN112118284A (en) Gateway device-oriented http data request method, device and medium
Errata MQTT Version 3.1. 1 Plus Errata 01
CN106789864B (en) Message anti-attack method and device
CN104917728A (en) Implementation method of cross-terminal single sign-on system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant