This application claims the benefit, under 35 U.S.C. § 365 of
International Application PCT/CN2007/000624, filed Feb. 27, 2007, which was published in accordance with PCT Article 21(2) on Sep. 4, 2008 in English.
1. Field of the Invention
The present invention relates to the technical field of wireless local area networking (WLAN) and, more particularly, to a method and apparatus for power saving in a WLAN.
2. Description of Related Art
With the proliferation of portable computing and mobile technology, energy conservation has become an important issue and receives more and more attention. To make the best use of battery resources and prolong a device's battery life, a power saving mechanism is proposed within the IEEE 802.11 standards (IEEE 802.11 standard for Information Technology—Telecommunications and Information Exchange between Systems Local and Metropolitan Area Networks Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. ANSI/IEEE Std. 802.11, ISO/IEC 8802-11. First Ed. (1999)). As specified in the standard, an IEEE 802.11 based wireless adapter, or station, can be in one of two states at any time, awake or sleep. The sleep state usually consumes an order of magnitude less power than the awake state. Therefore, the task of the power saving mechanism is to maximize time spent in the sleep state and minimize time spent in the awake state, while not degrading the networking performance of the device.
A station in PSM (any of stations 32) cooperates with its associated AP (31) to achieve power savings. Within the IEEE 802.11 standard, the general idea is for the AP to buffer frames for stations in PSM and to synchronize these stations to wake up at the same time. At the wakeup time, there starts a window where the AP announces its buffer status to the associated mobile stations by using a beacon. The AP periodically transmits the beacon and a mobile station in PSM shall power up to listen to the beacon to check whether there are frames buffered in the AP. The stations determine whether there are buffered frames by analyzing bitmap information in a traffic indication map (TIM) element contained in the beacon. The TIM structure is depicted in
In the unicast case, the AP buffers incoming frames destined to a power saving (PS) station, announce this event through the TIM in a beacon frame, and then these buffered frames are retrieved by the PS station through PS-Poll requests. In the B/M case, the AP buffers all incoming broadcast/multicast frames if any client in the BSS is in PSM and sends them out without polling after a beacon with a delivery traffic indication message (DTIM) has been transmitted. A DTIM is a special TIM. In both cases, the PS station stays in the awake state unless it is explicitly notified that the buffered frames, destined for it or for a group, are swept out.
The TIM element of the beacon frame plays a key role in the overall procedure. It provides a one to one mapping between bits and mobile stations through the association identifiers (AIDs). AIDs are assigned to each client within a basic service set (BSS) during the association procedure. When a client joins a BSS the AP gives the client an AID. In addition, the AID is used to determine the location of a stations bit in the TIM. In other words, each station associated with the AP is assigned one bit in the bitmap of a TIM with the position of the bit being related to the AID the station was assigned. The bit number N corresponds with the AID N in the TIM bitmap. If the bit N is set in the TIM of a beacon the existence of buffered unicast frames for the station AID N is indicated.
With reference to
A special bit, corresponding to AID 0, is reserved for B/M frames. As shown in
Generally the PSM outperforms the CAM in terms of power consumption, at the cost of networking performance, such as delay and throughput. However, in practice the current PSM is still not efficient enough to achieve power conservation. For example:
1) Though a station can be informed of the existence of buffered unicast frames for it at the AP through a TIM within a beacon frame, it is impossible, as implied by the current mechanism, for the station to control the timing of the starting and ending of the transmission of the buffered frames; thus, the station has to stay awake for an unpredictable period, until the procedure concludes. The length of the awake period within a beacon interval depends on the number and size of a station's buffered frames at the AP, but also is greatly affected by other stations retrieval of buffered frames. The progress of transmitting the buffered frames for one station can be put off for a long time because of another station's behavior, causing substantial power consumption by the station.
2) According to the 802.11 standard, once a DTIM has been sent out with a beacon, the AP can sweep out all the buffered B/M frames thereafter. This behavior may have a great impact on another station's networking performance, especially for unicast applications, as the intrinsic preemptive characteristic of broadcasting/multicasting can lead to the non-availability of the wireless medium for other stations. A more flexible scheme should be adopted for the transmission of B/M frames.
3) The current mechanism uses one bit to indicate the existence of buffered B/M frames at the AP. Therefore, the current mechanism does not differentiate between multicast frames and broadcast frames, and moreover, multicast frames belonging to different multicast groups are treated as the same. This coarse granularity makes the scheme work inefficiently in multicasting environments. The major deficiency lies in that a mobile station has to stay in the active state whenever there are multicasting frames transmitting at the AP, even if these frames are destined to other multicast groups than the group this station belongs to, or a worse case that this station does not join any multicast group at all. The energy used to scout multicast traffic that will not be received by a station is an unnecessary waste.
What is needed is an arrangement and method that addresses the above-mentioned problems
In an embodiment of the present invention a method for transmitting data in a wireless local area network is described. The method includes buffering, at an access point, frames including data to be transmitted to stations capable of operating in a power-saving state. Prior to sending a beacon frame, the access point divides an interval between beacon frames into a number of time slices. The access point transmits the beacon frame including information about a time slice when buffered frames destined for particular stations will be sent.
In a further embodiment a method for use in a node in a 802.11 wireless local area network, the network including an access point and at least one station. The method includes formatting data into a control frame for use in the wireless local area network, the frame including an indication, for each station associated with the wireless local area network, whether frames are buffered awaiting transmission to each respective station, a number of time intervals between control frames, and at which time interval the transmission of the buffered frames will begin for each station having buffered frames awaiting transmission. The frame is then transmitted.
In another embodiment an access point in a wireless local area network, which periodically transmits a beacon frame is described. The access point includes a transmitter for transmitting data, including the beacon frame, through the wireless local area network to plural stations, a memory to buffer frames awaiting transmission to the plural stations, which are capable of operating in a power-saving state, and a processor dividing an interval between beacon frames into a number of time slices, and transmitting information about a time slice when buffered frames for a respective station will be sent.
In another embodiment a method of receiving data in a wireless local area network is described. The method includes receiving a beacon frame having information regarding time slices indicating when data associated with a particular station will be transmitted; and determining whether an interval between a current beacon frame and a subsequent beacon frame includes data to be received by the particular station, if so, determining a time slice within the interval that includes the data to be received.
In another embodiment a station in a wireless local area network is described. The station includes a receiver receiving a beacon frame having information regarding time slices indicating when data associated with a particular station will be transmitted; and a processor determining whether an interval between a current beacon frame and a subsequent beacon frame includes data to be received by the particular station, if so, determining a time slice within the interval that includes the data to be received.
These and other aspects, features and advantages of the present invention will become apparent from the following description of non-limiting exemplary embodiments, which is to be read in connection with the accompanying drawings.
a): an exemplary embodiment of a Beacon with a newly designed TIM structure in accordance with the present invention;
b): an exemplary embodiment of a frame structure of the present invention in accordance with the present invention;
The original TIM structure in the IEEE 802.11 standard, as described above, does not carry sufficient information for supporting a more complicated power saving scheme. An embodiment of the invention provides a TIM structure that is able to support time slicing operations for power management and addresses the problems mentioned above.
a) shows an exemplary embodiment of a TIM structure of a Beacon frame. Compared with the original TIM structure, two fields, slicing control field and slicing map field, are added at the end of the partial virtual bitmap (PVB) for supporting time slicing. In addition, the significance of the PVB bits changes within this new structure. These amendments and modifications are detailed as follows.
1) Slicing Control Field:
The slicing control field, as shown in
Once the number of bits for each SI is set in the slicing control field, the AP can determine how many time slices the beacon period should be divided into. The number of time slices shall equal the maximal possible value of the SI, that is, for a n-bit-wide SI, a total of 2n−1 slices shall be derived. For example, if the slicing control field is set to 5, then the beacon period should be divided into 25−1=31 consecutive time slices. For a beacon period of 100 ms, each time slice lasts about 100/31=3.226 ms.
As the slicing control field is constrained to 8 bits, the maximal number of bits for a SI can be set to 28−1=255; therefore, the maximum number of bits in an SI is 255 where the beacon period could be divided into 2255−1 consecutive time slices. Various factors and variables are evaluated as desired to implement an “optimal” slice control. These variables may include the number of slices desired, a desired granularity, and the number of different stations having buffered frames. In addition the higher the value of the slicing control field means finer granularity of the time divisions and thus less power consumption, however this comes at the cost of a longer slicing map (SI), which results in more overhead of the beacon frame. Hence setting this field is a trade-off between power performance and increasing the overhead of the beacon frames. In a preferred embodiment, the slicing control field value should not exceed 10, as 210−1=1023, that is, using 1023 bits to indicate the position of the assigned time slices, which is a large overhead for the beacon frames.
2) Slicing Map Field:
The slicing map field, as shown in
Other SIs can't be set to 0 (otherwise the SI can be omitted) and each SI corresponds to an AID whose bit is set in the Partial Virtual Bitmap. As shown in
For example, in
3) Partial Virtual Bitmap Field:
In the original TIM, each bit corresponds to one client identified by an AID. With reference to
As an AP primarily deals with MAC layer information, a multicast group is differentiated using its MAC address. Therefore each multicast group is assigned a MAC address and a corresponding AID. Though the multicast IP addresses and their corresponding MAC addresses are not strictly one-to-one mapping, it is still reasonable to maintain an AID for each multicast MAC address rather than a multicast IP address at the AP, as the possibility of two multicast IP addresses mapped to one MAC address is extremely small.
Note that though the two fields, slicing control and slicing map field, are appended after the partial virtual bitmap as two components of the TIM structure in
b) is an exemplary structure of the new element containing the two fields. The new element may be inserted immediately after the TIM element to send within the beacon frames, or it may be piggybacked onto another type of frames to all mobile stations after the launching of a beacon frame.
For clarity, the following descriptions are based on
Time Slicing Scheme
The time slicing scheme primarily deals with the processing of the buffered frames for the PSM mobile stations. In other cases, for example, when a client stays in active mode, all unicast frames destined for it may be handled at the AP in its normal way.
With reference to
As pointed out above, before a beacon frame is launched, the AP divides the beacon interval into a fixed number of slices of equal length. In an exemplary embodiment the processor 640 of
As disclosed herein, an AP 610 is assigned to each multicast MAC address as for a mobile station, and all the pending frames are grouped according to their pertaining AIDs. The AP 610 employs a scheduling algorithm to calculate the number of consecutive slices for each group and the exact position of the starting time for these slices. When the AP 610 has finished this procedure, it fills the fields in the TIM structure, particularly the slicing map field (SI) that announces the starting points of the assigned slices for each AID, and then sends the beacon out through transceiver 630.
Each station in power saving mode maintains an AID list, containing one unicast AID that is assigned by the AP during the association phase, and several other multicast AIDs assigned by the AP when joining multicast groups. Note that AID 0 is used for broadcast and it is known by all stations, so it maybe omitted in the list held in each station. The AID list held by the station is used to check the Partial Virtual Bitmap of the TIM after a beacon frame is received. If a bit corresponding to an AID in the station's list is set in the bitmap, the station goes further towards the slicing map field and locates the SI that matches the bit. The value of SI is used to calculate the time for it to wake up to receive frames. Thereafter the station can enter into sleep state and wake up at the calculated time. If multiple bits corresponding to AIDs in the station's list are set in the bitmap, then the station has to wake up and sleep several times within a beacon interval. However, as the starting time of the beacon period of the station is a little later than that of the AP, caused by the delay of beacon frames, it is reasonable for the station to wake up earlier for some time than expected so as not to miss the transmission of pending frames by the AP. Once the transmission of pending frames for this AID concludes, the station may return to sleep state, or keep in active state, if it has to wake up in a short time later.
The AP is responsible for controlling the starting time and lasting period for the transmission of pending frames for each group. The AP gains control of the wireless medium through a Priority Inter-frame Space (PIFS) as used for beacon frames. The PIFS is shorter than Distributed Inter-Frame Space (DIFS), so the AP takes an advantage over the other stations to gain the wireless medium. Once the starting time of slices that are assigned to some AIDs comes, the AP senses the wireless medium and tries to access the medium to commence the transmission of buffered frames. It is recommended that the AP hold the control of the wireless medium by protection, until all buffered frames for this SI are delivered out, or the next SI comes.
Multicast Association Procedure
As pointed out above each multicast group is assigned an AID during the negotiation phase when a client joins a multicast group with each multicast group having an MAC address. The AP maintains a mapping table between AIDs and MAC addresses for the purpose of managing the virtual bitmap within the TIM structure. AID 0 is reserved for broadcasting, while other positive integers are used for both multicasting and unicasting. A unicast AID is assigned to a station during its (re) association procedure with the AP, and a multicast AID is assigned to a group during a multicast association procedure, as described below.
An exemplary frame format of a multicast association request, multicast association response and multicast disassociation are shown in
The multicast association procedure works in a similar manner to the (re)association procedure defined in the 802.11 standard. Once a station has been confirmed by the router (through IGMP messages) that it has joined a multicast group, it initiates a multicast association request to the AP, with some field of the request being the MAC address of the multicast group. For example
The AP responds to the station with a multicast association response frame filled with an AID for that MAC address. For example
The AP may optionally maintain a member list for a multicast AID, of which a member corresponds to a station that joined the multicast group. A member list is useful for the AP to determine whether or not an incoming multicast frame pertaining to this multicast group should be buffered. If all members in the list are in CAM, then the frame is not buffered for power saving reasons.
When a station decides to quit a multicast group, it may choose to send a multicast disassociation frame to the AP with one field to be the multicast MAC address of the group. As shown in
As mentioned, the MAC address of a multicast group can be derived from its IP address. The last 23 bits (of 32) of the multicast IP address is used as the least significant 23 bits (of 48) of the MAC address, and the other 25 bits are fixed for the MAC multicast address. Though the mapping between these two addresses is not one-to-one, the possibility of two multicast addresses mapping to one MAC address can be ignored (1/223). A direct mapping technique is employed to map each group to an AID to enable the physical devices to become aware of the multicast frames buffered for the multicast group at the AP.
Service Period (SP)
The concept of service period as an embodiment of the time slicing scheme is described and exemplified in
In an embodiment of the present invention the AP is responsible of administrating the time slices, including the setting of a proper number of slices within one beacon interval, the allocation of time slices to an AID and the scheduling of buffered frames for transmission. The AP also assembles the information of slice allocation and fills in the slicing map field to be sent with the beacon frames. Moreover, the AP should gain control of the wireless medium in time to ensure the progress of the time slicing.
The frame transactions within the SP are implementation dependent, for example the transactions between a AP and a station for delivering the buffered frames. A protection method through network allocation vector (NAV) channel updating to avoid contention during transmission of pending frames may be implemented, as it squeezes the total time of the scheduled frame delivery for this SP, thus conserves power for the station. In spite of the manner of pending frame transaction during the SP, other stations can access the wireless channel using the normal distributed coordinated function (DCF) rules.
It is possible that the pending frames for a destination may not be delivered out within the appointed SP. In this situation, the AP can choose to send the remaining frames at its convenience in the current beacon interval or assign new time slices for their delivery in the next beacon interval.
Power State Transition of the Stations
In an embodiment of the present invention a station in power saving mode transitions between awake and sleep states according to the following rules:
1) The station shall enter the awake state prior to each TBTT (Target Beacon Transmission Time) to receive beacon frames.
2) If the SPs that are allocated for this station or for a multicast group to which this station belongs are not immediately transmitted after the beacon, the station can enter into the sleep state and wake up prior to the next targeting SP, otherwise, the station remains awake until the current SP concludes.
3) The station can choose to sleep within the SP, once it ensures that all buffered frames for it during this SP have been delivered. However, it is required to wake up prior to the next targeting SP.
From the foregoing description, one skilled in the art can ascertain certain features and advantages gained through this methodology. For example more power conservation should be achieved than that of the original standard. A station may wake up at the expected time to receive buffered frames from the AP and return to sleep state once the transaction concludes. Thus the energy drained while in an idle state is greatly reduced. Moreover, the activities of other stations have little effect on the power performance of the current station in PSM.
In addition, the delivery of the pending frames at the AP can be scheduled in a much more flexible manner. The AP can choose time slices for the transmission of the buffered frames within a beacon interval by utilizing it's own scheduling algorithms. This solution provides a possibility for the AP to process the pending frames in an optimized fashion, complying with the requirements of the stations.
These and other features and advantages of the present invention may be readily ascertained by one of ordinary skill in the pertinent art based on the teachings herein. It is to be understood that the principles of the present invention may be implemented in various forms of hardware, software, firmware, special purpose processors, or combinations thereof.
Most preferably, the principles of the present invention are implemented as a combination of hardware and software. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium. The application program may be uploaded to, and executed by, a machine comprising any suitable architecture. Preferably, the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPU”), a random access memory (“RAM”), and input/output (“I/O”) interfaces. The computer platform may also include an operating system and microinstruction code. The various processes and functions described herein may be either part of the microinstruction code or part of the application program, or any combination thereof, which may be executed by a CPU, whether or not such computer or processor is explicitly shown. In addition, various other peripheral units may be connected to the computer platform such as an additional data storage unit and a printing unit.
It is to be further understood that, because some of the constituent system components and methods depicted in the accompanying drawings are preferably implemented in software, the actual connections between the system components or the process function blocks may differ depending upon the manner in which the present invention is programmed. Given the teachings herein, one of ordinary skill in the pertinent art will be able to contemplate these and similar implementations or configurations of the present invention.
Although the illustrative embodiments have been described herein with reference to the accompanying drawings, it is to be understood that the present invention is not limited to those precise embodiments, and that various changes and modifications may be effected therein by one of ordinary skill in the pertinent art without departing from the scope or spirit of the present invention. All such changes and modifications are intended to be included within the scope of the present invention as set forth in the appended claims.
All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.
The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term “processor” or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (“DSP”) hardware, read-only memory (“ROM”) for storing software, random access memory (“RAM”), and non-volatile storage.
Other hardware, conventional and/or custom, may also be included. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.
In the claims hereof, any element expressed as a means for performing a specified function is intended to encompass any way of performing that function including, for example, a) a combination of circuit elements that performs that function or b) software in any form, including, therefore, firmware, microcode or the like, combined with appropriate circuitry for executing that software to perform the function. The invention as defined by such claims resides in the fact that the functionalities provided by the various recited means are combined and brought together in the manner which the claims call for.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/CN2007/000624 | 2/27/2007 | WO | 00 | 3/23/2010 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2008/104095 | 9/4/2008 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6622251 | Lindskog et al. | Sep 2003 | B1 |
7457973 | Liu | Nov 2008 | B2 |
7508781 | Liu et al. | Mar 2009 | B2 |
7519017 | Yi | Apr 2009 | B2 |
8005032 | Wang et al. | Aug 2011 | B2 |
20040141490 | Hong | Jul 2004 | A1 |
20040190467 | Liu et al. | Sep 2004 | A1 |
20040253996 | Chen et al. | Dec 2004 | A1 |
20050003794 | Liu | Jan 2005 | A1 |
20050009512 | Rue | Jan 2005 | A1 |
20050201341 | Griswold | Sep 2005 | A1 |
20050254444 | Meier et al. | Nov 2005 | A1 |
20050276237 | Segal et al. | Dec 2005 | A1 |
20060140186 | LoGalbo et al. | Jun 2006 | A1 |
20060187864 | Wang et al. | Aug 2006 | A1 |
20070248034 | Hsu et al. | Oct 2007 | A1 |
Number | Date | Country |
---|---|---|
2403875 | Jan 2005 | GB |
2007336078 | Dec 2007 | JP |
WO 2005069806 | Aug 2005 | WO |
WO2005107182 | Nov 2005 | WO |
WO 2006062292 | Jun 2006 | WO |
Entry |
---|
Search Report Dated Nov. 14, 2007. |
Number | Date | Country | |
---|---|---|---|
20100189021 A1 | Jul 2010 | US |