CN112104660A - Data transmission method, related equipment and readable storage medium - Google Patents

Data transmission method, related equipment and readable storage medium Download PDF

Info

Publication number
CN112104660A
CN112104660A CN202010986839.2A CN202010986839A CN112104660A CN 112104660 A CN112104660 A CN 112104660A CN 202010986839 A CN202010986839 A CN 202010986839A CN 112104660 A CN112104660 A CN 112104660A
Authority
CN
China
Prior art keywords
field
data
byte stream
data message
sender
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
Application number
CN202010986839.2A
Other languages
Chinese (zh)
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.)
State Grid Zhejiang Electric Power Co Ltd
Zhejiang Huayun Information Technology Co Ltd
Information and Telecommunication Branch of State Grid Zhejiang Electric Power Co Ltd
Original Assignee
State Grid Zhejiang Electric Power Co Ltd
Zhejiang Huayun Information Technology Co Ltd
Information and Telecommunication Branch of State Grid Zhejiang Electric Power Co 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 State Grid Zhejiang Electric Power Co Ltd, Zhejiang Huayun Information Technology Co Ltd, Information and Telecommunication Branch of State Grid Zhejiang Electric Power Co Ltd filed Critical State Grid Zhejiang Electric Power Co Ltd
Priority to CN202010986839.2A priority Critical patent/CN112104660A/en
Publication of CN112104660A publication Critical patent/CN112104660A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/66Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22Parsing or analysis of headers

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Communication Control (AREA)

Abstract

The application discloses a data transmission method, related equipment and a readable storage medium. Based on the above scheme, the sender may send the binary format data packet including the header byte field, the request sequence number field, the operation code field, the object identification field, the message body length field, the message body field, and the check code field, and the receiver may parse the binary format data packet. The binary format data message occupies smaller transmission resources compared with JSON, XML and other formats, and the edge gateway and the cloud platform can be a sender and a receiver for each other, so that when the data transmitted between the edge gateway and the cloud platform is the binary format data message, the efficiency and the reliability of data transmission between the edge gateway and the cloud platform can be improved.

Description

Data transmission method, related equipment and readable storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a data transmission method, a related device, and a readable storage medium.
Background
In the power internet of things (as shown in fig. 1), an edge gateway needs to collect data reported by a sensing layer terminal based on a local communication mode and report the collected data to a cloud platform based on a remote communication mode, and the cloud platform also needs to issue some data to the edge gateway based on the remote communication mode.
At present, when data transmission is performed between an edge gateway and a cloud platform, formats such as JSON and XML are often used, but the transmission channel resources occupied by the formats are large, and in some cases, for example, a large number of edge gateways report data to the cloud platform at the same time, the traffic of the transmission channel is limited, and the like, which easily causes low data transmission efficiency and reliability between the edge gateway and the cloud platform.
Therefore, data transmission between the edge gateway and the cloud platform needs to be optimized.
Disclosure of Invention
In view of the foregoing problems, the present application provides a data message parsing method, a related device, and a readable storage medium. The specific scheme is as follows:
a data transmission method is applied to a receiving party, and the method comprises the following steps:
receiving a data message sent by a sender; the data message is in a binary format and comprises a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field and a check code field;
the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
Optionally, the receiving a data packet sent by a sender includes:
receiving a transport protocol byte stream sent by a sender;
determining whether the transport protocol byte stream is new data;
if the transmission protocol byte stream is new data, judging whether the format of the transmission protocol byte stream is complete;
and if the format of the transmission protocol byte stream is complete, determining the transmission protocol byte stream as a data message.
Optionally, the determining whether the transport protocol byte stream is new data includes:
obtaining the value of a request sequence number field in the transport protocol byte stream;
judging whether the value of the request sequence number field in the transport protocol byte stream is consistent with the request sequence number of the data message analyzed by the receiver;
if the value of the request sequence number field in the transmission protocol byte stream is not consistent with the request sequence number of the data message analyzed by the receiver, determining that the transmission protocol byte stream is new data;
and if the value of the request sequence number field in the transmission protocol byte stream is consistent with the request sequence number of the data message analyzed by the receiver, determining that the transmission protocol byte stream is not new data.
Optionally, the determining whether the format of the transport protocol byte stream is complete includes:
obtaining a value of a header byte field in the transport protocol byte stream;
judging whether the value of a head byte field of the transmission protocol byte stream is a preset value or not;
if the value of the head byte field of the transmission protocol byte stream is a preset value, determining that the format of the transmission protocol byte stream is complete;
and if the value of the head byte field of the transport protocol byte stream is not a preset value, determining that the format of the transport protocol byte stream is incomplete.
Optionally, after receiving the data packet sent by the sender, the method further includes:
calculating a check code of the data message;
judging whether the calculated check code of the data message is consistent with the value of the check code field of the data message or not, and if so, analyzing the data message; and if the two are not consistent, sending an error notification message to the sender.
Optionally, the calculating the check code of the data packet includes:
and (4) the total byte number of the data message is left to 256, and the check code of the data message is calculated.
Optionally, the parsing the data packet includes:
analyzing the message body field of the data message to obtain a data item corresponding to the data message;
and analyzing the operation code field of the data message to obtain the instruction information corresponding to the data message.
A data transmission apparatus applied to a receiving side, the apparatus comprising:
a receiving unit, configured to receive a data packet sent by a sender; the data message is in a binary format and comprises a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field and a check code field;
the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
A data transmission device comprising a memory and a processor;
the memory is used for storing programs;
the processor is configured to execute the program to implement the steps of the data transmission method.
A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the data transmission method as described above.
By means of the technical scheme, the application discloses a data transmission method, related equipment and a readable storage medium. Based on the above scheme, the sender may send the binary format data packet including the header byte field, the request sequence number field, the operation code field, the object identification field, the message body length field, the message body field, and the check code field, and the receiver may parse the binary format data packet. The binary format data message occupies smaller transmission resources compared with JSON, XML and other formats, and the edge gateway and the cloud platform can be a sender and a receiver for each other, so that when the data transmitted between the edge gateway and the cloud platform is the binary format data message, the efficiency and the reliability of data transmission between the edge gateway and the cloud platform can be improved.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a schematic structural diagram of an electric power internet of things disclosed in an embodiment of the present application;
fig. 2 is an interaction diagram of a data transmission method disclosed in an embodiment of the present application;
FIG. 3 is a diagram illustrating a data message format according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a data item disclosed in an embodiment of the present application;
FIG. 5 is a schematic diagram of an operation code disclosed in the embodiments of the present application;
fig. 6 is a schematic flowchart of a method for receiving a data packet sent by a sender according to an embodiment of the present application;
fig. 7 is a flowchart illustrating a method for determining whether the transport protocol byte stream is new data according to an embodiment of the present application;
fig. 8 is a schematic flowchart of a method for determining whether a format of the transport protocol byte stream is complete according to an embodiment of the present application;
fig. 9 is a schematic flow chart illustrating a data message processing method according to an embodiment of the present application;
fig. 10 is a block diagram of a hardware structure of a data transmission device disclosed in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Next, a data transmission method provided by the present application is described by the following embodiments.
Referring to fig. 2, fig. 2 is an interaction schematic diagram of a data transmission method disclosed in an embodiment of the present application, where the method may include:
step S101: and the sender sends the data message to the receiver.
It should be noted that, in the present application, the data packet is in a binary format, for convenience of understanding, please refer to fig. 3, and fig. 3 is a schematic diagram of a data packet format disclosed in an embodiment of the present application, and as shown in fig. 3, the data packet includes a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field, and a check code field. The message body field is in binary format, and is a list of data items, such as data item 1, data item 2, and data item 3 … …, as shown in fig. 4, where each data item includes three parts, such as a type identifier, a length, and a value. The operation code field is used to indicate the instruction information to be sent by the sender, and as shown in fig. 5, the operation code includes notification, read request, write request, call request, read response, write response, and call response.
Step S102: the receiving party receives the data message sent by the sending party.
It should be noted that the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
The embodiment discloses a data transmission method. Based on the method, the sender can send the binary format data message comprising the header byte field, the request sequence number field, the operation code field, the object identification field, the message body length field, the message body field and the check code field, and the receiver can analyze the binary format data message. The binary format data message occupies smaller transmission resources compared with JSON, XML and other formats, and the edge gateway and the cloud platform can be a sender and a receiver for each other, so that when the data transmitted between the edge gateway and the cloud platform is the binary format data message, the efficiency and the reliability of data transmission between the edge gateway and the cloud platform can be improved.
Next, the data transmission method of the present application is described in detail in the embodiment of the present application from the perspective of the receiving side.
In another embodiment of the present application, a detailed description is given to a specific implementation manner of the step S101 of receiving the data packet sent by the sender, referring to fig. 6, where the implementation manner may include the following steps:
step S201: and receiving the transport protocol byte stream sent by the sender.
In this application, the transport protocol byte stream is also in binary format.
Step S202: it is determined whether the transport protocol byte stream is new data, and if the transport protocol byte stream is new data, step S203 is performed, and if the transport protocol byte stream is not new data, step S05 is performed.
Referring to fig. 7 as an implementation manner, fig. 7 is a schematic flowchart of a method for determining whether the transport protocol byte stream is new data according to an embodiment of the present application, where the method may include the following steps:
step S2021: and acquiring the value of a request sequence number field in the transport protocol byte stream.
Step S2022: judging whether the value of the request sequence number field in the transport protocol byte stream is consistent with the request sequence number of the data message analyzed by the receiver; if the value of the request sequence number field in the transport protocol byte stream is not consistent with the request sequence number of the data message analyzed by the receiver, executing step S2023; if the value of the request sequence number field in the transport protocol byte stream is consistent with the request sequence number of the data message analyzed by the receiver, step S2024 is executed.
Step S2023: determining the transport protocol byte stream as new data.
Step S2024: determining that the transport protocol byte stream is not new data.
Step S203: and judging whether the format of the transport protocol byte stream is complete, if so, executing the step S204, and if not, executing the step S206.
Referring to fig. 8 as an implementable manner, fig. 8 is a schematic flowchart of a method for determining whether a format of the transport protocol byte stream is complete, which is disclosed in an embodiment of the present application, and the method may include the following steps:
step S2031: and acquiring the value of a head byte field in the transport protocol byte stream.
Step S2032: judging whether the value of a head byte field of the transmission protocol byte stream is a preset value or not; if the value of the header byte field of the transport protocol byte stream is a preset value, step S2033 is performed, and if the value of the header byte field of the transport protocol byte stream is not a preset value, step S2034 is performed.
Step S2033: determining that the format of the transport protocol byte stream is complete.
Step S2034: determining that a format of the transport protocol byte stream is incomplete.
It should be noted that, as an example, the preset value may be 0xA 1.
Step S204: and determining the transmission protocol byte stream as a data message.
Step S205: and not processing the transmission protocol byte stream, and continuously waiting for receiving the transmission protocol byte stream sent by the sender.
Step S206: buffering the transport protocol byte stream.
It should be noted that, referring to fig. 9, fig. 9 is a schematic flow chart of a data message processing method disclosed in the embodiment of the present application, and as shown in fig. 9, for a receiving side, after receiving a data message sent by a sending side, the following steps may be further performed:
step S301: and calculating the check code of the data message.
In this application, the manner of calculating the check code of the data packet may be: and (4) the total byte number of the data message is left to 256, and the check code of the data message is calculated.
Step S302: judging whether the calculated check code of the data message is consistent with the value of the check code field of the data message, if so, executing the step S303; if not, go to step S304.
Step S303: and analyzing the data message.
In this application, the analyzing the data packet may include: analyzing the message body field of the data message to obtain a data item corresponding to the data message; and analyzing the operation code field of the data message to obtain the instruction information corresponding to the data message.
Step S304: and sending an error notification message to the sender.
The following describes a data transmission device disclosed in an embodiment of the present application, and the data transmission device described below and the data transmission method described above may be referred to correspondingly.
The data transmission apparatus may include:
a receiving unit, configured to receive a data packet sent by a sender; the data message is in a binary format and comprises a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field and a check code field;
the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
Referring to fig. 10, fig. 10 is a block diagram of a hardware structure of a data transmission device according to an embodiment of the present application, and referring to fig. 10, the hardware structure of data transmission may include: at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4;
in the embodiment of the application, the number of the processor 1, the communication interface 2, the memory 3 and the communication bus 4 is at least one, and the processor 1, the communication interface 2 and the memory 3 complete mutual communication through the communication bus 4;
the processor 1 may be a central processing unit CPU, or an application Specific Integrated circuit asic, or one or more Integrated circuits configured to implement embodiments of the present invention, etc.;
the memory 3 may include a high-speed RAM memory, and may further include a non-volatile memory (non-volatile memory) or the like, such as at least one disk memory;
wherein the memory stores a program and the processor can call the program stored in the memory, the program for:
receiving a data message sent by a sender; the data message is in a binary format and comprises a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field and a check code field;
the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
Alternatively, the detailed function and the extended function of the program may be as described above.
Embodiments of the present application further provide a readable storage medium, where a program suitable for being executed by a processor may be stored, where the program is configured to:
receiving a data message sent by a sender; the data message is in a binary format and comprises a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field and a check code field;
the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
Alternatively, the detailed function and the extended function of the program may be as described above.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A data transmission method, applied to a receiving side, the method comprising:
receiving a data message sent by a sender; the data message is in a binary format and comprises a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field and a check code field;
the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
2. The method of claim 1, wherein the receiving the data packet sent by the sender comprises:
receiving a transport protocol byte stream sent by a sender;
determining whether the transport protocol byte stream is new data;
if the transmission protocol byte stream is new data, judging whether the format of the transmission protocol byte stream is complete;
and if the format of the transmission protocol byte stream is complete, determining the transmission protocol byte stream as a data message.
3. The method of claim 2, wherein the determining whether the transport protocol byte stream is new data comprises:
obtaining the value of a request sequence number field in the transport protocol byte stream;
judging whether the value of the request sequence number field in the transport protocol byte stream is consistent with the request sequence number of the data message analyzed by the receiver;
if the value of the request sequence number field in the transmission protocol byte stream is not consistent with the request sequence number of the data message analyzed by the receiver, determining that the transmission protocol byte stream is new data;
and if the value of the request sequence number field in the transmission protocol byte stream is consistent with the request sequence number of the data message analyzed by the receiver, determining that the transmission protocol byte stream is not new data.
4. The method of claim 2, wherein determining whether the format of the transport protocol byte stream is complete comprises:
obtaining a value of a header byte field in the transport protocol byte stream;
judging whether the value of a head byte field of the transmission protocol byte stream is a preset value or not;
if the value of the head byte field of the transmission protocol byte stream is a preset value, determining that the format of the transmission protocol byte stream is complete;
and if the value of the head byte field of the transport protocol byte stream is not a preset value, determining that the format of the transport protocol byte stream is incomplete.
5. The method of claim 1, wherein after receiving the data packet sent by the sender, the method further comprises:
calculating a check code of the data message;
judging whether the calculated check code of the data message is consistent with the value of the check code field of the data message or not, and if so, analyzing the data message; and if the two are not consistent, sending an error notification message to the sender.
6. The method of claim 5, wherein the calculating the check code of the data packet comprises:
and (4) the total byte number of the data message is left to 256, and the check code of the data message is calculated.
7. The method of claim 5, wherein parsing the data packet comprises:
analyzing the message body field of the data message to obtain a data item corresponding to the data message;
and analyzing the operation code field of the data message to obtain the instruction information corresponding to the data message.
8. A data transmission apparatus, applied to a receiving side, the apparatus comprising:
a receiving unit, configured to receive a data packet sent by a sender; the data message is in a binary format and comprises a header byte field, a request sequence number field, an operation code field, an object identification field, a message body length field, a message body field and a check code field;
the sender is an edge gateway, and the receiver is a cloud platform; or, the sender is a cloud platform, and the receiver is an edge gateway.
9. A data transmission device comprising a memory and a processor;
the memory is used for storing programs;
the processor, configured to execute the program, implementing the steps of the data transmission method according to any one of claims 1 to 7.
10. A readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the data transmission method according to any one of claims 1 to 7.
CN202010986839.2A 2020-09-18 2020-09-18 Data transmission method, related equipment and readable storage medium Pending CN112104660A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010986839.2A CN112104660A (en) 2020-09-18 2020-09-18 Data transmission method, related equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010986839.2A CN112104660A (en) 2020-09-18 2020-09-18 Data transmission method, related equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN112104660A true CN112104660A (en) 2020-12-18

Family

ID=73759479

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010986839.2A Pending CN112104660A (en) 2020-09-18 2020-09-18 Data transmission method, related equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN112104660A (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113259418A (en) * 2021-04-25 2021-08-13 深圳市城市交通规划设计研究中心股份有限公司 Method, apparatus and computer-readable storage medium for transmitting data
CN113452480A (en) * 2021-06-21 2021-09-28 青岛海尔科技有限公司 Data transmission method and device and data receiving method and device
CN114222008A (en) * 2021-12-16 2022-03-22 杭州当虹科技股份有限公司 Package and unpacking method based on TCP custom data protocol
CN114362885A (en) * 2022-01-10 2022-04-15 中电望辰科技有限公司 Internet of things data transmission method, device, equipment and medium
CN114374883A (en) * 2021-12-01 2022-04-19 慷智集成电路(上海)有限公司 Data transmission verification method, device and system and vehicle
CN114500328A (en) * 2022-01-20 2022-05-13 深圳市迈睿迈特环境科技有限公司 Data communication method, device and computer readable storage medium
CN115022682A (en) * 2022-06-01 2022-09-06 广州市保伦电子有限公司 Video data transmission verification method based on serdes channel

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070242694A1 (en) * 2006-04-13 2007-10-18 Directpacket Research, Inc. System and method for cross protocol communication
CN104901889A (en) * 2015-05-15 2015-09-09 嘉兴市稠江光电仪器技术有限公司 Remote data collection and control method based on improved-type UDP/IP protocol
CN105471917A (en) * 2016-01-14 2016-04-06 成都麦杰康科技有限公司 Data transmission method and system
CN108306852A (en) * 2017-12-05 2018-07-20 上海金融期货信息技术有限公司 A kind of message-oriented middleware system and method based on simple binary coding
CN109246090A (en) * 2018-08-22 2019-01-18 北京九五智驾信息技术股份有限公司 Data processing equipment, intelligent back vision mirror and data processing system
CN110971704A (en) * 2019-12-11 2020-04-07 杭州安恒信息技术股份有限公司 Data transmission method and device based on JSON configuration file

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070242694A1 (en) * 2006-04-13 2007-10-18 Directpacket Research, Inc. System and method for cross protocol communication
CN104901889A (en) * 2015-05-15 2015-09-09 嘉兴市稠江光电仪器技术有限公司 Remote data collection and control method based on improved-type UDP/IP protocol
CN105471917A (en) * 2016-01-14 2016-04-06 成都麦杰康科技有限公司 Data transmission method and system
CN108306852A (en) * 2017-12-05 2018-07-20 上海金融期货信息技术有限公司 A kind of message-oriented middleware system and method based on simple binary coding
CN109246090A (en) * 2018-08-22 2019-01-18 北京九五智驾信息技术股份有限公司 Data processing equipment, intelligent back vision mirror and data processing system
CN110971704A (en) * 2019-12-11 2020-04-07 杭州安恒信息技术股份有限公司 Data transmission method and device based on JSON configuration file

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113259418A (en) * 2021-04-25 2021-08-13 深圳市城市交通规划设计研究中心股份有限公司 Method, apparatus and computer-readable storage medium for transmitting data
CN113452480A (en) * 2021-06-21 2021-09-28 青岛海尔科技有限公司 Data transmission method and device and data receiving method and device
CN114374883A (en) * 2021-12-01 2022-04-19 慷智集成电路(上海)有限公司 Data transmission verification method, device and system and vehicle
CN114374883B (en) * 2021-12-01 2023-08-15 慷智集成电路(上海)有限公司 Data transmission verification method and device and vehicle
CN114222008A (en) * 2021-12-16 2022-03-22 杭州当虹科技股份有限公司 Package and unpacking method based on TCP custom data protocol
CN114362885A (en) * 2022-01-10 2022-04-15 中电望辰科技有限公司 Internet of things data transmission method, device, equipment and medium
CN114362885B (en) * 2022-01-10 2024-04-26 中电望辰科技有限公司 Data transmission method, communication system, equipment and medium of Internet of things
CN114500328A (en) * 2022-01-20 2022-05-13 深圳市迈睿迈特环境科技有限公司 Data communication method, device and computer readable storage medium
CN115022682A (en) * 2022-06-01 2022-09-06 广州市保伦电子有限公司 Video data transmission verification method based on serdes channel
CN115022682B (en) * 2022-06-01 2024-02-09 广东保伦电子股份有限公司 Video data transmission verification method based on serdes channel

Similar Documents

Publication Publication Date Title
CN112104660A (en) Data transmission method, related equipment and readable storage medium
CN104253741B (en) A kind of method for sending information, relevant apparatus and system
CN110515965B (en) Business document processing method and device, computer equipment and storage medium
CN110912803B (en) IM message transmission method and terminal
CN109120684B (en) Information management method and device, ESB (Enterprise service bus) platform and storage medium
CN105376225A (en) Software-as-a-service method and device
CN112383533A (en) Message format conversion method and device
CN110855555A (en) Mail sending method, device, equipment and computer readable storage medium
CN112087468A (en) Message processing method, related equipment and readable storage medium
CN111651140B (en) Service method and device based on workflow
CN113778708A (en) High-concurrency Push service platform
CN108200543B (en) Short message sending method and device
JP2014523671A (en) Assessing the overall performance of interactive application services
CN108600255B (en) Mock service management method, device, computer equipment and storage medium
CN108306865B (en) Modbus packet-sticking processing method and device based on Netty framework
KR100620331B1 (en) Mms transfer process test system including mms monitoring device for tracing and display mms transfer process, and test method transfer process using the same
CN114138886A (en) Document export method, user side and server side
CN114363268A (en) Message delay consumption method and related product
CN114374737A (en) Message pushing method and device, computer equipment and storage medium
CN111314203B (en) Communication method, device, medium and electronic equipment
CN108683716B (en) business logic learning and protecting method and learning and protecting device based on big data
US20150149614A1 (en) Ascertain tethering of device
CN112422414B (en) Session message processing method, device and computer readable storage medium
CN117376852B (en) Intelligent short message generation and processing method and device, electronic equipment and medium
WO2023279361A1 (en) Methods for sending and receiving information in private network, and related device

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
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20201218