CN117440028A - Communication method and system for interaction between upper device and embedded device based on TCP - Google Patents
Communication method and system for interaction between upper device and embedded device based on TCP Download PDFInfo
- Publication number
- CN117440028A CN117440028A CN202311665794.9A CN202311665794A CN117440028A CN 117440028 A CN117440028 A CN 117440028A CN 202311665794 A CN202311665794 A CN 202311665794A CN 117440028 A CN117440028 A CN 117440028A
- Authority
- CN
- China
- Prior art keywords
- packet
- response
- request
- data packet
- request data
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000004891 communication Methods 0.000 title claims abstract description 31
- 230000003993 interaction Effects 0.000 title claims abstract description 29
- 230000004044 response Effects 0.000 claims abstract description 161
- 230000008569 process Effects 0.000 claims abstract description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Classifications
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
-
- 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
-
- 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)
Abstract
The invention discloses a communication method and a system for interaction between a superior device and an embedded device based on TCP, which relate to the technical field of communication, and the method comprises the following steps: the client creates a request data packet and transmits the request data packet to the server; the server analyzes the request data packet to obtain a request data packet, the server processes the request data in the request data packet to obtain a processing result based on the request packet type of the request data packet, and creates a response data packet according to the packet serial number of the request data packet; the client receives the response data packet sent by the server and confirms whether the response data packet is of a response packet type corresponding to the response data packet according to the second fixed packet header; the client acquires a callback mode from a preset request response callback list according to the packet sequence number, and returns response data to the client through the callback mode; the embedded device can easily find corresponding request original data after executing the response result, and the problem that the request of the upper device cannot acquire the response result is solved.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a communication method and a system for interaction between a high-level device and an embedded device based on TCP.
Background
In the industrial control field, the communication between the upper device and the embedded device generally uses a fixed-length data packet protocol format for interaction, so that the length and the format of data are greatly limited, the expansion of the data is inconvenient, and the interactive data format is inconvenient to understand in the service level, so that a lot of inconvenience is caused to developers; in addition, in some service scenarios, after the upper device sends a request command data packet to the embedded device, it is necessary to wait for the embedded device to execute the response result of the request command.
Disclosure of Invention
The invention aims to provide a communication method and a communication system for interaction between a high-level device and an embedded device based on TCP, so as to solve the problems in the background technology.
The technical aim of the invention is realized by the following technical scheme:
in a first aspect, an embodiment of the present application provides a communication method for interaction between a host device and an embedded device based on TCP, which is applied to interaction between a server corresponding to the host device and a client corresponding to the embedded device; the method comprises the following steps:
the client generates and sends a connection request to the server, and the server establishes TCP long connection with the client based on the connection request;
the client creates a request data packet, and transmits the request data packet to the server through the established TCP long connection, wherein the request data packet comprises a first fixed packet header and request data;
the server analyzes the format of the request data packet to obtain the request data packet, and obtains the request packet type and the packet sequence number of the request data packet from the first fixed packet header;
the service end processes the request data in the request data packet based on the request packet type of the request data packet to obtain a processing result, and creates a response data packet according to the packet serial number of the request data packet, wherein the response data packet comprises a second fixed packet header and response data, and the response data is the processing result corresponding to the request data;
the client receives the response data packet sent by the server and confirms whether the response data packet is of a response packet type corresponding to the response data packet according to the second fixed packet header, and if the current response data packet is determined to be of the response packet type, the packet serial number of the response data packet is obtained from the second fixed packet header;
if the packet sequence number of the request data packet is the same as or corresponds to the packet sequence number of the response data packet, the client acquires a callback mode from a preset request response callback list according to the packet sequence number, and returns the response data to the client through the callback mode.
The beneficial effects of the invention are as follows: in the scheme, the data interaction between the client and the server is realized by using the mode, the client and the server commonly observe the correspondence of the packet serial numbers, namely the client carries the corresponding packet serial numbers in the request data packet, the server carries the same or corresponding packet serial numbers in the response data packet, and after the client receives the response, the client searches the corresponding result callback method from the request response callback list according to the packet serial numbers in the response data packet, so that the client obtains the response data after the processing is completed; meanwhile, the length of the request data is not limited in the corresponding data packet, so that the expansion of the data can be facilitated, and furthermore, the request data or the response data is connected after the packet head is fixed through a specified data packet format, so that the understanding of personnel is facilitated; and the same or corresponding packet sequence numbers are utilized, so that the embedded equipment can easily find out corresponding request original data after executing a response result, and the problem that the request of the upper equipment cannot acquire the response result is solved.
On the basis of the technical scheme, the invention can be improved as follows.
Further, the first fixed packet header or the second fixed packet header includes a byte length, a packet type, and a packet sequence number.
Further, the response data packet further includes a response status code, where the response status code characterizes an execution result of the request data by the server, and the execution result includes execution success and execution failure.
Further, the data packet types include a heartbeat packet type, a request packet type, a response packet type, a no response type, a message distribution type, and an invalid packet type.
Further, the client receives a response data packet sent by the server by using an asynchronous response processing thread.
In a second aspect, an embodiment of the present application provides a communication system for interaction between a host device and an embedded device based on TCP, which is applied to a communication method for interaction between a host device and an embedded device based on TCP in any one of the first aspect, and an interaction between a server corresponding to the host device and a client corresponding to the embedded device; the system comprises:
the first module is used for generating and sending a connection request to the server through the client, and the server establishes TCP long connection with the client based on the connection request;
the second module is used for creating a request data packet through the client and transmitting the request data packet to the server through the established TCP long connection, wherein the request data packet comprises a first fixed packet head and request data;
the third module is used for analyzing the request data packet according to the format of the request data packet through the server side, and obtaining the request packet type and the packet serial number of the request data packet from the first fixed packet header;
a fourth module, configured to process, by the server, the request data in the request data packet based on the request packet type of the request data packet to obtain a processing result, and create a response data packet according to a packet sequence number of the request data packet, where the response data packet includes a second fixed packet header and response data, and the response data is a processing result corresponding to the request data;
a fifth module, configured to receive, by using the client, a response packet sent by the server, and confirm whether the response packet is a response packet type corresponding to the response packet according to the second fixed packet header, and if the current response packet is determined to be the response packet type, obtain a packet sequence number of the response packet from the second fixed packet header;
and a sixth module, configured to obtain, by the client, a callback mode from a preset request response callback list according to the packet sequence number if the packet sequence number of the request data packet is the same as or corresponds to the packet sequence number of the response data packet, and return the response data to the client in the callback mode.
Further, in the fourth module, the response data packet further includes a response status code, where the response status code characterizes an execution result of the request data by the server, and the execution result includes execution success and execution failure.
Further, in the above system, the data packet type includes a heartbeat packet type, a request packet type, a response packet type, a no response type, a message distribution type, and an invalid packet type.
In a third aspect, embodiments of the present application provide an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of the first aspects when executing the computer program.
In a fourth aspect, a non-transitory computer-readable storage medium stores computer instructions that cause a computer to perform the method of any of the first aspects.
Compared with the prior art, the invention has at least the following beneficial effects:
in the application, the data interaction between the client and the server is realized by using the method, the client and the server commonly observe the correspondence of the packet serial numbers, namely the corresponding packet serial numbers in the request data packet are carried by the client, the same or corresponding packet serial numbers in the response data packet are carried by the server, after the client receives the response, the client searches the corresponding result callback method from the request response callback list according to the packet serial numbers in the response data packet, and the client obtains the response data after the processing is completed; meanwhile, the length of the request data is not limited in the corresponding data packet, so that the expansion of the data can be facilitated, and furthermore, the request data or the response data is connected after the packet head is fixed through a specified data packet format, so that the understanding of personnel is facilitated; and the same or corresponding packet sequence numbers are utilized, so that the embedded equipment can easily find out corresponding request original data after executing a response result, and the problem that the request of the upper equipment cannot acquire the response result is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of embodiments of the invention and are incorporated in and constitute a part of this application, illustrate embodiments of the invention. In the drawings:
FIG. 1 is a flow chart of a communication method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a format of a request packet according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a format of a response packet according to an embodiment of the present invention;
fig. 4 is a schematic diagram of connection of a communication system according to an embodiment of the present invention;
fig. 5 is a schematic connection diagram of an electronic device according to an embodiment of the invention.
Description of the embodiments
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the description of the embodiments of the present invention, "plurality" means at least 2.
Example 1
The embodiment of the application provides a communication method for interaction between a host device and an embedded device based on TCP, which is applied to interaction between a server corresponding to the host device and a client corresponding to the embedded device; as shown in fig. 1, the method comprises the steps of:
s1, a client generates and transmits a connection request to a server, and the server establishes TCP long connection with the client based on the connection request.
The communication mode is a communication protocol interaction format based on TCP, and the interaction data length and the content format can be customized, the types of the data packets can be distinguished, and the serial numbers of the data packets can be provided at the bottom layer of a protocol framework; the communication mode is suitable for application of a CS communication mode, the communication roles are divided into a client and a server, the client sends request data, and the server processes the request and responds to the processing result to the client.
S2, the client creates a request data packet, and transmits the request data packet to the server through the established TCP long connection, wherein the request data packet comprises a first fixed packet header and request data.
After receiving the request data packet, the server side can obtain the first fixed packet header and the information of the request data in the request data packet; referring to fig. 2, fig. 2 is a schematic diagram of a format of a request packet, and as can be seen from fig. 2, for the request packet, which is composed of a fixed packet header and custom data, the first 4 bytes in the fixed packet header represent the total length of all the following bytes, and the 5 th byte in the fixed packet header represents the message type (packet type); in particular, the message types are represented by different codes, such as: 0 represents a heartbeat packet, and the heartbeat packet is received without processing or returned; 1 represents a request packet, which represents a request execution command data packet sent by a client to a server, and the server needs to return a corresponding execution operation response packet to the client; 2 represents a response packet, which represents the result of the request execution operation returned by the server to the client; 3 represents a message pushed to the client by the server or a message pushed to the server by the client, and the operation does not need to respond to each other; 4 represents a message that the client sends to the server and needs the server to distribute; the other data represents an invalid packet.
Optionally, the data packet types include a heartbeat packet type, a request packet type, a response packet type, a no response type, a message distribution type, and an invalid packet type.
The heartbeat packet type, the request packet type, the response packet type, the no-response type, the message distribution type and the invalid packet type are indicated in the 5 th byte of the first fixed packet header, namely by 0, 1, 2, 3, 4 and other numbers.
Optionally, the first fixed packet header or the second fixed packet header includes a byte length, a packet type, and a packet sequence number.
Wherein, the 6 th byte and the 7 th byte of the fixed packet head represent the packet serial numbers of the data packet, the field is only valid for the request data packet and the response data packet, each request data packet needs to have a unique packet serial number, and the serial numbers need to be filled in the packet serial number bits of the response data packet as they are so as to distinguish which request data packet the response data packet corresponds to; specifically, the unsolicited packet and the unresponsive packet may not be set, and may be set to 0 by default.
S3, the server analyzes the request data packet according to the format of the request data packet, and obtains the request packet type and the packet sequence number of the request data packet from the first fixed packet header.
S4, the service end processes the request data in the request data packet based on the request packet type of the request data packet to obtain a processing result, and creates a response data packet according to the packet serial number of the request data packet, wherein the response data packet comprises a second fixed packet header and response data, and the response data is the processing result corresponding to the request data.
Optionally, the response data packet further includes a response status code, where the response status code characterizes an execution result of the server on the request data, and the execution result includes execution success and execution failure.
The server side understands the separated request data packet and carries out corresponding processing according to the type and service requirement of the request data packet; specifically, if the type of the received data packet is the request packet type, creating a corresponding response data packet according to the packet serial number of the request data packet, adding data of a service processing result into the response data packet, and then sending the response data packet to the client; specifically, as shown in fig. 3, the format of the response data packet is the same as that of the request data packet, and the first 7 bytes of the response data packet are also fixed packet headers and finally are custom data; the difference is that: there is a response status code bit between the fixed packet header and the custom data, and the response data packet adds 2 bytes to serve as a response status code after the fixed packet header, which indicates that the server end can set the execution result of the request message to 200 if the execution is successful, while other values are execution failures.
And S5, the client receives the response data packet sent by the server, confirms whether the response data packet is of a response packet type corresponding to the response data packet according to the second fixed packet header, and acquires the packet sequence number of the response data packet from the second fixed packet header if the current response data packet is determined to be of the response packet type.
Optionally, the client receives the response data packet sent by the server by using an asynchronous response processing thread.
And S6, if the packet sequence number of the request data packet is the same as or corresponds to the packet sequence number of the response data packet, the client acquires a callback mode from a preset request response callback list according to the packet sequence number, and returns the response data to the client through the callback mode.
Example 2
The embodiment of the application provides a communication system for interaction between a superior device and an embedded device based on TCP, which is applied to the communication method for interaction between the superior device and the embedded device based on TCP in any one of the embodiment 1, and is applied to interaction between a server corresponding to the superior device and a client corresponding to the embedded device; as shown in fig. 4, the system includes:
the first module is used for generating and sending a connection request to the server through the client, and the server establishes TCP long connection with the client based on the connection request.
And the second module is used for creating a request data packet through the client and transmitting the request data packet to the server through the established TCP long connection, wherein the request data packet comprises a first fixed packet header and request data.
And the third module is used for analyzing the request data packet according to the format of the request data packet through the server side and obtaining the request packet type and the packet sequence number of the request data packet from the first fixed packet header.
And a fourth module, configured to process, by the server, the request data in the request data packet based on the request packet type of the request data packet to obtain a processing result, and create a response data packet according to the packet sequence number of the request data packet, where the response data packet includes a second fixed packet header and response data, and the response data is a processing result corresponding to the request data.
Optionally, in the fourth module, the response data packet further includes a response status code, where the response status code characterizes an execution result of the request data by the server, and the execution result includes execution success and execution failure.
And a fifth module, configured to receive, by the client, the response packet sent by the server, and confirm whether the second fixed packet header is a response packet type corresponding to the response packet, and if the current response packet is determined to be the response packet type, obtain a packet sequence number of the response packet from the second fixed packet header.
And a sixth module, configured to obtain, by the client, a callback mode from a preset request response callback list according to the packet sequence number if the packet sequence number of the request data packet is the same as or corresponds to the packet sequence number of the response data packet, and return the response data to the client in the callback mode.
Optionally, in the system, the data packet type includes a heartbeat packet type, a request packet type, a response packet type, a no response type, a message distribution type, and an invalid packet type.
Example 3
An embodiment of the present application provides an electronic device, as shown in fig. 5, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the method of any one of embodiment 1.
Example 4
A non-transitory computer readable storage medium storing computer instructions that cause a computer to perform the method of any one of embodiment 1.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (10)
1. The communication method of interaction between the upper device and the embedded device based on the TCP is applied to interaction between a server corresponding to the upper device and a client corresponding to the embedded device; characterized in that the method comprises the steps of:
the client generates and transmits a connection request to a server, and the server establishes TCP long connection with the client based on the connection request;
the client creates a request data packet and transmits the request data packet to a server through the established TCP long connection, wherein the request data packet comprises a first fixed packet head and request data;
the server analyzes the request data packet according to the format of the request data packet, and obtains the request packet type and the packet sequence number of the request data packet from the first fixed packet header;
the server side processes the request data in the request data packet based on the request packet type of the request data packet to obtain a processing result, and creates a response data packet according to the packet serial number of the request data packet, wherein the response data packet comprises a second fixed packet header and response data, and the response data is the processing result corresponding to the request data;
the client receives a response data packet sent by a server, confirms whether the response data packet is of a response packet type corresponding to the response data packet according to the second fixed packet header, and acquires a packet sequence number of the response data packet from the second fixed packet header if the current response data packet is determined to be of the response packet type;
if the packet sequence number of the request data packet is the same as or corresponds to the packet sequence number of the response data packet, the client acquires a callback mode from a preset request response callback list according to the packet sequence number, and returns response data to the client through the callback mode.
2. The communication method for interaction between a TCP-based host device and an embedded device according to claim 1, wherein the first fixed packet header or the second fixed packet header includes a byte length, a packet type, and a packet sequence number.
3. The communication method for interaction between a TCP-based host device and an embedded device according to claim 1, wherein the response packet further includes a response status code, the response status code characterizes an execution result of the request data by the server, and the execution result includes execution success and execution failure.
4. The communication method for interaction between a TCP-based superordinate device and an embedded device according to claim 2, wherein the data packet type includes a heartbeat packet type, a request packet type, a response packet type, a no-response type, a message distribution type, and an invalid packet type.
5. The communication method for interaction between a TCP-based host device and an embedded device according to claim 1, wherein the client receives a response packet sent by the server by using an asynchronous response processing thread.
6. The communication system for interaction between the upper device and the embedded device based on the TCP is applied to the communication method for interaction between the upper device and the embedded device based on the TCP as claimed in any one of claims 1 to 5, and is applied to interaction between a server corresponding to the upper device and a client corresponding to the embedded device; characterized in that the system comprises:
the first module is used for generating and sending a connection request to a server through the client, and the server establishes TCP long connection with the client based on the connection request;
the second module is used for creating a request data packet through the client and transmitting the request data packet to a server through the established TCP long connection, wherein the request data packet comprises a first fixed packet header and request data;
the third module is used for analyzing the request data packet according to the format of the request data packet through the server side, and obtaining the request packet type and the packet sequence number of the request data packet from the first fixed packet header;
a fourth module, configured to process, by the server, request data in a request data packet based on a request packet type of the request data packet to obtain a processing result, and create a response data packet according to a packet sequence number of the request data packet, where the response data packet includes a second fixed packet header and response data, and the response data is a processing result corresponding to the request data;
a fifth module, configured to receive, by using the client, a response packet sent by a server, and determine, according to the second fixed packet header, whether the response packet is a response packet type corresponding to the response packet, and if it is determined that the current response packet is a response packet type, obtain a packet sequence number of the response packet from the second fixed packet header;
and a sixth module, configured to obtain, by the client, a callback mode from a preset request response callback list according to the packet sequence number if the packet sequence number of the request data packet is the same as or corresponds to the packet sequence number of the response data packet, and return the response data to the client in the callback mode.
7. The communication system according to claim 6, wherein in the fourth module, the response data packet further includes a response status code, the response status code characterizes an execution result of the request data by the server, and the execution result includes execution success and execution failure.
8. The communication system in which a TCP-based superordinate device and an embedded device interact according to claim 6, wherein the data packet type includes a heartbeat packet type, a request packet type, a response packet type, a no response type, a message distribution type, and an invalid packet type.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of claims 1-5 when the computer program is executed by the processor.
10. A non-transitory computer readable storage medium storing computer instructions that cause a computer to perform the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311665794.9A CN117440028A (en) | 2023-12-07 | 2023-12-07 | Communication method and system for interaction between upper device and embedded device based on TCP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311665794.9A CN117440028A (en) | 2023-12-07 | 2023-12-07 | Communication method and system for interaction between upper device and embedded device based on TCP |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117440028A true CN117440028A (en) | 2024-01-23 |
Family
ID=89551646
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311665794.9A Pending CN117440028A (en) | 2023-12-07 | 2023-12-07 | Communication method and system for interaction between upper device and embedded device based on TCP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117440028A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106330833A (en) * | 2015-06-29 | 2017-01-11 | 中兴通讯股份有限公司 | Communication method based on ICAP (Internet Content Adaptation Protocol), client and server |
| CN106921992A (en) * | 2016-07-06 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The determination method of wireless network connection status, client and service end |
| CN107395559A (en) * | 2017-05-27 | 2017-11-24 | 北京五八信息技术有限公司 | Data processing method and equipment based on redis |
| CN109922053A (en) * | 2019-02-22 | 2019-06-21 | 北京三快在线科技有限公司 | Data transmission method, device, electronic equipment and readable storage medium storing program for executing |
| CN115604013A (en) * | 2022-10-21 | 2023-01-13 | 北京珞安科技有限责任公司（Cn） | Industrial data interaction platform and interaction method |
-
2023
- 2023-12-07 CN CN202311665794.9A patent/CN117440028A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106330833A (en) * | 2015-06-29 | 2017-01-11 | 中兴通讯股份有限公司 | Communication method based on ICAP (Internet Content Adaptation Protocol), client and server |
| CN106921992A (en) * | 2016-07-06 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The determination method of wireless network connection status, client and service end |
| CN107395559A (en) * | 2017-05-27 | 2017-11-24 | 北京五八信息技术有限公司 | Data processing method and equipment based on redis |
| CN109922053A (en) * | 2019-02-22 | 2019-06-21 | 北京三快在线科技有限公司 | Data transmission method, device, electronic equipment and readable storage medium storing program for executing |
| CN115604013A (en) * | 2022-10-21 | 2023-01-13 | 北京珞安科技有限责任公司（Cn） | Industrial data interaction platform and interaction method |
Non-Patent Citations (3)
| Title |
|---|
| 刘瑜，安义，陈逸怀等: "Python FastAPI Web开发从入门到项目实战（视频版）", 30 September 2022, 华中科技大学出版社, pages: 104 - 105 * |
| 郑丽娜: "网络通信实验教程", 30 April 2015, 山东大学出版社, pages: 182 - 183 * |
| 陆晓蕾，倪斌: "Python 3：语料库技术与应用", 31 January 2021, 厦门大学出版社, pages: 26 - 27 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111083161A (en) | Data transmission processing method and device and Internet of things equipment | |
| CN109451032B (en) | Message transmission system | |
| US7185014B1 (en) | Retrieving data from a server | |
| CN111756674B (en) | Network communication method, system, device and computer readable storage medium | |
| CN109547524B (en) | User behavior storage method, device, equipment and storage medium based on Internet of things | |
| CN109327511B (en) | Data request method and server based on HTTP (hyper text transport protocol) | |
| CN110324405B (en) | Message sending method, device, system and computer readable storage medium | |
| CN109217983B (en) | Industrial Internet of things operation terminal communication protocol design method | |
| US11889255B2 (en) | Communication method between earphones and charging box, charging box, earphones and readable storage medium | |
| KR101682243B1 (en) | Method for providing message and device therefor | |
| US6233730B1 (en) | Revision compatibility between programs | |
| US20170085673A1 (en) | Attribute Operating Method and Apparatus | |
| CN110830466B (en) | Method and device for framing DL/T645 protocol message based on XML | |
| CN113220481A (en) | Request processing and feedback method and device, computer equipment and readable storage medium | |
| KR102285352B1 (en) | PROXY, METHOD FOR INTERWORKING BETWEEN HETEROGENEOUS IoT DEVICE AND IoT FLATFORM AND SYSTEM THE PROXY | |
| CN117440028A (en) | Communication method and system for interaction between upper device and embedded device based on TCP | |
| CN111756844A (en) | Multi-language message agent method and device | |
| US11196792B2 (en) | Method, device and system for transmitting data | |
| CN114157714B (en) | Method, system and storage device for realizing financial system protocol communication based on Netty | |
| CN113992740B (en) | Middleware based on autonomous control and data transmission method | |
| CN107171915B (en) | Communication protocol changing method and device | |
| CN112954658B (en) | Business card system suitable for data exchange of communication protocol layer and data exchange method | |
| US20220052902A1 (en) | Method for managing remote device through management device | |
| US20040088395A1 (en) | Method for probing a server | |
| JP2017033221A (en) | Api request processing device, api request processing method, and api request processing program |
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 |