CN109067754B - Communication method and system for request terminal and server terminal - Google Patents
Communication method and system for request terminal and server terminal Download PDFInfo
- Publication number
- CN109067754B CN109067754B CN201810940776.XA CN201810940776A CN109067754B CN 109067754 B CN109067754 B CN 109067754B CN 201810940776 A CN201810940776 A CN 201810940776A CN 109067754 B CN109067754 B CN 109067754B
- Authority
- CN
- China
- Prior art keywords
- message
- request
- byte stream
- server
- area
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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
Abstract
The invention belongs to the technical field of software communication, and discloses a communication method and a system of a request end and a service end, wherein the request end and the service end are communicated through ASN.1 serialized byte stream messages, a memory copy mode is adopted for communication in a process, the communicated messages adopt a layered design comprising message headers and message bodies, and the message bodies comprise request messages or reply messages; only the request message needs to be filled when the request is sent; only the reply message needs to be filled when a result is returned; the adaptive memory allocation strategy is adopted in the process of receiving the byte stream to improve the memory reuse rate, so that the coding and decoding efficiency is improved, and the system bottleneck of a fixed memory management strategy is overcome; the communication method and the system based on the ASN.1 solve the problems of easy error and difficult maintenance of communication by adopting a character string protocol and a binary stream protocol through the structured data of the ASN.1.
Description
Technical Field
The present invention belongs to the technical field of information communication, and more particularly, to a method and a system for communication between a request side and a service side.
Background
In the communication application of middle and small software, the message format is mostly self-defined, such as a protocol expressed by ASCII codes and a TLV (threshold value Length value) protocol of binary streams, and the protocol adopting character strings and binary streams needs to be newly added for processing byte streams each time when the protocol is newly added, so that the compatibility is poor, errors are easy to occur, the maintenance workload is increased, and the development speed is influenced.
ASN.1(Abstract Syntax Notation One) Abstract Syntax Notation description language is a set of standards used to describe the representation, coding, transmission, decoding of data. It provides a formal, unambiguous and precise set of rules to describe the structure of an object independent of the particular computer hardware. Asn.1 itself defines only the abstract syntax for representing information, and does not define the method of encoding it. Various asn.1 coding rules provide a transport syntax for the values of data whose abstract syntax is described by the asn.1. The standard asn.1 coding Rules include Basic coding Rules (BER), Canonical coding Rules (CER), unique coding Rules (DER), Packed coding Rules (PER), and XML coding Rules (XER).
Disclosure of Invention
Aiming at the defects or the improvement requirements of the prior art, the invention provides a communication method and a communication system of a request end and a service end, wherein the request end and the service end are communicated through ASN.1 serialized byte stream messages, and the communication method and the communication system aim at solving the problems of high error probability and difficult maintenance when a character string protocol and a binary stream protocol are adopted for communication.
To achieve the above object, according to an aspect of the present invention, there is provided a method for a requester to communicate with a server, including:
s10, the request end generates a request message containing a message header and a message body under the request trigger; the message head comprises a function ID, a device ID and a request ID, and the message body comprises a request message;
s20, the request end encodes the request message into ASN.1 byte stream data and sends the data to the server end;
s30, the server side receives the byte stream data, decodes the received byte stream data, decodes the message header first, and forwards the message header to the corresponding processing module according to the segmented mark of the analyzed function ID;
the function ID segment mark is a segment representation mode which uses the first bits in the message header to represent the ID of the processing module;
s40, the server side searches the corresponding request message definition according to the request ID and decodes the request data;
and S50, when the requested service processing is finished, the server side fills the reply message and returns the filled message to the request side according to the message header.
Preferably, in the communication method between the request side and the server side, the request side is a client side or other server sides.
Preferably, in the communication method between the request side and the service side, in the processing of receiving the byte stream by the service side, the following memory management method is adopted:
s31, initializing a memory block, wherein the memory block comprises a decoded area, an un-decoded area and a free area;
s32, when the byte stream is received,
when the length of the byte stream is smaller than that of the idle area, directly copying the byte stream to the idle area, and setting the corresponding idle area as an un-decoded area;
when the length of the byte stream is greater than the idle area and the length of the byte stream is less than the sum of the idle area and the decoded area, combining the decoded area and the idle area to form a new idle area, and copying the byte stream to the new idle area;
when the length of the byte stream is larger than the sum of the idle area and the decoded area, the memory block is expanded according to the sum of the length of the byte stream and the length of the un-decoded area, and the byte stream is copied to the expanded memory block.
Preferably, in the communication method between the request side and the service side, a processing method of forward and backward compatibility of the messages including the asn.1 is adopted in the decoding processing, so as to realize forward and backward compatibility when the request side and the service side adopt different versions of the messages; the method comprises the following specific steps:
s41, backward compatibility method:
when the request end uses a low version message, the server end uses a high version message, the server end receives a low version message request, and in the decoding process using the high version message, one of the following conditions is met, namely the decoding is successful:
i, the length of the current message byte stream is completely decoded and has no abnormity;
ii. The current decoding message is completely analyzed and has no abnormity;
s42, forward compatibility method:
when the request end uses the high version message, the server end uses the low version message, the server end receives the high version request, and in the decoding process using the low version message, one of the following conditions is met, namely the decoding success is represented;
I. the length of the current message byte stream is completely decoded, and no abnormity exists;
II. The current decoded message is completely analyzed and has no abnormity.
To achieve the object, according to another aspect of the present invention, there is provided a communication system of a request side and a service side, comprising
The request end message generating module is used for generating a request message containing a message header and a message body under the request trigger; the message head comprises a function ID, a device ID and a request ID, and the message body comprises a request message;
the request end message forwarding module is used for coding the message into ASN.1 byte stream data and sending the ASN.1 byte stream data to the server end;
the server side forwarding module is used for receiving the byte stream at the server side, decoding the received byte stream, decoding a message header firstly, and forwarding the message header to the corresponding processing module according to the segmented mark of the analyzed function ID;
the function ID segment mark is a segment representation mode which uses the first bits in the message header to represent the ID of the processing module;
the message sending module is used for filling the reply message after the requested service is processed, and returning the filled message to the request end according to the received message header;
and the server processing module is used for searching the corresponding request message definition according to the request ID in the message header and decoding the request data.
Preferably, in the communication system between the request side and the service side, the request side is a client side or other service sides.
Preferably, in the communication system between the request side and the server side, the server side forwarding module of the communication system adopts the following memory management method in the process of receiving the byte stream:
s31, initializing a memory block, wherein the memory block comprises a decoded area, an un-decoded area and a free area;
s32, when the byte stream is received,
when the length of the byte stream is smaller than that of the idle area, directly copying the byte stream to the idle area, and setting the corresponding idle area as an un-decoded area;
when the length of the byte stream is greater than the idle area and the length of the byte stream is less than the sum of the idle area and the decoded area, combining the decoded area and the idle area to form a new idle area, and copying the byte stream to the new idle area;
when the length of the byte stream is larger than the sum of the idle area and the decoded area, the memory block is expanded according to the sum of the length of the byte stream and the length of the un-decoded area, and the byte stream is copied to the expanded memory block.
Preferably, in the communication system between the request side and the service side, the service side forwarding module of the communication system adopts a processing method of forward and backward compatibility of the messages including the asn.1 in the decoding processing, so as to realize forward and backward compatibility when the request side and the service side adopt different versions of the messages; the method comprises the following specific steps:
s41, backward compatibility method:
when the request end uses a low version message, the server end uses a high version message, the server end receives a low version message request, and in the decoding process using the high version message, one of the following conditions is met, namely the decoding is successful:
i. the length of the current message byte stream is completely decoded, and no abnormity exists;
ii. The current decoding message is completely analyzed and has no abnormity;
s42, forward compatibility method:
when the request end uses the high version message, the server end uses the low version message, the server end receives the high version request, and in the decoding process using the low version message, one of the following conditions is met, namely the decoding success is represented;
I. the length of the current message byte stream is completely decoded, and no abnormity exists;
II. The current decoded message is completely analyzed and has no abnormity.
In general, compared with the prior art, the above technical solution contemplated by the present invention can achieve the following beneficial effects:
(1) according to the communication method and system of the request end and the server end, the client end and the server end as well as the server end and the server end are communicated through ASN.1 serialized byte stream messages, a memory copy mode is adopted for communication in a process, based on ASN.1 abstract language, due to the ASN.1 structured information characteristic, developers do not need to pay attention to coding and decoding work of each protocol, the error probability of a newly added protocol is reduced, and when character strings and binary streams are adopted, the byte stream processing needs to be newly added for each newly added protocol; compared with the prior art, the method provided by the invention has the advantages that the development speed is increased, the maintenance workload is reduced, and the problems of high possibility of errors and difficult maintenance in communication by adopting a character string protocol and a binary stream protocol are solved.
(2) The communication method and the system of the request terminal and the server terminal provided by the invention have the advantages that the communication message adopts a layered design comprising a message header and a message body, and the message body comprises a request message or a reply message; the realization of the hierarchical design and the forwarding module simplifies the programming complexity of CS framework software; when a request end sends a request, only a request message needs to be filled; when the server returns the result, only the reply message needs to be filled, and the method for processing the code division scene of the message improves the overall operation efficiency of the software.
(3) The communication method and the communication system of the request end and the server end have the advantages that the front and back compatible processing modes are consistent, the version of the message does not need to be sensed, and special marks do not need to be made on the version of the message, so that the coding mode and the corresponding processing flow are simplified.
(4) The communication method and the communication system of the request terminal and the service terminal adopt the self-adaptive memory allocation strategy during the receiving of the byte stream, can improve the memory reuse rate, further improve the coding and decoding efficiency, and overcome the system bottleneck of a fixed memory management strategy.
Drawings
Fig. 1 is a schematic communication flow diagram of an embodiment of a communication method between a request end and a service end provided by the present invention;
FIG. 2 is a schematic diagram of a communication architecture of an embodiment of a communication method between a request end and a service end provided by the present invention;
fig. 3 is a schematic flow chart of a byte stream memory management method in an embodiment of a communication method between a request side and a service side provided by the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
Referring to fig. 1 to fig. 3, a communication method between a request side and a service side according to an embodiment is specifically described.
According to the communication method of the request terminal and the server terminal provided by the embodiment, the flow of the communication between the request terminal and the server terminal comprises the following steps:
s10, under the trigger of a User Interface (UI) of the request end, the request end generates a request message containing a message header and a message body; the message header comprises a function ID, a device ID and a request ID, and the message body comprises a request message.
The request end UI trigger comprises software button trigger, binding entity shortcut key trigger or automatic function item trigger; when a request end sends a request, only a request message needs to be filled; when the server returns the result, only the reply message needs to be filled. In the embodiment, the UI message is assembled and then is transmitted by calling the interface function of the forwarding module.
S20, encoding the request message into ASN.1 byte stream data, and sending the data to the server through the network;
the assembled message is coded into ASN.1 byte stream data through a client forwarding module and is sent to a server through a TCP (transmission control protocol);
in an embodiment, the coding rule uses BER coding, and the coding and decoding of each message, request message and reply message are automatically generated by the tool.
And S30, the server decodes the message header and forwards the message header to a corresponding processing module.
The server receives the byte stream data, decodes the received byte stream data through the forwarding module, decodes a message header first, and forwards the message header to the corresponding processing module according to the segmented mark of the analyzed function ID;
the function ID segment identifier is a segment representation that uses the first few bits in the message header to represent the processing module ID.
In the ASN.1 decoding process, memory blocks with continuous addresses are required to be utilized, and a one-dimensional array is adopted in the embodiment of the invention to store byte streams. Referring to fig. 3, in a process of receiving a byte stream, a preferred embodiment provides a memory management method, which specifically includes the following steps:
s31, initializing a memory block, wherein the memory block comprises a decoded area, an un-decoded area and a free area;
s32, receiving byte stream processing:
when the length of the byte stream is smaller than that of the idle area, directly copying the byte stream to the idle area, and setting the corresponding idle area as an un-decoded area;
when the length of the byte stream is greater than the idle area and the length of the byte stream is less than the sum of the idle area and the decoded area, combining the decoded area and the idle area to form a new idle area, and copying the byte stream to the new idle area;
when the length of the byte stream is larger than the sum of the idle area and the decoded area, the memory block is expanded according to the sum of the length of the byte stream and the length of the un-decoded area, and the byte stream is copied to the expanded memory block.
By the self-adaptive memory allocation strategy, the memory reuse rate can be improved, the coding and decoding efficiency is further improved, and the system bottleneck of a fixed memory management strategy is overcome. In another embodiment, the memory management method is implemented by QByteArray, such as Qt, or a dynamic array.
S40, the server processing module searches the corresponding request message definition according to the request ID in the message header and decodes the specific request data;
the problem of communication protocol versions exists between different versions of the same software, and differences exist between messages of different versions, for example, a Ver2.0 message increases a parameter autoUpdate relative to a Ver1.0 message, so that the decoding is difficult; particularly for CS (client-server) architecture software, the problem of protocol version compatibility between a client and a server is an important problem of software front-back version compatibility.
In the decoding process, a preferred embodiment provides a processing method for realizing forward and backward compatibility of messages containing ASN.1, and forward and backward compatibility is realized under the condition that a client and a server adopt messages with different versions; the method comprises the following specific steps:
s41, backward compatibility method:
when the client uses a low version message such as a Ver1.0 message, the server uses a high version message such as a Ver2.0 message, the server receives a request of the low version message such as a Ver1.0 message, and during decoding using the high version message such as a Ver2.0 message, one of the following conditions is satisfied, that is, the decoding is successful:
i. the length of the current message byte stream is completely decoded, and no abnormity exists;
ii. The current decoding message is completely analyzed and has no abnormity;
s42, forward compatibility method:
the client uses a high version such as a Ver2.0 message, the server uses a low version such as a Ver1.0 message, the server receives a request of the high version such as the Ver2.0 message, and when one of the following conditions is met in the decoding process of using the low version such as the Ver1.0 message, the decoding is successful;
I. the length of the current message byte stream is completely decoded, and no abnormity exists;
II. The current decoded message is completely analyzed and has no abnormity.
By adopting the method, the processing modes which are compatible before and after are consistent, the version of the message does not need to be sensed, and special marks do not need to be made on the version of the message, thereby playing the role of simplifying the coding mode and the corresponding processing flow.
And S50, when the requested service processing is finished, filling the reply message, and returning to the request end according to the received message header. The request end may be a client end or other service ends.
The request end receives the byte stream of the result message, and the method comprising the steps of S31 and S32 is adopted for processing; the decoding compatibility of the result message is processed by adopting the methods including S41 and S42.
According to the communication method and system of the request terminal and the server terminal, the client terminal and the server terminal, as well as the server terminal and the server terminal can communicate through ASN.1 serialized byte stream messages, and the problems of high error probability and difficult maintenance of a character string protocol and a binary stream protocol are solved based on the structured data of the ASN.1.
The message adopts the layered design comprising a message header and a message body, and the routing information in the message header enables the message to have flexible transmission capability, for example, a client UI can access a processing module of any server in a known server group, and the servers can also communicate with other servers according to the routing information in the message header; the message body is a request and reply message in the actual business process.
The client and the server are both provided with a forwarding module, and the forwarding module is a process window and is responsible for decoding the message header and forwarding the message header to a corresponding UI or a processing module; the forwarding module also abstracts the coding work of the message and is responsible for the coding work of the message, and each processing module and UI only need to pay attention to the content of the message.
According to the communication method of the request terminal and the service terminal, when message transmission needs to be carried out through network byte stream transmission, for example, between two processes or between two PCs, ASN.1 messages need to be transmitted in a network after the serialization of the network byte stream is carried out through encoding and decoding. But for the request processing among the processing modules in the same process, the network transmission is not involved, and the message interaction among the processing modules skips the encoding and decoding processes and directly stores the copy so as to improve the interaction efficiency; the processing method is packaged in a unified encoding and decoding object, and is transparent to each processing module, so that the service processing flow of the processing module can be simplified. Referring to fig. 2, by adopting the communication method provided by the invention, based on the structural information characteristics of the asn.1, the communication capacity between the client and the server or the service group, and between the server and the server, is expanded. In other embodiments, the ASN.1 standard can be replaced by other existing mature technologies, such as Google Protocol Buffer (Protobuf).
It will be understood by those skilled in the art that the foregoing is only a preferred embodiment of the present invention, and is not intended to limit the invention, and that any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (8)
1. A communication method between a request end and a service end is characterized by comprising the following steps:
s10, the request end generates a request message containing a message header and a message body under the request trigger; the message header comprises a function ID, a device ID and a request ID, and the message body comprises a request message;
s20, encoding the request message into ASN.1 byte stream data and sending the ASN.1 byte stream data to a server;
s30, the server receives the byte stream data, when the byte stream is received, when the length of the byte stream is larger than the sum of the idle area and the decoded area, the memory block is expanded according to the sum of the length of the byte stream and the length of the un-decoded area, and the byte stream is copied to the expanded memory block; decoding the received byte stream data, decoding a message header firstly, and forwarding the message header to a corresponding processing module according to the segmented mark of the analyzed functional ID; the segment mark is a segment representation mode which uses the first bits in the message header to represent the ID of the processing module;
s40, the server side searches the corresponding request message definition according to the request ID and decodes the request data;
and S50, when the requested service processing is finished, the server side fills the reply message and returns the filled message to the request side according to the message header.
2. The communication method according to claim 1, wherein in the process of receiving the byte stream at the server, the memory management method further comprises:
s31, initializing a memory block, wherein the memory block comprises a decoded area, an un-decoded area and a free area;
s32, when the byte stream is received,
when the length of the byte stream is smaller than that of the idle area, directly copying the byte stream to the idle area, and setting the corresponding idle area as an un-decoded area;
and when the length of the byte stream is greater than the idle area and the length of the byte stream is less than the sum of the idle area and the decoded area, combining the decoded area and the idle area to form a new idle area, and copying the byte stream to the new idle area.
3. The communication method of claim 1, wherein in the decoding process, a process of forward-backward compatibility of the message including the asn.1 is adopted, including
S41, backward compatibility method:
when the request end uses a low version message, the server end uses a high version message, the server end receives a low version message request, and in the decoding process using the high version message, one of the following conditions is met, namely the decoding is successful:
i. the length of the current message byte stream is completely decoded, and no abnormity exists;
ii. The current decoding message is completely analyzed and has no abnormity;
s42, forward compatibility method:
when the request end uses the high version message, the server end uses the low version message, the server end receives the high version request, and in the decoding process using the low version message, one of the following conditions is met, namely the decoding success is represented;
I. the length of the current message byte stream is completely decoded, and no abnormity exists;
II. The current decoded message is completely analyzed and has no abnormity.
4. The communication method according to any one of claims 1 to 3, wherein the requesting side is a client or other server.
5. A communication system of a request end and a service end is characterized by comprising
The request end message generating module is used for generating a request message containing a message header and a message body under the request trigger; the message head comprises a function ID, a device ID and a request ID, and the message body comprises a request message;
the request end message forwarding module is used for coding the message into ASN.1 byte stream data and sending the ASN.1 byte stream data to the server end;
the server side forwarding module is used for receiving the byte stream at the server side, expanding the memory block according to the sum of the length of the byte stream and the length of the un-decoded area when the length of the byte stream is larger than the sum of the idle area and the decoded area when the byte stream is received, and copying the byte stream to the expanded memory block; decoding the received byte stream, decoding a message header firstly, and forwarding the message header to a corresponding processing module according to the segmented mark of the analyzed functional ID;
the function ID segment mark is a segment representation mode which uses the first bits in the message header to represent the ID of the processing module;
the message sending module is used for filling the reply message after the requested service is processed, and returning the filled message to the request end according to the received message header;
and the server processing module is used for searching the corresponding request message definition according to the request ID in the message header and decoding the request data.
6. The communication system according to claim 5, wherein the memory management method adopted by the server-side forwarding module in the process of receiving the byte stream further comprises:
s31, initializing a memory block, wherein the memory block comprises a decoded area, an un-decoded area and a free area;
s32, when the byte stream is received,
when the length of the byte stream is smaller than that of the idle area, directly copying the byte stream to the idle area, and setting the corresponding idle area as an un-decoded area;
and when the length of the byte stream is greater than the idle area and the length of the byte stream is less than the sum of the idle area and the decoded area, combining the decoded area and the idle area to form a new idle area, and copying the byte stream to the new idle area.
7. The communication system of claim 5, wherein the server forwarding module employs a forward-backward compatible processing method for the packets containing the asn.1 in the decoding process, so as to achieve forward-backward compatibility when the requesting side and the server side employ different versions of the packets; the method comprises the following specific steps:
s41, backward compatibility method:
when the request end uses a low version message, the server end uses a high version message, the server end receives a low version message request, and in the decoding process using the high version message, one of the following conditions is met, namely the decoding is successful:
i. the length of the current message byte stream is completely decoded, and no abnormity exists;
ii. The current decoding message is completely analyzed and has no abnormity;
s42, forward compatibility method:
when the request end uses the high version message, the server end uses the low version message, the server end receives the high version request, and in the decoding process using the low version message, one of the following conditions is met, namely the decoding success is represented;
I. the length of the current message byte stream is completely decoded, and no abnormity exists;
II. The current decoded message is completely analyzed and has no abnormity.
8. A communication system according to any of claims 5 to 7, wherein the requesting party is a client or other server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810940776.XA CN109067754B (en) | 2018-08-17 | 2018-08-17 | Communication method and system for request terminal and server terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810940776.XA CN109067754B (en) | 2018-08-17 | 2018-08-17 | Communication method and system for request terminal and server terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109067754A CN109067754A (en) | 2018-12-21 |
| CN109067754B true CN109067754B (en) | 2021-04-20 |
Family
ID=64687197
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810940776.XA Active CN109067754B (en) | 2018-08-17 | 2018-08-17 | Communication method and system for request terminal and server terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109067754B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111858103B (en) * | 2020-07-30 | 2022-08-16 | 南京甄视智能科技有限公司 | Compatible realization method for communication of high and low versions of modules in software system |
| CN113852635A (en) * | 2021-09-26 | 2021-12-28 | 招商银行股份有限公司 | Task processing method and device, terminal equipment and storage medium |
| CN114125081B (en) * | 2021-10-27 | 2023-09-22 | 桂林长海发展有限责任公司 | Method and device for processing received data and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102780698A (en) * | 2012-07-24 | 2012-11-14 | 南京邮电大学 | User terminal safety communication method in platform of Internet of Things |
| CN103607593A (en) * | 2013-08-01 | 2014-02-26 | 广东本致数码科技有限公司 | Method for realization of streaming media on server |
| CN106713428A (en) * | 2016-12-08 | 2017-05-24 | 中国电信股份有限公司物联网分公司 | Business operation support system applied to Internet-of-things self-management platform |
| CN106919479A (en) * | 2015-12-24 | 2017-07-04 | 北京谊安医疗系统股份有限公司 | A kind of real-time logs recording method of embedded device controller |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9578544B2 (en) * | 2014-01-30 | 2017-02-21 | Intel Corporation | Radio resource control messaging for dual connectivity networks |
-
2018
- 2018-08-17 CN CN201810940776.XA patent/CN109067754B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102780698A (en) * | 2012-07-24 | 2012-11-14 | 南京邮电大学 | User terminal safety communication method in platform of Internet of Things |
| CN103607593A (en) * | 2013-08-01 | 2014-02-26 | 广东本致数码科技有限公司 | Method for realization of streaming media on server |
| CN106919479A (en) * | 2015-12-24 | 2017-07-04 | 北京谊安医疗系统股份有限公司 | A kind of real-time logs recording method of embedded device controller |
| CN106713428A (en) * | 2016-12-08 | 2017-05-24 | 中国电信股份有限公司物联网分公司 | Business operation support system applied to Internet-of-things self-management platform |
Non-Patent Citations (1)
| Title |
|---|
| 健康监测大数据平台中统一的数据接入协议研究与实现;赵博扬;《中国优秀硕士学位论文全文数据库 信息科技辑》;20180715;参见正文第2-4章，第7-50页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109067754A (en) | 2018-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109067754B (en) | Communication method and system for request terminal and server terminal | |
| US6453343B1 (en) | Methods, systems and computer program products for maintaining a common checkpoint cache for multiple sessions between a single client and server | |
| JP4633365B2 (en) | Improved synchronization method between server and client | |
| US7917578B1 (en) | Managing state information in a computing environment | |
| CN101341724B (en) | System and method for history driven optimization of web services communication | |
| US20060020560A1 (en) | Content distribution using network coding | |
| US8224980B2 (en) | Adaptive parsing and compression of SOAP messages | |
| US8667506B2 (en) | Object oriented management device for ASN.1 message | |
| CN110505123B (en) | Packet loss rate calculation method, server and computer-readable storage medium | |
| US20050027731A1 (en) | Compression dictionaries | |
| CN102546612B (en) | Remote procedure call implementation method based on remote direct memory access (RDMA) protocol in user mode | |
| CN111314023A (en) | Synchronization method of tree network topology information | |
| US20140304369A1 (en) | Content Handling Method, Apparatus, and System | |
| CN113225320A (en) | Network message analysis method for keeping user configurable message format secret | |
| CN115994141A (en) | Tree-shaped coding method and system | |
| CN109327435B (en) | Media resource acquisition method and device and gateway equipment | |
| CN110049133B (en) | Method and device for issuing full amount of DNS zone files | |
| CN111913817A (en) | Data transmission method, system and equipment and computer readable storage medium | |
| CN114996361B (en) | Data processing method and system | |
| CN111163100B (en) | Data structure, communication method, device, storage medium and equipment | |
| CN102263796B (en) | Data transmission method based on simple network management protocol | |
| CN113992644A (en) | Internet of things gateway system based on non-service technology and data processing method thereof | |
| CN117135156B (en) | Edge cluster nano-tube method, system, computer readable storage medium and electronic equipment based on publish/subscribe message protocol | |
| US11907773B2 (en) | Method for communicating between software entities via an API | |
| CN115665042B (en) | Data processing method, device, user plane functional entity 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |