CN102946376B - Method for implementing asynchronous communication - Google Patents
Method for implementing asynchronous communication Download PDFInfo
- Publication number
- CN102946376B CN102946376B CN201110387021.XA CN201110387021A CN102946376B CN 102946376 B CN102946376 B CN 102946376B CN 201110387021 A CN201110387021 A CN 201110387021A CN 102946376 B CN102946376 B CN 102946376B
- Authority
- CN
- China
- Prior art keywords
- agent side
- management end
- request message
- message
- call back
- 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
Landscapes
- Computer And Data Communications (AREA)
- Communication Control (AREA)
Abstract
The invention discloses a method for implementing asynchronous communication. An asynchronous communication module and various application protocols are used for data communication. The method comprises the following steps: setting the asynchronous communication module between an application A and an application B, wherein the asynchronous communication module is divided into a management side and a proxy side which are placed on the application A as an initiating side and the application B as a receiving side respectively; and implementing asynchronous communication between the management side and the proxy side by a protocol stack.
Description
Technical field
The present invention relates to a kind of communication technology, particularly relate to a kind of method using asynchronous communication assembly to realize data communication.
Background technology
In distributing communication field, in software development process, various application protocol can be run into.A lot of application protocol both provides the code prototype of synchronous mode, as SNMP (Simple Network Management Protocol, Simple Network Management Protocol), SOAP (Simple Object Access Protocol, Simple Object Access Protocol) etc.In synchronous mode, receive multiple request simultaneously, and according to these events of hyposynchronous process.But, once there be the request needing to process the long period to occur, then can reduce treatment effeciency.
How to use these agreement prototypes, the agreement API (Application Programming Interface, application programming interface) realizing developing asynchronous communication on multiple application protocol is the problem needing to solve.Agreement API in the prior art owing to not being exploitation asynchronous communication at multiple application protocol, therefore, applicable protocols is single, and the development and maintenance cost of bitcom increases, and the asynchronous communication function of realization is relatively simple.The technical scheme that such as publication number is CN 1195242A, name is called a kind of method of computer network asynchronous communication, adopt and comprise for carrying out the communication module of communication with other network terminal at a network terminal, at least one communication management module and at least one communication link control module are set in this communication module; Communication management module is used for arranging Connecting quantity, writes communication applications program etc.; The various events that communication link program module occurs in connecting for the treatment of network, and automatically recover when there is network failure, same communication module can respectively as client modules or server module.Decrease programing work amount, use identical program to realize the function of client-server.Its weak point is that applicable protocols is single, and the asynchronous communication function of realization is relatively simple.
Summary of the invention
Main purpose of the present invention is the implementation method providing a kind of asynchronous communication, and it uses a kind of asynchronous communication assembly, uses various agreement to carry out data communication.
The present invention is directed to that prior art problem mainly solved by following technical proposals, a kind of implementation method of asynchronous communication, comprising:
(A) between application A and application B, arrange asynchronous communication assembly, asynchronous communication assembly is divided into management end and agent side two parts, and management end is placed on the application A of initiatively transmission, and agent side is placed on the application B of passive reception;
(B) asynchronous communication is carried out by protocol stack between management end and agent side.
Most of communications protocol is the model work based on request, response, also there are two kinds of roles of request, response in the asynchronous communication assembly of this method design, realized by management end and agent side two part, it is upper with on the application B of passive reception that management end and agent side are placed on the application A initiatively sent respectively.
In concurrent design, event DeMux can be separated with its protocol handling code with connection management, uses the code prototype of agreement to adopt synchronous mode realization event DeMux and connection management.This method adopts a kind of asynchronous mode to achieve event DeMux and connection management, and using this part code as component reusing technology, use multiple application protocol, the agreement API met the demands can be sent by fast open, thus realize using various agreement to carry out data communication by protocol stack between management end and agent side.
As preferably, management end comprise an asynchronous transmission interface, transmit queue, receiving queue, one group send and receiving thread, management end buffer area, one group of worker thread and a monitor thread; Agent side comprises a receiving queue, transmit queue, one group receives and send thread, one group of worker thread, an agent side buffer area, a Chong Bao detection zone and one asynchronously returns interface.
As preferably, application A constantly calls asynchronous transmission interface and various request message is sent to agent side, wherein the request message of a type associates a management end call back function, after receiving return messages from agent side, worker thread carries out DeMux to various return messages, and call different management end call back functions, what complete message returns process, monitor thread is responsible for monitoring the message time-out that various abnormal conditions cause, and carries out message retransmission.
As preferably, after agent side receives various request message, wherein the request message of a type is associated with an agent side call back function, agent side calls different agent side call back functions, under synchronous mode, agent side call back function directly completes the process of message and returns, and under asynchronous mode, message is put into the Message Processing queue of application B by agent side call back function.
As preferably, the transmission flow of management end comprises:
1) apply A to call asynchronous transmission interface with non-blocking fashion and send a request message, and request message is put into management end transmit queue;
2) management end sends thread and take out request message from transmit queue, request message is put into management end buffer area with the management end call back function associated, and is sent by request message;
The reception flow process of described agent side comprises:
3) agent side receiving thread receives request message, and puts into agent side receiving queue;
4) agent side worker thread takes out message from receiving queue, their agent side call back function is called according to type of message, if simultaneous operation, Message Processing is completed in call back function, return to management end immediately, if asynchronous operation, call back function does not complete Message Processing, also management end is not returned immediately, but by request message, transmitting terminal address information stored in agent side buffer area, and obtain an agent side buffer area unique identification, then message is put into together with agent side buffer area unique identification the Message Processing queue of application B;
The Returning process of described agent side comprises:
5) apply B and obtain message from Message Processing queue, process, after being disposed, call that agent side is asynchronous returns interface;
6) the asynchronous interface that returns of agent side is according to agent side buffer area unique identification obtaining request message and context, and then return messages are put into agent side transmit queue by structure return messages;
7) agent side sends thread and take out return messages from transmit queue, and returns to management end;
The reception flow process of described management end comprises:
8) management end receiving thread receives return messages, puts into management end receiving queue;
9) management end worker thread takes out return messages from receiving queue, management end worker thread is according to the unique identification of return messages, request message before finding in management end buffering area and call back function, then inform to corresponding management end call back function by return messages, request message;
10) management end call back function completes the process of return messages.
As preferably, monitor thread carries out intermittent scanning to whole buffer area, the situation of message time-out in monitoring management end buffer area, and each request message has a time-out time and maximum number of retransmissions, if find time-out bag, will retransmit; When repeating transmission exceedes maximum times, management end call back function will be activated, notice application A request message time-out.There is a monitor thread at management end, intermittent scanning is carried out to whole buffer area, the situation of message time-out in monitoring management end buffer area, if find time-out bag, will retransmit, when repeating transmission exceedes maximum times, call back function will be activated, notice application A request message time-out.
As preferably, agent side is provided with heavily bag measuring ability, request message unique identification and return messages are associated, after transmission thread constructing return messages, return messages are stored in Chong Bao detection zone, if there is same uniquely identified request message to come, to not notify to apply B, directly return return messages.Request message unique identification and return messages associate by agent side, after transmission thread constructing return messages, return messages are stored, if there is same uniquely identified request message to come, to not notify to apply B, directly return return messages, doing so avoids the reprocessing of same message.
The beneficial effect that the present invention brings is, uses asynchronous communication assembly conveniently to develop the agreement API of asynchronous communication, realizes using various protocols to carry out data communication.
Accompanying drawing explanation
Fig. 1 is a kind of asynchronous communication modular construction schematic diagram of the present invention;
Fig. 2 is a kind of Data Stream Processing journey figure of the present invention.
In figure, 101 is application A, and 102 is management ends, and 103 is protocol stacks, and 104 is agent sides, and 105 is application B.
Embodiment
Below by embodiment, and by reference to the accompanying drawings, technical scheme of the present invention is further described in detail.
Embodiment 1: as shown in Figure 1, the present invention is a kind of implementation method of asynchronous communication,
Between application A 101 and application B105, asynchronous communication assembly is set, asynchronous communication assembly is divided into management end 102 and agent side 104 two parts, management end 102 is placed on the application A 101 of initiatively transmission, and agent side 104 is placed on the application B105 of passive reception; Management end 102 and agent side 104 carry out asynchronous communication by protocol stack 103.
Figure 2 shows that the flow chart of data processing figure of asynchronous communication assembly, as shown in the figure:
The transmission flow of management end 102:
1) apply A101 to call asynchronous transmission interface with non-blocking fashion and send a request message;
2) request message is put into management end 102 transmit queue by asynchronous transmission function;
3) management end 102 sends thread and take out request message from transmit queue, and request message is put into management end buffer area with the management end call back function associated, and then request message sends by invocation protocol stack 103 handling procedure;
The reception flow process of agent side 104:
4) agent side 104 receiving thread invocation protocol stack 103 handling procedure receives request message, and whether be retransmitted packet, be if detecting in agent side 104 Chong Bao detection zone, uses protocol stack 103 handling procedure that the return messages detected are sent to management end 102; Otherwise request message is put into agent side 104 receiving queue;
5) agent side 104 worker thread takes out message from receiving queue, calls their agent side call back function according to type of message; If simultaneous operation, in call back function, complete Message Processing, after structure return messages, return messages are stored in Chong Bao detection zone, return to management end 102 immediately; If asynchronous operation, call back function does not complete Message Processing, also management end is not returned immediately, but by information such as request message, transmitting terminal addresses stored in agent side 104 buffer area, and obtain an agent side buffer area unique identification, then message is put into together with agent side buffer area unique identification the Message Processing queue of application B105;
The Returning process of agent side 104:
6) apply B105 and obtain message from Message Processing queue, process.(just may be disposed through multiple thread) after being disposed, call that agent side 104 is asynchronous returns interface;
7) the asynchronous interface that returns of agent side 104 is according to agent side buffer area unique identification obtaining request message and context, and then return messages are put into agent side transmit queue by structure return messages;
8) agent side 104 sends thread and take out return messages from transmit queue, and after structure return messages, return messages are stored in Chong Bao detection zone, then invocation protocol stack 103 handling procedure returns to management end 102; The reception flow process of management end 102:
9) management end 102 receiving thread invocation protocol stack 103 handling procedure receives return messages, puts into management end 102 receiving queue;
10) management end 102 worker thread takes out return messages from receiving queue; Because return messages are identical with the message unique identity of request message, so management end 102 worker thread is according to the unique identification of return messages, request message before finding in management end 102 buffering area and call back function, then inform to corresponding management end 102 call back function by return messages, request message;
11) management end 102 call back function completes the process of return messages.
Communication part is to the process of abnormal conditions:
Each request message has a time-out time and maximum number of retransmissions.There is a monitor thread at management end 102, intermittent scanning is carried out to whole buffer area, the situation of message time-out in monitoring management end 102 buffer area, if find time-out bag, will retransmit, when repeating transmission exceedes maximum times, call back function will be activated, notice application A request message time-out;
Agent side 104 has heavily bag measuring ability, and request message unique identification and return messages associate by agent side 104, return messages is stored after transmission thread constructing return messages.If there is same uniquely identified request message to come, will not notifies to apply B105, directly return return messages.
Embodiment 2: be the embodiment in conjunction with compilation tool gSOAP and this method exploitation asynchronous communication SOAP API below.
GSOAP compilation tool can generate stake required for exploitation Soap agreement and framing program automatically.Stake is one " agency " being placed on client, and framework is one " agency " being placed on server end.State a function in stake, but content is wherein not concrete algorithm, but the agreement that a series of network connects, automatically remove the main frame at search framework place, then with its swap data, and obtain a series of codes of return value.Now the process of client only needs to adjust the function in stake, can realize the exchanges data with far-end server, so just ensure that the transparency of transfer of data for application process.
The handling process of the stake code that gSOAP generates is:
1. initialization running environment example;
2. construct request message head and entity;
3. connect and complete message and send;
4. wait-receiving mode is receiveed the response;
5. resolve receive the response head and entity, acquisition returns results;
6. close and connect.
The framework using gSOAP to produce needs first in application program, to start listening port, initialization running environment example, and etc. to be connected.After a connection is come, the method that invocation framenort provides processes.The handling process of the skeleton code that gSOAP generates is:
1. receive request message;
2. analysis request message, obtaining request information, activates call back function;
3. call back function returns, and obtains return messages, and structure returns bag;
4. send and return bag.
Use asynchronous communication assembly of the present invention, in conjunction with the code of stake and framework, exploitation asynchronous communication SOAP API.This API comprises the management end part different with agent side two.Application A calls management end asynchronous transmission interface and sends Soap message to opposite end, is received the Soap message returned by management end call back function.
The handling process of management end is:
1. asynchronous transmission interface uses the handling process 1 initialization running environment example of stake code, puts into transmit queue by needing the information sent;
2. sending thread uses the handling process 2 of stake code to construct transmission bag, and transmission bag and call back function are put into management end buffer area, uses the handling process 3 of stake code message to be sent;
3. receiving thread uses the handling process 4 of stake code to receive return messages, uses the handling process 5 of stake code to resolve this return messages, and the message after resolving is put into receiving queue;
4. worker thread takes out message from receiving queue, finds and sends information context, and activate call back function in management end buffer area, and in call back function, API is by the full detail providing transmission and the full detail received;
5. the message sent in monitor thread monitor management end buffer area, if return time-out, will retransmit.Repeatedly repeat still without returning, then to activate call back function.In call back function, API will provide full detail and the timeout flag of transmission.
The receiving thread of agent side starts listening port, initialization running environment example, and etc. to be connected.When a connection comes then, the handling process of agent side is:
1. receiving thread uses the handling process 1 of skeleton code to receive request message, and whether be retransmitted packet, be if detecting in Chong Bao detection zone, use the handling process 4 of skeleton code to send return messages, otherwise request message puts into receiving queue;
2. worker thread uses the handling process 2 of skeleton code to process request message, and activates call back function;
3. request message is put into agent side buffer area by call back function, and proxy caching district can return a unique identification, and request message and proxy caching district unique identification are informed to application B by call back function;
4. apply B after processing request message, call and asynchronously return interface, use agent side buffer area unique identification from buffer area, find the information of this request message, use the handling process 3 of skeleton code to construct return messages, and Chong Bao detection zone and transmit queue will be put into;
5. sending thread uses the handling process 4 of skeleton code return messages to be returned.
Through above-mentioned conversion processing, asynchronous communication assembly by the soap protocol API of a synchronous communication, can become a soap protocol API that is reliable, asynchronous communication efficiently.Can also be applied in other agreement, more efficient, the reliable asynchronous communication agreement API of convenient realization.
So the present invention has the agreement API using asynchronous communication Components Development asynchronous communication, realize using various protocols to carry out data communication, the features such as convenient and swift, strong adaptability of programming.
Claims (6)
1. an implementation method for asynchronous communication, its feature comprises:
(A) between application A and application B, arrange asynchronous communication assembly, described asynchronous communication assembly is divided into management end and agent side two parts, and described management end is placed on the application A of initiatively transmission, and described agent side is placed on the application B of passive reception;
(B) asynchronous communication is carried out by protocol stack between described management end and agent side;
The transmission flow of described management end comprises:
(1) apply A to call asynchronous transmission interface with non-blocking fashion and send a request message, and request message is put into management end transmit queue;
(2) management end sends thread and take out request message from transmit queue, request message is put into management end buffer area with the management end call back function associated, and is sent by request message;
The reception flow process of described agent side comprises:
(3) agent side receiving thread receives request message, and puts into agent side receiving queue;
(4) agent side worker thread takes out message from receiving queue, their agent side call back function is called according to type of message, if simultaneous operation, Message Processing is completed in call back function, return to management end immediately, if asynchronous operation, call back function does not complete Message Processing, also management end is not returned immediately, but by request message, transmitting terminal address information stored in agent side buffer area, and obtain an agent side buffer area unique identification, then message is put into together with agent side buffer area unique identification the Message Processing queue of application B;
The Returning process of described agent side comprises:
(5) apply B and obtain message from Message Processing queue, process, after being disposed, call that agent side is asynchronous returns interface;
(6) the asynchronous interface that returns of agent side is according to agent side buffer area unique identification obtaining request message and context, and then return messages are put into agent side transmit queue by structure return messages;
(7) agent side sends thread and take out return messages from transmit queue, and returns to management end;
The reception flow process of described management end comprises:
(8) management end receiving thread receives return messages, puts into management end receiving queue;
(9) management end worker thread takes out return messages from receiving queue, management end worker thread is according to the unique identification of return messages, request message before finding in management end buffering area and call back function, then inform to corresponding management end call back function by return messages, request message;
(10) management end call back function completes the process of return messages.
2. the implementation method of a kind of asynchronous communication according to claim 1, is characterized in that: described management end comprise an asynchronous transmission interface, transmit queue, receiving queue, one group send and receiving thread, management end buffer area, one group of worker thread and a monitor thread; Described agent side comprises a receiving queue, transmit queue, one group receives and send thread, one group of worker thread, an agent side buffer area, a Chong Bao detection zone and one asynchronously returns interface.
3. the implementation method of a kind of asynchronous communication according to claim 2, it is characterized in that: application A constantly calls asynchronous transmission interface and various request message is sent to agent side, wherein the request message of a type associates a management end call back function, after receiving return messages from agent side, worker thread carries out DeMux to various return messages, call different management end call back functions, what complete message returns process, monitor thread is responsible for monitoring the message time-out that various abnormal conditions cause, and carries out message retransmission.
4. the implementation method of a kind of asynchronous communication according to claim 2, it is characterized in that: after described agent side receives various request message, wherein the request message of a type is associated with an agent side call back function, agent side calls different agent side call back functions, under synchronous mode, agent side call back function directly completes the process of message and returns, and under asynchronous mode, message is put into the Message Processing queue of application B by agent side call back function.
5. the implementation method of a kind of asynchronous communication according to claim 2, it is characterized in that: described monitor thread, intermittent scanning is carried out to whole buffer area, the situation of message time-out in monitoring management end buffer area, each request message has a time-out time and maximum number of retransmissions, if find time-out bag, will retransmit; When repeating transmission exceedes maximum times, management end call back function will be activated, notice application A request message time-out.
6. a kind of implementation method of asynchronous communication according to claim 1 or 2 or 3 or 4 or 5, it is characterized in that: described agent side is provided with heavily bag measuring ability, request message unique identification and return messages are associated, after transmission thread constructing return messages, return messages are stored in Chong Bao detection zone, if there is same uniquely identified request message to come, to not notify to apply B, directly return return messages.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110387021.XA CN102946376B (en) | 2011-11-29 | 2011-11-29 | Method for implementing asynchronous communication |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110387021.XA CN102946376B (en) | 2011-11-29 | 2011-11-29 | Method for implementing asynchronous communication |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102946376A CN102946376A (en) | 2013-02-27 |
| CN102946376B true CN102946376B (en) | 2015-04-29 |
Family
ID=47729283
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110387021.XA Active CN102946376B (en) | 2011-11-29 | 2011-11-29 | Method for implementing asynchronous communication |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102946376B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104125252B (en) * | 2013-04-27 | 2017-12-01 | 博雅网络游戏开发（深圳）有限公司 | Data-storage system and method |
| CN103324480A (en) * | 2013-06-21 | 2013-09-25 | 徐州赫思曼电子有限公司 | Method for Flash Player thread to acquire underlying information in QNX (quick Unix) system |
| CN103701720A (en) * | 2014-01-13 | 2014-04-02 | 中国银行股份有限公司 | Communication method with Socket server and online transaction management system |
| CN104360904A (en) * | 2014-10-16 | 2015-02-18 | 四川长虹电器股份有限公司 | Intermodular message transmission mechanism based on event bus |
| CN104580209B (en) * | 2015-01-06 | 2017-08-01 | 烽火通信科技股份有限公司 | Realize the device and method of multi-platform Message Processing |
| CN105119981B (en) * | 2015-07-23 | 2019-06-07 | 上海斐讯数据通信技术有限公司 | A method of processing message |
| CN105915656B (en) * | 2016-06-30 | 2019-09-24 | 中国银行股份有限公司 | It is related to the data processing method and device of batch far call |
| CN108347445B (en) * | 2018-03-19 | 2021-04-27 | 武汉斗鱼网络科技有限公司 | Method and device for realizing remote calling |
| CN108717380B (en) * | 2018-05-15 | 2021-08-10 | 西安万像电子科技有限公司 | Message processing method and device |
| CN109086150A (en) * | 2018-09-20 | 2018-12-25 | 杭州安恒信息技术股份有限公司 | A kind of method, apparatus for avoiding multiple asynchronous methods from repeating and electronic equipment |
| CN113076209B (en) * | 2021-06-08 | 2021-08-17 | 贝壳技术有限公司 | Communication method, communication device, electronic device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040162994A1 (en) * | 2002-05-13 | 2004-08-19 | Sandia National Laboratories | Method and apparatus for configurable communication network defenses |
| CN101179790A (en) * | 2007-11-03 | 2008-05-14 | 青岛海信移动通信技术股份有限公司 | Serial port communication method between mobile terminal processor |
| CN101196813A (en) * | 2007-12-26 | 2008-06-11 | 上海科泰世纪科技有限公司 | Method for implementing event call-back based on component interface in computer software system |
| CN101969435A (en) * | 2010-09-30 | 2011-02-09 | 北京新媒传信科技有限公司 | Interaction method and system based on SIP (Session Initiation Protocol)-C protocol |
-
2011
- 2011-11-29 CN CN201110387021.XA patent/CN102946376B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040162994A1 (en) * | 2002-05-13 | 2004-08-19 | Sandia National Laboratories | Method and apparatus for configurable communication network defenses |
| CN101179790A (en) * | 2007-11-03 | 2008-05-14 | 青岛海信移动通信技术股份有限公司 | Serial port communication method between mobile terminal processor |
| CN101196813A (en) * | 2007-12-26 | 2008-06-11 | 上海科泰世纪科技有限公司 | Method for implementing event call-back based on component interface in computer software system |
| CN101969435A (en) * | 2010-09-30 | 2011-02-09 | 北京新媒传信科技有限公司 | Interaction method and system based on SIP (Session Initiation Protocol)-C protocol |
Non-Patent Citations (1)
| Title |
|---|
| 林巍凌.基于XML/SOAP的WebGIS构建研究.《中国优秀博硕士学位论文全文数据库 (硕士) 基础科学辑》.2006, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102946376A (en) | 2013-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102946376B (en) | Method for implementing asynchronous communication | |
| CN102377814B (en) | Remote assistance service method aiming at embedded operation system | |
| CN103220292B (en) | Cross-safe-area data transmission and system | |
| CN102567125B (en) | Method for realizing communication between browser pages | |
| CN101848107B (en) | SNMP (Simple Network Management Protocol) network element and communication method of SNMP network element and proprietary protocol network element | |
| CN103139157B (en) | A kind of based on the network communication method of socket, Apparatus and system | |
| CN103516673A (en) | Network data communication method, network data communication system, network data communication client and network data communication server | |
| CN105897652A (en) | Standard protocol based heterogeneous terminal dynamic access method | |
| CN101136828A (en) | RS485 based multi-host machine wired serial communication method | |
| CN103023857A (en) | Method and system for remote deployment of information resources | |
| CN101340268A (en) | Implementing method and system for inter-node communication confirming mechanism | |
| CN104660627B (en) | A kind of communication means and system of host computer and slave computer | |
| CN104317661A (en) | Intersystem communication method and device of dual embedded systems | |
| CN107147655A (en) | A kind of network dual stack parallel process model and its processing method | |
| CN107567107A (en) | A kind of method and device for transmitting data | |
| CN102857354A (en) | Method, device and system for reporting alarm information | |
| CN101873235A (en) | Detection method of equipment network link, network management system and network system | |
| CN104536934A (en) | Serial port communication method and system | |
| CN103051724A (en) | Socket synchronization method based on long connection | |
| CN104580346A (en) | Data transmission method and device | |
| CN101022364A (en) | Trap message reporting method and system warning information resource/warning agent service device | |
| CN101277247B (en) | Real-time communication system | |
| KR20020042180A (en) | Automatic management method for socket of mobile communication system | |
| CN113992740B (en) | Middleware based on autonomous control and data transmission method | |
| CN210274135U (en) | Remote connection system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20151203 Address after: 100088, Beijing, Haidian District, Huayuan Road No. 4 Tong Heng building, room B07 Patentee after: UT Sidakang (China) Co., Ltd. Address before: 310052 No. six, No. 368, Binjiang District Road, Zhejiang, Hangzhou Patentee before: UT Starcom Communication Co., Ltd. |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20190103 Address after: 518000 Lenovo Building, No. 016, Gaoxin Nantong, Yuehai Street, Nanshan District, Shenzhen City, Guangdong Province, on the east side of the third floor Patentee after: Excellent network Co., Ltd. Address before: Room B07, Tongheng Building, 4 Garden Road, Haidian District, Beijing 100088 Patentee before: UT Sidakang (China) Co., Ltd. |
|
| TR01 | Transfer of patent right |