CN114244820A - Embedded distribution system and data communication method thereof - Google Patents
Embedded distribution system and data communication method thereof Download PDFInfo
- Publication number
- CN114244820A CN114244820A CN202010929941.9A CN202010929941A CN114244820A CN 114244820 A CN114244820 A CN 114244820A CN 202010929941 A CN202010929941 A CN 202010929941A CN 114244820 A CN114244820 A CN 114244820A
- Authority
- CN
- China
- Prior art keywords
- server
- client
- interface file
- file
- call request
- 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
- 238000004891 communication Methods 0.000 title claims abstract description 57
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000003993 interaction Effects 0.000 claims abstract description 58
- 238000011161 development Methods 0.000 abstract description 18
- 230000008569 process Effects 0.000 abstract description 10
- 230000015654 memory Effects 0.000 description 12
- 230000006870 function Effects 0.000 description 7
- 238000012856 packing Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004590 computer program 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
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses an embedded distribution system and a data communication method thereof, wherein the embedded distribution system comprises a client and a server, and the data communication method comprises the following steps: the method comprises the steps of creating a protocol description file in advance, compiling the protocol description file to generate a first interface file and a second interface file, compiling the first interface file to a client and compiling the second interface file to a server; the client converts the call request into a byte stream through the first interface file and sends the byte stream to the server, wherein the call request is used for calling the service deployed on the server; and the server converts the byte stream through the second interface file to obtain a calling request, and provides corresponding service for the client according to the calling request. The method can realize the data interaction of the embedded distribution system, does not need to consider the communication of the underlying network, effectively reduces the error rate in the data interaction process, reduces the development time and shortens the development period.
Description
Technical Field
The present invention relates to the field of embedded technologies, and in particular, to a data communication method for an embedded distribution system and an embedded distribution system.
Background
Generally, when the single chip microcomputer performs data interaction with the outside, for example, data interaction with a computer, a communication interaction protocol is mainly formulated, and data packing and unpacking codes are written in a computer end and a single chip microcomputer end respectively, so as to realize protocol data interaction.
However, this method is cumbersome and prone to parsing or packing errors, and after the communication interaction protocol is determined, it often takes a long time (e.g., a week) to parse, pack, and debug the data protocol, and once the protocol is changed, the data protocol needs to be parsed, packed, and debugged again, which results in a long development period.
Disclosure of Invention
The present invention is directed to solving, at least in large part, one of the technical problems in the related art. Therefore, a first objective of the present invention is to provide a data communication method for an embedded distribution system, which not only can implement data interaction of the embedded distribution system, but also does not need to consider underlying network communication, thereby effectively reducing error rate in the data interaction process, reducing development time, and shortening development period.
A second object of the present invention is to provide an embedded distribution system.
In order to achieve the above object, an embodiment of a first aspect of the present invention provides a data communication method for an embedded distributed system, where the embedded distributed system includes a client and a server, and the data communication method includes the following steps: the method comprises the steps of creating a protocol description file in advance, compiling the protocol description file to generate a first interface file and a second interface file, compiling the first interface file to a client and compiling the second interface file to a server; the client converts the call request into a byte stream through the first interface file and sends the byte stream to the server, wherein the call request is used for calling the service deployed on the server; and the server converts the byte stream through the second interface file to obtain a calling request, and provides corresponding service for the client according to the calling request.
According to the data communication method of the embedded distribution system, the protocol description file is created in advance, the protocol description file is compiled to generate the first interface file and the second interface file, the first interface file is compiled to the client side, the second interface file is compiled to the server side, and data interaction between the client side and the server side is conducted through the first interface file and the second interface file. The method can realize the data interaction of the embedded distribution system, does not need to consider the communication of the underlying network, effectively reduces the error rate in the data interaction process, reduces the development time and shortens the development period.
In addition, the data communication method of the embedded distribution system according to the above embodiment of the present invention may further have the following additional technical features:
according to one embodiment of the invention, the client is located in an MCU or a device with an operating system; the server is located in the MCU or the equipment with the operating system.
According to one embodiment of the invention, when the client is located in the MCU and the server is located in the device with the operating system, or the client is located in the device with the operating system and the server is located in the MCU, the client and the server perform data interaction through a streaming protocol.
According to one embodiment of the invention, the streaming protocol comprises one of a CAN communication protocol, a USB communication protocol, and a serial communication protocol.
According to one embodiment of the invention, creating a protocol description file comprises: and defining a service interface for data interaction between the client and the server.
According to one embodiment of the invention, the first interface file and the second interface file are both executable files, wherein the first interface file is used for serializing the call request to obtain a byte stream; the second interface file is used for deserializing the byte stream to obtain a call request.
In order to achieve the above object, a second embodiment of the present invention provides an embedded distribution system, including: the client converts a calling request into a byte stream through a first interface file and sends the byte stream to the server, wherein the calling request is used for calling a service deployed on the server, and the first interface file is generated by compiling a protocol description file created in advance; and the server converts the byte stream through a second interface file to obtain a calling request, and provides corresponding service for the client according to the calling request, wherein the second interface file is generated by compiling a protocol description file created in advance.
According to the embedded distribution system provided by the embodiment of the invention, the pre-created protocol description file is compiled to generate the first interface file and the second interface file, so that data interaction between the client and the server is performed through the first interface file and the second interface file, and therefore, the data interaction of the embedded distribution system can be realized, the underlying network communication does not need to be considered, the error rate in the data interaction process is effectively reduced, the development time is reduced, and the development period is shortened.
In addition, the embedded distribution system according to the above embodiment of the present invention may further have the following additional technical features:
according to one embodiment of the invention, the client is located in an MCU or a device with an operating system; the server is located in the MCU or the equipment with the operating system.
According to one embodiment of the invention, the protocol description file comprises: and the client and the server carry out data interaction.
According to one embodiment of the invention, the first interface file and the second interface file are both executable files, wherein the first interface file is used for serializing the call request to obtain a byte stream; the second interface file is used for deserializing the byte stream to obtain a call request.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
FIG. 1 is a flow chart of a method of data communication for an embedded distributed system according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an embedded distribution system according to an embodiment of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative and intended to be illustrative of the invention and are not to be construed as limiting the invention.
Generally, when the single chip microcomputer performs data interaction with the outside, for example, data interaction with a computer, a communication interaction protocol is mainly formulated, and data packing and unpacking codes are written in a computer end and a single chip microcomputer end respectively, so as to realize protocol data interaction. However, this method is cumbersome and prone to parsing or packing errors, and after the communication interaction protocol is determined, it often takes a long time (e.g., a week) to parse, pack, and debug the data protocol, and once the protocol is changed, the data protocol needs to be parsed, packed, and debugged again, which results in a long development period.
For data interaction, if it is placed in the internet industry, there is a good solution, for example, RPC (Remote Procedure Call) technology can be used, which allows one computer program to remotely Call a subprogram or a sub-service of another computer without concern for underlying network communication. For example, the solution of the net under microsoft is WCF (Windows Communication Foundation, Windows Communication development platform), but the single chip cannot run the Windows system, and thus cannot run the net; for another example, Google develops a GRPC based on C + + language, but the GRPC has a huge Runtime (a set of API based on C), and the single chip cannot run; for another example, the GitHub has a Nanopb developed by using the IDL (Interactive Data Language) of Protobuf, but since Protobuf does not have a 1-byte Data type such as uin 8, uin 16, sint8 or sint16, and the one-chip microcomputer communication often has a large amount of uin 8, uin 16, sint8 or sint16, it does not have applicability, of course, when a communication protocol is formulated, 32-bit types supported by Protobuf can be used, but this wastes much memory space, and the one-chip microcomputer is just extremely sensitive to memory, and meanwhile, the Nanopb is only a serialization and deserialization library, not RPC, and does not have serialization and deserialization functions; additionally, there is also a Flatcc on GitHub, which is also just a serialization and deserialization library. Therefore, the above solutions all cannot effectively solve the problem of data interaction of the single chip microcomputer, and all the above solutions adopt TLV or TTLV encoding schemes, which have high memory requirements and are not suitable for the single chip microcomputer.
Based on this, the applicant proposes a distributed data Communication framework MCUCF (microcontroller Unit Communication foundation) capable of operating in environments such as embedded systems and low-end controllers with extremely limited memories, such as MCUs, and provides a data Communication method of an embedded distribution system and an embedded distribution system based on the MCUCF.
A data communication method of an embedded distribution system and an embedded distribution system proposed according to an embodiment of the present invention are described below with reference to the accompanying drawings.
Fig. 1 is a flowchart of a data communication method of an embedded distribution system according to an embodiment of the present invention, where the embedded distribution system includes a client and a server. Referring to fig. 1, the data communication method of the embedded distribution system may include the steps of:
step S101, a protocol description file is created in advance, compiled to generate a first interface file and a second interface file, and the first interface file is compiled to a client and the second interface file is compiled to a server.
Specifically, before data interaction is performed between the client and the server, a protocol description file, which is also called an interface definition file or code, is created, and is mainly used for defining an interface, and then the protocol description file is compiled to generate a first interface file and a second interface file, where the first interface file is also called a first interface specific implementation file or code, and the second interface file is also called a second interface specific implementation file or code, and the first interface file is compiled into the client, and the second interface file is compiled into the server, so that data interaction between the client and the server is realized through the first interface file and the second interface file.
According to one embodiment of the invention, creating the protocol description file may comprise: and defining a service interface for data interaction between the client and the server.
Specifically, in practical applications, a protocol description file may be created through IDL, where the protocol description file includes definitions of service interfaces for data interaction between a client (e.g., a computer) and a server (e.g., an MCU).
For example, taking the summation function GetSum () as an example, the corresponding protocol description file is shown as follows and named Demo:
a using System; the System namespace contains base classes and base classes that define common values and reference data types, events and event handlers, interfaces, properties, and handle exceptions
using MCUCF; v. reference the namespace named MCUCF which contains the definition of the IOptinoprocess interface @ is a @ is a @ is a @ is a @ is a @ is @ is a @ is a @ is a name of the MCUCF name
In the protocol description file, a service interface for data interaction between the client and the server is defined through interface DemoInter { }, and some configuration items such as the name of an interface file to be generated are defined through public class operation process { }, which may include definitions of access forms of byte streams, for example.
After the protocol description file is created, the protocol description file may be compiled, and for example, the first interface file and the second interface file may be generated by an mcucf.
Mcucf. exe demo. cs-o. directory
Where, -o denotes a storage directory or location of the generated first interface file and second interface file.
After the first interface file and the second interface file are generated, the first interface file is compiled to the client, and the second interface file is compiled to the server, so that data interaction between the client and the server is facilitated.
Step S102, the client converts the call request into a byte stream through the first interface file and sends the byte stream to the server, wherein the call request is used for calling the service deployed on the server.
Step S103, the server converts the byte stream through the second interface file to obtain a call request, and provides corresponding service to the client according to the call request.
Specifically, when the client and the server perform data interaction, the client can convert the call request into a byte stream through the first interface file and send the byte stream to the server so as to call the service deployed on the server, then the server converts the byte stream through the second interface file so as to obtain the call request, provides the corresponding service for the client according to the call request, and feeds back the processing result to the client.
According to one embodiment of the invention, the first interface file and the second interface file are both executable files, wherein the first interface file is used for serializing the call request to obtain a byte stream; the second interface file is used for deserializing the byte stream to obtain a call request.
That is to say, when data interaction is performed between the client and the server, the call request is serialized through the first interface file to obtain a corresponding byte stream, then the byte stream is transmitted to the server, then the server performs deserialization on the received byte stream through the second interface file to obtain the call request, and provides corresponding service for the client according to the call request.
For example, still taking the summation function GetSum () as an example, when the client performs data interaction with the server, the following call request may be set at the client:
auto r ═ client.request.getsum (1, 3); v/Call summation function GetSum ()
Meanwhile, the following services are set at the server side:
during data interaction, when a client executes a client request GetSum (1,3), a first interface file in the client serializes the call request to convert the call request into a Byte stream, the Byte stream is transmitted to a server, the server receives the Byte stream and deserializes the Byte stream through a second interface file to obtain the call request sent by the client, and calls Demo _ GetSumServer according to the call request, wherein GetSum (Int 32A, Byte B) is used for summing 1 and 3, and a summation result 4 is fed back to the client. If the r.return value of the client is 4, the data interaction is successful. Therefore, when a client (such as a computer) and a server (such as an MCU) carry out data interaction, a corresponding protocol description file can be written firstly, an executable file or a code is generated by one key, and then the executable file or the code is integrated into a project, so that the problem of data interaction does not need to be considered in the data interaction process, namely the problem of underlying network communication does not need to be considered, only corresponding calling is needed, the writing and debugging of related codes for protocol conversion are avoided, the development speed is greatly improved, for example, when the program is used in a TBOX (vehicle-mounted networking terminal) project of intelligent networking, the work of a data interaction part can be omitted, and the time of about 1 to 3 weeks is saved for the project; meanwhile, when the generated executable file or code runs, the memory occupation is small, so that the 8-32 bit low-end controller MCU can run completely, and the problem of insufficient memory is effectively solved.
In the embodiment, the protocol description file is created in advance, the protocol description file is compiled to generate the first interface file and the second interface file, the first interface file is compiled to the client and the second interface file is compiled to the server, and data interaction between the client and the server is performed through the first interface file and the second interface file, so that data interaction of an embedded distribution system, such as data interaction between a low-end controller (MCU) and a computer, can be realized, underlying network communication does not need to be considered, the error rate in the data interaction process is effectively reduced, the development time is reduced, and the development period is shortened.
According to one embodiment of the invention, the client is located in an MCU or a device with an operating system; the server is located in the MCU or the equipment with the operating system. That is to say, the data communication method of the present application can be used not only in a low-end controller such as an MCU with a very limited memory, but also in devices with operating systems such as Windows, Linux, and android NDK, i.e., can be used in a cross-platform manner. Furthermore, the method can be used for data interaction between different processes in the MCU, data interaction between different MCUs, and data interaction between the MCU and equipment with an operating system, such as a computer and the like. Meanwhile, the data stream can be analyzed not only by C + +, but also by other languages, such as C #, i.e., can be used across languages.
Further, according to an embodiment of the present invention, when the client is located in the MCU and the server is located in the device having the operating system, or the client is located in the device having the operating system and the server is located in the MCU, the client and the server perform data interaction through a streaming protocol, where the streaming protocol includes one of a CAN communication protocol, a USB communication protocol, and a serial communication protocol. That is to say, when data interaction between the MCU and a device having an operating system, such as a computer, is realized by the data communication method of the present application, the stream protocol is not limited, for example, a CAN communication protocol, a USB communication protocol, a serial communication protocol, etc. may be used, and the stream protocol may be specifically selected according to actual requirements.
In summary, according to the data communication method of the embedded distribution system in the embodiment of the present invention, not only the data interaction of the embedded distribution system can be realized, but also the underlying network communication does not need to be considered, so that the error rate in the data interaction process is effectively reduced, the development time is reduced, the development period is shortened, and the applicability is strong.
Fig. 2 is a schematic structural diagram of an embedded distribution system according to an embodiment of the present invention, and referring to fig. 2, the embedded distribution system may include: a client 10 and a server 20.
The client 10 converts a call request into a byte stream through a first interface file and sends the byte stream to the server 20, wherein the call request is used for calling a service deployed on the server 20, and the first interface file is generated by compiling a protocol description file created in advance; the server 20 converts the byte stream through a second interface file to obtain a call request, and provides a corresponding service to the client 10 according to the call request, where the second interface file is generated by compiling a protocol description file created in advance.
According to one embodiment of the invention, the client 10 is located in an MCU or a device with an operating system; the server 20 is located in an MCU or a device with an operating system.
According to one embodiment of the invention, the protocol description file comprises: and the client 10 and the server 20 are used for data interaction.
According to one embodiment of the invention, the first interface file and the second interface file are both executable files, wherein the first interface file is used for serializing the call request to obtain a byte stream; the second interface file is used for deserializing the byte stream to obtain a call request.
It should be noted that, for the description of the embedded distribution system in the present application, please refer to the description of the data communication method of the embedded distribution system in the present application, and details are not repeated herein.
According to the embedded distribution system provided by the embodiment of the invention, the pre-created protocol description file is compiled to generate the first interface file and the second interface file, so that data interaction between the client and the server is performed through the first interface file and the second interface file, and therefore, the data interaction of the embedded distribution system can be realized, the underlying network communication does not need to be considered, the error rate in the data interaction process is effectively reduced, the development time is reduced, and the development period is shortened.
It should be noted that the logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
In the present invention, unless otherwise expressly stated or limited, the terms "mounted," "connected," "secured," and the like are to be construed broadly and can, for example, be fixedly connected, detachably connected, or integrally formed; can be mechanically or electrically connected; they may be directly connected or indirectly connected through intervening media, or they may be connected internally or in any other suitable relationship, unless expressly stated otherwise. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (10)
1. A data communication method of an embedded distribution system is characterized in that the embedded distribution system comprises a client and a server, and the data communication method comprises the following steps:
a protocol description file is created in advance, and is compiled to generate a first interface file and a second interface file, and the first interface file is compiled to the client and the second interface file is compiled to the server;
the client converts a call request into a byte stream through the first interface file and sends the byte stream to the server, wherein the call request is used for calling the service deployed on the server;
and the server converts the byte stream through the second interface file to obtain the call request, and provides corresponding service for the client according to the call request.
2. The data communication method of the embedded distributed system according to claim 1, wherein the client is located in an MCU or a device having an operating system; the server is located in the MCU or the equipment with the operating system.
3. The data communication method of the embedded distributed system according to claim 2, wherein when the client is located in the MCU and the server is located in the device with the operating system, or when the client is located in the device with the operating system and the server is located in the MCU, the client and the server perform data interaction through a streaming protocol.
4. The data communication method of the embedded distribution system according to claim 3, wherein the streaming protocol includes one of a CAN communication protocol, a USB communication protocol, and a serial communication protocol.
5. The data communication method of the embedded distribution system according to any one of claims 1 to 4, wherein the creating a protocol description file comprises:
and defining a service interface for data interaction between the client and the server.
6. The data communication method of the embedded distribution system according to claim 5, wherein the first interface file and the second interface file are both executable files, wherein the first interface file is used for serializing the call request to obtain the byte stream; the second interface file is used for deserializing the byte stream to obtain the call request.
7. An embedded distributed system, comprising: a client side and a server side, wherein,
the client converts a call request into a byte stream through a first interface file and sends the byte stream to the server, wherein the call request is used for calling the service deployed on the server, and the first interface file is generated by compiling a protocol description file created in advance;
and the server converts the byte stream through a second interface file to obtain the call request, and provides corresponding service for the client according to the call request, wherein the second interface file is generated by compiling the protocol description file which is created in advance.
8. The embedded distribution system of claim 7, wherein the client is located in an MCU or a device with an operating system; the server is located in the MCU or the equipment with the operating system.
9. The embedded distribution system of claim 7 or 8, wherein the protocol description file comprises: and the client and the server carry out data interaction.
10. The embedded distribution system of claim 9, wherein the first interface file and the second interface file are both executable files, wherein the first interface file is configured to serialize the call request to obtain the byte stream; the second interface file is used for deserializing the byte stream to obtain the call request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010929941.9A CN114244820A (en) | 2020-09-07 | 2020-09-07 | Embedded distribution system and data communication method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010929941.9A CN114244820A (en) | 2020-09-07 | 2020-09-07 | Embedded distribution system and data communication method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114244820A true CN114244820A (en) | 2022-03-25 |
Family
ID=80742463
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010929941.9A Pending CN114244820A (en) | 2020-09-07 | 2020-09-07 | Embedded distribution system and data communication method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114244820A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262560A (en) * | 2010-05-27 | 2011-11-30 | 阿里巴巴集团控股有限公司 | Calling method, device and system for remote service |
| CN105335310A (en) * | 2014-06-05 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Interface defining method, and data transmission method and apparatus |
| CN105763619A (en) * | 2016-03-31 | 2016-07-13 | 广州华多网络科技有限公司 | Method and device for communication of client and server |
| CN109886692A (en) * | 2019-03-08 | 2019-06-14 | 泰康保险集团股份有限公司 | Data transmission method, device, medium and electronic equipment based on block chain |
| CN110300082A (en) * | 2018-03-21 | 2019-10-01 | 腾讯科技（深圳）有限公司 | A kind of interface creation method, device and storage medium |
| CN111338717A (en) * | 2020-03-27 | 2020-06-26 | 广州华多网络科技有限公司 | Interface calling method, application program upgrading method, server and client |
-
2020
- 2020-09-07 CN CN202010929941.9A patent/CN114244820A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262560A (en) * | 2010-05-27 | 2011-11-30 | 阿里巴巴集团控股有限公司 | Calling method, device and system for remote service |
| CN105335310A (en) * | 2014-06-05 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Interface defining method, and data transmission method and apparatus |
| CN105763619A (en) * | 2016-03-31 | 2016-07-13 | 广州华多网络科技有限公司 | Method and device for communication of client and server |
| CN110300082A (en) * | 2018-03-21 | 2019-10-01 | 腾讯科技（深圳）有限公司 | A kind of interface creation method, device and storage medium |
| CN109886692A (en) * | 2019-03-08 | 2019-06-14 | 泰康保险集团股份有限公司 | Data transmission method, device, medium and electronic equipment based on block chain |
| CN111338717A (en) * | 2020-03-27 | 2020-06-26 | 广州华多网络科技有限公司 | Interface calling method, application program upgrading method, server and client |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111083225B (en) | Data processing method and device in Internet of things platform and Internet of things platform | |
| CN111176626B (en) | Cross-programming-language code calling method and device, medium and equipment | |
| US7752598B2 (en) | Generating executable objects implementing methods for an information model | |
| JP2007234047A (en) | Method and apparatus for transporting interface definition language-defined data structure between heterogeneous systems | |
| CN112685035B (en) | Project development method and device, computer readable storage medium and electronic equipment | |
| WO2008058473A1 (en) | Mapping method in the program testing system and program testing system | |
| US20040268301A1 (en) | Adding new compiler methods to an integrated development environment | |
| WO2023124425A1 (en) | Data processing method and apparatus, electronic device, and storage medium | |
| CN111740948A (en) | Data packet issuing method, dynamic updating method, device, equipment and medium | |
| CN112667287A (en) | Method, device and equipment for creating rule file and computer readable storage medium | |
| CN111913741A (en) | Object interception method, device, medium and electronic equipment | |
| US8997116B2 (en) | Event logging application programming interface (API) | |
| CN113434147B (en) | Method and device for analyzing message based on ProtoBuf protocol | |
| CN113660307A (en) | Algorithm comprehensive integrated service system | |
| CN106775916B (en) | Method and device for reducing application installation packages and electronic equipment | |
| CN114244820A (en) | Embedded distribution system and data communication method thereof | |
| CN116841559A (en) | Transcoding method, device, apparatus, medium and program product | |
| CN116166457A (en) | Data processing method and related equipment | |
| CN111970349B (en) | Communication system, method, device, equipment and medium based on remote procedure call | |
| CN112711602B (en) | Method and device for running stored procedure, database system and storage medium | |
| CN110908665A (en) | Jenkins construction plug-in development optimization method and system | |
| JP2007141248A (en) | Support in method references in java language | |
| CN114443316B (en) | Object access method and device and electronic equipment | |
| US20170031660A1 (en) | Methods for utilizing powershell modules in .net applications and devices thereof | |
| CN116521149A (en) | Vehicle service script generation method and device, electronic equipment and storage medium |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20220325 |