The present invention relates generally to network communications and, in particular, to a method and apparatus for bandwidth reservation. The invention is particularly suitable for implementation in a wireless Local Area Network (WLAN) system operating in accordance with the Institute of Electrical & Electronics Engineers' (IEEE) 802.11 standards.
Conventionally, the IEEE 802.11 based architecture is comprised of several components and services that interact to provide station mobility transparent to the higher layers of the network stack. The IEEE 802.11 based network defines a station as the component that connects to a wireless medium and contains the functionality of the IEEE 802.11 protocols, that being MAC (Medium Access Control), PHY (Physical Layer), and a connection to the wireless media. Typically, the IEEE 802.11 protocols are implemented in the hardware and/or software of a network interface card.
A station could be a laptop PC, handheld device, or an access point (AP). Stations may be mobile, portable, or stationary and all stations support the IEEE 802.11 station services of authentication, de-authentication, privacy, and data delivery.
The MAC layer's primary function is to provide a fair mechanism to control access of shared wireless media. However, prior to transmitting a frame, the MAC layer must gain access to the network, which it does through two different access mechanisms: a contention-based mechanism, called the distributed coordination function (DCF), and a centrally controlled access mechanism, called the point coordination function (PCF).
The PCF modes allow the implementation of a quality of service (QoS) mechanism, but it is optional and requires extra interactions in order to negotiate a QoS between the mobile terminal and the ID. The DCF mode, considered the default mode, does not provide any QoS mechanism. Consequently all stations, including the base station ID, in a WLAN have the same probability to acquire and to send data within the medium. This type of service is referred to as a “best effort”.
Three interframe space (IFS) intervals defer an IEEE 802.11 station's access to the medium and provide various levels of priority. Each interval defines the duration between the end of the last symbol of the previous frame to the beginning of the first symbol of the next frame. The Short Interframe Space (SIFS) provides the highest priority level by allowing some frames to access the medium before others, such as an ACK frame, a Clear-to-Send (CTS) frame, or a fragment of a previous data frame.
Simultaneous transmit attempts lead to collisions in the downlink, since only one transport stream can be transmitted during any one period. The problem is particularly acute during periods of high traffic loads and may render the protocol unstable. The IEEE 802.11 MAC layer uses collision avoidance rather than collision detection in order to simultaneously transmit and receive data. To resolve collisions, subsequent transmission attempts are typically staggered randomly in time using a binary exponential backoff. The DCF uses physical and virtual carrier sense mechanisms (carrier sense multiple access with collision avoidance (CSMA/CA)) with a binary exponential backoff that allows access attempts after sensing the channel for activity.
If the broadcast or multicast originator is a mobile terminal, broadcast or multicast data are first transferred from the mobile terminal to the ID in a unicast transmission. According to the IEEE 802.11 specifications, the broadcast/multicast message may be distributed into the BSS by the ID. Regardless of the length of the frame, no RTS/CTS exchange can be used. In addition, no acknowledgement (ACK) is permitted to be transmitted to the ID by any of the recipients of the multicast/broadcast frame(s). There is no MAC-level recovery on broadcast or multicast frames sent from the ID.
When several devices share the same medium, there is a need for a mechanism in order to arbitrate acquisition of the medium. This mechanism is conventionally implemented in the MAC (Medium Access Control) layer. When the mechanism is distributed (i.e. there is no central controller) there is no possibility of QOS. The service offered to the upper protocol layers is said to be “best effort”. However, there is a need to provide some quality of service using some mechanism implemented in upper layers like network (IP) or transport (TCP/UDP). In order to cope with legacy devices, the mechanism should not impact the end devices (terminal or server). It should then be implemented in an intermediate device like an AP or a bridge, where bridge and/or AP are used herein to include router and/or brouter or any device having equivalent functionality. There is a mechanism at the IP layer like Diffserv that stores all incoming packets into the different queues according to the Diffserv class to which the packet belongs. The queues are emptied according to an algorithm that prioritizes the packets belonging to the queue associated with the highest-class number or some other predetermined algorithm/method.
The problem with such a mechanism is that it introduces packet dropping and packet re-transmissions. In a network, e.g., WLAN environment, a mechanism that avoids packet dropping is needed.
The context of the present invention is the family of wireless local area networks or WLANs based upon the IEEE 802.11 standards, which define intermediate devices (IDs) such as access points (APs), bridges, routers and brouters that provide access for mobile devices and to other networks, such as hard-wired local area and global networks, such as the Internet. Wireless receiving points utilized in access broadcast video streaming may include a set top box in a simple system, whereas in commercial rebroadcast system a transcoder/multiplexer/demultiplexer or TMD may operate in conjunction with a local video server. In receiving Internet data, a common gateway operating in a conventional Internet Protocol/Transmission Control Protocol/User Datagram Protocol (IP/TCP/UDP) protocol may be utilized.
When no Quality of Service (QOS) mechanism is provided, in a best effort environment, the invention proposes a mechanism at the transport level (TCP/UDP) that provides a bandwidth reservation mechanism for UDP traffic by slowing down the TCP traffic. Moreover the invention deals with the near/far problem typical in a WLAN environment.
Based on the assumption that UDP traffic is typically used for video, the present invention describes a mechanism that deals with the TCP packets. In order to prioritize the UDP traffic (that is typically used for video) the intermediate device (the AP, for example) measures the TCP traffic and when the throughput passes a certain threshold, it slows down the TCP traffic by slowing down the TCP ACK packets.
It is known in the art, how to enhance the TCP efficiency in a WLAN environment. However, no one teaches controlling the TCP traffic in order to limit the throughput rate in a WLAN intermediate device (ID) for bandwidth reservation purposes.
The present invention describes a method for implementing a bandwidth reservation mechanism in an ID at a higher level/layer in order to ensure a certain minimum bandwidth (and, therefore, QoS), for a certain type or class/category of data packets.
The present invention relates to the DCF mode, maintaining compatibility with the current ID standard for bandwidth allocation in the downlink, and thus, prioritizes a video broadcast or multicast downlink stream. The methods described herein, however, may be used in the uplink or both the uplink and the downlink.
A system and method for controlling bandwidth allocation of first and second data packet types in a single rate and multi-rate network by determining, by a device, a throughput rate of the first data packet type in the network and reducing, by the throughput rate of the first data packet type when the throughput rate reaches a predetermined level, thereby guaranteeing a minimum bandwidth for the second data packet type, are described. Additionally, a comparison is made against a lower threshold and a determination is made if the throughput rate reduction should be continued or if the throughput rate should be raised. The device is typically an intermediate device, which may be, for example, an access point (AP), a bridge, a router or a brouter.
The mechanism of the present invention, thus, provides a method to reserve bandwidth for a certain traffic category/class without impacting the end devices (terminal, server). The mechanism is particularly suitable for WLAN environments and when UDP traffic (video broadcast for instance) has to take priority over other traffic.
The mechanism of the present invention can also handle the WLAN near/far problem. The near/far problem exists when an adaptive (or dynamic) link adaptation mechanism is part of the wireless communication. The physical mode (modulation and error correction scheme) may change at any moment depending of the quality of the radio signal. One consequence is that the maximum bit rate is lower at the edges of the cell (far) and higher closer to the intermediate device (near). The UDP traffic is assumed to be broadcast/multicast (e.g., video multicast). That means a certain maximum range is established as a target because the combination of bit rate and error rate beyond that range makes multicast infeasible. For example, the target might be 100 meters. The intermediate devices are configured such that the physical coding mode (coding plus modulation) corresponds to a maximum bit rate of 5.5 Mbps for transmitting UDP packets. There must be sufficient bandwidth for the UDP traffic/data packets according to a user configured maximum bandwidth. Each new TCP session results in a re-calculation of the TCP packet throughput rate in accordance with UDP traffic/data packet requirements. For example, assume that all UDP traffic/data packets are targeted for 100 meters. That is, the UDP traffic/data packets are all being multicast/broadcast to members of the data packet category/class 100 meters (±delta) from the intermediate device. At 100 meters, the maximum bit rate for the physical coding mode is 5.5 Mbps. This controls both the number of TCP sessions and the distance of the TCP sessions from the intermediate device because the distance from the intermediate device dictates the maximum bit rate. Since TCP sessions and the attendant transmission of TCP data packets is constantly changing in a network and even more particularly in a WLAN because it is assumed that the user device is a mobile terminal/mobile device (MT/MD), the predetermined upper and lower thresholds are constantly being re-calculated. That is, while the upper and lower threshold may be static it is more likely that they are dynamic.
The invention is best understood with reference to the Detailed Description of the Preferred Embodiments and the drawings where:
As further illustrated in
The method described herein teaches controlling the bandwidth allocation in a shared medium (network) that may be a WLAN. The mechanism segregates TCP and UDP traffic and reserves bandwidth for UDP traffic. The mechanism also works in the case where only TCP traffic exists. In that case, the mechanism functions to reserve bandwidth for a particular class/category of traffic (data packets).
In a first embodiment, the maximum bandwidth offered by the medium is fixed. For example, the bandwidth can be a 10 Mbit/s Ethernet segment or a WLAN network with a short coverage in such a way that the coding and modulation cannot vary. The physical coding mode is forced to always be the same. Consequently, the maximum coverage is always the same. The second embodiment, deals with the particular case of the network (e.g., WLAN) technology where the maximum bit rate may vary as a function of the position of the user terminal, e.g., the network may be a WLAN and the user may be using a mobile terminal/mobile device (MT/MD). Any network where the maximum bit rate varies as a function of the position (distance) of the user terminal from an ID in the network qualifies as an exemplary network for purposes of discussion for the second or alternative embodiment of the present invention.
The method comprises segregating the traffic going through the base station (or AP) into two types of data packets (TCP and UDP) and reserving some bandwidth for the UDP traffic in such a way that whatever the TCP traffic is, there will be sufficient bandwidth for the UDP traffic. The mechanism of the present invention can be applied in one direction only (i.e. either uplink or downlink) or in both directions.
In order to control the TCP traffic it is necessary to measure the TCP throughput (.TT) that crosses the base station and compare it with the Maximum TCP Throughput (MTT) that will be permitted.
The TCP throughput is the sum of Nt individual TCP session throughputs TTi and is measured continuously.
The MTT is the Maximum Possible throughput (MPT) that can be expected from the radio interface minus the Maximum UDP Throughput (MUT) needed to be provisioned. The MUT may be a fixed value, which would mean that resources would be provisioned based on the real need. Alternatively, the MUT may be the current UDP traffic throughput (UT) with a Maximum Configured UDP traffic (MCUT) value that it cannot exceed.
MTT=MPT−MUT 2.
If UT<MCUT then MUT=UT else MUT=MCUT 3.
If TT becomes greater than MTT the mechanism limits the TCP traffic by slowing the TCP acknowledgements down. All received TCP ACK are then systematically slowed down until the TT drops below a certain predetermined threshold. The time (ST) required to slow down the TCP traffic is computed as follows:
ST=(TT−MTI)/TT 4.
The overall time ST is then distributed proportionally among TCP packets. For each individual TCP packet, the corresponding TCP ACK will be slowed down according to its packet size (Sp), where STp is the slow down time per packet:
STp=(Sp/TT)*ST 5.
There may be other methods to distribute the overall time ST among TCP packets such as using an equal distribution algorithm, where the ST is divided by the number of TCP sessions. For each session i, the ACK is slowed down according to the corresponding ST (STi). This method is not fair but advantaging the TCP sessions that have a big throughput is an alternative. In this method STi is the overall slow down time per session, STpi is the slow down time per packet per session and SPi is the packet size per session.
STi=ST/NT 6.1
STpi=(Spi/TTi)*STi 6.2
Once the slowing down begins, there is an expected inertia due to the TCP congestion mechanism that smoothes the RTT (Round Trip Timeout) in order to cope with lost packets (i.e. a lost packet does not cause the RTT to increase accordingly). Thus, the threshold for starting to limit the TCP throughput should be smaller than the MTT. Consider K as the high threshold that triggers the TCP ACK slow down mechanism. K is dependent on MTT.
When a new TCP session starts, some time is required to compute the effects on the TCP throughput (TT). It is also important to consider the resolution of the RTT in the TCP server. This means that if the TCP ACK is slowed down for a very short period, it is likely the TCP server will not react (the RTT will not be updated). Therefore, Y is chosen as the low threshold value (lower bound) that stops the TCP ACK slow down.
Y<K with K and Y=f(MTT) 7.1
Then Equation 4 becomes:
ST=(TT−Y)/TT 7.2
In the second or alternative embodiment of the present invention, also called the multi-bit rate network embodiment, in networks, such as the WLAN IEEE 802.11 or ETSI Hiperlan2, the overall available bit rate at the radio interface depends on the distance between the user (e.g., MT) and a point of access into the network (e.g., AP). According to this distance, the physical layer (PHY) applies different error correction mechanisms as well as different modulation schemes. For instance, according to the IEEE 802.11b specification the AP coverage is 400 m at 1 Mbit/s, 170 m at 2 Mbit/s, 100 m at 5.5 Mbit/s and 50 m at 11 Mbit/s. The user, e.g. MT is assumed to be mobile and thus the control of the bit rate used by the TCP traffic depends on the location of the users (the distance of the user (MT) from an AP).
It is assumed that the downlink UDP traffic is forwarded by the ID using the same constant bit-rate, for example 5.5 Mbit/s (the access point forces the physical mode for each of those downlink UDP packet). It is also assumed that there is already a mechanism in the radio interface in order to trigger the change of the modulation/error correction scheme according to a measurement such as SNR (Signal/Noise ratio) for TCP packets.
The TCP sessions that are established between the ID and the user terminals consume the bandwidth as a function of the distance between the ID and the user terminal and thus as a function of the physical coding (modulation). In order to apply the rules and equations as detailed in the previous embodiment, it is necessary to convert the throughput linked with a TCP session taking into account the physical mode used with that session. As an example, assume the UDP traffic is forwarded using the 5.5 Mbps physical mode. Any TCP session throughput computation is then converted according to the 5.5 Mbps mode. For instance, a mobile device located far from the access point (ID) required the physical mode associated with the 1 Mbps bit rate. The mobile device is involved in a TCP session consuming 500 Kbps. After conversion (500 Kbps with a 1 Mbps bit rate requires 0.5 seconds) the TCP session associated with the mobile device consumes 2.75 Mbps taking into account the 5.5 Mps physical mode bit-rate. The TTi as required by the equation 1, is computed as follows.
TTi=UPM*TTRi/TPMi 8.1
with UPM being the UDP physical mode bit rate as 5.5 Mbps in the example above, TTRi being the real TCP throughput (500 Kbps in the example above) measured with the physical mode currently used associated with the maximum bit rate T?Mi (1 Mbps in the example above). Of course, after computing equation 5, the symmetric conversion is required in order to compute the time the packet has to be slowed down according to the physical mode linked with the corresponding TCP session. The real slow down time for each TCP packet (RSTp) is then computed as follows:
RSTp=STp*TPMi/UPM 8.2
with STp being computed using equation 5, UPM being the UDP physical mode bit rate (5.5 Mbps in the example above) and TPMi the maximum bit rate associated with the physical mode currently used by TCP session i associated with the TCP packet (1 Mbps in the example above).
The mechanism can be adapted to support a layer-3 mechanism such as Diffserv. Diffserv is a mechanism that permits the application of different levels of quality of service (QoS) according to a stream class. Basically, each data packet is marked by an ingress router/bridge/brouter at the edge of the Diffserv domain. The ingress router/bridge/brouter sets a dedicated field of the IP packet header called type of service (ToS) to IPV4. The value is chosen according to configuration rules, for example, all packets with a particular source address will get the same ToS. When a marked IP packet crosses a router/bridge/brouter within the Diffserv domain, the router/bridge/brouter applies a forwarding behavior according to the ToS field. The behavior is related to scheduling, queueing and/or policing. Each Diffserv class may correspond to a class/category of segregated TCP traffic. It is assumed then that Diffserv traffic (data packets) is only TCP.
Referring next to
It is to be understood that the present invention may be implemented in hardware, software or firmware or any combination thereof. It is to be further understood that, because some of the constituent system components and method steps depicted in the accompanying figures may be implemented in software, the actual connections between the system components (or the process steps) may differ depending upon the manner in which the present invention is programmed. Given the teachings herein, one of ordinary skill in the related art will be able to contemplate these and similar implementations or configurations of the present invention.
It is to be understood that the form of this invention as shown is merely a preferred embodiment. Various changes may be made in the function and arrangement of parts; equivalent means may be substituted for those illustrated and described; and certain features may be used independently from others without departing from the spirit and scope of the invention as defined in the following claims. For example, although the invention is described in the context of IEEE 802.11 based WLANs, it is to be understood that the invention may be applied to structures based on other wireless LAN standards wherein the synchronization is to be maintained.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US04/32954 | 10/6/2004 | WO | 3/29/2006 |
Number | Date | Country | |
---|---|---|---|
60510200 | Oct 2003 | US |