CN102368700A - Transmission method of massages in distributed system - Google Patents
Transmission method of massages in distributed system Download PDFInfo
- Publication number
- CN102368700A CN102368700A CN2011103283189A CN201110328318A CN102368700A CN 102368700 A CN102368700 A CN 102368700A CN 2011103283189 A CN2011103283189 A CN 2011103283189A CN 201110328318 A CN201110328318 A CN 201110328318A CN 102368700 A CN102368700 A CN 102368700A
- Authority
- CN
- China
- Prior art keywords
- message
- transmit leg
- recipient
- sequence number
- sent
- 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.)
- Granted
Links
Images
Abstract
The invention provides a high-reliability transmission method of messages in a distributed system. The transmission method can provide efficient and reliable message transmission to the distributed system and guarantee the reliability of the message transmission which is memorized into a memory level; meanwhile, the transmission method also can guarantee that the messages lost in a network transmission process can be retransmitted to a receiver in a recovering step after the network is malfunctioned, so that the reliability of the system is guaranteed.
Description
Technical field
The present invention relates to the communication system of parallel file system, the highly reliable transmission of messages field in particularly a kind of distributed system.
Background technology
Communication system has great importance as the communication infrastructure between each node of system in the distributed system.Because the node and the network equipment in the distributed system are separate, all possibly break down at any time, the messages between nodes transmission path relates to a plurality of parts simultaneously; The message buffer that comprises communication system, the message of system is sent buffering area, the hardware buffer of network interface card and switch; The reception buffering area of system; The reception buffering area of communication system when breaking down in system, can't confirm where communication information is positioned at.
In the once communication of a distributed system; Be divided into communication initiator and communication receiver, the communication initiator initiates traffic operation, and the communication receiver receives message and handles to message content; And send the message of finishing dealing with and give the communication initiator, notifying communication initiator finishes dealing with.Communication information sends to message receiver from message sender need pass through message sender, and communication layers is sent buffering, the network interface card hardware buffer, and exchange hardware input, output buffering, the network interface card hardware buffer, communication layers receives buffering, finally arrives message receiver.The message of finishing dealing with that traffic operation that the communication initiator sends and communication receiver reply all need be passed through said communication paths.When system broke down, communication information possibly be present in any place, possibly be present in the transmit path, and in recipient's buffering area, the perhaps side's of being received processing is not replied but accomplish to handle.Also possibly be that the recipient receives and finishes dealing with, response message is lost, and response message is in the communication layers buffering area, in the hardware buffer district of network interface card or switch.After system broke down, general reliability processing mode resend the not message of correct handling then for communicating reconstruction.But for the communication that can not repeat; Because communication request side can't know whether communication information is received and carry out by communication service side; If this moment, the communication initiator sent identical communication information once more; Can cause the communication receiver unknown system mode to occur, thereby make distributed system inconsistent state occur.Traditional solution makes the communication of application layer become complicated on application layer, to handle.
Simultaneously, the succession of transmission of messages is extremely important in distributed system, for the succession that guarantees to communicate by letter, generally realizes guaranteeing the preface of communication in application layer.After network breaks down, keep this succession and become very complicated, a kind of reliable network layer need be provided, provide reliable transmission of messages to ensure in proper order.
On the other hand; Because possibly there is fault in the transmission channel of intra-node; Even if transmission over networks has guaranteed reliability, can not guarantee to use the data consistency end to end of one-level, need the reliable news transmission mechanism of memory-to-memory level in a kind of communication process.Under this background, this patent has proposed a kind of highly reliable method for message transmission, and having guaranteed provides the memory-to-memory level reliable transmission of messages under the prerequisite of transmission of messages interface terseness of application layer.
Summary of the invention
The objective of the invention is to solve the integrity problem of transmission of messages in the distributed system, method for message transmission highly reliable in a kind of distributed system is provided.
In order to solve in the system failure; The communication initiator is to the unknown problem of the state of a traffic operation; The present invention proposes a kind of based on error control mechanism and verification scheme end to end; Condition of information be can in fault, confirm, and the succession and the correctness of Network Transmission message guaranteed.
The transmission method of message in a kind of distributed system,
Safeguard a message sequence number and expection message SN respectively at the two ends of communication path, when connecting foundation for the first time, communicating pair is 0 through control messages synchronization message sequence number at first, and communicating pair expects that synchronously message SN is 0 simultaneously;
For the message of each transmission, at first obtain the message sequence number of connection, this message sequence number is filled in the control messages head that sends message; After sending the message success; Upgrade the transmitting time of sending message, this message is put into transmission message queue to be confirmed, wait for affirmation from the recipient;
The recipient is after receiving message, and whether the message sequence number on the inspection message header matees with current expection message sequence number;
Transmit leg is receiving the affirmation message that the recipient returns; According to message number with message number in the formation to be sent smaller or equal to the message of this message number; Confirm to send accomplish, the notice upper strata is sent and is accomplished, and the message number to be confirmed of upgrading side to be sent simultaneously is an acknowledge message number; If acknowledge message number does not find message to be confirmed in formation to be sent, think that then this message is identified, directly abandons this acknowledge message;
If the request in the formation to be sent of transmit leg was not replied in the set time, then think to resend this message by the transmission information drop-out, wait acknowledge message;
After breaking down; Transmit leg and recipient consult message number to be confirmed and send message number; If find the to be confirmed message number of recipient's message number to be confirmed greater than transmit leg, then the expression existence receives, but the unacknowledged message number of transmit leg; The synchronous message number to be confirmed of transmit leg is recipient's a message number to be confirmed, simultaneously message number in the message queue to be sent is expected that the recipient message that message number and transmit leg send between the message number-1 retransmits.
Preferably, in the message sequence number of inspection on the message header whether during with current expection message sequence number coupling,
If the message sequence number, thinks then that this message sent completion less than expection message sequence number, abandon the message of receiving, and return acknowledge message to transmit leg, confirm number to be current expection message sequence number-1;
If the message sequence number greater than expection message sequence number, is then inserted this message and waited to receive in the message queue, wait for expection message;
If the message sequence number equals to expect message number, then this message is submitted to the recipient and handle, search for message queue to be received; Continuous message after the existence expection message number whether; If exist, submit to the recipient in the lump and handle, upgrade the latest news N+1 of up-to-date expection message number for submitting to; Return acknowledge message to transmit leg at last, acknowledge message number up-to-date message number N for submitting to.
Preferably, said transmit leg uses the message checking algorithm to calculate the message check value between message is sent, and this check value is appended in the transmission message header, carries out message and sends.
Preferably, said checking algorithm adopts MD5 or CRC.
Preferably, said recipient is after receiving message, after message receives the internal memory that receives buffering area fully; Just begin to calculate the check value of message,, then think message error of transmission on bang path if the transmit leg check value that carry the message check value of finding to calculate and message header centre does not match; Directly this message is abandoned; Do not carry out the reception operation in the error control step, send NAK message and give transmit leg, carry this wrong message number.
Preferably, said transmit leg is receiving NAK message, knows that then the recipient receives this message error, in transmission message queue to be confirmed, finds the identical message of message number, carries out message retransmission, the message authentication of message to be sent such as continuation.
Highly reliable method for message transmission in a kind of distributed system that the present invention proposes; Can the high-efficiency reliable transmission of messages be provided for distributed system; Guarantee the reliability of other transmission of messages of memory-to-memory level; After network breaks down, can guarantee that the message of losing in the Network Transmission is transferred to the recipient again in recovering step simultaneously, guarantee the reliability of system.
Description of drawings
Below, specify embodiments of the invention in conjunction with accompanying drawing, wherein:
Fig. 1 is a message transmit path sketch map;
Fig. 2 is the corresponding scene sketch map of highly reliable transmission of messages mechanism;
Embodiment
Below in conjunction with accompanying drawing and embodiment method of the present invention is described.
The thought of error control mechanism is end to end: adopt message request sequence number+reply (ACK)+retransmit the mode of (NAK)+overtime repeating transmission, guarantee that message sends to target side and is processed.Concrete grammar is:
Step S1; Safeguard a message sequence number and expection message SN respectively at the two ends of communication path, the message sequence number of transmit leg is send_msg_sn, and expection message sequence number is send_ack_sn; Recipient's message number is recv_msg_sn; The expection message number is recv_ack_sn, and it is msg_sn that message header carries message number, and acknowledge message number is ack_sn.When connecting foundation for the first time, communicating pair is 0 through control messages synchronization message sequence number at first, and communicating pair expects that synchronously message SN is 0. simultaneously
Step S2; For the message of each transmission, at first obtain the message sequence number send_msg_sn of connection, this message sequence number is filled among the control messages head msg_sn that sends message; After sending the message success; Upgrade the transmitting time of sending message, this message is put into transmission message queue to be confirmed, wait for affirmation from the recipient
Step S3, recipient are after receiving message, and whether the message sequence number on the inspection message header matees with current expection message sequence number, has following three kinds of situation:
(1) if message sequence number msg_sn, thinks then that this message sent completion less than expection message sequence number recv_ack_sn, abandons the message of receiving, and return acknowledge message, confirm number to be current expection message sequence number recv_ack_sn-1 to transmit leg.
(2) if message sequence number msg_sn greater than expection message sequence number recv_ack_sn, then inserts this message and waits to receive in the message queue, wait for expection message
(3) if message sequence number msg_sn equals to expect message number recv_ack_sn; Then this message being submitted to the recipient handles; Search for message queue to be received, whether have expection message number continuous message afterwards, if exist; Submit to the recipient in the lump and handle, upgrade the latest news N+1 of up-to-date expection message number for submitting to.Return acknowledge message to transmit leg at last, acknowledge message number up-to-date message number N for submitting to.
Step S4; Transmit leg is receiving the affirmation message that the recipient returns; According to message number ack_sn, message number in the formation to be sent smaller or equal to the message of this message number ack_sn, is confirmed to send and accomplished; The notice upper strata is sent and is accomplished, and the message number send_ack_sn to be confirmed that upgrades side to be sent simultaneously is ack_sn.If acknowledge message ack_sn does not find message to be confirmed in formation to be sent, think that then this message is identified, directly abandons this acknowledge message
Step S4 if the request in the formation to be sent of transmit leg was not replied in the set time, then thinks and uses step S1 to resend this message, wait acknowledge message by the transmission information drop-out
Step S5; After breaking down; Transmit leg and recipient consult message number to be confirmed and send message number, if find the to be confirmed message number of recipient's message number to be confirmed greater than transmit leg, then the expression existence receives; But the unacknowledged message number of transmit leg, the synchronous message number to be confirmed of transmit leg is recipient's a message number to be confirmed.Simultaneously message number in the message queue to be sent is expected that the recipient message that message number recv_ack_sn and transmit leg send between the message number send_msg_sn-1 retransmits, so just can guarantee reliably orderly transmission message
The message verification scheme is:
Step S1, transmit leg at first use message checking algorithm modes such as () MD5/CRC to calculate the message check value between message is sent, and this check value appended to send in the message header, carry out message and send
Step S2, recipient are after receiving message, after message receives the internal memory that receives buffering area fully; Just begin to calculate the check value of message,, then think message error of transmission on bang path if the transmit leg check value that carry the message check value of finding to calculate and message header centre does not match; Directly this message is abandoned; Do not carry out the reception operation in the error control step, send NAK message and give transmit leg, carry this wrong message number.
Step S3, transmit leg is receiving NAK message, knows that then the recipient receives this message error, in transmission message queue to be confirmed, finds the identical message of message number, carries out message retransmission, the message authentication of message to be sent such as continuation.
The path of a message transmission is as shown in Figure 1, mainly is divided into following several steps:
Step S1 uses the initiator and initiates traffic operation, transfers to communication layers and handles
Step S2, communication layers is carried out the message transmit operation, and communication layers maybe the buffer memory communication information
Step S3, the communication network interface card sends message, and possibly there is the hardware buffer district in the communication network interface card
Step S4, data are sent in communication network, and possibly there is the exchange hardware buffering area in the switch of communication network
Step S5, communication network card receiver message, there is the hardware buffer district in the communication network interface card
Step S6, communication layers is carried out the reception operation of message, and transfer to after finishing receiving and use the receiving layer processing, the communication information that the possibility buffer memory partly receives in communication layers,
Step S7 uses receiving layer and receives communication information, handles operation
The possible situation of highly reliable transmission of messages mechanism is as shown in Figure 2:
Situation S1, transmit leg initiates a message, and the recipient normally receives acknowledge message, and sends response message ACK,
Situation S2, transmit leg initiates a message, and the recipient receives message, finds to cause message error in the transmission course through the calculation check value, abandons, and uses the NAK mode to notify transmit leg to carry out message retransmission
Situation S3, transmit leg initiates a message, but in the set time, does not receive recipient's response message, and then resend message waits for that the recipient after receiving message, carries out message authentication.
Claims (6)
1. the transmission method of message in the distributed system is characterized in that:
Safeguard a message sequence number and expection message SN respectively at the two ends of communication path, when connecting foundation for the first time, communicating pair is 0 through control messages synchronization message sequence number at first, and communicating pair expects that synchronously message SN is 0 simultaneously;
For the message of each transmission, at first obtain the message sequence number of connection, this message sequence number is filled in the control messages head that sends message; After sending the message success; Upgrade the transmitting time of sending message, this message is put into transmission message queue to be confirmed, wait for affirmation from the recipient;
The recipient is after receiving message, and whether the message sequence number on the inspection message header matees with current expection message sequence number;
Transmit leg is receiving the affirmation message that the recipient returns; According to message number with message number in the formation to be sent smaller or equal to the message of this message number; Confirm to send accomplish, the notice upper strata is sent and is accomplished, and the message number to be confirmed of upgrading side to be sent simultaneously is an acknowledge message number; If acknowledge message number does not find message to be confirmed in formation to be sent, think that then this message is identified, directly abandons this acknowledge message;
If the request in the formation to be sent of transmit leg was not replied in the set time, then think to resend this message by the transmission information drop-out, wait acknowledge message;
After breaking down; Transmit leg and recipient consult message number to be confirmed and send message number; If find the to be confirmed message number of recipient's message number to be confirmed greater than transmit leg, then the expression existence receives, but the unacknowledged message number of transmit leg; The synchronous message number to be confirmed of transmit leg is recipient's a message number to be confirmed, simultaneously message number in the message queue to be sent is expected that the recipient message that message number and transmit leg send between the message number-1 retransmits.
2. the method for claim 1 is characterized in that: whether the message sequence number on the inspection message header during with current expection message sequence number coupling,
If the message sequence number, thinks then that this message sent completion less than expection message sequence number, abandon the message of receiving, and return acknowledge message to transmit leg, confirm number to be current expection message sequence number-1;
If the message sequence number greater than expection message sequence number, is then inserted this message and waited to receive in the message queue, wait for expection message;
If the message sequence number equals to expect message number, then this message is submitted to the recipient and handle, search for message queue to be received; Continuous message after the existence expection message number whether; If exist, submit to the recipient in the lump and handle, upgrade the latest news N+1 of up-to-date expection message number for submitting to; Return acknowledge message to transmit leg at last, acknowledge message number up-to-date message number N for submitting to.
3. the method for claim 1 is characterized in that: said transmit leg uses the message checking algorithm to calculate the message check value between message is sent, and this check value appended to sends in the message header, carries out message and sends.
4. method as claimed in claim 3 is characterized in that: said checking algorithm adopts MD5 or CRC.
5. the method for claim 1; It is characterized in that: said recipient after message receives the internal memory that receives buffering area fully, just begins to calculate the check value of message after receiving message; If finding the message check value and the middle transmit leg check value that carries of message header that calculate does not match; Then think directly this message to be abandoned message error of transmission on bang path, do not carry out the reception operation in the error control step; Send NAK message and give transmit leg, carry this wrong message number.
6. the method for claim 1; It is characterized in that: said transmit leg is receiving NAK message, knows that then the recipient receives this message error, in transmission message queue to be confirmed, finds the identical message of message number; Carry out message retransmission, the message authentication of message to be sent such as continuation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110328318.9A CN102368700B (en) | 2011-10-25 | 2011-10-25 | Transmission method of massages in distributed system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110328318.9A CN102368700B (en) | 2011-10-25 | 2011-10-25 | Transmission method of massages in distributed system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102368700A true CN102368700A (en) | 2012-03-07 |
| CN102368700B CN102368700B (en) | 2014-10-22 |
Family
ID=45761250
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110328318.9A Active CN102368700B (en) | 2011-10-25 | 2011-10-25 | Transmission method of massages in distributed system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102368700B (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104348874A (en) * | 2013-08-06 | 2015-02-11 | 中国电信股份有限公司 | Method and device for message transmission between cloud platform components |
| CN104348711A (en) * | 2013-08-07 | 2015-02-11 | 三星Sds株式会社 | Apparatus and method for receiving messages |
| CN105162838A (en) * | 2015-07-30 | 2015-12-16 | 青岛海尔智能家电科技有限公司 | Message pushing method, and method and device for receiving pushed message |
| CN105450356A (en) * | 2014-09-03 | 2016-03-30 | 中兴通讯股份有限公司 | Lost data recovery processing method and device |
| CN106027379A (en) * | 2016-07-28 | 2016-10-12 | 贵州中科汉天下信息技术有限公司 | Push message receiving processing method |
| CN106201735A (en) * | 2016-06-27 | 2016-12-07 | 北京票之家科技有限公司 | Method for message transmission and system |
| CN109299193A (en) * | 2018-09-25 | 2019-02-01 | 深圳市佰仟金融服务有限公司 | Method of data synchronization and relevant device |
| CN109684128A (en) * | 2018-11-16 | 2019-04-26 | 深圳证券交易所 | Cluster overall failure restoration methods, server and the storage medium of message-oriented middleware |
| CN109714392A (en) * | 2018-11-26 | 2019-05-03 | 聚好看科技股份有限公司 | Across the computer room method of data synchronization of one kind and device |
| CN109788026A (en) * | 2018-12-13 | 2019-05-21 | 新华三大数据技术有限公司 | Message treatment method and device |
| CN110008037A (en) * | 2019-02-28 | 2019-07-12 | 北京达佳互联信息技术有限公司 | Message treatment method, device and storage medium |
| CN110109799A (en) * | 2019-03-29 | 2019-08-09 | 北京奇安信科技有限公司 | A kind of real time monitoring processing method and processing device of computing resource operation conditions |
| CN110727507A (en) * | 2019-10-21 | 2020-01-24 | 广州欢聊网络科技有限公司 | Message processing method and device, computer equipment and storage medium |
| CN110928944A (en) * | 2018-08-30 | 2020-03-27 | 阿里巴巴集团控股有限公司 | Data processing method and device |
| CN111708624A (en) * | 2020-06-16 | 2020-09-25 | 北京百度网讯科技有限公司 | Concurrency distribution method, device, equipment and storage medium based on multiple transmitters |
| CN112162875A (en) * | 2020-10-12 | 2021-01-01 | 上交所技术有限责任公司 | High-reliability message transmission method in transaction system |
| CN112865927A (en) * | 2019-11-27 | 2021-05-28 | 浙江大搜车软件技术有限公司 | Message delivery verification method, device, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1510964A (en) * | 1998-08-27 | 2004-07-07 | ض� | Inputting/outputting chain circuit retry, fault in computer network, and restoring method and apparatus |
| CN1691571A (en) * | 2004-04-21 | 2005-11-02 | 华为技术有限公司 | Method for data synchronization in communication system and apparatus therefor |
| CN1753354A (en) * | 2005-10-25 | 2006-03-29 | 华中科技大学 | Base station TCP agency confirmation method based on ARQ information and its system |
| CN1889414A (en) * | 2005-06-30 | 2007-01-03 | 华为技术有限公司 | Method for transmitting status PDU based on missing PDU detection mechanism |
| CN101217346A (en) * | 2007-01-05 | 2008-07-09 | 大唐移动通信设备有限公司 | An AM mode state feedback method and system |
-
2011
- 2011-10-25 CN CN201110328318.9A patent/CN102368700B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1510964A (en) * | 1998-08-27 | 2004-07-07 | ض� | Inputting/outputting chain circuit retry, fault in computer network, and restoring method and apparatus |
| CN1691571A (en) * | 2004-04-21 | 2005-11-02 | 华为技术有限公司 | Method for data synchronization in communication system and apparatus therefor |
| CN1889414A (en) * | 2005-06-30 | 2007-01-03 | 华为技术有限公司 | Method for transmitting status PDU based on missing PDU detection mechanism |
| CN1753354A (en) * | 2005-10-25 | 2006-03-29 | 华中科技大学 | Base station TCP agency confirmation method based on ARQ information and its system |
| CN101217346A (en) * | 2007-01-05 | 2008-07-09 | 大唐移动通信设备有限公司 | An AM mode state feedback method and system |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104348874B (en) * | 2013-08-06 | 2019-04-05 | 中国电信股份有限公司 | The method and apparatus that message is transmitted between cloud platform component |
| CN104348874A (en) * | 2013-08-06 | 2015-02-11 | 中国电信股份有限公司 | Method and device for message transmission between cloud platform components |
| CN104348711A (en) * | 2013-08-07 | 2015-02-11 | 三星Sds株式会社 | Apparatus and method for receiving messages |
| CN104348711B (en) * | 2013-08-07 | 2018-07-13 | 三星Sds株式会社 | Message receiving apparatus and method |
| CN105450356A (en) * | 2014-09-03 | 2016-03-30 | 中兴通讯股份有限公司 | Lost data recovery processing method and device |
| CN105162838A (en) * | 2015-07-30 | 2015-12-16 | 青岛海尔智能家电科技有限公司 | Message pushing method, and method and device for receiving pushed message |
| CN106201735A (en) * | 2016-06-27 | 2016-12-07 | 北京票之家科技有限公司 | Method for message transmission and system |
| CN106027379A (en) * | 2016-07-28 | 2016-10-12 | 贵州中科汉天下信息技术有限公司 | Push message receiving processing method |
| CN110928944A (en) * | 2018-08-30 | 2020-03-27 | 阿里巴巴集团控股有限公司 | Data processing method and device |
| CN110928944B (en) * | 2018-08-30 | 2024-04-02 | 阿里巴巴集团控股有限公司 | Data processing method and device |
| CN109299193A (en) * | 2018-09-25 | 2019-02-01 | 深圳市佰仟金融服务有限公司 | Method of data synchronization and relevant device |
| CN109684128A (en) * | 2018-11-16 | 2019-04-26 | 深圳证券交易所 | Cluster overall failure restoration methods, server and the storage medium of message-oriented middleware |
| CN109714392A (en) * | 2018-11-26 | 2019-05-03 | 聚好看科技股份有限公司 | Across the computer room method of data synchronization of one kind and device |
| CN109788026A (en) * | 2018-12-13 | 2019-05-21 | 新华三大数据技术有限公司 | Message treatment method and device |
| CN109788026B (en) * | 2018-12-13 | 2022-03-08 | 新华三大数据技术有限公司 | Message processing method and device |
| CN110008037A (en) * | 2019-02-28 | 2019-07-12 | 北京达佳互联信息技术有限公司 | Message treatment method, device and storage medium |
| CN110109799A (en) * | 2019-03-29 | 2019-08-09 | 北京奇安信科技有限公司 | A kind of real time monitoring processing method and processing device of computing resource operation conditions |
| CN110727507A (en) * | 2019-10-21 | 2020-01-24 | 广州欢聊网络科技有限公司 | Message processing method and device, computer equipment and storage medium |
| CN112865927A (en) * | 2019-11-27 | 2021-05-28 | 浙江大搜车软件技术有限公司 | Message delivery verification method, device, computer equipment and storage medium |
| CN112865927B (en) * | 2019-11-27 | 2023-09-12 | 浙江大搜车软件技术有限公司 | Message delivery verification method, device, computer equipment and storage medium |
| CN111708624A (en) * | 2020-06-16 | 2020-09-25 | 北京百度网讯科技有限公司 | Concurrency distribution method, device, equipment and storage medium based on multiple transmitters |
| CN111708624B (en) * | 2020-06-16 | 2023-09-29 | 北京百度网讯科技有限公司 | Concurrency allocation method, device, equipment and storage medium based on multiple transmitters |
| CN112162875A (en) * | 2020-10-12 | 2021-01-01 | 上交所技术有限责任公司 | High-reliability message transmission method in transaction system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102368700B (en) | 2014-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102368700B (en) | Transmission method of massages in distributed system | |
| CN101094446B (en) | Mobile communications system and method for transmitting data when handover occurs | |
| CN1973500B (en) | Method of, and system for and a station for transmitting data | |
| CN102025474B (en) | Network data transmission method | |
| EP1909468B1 (en) | Method and apparatus for backing up TCP connection | |
| WO2018006674A1 (en) | Data processing method and apparatus | |
| CN102449944A (en) | Method and apparatus for downlink data transmission control in multi-hop relay communication system | |
| US9031076B2 (en) | Processing requests | |
| UA77047C2 (en) | Method of moving a receiving window in a wireless mobile communication system | |
| CN105657646A (en) | Bluetooth 4.0 based device-to-device big data communication method | |
| CN104113403A (en) | Sliding window-based half-duplex communication method and system | |
| EP2613497A2 (en) | Method of transporting data in a sub-segmented manner | |
| WO2009127144A1 (en) | Data transmission method | |
| EP1580916B1 (en) | System and method for transmitting units of messages in a mobile communication system | |
| CN110601799A (en) | Link retransmission method and device based on double sliding windows | |
| WO2014194493A1 (en) | Method, device and system for reducing confirmation packets at transmission control layer | |
| CN112738229B (en) | Communication method for realizing automatic data continuous transmission | |
| US9510242B2 (en) | Reducing superfluous traffic in a network | |
| CN108183767A (en) | A kind of method for reliable transmission suitable for space DTN networks | |
| JP2009212796A (en) | Transmitter, data transfer system, data transfer method, and data transfer program | |
| JP2006191368A (en) | Network transmission device | |
| Bada | Automatic repeat request (Arq) protocols | |
| CN110121193B (en) | Interlayer data transmission method, device, medium and equipment | |
| WO2019128937A1 (en) | Uplink data scheduling method and relevant device | |
| CN101399649A (en) | Data transmission method, system and device |
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 | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20120307 Assignee: JIANGSU DAWN INFORMATION TECHNOLOGY Co.,Ltd. Assignor: Dawning Information Industry (Beijing) Co.,Ltd. Contract record no.: 2017320000013 Denomination of invention: Transmission method of massages in distributed system Granted publication date: 20141022 License type: Exclusive License Record date: 20170217 |
|
| LICC | Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220725 Address after: 100193 No. 36 Building, No. 8 Hospital, Wangxi Road, Haidian District, Beijing Patentee after: Dawning Information Industry (Beijing) Co.,Ltd. Patentee after: DAWNING INFORMATION INDUSTRY Co.,Ltd. Address before: 100084 Beijing Haidian District City Mill Street No. 64 Patentee before: Dawning Information Industry (Beijing) Co.,Ltd. |