Communication system and techniques for transmission from source to destination

Abstract

A system and method for transmitting and presenting streaming digital information signals that optimizes performance in the context of goodput, throughput, delay, receiver buffer requirements and tolerance to loss and jitter. The method provides ordering packets of information based on a priority associated with each of the packets; managing the flow of the packets into and out of a buffer; adjusting the rate at which the packets are provided to a communication medium; and transmitting and retransmitting the packets as needed.

Description

This application is a continuation-in-part of U.S. patent application No. 10/254,978 filed on Sep. 27, 2002, which claims the benefit of U.S. Provisional Patent Application No. 60/325,017 filed on Sep. 27, 2001, both of which are hereby incorporated by reference for all purposes as if fully set forth herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a system and method for transmitting signals, and more particularly, the present invention relates to a system and method for transmitting and receiving time sensitive, not fully reliable digital signals between a source and a receiver.

2. Discussion of the Related Art

Time sensitive, not fully reliable digital signals include single-media and multi-media data streams, including audio, audio and graphics, video, and synchronized audio and video data. As discussed herein, the concepts of the present invention are applicable to any system for streaming digital information from at least one sender to at least one receiver in which the data transmission is time sensitive but does not require the fidelity provided by full reliability. In addition, the data or information in the transmission may have a priority scheme, e.g., multiple priorities assigned to different portions, such as packets, of the data or information (e.g., heterogeneous priority).

For example, multimedia data are presented to a user in a time critical way. For example, the auditory experience of the user is hindered if the data are presented too slowly or in an incorrect order. If presented too slowly, the user may hear a lower frequency voice than belongs to the speaker, which decreases the fidelity of the presentation. The decreased fidelity diminishes the utility of such audio data as music. In the case of speech, if data are dropped out or swapped in sequence, the user may be unable to determine what the speaker is saying, which decreases the utility of the communication. As another example, the visual experience of the user is hindered if the video data is presented out of sequence or out of synchronization with the audio data. Out of sequence video data at time scales longer than transmission time for one frame causes smooth motion to become zigzagged as frames are shown out of sequence, destroying the utility for motion critical video such as dance, sporting events, and scientific research. Out of sequence video data on shorter time scales causes portions of a single frame to be presented at incorrect spatial positions on a display screen, so that the image is at best distorted or, at worst, unrecognizable.

Multi-media data takes many forms known in the art. For example, audio data is stored as files of binary data using various formats. In some formats, the data is compressed so that the number of binary digits (bits) when stored in the file is less than the number of bits used during presentation to a human observer. Example image formats, often indicated by extension on the names of the files used to store their data, include GIF, JPEG, TIFF, bit map (BMP), CGM, DXF, EPS, PCX, PDF, PIC, among others. Example audio formats, often indicated by extensions on the names of the files used to store their data, include waveform audio (WAV), MP3, audio interchange file format (AIFF), unix audio (AU), musical instrument digital interface (MIDI), and sound files (SND), among others. Example video formats, often indicated by extensions of the names of the files used to store their data, include QuickTime, AVI and the Motion Picture Experts Group format (MPEG), among others. Further treatment of the subject is provided in the book Video Communication, (1) Image and Video Compression Standards, V. Bhaskaran and K. Konstantinides, Kluwer Academic, 1995.

To allow a plurality of complex systems to communicate, a common set of standards has been established that system and component manufacturers have agreed to use in their systems and components. These standards relate to a basic set of functions. Among the functions, and at the most basic level, is the communication function and the rules, or protocols, for exchanging information. The applicable standard depends on the syntax of the data and the network or system over which the data is sent, for example, MPEG, Cable, Internet, etc. For example, two well-known Internet protocols are the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP). The principles of the present invention are applicable to any such system, regardless of the underlying protocols.

TCP includes a feedback loop that allows for full reliability. TCP guarantees delivery of data and also guarantees that packets will be delivered in the same order in which they were sent. TCP attempts to recover from packet losses by allowing for multiple retransmissions of packets as indicated by the feedback information and adjusts the sending rate dynamically if it perceives packet losses. However, the trade-off for minimizing packet losses is an inherent delay caused by the retransmission process. Thus, TCP is particularly slow for multimedia transport; for example, video transmission is slow if TCP is used. In fact, systems using TCP under lossy conditions can “lock up” so that the user does not see or hear streaming information, thus compromising quality of service. The delay between sending a data packet from a server and receiving the packet at a client is called network latency. TCP is a good protocol for high-latency-tolerant data traffic requiring full reliability.

UDP has no reliability mechanisms, no feedback loop, and provides choppy video transmission. Because UDP is so unsophisticated (or “dumb”), UDP incurs no delay, but does not permit retransmission. UDP is better suited for communications that are not tolerant of high latency. For example, UDP is often used for broadcast transmission.

Applications have been adapted to improve the display quality of streaming signals transmitted over a network such as the Internet or Cable. However, such applications still do not provide high quality display because of the inherent problems in transmission when available bandwidth is limited.

SUMMARY OF THE INVENTION

Accordingly, the present invention is directed to a system for communicating data that substantially obviates one or more of the problems due to limitations and disadvantages of the related art.

An advantage of the present invention is to provide transmission and presentation of streaming digital information signals that optimizes performance in the context of the contentions among different dimensions of performance including goodput, throughput, delay, receiver buffer requirements and tolerance to loss and jitter.

Another advantage of the present invention is to maximize reliability and to minimize latency.

Another advantage of the present invention is to adjust dimensions of performance in view of user experience and requirements.

Another advantage of the present invention is to provide a technique for fast detection of loss of a transmitted signal.

Another advantage of the present invention is to provide proactive buffer management at either transmitter or intermediate nodes.

Another advantage of the present invention is to provide a technique for rate control or congestion control in a constant bit rate environment.

Another advantage of the present invention is to provide a technique for rate control or congestion control in a variable bit rate environment.

Another advantage of the present invention is to provide an interactive signal or feedback to a sender to indicate quality of service requirements of a receiver.

Another advantage of the present invention is to provide an method of sharing over-provisioned bandwidth between network links shared by a plurality of the destinations.

Another advantage of the present invention is to provide a method of fast caching packets transmitted from a source to a destination.

Another advantage of the present invention is to provide a dynamic prioritization of the attributes to particular data depending upon the progress of the connection.

The system adaptation and techniques according to the present invention are beneficial for both non-legacy and legacy systems. System adaptation and techniques according to the present invention can be made at the application or the transport layer of source and client nodes and possibly at the network or data link levels in routers or other nodes. Adaptation at levels other than the application layer (e.g., the transport layer) are beneficial for legacy applications because fine grained adaptation is possible while not affecting any legacy application. Such adaptation differs from conventional adaptation, which can be performed at the application layer only and hence can adapt only in a coarse-grained fashion and also cannot be used to improve the performance of a legacy application.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

To achieve these and other advantages and in accordance with the purpose of the present invention, as embodied and broadly described, a method for providing digital communication, includes ordering segments of information based on a priority associated with each of the segments of the information; managing of flow of the segments into and out of a buffer based on the priority of the segments of information; adjusting a rate at which information is provided to a communication medium; and transmitting the information.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention.

In the drawings:

FIG. 1 illustrates an exemplary flow of signals according to one embodiment of the present invention;

FIG. 2 illustrates an exemplary flow of signals according to another embodiment of the present invention;

FIG. 3 illustrates an exemplary router configuration according to another embodiment of the present invention;

FIG. 4 illustrates exemplary router component functionality according to another aspect of the present invention;

FIG. 5 illustrates an exemplary router configuration according to another embodiment of the present invention;

FIG. 6 illustrates exemplary router component functionality according to another aspect of the present invention;

FIG. 7 illustrates an exemplary router configuration according to another embodiment of the present invention;

FIG. 8 illustrates exemplary router component functionality according to another aspect of the present invention;

FIG. 9 illustrates a block diagram of basic operations performed to optimize the performance of the system according to one embodiment of the present invention;

FIG. 10 illustrates adjustment of functionality of a system according to the present invention based on quality of service requirements or requests; and

FIG. 11 is a flow diagram illustrating an exemplary process for dynamic prioritization according to one aspect of the present invention;

FIG. 12 illustrates an exemplary block diagram of a multimedia streaming session;

FIG. 13 is a flow diagram illustrating an exemplary process for sharing over-provisioned bandwidth according to an embodiment of the invention;

FIG. 14 illustrates an exemplary destination buffer according to an embodiment of the invention; and

FIG. 15 is flow diagram illustrating an exemplary fast caching process according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

FIG. 1 illustrates an example of data flow 101, a control path 102 and feedback 103 using the present system from the sender 105 to the receiver 107 and from the receiver 107 to the sender 105 according to the present invention. Each of the paths will be discussed with respect to FIG. 1.

The data flow path 101 is from the sender 105 to the receiver 107. The flow of the data is affected by any of a number of operations at the sender side 105 or the on the receiver side 107. Also, the type of data can influence the various operations performed on the data.

Again, referring to FIG. 1, a priority order assigned to the data is assigned according to an expert system 109 on the sender side 105. The sender side 105 may also replicate 111 important data or data packets for transmissions along the data path 101 based on the priority assigned by the expert system 109. Also, packet interleaving 113 is performed on the sender side 105 and may be performed according to the priority assigned by the dynamic prioritization expert system 109. Other techniques for error correction coding may also be applied. Data is buffered 115 and placed on a transmission medium, e.g., on an open network such as the Internet, on a closed network such as a wide area or local area network, on a broadcast system or on a point to point system, or the like. Typically, the data is passed through an interface 117, such as a network interface, before being placed on the transmission medium.

At the receiver side 107, the data is typically received via an interface 117, such as a network interface, from the transmission medium. At the receiver side 107, loss detection 119 is performed. Also, if the capability is available, error concealment 121 is performed on the data flow 101. The data is buffered 123 and provided to the receiver side application 125 for use by a user.

Each of the operations performed on the data in the data path 101 can be affected by any of a number of operations such as prioritization 109, replication 111, interleaving 113 and buffering 115, among other operations not described here, but known to those of skill in the art, including error coding or similar operations. According to the present invention, the operations performed on the data are adaptable based on feedback and controls between and among the receiver 107 and the sender 105. These operations can be performed singly or in any combination or order.

The feedback path 103 is shown as a dotted line in FIG. 1. At least three types of feedback from the receiver/destination 107 are useful in improving the quality and reliability of data transmission according to the present invention. For example, there are signal/data feedback such as whether a signal was actually received, network feedback such as available bandwidth, and receiver feedback such as buffer overflow at the receiver.

As shown in FIG. 1, receiver feedback 103a includes information about whether the receiver has an error concealment function that can compensate for losses in the data transmitted from the sender 105. Data loss detection feedback is provided to the sender only if error concealment 121 cannot compensate for information lost. Error concealment 121 can be performed by interpolating the data actually received to estimate the data not received. Buffer management feedback 103b is provided to prevent buffer overflow at the receiver such that information is lost because the buffer must discard data that does not fit into the buffer at the receiver. The buffer manager 124 actively monitors buffer activity at the destination. In most cases, receiver feedback 103d will be empirical data about actual losses in the data received by the receiver or destination application 125. The use of the receiver feedback will be discussed with respect to sender side 105.

Network feedback 103c includes bandwidth availability information that is used by the sender to adjust the rate at which data or data packets are placed on the network or transmission medium at the network interface, i.e., rate control 126. The rate at which data or data packets are placed on the network or transmission medium is the rate at which the buffer is drained, if the buffer 115 is populated with information. A buffer management algorithm 127 can adjust the drain rate of the buffer 115 according to the rate at which the application provides information to the buffer 115 and according to the bandwidth availability information from the network feedback 103c. The buffer management algorithm 127 can also drop information according to apriori information about the data priority, the buffer characteristics or the network characteristics.

Signal feedback 103d may be provided actively, for example, for each block of data transmitted, a signal is sent back to the sender to indicate that the block was received or not received. However, such feedback can take up valuable bandwidth or induce time delay while the sender evaluates the feedback before compensating for lost data. Therefore, while a positive feedback signal may be used, a negative feedback signal is preferred. That is, the receiver only sends a feedback signal that it did not receive a data block or packet or a portion of a data block packet, but the receiver does not send any signal if the data is received without loss. In addition, even if the system does not receive a portion of data, but the error can be effectively concealed at the receiver, a negative acknowledgement feedback signal does not need to be provided to the sender.

Signal feedback 103d can be provided to any of the various operations performed on the server side. For example, the priority assigned by the dynamic prioritization algorithm can be calculated based on the rate at which information is being lost. The degree of packet replication can be increased or decreased to compensate for the loss rate on the system. Also, the sender can retransmit replicated packets or blocks when a feedback signal from the receiver indicates that data has been lost.

The sender 105 may have a separate retransmission buffer 129 for buffering data according to the dynamic priority scheme. The retransmission buffer 129 may also be part of the main buffer for buffering the data flow that is transmitted.

As illustrated in FIG. 2, intermediate routers 230 may be in the path between the source 205 and destination 207. As will be discussed with reference to FIGS. 3-8, the intermediate routers may have varying degrees of functionality of the source and destination included.

In the router configuration illustrated in FIG. 3, the routers 330 do not respond to any of the feedback between the destination 307 and the source 305. As illustrated in FIG. 4, the router configuration illustrated in FIG. 3 may include dynamic priority 409, buffer 415, buffer management 427, and rate control 426 according to the present invention.

In the router configuration illustrated in FIG. 5, the routers 530 may include the source components 532 of the present system so that the routers 530 can adapt based on feedback from the destination 507 or from a router 530 that is upstream and therefore can be adjusted based on feedback from an upstream router or the destination. For example, as illustrated in FIG. 6, the router illustrated in FIG. 5, may include dynamic prioritization 609, packet replication 611, packet interleaving 613, buffer 615 and buffer management 627, rate control 626, and loss retransmission 616, as in the source according to the present invention.

In the router configuration illustrated in FIG. 7, the routers 730 may include the source components 732, as described with respect to FIGS. 5 and 6, and also include receiver components 734 of the present system so that the router 730 can adapt based on the data from a downstream router R2 or destination 707. For example, as illustrated in FIG. 8, the router R1 on the upstream side may include source components 732, such as, dynamic prioritization 809, packet replication 811, packet interleaving 813, buffer 815, buffer management 827, rate control 826, and loss retransmission 816 as in the source 705 according to the present invention. In addition, for example, the router R2 on the downstream side may include receiver components 734 according to the present invention, such as fast loss detection 819, error concealment 821, buffer 823, and buffer management 824.

A statistical multiplexer (Stat Mux) can also be implemented with any and all of the features as discussed above with respect to intermediate routers.

Several of the operations performed in the architecture of an exemplary architecture according to the present invention will be discussed with respect to FIG. 9. FIG. 9 is a flow diagram illustrating the operations performed on the receiver and server sides. As can be seen in the figure, the operations in the present system architecture interrelate to one another and the system adapts according to the information flowing between the operations.

Initially, the prioritization is set based on the initial encoding of the signal. The dynamic priority calculation 909 also can take into account the application information at the client device and service requirement information from the user. The prioritization scheme that results from the dynamic priority calculation 909 is provided to a transmission/retransmission mechanism that will request transmission or retransmission via a network 904. In other words, the data may be prioritized according to a plurality of application, network and signal attributes. When a loss of data occurs, the system may retransmit the data as appropriate or drop the data as appropriate, depending on the prioritization or attributes.

A loss detector 919 determines whether a signal received over the network 904 includes information losses. As discussed above, the loss information may be provided to the dynamic priority calculation 909. After the initial prioritization when transmission begins, the dynamic priority calculation 909 is revised to include the loss information from the loss detector 919. Dynamic priority calculation 909 according to the present invention will be discussed in greater detail below.

One method for providing loss detection information to the server is to provide only negative loss information for data in which errors cannot be concealed. So, the only signals that are reported as lost to the server are those that cannot be concealed at the receiver. A positive acknowledgement for other data is assumed. For example, if two negative acknowledgments are received for first and third data packets sent, but no negative acknowledgment is received for the second data packet, then it is assumed that the second data packet was not lost. Loss detection according to the present invention will be discussed in greater detail below. Some positive acknowledgement at coarse granularity can be used to recover from losses of negative acknowledgements.

A signature profile sent by the sender to the receiver, perhaps as a signal header, provides information to the receiver about the time synchronization of the signal being transmitted. In other words, the receiver knows when to expect a data packet in the signal stream based on the signature profile, which can be thought of as time signature and/or priority signature for packet or data receipt.

As discussed above, the network 904 also provides information as to bandwidth and transmission rate. The rate or bandwidth information is taken into account in rate control 929 and buffer management 927, which includes a mechanism for dropping low priority data 902. Buffer management 927 is required if the transmission rate exceeds the network transmission rate. The buffer manager can predict in advance if there is going to be a data overflow based on information in the signature profile. Buffer management according to the present invention will be discussed in greater detail below.

According to the present invention, a plurality of inventive techniques may be used to optimize transmission of information in a network environment. Various aspects of these techniques are discussed in details as follows.

Loss Detection

It is always desirable to have knowledge of a packet drop inside the network as soon as possible. This is more so in a video streaming application as information is time sensitive. Most mechanisms for loss detection rely on a time out at the sender (which is a coarse estimate of the time taken for an acknowledgment to come back from the receiver). However, such timeouts, being coarse, introduce a delay into the packet stream that can result in large buffer requirements or alternatively larger over-provisioning of bandwidth. (Over-provisioning of bandwidth is discussed further below.)

One method for providing loss detection information to the server is to provide only negative loss information for data in which errors cannot be concealed. So, the only signals that are reported as lost to the server are those that cannot be concealed at the receiver. A positive acknowledgement for other data is assumed. For example, if two negative acknowledgments are received for first and third data packets sent, but no negative acknowledgment is received for the second data packet, then it is assumed that the second data packet was not lost.

The present system provides loss detection much faster than conventional positive acknowledgement systems. In these conventional systems, the sender expects to receive positive acknowledgement of a signal from the receiver at a certain time. If the source has not received the expected acknowledgement by the certain time, the sender continues to wait for some additional time period to see if it receives the acknowledgement. Only after the additional time period does the sender of the conventional system accept that the signal is lost and take measures to compensate for the lost signal, such as performing a retransmission, if necessary.

In the loss detection of the present system, the waiting period is dynamically tuned based on the priority of expected data. A signature profile in advance of the information signal may provide time synchronization information (codes) and priority information (priority profile) about the signal to be received, including when a signal is to be expected. The signature profile also provides information to the receiver about inter-packet separation time (IPS) if the traffic is variable bit rate. IPS between any two consecutive packets can be different. Such IPS information is provided by the signature profile. Based on the signature profile, the receiver knows when to expect a signal and when to expect the subsequent signal. That is, if a first signal is expected at t_i, then the next signal is expected at t_i+1=t_i+IPS_i. In the loss detection according to the present system, when time t_i+1 is reached, but the expected signal has not been received, then the receiver takes action to compensate for the lost signal.

Generally, loss detection of the present invention is more aggressive in proportion to the priority of a packet in a heterogeneous priority system. In general, the relationship between reporting of a loss and the packet priority is a monotonically non-increasing function.

In some systems, packets arrive in a periodic stream with a certain fixed or variable EPS between packets. In file transfer, for example, packets may be transferred back to back with little or no IPS. However, packet arrival timing and interpacket separation may be determined by actual monitoring of the packet stream over time, e.g., by empirical data. After empirical sampling, the system can adjust for an interpacket separation that can vary because the available transmission rate changes.

An exemplary client side loss detection algorithm makes use of intelligence provide by the signature profile.

At the beginning of the connection lifetime, the sender sends across to the receiver the signature profile. The signature profile may include time stamp information and/or priority information according to whether the signal is constant bit rate or variable bit rate and to whether the signal has homogeneous or heterogeneous priority. If the signal is constant bit rate, then only the streaming rate R and the packet length L is included instead of time stamp information in the signature profile.

The priority profile indicates the list of priorities for the packets to be streamed. For example, let p_i be the priority for the first packet.

After the receipt of the i^th packet, the client waits, for example,

T_w=c1*f_x(L/R)+c2*f_y(K(p_i+1))*f_z(dev(J))

• • before it sends a negative acknowledgement (NACK) to the sender. The parameters in the expression are as follows:

K(p_i+1) is a constant specific to the priority level for the expected packet.

K(x)>K(y) if, and only if, x<y

That is, for a high priority packet, K(p) will be low, making the client send the NACK faster to the sender.

Thus, faster feedback is given to the sender and at the same time, spurious retransmissions are prevented for low priority packets.

Another aspect of the loss detection of the present system, a start up delay is provided to allow for jitter compensation and retransmission time when a loss is detected and retransmission is requested. The start up delay depends on buffer size. The variable loss detection as described above minimizes the start up delay requirements by requesting retransmission faster and limiting the retransmission requests to higher priority information. Such advantages are particularly helpful in systems having a fixed buffer size or where users require a smaller start-up delay.

While this “fast” lost detection system is described for use in systems having information having heterogeneous priority, such loss detection is also applicable to data systems having no priority scheme.

This “fast” loss detection can also be used in systems having selective acknowledgement of received signals, such as in a traditional Internet environment. The “fast” loss detection can also be used in conjunction with error concealment techniques.

Buffer Management

The present system includes active buffer management both at the source and the receiver. Buffer management at the receiver will be discussed with respect to flow control.

On the source side, a buffer manager monitors the fill rate of a buffer before the interface between the source and the network. The buffer manager monitors whether the buffer overflows or is about to overflow. In this system, if the rate that data is output is sufficiently greater than the fill (input) rate of the buffer, the buffer remains empty, and there is no need for buffer management. It is possible that, for small time periods, the output rate is greater than the fill rate, and for other periods of time that the input rate is greater than the output rate, so the buffer management may be necessary. If the output rate onto the network is equal to or less than the fill rate of the buffer, there needs to be buffer management, and information may need to be dropped before it is placed on the network. In typical systems, the next packet to be placed in a filled buffer is dropped without regard to the importance of the information contained in the packet. However, the present system takes into account the priority or importance information related to the information in the buffer and the information that needs to be placed in the buffer. A rate control algorithm controls the output rate.

Priority drop removes lower priority packets from the queue if higher priority packets needs to be buffered.

Proactive drop predicts a loss in advance based on the expected timing of receipt of information having different priorities and on the current estimate of the output rate as determined by the rate control component. If a loss is predicted, it drops lower priority information even if the buffer is not yet full. In some systems, the proportion of priorities in an information stream does not fluctuate. Using this information, the buffer manager can predict what the priority of the next incoming information will be and can determine if the buffer is able to receive all of the higher priority information. If the buffer predicts the loss of information that have priority higher than some of the packets in the buffer, the buffer manager will instruct the buffer to drop a number of lower priority packets from the buffer to accommodate the incoming higher priority information. This drop instruction can be given to the buffer even if the buffer is not full if the amount of predicted high priority incoming information warrants such a drop.

Even if the priority profile of an information stream does fluctuate, the signature profile can provide sufficient information for proactive buffer management and predict packet receipt. In addition, the buffer manager may know from its own information or by notice from another system, e.g., the rate controller, that the buffer will overflow. For example, the buffer manager can predict the priority of the information in the buffer when a high priority packet P is expected. If the buffer manager predicts that the only information in the buffer when the high priority packet P is received are packets P_x of the same priority or higher priority than the high priority packet P, the buffer manager can instruct the buffer in advance to drop lower priority packets to allow the higher packets P_x in the buffer not to be dropped and to be transmitted earlier than they would have been otherwise.

Such proactive drop is particularly applicable to any data scheme that has heterogeneous priority.

Shared Over-provisioned Bandwidth

Due to the random packet loss over the path from a source to a destination, to get a perfect data stream the bandwidth is over-provisioned. As referred to herein, over-provisioned bandwidth refers to an amount of bandwidth reserved for a network path, in addition to the amount of bandwidth needed to transmit the original data stream. Accordingly, the reserved bandwidth is equal to the media bandwidth plus the over-provisioned bandwidth. The over-provisioned bandwidth (OPB) is utilized to increase the reliability of the system. Depending on the scheme employed, the OPB is utilized to retransmit lost packets, or to transmit error correction/concealment information.

Different error correction methods/schemes have different bandwidth requirements referred to herein as BR(t). For example in automatic repeat request (ARQ) scheme, BR(t) has the same randomness and burstness as that of the network path because the amount of extra bandwidth required is dependent on the number of packets lost during transmission. In contrast, in a forward error correction (FEC) scheme, BR(t) is a constant because the additional correction bits are transmitted regardless of whether or not a packet is lost.

In an ARQ scheme, the over-provisioned bandwidth OPB is utilized to retransmit lost packets. Therefore, the amount of over-provisioned bandwidth needed in an ARQ scheme is defined as the maximum number of packets requested by the destination to be retransmitted during any given time period T. OPB=max(BR(t)).

When an ARQ scheme is utilized in a streaming session including one source and multiple destinations, for example, one server and M clients (M>1) as shown in FIG. 12, over-provisioned bandwidth for each network path from the server 1202 to clients 1 . . . M is needed, (OPBi, i=1 . . . M). The number of packets a client-i requests to be retransmitted during a period T, BRi(t) where t=T, 2T, 3T . . . , varies due to the random nature of packet loss over the network path during streaming. Therefore, the over-provisioned bandwidth for each link between the server and a client i is the maximum number of packets requested by client I during the time period t, OPBi=max(BRi(t)) where t=T, 2T, 3T, . . .

As shown in FIG. 12, the network path between the server 1202 and the M clients 1208 share at least one network link 1210. In conventional systems, the over-provisioned bandwidth OPBi for each individual link I is reserved for the shared link. As a result, the total over-provisioned bandwidth over the shared link is the sum of the individual OPBs, $\sum _{i=1}^M\mathrm{OPBi}=\sum _{i=1}^M\max \left(\mathrm{BRi}\left(t\right)\right)\mathrm{where}t=T,2T,3t\dots$
However, this method of over-provisioning the shared link is inefficient because it assumes that each of the clients will require all the over-provisioned bandwidth at the same time, which is not likely to be the case.

The present invention overcomes the inefficiency of conventional methods by providing a method by which the clients share the over-provisioned bandwidth reserved for the common network link. According to an embodiment of the invention, when ARQ is applicable, the multiple clients share the over-provisioned bandwidth at the common network links such that the total shared over-provisioned bandwidth, SOPB, reversed for a common link is the maximum of the number of packets requested by all the clients which share the link during the time period t, $\mathrm{SOPB}=\max \left(\sum _{i=1}^M\mathrm{BRi}\left(t\right)\right),$
where t=T, 2T, 3T and i=1 . . . M. Because the following inequation holds, the bandwidth saved by the invention is $\sum _{i=1}^M\max \left(\mathrm{BRi}\left(t\right)\right)-\mathrm{SOPB}.$ $\begin{array}{c}\mathrm{SOPB}=\max \left(\sum _{i=1}^M\mathrm{BRi}\left(t\right)\right)\le \sum _{i=1}^M\max \left(\mathrm{BRi}\left(t\right)\right)\\ \sum _{i=1}^M\mathrm{OPBi}(t=T,2T,3T\dots )\end{array}$

FIG. 13 illustrates an exemplary method for providing shared over-provisioned bandwidth according to an embodiment of the invention. The process begins at step 1301 with the initialization of the individual OBP for each client i, based, for example, on the traffic trace history for the individual network paths. In other words, OPBi is set to the maximum number of packets lost along the path in any period of T. At step 1303, the shared over-provisioning bandwidth is initially set to the sum of the individual bandwidths, $\mathrm{SOPB}=\sum _{i=1}^M\mathrm{OPBi}.$
At step 1305, the server monitors the extra bandwidth, BRi(t), requested by each client-i during the monitoring window T. At step 1307, the individual and shared over-provisioning values are updated, i.e., OPBi is set to max(BRi(t)) and SOPB is set to max $\left(\sum _{i=1}^M\mathrm{BRi}\left(t\right)\right).$
This process repeats periodically, every K seconds.

Flow Control

Flow control is used to coordinate the transmission process at a source and the receiving process at a destination, for example from a server to one or more clients. The feedback channel discussed above allows a receiver to send back status information regarding, for example, packet loss and/or fullness of the receiving buffer, to the sender. The sender can then adjust its sending rate based on the feedback if necessary.

Buffer management 1408 at the receiver allows for flow control. That is, if the receiving rate at the destination changes for whatever reason, the buffer 1404 will fill at a changed rate. The buffer manager 1408 will detect the different fill rate at the receiver, client 1406 and provides feedback to the source, server 1402, that the sending rate should be adjusted. In other words, the buffer 1404 at the receiver 1406 is actively monitored in order to prevent overflow. Generally, the sending rate is maintained such that the buffer is less than half full.

As discussed above, in the event of packet loss, the sender uses a retransmission protocol, for example, ARQ, to retransmit lost data packets on the over-provisioned bandwidth. The over-provisioned bandwidth is set based on the maximum number of packets requested over a defined time period. While the OPB is updated on a periodic basis, during a specific time period, known as the current OP window, there is a fixed amount of over-provisioned bandwidth N. Furthermore, the server receives requests for retransmission of a number, M, of lost data packets during each Op window. If the number of packets requested for retransmission is less than the amount of over-provisioned bandwidth, M≦N. then the retransmission request is satisfied. However, if M is greater than N, only N of the M packets will be transmitted. In other words, M−N of the packets requested for retransmission will not be transmitted. Accordingly, in the first case (M<N), part of the over-provisioned bandwidth is not utilized, and in the second case (M>N) a number (N−M) of the requested packets are not retransmitted. Both cases are possible in a streaming session due to the randomness of packet loss.

According to an exemplary embodiment of the invention, the unused OPB in the first case is utilized to create retransmission credit. The retransmission credit is then used to decrease the number of denied retransmission packets in the second case. The retransmission credit is created by fast caching media packets. Media packets, as used herein, refers to packets which are being transmitted for the first time. According to the invention, when there is unused OPB and there is buffer space available at the client end, the server sends media packets faster than the encoding rate using the unused OPB. This increase in the sending rate results in a retransmission credit because the server can subsequently decrease the sending rate below the encoding rate (thereby using less of the reserved bandwidth). The unused media bandwidth or “retransmission credit” is then used to retransmit lost packets.

FIG. 15 illustrates an exemplary method for fast caching media packets according to an embodiment of the invention. The process begins a step 1501 with a request from the server to the client for the status of the receiving buffer. The client sends back the amount of available receiving buffer space (current_buffer) to the server every T seconds. At step 1503, the feedback arrives at the server (t1 seconds after the beginning of current OP window). The server then estimates the buffer space available at the end of the OP window (future_buffer) at step 1505.

The amount of buffer space available at the end of the op window is equal to the current buffer minus the packets received since transmission of the current buffer value. Accordingly, future_buffer=current_buffer−(T−t1+RTT)*(sending rate—encoding rate). At step 1507, the sever determines whether or not the future buffer, i.e., the amount of space in the receiving at the end of the Op window, is greater than 0. If the estimated future buffer is less than or equal to zero then there is no space to cache media packets. Therefore, no retransmission credits can be generated as illustrated by the NO path out of step 1507. If there is space in the receiving buffer (YES path out of step 1507), then the server determines if there is any unused OPB at step 1509. If there is used OPB, i.e., M<N, and future buffer>0 (YES path out of step 1509) the sever will increase the sending rate at step 1511 such that min((N−M), future_buffer) additional packets are transmitted to the receiving buffer and set the retransmission credit=min((N_M), future_buffer) for the next OP window.

When the server receives a request to retransmit a packet, first it determines whether or not the total number M of retransmission requests is less than or equal to the amount of over-provisioned bandwidth, N, i.e., is M≦N. If M≦N the requested packet is retransmitted and the number of retransmission packet requests M is increased by 1. If M>N and there is retransmission credit, i.e., retransmission credit>0, the packet is sent out and the retransmission credit is decreased by 1. Otherwise the retransmission is denied.

If there is retransmission credit available, then the server can subsequently decrease the sending rate below the encoding rate and the unused media bandwidth can be used to retransmit lost packets. If the amount of retransmission credit used, X, is less than the total retransmission credit, RC, which means there is unused retransmission credit available in the current OP window, the server can use the unused retransmission credit to transmit media packets to create more retransmission credit for the next OP window or just discard the unused retransmission credit depending the specific application.

Rate Control

Rate control is different depending on the environment. For example, rate control in a public domain Internet is different from rate control in a private domain network. Within public domain Internet rate control, rate control in a constant bit (digital) rate environment is different than rate control in a variable bit rate environment. In a constant bit rate environment, information is provided at a constant rate that is the average rate that can be provided by the system. Such rate control is source friendly and TCP friendly. That is, the source can send at a constant rate.

While most of the current Internet traffic runs atop the TCP transport layer protocol, the advent of other traffic types such as multimedia has necessitated non-TCP based transport layer algorithms especially for the problem of congestion control. At the same time, in order to remain fair to the existing majority of TCP flows, it is required for these new algorithms to still exhibit “TCP friendliness”. In other words, if a non-TCP congestion control algorithm is used by a connection, it has to be ensured that the long-term average rate enjoyed by the connection is the same as what a TCP flow would have enjoyed under the same settings. Several such algorithms have been proposed for constant bit rate (“CBR”) traffic that provide non-fluctuating (on shorter time scales) rate while at the same time remaining TCP friendly. Examples of such algorithms include binomial congestion control (BCC), TFRC (TCP friendly rate control), and the like. Such algorithms estimate the “TCP friendly” rate by appropriately monitoring the loss rate (p) and round-trip time (rtt) that are the key factors that impact a TCP connection's rate. Techniques described herein attempt to achieve TCP friendly rate control for CBR traffic.

The techniques according to aspects of the present invention also include a TCP friendly rate control for variable bit rate (“VBR”) traffic called TCP variable rate control (“TVRC”) that is novel and unique. Essentially, TVRC like CBR friendly rate control algorithms calculates the TCP friendly rate from estimates of the loss rate and round-trip time. However, if the connection's application rate happens to be lower than the available TCP friendly rate, TVRC maintains a “credit” for the connection that accounts for the amount of bandwidth yielded by the connection. At a later point, if the application's output rate happens to be larger than the TCP friendly rate, TVRC allows the connections output rate to go beyond the TCP friendly rate as long as the available credit is larger than the excess (and decreases the credit accordingly). Once the accumulated credit is used up, TVRC does not allow the connection's rate to go beyond that of the TCP friendly rate. TVRC connections below the available TCP friendly rate (lagging connections) periodically send packets at a larger rate (either using dummy packets or real data packets that are held back for the purpose) to track the true loss rate p. Losses experienced during such probe periods are used by TVRC connections that are enjoying larger than TCP friendly rates (leading connections) to keep track of the additional service they are receiving. TVRC connections use a TCP subservient congestion control mechanism when they are leading connections.

The above mechanism allows for providing TCP-friendly rate while at the same time providing the best possible rate control mechanism for VBR traffic.

Another aspect of the present invention is bandwidth aware congestion control for reliable point-to-point information delivery over networks with quality of service (QoS) provisioning. When video is delivered in a point-to-point manner (unicast) over an IP network using TCP/IP protocol stack, a significant amount of over-provisioning is required to account for TCP's inefficient rate control.

TCP's LIMD (linear increase multiplicative decrease) algorithm with increase and decrease factors of 1 and 0.5, respectively, is suitable for the best-effort (and larger) Internet environment. However, in any environment where connections or streams are provided with a certain level of quality of service, the LIMD algorithm is no longer acceptable. For example, in a cable IP environment where the cable service provider streams only as many flows (movie streams) as allowed by the capacity of the available pipe, the LIMD algorithm no longer is optimal. Because of these limitations, typical over-provisioning percentages are between 10-50% of the minimum required bandwidth to support the data rate of the flows. For example, if there are 10 flows, each being streamed at 3 Mbps, the amount of raw bandwidth required when using TCP to insure lossless and timely service such that frame display deadlines are not violated can be up to 45 Mbps, although the minimum required bandwidth is only 30 Mbps.

The present system provides a congestion control algorithm that operates in the above environment and that reduces the amount of over-provisioning required and uses the following algorithm.

Instead of starting from a congestion window of 1, as in TCP, the congestion control technique provided according to the present invention starts from a congestion window of f_xx(C_ideal/2), where C_ideal is the ideal congestion window computed as the bandwidth-delay product R * rtt, where rtt is the roundtrip time on the pipe, and R is the data rate of the flow. This reduces the time for the congestion control algorithm to reach the ideal operating rate of R.

For an increase in congestion, the congestion control algorithm of the present invention uses an increase constant of x, which can be the same as in TCP (1).

For a decrease in congestion, the congestion control algorithm of the present invention uses a bandwidth aware decrease mechanism, as opposed to the blind 0.5 decrease used by TCP. Specifically, when a flow experiences a loss, and its current congestion window is C_current, the flow decreases its congestion window by:

• • f_yy(Max(0, C_current-C_ideal))

Essentially, a flow decreases its congestion window only if the current window size is greater than the ideal window size. If a decision to decrease is made, the amount by which the congestion window is decreased is a function of how much the congestion window is larger than the ideal window size.

The reasoning behind the above algorithms is as follows: fixing the congestion window at a constant value (say ideal) is undesirable because of its consequences (high multiplex frequency—related loss rate). Hence, some kind of adaptation as in TCP is desirable. However, when adaptation is performed, it should take into account the available bandwidth. Decreasing the instantaneous rate (C_current) by a function of the amount it is overshooting the ideal rate results in heuristically trying to make the average rate of the flow equal to the ideal rate R.

Quality of Service

Another technique that can be used to optimize signal transmission is to optimize according to the quality of service (QOS) required or requested at the receiver/destination/client. Such optimization can take into account actual user requirements, human perception minimum requirement or application specific requirements. Scaling can also be provided based on the size of the network or the number of users on the network. The quality of service requirement seeks to trade off or balance quality, complexity, delay, and data rate. In other words, the QOS techniques of the present invention seek to minimize delay and maximize throughput. That is, to maximize quality within constraints.

An expert system may be provided to coordinate at least four inputs for quality of service. For example, input for quality of service requirements can be at four different “levels” of the communication between the sender and the receiver: the network, the source, the client application or device, and the user. Such input can also be provided via real time feedback or on a per session basis, on a market (customer) basis, or on a market (domain) basis.

Quality of Service primitives (i.e., communication quality factors that can be adjusted according to sender, receiver, client application and user capabilities and requirements) can include, for example, video quality; spatial resolution; temporal resolution; display size, quality and resolution; audio quality; bandwidth; spatial realism; voice control and feedback; start up delay tolerance; midstream latency; or the like. The QOS primitives can be translated into network or system parameters that can actually be implemented by various components of the communication system. Such parameters include video bit rate, video bit error rate profile, video packet loss profile, audio bit rate, audio bit error rate profile, audio packet loss profile, variable/constant/adaptive bit rates, global delay jitter profile, differential jitter profile, or the like.

The QOS primitives can be assessed and translated according to an expert system which can provide input to other aspects, techniques or components of the present invention. The QOS expert system and other aspects of providing adaptation of source, network, client application and user requirements according to quality of service requirements and active feedback are described in U.S. patent application No. 10/254,685, titled, “System and Method of Quality of Service Feedback between Client and Server Devices,” filed on Sep. 26, 2002, which is hereby incorporated by reference for all purposes as if fully set forth herein.

As illustrated in FIG. 10, the QoS expert system may provide QoS signaling to the application layer, the dynamic priority calculation, the packet replication, packet interleaving, loss recovery, buffer manager, and rate control. For example, the application layer may receive QoS information that adjusts the error correction techniques or the start up delay; the dynamic priority calculation may receive information that adjusts the display rate, the start-up delay, or the E2E delay. The packet replicator may include QoS information about the network loss rate. The loss recovery may be affected by QoS information such as the display rate and quality. The rate control may be adjusted according to QoS information about the quality requested by the user and the last mile access medium.

Dynamic Prioritization

A process for dynamic prioritization 1109 according to the present invention will be described with reference to FIG. 11. Initially, the prioritization set by the present system is determined based on the prioritization applied to the signal when the signal is first encoded. In step 1120, the application that sends the data and the data types being sent are determined. In step 1130, several scenarios are determined that involve the application and data types. For example, scenarios that define the data rates seen and used by a human, as well as scenarios that determine the number of channels a cable operator can provide within a link with a certain bandwidth links, are defined.

In step 1140, the properties of the signal and network that may be adjusted are varied over a range and human perception is simulated and expressed as a perception performance measure. In step 1150, the optimal values are selected based on the best ratio of “goodput” to throughput. In step 1160, the present system is applied with the adjustable properties set to optimize their values in view of the goodput/throughput ratio. In other words, the present system acts as a broker between the application and the network.

The dynamic prioritization is performed taking into account various attributes of the data and the signal. For example, priority is computed and recomputed based on (1) dependencies between information segments; (2) deadlines for reaching the receiver; (3) client destination/receiver capabilities; (4) connection history between the source and the receiver; and (5) rate mismatches between the source, network and receiver.

Dependencies arise in heterogeneous priority systems in which lower priority packets often depend on higher priority packets such that, if a higher priority packet is dropped, and cannot be recovered, there is no need to transmit the dependent lower priority packet.

Deadlines are the time t_D at which a packet must be received at the destination. If the information packet is not received by the deadline, it may be useless to the receiver. If the packet is transferred at time t_c and the transfer time between the source and the destination is t_t, then the expected arrival time of the information at the destination/receiver is t_c+t_t. If the deadline time t_D is greater than current t_c plus the transfer time t_t (t_D>t_c+t_t), then the packet might as well be dropped since it will arrive at the destination too late to be useful to the destination/receiver. An exception would be if a dependent packet that later will be transmitted can reach the receiver in time in this cast the current packet may still be transmitted even if it will be received after its deadline so that the later dependent packet can be correctly decoded.

Client/destination capabilities include whether the destination/receiver has a strong post-processing capability, such as the ability to perform error concealment. The dynamic prioritization will also take into account if the destination/receiver will automatically drop information if the receive rate is less than the transfer rate.

Connection history accounts for the rate provided by the network and attempts to send information of a quality that will balance destination requirements against expected network bandwidth. The expected network bandwidth may be determined in view of past bandwidth provided on the network, and the system may attempt to stay within an average bandwidth or lowest expected bandwidth. Monitoring and adaptation based on connection history allows the system to provide consistent quality of service to the user.

When there are rate mismatches, the dynamic prioritization takes into account the attributes of individual packets to adjust for the rate mismatches. That is, the dynamic prioritization will look at frames having equal priorities and assess whether each of those frames is likely to reach the destination by the time it is needed by the destination/receiver. The dynamic prioritization will adjust the queue of sending order of the packets based on whether they will be received at the destination/receiver.

Moreover, the user can provide information that is taken into account by the present system so that retransmission or error suppression can be applied to balance the network attributes with the capabilities of the sender and receiver systems and the user quality of service requirements, which can be provided as part of the receiver feedback to the sender.

For example, in the context of MPEG video data, frames can be encoded in three types: intra-frames (I-frames), forward predicted frames (P-frames), and bi-directional predicted frames (B-frames). I-frames are a single image, with no reference to any past or future frames and may be called an anchor frame. A P-frame is encoded relative to the past reference frame such as a past I-frame or past P-frame. A B-frame is encoded relative to the past reference frame, the future reference frame, or both frames. Typically, I-frames require more units, e.g., bits, for transfer than P- or B-frames because, by their nature, I-frames contain more information.

Frames are divided into macroblocks, a unit typically used in motion-compensated compression, which include blocks that contain data such as luminance and chrominance blocks.

Video pictures in MPEG format may be expressed as a “group of pictures” or GOP. A typical GOP includes an I-frame, and related B-frames and P-frames. The order of the frames in a GOP is in the order of display of the frames. However, the corresponding bit stream is typically ordered based on related frames, with the I-frame first. For example, typical GOPs might be:

The present system adapts to different levels of granularity. For example, in the context of MPEG, the present system may be applied at the frame level, the macroblock level, or the block level.

If, for example, the frame I, is lost, there is no anchor frame containing the necessary information for proper presentation of the remaining frames in the GOP. Depending on the application and presentation of the information, the present system may request retransmission of the I-frame, if the resulting latency is acceptable in view of the application, or the present system may delete the entire GOP, if the resulting choppy presentation is acceptable.

If, for example, a P-frame is lost, the related B-frames are not transmitted.

A dynamic priority calculation receives information from multiple sources, including the application client. Information from the application includes quality of service requirements and information dependencies. Other information on the application client side includes other user parameters besides quality of service requirements, post-processing requirements, application sending rate and error concealment capability at the client.

The dynamic priority calculation also receives information about the data signal, including a signature profile that gives time synchronization information (codes) about the signal to be received, including when data packets are to be expected. Thus, the signature profile assists the client in detecting packet loss and loss profiling and recovery. Also, the dynamic priority calculation can also take into consideration the quality of service requirements provided by the receiver system or by the user at the receiver system.

The dynamic priority calculation also takes into account information about the network and transmission medium, including the bandwidth, transmission rate and time for retransmission of information. Also, the dynamic priority calculation must take into account buffer management and rate control, including differences between the application sending rate, overflow, and congestion management.

As discussed in an example above, P-frame and B-frame information may be dropped if an I-frame is not received. Thus, information in the buffer may be deleted, freeing buffer space, so the actual dropping mechanism may provide drop information to the buffer management. Buffer occupancy information may be useful and taken into account in the dynamic prioritization calculation.

While examples herein relate to the transfer of video data over a network, the principles of the present invention are also applicable to any digital signal, including video, audio and speech, in a packet switched environment in any of a plurality of syntaxes such as MPEG, cable, internet protocols, etc. In fact, the systems of the present invention may be applicable to any transport scheme, including MPEG 2 and MPEG 4.

The system and method of the present invention may be used in the application layer or transport layer of the five-layer model. The system and method of the present invention is highly adaptive to signal and network requirements and can be adapted accordingly. Underlying the system and method of the present invention is the concept that digital information should permit retransmission in some circumstances and avoid retransmission in other circumstances. For example, retransmission can be avoided when error concealment can fill a hole created in video frame by a lost packet. Also, for some signals that will be presented for a human user, such as video or audio, it is not necessary to retransmit a frame if the absence of such frame will not be perceived by the human user. Similarly, the loss of certain data may not affect the performance of some applications, and thus retransmission may not be necessary. However, the loss of certain data may affect the performance of other time sensitive, not fully reliable applications and retransmission may be necessary.

Potential applications of the present inventions range from pointcasts, which send multimedia data to a single destination, such as on-line video rental, video telecasting, and video on demand (VoD) to multicasts, which send multimedia data to a plurality of devices, such as interactive television (ITV), and video teleconferences, or multiple unicasts.

While the system is described herein with exemplary reference to communication of data having heterogeneous priority between a source and a destination via a network, the techniques of the present system are also applicable in other environments or sub-environments.

In addition, the principles of the present system are applicable not only between client and source, but also between destination and intermediate routers, between intermediate routers, and between intermediate routers and the source. For example, without limitation, the techniques described herein, such as “fast” loss detection, fast caching, shared over-provisioned bandwidth, buffer management, flow control, rate control, and dynamic prioritization can be applied between routers.

The techniques, according to the present invention, identifies which attributes of the signal, the network and the presentation are necessary and which may be lost without significant impact on the quality of service required by a particular user.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Claims

1. A method for sharing over-provisioned bandwidth, the method comprising

establishing a plurality of network paths between a single source and a plurality of destinations, the plurality of network paths including at least one shared network link;

determining an individual over-provisioned bandwidth needed for each of said plurality of network paths; and

determining a shared over-provisioned bandwidth for the at least one shared network link.

2. The method of claim 1, wherein determining the individual over-provisioned bandwidth comprises:

setting the individual over-provisioned bandwidth to the maximum number of retransmission requests received from a destination in any period of time T.

3. The method of claim 1, wherein determining the shared over-provisioned bandwidth comprises:

setting the shared over-provisioned bandwidth equal to the maximum of the individual over-provisioned bandwidths.

4. The method of claim 1, further comprising:

monitoring retransmission requests from each of said plurality of destinations;

updating the individual over-provisioned bandwidths based on said monitoring; and

updating the shared over-provisioned bandwidth, said updating occurring periodically during a transmission stream.

5. The method of claim 1, wherein the individual over-provisioned bandwidths are based on traffic trace history.

6. A method of fast caching packets transmitted from a source to a destination, comprising:

requesting the current status of a destination buffer;

calculating a future status of the destination buffer;

determining if any reversed bandwidth is unused; and

increasing the rate at which packets are transmitted to the destination if there is unused bandwidth and the future status indicates that the destination buffer is not full.

7. The method of claim 6, wherein that rate at which packets are transmitted to the destination is increased such that the number of additional packets transmitted is the lessor of the unused bandwidth and the available buffer space.

8. The method of claim 6, wherein calculating the future status of the destination buffer comprises:

receiving the current status of the destination buffer tc seconds after the beginning of an op window; and

setting the future buffer status equal to current buffer status—((T−tc+RTT)*(sending rate—encoding rate)).

9. The method of claim 7, further comprising:

setting a retransmission credit equal to the number of additional packets transmitted.

10. A method of transmitting data between a source and at least one destination, comprising:

transmitting the data as a series of packets to the at least one destination over a communications medium;

determining if one or more of the transmitted packets needs to be retransmitted;

requesting retransmission of a packet if it is determined that retransmission is required;

determining if there is available bandwidth to retransmit the request packet;

transmitting the request packet if there is available bandwidth;

determining if there is a retransmission credit available if it is determined that there is not any available bandwidth;

transmitting the request packet if there is a retransmission credit available; and

otherwise denying retransmission of the requested packet.

11. The method of claim 10, where the retransmission credit is generated by fast caching packets.

12. The method of claim 10, wherein determining if one or more of the transmitted packets needs to be retransmitted comprises:

receiving information regarding the packets to be received;

waiting a specific time period for receipt of an expected packet; and

sending a retransmission request if the expected packet is not received within the specified time period.