A method for controlling the throughput of a data transmitter as a function of the bandwidth of a data packet transmission link

BACKGROUND OF THE INVENTION

Field of the invention

0001The present invention generally relates to a method for controlling the throughput of a data transmitter as a function of the bandwidth of a data packet transmission link.

0002Nowadays telecommunication networks use the Internet protocol family more and more frequently. Transmission of a signal (audio, video, or simple data) are transmitted from one point to another in data packets that do not always follow a same path between these two points because there is no reserved circuit for a given signal. Such a network comprises routers that choose a path for each packet whenever there are several possible paths, according to routing tables. The configuration of a network may vary for several reasons such as an interruption or congestion on a link. Routers automatically adapt their respective routing tables to the configuration of the network, in order to maintain a predefined quality of service, in particular to maintain a nominal bandwidth, as often as possible.

0003The bandwidth on a given data packet transmission link is not actually constant. It is always fluctuating. There are short term fluctuations due to the variations of the data load, and long term variations mainly due to transmission equipment failures. In order to prevent data packet losses when the bandwidth is decreasing, a data transmitter should adapt the bit rate of the transmission according to the current bandwidth. Thus it is desirable to measure the current bandwidth of this link and control the throughput of this data transmitter as a function of the current bandwidth of the data packet transmission link.

Description of the prior art

0004Some methods for measuring the bandwidth are known. They are called: ABget, Pathchirp, Path load, TOPP. They are well adapted to punctually measure the bandwidth of a data transmission link, i. e. at a given instant. However they are not well suited for continuously measuring a bandwidth because they use too many network resources. These known methods essentially consist in injecting test packets, at an input point of the network, receiving these test packets at an output point, and then calculating the bandwidth between these two points. A time stamp is inserted in each test packet at the input point. This time stamp indicates the departure time of the packet. It is read when the packet arrives at the output point. The departure time and the arrival time of each packet are inserted in an acknowledgement message that is sent back to the input point. When the acknowledgement message arrives at the input point, the departure time is subtracted from the arrival time, in order to determine the duration of the transit through the network. A bandwidth value is computed based on transit times of a plurality of test packets. For instance the document <patcit id="pcit0001" dnum="US6498783A"><text>US 6.498.783</text></patcit> describes such a method.

0005A 3GPP standard, TR 25.902, proposes other methods for detecting a bandwidth reduction caused by a transmission equipment failure: <ul id="ul0001" list-style="dash" compact="compact"><li>either detecting packet losses by checking a sequence number inserted into each data packet,</li><li>or detecting an increase of the transit time through the network, but this method converges very slowly.</li></ul>

0006These methods are well suited for synchronous time division networks (that set up circuits) and for asynchronous time division networks (that set up virtual circuits), but they are not well suited for networks that use the Internet protocol family. Thus, there is a need to provide a method better suited for measuring the bandwidth of a data packet transmission link and controlling the throughput of a data transmitter as a function of the measured bandwidth, in networks that use the Internet protocol family.

SUMMARY OF THE INVENTION

0007A first object of the invention is a method for controlling the throughput of a data transmitter as a function of the bandwidth of a data packet transmission link, characterized in that it comprises the steps of: <ul id="ul0002" list-style="dash" compact="compact"><li>transmitting a stream of data packets to a receiver coupled at a far end of the link,</li><li>determining a continuous series of data packets in the stream of data packets;</li><li>measuring the data amount sent by the transmitter while transmitting the series of data packets,</li><li>measuring the data amount received by the receiver, while receiving substantially the same series of data packets,</li><li>sending to the data transmitter the measure of the received data amount,</li><li>comparing the measure of the received data amount and the measure of the sent data amount,</li><li>then computing a data amount to be sent by the transmitter per unit of time so that the sent data amount will be adapted to the current bandwidth of the data transmission link.</li></ul>

0008This method enables a continuous control of the transmitter throughput, as a function of the current link bandwidth, without consuming a lot of network resources, because the measurement of the link bandwidth is made by using a part of the regular data stream to constitute test packets. In order to determine a peculiar series of packets, i. e. to identify them at the reception side, a very little overhead is needed. In order to periodically send, to the data transmitter, the measure of the received data amount, another very little overhead is needed.

0009In a peculiar implementation of the method according to the present invention, <ul id="ul0003" list-style="dash" compact="compact"><li>for measuring the data amount sent by the transmitter while transmitting a series of data packets, it comprises the step of determining this series by determining a measurement time interval with a local clock in the transmitter;</li><li>for measuring the data amount received by a data receiver, while receiving substantially the same series of data packets, it comprises the step of determining this series by determining a measurement time interval with a local clock in the receiver, and periodically re-synchronizing this local clock with the local clock of the data transmitter by sending a marker from the transmitter to the receiver.</li></ul>

0010In another peculiar implementation of the method according to the present invention, <ul id="ul0004" list-style="dash" compact="compact"><li>for measuring the data amount sent by the transmitter while transmitting a series of data packets, it comprises the step of determining this series by determining a measurement time interval with a local clock in the transmitter, and sending, to the receiver, a first marker and a second marker respectively at the start and at the end of the series of data packets;</li><li>for measuring the data amount received by a data receiver, while receiving substantially the same series of data packets, it comprises the step of determining this series by receiving, from the transmitter, a first marker and a second marker respectively indicating the start and the end of the series of data packets to be used for measuring the data amount received by the data receiver.</li></ul>

0011A second object of the invention is a data receiver for controlling the throughput of a data transmitter as a function of the bandwidth of a data packet transmission link, the two ends of which are respectively coupled to this receiver and to this transmitter, characterized in that it comprises: <ul id="ul0005" list-style="dash" compact="compact"><li>means for determining a continuous series of data packets in a stream of received data packets;</li><li>means for measuring the data amount received by the data receiver, while receiving this series of data packets,</li><li>means for sending to the data transmitter the measure of the received data amount.</li></ul>

0012A third object of the invention is a data transmitter the throughput of which is controlled as a function of the bandwidth of a data packet transmission link coupled to this transmitter, characterized in that it comprises: <ul id="ul0006" list-style="dash" compact="compact"><li>means for sending a stream of data packets to a data receiver coupled to a far end of the link,</li><li>means for determining a continuous series of data packets in the stream of transmitted data packets,</li><li>means for measuring the data amount transmitted by the data transmitter, while transmitting this series of data packets,</li><li>means for receiving the measure of the received data amount measured by the data receiver while receiving the series of data packets determined by the transmitter.</li></ul>

0013Other features and advantages of the present invention will become more apparent from the following detailed description of embodiments of the present invention, when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

0014In order to illustrate in detail features and advantages of embodiments of the present invention, the following description will be with reference to the accompanying drawings. If possible, like or similar reference numerals designate the same or similar components throughout the figures thereof and description, in which: <ul id="ul0007" list-style="dash" compact="compact"><li><figref idref="f0001">Figure 1</figref> illustrates a first variant of the method according to the invention.</li><li><figref idref="f0002">Figure 2</figref> illustrates a second variant of the method according to the invention.</li><li><figref idref="f0003">Figure 3</figref> represents a flow chart of the operations made by a first embodiment of the data receiver according to the invention, applying the first variant of the method according to the invention.</li><li><figref idref="f0004">Figure 4</figref> represents a flow chart of the operations made by a first embodiment of the data transmitter according to the invention, applying the first variant of the method according to the invention.</li><li><figref idref="f0005">Figure 5</figref> represents a flow chart of the operations made by a second embodiment of the data receiver according to the invention, applying the second variant of the method according to the invention.</li><li><figref idref="f0006">Figure 6</figref> represents a flow chart of the operations made by a second embodiment of the data transmitter according to the invention, applying the second variant of the method according to the invention.</li></ul>

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

0015In the following description, we will alternately use the wording "bandwidth" as well as the wording "amount of data" because the bandwidth of a data transmission link can be assessed by measuring an amount of data per time unit.

0016Generally data packets that are transmitted through a network that uses the Internet protocol family are assigned respective priority levels, indicated by six bit fields called differentiated Service Code Points, inserted into the packet headers. The routers take the priority level of each packet into account for choosing the packets to be sent first, and for choosing packets to be discarded when congestion occurs. So the method according to the invention is preferably implemented independently for each priority level. In the following description, we will consider data packets that all belong to a same priority level.

0017<figref idref="f0001"><b>Figure 1</b></figref> illustrates a first variant of the method according to the invention. The upper graph represents the transmitted data throughput, of an example of data transmitter, and the lower graph represents the received data throughput at the other end of a data packet transmission link. In this example the transmitted throughput is constant. The received throughput is fluctuating because of the fluctuations of the bandwidth of the link. In particular, the bandwidth is fluctuating because the network data load is fluctuating. The bandwidth is periodically measured in the data transmitter by counting the amount of data sent during a measurement time interval having a fixed duration T (for instance T = 1 second). The measurement is reiterated with a period equal to T, so that the intervals are contiguous. The measurement time intervals for the sent data are determined by a local clock in the transmitter. The sent data amount is successively measured during the time intervals t1-t2, t2-t3, t100-t101, ....

0018The data transmitter periodically sends a packet containing a marker, with a fixed period N x T (for instance N = 100). It sends a first marker m1 at the instant t1, then a second marker m2 at the instant t100, etc.

0019The bandwidth is also measured in the data receiver by measuring the amount of data received during a time interval having a fixed duration T. The receiver regularly receives a packet containing a marker with an interval that is more or less than N x T, according to the fluctuations of the throughput. It receives the first marker m1 at the instant t1' (some time after t1 because of the transit delay), then the second marker m2 at the instant t100' (that does not generally coincide with t100 because the data throughput is fluctuating), etc.

0020The received data amount is successively measured during each time interval t1'-t2', t2'-t3', ... , determined by a local clock, in the receiver. The first received marker m1 triggers the first measurement time interval t1'-t2'. Then the local clock supplies a clock signal with a period T in order to define N successive time intervals for making N measurements in N contiguous time intervals. This clock is re-synchronized by the received markers. This clock stops the first measurement interval at instant t2' after a duration T, and immediately starts a new measurement interval t2'-t3'. The first received data amount measurement is made with almost the same data as the sent data amount measurement made in transmitter (except at the end of the interval t1'-t2'where there may be a little more or a little less data). The second measurement (made during the interval t2'-t3') is made with almost the same data as the measurement made in transmitter during the interval t2-t3 (except at the beginning and at the end of the interval where there may be a little more or a little less data).

0021The coincidence between the data used for the measurement in the transmitter and the data used for the measurement in the receiver is degrading for the successive time intervals.

0022The 100^th interval is stopped either by the 100^th clock signal or by the reception of the second marker m2 if this marker arrives before the 100^th clock signal. In any case, the 101^st interval is started when the marker m2 is received. So the marker m2 is used to resynchronize the data used for the measurement in the transmitter and the data used for the measurement in the receiver.

0023The measure of the data amount received in the receiver is sent back to the data transmitter via a reliable link, with a sequence number identifying the measurement time interval, this sequence number being reset each time a marker is received. In the data transmitter, the sent data amount and the received data amount, for a same time interval, are compared. A data amount to be sent during the next time interval is computed so that the sent data amount will be adapted to the current bandwidth of the data transmission link. Of course, if the current received data amount corresponds to the nominal bandwidth, the data amount to be sent during the next time interval will preferably be chosen equal to the nominal bandwidth. An implementation of the computing is described below with reference to <figref idref="f0004">figure 4</figref>.

0024The re-synchronization by the markers m1, m2, ... improves the accuracy of the control over the throughput of the data transmitter, because the measurement comparison is all the more accurate as the data are more identical. For instance, thanks to the reception of the marker m2, the data received during the interval t100'-t101' are almost the same data as the data sent by the transmitter during the interval t100-t101 (except at the end of the interval where there may be a little more or a little less data).

0025For controlling the throughput of the data transmitter as a function of the bandwidth of the data packet transmission link: <ul id="ul0008" list-style="dash" compact="compact"><li>the received data amount is measured in the receiver,</li><li>its measure is sent back to the data transmitter via a reliable link, with a sequence number identifying the measurement time interval, this number being reset each time a marker is received;</li><li>in the data transmitter, the sent data amount and the received data amount, for a same time interval, are compared;</li><li>then a data amount to be sent during the next time interval is computed so that the sent data amount will be adapted to the current bandwidth of the data transmission link.</li></ul>

0026<figref idref="f0002"><b>Figure 2</b></figref> illustrates a second variant of the method according to the invention. The upper graph represents the transmitted data throughput, and the lower graph represents the received data throughput. In this example, the transmitted throughput is constant. The received throughput is fluctuating. The bandwidth is periodically measured in the data transmitter by counting the amount of data sent during a time interval having a fixed duration T (for instance T = 1 second), and with a period also equal to T, so that the intervals are contiguous. The measurement time intervals for the sent data are determined by a local clock in the transmitter. The sent data amount is successively measured during the time intervals t1-t2, t2-t3, ... , t100-t101, .... The data transmitter periodically sends a packet containing a marker with a fixed period T. It sends a first marker M1 at the instant t1, then a second marker M2 at the instant t2, ... , a 100^th marker M100 at the instant t100, etc.

0027The bandwidth is also measured in the data receiver by counting the amount of data received during a time interval having a duration that is roughly equal to T. In contrast with the first variant, the measurement time intervals are not determined by a local clock in the receiver; they are all triggered by the receptions of markers M1, M2, M3,..., M100, .... Thus the data used for measuring the received data amount are exactly the same as the data used for measuring the sent data amount, because their delineated by two successive markers.

0028The receiver regularly receives a packet containing a marker, two successive markers being received with an interval that is more or less than T, according to the fluctuations of the throughput. The reception of each marker stops the current measurement interval and immediately starts a new measurement interval. The receiver receives the first marker M1 at the instant t1" (some time after t1 because of the transit delay), then the second marker M2 at the instant t2" (that does not generally coincide with t2 because the data throughput is fluctuating), ... then the 100^th marker M100 at the instant t100" (that does not generally coincide with t100 because the data throughput is fluctuating), etc. The received data amount is successively measured during the time intervals t1 "-t2", t2"-t3", ... , t100"-t101".

0029Thanks to the receptions of the markers M1 and M2, the first measurement in the receiver is made with exactly the same data as the measurement made in the transmitter (except if there is a packet loss between the markers M1 and M2). Thanks to the receptions of the markers M2 and M3, the second measurement in the receiver is made with exactly the same data as the measurement made in the transmitter (except if there is a packet loss between the markers M2 and M3)..... Thanks to the receptions of the markers M100 and M101, the 100^th measurement in the receiver is made with exactly the same data as the measurement made in the transmitter (except if there is a packet loss between the markers M100 and M101). Thus the markers resynchronize the data used for the measurement in the transmitter and the data used for the measurement in the receiver, so the measurement comparison is more accurate as the data are more identical.

0030For controlling the throughput of the data transmitter as a function of the bandwidth of the data packet transmission link: <ul id="ul0009" list-style="dash" compact="compact"><li>the received data amount is measured in the receiver,</li><li>its measure is sent back to the data transmitter via a reliable link, with a sequence number identifying the measurement time interval, this number being reset each time a marker is received;</li><li>in the data transmitter, the sent data amount and the received data amount, for a same time interval, are compared;</li><li>then a data amount to be sent during the next time interval is computed so that the sent data amount will be adapted to the current bandwidth of the data transmission link.</li></ul>

0031Of course, if the current received data amount corresponds to the nominal bandwidth, the data amount to be sent during the next time interval will be chosen equal to the nominal bandwidth. An implementation of the computing is described below with reference to <figref idref="f0006">figure 6</figref>.

0032In a peculiar implementation of the method according to the invention, the measured bandwidth/amount of received data may be determined by calculating the average of three consecutive measures, in three contiguous time intervals, for smoothing the fluctuations of the bandwidth.

0033<figref idref="f0003"><b>Figure 3</b></figref> represents a flow chart of the operations made by a first embodiment of the data receiver according to the invention, applying the first variant of the method according to the invention. During time intervals of constant duration T1, determined by a local clock, the transmitter measures the amount of data sent. During time intervals of constant durations T1, determined by another local clock, the receiver measures the amount of data received. Once every 100 intervals, the transmitter sends a marker to resynchronize the receiver and the transmitter, so that they substantially use a same series of data packets for measuring the sent data amount in the transmitter and the received data amount respectively.

0034Every measurement interval in the receiver has a sequential number NSeq. The receiver will re-initialize this sequential number NSeq when it receives a marker with a sequence number NseqR from the transmitter, and when it reaches a predetermined maximal value NSeqM (for instance NSeq = 100 in order to re-initialize after every 100th time interval). The transmitter provides this maximal value NSeqM to the receiver, along with a marker, in a synchronization message. The receiver will use this maximal value NSeqM as a base for the sequential numbering of its own measurement time intervals. The sequential number NSeq will enable identifying measured data in the transmitter and in the receiver for every measurement time interval. The receiver will send a notification to the transmitter, via a reliable link (like TCP or SCTP), at the end of every measurement interval. This notification will contain the amount MRcvBW of data received during the interval, and the corresponding sequence number NSeq.

0035This first embodiment of the receiver makes the following steps: <ul id="ul0010" list-style="none" compact="compact"><li><b>Step 301</b>: Initialization: <ul id="ul0011" list-style="dash" compact="compact"><li>Get provisioned parameters (T1).</li><li>Receive a marker (containing a received sequence number NseqR).</li><li>Start timer T1.</li><li>Initialize the value NSeq of a local sequence number counter with NSeqR.</li><li>Reset the value MRcvBW of the received data amount/bandwidth measured by the receiver.</li></ul></li><li><b>Step 302:</b> Wait to receive (pending waiting the received data amount/bandwidth will be measured by the receiver into MRcvBW): <ul id="ul0012" list-style="dash" compact="compact"><li>either a T1 timer signal,</li><li>or a marker from the transmitter.</li></ul></li><li><b>Step 303:</b><ul id="ul0013" list-style="dash" compact="compact"><li>If a signal is received from the timer T1, make step 304.</li><li>If a marker is received, make the step 305.</li></ul></li><li><b>Step 304:</b> A signal has been received from the timer T1: <ul id="ul0014" list-style="dash" compact="compact"><li>Send a notification to the transmitter, containing the current value MRcvBW of the received data amount, and the current value Nseq of the sequence number, corresponding to the current measurement interval.</li><li>Increment the value of the sequence number: NSeq = NSeq + 1.</li><li>Reset the value MRcvBW of the measured received data amount/bandwidth, for next interval.</li><li>Restart timer T1.</li><li>Then return to step 302.</li></ul></li><li><b>Step 305:</b> A marker has been received (before the end of the time interval T1): <ul id="ul0015" list-style="dash" compact="compact"><li>Resynchronize the value of the sequence number Nseq with the value NseqR received along with the marker.</li><li>Reset the value MRcvBW of the measured received data amount/bandwidth, for next interval.</li><li>Reset and restart timer T1.</li><li>Then return to step 302.</li></ul></li></ul>

0036<figref idref="f0004"><b>Figure 4</b></figref> represents a flow chart of the operations made by a first embodiment of the data transmitter according to the invention, applying the first variant of the method according to the invention.

0037The transmitter will store the sent data amount in a register SND[] of a circular array, the index of the register SND[] in this array being computed by using the formula: <ul id="ul0016" list-style="none" compact="compact"><li>Index = NSeq % Ssize</li></ul> where Nseq is the current sequence number for the measurement made by the transmitter, and where % Ssize means "modulo Ssize", with SSize being the dimension of the circular array (Ssize could be 10 for a maximum delay of about 3 seconds between receiver and transmitter for the notification). If the link could induce greater delays it would be recommended to have a bigger Ssize.

0038The transmitter will compare the received data amount MRcvBW (provided by the receiver) with the corresponding sent data stored into SND array at the <ul id="ul0017" list-style="none" compact="compact"><li>Index = NSeqR % Ssize.</li></ul>

0039NSeqR being a sequence number received with MRcvBW in the same notification sent by the receiver.

0040This first embodiment of the transmitter makes the following steps: <ul id="ul0018" list-style="none"><li><b>Step 401:</b> Initialization: <ul id="ul0019" list-style="dash" compact="compact"><li>Get provisioned parameters: <ul id="ul0020" list-style="none" compact="compact"><li>-- Nominal value PrvBW of the sent data amount/bandwidth,</li><li>-- Time interval T1,</li><li>-- Provisioned increment IPrvBW that will be used in the recovery process to regain the lost bandwidth.</li><li>-- The maximal value NSeqM of the sequence number for the measurement time intervals in the transmitter, determining the period of sending markers, expressed as number of T1 intervals NSeqM = 100 in this example).</li><li>-- The size Ssize of a circular memory array for storing the measures of the amounts of transmitted data.</li><li>-- A threshold number NLowM, defining the number of measures indicating a bandwidth decrease, necessary to decide changing the state of the transmitter from NORMAL to INTERMEDIATE.</li></ul></li><li>Start timer T1.</li><li>Reset the measured sent data amount/bandwidth : MSndBW = 0.</li><li>Initialize the value CrtBW of the current sent data amount/bandwidth to the value PrvBW of the nominal sent data amount/bandwidth (It determines the maximal amount of data that the transmitter is allowed to send during a T1 interval).</li><li>Reset the sequence number NSeq of the measurement time intervals.</li><li>Set the state of the transmitter to NORMAL.</li><li>Reset the contents of all the registers of the array SND[ ] that will store the amounts of data sent during the time intervals.</li></ul></li><li><b>Step 402:</b> Wait to receive: <ul id="ul0021" list-style="dash" compact="compact"><li>either a T1 timer signal,</li><li>or a notification from the receiver.</li></ul></li><li><b>Step 403:</b> if a T1 timer signal is received, make the step 404. If a notification is received from the receiver make the step 410.</li><li><b>Step 404:</b> A T1 timer signal has been received: <ul id="ul0022" list-style="dash" compact="compact"><li>Restart timer T1 for next time interval.</li><li>Store the current value MSndBW of the measured amount of sent data, into the register SND[NSeq % Ssize].</li></ul></li><li><b>Step 405:</b> Check whether state is RECOVERY : <ul id="ul0023" list-style="dash" compact="compact"><li>If it is RECOVERY make step 406.</li><li>If it is NORMAL or INTERMEDIATE make the step 407.</li></ul></li><li><b>Step 406:</b> state is RECOVERY (i. e. the sent data amount must be increased because the actual bandwidth is increasing towards its nominal value): <ul id="ul0024" list-style="dash" compact="compact"><li>Compute a new value ClncBW for the current bandwidth/sent data amount increment, to be used for recovery process, during the current time interval. The used bandwidth is progressively incremented in order to avoid a congestion that could cause packet losses. It is computed according to the formula: <ul id="ul0025" list-style="none" compact="compact"><li>ClncBW = min ((CrtBW + IPrvBW), PrvBW) - SSndBW, where: <ul id="ul0026" list-style="none" compact="compact"><li>-- CrtBW is the current sent data amount/bandwidth;</li><li>-- IPrvBW is the provisioned increment to be used in the recovery process to regain the lost bandwidth;</li><li>-- PrvBW is the nominal bandwidth i. e. the maximal data amount that may be sent by the transmitter;</li><li>-- SSndBW is the amount of sent data amount/bandwidth for the previous interval.</li></ul></li></ul></li><li>Increase the current sent data amount/bandwidth CrtBW with the current increment ClncBW:</li><li>Send a supplement of data, the size of which is equal to this current increment ClncBW. As there is a high risk of losing these supplementary data, these supplementary data are blank data that are only used to test the link.</li><li>Increment the amount of sent data, stored in the register SND[NSeq % Ssize], with the current increment ClncBW.</li></ul></li><li><b>Step 407:</b><ul id="ul0027" list-style="dash" compact="compact"><li>Reset the value MSndBW of the measured sent data amount/bandwidth for next interval.</li><li>Increment the sequence number NSeq of the measurement intervals.</li></ul></li><li><b>Step 408:</b> Check whether the sequence number NSeq has reached its maximal value NSeqM (100 in our case): <ul id="ul0028" list-style="dash" compact="compact"><li>If it has reached its maximal value, make the step 409.</li><li>If it has not reached its maximal value, return to the step 402.</li></ul></li><li><b>Step 409:</b> The sequence number NSeq has reached is maximal value NSeqM, i. e. a series of N measurement intervals is finished: <ul id="ul0029" list-style="none" compact="compact"><li>Send a new marker to the receiver with its sequence number NSeq and return to step 402.</li></ul></li><li><b>Step 410:</b> A notification has been received from the receiver, this notification containing the value MRcvBW of the received data amount/bandwidth, and the sequence number NSeqR of the corresponding time interval: <ul id="ul0030" list-style="none" compact="compact"><li>Check whether this value, MRcvBW, is lower than the value SND[NseqR % Ssize] of the sent data amount/bandwidth stored at the index NseqR % Ssize, designating the corresponding interval where the measure was made by the receiver : <ul id="ul0031" list-style="none" compact="compact"><li>-- If it is lower, i. e. if the bandwidth is decreasing, make the step 411.</li><li>-- If it is greater, i. e. if the bandwidth is stable or increasing, make the step 414.</li></ul></li></ul></li><li><b>Step 411:</b> The bandwidth is lower than corresponding sent data amount/bandwidth: Increment the counter Nlow that counts the number of consecutive measures showing a decrease of the measured received data amount/bandwidth.</li><li><b>Step 412:</b> Check whether the counter Nlow has reached its maximal value NlowM: <ul id="ul0032" list-style="dash" compact="compact"><li>If it has reached its maximal value, make the step 413.</li><li>If it has not reached its maximal value, make the step 414.</li></ul> If MRcvBW is lower than MSndBW during NlowM consecutive measurement intervals, it will be concluded that bandwidth has really decreased. So it is necessary to reduce the data throughput (Pass into INTERMEDIATE state). Preferably, NlowM is chosen equal to 3, or greater.</li><li><b>Step 413:</b> The counter Nlow has reached its maximal value NlowM: <ul id="ul0033" list-style="dash" compact="compact"><li>Set state to INTERMEDIATE, because it is confirmed that the bandwidth has decreased.</li><li>Reduce the value CrtBW of the current sent data amount/bandwidth used for sending data, to the value MRcvBW of the received data amount/bandwidth actually measured by the receiver.</li><li>Reset the counter Nlow that counts the number of consecutive measures showing a decrease of the measured received data amount/bandwidth.</li><li>Then return to the step 402.</li></ul></li><li><b>Step 414:</b> The value MRcvBW of the received data amount/bandwidth is greater or equal than the value SND[NseqR % Ssize] of the sent data amount/bandwidth, i. e. the bandwidth is recovering or normal: Reset the counter Nlow that counts the number of consecutive measures showing a decrease of the measured received data amount/bandwidth.</li><li><b>Step 415:</b> Check whether the state is INTERMEDIATE: <ul id="ul0034" list-style="dash" compact="compact"><li>If it is INTERMEDIATE, make the step 416.</li><li>If it is NORMAL, or RECOVERY, make the step 417.</li></ul></li><li><b>Step 416:</b> The state is INTERMEDIATE whereas the bandwidth is not decreasing anymore: Set state to RECOVERY and then return to step 402.</li><li><b>Step 417:</b> The state is not INTERMEDIATE: Check whether the state is RECOVERY : <ul id="ul0035" list-style="dash" compact="compact"><li>If it is RECOVERY, make the step 418.</li><li>If it is NORMAL, return to step 402.</li></ul></li><li><b>Step 418:</b> The state is RECOVERY. It is possible to cautiously increase the amount of data to be sent: <ul id="ul0036" list-style="dash" compact="compact"><li>Increment the value CrtBW of the current sent data amount/bandwidth with the current value ClncBW of the increment.</li><li>Then reset the current value ClncBW of the increment.</li></ul></li><li><b>Step 419:</b> Check whether the current value CrtBW of the current sent data amount/bandwidth is equal to the nominal bandwidth PrvBW: <ul id="ul0037" list-style="dash" compact="compact"><li>If it is equal to the nominal bandwidth PrvBW, make the step 420.</li><li>If it is not equal to the nominal bandwidth PrvBW, return to the step 402.</li></ul></li><li><b>Step 420:</b> The current value CrtBW of the current sent data amount/bandwidth used by the transmitter is equal to the nominal bandwidth, it is time to return to the normal state: Set state to NORMAL, and then return to step 402.</li></ul>

0041<figref idref="f0005"><b>Figure 5</b></figref> represents a flow chart of the operations made by a second embodiment of the data receiver according to the invention, applying the second variant of the method according to the invention. The transmitter will send a marker for each measurement interval. The receiver will measure the value MRcvBW of the amount of received data in a measurement time interval defined by elapsed time between two consecutive received markers. So a same series of data is used for measuring a data amount in the transmitter and in the receiver (if there is no packet loss between the two markers). The receiver will send, to the transmitter, a notification containing this value MRcvBW and a sequence number Nseq corresponding to the measurement time interval, via a reliable link (like TCP or SCTP), after reception of every marker.

0042A marker may be lost during transmission. In order to deal with this case, a second timer T2 will be used: T2 is longer than T1 (T2 = 1.5 T1 for instance). After an elapsed time T2, if an expected marker has not bee received, this marker is considered as lost. The measurement of the amount of received data will be made along the full T2 interval, and then it is corrected to determine the amount corresponding to a time interval T1 only.

0043At initialization, the receiver will wait for a first marker, delivering a first value NSeqR of the sequence number. This first value of the sequence number NSeq will be incremented and used to check the validity of the sequence number values that will be contained in the following markers.

0044This second embodiment of the receiver makes the following steps: <ul id="ul0038" list-style="none" compact="compact"><li><b>Step 501:</b> Initialization: <ul id="ul0039" list-style="dash" compact="compact"><li>Get provisioned parameters (T1).</li><li>Receive a first marker (containing a value NSeqR of the sequence number).</li><li>Start a timer T1.</li><li>Initialize the current value NSeq of the local sequence number counter with NSeqR + 1.</li><li>Reset the value MRcvBW of the received data amount/bandwidth measured by the receiver.</li></ul></li><li><b>Step 502:</b> Wait to receive: <ul id="ul0040" list-style="dash" compact="compact"><li>either a T1 timer signal,</li><li>or a T2 timer signal,</li><li>or a marker from the transmitter.</li></ul></li><li><b>Step 503:</b> check whether a T1 timer signal has been received: <ul id="ul0041" list-style="dash" compact="compact"><li>If a T1 timer signal has been received make the step 504.</li><li>If a T1 timer signal has not been received make the step 505.</li></ul></li><li><b>Step 504:</b> A T1 timer signal has been received: <ul id="ul0042" list-style="dash" compact="compact"><li>Initialize the value SRcvBW of the saved measured received data amount/bandwidth with the current value MRcvBW of the measured received data amount/bandwidth (T1 timer signals indicates the end of a theoretical time interval). This value will be useful only if the expected marker never arrives. In this case, it will constitute an approximate measure of the received data amount/bandwidth instead of the accurate value that would have been measured between two successive markers. If the expected marker never arrives, the value MRcvBW of the measured received data amount/bandwidth will then continue to be updated until the timer T2 fires.</li><li>Start timer T2.</li><li>Re-start timer T1.</li><li>Return to the step 502.</li></ul></li><li><b>Step 505:</b> A T2 timer signal or a marker has been received: Check whether it is a T2 timer signal: <ul id="ul0043" list-style="dash" compact="compact"><li>If a T2 timer signal has been received, make the step 508.</li><li>If a T2 timer signal has not been received, then a marker has been received, make the step 506.</li></ul></li><li><b>Step 506:</b> A marker has been received: Check whether the value NSeqR that it contains is equal to the current value NSeq of the local counter for the sequence number counting the measurement intervals: <ul id="ul0044" list-style="dash" compact="compact"><li>If NSeqR is equal to Nseq, make the step 507.</li><li>If NSeqR is not equal to Nseq, the received marker is invalid. Discard the received marker and return to the step 502.</li></ul></li><li><b>Step 507:</b> A valid marker has been received: <ul id="ul0045" list-style="dash" compact="compact"><li>Cancel timer T1.</li><li>Cancel timer T2 (if armed)</li><li>Send a notification to the transmitter, containing the current value MRcvBW of the received amount of received data amount (that is the accurate value measured between two successive markers) and the current value NSeq of the sequence number.</li><li>Increment the value of the counter NSeq.</li><li>Reset the value MRcvBW of the measured received data amount/bandwidth, for next interval.</li><li>Start timer T1.</li><li>Return to the step 502.</li></ul></li><li><b>Step 508:</b> The timer T2 has fired because a marker has been lost in the transmission. At this instant, the current value MRcvBW measured the received data amount corresponding to the T1 + T2 time interval. Two measures of received data amount/bandwidth must be determined: a first measure corresponding to a first time interval with duration T1, and a second measure corresponding to a second time interval spanning from the end of the interval T1 to the reception of a next marker (corresponding to T2). The value SRcvBW of the received data amount determined during the time interval T1 has been stored during step 504 when the timer T1 has fired. So the receiver makes the following operations: <ul id="ul0046" list-style="dash" compact="compact"><li>Send a notification to the transmitter, containing the value SRcvBW of the received data amount determined during the time interval T1 (instead of the time interval defined by two successive markers) and the current value NSeq of the sequence number counter.</li><li>Then increment the value NSeq of the sequence number counter.</li><li>Then determine a second received data amount corresponding to the next interval from the end of interval T1 to the reception of a next marker: It is calculated by subtracting from the current value stored into MRcvBW the value stored into SRcvBW corresponding to T1 interval (this in fact correspond to the measure of the amount of received data along the T2 interval.<maths id="math0001"><math display="block"><mi mathvariant="normal">M</mi><mo>⁢</mo><mi mathvariant="normal">R</mi><mo>⁢</mo><mi mathvariant="normal">c</mi><mo>⁢</mo><mi mathvariant="normal">v</mi><mo>⁢</mo><mi mathvariant="normal">B</mi><mo>⁢</mo><mi mathvariant="normal">W</mi><mo mathvariant="normal">=</mo><mi mathvariant="normal">M</mi><mo>⁢</mo><mi mathvariant="normal">R</mi><mo>⁢</mo><mi mathvariant="normal">c</mi><mo>⁢</mo><mi mathvariant="normal">v</mi><mo>⁢</mo><mi mathvariant="normal">B</mi><mo>⁢</mo><mi mathvariant="normal">W</mi><mo mathvariant="normal">-</mo><mi mathvariant="normal">S</mi><mo>⁢</mo><mi mathvariant="normal">R</mi><mo>⁢</mo><mi mathvariant="normal">c</mi><mo>⁢</mo><mi mathvariant="normal">v</mi><mo>⁢</mo><mi mathvariant="normal">B</mi><mo>⁢</mo><mi mathvariant="normal">W</mi></math><img file="EP2506507A1_D0001.tif" /></maths></li></ul> This difference is stored into the register MRcvBW. This value is not sent to the transmitter because it only corresponds to a time interval T2.The value in the register MRcvBW continues to be updated until the reception of the next marker. Then this register will contain the measure corresponding to the interval between the end of the time interval T1 and the arrival of the next marker. So, when this next marker arrives, the next notification will be able to carry a value of the measured received data amount.</li></ul>

0045<figref idref="f0006"><b>Figure 6</b></figref> represents a flow chart of the operations made by a second embodiment of the data transmitter according to the invention, applying the second variant of the method according to the invention.

0046A circular memory array SND[] stores the values of the sent data amount/bandwidth. This array is indexed by the index: NSeq % Ssize, where % Ssize means modulo Ssize, with SSize being the dimension of the circular memory array (Ssize could be 10 for a maximum round trip delay of about 3 seconds between receiver and transmitter, for a notification).

0047This second embodiment of the transmitter makes the following steps: <ul id="ul0047" list-style="none"><li><b>Step 601:</b> Initialization: <ul id="ul0048" list-style="dash" compact="compact"><li>Get provisioned parameters: <ul id="ul0049" list-style="none" compact="compact"><li>-- Nominal value PrvBW of the sent data amount/bandwidth.</li><li>-- Time interval T1.</li><li>-- A provisioned increment IPrvBW that will be used for the recovery process, to increase the sent data amount/bandwidth up to its nominal value.</li><li>-- A threshold number NmbSR, defining the number of measures indicating a bandwidth not decreasing, necessary to decide changing the state of the transmitter from INTERMEDIATE to RECOVERY.</li></ul></li><li>Start timer T1.</li><li>Reset the value MSndBW of the sent data amount/bandwidth.</li><li>Initialize the value CrtBW of the current sent data amount/bandwidth to the value PrvBW of the nominal sent data amount/bandwidth (It determines the maximal amount of data that the transmitter is allowed to send during a T1 interval).</li><li>Reset the sequence number Nseq designating a measurement time interval, and a corresponding series of data packets, used for a measurement.</li><li>Set the state of the transmitter to NORMAL.</li><li>Reset the contents of the registers SND[] that will store the values of the measured sent data amount/bandwidth.</li></ul></li><li><b>Step 602:</b> Wait to receive: <ul id="ul0050" list-style="dash" compact="compact"><li>either a T1 timer signal,</li><li>or a notification from the receiver.</li></ul></li><li><b>Step 603:</b> Check whether a T1 timer signal is received: <ul id="ul0051" list-style="dash" compact="compact"><li>if a T1 timer signal is received make the step 604.</li><li>if a notification is received make the step 608.</li></ul></li><li><b>Step 604:</b> A T1 timer signal has been received: <ul id="ul0052" list-style="dash" compact="compact"><li>Restart timer T1 for next interval.</li><li>Save the value MSndBW of the sent data amount/bandwidth in a register of the circular memory SND[], at the index [Nseq % Ssize].</li></ul></li><li><b>Step 605:</b> Check whether the state is RECOVERY: <ul id="ul0053" list-style="dash" compact="compact"><li>If it is RECOVERY make the step 606.</li><li>If it is NORMAL or INTERMEDIATE, make the step 607.</li></ul></li><li><b>Step 606:</b> The state is RECOVERY: <ul id="ul0054" list-style="dash" compact="compact"><li>Compute a new value CIncBW of the current data amount/bandwidth increment for recovery process, according to the formula: <ul id="ul0055" list-style="none" compact="compact"><li>ClncBW = min ((CrtBW + IPrvBW), PrvBW) - SND[Nseq % Ssize], where: <ul id="ul0056" list-style="none" compact="compact"><li>-- CrtBW is the value of the current sent data amount/bandwidth,</li><li>-- IPrvBW is the provisioned increment that will be used in the recovery process to progressively increase the sent data amount/bandwidth,</li><li>-- PrvBW is the nominal sent data amount/bandwidth i. e. the maximal bandwidth that can be used by the transmitter,</li><li>-- SND[Nseq % Ssize] is the sent data amount/bandwidth for the current interval (MSndBW).</li></ul></li></ul></li><li>Increase the current sent data amount/bandwidth CrtBW with the current increment ClncBW. The sent data amount/bandwidth is progressively incremented in order to avoid a congestion that could cause packet losses.</li><li>Send a supplement of data, the size of which is equal to this current increment ClncBW. As there is a high risk of losing these supplementary data, these supplementary data are blank data that are only used to test the link.</li><li>Increment the value of the current sent data amount/bandwidth, stored in the register</li></ul> SND[Nseq % Ssize], with the current increment ClncBW.</li><li><b>Step 607:</b> The state it is NORMAL or INTERMEDIATE: <ul id="ul0057" list-style="dash" compact="compact"><li>Send a marker to the receiver with the sequence number Nseq.</li><li>Reset the value MSndBW of the sent data amount/bandwidth for next interval.</li><li>Increment the sequence number Nseq.</li><li>return to step 602.</li></ul></li><li><b>Step 608:</b> A notification has been received from the receiver, this notification containing the value MRcvBW of the received data amount/bandwidth, and the corresponding receiver sequence number NSeqR: <ul id="ul0058" list-style="none" compact="compact"><li>Check whether the received data amount/bandwidth MRcvBW is greater than the value SND[NSeqR % Ssize] of the sent data amount/bandwidth, stored at the index NSeqR % Ssize corresponding to data amount/bandwidth sent by the transmitter at the corresponding time interval: <ul id="ul0059" list-style="none" compact="compact"><li>-- If it is lower or equal, make the step 609.</li><li>-- If it is greater, discard the notification, and return to step 602.</li></ul></li></ul></li><li><b>Step 609:</b> A notification has been received from the receiver, this notification containing the value MRcvBW of the received data amount/bandwidth, and the sequence number NSeqR corresponding to the series of packets where the measure was made by the transmitter and the receiver: <ul id="ul0060" list-style="none" compact="compact"><li>Check whether the value MRcvBW is lower than the value SND[NseqR % Ssize] of the sent data amount/bandwidth at the corresponding interval: <ul id="ul0061" list-style="none" compact="compact"><li>-- If it is lower i. e. if the bandwidth is decreasing make the step 610.</li><li>-- If it is equal i. e. if the bandwidth is stable, make the step 611.</li></ul></li></ul></li><li><b>Step 610:</b><ul id="ul0062" list-style="dash" compact="compact"><li>Set state to INTERMEDIATE, because the received data amount/bandwidth is decreasing.</li><li>Reduce the value CrtBW of the sent data amount/bandwidth used for sending data, to the value MRcvBW of the received data amount/bandwidth presently measured by the receiver.</li><li>Reset the counter cNmbSR used for RECOVERY state detection, which counts the number of consecutive measures showing that the received data amount/bandwidth is equal to sent by transmitter data amount/bandwidth in INTERMEDIARY state.</li><li>Then return to the step 602.</li></ul></li><li><b>Step 611:</b> Check whether the state is INTERMEDIATE: <ul id="ul0063" list-style="dash" compact="compact"><li>If it is INTERMEDIATE, make the step 612.</li><li>If it is NORMAL, or RECOVERY, make the step 615.</li></ul></li><li><b>Step 612:</b> The state is INTERMEDIATE, increment the counter cNmbSR that counts the number of intervals where the received data amount/bandwidth is equal to sent by transmitter data amount/bandwidth, while the state is INTERMEDIATE.</li><li><b>Step 613:</b> Check whether the counter cNmbSR reaches the threshold NmbSR. <ul id="ul0064" list-style="dash" compact="compact"><li>If it reaches the threshold, make the step 614.</li><li>If it does not reach the threshold, keep the state INTERMEDIATE, return to the step 602.</li></ul></li><li><b>Step 614:</b> Set the state to RECOVERY, because the received data amount/bandwidth is stable. Then return to step 602.</li><li><b>Step 615:</b> The state is RECOVERY or NORMAL. Check whether the value MRcvBW of the received data amount/bandwidth is equal to the nominal value PrvBW of the sent data amount/bandwidth: <ul id="ul0065" list-style="dash" compact="compact"><li>If it is equal to PrvBW, the link has completely returned to normal conditions, make step 616.</li><li>If it is not equal to PrvBW, the link has not completely returned to normal conditions, return to the step 602.</li></ul></li><li><b>Step 616:</b> The link has completely returned to normal conditions, set the state to NORMAL, then return to step 602.</li></ul>