CN101127702A - Multi-to-multi reliable multicast error recovery method for plane structure network - Google Patents
Multi-to-multi reliable multicast error recovery method for plane structure network Download PDFInfo
- Publication number
- CN101127702A CN101127702A CNA2007101198965A CN200710119896A CN101127702A CN 101127702 A CN101127702 A CN 101127702A CN A2007101198965 A CNA2007101198965 A CN A2007101198965A CN 200710119896 A CN200710119896 A CN 200710119896A CN 101127702 A CN101127702 A CN 101127702A
- Authority
- CN
- China
- Prior art keywords
- message
- reliable
- turn
- server
- multicast
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The utility model relates to a multi-to-multi and reliable multi cast error restoring method applied in the flat surface structured environment of local network. The method can restore the multi cast lost message by the way of setting the cache of a plurality of sending pitch points, receiving the cache of a plurality of pitch points and the cluster of a reliable multi cast server. When the initialization, all the pitch points and the reliable multi cast server register and get the only ID and the configuration file in the whole network from a main control server. The utility model adopts the technical proposal that: firstly, the data message cached is transmitted to the whole multi cast group by the sending pitch points through casting; secondly, the lost message is received and tested by the reliable server and the retransmission request is sent by the receiving pitch points in the multi cast respectively; wherein, the restoring strategy is chosen according to the message transmission request (reliable, time delay, ordered) and the retransmission request is sent by the receiving pitch points; thirdly, the data message is searched and the request is responded. The utility model is characterized in settling the communication reliability problem of the multi-to-multi, planar and large scale pitch points in the local network. The utility model has the advantages of having low computation complexity and broad applicability to choose the restoring strategy fast according to the different transmission request to restore the message within valid time and polymerize the request and to retransmit message effectively, reducing the occupancy of the network resource of the retransmit or request the message and decreasing the cost of network burden and pitch points greatly.
Description
Technical field
The present invention relates to the computer network transmission technology, specifically a kind of error recovery method that is used to realize the reliable multicast transfer of data in this field that is applied in.
Background technology
Along with the appearance of development of internet technology and a large amount of emerging services, traditional data communication mode can not satisfy demands of applications.In video conference, remote teaching, network interactive recreation, remote dummy reality etc. are used,, not only waste a large amount of network bandwidths, and efficient is very low if with traditional point to point link mode.Multicast adopts the message ways of distribution of one-to-many as a kind of group of transmission mechanism, can effectively save bandwidth, but because it is a kind of transmission means as possible, can not handle the mistake in the transmission course, can't guarantee the reliability of data message.In order to satisfy application demand, how to design a kind of reliable multicast (Reliable Multicast) mechanism that can finish the reliable transmission function of TCP in the similar unicast services, make it in the cast communication process, can be according to the divide into groups situation of message of network loss, recover the message lose efficiently rapidly,, make the recipient receive correct, orderly message, become current research focus.
Reliable multicast implementation commonly used mainly contains based on the reliable group communication of TCP with based on the reliable transmission dual mode of IP multicast.Wherein, the reliable group communication mode of TCP is to adopt multicast packet is duplicated many parts, sends in turn with TCP that different recipients realizes.This mode realizes simply, can guarantee the real-time and the reliability of data, but the overhead that brings owing to the characteristics of TCP itself is big, system availability is low, make whole system when sending data, be easy to cause congested and cause network meltdown collapse, poor expandability; And the reliable transmission mode of IP multicast, it only needs to send a data copy, message just can duplicate in network transmission process as required automatically, avoided many unicast streams to establish a communications link and sent the shortcoming of data message separately for each recipient, overhead is little, but because it is based on the realization of IP multicast, in message transmission procedure, lose with out of order and happen occasionally, therefore, how to guarantee the reliability of data, enable effectively to revert to key issue for IP multicast reliable transmission mode to losing message.
The problem that error control is faced in the reliable multicast is more many than reliable clean culture complexity, comprise: by whom be responsible for detecting loss of data, adopt which kind of mode to send testing result and control signal, adopt which kind of recovery algorithms to recover the data of losing, and acknowledge message inhibition, time-delay, extensibility and network isomerism problem etc.At present, the implementation that mistake is recovered is more, concludes to get up to mainly contain: based on the NACK feedback, as SRM and MDP2, thereby this quasi-protocol does not need the support of particular network structure by NACK request retransmission limiting network flow; Based on the ACK feedback of tree, as RMTP, RMTP-II, TRMP, this quasi-protocol suppresses the blast of ACK message by utilizing the server in the network; Based on the FEC encoding and decoding, thereby this quasi-protocol is not owing to need reach higher throughput from the feedback of recipient and network condition; Utilize router software, as PGM, this quasi-protocol can and utilize route software to carry out negative feedback and re-transmission in conjunction with above-mentioned three quasi-protocols.Wherein,, be fit to the transmission mode of one-to-many based on the reliable multicast traffic model of tree-shaped or hierarchical structure, and and if only if the structure match of structure of models and routing tree just has higher performance under the situation preferably.Therefore need in time obtain topology of networks, and when the multicast group dynamic change bigger, detect network configuration in real time and will bring too much offered load.Error resilience algorithms based on FEC has higher requirements to vector operation, realizes bringing bigger time-delay with software approach.
Above error recovery method respectively has pluses and minuses, also have some researchs that multi-method is traded off or combination simultaneously, attempt to obtain a kind of error recovery method of better adaptability, but existing research mainly is based on one-to-many reliable multicast end to end, the reliability of transmitting between emphasis consideration communicating pair node.And in large-scale distributed LAN environment, the data volume that multi-to-multi planar structure multicast node (be transmit leg be again the recipient) is produced has increased the computational load of wrong recovery the complex nature of the problem and node along with the increase of scale increases fast.At present in the world, the research for this respect does not also have good way.
Summary of the invention
The purpose of this invention is to provide a kind of multi-to-multi reliable multicast error recovery method that is used for plane structure network, make receiving terminal in large-scale distributed LAN environment, can fast and effeciently recover according to the message dropping situation, guarantee reliability of data transmission message.Described method has the autgmentability height, the real-time and little characteristics of node expense.
For finishing purpose of the present invention, the technical scheme that the present invention takes comprises the steps:
1) the data cached message of sending node is sent to whole multicast group with it by the multicast mode;
2) reliable server in the multicast group and receiving node receive respectively and the deal with data message, send repeat requests when detecting message dropping;
3) search data message, response request retransmits message to the request end.Thereby make message reach reliable.
Compared with prior art, the invention has the beneficial effects as follows: (1) the present invention stores all multicast group data by a reliable multicast server group of planes is set, when receiving node finds that the packet loss request recovers, server is the data retransmission message fast and effeciently, has guaranteed the real-time of data; (2) the reliable multicast server adopts the multicast mode to back up, and can reduce reliable server as far as possible mistake is retransmitted the influence that the message time delay is brought; (3) receiving terminal can require (reliable, time delay, orderly) to select different message recovery policies according to message transmissions, provides possibility for satisfying the different application demand; (4) adopt message convergence mechanism that request message is merged, reduced re-transmission message and request message, reduced network burden the occupancy of Internet resources; (5) utilize the transmitting terminal metadata cache that reliable multicast server message dropping is recovered, alleviate the overhead that loss recovery brings to multicast node greatly, can effectively increase network utilization and the overall performance of system.
Description of drawings:
Fig. 1 is a reliable multicast mistake recovery system structure chart;
Fig. 2 detects and request retransmission message flow chart for reliable server;
Fig. 3 detects and request retransmission message flow chart for receiving node;
Fig. 4 is a reliable server processing request message process chart.
Embodiment:
The transmission means that the present invention relates generally to mainly contains:
Multicast: the message ways of distribution as possible that is a kind of one-to-many.Packet loss and out of order problem may take place in message transmitting procedure, are a kind of unreliable transmission meanss.The present invention mainly is to use the multicast mode message that transmits and receive data.
Reliable UDP: be a kind of message based reliable communication mode, bottom adopts UDP (User Datagram Protoco (UDP)) as bearing protocol.It can guarantee reliably transmission according to the order of sequence of message, has certain redundancy, and message structure is simple, and resource occupation is few.The present invention mainly is to use this mode to send request message and the re-transmission message is lost in transmission.
The present invention is described in further detail below in conjunction with drawings and Examples.
Under LAN environment, whole reliable multicast system model is made up of sending node, receiving node and reliable multicast server cluster three parts.Wherein, sending node, receiving node and reliable multicast server cluster are planar structures, and their each nodes in network are in all node status of peering structure and equate.As shown in Figure 1.
In large-scale distributed LAN environment, the reliable multicast server cluster mainly is divided into main control server and reliable server group two parts.Main control server is the manager of whole model, the configuration effort when having undertaken system initialization.Main control server receiving group node and reliable server registration; Generate and safeguard the mapping table configuration file; The receiving group node adds the multicast group request of withdrawing from.Reliable server group provides the main body of reliability services, is responsible for the backup message and the multicast node packet loss is carried out the mistake recovery.
When initial, sending node, receiving node and reliable server group all send registration by the mode of reliable UDP to main control server, behind to be confirmed the passing through, obtain an ID and a configuration file that the overall situation is unique, main control server notice reliable server adds multicast group backup message and the response repeat requests message of being responsible for simultaneously, and one of them reliable server can be responsible for the work of a plurality of multicast group, to satisfy the reliable demand of extensive multi-to-multi.
The present invention is a kind of multi-to-multi reliable multicast error recovery method that is used for plane structure network, and it comprises following steps:
1) the data cached message of sending node, and it is sent to whole multicast group by the multicast mode;
2) reliable server in the multicast member and receiving node receive respectively and the deal with data message, send repeat requests when detecting message dropping;
3) search data message, response request retransmits message to the request end, thereby makes message reach reliable.
Above-mentioned steps 1) in, sending node safeguards that for each multicast group sends a buffering, is used to store the message of losing without the message and the response reliable server of reliable server affirmation and recovers.Sending node is put into these data earlier before sending message and is sent the buffering backup, sends by multicast then, and reliable server and receiving terminal receive message by multicast.
As shown in Figure 2, above-mentioned steps 2) reliable server handle and detect the data message detailed step and be divided into:
2.1) receiving data packets, search the corresponding buffer queue that receives of multicast group according to its sequence number;
2.2) judge type of message and whether have message dropping, be, then empty message is inserted the buffer queue correspondence position, and send the NACK request to the source transmitting terminal, turn to 2.3); , then do not turn to 2.3);
2.3) revise the current maximum message segment value of receiving, deposit data message in buffer memory, turn to 2.1) continue reception and handle all the other messages;
Step 2.2 wherein) be further divided into again:
2.2.1) whether judge test serial number greater than the current maximum message segment sequence number lastReceived+1 that receives of the corresponding multicast group of reliable server, if greater than, show packet loss has taken place, then turn to 2.2.2); If equal, show normally, turn to 2.2.3); If less than, turn to 2.2.4);
2.2.2) empty message is inserted the buffer queue correspondence position, and send the NACK request to the source transmitting terminal, turn to 2.3);
2.2.3) will not send ACK counting and add 1, and judge whether counting arrives maximum, is, then sends the ACK message to the source transmitting terminal, be used for the message received in the clear to send end buffer memory reliable server, turn to 2.3); , do not turn to 2.3);
2.2.4) showing message owing to network problem, the back arrives in the big message of sequence number, and as retransmitting the message processing, judge whether the buffer memory correspondence position is empty with it this moment, be, then deposit this position in, not, illustrate that then this message has been retransmitted recovery, abandon this message, turn to 2.3).
As shown in Figure 3, above-mentioned steps 2) in, be that the member's of multicast group receiving node is handled and detection data message step equally, be further divided into:
2.1) receiving data packets, search the corresponding buffer queue that receives of multicast group according to its sequence number;
2.2) judge type of message, and whether detection messages exist and lose, and is, then requires (reliable, time delay, in order) to select message recovery policy according to message transmissions, turns to 2.3); , then do not turn to 2.3);
2.3) revise the current maximum message segment value of receiving, deposit data message in buffer memory, turn to 2.1) continue reception and handle all the other messages;
Described step 2.2) in, transmission requirement mainly contains following attribute:
Reliably: require message all to arrive receiving terminal, do not allow to lose message;
Time delay: exceed the time delay scope, message belongs to useless message with expired, need not retransmit and receive;
In order: need message to arrive receiving node by sending order;
For data of different types, reliable transmission is treated with a certain discrimination.Upper layer application need be done specific requirement to transfer of data in the initialization transmission channel, do not explicitly call for if make, then default setting be＜fully reliable, in order, time delay infinity〉attribute; The reliable multicast model receives in the process of handling at message will determine as requested how message is delivered to strategies such as upper layer application and loss recoveries.For example: for the data of file transfer, all messages of losing all ask to recover, needn't the consideration order when message consigns to upper layer application; For the new data more of the attribute in the simulation process, need guarantee the order when message consigns to upper layer application, and the data at no reliable request are not done recovery, reduce expense and time delay that message recovers, guarantee that the real-time of data message is delivered; And, then need to guarantee simultaneously order and reliability for the control message in the simulation process.
Described step 2.2) receiving terminal requires (reliable, time delay, orderly) to select the message recovery policy according to message transmissions, is further divided into:
2.2.1) whether judge test serial number greater than the current maximum message segment sequence number lastReceived+1 that receives of the corresponding multicast group of reliable server, if greater than, show packet loss has taken place, then turn to 2.2.2); If equal, show normally, turn to 2.2.5); If less than, show that the back arrives earlier in the big message of sequence number, turns to 2.2.6);
2.2.2) require (reliable, time delay, orderly) to select the message recovery policy according to message transmissions.Judge whether packet loss quantity can tolerate (promptly being reliability requirement), is, show that then message allows packet loss (being applicable to the data of no reliability requirement), turns to 2.3); , then do not turn to 2.2.3);
2.2.3) need to judge whether in order, be, then empty message is inserted the buffer queue correspondence position, for losing the message headspace, turn to 2.2.4);
2.2.4) calculate the message dropping number, and judge and whether lose number greater than sending the NACK threshold value, be then to send the NACK message of this multicast group; Not, then will lose message request and add the NACK formation, and expired time (if there is not delay requirement, then being made as infinity) will be set, turn to 2.3) according to delay requirement;
2.2.5) will not send ACK counting and add 1, and judge whether counting arrives maximum, is, then sends the ACK message to transmitting terminal, be used for the message received in the clear to send end buffer memory reliable server, turn to 2.3); , do not turn to 2.3);
2.2.6) message is handled as retransmitting message, turn to 2.3), herein with reliable server 2.2.4) handle.
Be the quantity and the reduction network overhead that reduce request message, receiving terminal adopts dual mode polymerization request message, is respectively NACK threshold value and timer are set.Wherein, threshold value is set at step 2.2.4) in explanation; It mainly is in order to send NACK request message and the out-of-date message of deletion that timer is set.Timer will all be sent to reliable server with the NACK request message of the current maximum sequence number of receiving of continuous message of subsidiary this multicast group that is accumulated in this cycle at interval by certain hour.Simultaneously, the item in the traversal retransmission list judges according to time stamp whether this has surpassed the delay requirement of message.If surpassed delay requirement, then should from retransmission list, delete by item, if message transmission in order, the position of reserving for this message during then deletion is lined up and cushioned.
In the described step 3), response request is mainly finished by reliable server and sending node two parts.Wherein:
The reliable server part:
Receive and handle the NACK request from receiving terminal, and according to request msg message memory state, select part or full recovery mode, response request retransmits message to receiving node, as shown in Figure 4.Being provided with mainly in order to recover error message of reliable server, it has stored all data in the responsible multicast group of institute.When new receiving node added multicast group, reliable server was responsible for all data re-transmission with this multicast group to this node.
For the NACK that sends from receiving terminal, reliable server divides three classes to handle:
1. all can recover
2. all no shows
3. part can be recovered the part no show
According to this three classes situation, introduce the processing procedure of reliable server in detail below.
For whole recoverable NACK requests, reliable server is searched cache table, find Key value among the NACK begin sequence number to the message backup that finishes sequence number from packet loss in the corresponding backup message, with its packing, send to the receiving terminal of packet loss by Reliable UDP mode.
For the situation of whole no shows, show that reliable server is not received from packet loss yet and begin sequence number to the multicast message that finishes sequence number.Reliable server is on the one hand by step 2) re-transmission of request transmitting terminal.On the other hand, reliable server sends the NACK message of whole no shows once to this machine again.Receive after transmitting terminal retransmits message etc. reliable server, can ask, finish this recovery process according to NACK.
Can recover for part, the situation of part no show, establishing recoverable maximum message segment sequence number is i, but to the message of recovered part, but reliable server adopts all reset modes, recovers sequence number and be the message before the i.Then request message is begun sequence number and change i+1 into, Xiang Benji sends this NACK message once.Handling process is with all no show is identical.
The sending node part:
Receive, handle request and ACK message from reliable server, it searches buffer memory data retransmission message by test serial number, and removes all data before the test serial number.Owing to send the capacity of buffering the upper limit is arranged, after buffering takes, message temporarily can't be put into buffering (also can't multicast go out), just can proceed the message transmission after the message that will have obtained confirming during the ACK message that needs to wait for reliable server this moment will cushion is removed.
Receive the message of request retransmission when reliable server after, whether be empty, if be empty, message is put into buffer memory if searching the corresponding multicast group cache location of message, otherwise, show that message exists, abandon this message.
The present invention mainly is the extensive multi-to-multi plane level of a local area network (LAN) inter-node communication integrity problem, and it not only can be selected reset mode apace according to multiple different transmission requirements, and data can be restored in effective time; And can carry out polymerization to request and re-transmission message effectively, reduced re-transmission message and request message occupancy widely to Internet resources, reduced network burden, adopt different server that many multicast group message is carried out multicast backup and reset mode simultaneously, reduced reliable server mistake has been retransmitted the influence that the message time delay is brought, reduce the expense of each node, avoided the generation of single bottleneck, thereby reached the reliable purpose of message effectively.
The above only is the preferred implementation that the present invention is used for the multi-to-multi reliable multicast error recovery method of plane structure network; should be understood that; for those skilled in the art; be used under the prerequisite of multi-to-multi reliable multicast error recovery method principle of plane structure network not breaking away from the present invention; can also make some improvements and modifications, these improvements and modifications also should be considered as the protection range that the present invention is used for the multi-to-multi reliable multicast error recovery method of plane structure network.
Claims (10)
1. multi-to-multi reliable multicast error recovery method that is used for plane structure network, the reliable multicast member is made up of sending node, receiving node and reliable multicast server cluster three parts, the reliable multicast server cluster mainly is divided into main control server and reliable server group two parts, it is characterized in that comprising following steps:
1) the data cached message of sending node is sent to whole multicast group with it by the multicast mode;
2) multicast member-reliable server and receiving node receive respectively and the deal with data message, send repeat requests when detecting message dropping;
3) search data message, response request retransmits message to the request end.
2. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 1 is characterized in that:
In the described step 1), sending node safeguards that for each multicast group sends a buffer queue, is used for message data cached and that response reliable multicast server is lost and recovers;
Described step 2) in, reliable server and receiving node add multicast group simultaneously and receive data, and set up the reception buffer queue for each multicast group, are used for detection messages and lose, and reliable server also is used to respond the message recovery that receiving node is lost.
3. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 1 is characterized in that: described step 2), reliable server is handled and is detected data message and further comprises the steps:
2.1) receiving data packets, search the corresponding buffer queue that receives of multicast group according to its sequence number;
2.2) judge type of message and whether have message dropping, be, then empty message is inserted the buffer queue correspondence position, and send the NACK request to the source transmitting terminal, turn to 2.3); , then do not turn to 2.3);
2.3) deposit data message in buffer memory, turn to 2.1) continue reception and handle all the other messages.
4. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 3 is characterized in that:
Describedly judge type of message and whether have a message dropping step 2.2) be further divided into again:
2.2.1) whether judge test serial number greater than the current maximum message segment sequence number of receiving of the corresponding multicast group of reliable server, if greater than, then turn to 2.2.2); If equal, turn to 2.2.3); If less than, turn to 2.2.4);
2.2.2) empty message is inserted the buffer queue correspondence position, and send the NACK request to the source transmitting terminal, turn to 2.3);
2.2.3) will not send ACK counting and add 1, and judge whether counting arrives maximum, is, then sends the ACK message to the source transmitting terminal, be used for the message received in the clear to send end buffer memory reliable server, turn to 2.3); , do not turn to 2.3);
2.2.4) showing that owing to network problem the back arrives earlier in the big message of sequence number, handle it this moment as the re-transmission message, judge whether the buffer memory correspondence position is empty, be, then deposit this position in, not, illustrate that then this message has been retransmitted recovery, abandon this message, turn to 2.3).
5. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 1 is characterized in that:
Described step 2) in, receiving terminal is handled and is detected data message and further comprises the steps:
2.1) receiving data packets, search the corresponding buffer queue that receives of multicast group according to its sequence number;
2.2) judge type of message, and whether detection messages exist and lose, and is, then requires to select the message recovery policy according to message transmissions, turns to 2.3); , then do not turn to 2.3);
2.3) deposit data message in buffer memory, turn to 2.1) continue reception and handle all the other messages.
6. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 5 is characterized in that:
Described step 2.2) receiving terminal requires to select the message recovery policy according to message transmissions in, is further divided into again:
2.2.1) whether judge test serial number greater than the current maximum message segment sequence number of receiving of the corresponding multicast group of reliable server, if greater than, then turn to 2.2.2); If equal, turn to 2.2.5); If less than, turn to 2.2.6);
2.2.2) require to select the message recovery policy according to message transmissions, judge whether packet loss quantity can be tolerated, is, show that then message allows packet loss, turns to 2.3); , then do not turn to 2.2.3);
2.2.3) need to judge whether in order, be, then empty message is inserted the buffer queue correspondence position, for losing the message headspace, turn to 2.2.4);
2.2.4) calculate the message dropping number, and judge and whether lose number greater than sending the NACK threshold value, be then to send the NACK message of this multicast group; Not, then will lose message request and add the NACK formation, and expired time will be set, turn to 2.3) according to delay requirement;
2.2.5) will not send ACK counting and add 1, and judge whether counting arrives maximum, is, then sends the ACK message to transmitting terminal, be used for the message received in the clear to send end buffer memory reliable server, turn to 2.3); , do not turn to 2.3);
2.2.6) showing that owing to network problem the back arrives earlier in the big message of sequence number, handle it this moment as the re-transmission message, judge whether the buffer memory correspondence position is empty, be, then deposit this position in, not, illustrate that then this message has been retransmitted recovery, abandon this message, turn to 2.3).
7. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 1 is characterized in that:
In the described step 3), response request is mainly finished by reliable server and sending node, wherein:
Reliable server receives and handles the request from receiving terminal, and according to request msg message memory state, selects part or full recovery mode, and response request retransmits message to receiving node;
Sending node receives and handles the request from reliable server, and it searches buffer memory data retransmission message by test serial number, removes test serial number all data before simultaneously.
8. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 1 is characterized in that:
Described step 2) and 3) in, request message and retransmit message and adopt the mode of reliable UDP to transmit.
9. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 5 is characterized in that:
Described step 2.2) in, transmission requirement mainly contains following attribute:
Reliably: require message all to arrive receiving terminal, do not allow to lose message;
Time delay: surpass the time delay scope, message belongs to useless message with expired;
In order: need message to arrive receiving node by sending order.
10. the multi-to-multi reliable multicast error recovery method that is used for plane structure network according to claim 5 is characterized in that:
Described step 2.2) in, receiving terminal adopts the message convergence mode to send repeat requests to reliable server after requiring to select the message recovery policy according to message transmissions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007101198965A CN101127702A (en) | 2007-08-02 | 2007-08-02 | Multi-to-multi reliable multicast error recovery method for plane structure network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007101198965A CN101127702A (en) | 2007-08-02 | 2007-08-02 | Multi-to-multi reliable multicast error recovery method for plane structure network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101127702A true CN101127702A (en) | 2008-02-20 |
Family
ID=39095629
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007101198965A Pending CN101127702A (en) | 2007-08-02 | 2007-08-02 | Multi-to-multi reliable multicast error recovery method for plane structure network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101127702A (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101848140A (en) * | 2009-03-25 | 2010-09-29 | 冲电气工业株式会社 | Jitter buffer control device, method, program and information processing device |
| CN102098150A (en) * | 2009-12-10 | 2011-06-15 | 中兴通讯股份有限公司 | Reception acknowledgement processing method and base station |
| CN102163231A (en) * | 2011-04-13 | 2011-08-24 | 浪潮(北京)电子信息产业有限公司 | Method and device for data collection |
| CN104205735A (en) * | 2012-03-29 | 2014-12-10 | 国际商业机器公司 | Communication transport protocol for distributed information technology architectures |
| US8977772B2 (en) | 2009-12-17 | 2015-03-10 | Intel Corporation | Method and system for facilitating one-to-many data transmissions with reduced network overhead |
| CN104717257A (en) * | 2013-12-13 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Method and device for transmitting data messages |
| US9525629B2 (en) | 2013-12-13 | 2016-12-20 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for transmitting data packets |
| CN106330414A (en) * | 2016-08-16 | 2017-01-11 | 杭州华三通信技术有限公司 | Message transmission method and device |
| WO2017215583A1 (en) * | 2016-06-16 | 2017-12-21 | 华为技术有限公司 | Video service quality evaluation method and device |
| CN108173807A (en) * | 2017-11-28 | 2018-06-15 | 贵阳语玩科技有限公司 | Unified message is sent, processing method and processing device |
| CN108886409A (en) * | 2016-04-01 | 2018-11-23 | 联发科技股份有限公司 | Data transmission method and device |
| CN110535567A (en) * | 2019-09-20 | 2019-12-03 | 中科睿微(宁波)电子技术有限公司 | A kind of method and system that wlan system polymerization retransmits |
| CN112134659A (en) * | 2020-09-16 | 2020-12-25 | 中国科学院国家空间科学中心 | Error recovery system supporting FDIR function |
| CN112565430A (en) * | 2020-12-08 | 2021-03-26 | 上证所信息网络有限公司 | Low-delay reliable transmission method of multi-market data in wide area network |
| WO2022199558A1 (en) * | 2021-03-22 | 2022-09-29 | 华为技术有限公司 | Data transmission method, and related apparatus and device |
| CN115278291A (en) * | 2022-07-26 | 2022-11-01 | 南京禹步信息科技有限公司 | Screen projection data sharing method and system |
-
2007
- 2007-08-02 CN CNA2007101198965A patent/CN101127702A/en active Pending
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101848140A (en) * | 2009-03-25 | 2010-09-29 | 冲电气工业株式会社 | Jitter buffer control device, method, program and information processing device |
| CN102098150A (en) * | 2009-12-10 | 2011-06-15 | 中兴通讯股份有限公司 | Reception acknowledgement processing method and base station |
| US8977772B2 (en) | 2009-12-17 | 2015-03-10 | Intel Corporation | Method and system for facilitating one-to-many data transmissions with reduced network overhead |
| US10503599B2 (en) | 2009-12-17 | 2019-12-10 | Intel Corporation | Method and system for facilitating one-to-many data transmissions with reduced network overhead |
| CN102163231A (en) * | 2011-04-13 | 2011-08-24 | 浪潮(北京)电子信息产业有限公司 | Method and device for data collection |
| CN104205735B (en) * | 2012-03-29 | 2017-06-13 | 国际商业机器公司 | For the communication transport protocols of distributed IT architecture |
| CN104205735A (en) * | 2012-03-29 | 2014-12-10 | 国际商业机器公司 | Communication transport protocol for distributed information technology architectures |
| WO2015085744A1 (en) * | 2013-12-13 | 2015-06-18 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for transmitting data packets |
| US9525629B2 (en) | 2013-12-13 | 2016-12-20 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for transmitting data packets |
| CN104717257A (en) * | 2013-12-13 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Method and device for transmitting data messages |
| CN104717257B (en) * | 2013-12-13 | 2018-09-28 | 腾讯科技（深圳）有限公司 | The method and device of data message transmission |
| CN108886409A (en) * | 2016-04-01 | 2018-11-23 | 联发科技股份有限公司 | Data transmission method and device |
| WO2017215583A1 (en) * | 2016-06-16 | 2017-12-21 | 华为技术有限公司 | Video service quality evaluation method and device |
| CN107517410A (en) * | 2016-06-16 | 2017-12-26 | 华为技术有限公司 | The method and device that video service quality is assessed |
| US11363346B2 (en) | 2016-06-16 | 2022-06-14 | Huawei Technologies Co., Ltd. | Video service quality assessment method and apparatus |
| US11006185B2 (en) | 2016-06-16 | 2021-05-11 | Huawei Technologies Co., Ltd. | Video service quality assessment method and apparatus |
| CN106330414A (en) * | 2016-08-16 | 2017-01-11 | 杭州华三通信技术有限公司 | Message transmission method and device |
| CN108173807A (en) * | 2017-11-28 | 2018-06-15 | 贵阳语玩科技有限公司 | Unified message is sent, processing method and processing device |
| CN108173807B (en) * | 2017-11-28 | 2021-12-03 | 贵阳语玩科技有限公司 | Unified message sending and processing method and device |
| CN110535567A (en) * | 2019-09-20 | 2019-12-03 | 中科睿微(宁波)电子技术有限公司 | A kind of method and system that wlan system polymerization retransmits |
| CN112134659A (en) * | 2020-09-16 | 2020-12-25 | 中国科学院国家空间科学中心 | Error recovery system supporting FDIR function |
| CN112134659B (en) * | 2020-09-16 | 2023-05-30 | 中国科学院国家空间科学中心 | Error recovery system supporting FDIR function |
| CN112565430A (en) * | 2020-12-08 | 2021-03-26 | 上证所信息网络有限公司 | Low-delay reliable transmission method of multi-market data in wide area network |
| WO2022199558A1 (en) * | 2021-03-22 | 2022-09-29 | 华为技术有限公司 | Data transmission method, and related apparatus and device |
| CN115278291A (en) * | 2022-07-26 | 2022-11-01 | 南京禹步信息科技有限公司 | Screen projection data sharing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101127702A (en) | Multi-to-multi reliable multicast error recovery method for plane structure network | |
| US6934875B2 (en) | Connection cache for highly available TCP systems with fail over connections | |
| Delgrossi et al. | Internet stream protocol version 2 (ST2) protocol specification-version ST2+ | |
| Chawathe et al. | RMX: Reliable multicast for heterogeneous networks | |
| KR100946108B1 (en) | Method and apparatus for group communication with end-to-end reliability | |
| US7929422B2 (en) | Method of moving a transport connection among network hosts | |
| Rajagopalan | Reliability and scaling issues in multicast communication | |
| Hofmann | Enabling group communication in global networks | |
| US20020087912A1 (en) | Highly available TCP systems with fail over connections | |
| WO2006133655A1 (en) | A method for transmitting data reliably by using multicast and unicast protocol and the host for receiving the data | |
| Anastasi et al. | A reliable multicast protocol for distributed mobile systems: Design and evaluation | |
| Jones et al. | Protocol design for large group multicasting: the message distribution protocol | |
| CN111522656A (en) | Edge calculation data scheduling and distributing method | |
| CN103916253A (en) | Information transmission method and system on basis of information center network | |
| CN106059936A (en) | Method and device for multicasting files in cloud system | |
| KR100240645B1 (en) | Packet error controller of multicast communication and method thereof | |
| Koch et al. | Transparent TCP Connection Failover. | |
| JP5029685B2 (en) | Backup device | |
| Kostić et al. | High-bandwidth data dissemination for large-scale distributed systems | |
| CN113612737A (en) | Long message reliable transmission method based on grouping and retransmission mechanism | |
| Buskens et al. | Reliable multicasting of continuous data streams | |
| Gumbold | Software distribution by reliable multicast | |
| JP3326369B2 (en) | Communication device | |
| Fuchs et al. | A naming approach for ALF design | |
| CN111371888A (en) | Multi-source data transmission system and method based on erasure coding |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20080220 |