CN109729101B - Multi-level low coupling communication system - Google Patents
Multi-level low coupling communication system Download PDFInfo
- Publication number
- CN109729101B CN109729101B CN201910185006.3A CN201910185006A CN109729101B CN 109729101 B CN109729101 B CN 109729101B CN 201910185006 A CN201910185006 A CN 201910185006A CN 109729101 B CN109729101 B CN 109729101B
- Authority
- CN
- China
- Prior art keywords
- data
- layer
- request
- websocket
- access
- 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
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a multilayer low-coupling communication system, which comprises a local service layer: loading the data on an external computer to generate service request data; the access layer receives the WebSocket data and issues the WebSocket data to the local service layer; receiving service request data of a local service layer and processing abnormal service request data; the protocol analysis layer completes the packing, unpacking, encryption and decryption of the WebSocket protocol of the service request data; and the WebSocket transmission layer respectively realizes the transmission of WebSocket data between the access layer and the remote server. The system adopts a layered architecture design, cross-layer calling cannot be performed between layers, coupling between layers is reduced, the layers below an access layer do not perform serialization and deserialization on data, all serialization and deserialization float up to the implementation of a local service, and coupling between the system and specific service logic is reduced.
Description
Technical Field
The invention belongs to the technical field of communication, and particularly relates to a multi-level low-coupling communication system.
Background
General computer (client or server) and server interaction projects select WebSocket as a basic communication protocol, and each computer is required to design a basic communication protocol library according to the WebSocket protocol to support basic communication by defining a data transmission structure.
However, the general WebSocket protocol has strong dependence and relevance, and the fault tolerance, the extensibility and the robustness of the whole system are reduced.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a multi-level low-coupling communication system, which reduces the coupling of the system.
A multi-tier, low coupling communication system comprising:
a local service layer: the system is loaded on an external computer and used for generating service request data; the system is also used for sending or receiving WebSocket data; the external computer is used for interacting with a user;
an access layer: the system comprises a local service layer, a network layer and a network layer, wherein the local service layer is used for receiving WebSocket data and sending the WebSocket data to the local service layer; the local business layer is also used for receiving the business request data of the local business layer and processing the abnormal business request data;
a protocol analysis layer: the boxing and unpacking device is used for completing the WebSocket protocol; the access layer is also used for encrypting and decrypting the service request data of the access layer;
WebSocket transmission layer: the system comprises an access layer, a remote server and a network interface, wherein the access layer is used for accessing a WebSocket data file;
the remote server: the method is used for realizing the transmission of the WebSocket data between the WebSocket transmission layer and the network interface.
Preferably, the access stratum is specifically configured to:
the access layer receives the WebSocket data and judges whether the received WebSocket data is received data or not;
if so, discarding the WebSocket data;
if not, when the issuing mode of the local service layer is subscription, the access layer issues the WebSocket data to the local service layer in a subscription mode.
Preferably, the abnormal service request data includes service request data of request timeout, cancel request, request data persistence and request failure.
Preferably, the access stratum is specifically configured to:
the access layer starts a daemon thread and a queue to be overtime;
if the overtime time is set in the service request data, assembling a request path, a request ID, the overtime time and the time for successfully sending the request in the service request data into an object, and adding the object into the queue to be overtime;
the access layer wakes up the overtime thread, and circularly searches the object which is most quickly overtime from the queue to be overtime in sequence to perform overtime processing until the queue to be overtime is empty;
the timeout processing specifically includes: and when the waiting time of the object exceeds the overtime, calling a Timeout method to send a request path and a request ID in the object to the local service layer, and deleting the object from the queue to be overtime.
Preferably, the access stratum is specifically configured to:
the access layer stores the received service request data into a request object pool;
when the access layer receives a cancel request from the local service layer, searching whether the request object pool has a request ID of the service request data;
and if so, intercepting the service request data corresponding to the request ID.
Preferably, the access stratum is specifically configured to:
and after the access layer is successfully connected with the WebSocket transmission layer, the access layer searches whether an object needing to be retransmitted exists in the request object pool or not, and if so, retransmits the object through the WebSocket transmission layer.
Preferably, the access stratum is specifically configured to:
when receiving a data persistence request from the local service layer, the access layer acquires data to be persisted in the data persistence request and persists the data to be persisted;
the access layer generates a request for retransmitting the persistent data and sends the request to the local service layer;
the local service layer acquires data to be retransmitted in the retransmission persistent data request, generates a data persistence request according to the data to be retransmitted, and sends the data persistence request to the access layer;
and the access layer generates a request for deleting the persistent data, sends the request to the local service layer and deletes the request for deleting the persistent data when receiving a deletion response returned by the local service layer.
Preferably, the protocol resolution layer is further configured to:
when the service request data cannot be analyzed, generating an error data packet and sending the error data packet to the WebSocket transmission layer;
and when the WebSocket transmission layer receives the error data packet, acquiring service request data which cannot be analyzed in the error data packet, and forbidding to send the service request data to the local service layer.
Preferably, the WebSocket transport layer is further configured to:
when an input network automatic disconnection instruction is received, the WebSocket network is reconnected;
if the reconnection times of the WebSocket network are less than the preset maximum trial reconnection times, the reconnection time interval of the WebSocket network is calculated according to the following formula:
a time interval of min (1, (trial reconnection number × trial reconnection number) × ((maximum trial reconnection number × maximum trial reconnection number)/maximum time interval));
wherein the trial reconnection times refer to the WebSocket network reconnection times; min is a minimum function;
if the number of times of the WebSocket network reconnection is larger than the preset maximum trial reconnection number, the time interval of the WebSocket network reconnection is equal to the preset maximum interval time.
According to the technical scheme, the multi-level low-coupling communication system provided by the invention adopts a layered architecture design, the layers cannot be called in a cross-layer mode, the coupling performance between the layers is reduced, the layers below the access layer do not carry out serialization and deserialization on data, all serialization and deserialization are floated up to the local service realization, and the coupling between the system and specific service logic is reduced.
Drawings
In order to more clearly illustrate the detailed description of the invention or the technical solutions in the prior art, the drawings that are needed in the detailed description of the invention or the prior art will be briefly described below. Throughout the drawings, like elements or portions are generally identified by like reference numerals. In the drawings, elements or portions are not necessarily drawn to scale.
Fig. 1 is a block diagram of a communication system according to an embodiment of the present invention.
Fig. 2 is a schematic data interaction diagram of a communication system according to an embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The following examples are only for illustrating the technical solutions of the present invention more clearly, and therefore are only examples, and the protection scope of the present invention is not limited thereby. It is to be noted that, unless otherwise specified, technical or scientific terms used herein shall have the ordinary meaning as understood by those skilled in the art to which the invention pertains.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
The first embodiment is as follows:
a multi-level low coupling communication system, as shown in fig. 1 and 2, comprising:
a local service layer: the system is loaded on an external computer and used for generating service request data; the system is also used for sending or receiving WebSocket data;
specifically, the external computer is used for interacting with a user, and is a computer device, such as a computer, a smart phone, an intelligent chat robot, a mechanical arm, and the like, for obtaining user requirements and instructions. The system can realize the communication between the client and the remote server, and can also be expanded to the communication mode of the server 1, namely the client-remote server, which is indirect from the server to the server. The local service layer is mainly used for being responsible for specific service logic and processing serialization and deserialization of all service data. The local service layer also realizes the transmission and reception of WebSocket data between the local service layer and the access layer.
An access layer: the system comprises a local service layer, a network layer and a network layer, wherein the local service layer is used for receiving WebSocket data and sending the WebSocket data to the local service layer; the local business layer is also used for receiving the business request data of the local business layer and processing the abnormal business request data;
specifically, the access layer is responsible for processing the service data of the local service layer and processing the abnormal service request data, so as to ensure that the service data of the local service layer is processed timely and accurately.
A protocol analysis layer: the boxing and unpacking device is used for completing the WebSocket protocol; the access layer is also used for encrypting and decrypting the service request data of the access layer;
specifically, the protocol analysis layer is used for ensuring the safety of WebSocket communication.
WebSocket transmission layer: the system comprises an access layer, a remote server and a network interface, wherein the access layer is used for accessing a WebSocket data file;
specifically, the WebSocket transport layer is mainly responsible for WebSocket connection and disconnection, TCP data packet transmission and reception, and network disconnection and reconnection.
The remote server: the method is used for realizing the transmission of the WebSocket data between the WebSocket transmission layer and the network interface.
The system adopts a layered architecture design, cross-layer calling cannot be performed between layers, coupling between layers is reduced, the layers below an access layer do not perform serialization and deserialization on data, all serialization and deserialization float up to the implementation of a local service, and coupling between the system and specific service logic is reduced.
Example two:
the second embodiment is added with the following contents on the basis of the first embodiment:
the access stratum is specifically configured to:
the access layer receives the WebSocket data and judges whether the received WebSocket data is received data or not;
if so, discarding the WebSocket data;
if not, when the issuing mode of the local service layer is subscription, the access layer issues the WebSocket data to the local service layer in a subscription mode.
Specifically, the local service layer may receive WebSocket data in a subscription manner, and the access layer directly discards data that the local service layer has received. For example, after the access layer sends the WebSocket data to the local service layer for a period of time, the same WebSocket data is received again, but the data is repeatedly received, so that the newly received WebSocket data is directly discarded.
Preferably, the abnormal service request data includes service request data of request timeout, cancel request, request data persistence and request failure.
The access layer processes the business request data which is requested to be overtime.
The access layer starts a daemon thread and a queue to be overtime;
specifically, the daemon thread of this embodiment is responsible for monitoring the processing of the access stratum queue to be overtime on the message, and when no message needs to be processed on the access stratum, that is, the queue to be overtime is empty, the daemon thread is automatically closed. When the queue to be timed out is empty and a new message is received, it is automatically started.
If the overtime time is set in the service request data, assembling a request path, a request ID, the overtime time and the time for successfully sending the request in the service request data into an object, and adding the object into the queue to be overtime;
specifically, the timeout time is used to indicate the effective time of the service request data, and when the time for which the service request data a waits to be processed exceeds the timeout time, the service request data is considered to be timeout. The request Path may be denoted by Path, indicating the task/content of the current service request data. The request ID is represented by series number and may be an identification code or a serial number. When the timeout time is set in the service request data, the system records the task/content of the current request, the identification code, the timeout time, the time for starting to calculate the timeout waiting time (i.e. the time for the request to be sent successfully), wherein the task/content and the identification code of the current request are used for marking what the request of the information is, for example, how/where to implement the request of the information. The timeout time for the current request and the time the request was sent successfully are to calculate how long the information will time out.
The access layer wakes up the overtime thread, and circularly searches the object which is most quickly overtime from the queue to be overtime in sequence to perform overtime processing until the queue to be overtime is empty;
specifically, the access layer needs to sequentially take out objects in the queue to be overtime for performing the overtime processing until the queue to be overtime is empty. The access layer needs to find out the object which needs to be processed most urgently, namely the object which needs to be timed out most urgently, at each search.
The timeout processing specifically includes: and when the waiting time of the object exceeds the overtime, calling a Timeout method to send a request path and a request ID in the object to the local service layer, and deleting the object from the queue to be overtime.
Specifically, the object is considered to be timed out when the waiting time of the object exceeds the timeout time. The latency of an object refers to the time difference between the issuance of this piece of information and the timeout.
And the access layer processes the service request data for canceling the request.
The access layer stores the received service request data into a request object pool;
specifically, the access layer is further configured to maintain a request object pool, where the request object pool stores the successfully received service request data. Each object has a survival duration and is longer than a timeout duration.
When the access layer receives a cancel request from the local service layer, searching whether the request object pool has a request ID of the service request data;
specifically, the cancellation request may be with a request ID in the service request data. Since each service request data corresponds to a request ID, the request ID can uniquely identify which service request data.
And if so, intercepting the service request data corresponding to the request ID.
Specifically, when a request ID in a cancellation request exists in a request object pool, service request data corresponding to the request ID is intercepted. When the request ID in the request object pool exists, the cancel attribute of the request may also be set to true, indicating that the request needs to be canceled.
And thirdly, the access layer processes the service request data which fails to be requested.
And after the access layer is successfully connected with the WebSocket transmission layer, the access layer searches whether an object needing to be retransmitted exists in the request object pool or not, and if so, retransmits the object through the WebSocket transmission layer.
And fourthly, the access layer processes the service request data which requests data persistence.
When receiving a data persistence request from the local service layer, the access layer acquires data to be persisted in the data persistence request and persists the data to be persisted;
specifically, the data persistence request includes data to be persisted that needs to be persisted. Data persistence refers to the long-term storage of information. The persistence process may employ existing methods for persistent storage.
The access layer generates a request for retransmitting the persistent data and sends the request to the local service layer;
the local service layer acquires data to be retransmitted in the retransmission persistent data request, generates a data persistence request according to the data to be retransmitted, and sends the data persistence request to the access layer;
in particular, the access stratum requires the local service stratum to retransmit persistently stored data.
And the access layer generates a request for deleting the persistent data, sends the request to the local service layer and deletes the request for deleting the persistent data when receiving a deletion response returned by the local service layer.
Specifically, all the objects in the access layer that are requested to be overtime and cancelled are deleted from the request object pool after the request response is returned and the request is overtime. The system also needs to clear the request that does not need to be retransmitted in the request object pool after the network is disconnected. The system may send messages using a single thread, with the pool of request objects being a first-in-first-out ordered queue.
The system ensures that the service data of the local service layer is processed timely and accurately.
For the sake of brief description, the embodiments of the present invention do not refer to the corresponding contents in the foregoing embodiments of the present invention.
Example three:
embodiment three adds the following on the basis of other embodiments:
the protocol resolution layer is further configured to:
when the service request data cannot be analyzed, generating an error data packet and sending the error data packet to the WebSocket transmission layer;
and when the WebSocket transmission layer receives the error data packet, acquiring service request data which cannot be analyzed in the error data packet, and forbidding to send the service request data to the local service layer.
In particular, data transmitted by a computer or a remote server external to the system is always transmitted in the form of protocol packets. The service request data may be registered in a mapping table according to a mapping relationship of path — object class, and the specific mapping relationship may be determined according to a system specifically used by an external computer. And if the protocol packet cannot be analyzed, directly sending an error data packet to the WebSocket transmission layer, and not sending the error data packet to the local service layer.
For the sake of brief description, the embodiments of the present invention do not refer to the corresponding contents in the foregoing embodiments of the present invention.
Example four:
example four on the basis of other examples, the following are added:
the WebSocket transport layer is further configured to:
when an input network automatic disconnection instruction is received, the WebSocket network is reconnected;
specifically, after the WebSocket network is disconnected, it is necessary to determine whether the current WebSocket connection disconnection is manual disconnection, and if the current WebSocket connection disconnection is manual disconnection, it indicates that the current WebSocket connection disconnection is manually and actively disconnected, and the following reconnection operation is not triggered. If the automatic disconnection is performed, the system or the network is in failure, and the WebSocket network needs to be reconnected.
If the reconnection times of the WebSocket network are less than the preset maximum trial reconnection times, the reconnection time interval of the WebSocket network is calculated according to the following formula:
a time interval of min (1, (trial reconnection number × trial reconnection number) × ((maximum trial reconnection number × maximum trial reconnection number)/maximum time interval));
wherein the trial reconnection times refer to the WebSocket network reconnection times; min is a minimum function;
specifically, the trial reconnection number refers to the number of attempts to reconnect the WebSocket network after the WebSocket network is disconnected.
If the number of times of the WebSocket network reconnection is larger than the preset maximum trial reconnection number, the time interval of the WebSocket network reconnection is equal to the preset maximum interval time.
For the sake of brief description, the embodiments of the present invention do not refer to the corresponding contents in the foregoing embodiments of the present invention.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.
Claims (9)
1. A multi-level, low coupling communication system, comprising:
a local service layer: the system is loaded on an external computer and used for generating service request data; the system is also used for sending or receiving WebSocket data; the external computer is used for interacting with a user;
an access layer: the system comprises a local service layer, a network layer and a network layer, wherein the local service layer is used for receiving WebSocket data and sending the WebSocket data to the local service layer; the local business layer is also used for receiving the business request data of the local business layer and processing the abnormal business request data;
a protocol analysis layer: the boxing and unpacking device is used for completing the WebSocket protocol; the access layer is also used for encrypting and decrypting the service request data of the access layer;
WebSocket transmission layer: the system comprises an access layer, a remote server and a network interface, wherein the access layer is used for accessing a WebSocket data file;
the remote server: the transmission device is used for realizing the transmission of WebSocket data between the transmission device and the WebSocket transmission layer;
wherein cross-layer calls cannot be made between layers.
2. The multi-tier, low-coupling communication system of claim 1, wherein the access stratum is specifically configured to:
the access layer receives the WebSocket data and judges whether the received WebSocket data is received data or not;
if so, discarding the WebSocket data;
if not, when the issuing mode of the local service layer is subscription, the access layer issues the WebSocket data to the local service layer in a subscription mode.
3. The multi-level low coupling communication system of claim 1,
the abnormal service request data comprises service request data which is overtime, cancel request, request data persistence and request failure.
4. The multi-tier, low-coupling communication system of claim 3 wherein the access stratum is further configured to:
the access layer starts a daemon thread and a queue to be overtime;
if the overtime time is set in the service request data, assembling a request path, a request ID, the overtime time and the time for successfully sending the request in the service request data into an object, and adding the object into the queue to be overtime;
the access layer wakes up the overtime thread, and circularly searches the object which is most quickly overtime from the queue to be overtime in sequence to perform overtime processing until the queue to be overtime is empty;
the timeout processing specifically includes: and when the waiting time of the object exceeds the overtime, calling a Timeout method to send a request path and a request ID in the object to the local service layer, and deleting the object from the queue to be overtime.
5. The multi-tier, low-coupling communication system of claim 4 wherein the access stratum is further configured to:
the access layer stores the received service request data into a request object pool;
when the access layer receives a cancel request from the local service layer, searching whether the request object pool has a request ID of the service request data;
and if so, intercepting the service request data corresponding to the request ID.
6. The multi-tier, low-coupling communication system of claim 5 wherein the access stratum is further configured to:
and after the access layer is successfully connected with the WebSocket transmission layer, the access layer searches whether an object needing to be retransmitted exists in the request object pool or not, and if so, retransmits the object through the WebSocket transmission layer.
7. The multi-tier, low-coupling communication system of claim 5 wherein the access stratum is further configured to:
when receiving a data persistence request from the local service layer, the access layer acquires data to be persisted in the data persistence request and persists the data to be persisted;
the access layer generates a request for retransmitting the persistent data and sends the request to the local service layer;
the local service layer acquires data to be retransmitted in the retransmission persistent data request, generates a data persistence request according to the data to be retransmitted, and sends the data persistence request to the access layer;
and the access layer generates a request for deleting the persistent data, sends the request to the local service layer and deletes the request for deleting the persistent data when receiving a deletion response returned by the local service layer.
8. The multi-hierarchy low-coupling communication system of any one of claims 1-7, wherein the protocol resolution layer is further configured to:
when the service request data cannot be analyzed, generating an error data packet and sending the error data packet to the WebSocket transmission layer;
and when the WebSocket transmission layer receives the error data packet, acquiring service request data which cannot be analyzed in the error data packet, and forbidding to send the service request data to the local service layer.
9. The multi-hierarchy low-coupling communication system of any one of claims 1-7, wherein the WebSocket transport layer is further configured to:
when an input network automatic disconnection instruction is received, the WebSocket network is reconnected;
if the reconnection times of the WebSocket network are less than the preset maximum trial reconnection times, the reconnection time interval of the WebSocket network is calculated according to the following formula:
a time interval of min (1, (trial reconnection number × trial reconnection number) × ((maximum trial reconnection number × maximum trial reconnection number)/maximum time interval));
wherein the trial reconnection times refer to the WebSocket network reconnection times; min is a minimum function;
if the number of times of the WebSocket network reconnection is larger than the preset maximum trial reconnection number, the time interval of the WebSocket network reconnection is equal to the preset maximum interval time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910185006.3A CN109729101B (en) | 2019-03-12 | 2019-03-12 | Multi-level low coupling communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910185006.3A CN109729101B (en) | 2019-03-12 | 2019-03-12 | Multi-level low coupling communication system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109729101A CN109729101A (en) | 2019-05-07 |
| CN109729101B true CN109729101B (en) | 2021-08-06 |
Family
ID=66302310
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910185006.3A Active CN109729101B (en) | 2019-03-12 | 2019-03-12 | Multi-level low coupling communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109729101B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112261037B (en) * | 2020-10-20 | 2023-05-30 | 上海挚想科技有限公司 | Decoupling transmission method and system for separating communication layer from service layer |
| CN114726681B (en) * | 2022-03-31 | 2022-10-21 | 慧之安信息技术股份有限公司 | Gateway service layered design method and device with separated business and communication logic |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106027611A (en) * | 2016-05-06 | 2016-10-12 | 中国科学院合肥物质科学研究院 | Data transmission method between agricultural vehicle-mounted intelligent terminal and monitoring client based on WebGIS technology |
| CN106375272A (en) * | 2016-03-31 | 2017-02-01 | 深圳市美贝壳科技有限公司 | Method of multi-layer communication |
| CN107147543A (en) * | 2017-04-19 | 2017-09-08 | 武汉票据交易中心有限公司 | A kind of socket communication means of server towards pc client |
| CN109379303A (en) * | 2018-08-22 | 2019-02-22 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Parallelization processing framework system and method based on improving performance of gigabit Ethernet |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7873060B2 (en) * | 2008-10-18 | 2011-01-18 | Fortinet, Inc. | Accelerating data communication using tunnels |
-
2019
- 2019-03-12 CN CN201910185006.3A patent/CN109729101B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106375272A (en) * | 2016-03-31 | 2017-02-01 | 深圳市美贝壳科技有限公司 | Method of multi-layer communication |
| CN106027611A (en) * | 2016-05-06 | 2016-10-12 | 中国科学院合肥物质科学研究院 | Data transmission method between agricultural vehicle-mounted intelligent terminal and monitoring client based on WebGIS technology |
| CN107147543A (en) * | 2017-04-19 | 2017-09-08 | 武汉票据交易中心有限公司 | A kind of socket communication means of server towards pc client |
| CN109379303A (en) * | 2018-08-22 | 2019-02-22 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Parallelization processing framework system and method based on improving performance of gigabit Ethernet |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109729101A (en) | 2019-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5128111B2 (en) | System for preserving the sequence associated with a message, and method and computer program thereof | |
| KR101203275B1 (en) | Using subqueues to enhance local message processing | |
| US6161198A (en) | System for providing transaction indivisibility in a transaction processing system upon recovery from a host processor failure by monitoring source message sequencing | |
| US8429654B2 (en) | Apparatus and method for guaranteed batch event delivery in a process control system | |
| US10305813B2 (en) | Socket management with reduced latency packet processing | |
| US7624308B2 (en) | Failed message error recovery using application specific error queues | |
| CN103532822B (en) | The management method of message dilivery, server and system | |
| US6543005B1 (en) | Transmitting data reliably and efficiently | |
| US6920476B2 (en) | Messaging system for computers | |
| CN109729101B (en) | Multi-level low coupling communication system | |
| CN106506490A (en) | A kind of Distributed Calculation control method and distributed computing system | |
| EP4390712A1 (en) | Network interface card, message sending method and storage apparatus | |
| CN111970092B (en) | Multi-protocol redundant network asynchronous communication method supporting reliability adjustment | |
| JP3709289B2 (en) | Data transmission / reception device and parallel processor system for performing data retransmission | |
| CN112291047A (en) | Transmission confirmation method, device, equipment and storage medium | |
| US9069632B2 (en) | Message processing | |
| US20070240170A1 (en) | Computer implemented method and system for processing an event notification within a notification infrastructure of a database system using a persistent queue | |
| US20070206598A1 (en) | Communications apparatus and communication method | |
| US8234338B1 (en) | System and method for reliable message delivery | |
| CN113691627A (en) | Control method, device, equipment and medium for SOAR linkage equipment | |
| CN203574673U (en) | Message-processing system | |
| US11190301B2 (en) | Method and device for setting out-of-order value of network | |
| CN110266446B (en) | Method and device for adjusting out-of-order time length based on SACK mode | |
| US20120331172A1 (en) | Method And System For Improved Performance Of Network Communications With Interface Specific Buffers | |
| CN101132376B (en) | Method, device and corresponding system for controlling iSCSI message transmitting and receiving |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 215000 Room 301, building 39, 239 Renmin Road, Gusu District, Suzhou City, Jiangsu Province Applicant after: SHENZHEN GOWILD ROBOTICS Co.,Ltd. Applicant after: SHENZHEN GOWILD INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 518017-09, Dongfang Science and technology building, Keyuan Road, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province Applicant before: SHENZHEN GOWILD ROBOTICS Co.,Ltd. Applicant before: SHENZHEN GOWILD INTELLIGENT TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PP01 | Preservation of patent right | ||
| PP01 | Preservation of patent right |
Effective date of registration: 20220228 Granted publication date: 20210806 |