US 7,593,417 B2Grant
Handling broadcast and multicast traffic as unicast traffic in a wireless network
Issue Date:2009-09-22
•10 Claims
•5 Drawing Sheets
Abstract
An access point is to handle received broadcast or multicast traffic as multiple instances of unicast traffic, where each instance is destined for a corresponding wireless client device associated with the access point. A client device may adjust its listen interval parameter according to predefined considerations, for example a charge level of a battery to power the client device and an expected usage model for the device. A client device may initiate a reassociation request to inform the access point of its adjusted listen interval parameter.
Metadata
Assignee
- Research In Motion Limited
Inventors
- James Wang
- Tom Nagy
Application Information
Application Number:US 11/041,113
Filing Date:2005-01-21
Priority Date:2005-01-21
Art Unit:2617
Classifications
IPC:
H04L12/54
Patent Drawings (5 sheets)
Description
Background of the Invention
[0001] The invention generally relates to wireless networks. In particular, embodiments of the invention relate to power saving for one or more client devices in a wireless network.
[0002] A wireless access point (AP) is a device that “connects” wireless devices together to create a wireless network. The wireless devices, also known as “client devices”, communicate with each other or with other networks through the AP.
[0003] A client device may, or may not, be battery-powered. For example, a client device, such as a wireless-enabled laptop, a wireless-enabled cellphone, a wireless-enabled personal digital assistant (PDA), and the like, may sometimes be battery-powered, and at other times may receive power from an external source, such as a power outlet. Other client devices, such as a desktop computer, may receive power from an external source, such as a power outlet, and may not have the option to be battery-powered.
[0004] It may be beneficial to enhance the battery lifetime of battery-powered client devices.
Brief Description of the Drawings
[0005] Embodiments of the invention are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like reference numerals indicate corresponding, analogous or similar elements, and in which:
[0006] FIG. 1 is an illustration of an exemplary communications system, according to some embodiments of the invention;
[0007] FIG. 2 is an illustration of an exemplary sequence of beacon frames, helpful in understanding some embodiments of the invention;
[0008] FIG. 3 is a block diagram of an exemplary access point, according to an embodiment of the invention; and
[0009] FIG. 4 is a block diagram of an exemplary wireless client device, according to an embodiment of the invention.
[0010] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity.
Detailed Description of Embodiments of the Invention
[0011] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the invention. However it will be understood by those of ordinary skill in the art that the embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the embodiments of the invention.
[0012] FIG. 1 is an illustration of an exemplary communications system 100 according to embodiments of the invention. System 100 includes a wireless access point (AP) 102 and network gateways 104 and 106 coupled to AP 102 via wired connections 108 and 110, respectively. Network gateways 104 and 106, wired connections 108 and 110 may all be part of a “distribution system” for AP 102. Non-limiting examples for network gateways 104 and 106 are cable modems, Asymmetric Digital Subscriber Line (ADSL) modems, Asynchronous Transfer Mode (ATM) network gateways, dial-up modems, satellite modems, Integrated Services Digital Network (ISDN) gateways, T-carrier 1 (T1) modems, and the like. It is obvious that any other configuration of a distribution system for AP 102 is possible. System 100 also includes a desktop computer or server 112 coupled to gateway 104 via a wired connection 114.
[0013] AP 102 has at least one antenna 116 and is configurable to support at least one wireless network name, for example, at least one service set identifier (SSID). A non-exhaustive list of examples for antenna 116 includes a dipole antenna, a monopole antenna, a multilayer ceramic antenna, a planar inverted-F antenna, a loop antenna, a shot antenna, a dual antenna, an omnidirectional antenna and any other suitable antenna. AP 102 may include a router.
[0014] Exemplary communications system 100 includes wireless-enabled laptops 120 and 122, wireless-enabled cellphones 124 and 126 and wireless-enabled personal digital assistants (PDAs) 128 and 130. Each of wireless-enabled laptops 120 and 122, wireless-enabled cellphones 124 and 126 and wireless-enabled PDAs 128 and 130 is able to execute an initialization process to associate themselves in a wireless network with AP 102.
[0015] For example, wireless-enabled laptops 120 and 122, wireless-enabled cellphones 124 and 126 and wireless-enabled PDAs 128 and 130 may become associated with AP 102 over a wireless network 118. Wireless-enabled laptops 120 and 122, cellphones 124 and 126 and PDAs 128 and 130 are referred to as “client devices”.
[0016] The client devices shown in FIG. 1 are just an example and other suitable client devices and groupings of client devices are also possible. A non-exhaustive list of examples for client devices includes work stations, server computers, notebook computers, laptop computers, desktop personal computers (PCs), personal digital assistant (PDA) computers, hand-held computers, wireless local area network (WLAN) stationary units, WLAN add-on cards, WLAN personal computer memory card international association (PCMCIA) cards, WLAN PC cards, WLAN switches, WLAN routers, WLAN servers, game consoles, digital cameras, digital video cameras, television sets, wireless Internet-Protocol (IP) phones and the like.
[0017] In this example, AP 102 and the client devices are all “802.11-enabled”, which means that wireless communications therebetween are in accordance with one or more of the following standards defined by the Institute of Electrical and Electronic Engineers (IEEE) for Wireless LAN MAC and Physical layer (PHY) specifications:
[0018]
However, it will be obvious to those of ordinary skill in the art how to modify the following for other existing WLAN standards or future related standards, including 802.11n.
| Maximum | ||||
|---|---|---|---|---|
| Standard | Published | Speed | Frequency | Modulation |
| 802.11 | 1997 | 2 Mbps | 2.4 GHz | Phase-Shift |
| 802.11a | 1999 | 54 Mbps | 5.0 GHz | Orthogonal Frequency |
| Division Multiplexing | ||||
| 802.11b | 1999 | 11 Mbps | 2.4 GHz | Complementary Code |
| Keying | ||||
| 802.11g | 2003 | 54 Mbps | 2.4 GHz | Orthogonal Frequency |
| Division Multiplexing | ||||
However, it will be obvious to those of ordinary skill in the art how to modify the following for other existing WLAN standards or future related standards, including 802.11n.
[0019] The 1999 edition of the 802.11 standard (as reaffirmed Jun. 12, 2003) distinguishes between infrastructure WLANs and ad-hoc WLANs. The following description is for infrastructure WLANs, involving the use of access points.
[0020] The 802.11 standard explains that access points transmit beacon frames at substantially regular time periods to announce the existence of and to synchronize wireless networks. The number of time units between target beacon transmission times is referred to as a “beacon interval”. The format of beacon frames and their contents is explained in detail in the 802.11 standard. The beacon interval is included in each beacon frame.
[0021] Each beacon frame also includes a timestamp which is the value of a clock internal to the access point at the actual transmission time of the beacon. Due to use of carrier sense multiple access/collision detection (CSMA/CD) techniques, the actual transmission time may be later than the target beacon transmission time. Consequently, the timestamp field of the beacon frame is not filled until the actual transmission occurs. A client device receiving the beacon frame will update its internal clock according to the timestamp in the received beacon frame.
[0022] Each beacon frame also includes a Traffic Indication Map (TIM) that identifies client devices for which unicast traffic is pending and buffered in the access point. This information is encoded in a partial virtual bitmap. The TIM also includes an indication whether broadcast or multicast traffic is pending.
[0023] There are two different TIM types: TIM and delivery TIM (DTIM). A TIM includes a “DTIM count” field that indicates how many beacon frames (including the current frame) appear before the next DTIM. A DTIM count of zero indicates that the current TIM is a DTIM. The “DTIM period” field indicates the number of beacon intervals between successive DTIMs. Every DTIM period, a TIM of type “DTIM” is transmitted within a beacon, rather than an ordinary TIM. After a DTIM, the access point sends out the buffered broadcast or multicast traffic using normal frame transmission rules, before transmitting any unicast frames.
[0024] A client device may be in one of two different power states: “Awake”—the client device is fully powered; and “Doze”—the client device is unable to transmit or receive and consumes very low power. The manner in which a client device transitions between these two power states is determined by the power management mode of the client device. In “Active mode”, the client device may receive frames at any time and is in the “Awake” state. In “Power Save mode”, the client device listens to selected beacon frames (based upon the client device's “Listen Interval” parameter) and sends “Power Save poll (PS-poll)” frames to the access point if the TIM element in the most recent beacon frame indicates buffered unicast traffic for that client device.
[0025] In Power Save mode, a client device is in the Doze state and enters the Awake state to receive selected beacons, to receive broadcast and multicast transmissions following certain received beacons, to transmit, and to await responses to transmitted PS-poll frames or (for CF-pollable client devices) to receive contention-free transmissions of buffered traffic.
[0026] An access point maintains a Power Management status for each currently associated client device that indicates in which Power Management mode the client device is currently operating. Depending on the Power Management mode of the station, the access point temporarily buffers traffic destined for the client device. The access point transmits buffered unicast traffic to a client device in Power Save mode only in response to a PS-poll from that client device or during the contention-free (CF) period in the case of a CF-pollable client device in Power Save mode.
[0027] The “Listen Interval” parameter of a client device specifies the maximum number of beacon intervals that may pass before the client device awakens and listens for the next beacon frame. The client device informs the access point of its “Listen Interval” parameter during the association with the access point. The parameter may be determined, for example, by the desired power consumption/performance target of the client device.
[0028] The access point has an aging function to delete buffered traffic when it has been buffered for an excessive period of time. The aging function is based on the “Listen Interval” parameter, so that buffered traffic is retained for a period that is at least as long as a product of the Beacon Interval and the “Listen Interval” parameter of the client device for which the traffic is buffered.
[0029] The client device also has a Boolean parameter, entitled “Receive DTIMs”, which is set when the client device informs the access point of a change in the power management mode of the client device. When the “Receive DTIMs” parameter is true, the client device awakens to receive all beacon frames that include a DTIM. When the parameter is false, the client device is not required to awaken for every beacon frame that includes a DTIM.
[0030] More detail about the power-management operation of the access point and client devices during the contention period and the contention-free period is given in the section of the 802.11 standard entitled “Power management in an infrastructure network”.
[0031] The “Listen Interval” parameter of a particular client device affects the particular client device's power save behavior regarding unicast traffic, and the “DTIM period” of the access point and the “Receive DTIMs” parameter of the client devices affect the power save behavior of all client devices in the wireless network regarding broadcast and multicast traffic.
[0032] Client devices in a wireless network may have conflicting requirements for power consumption and communication throughput when in Power Save mode. Moreover, the need for power saving in a battery-powered client device may increase over time as the battery drains, overriding communication throughput considerations for the battery-powered client device.
[0033] Currently, an access point is able to store only a single DTIM period. Consequently, different client devices in Power Save mode will all wake up for the same beacon frames according to the single DTIM period. Currently, a network manager may need to balance the conflicting requirements for power consumption and communication throughput when in Power Save mode of client devices in a wireless network when configuring the DTIM period of an access point.
[0034] Currently, a client device that has its “Receive DTIMs” parameter set to true and is in Power Save mode will awaken according to the DTIM period of the access point with which it is associated in order to listen to DTIMs and determine whether to stay awake to receive broadcast or multicast traffic. That same client device will also awaken within a period determined by its “Listen Interval” parameter to listen to TIMs and determine whether to stay awake to issue a PS-poll frame for buffered unicast traffic.
[0035] Each client device has a unique hardware address, for example a medium access control (MAC) address, and is assigned an Internet Protocol (IP) address by a dynamic host configuration protocol (DHCP) server, which may be embedded in the access point. Alternatively, the IP address of a client device may be statically configured. In addition, an access point assigns an “association identifier (AID)” to client devices associated therewith and maintains a mapping of AIDs to MAC addresses. The access point identifies those client devices for which it has buffered unicast traffic by setting bits in the TIM's partial virtual bitmap that correspond to the appropriate AIDs. Moreover, the access point maintains an Address Resolution Protocol (ARP) table that contains a mapping of Internet Protocol (IP) addresses to MAC addresses.
[0036] A network gateway may receive from an external network one or more information frames to forward to a network device associated with a particular IP address. The network gateway may have to resolve the MAC address of the network device associated with the particular IP address in order to include the MAC address in the information frames and to send the information frames to the network device. The network gateway may generate an ARP request and send it to the various network devices, including the access point, which will treat it as broadcast traffic. The network device (or client device associated with the access point) having the particular IP address may respond to the ARP request with its MAC address.
[0037] According to an embodiment of the invention, AP 102 may handle received broadcast or multicast traffic as multiple instances of unicast traffic, where each instance is destined for a corresponding client device associated with AP 102. AP 102 will indicate in a TIM the existence of each instance that is destined for a client device in Power Save mode. This indication will be repeated in subsequent TIMs until the aging function of AP 102 has caused the instance to be discarded or until the client device has issued a PS-poll frame or has received the instance in a contention-free transmission of buffered traffic, whichever comes first.
[0038] AP 102 will no longer indicate in a DTIM the existence of the broadcast or multicast traffic and will no longer transmit the broadcast or multicast traffic following a DTIM. Consequently, this embodiment will affect all client devices associated with AP 102. Alternatively, AP 102 will continue to indicate in a DTIM the existence of the broadcast or multicast traffic and to transmit the broadcast or multicast traffic following the DTIM, in addition to the transmission of the broadcast or multicast traffic as multiple instances of unicast traffic. In this alternative embodiment, only those client devices having a “Receive DTIMs” parameter set to false will be affected.
[0039] FIG. 2 is an illustration of an exemplary sequence of beacon frames transmitted by AP 102, according to some embodiments of the invention. Each beacon frame 200 includes a TIM, and if, for example, the DTIM period of AP 102 is 3, then in every third beacon frame, the TIM is a DTIM.
[0040] For example, laptop 122, cellphone 126 and PDAs 128 and 130 may be in Power Save mode, with “Listen Interval” parameters of 4, 8, 8 and 6, respectively.
[0041] For example, if AP 102 receives an ARP request 201 prior to beacon frame 202, AP 102 will handle the broadcast traffic as multiple instances of unicast traffic, where each instance is destined for a corresponding wireless client device associated with AP 102. Since laptop 120 and cellphone 124 are in Active mode, AP 102 will transmit ARP request 201 to laptop 120 and cellphone 124 as soon as possible. AP 102 will buffer ARP request 201 for each of the client devices in Power Save mode.
[0042] AP 102 will then include in TIMs of subsequent beacon frames indications of this buffered “unicast” data. For example, AP 102 will include in the TIM of beacon frame 202 indications that unicast data is buffered for laptop 122, cellphone 126 and PDAs 128 and 130. Laptop 122 may awaken from Power Save mode to listen to the TIM of beacon frame 202, may identify that unicast data is buffered, and may send a PS-poll frame 204 to AP 102 in response. AP 102 may then transmit ARP request 201 to laptop 122.
[0043] AP 102 will then include in the TIM of beacon frame 206 indications that unicast data is buffered for cellphone 126 and PDAs 128 and 130. PDA 130 may awaken from Power Save mode to listen to the TIM of beacon frame 206, may identify that unicast data is buffered, and may send a PS-poll frame 208 to AP 102 in response. AP 102 may then transmit ARP request 201 to PDA 130.
[0044] AP 102 will then include in the TIMs of beacon frames 210, 212, 214, 216 and 218 indications that unicast data is buffered for cellphone 126 and PDA 128. Cellphone 126 and PDA 128 may awaken from Power Save mode to listen to the TIM of beacon frame 218, may identify that unicast data is buffered, and may send PS-poll frames 220 and 222, respectively, to AP 102 in response. AP 102 may then transmit ARP request 201 to cellphone 126, followed by a transmission of ARP request 201 to PDA 128.
[0045] FIG. 3 is a block diagram of an exemplary access point, according to some embodiments of the invention. AP 102 includes at least one antenna 116 coupled to a radio 302, which in turn is coupled to a processor 304 having baseband functionality. A non-exhaustive list of examples for processor 304 includes a central processing unit (CPU), a microcontroller, a digital signal processor (DSP), a reduced instruction set computer (RISC), a complex instruction set computer (CISC) and the like. Furthermore, processor 304 may be part of an application specific integrated circuit (ASIC) or may be a part of an application specific standard product (ASSP).
[0046] AP 102 also includes a wired network interface 306 coupled to a wired network controller 308. The wired network(s) may be, for example, Ethernet network(s), token rings, Universal Serial Bus (USB), wired network(s) according to the IEEE 1394-1995, IEEE 1394a-2000, and IEEE 1394b standards (commonly known as “FireWire”), or any combination thereof. Wired network interface 306 is able to use wired connections 108 and 110.
[0047] Radio 302 and processor 304 may be part of the same integrated circuit or in separate integrated circuits. Similarly, processor 304 and wired network controller 308 may be part of the same integrated circuit or in separate integrated circuits.
[0048] AP 102 also includes a memory 310, which may be fixed in or removable from AP 102. Memory 310 may be coupled to processor 304 or partly embedded in processor 304. A non-exhaustive list of examples for memory 310 includes any combination of the following:
-
- [0049] a) semiconductor devices such as registers, latches, read only memory (ROM), mask ROM, electrically erasable programmable read only memory devices (EEPROM), flash memory devices, non-volatile random access memory devices (NVRAM), synchronous dynamic random access memory (SDRAM) devices, RAMBUS dynamic random access memory (RDRAM) devices, double data rate (DDR) memory devices, static random access memory (SRAM), universal serial bus (USB) removable memory, and the like;
- [0050] b) optical devices, such as compact disk read only memory (CD ROM), and the like; and
- [0051] c) magnetic devices, such as a hard disk, a floppy disk, a magnetic tape, and the like.
[0052] Processor 304 and wired network controller 308 may be coupled by signals 311 to coordinate their activities, for example access to memory 310.
[0053] Memory 310 may store mappings 312 of MAC addresses of client devices associated with AP 102 to respective IP addresses, and mappings 314 of MAC addresses of client devices associated with AP 102 to respective AIDs. Alternatively, any or all of these mappings may be stored internally in processor 304. For example, cellphone 126 may have AID=1, PDA 130 may have AID=2, PDA 128 may have AID=3, laptop 122 may have AID=4, cellphone 124 may have AID=5, and laptop 120 may have AID=6.
[0054] Memory 310 may also include a buffering system 318 to store incoming traffic destined for client devices. For example, data 320 of incoming traffic may be transferred to buffering system 318 under control signals 322 of wired network controller 308.
[0055] Buffering system 318 already includes buffers to store unicast traffic on a per-client device basis.
[0056] In one embodiment, AP 102 will simply copy the received broadcast or multicast traffic to the buffers of each of the client devices which are to receive the traffic.
[0057] In another embodiment, AP 102 may maintain lists for each associated client device (indexed, for example, by the AID). AP 102 may allocate a buffer upon receipt of broadcast or multicast data and may include a pointer to the allocated buffer (or any other suitable indication of the allocated buffer) in the list for each client device in Power Save mode that is destined to receive the data. Each such allocated buffer is associated with a counter that is set to the total number of client devices in Power Save mode that are destined to receive the broadcast or multicast data. Each time the buffered data is sent to one of the client devices, the counter is decremented. Once the counter is zero, AP 102 is free to deallocate the allocated buffer and discard the buffered data.
[0058] For example, as AP 102 receives ARP request 201 prior to beacon frame 202 (FIG. 2 ), AP 102 may allocate buffer A to store ARP request 201. AP 102 may set a counter 324 associated with buffer A to the value 4, which is the total number of client devices that are currently in Power Save mode. AP 102 will include a pointer to buffer A (or any other suitable indication of buffer A) in the lists for AID 1, 2, 3 and 4 (corresponding to cellphone 126, PDA 130, PDA 128 and laptop 122, respectively, all of which are in Power Save mode).
[0059] Once AP 102 has transmitted ARP request 201 to laptop 122 (following the PS-poll frame sent by laptop 122 in response to beacon frame 202), the pointer to buffer A is removed from the list for AID 4, and counter 324 is decremented by 1.
[0060] Once AP 102 has transmitted ARP request 201 to PDA 130 (following the PS-poll frame sent by PDA 130 in response to beacon frame 206), the pointer to buffer A is removed from the list for AID 2, and counter 324 is decremented by 1.
[0061] Once AP 102 has transmitted ARP request 201 to cellphone 126 (following the PS-poll frame sent by cellphone 126 in response to beacon frame 218) and to PDA 128 (following the PS-poll frame sent by PDA 128 in response to beacon frame 218), the pointer to buffer A is removed from the lists for AID 1 and 3, and counter 324 is decremented by 2.
[0062] Processor 304 may handle the received broadcast or multicast traffic as multiple instances of unicast traffic, where each of the instances is destined for a corresponding wireless client device associated with AP 102, by accessing buffering system 318 through data signals 330 and control signals 332.
[0063] FIG. 4 is a block diagram of an exemplary client device, according to some embodiments of the invention. A wireless client device 400 includes at least one antenna 401 coupled to a radio 402, which in turn is coupled to a processor 404 having baseband functionality. A non-exhaustive list of examples for processor 404 includes a central processing unit (CPU), a digital signal processor (DSP), a reduced instruction set computer (RISC), a complex instruction set computer (CISC) and the like. Furthermore, processor 404 may be part of an application specific integrated circuit (ASIC) or may be a part of an application specific standard product (ASSP). Radio 402 and processor 404 may be part of the same integrated circuit in separate integrated circuits.
[0064] Client device 400 also includes a memory 410, which may be fixed in or removable from client device 400. Memory 410 may be coupled to processor 404 or partly embedded in processor 404. A non-exhaustive list of examples for memory 410 includes any combination of the following:
-
- [0065] a) semiconductor devices such as registers, latches, read only memory (ROM), mask ROM, electrically erasable programmable read only memory devices (EEPROM), flash memory devices, non-volatile random access memory devices (NVRAM), synchronous dynamic random access memory (SDRAM) devices, RAMBUS dynamic random access memory (RDRAM) devices, double data rate (DDR) memory devices, static random access memory (SRAM), universal serial bus (USB) removable memory, and the like;
- [0066] b) optical devices, such as compact disk read only memory (CD ROM), and the like; and
- [0067] c) magnetic devices, such as a hard disk, a floppy disk, a magnetic tape, and the like.
[0068] Processor 404 may access data stored in memory 410 through data signals 430 and control signals 432. Memory 410 may store an indication of its “Listen Interval” parameter. Memory 410 may store a default hard-coded value for the “Listen Interval” parameter. The “Listen Interval” parameter may be configurable by a user of client device 400.
[0069] Processor 404 may adjust the “Listen Interval” parameter according to predefined considerations. A non-exhaustive list of examples for such considerations includes:
-
- [0070] a) a charge level of a battery 420 to power the client device (for example, increasing the preferred DTIM period as the charge level drops):
- [0071] b) an expected usage model for the client device; and
- [0072] c) network parameters (for example, does the gateway remember the IP address—MAC address mapping after receiving a response to an ARP request?).
[0073] Processor 404 may initiate a reassociation request to declare this adjusted “Listen Interval” parameter to AP 102.
[0074] If a client device sets its “Receive DTIMs” parameter to False, then in Power Save mode, the client device will not wake up for DTIMs according to the DTIM period, yet will awaken to listen to TIMs within a period defined by the product of its “Listen Interval” and the beacon interval. If the client device has a “Listen Interval” parameter that is greater than the DTIM period of AP 102, then in this embodiment of the invention, the client device will increase its power-saving potential while retaining the ability to receive broadcast and multicast traffic. This increase in power-saving potential is in comparison to a client device having its “Receive DTIMs” parameter set to True and that is associated with an access point that buffers broadcast or multicast traffic for clients in Power Save mode, indicates the existence of the buffered broadcast or multicast traffic in a DTIM and transmits the buffered broadcast or multicast traffic following the DTIM and that does not handle the broadcast or multicast traffic as multiple instances of unicast traffic.
[0075] In order to make use of some embodiments of the invention, a client device may recognize that an access point with which the device is associated handles received broadcast and multicast traffic as multiple instances of unicast traffic, where the instances are destined for corresponding wireless client devices associated with the access point. The client device may set its “Receive DTIMs” parameter to false when entering Power Save mode.
[0076] The client device may configured manually or automatically to use this behavior. For example, manual configuration may be achieved through an option screen or configuration file of the client device or the like. Automatic configuration may be achieved by pushing the appropriate configuration to the client device, for example, by over-the-air policy management or by connecting the client device to a computer and loading the configuration information via the connection. Automatic configuration may be achieved through communication with the access point. For example, the client device could wait for an ARP to be sent either as a unicast message or as a broadcast message, and then configure its “Receive DTIMs” parameter appropriately on the assumption that the access point will continue to transmit broadcast traffic in the same manner. In another example, the access point could send a particular flag in one of the downlink frames to indicate that it intends to pursue this broadcast-free connection mode. In yet another example, the client device could query the access point regarding its handling of broadcast and multicast traffic.
[0077] While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the spirit of the invention.
Claims
What is claimed is:
1. A method in a wireless local area network access point, the method comprising:
receiving broadcast or multicast traffic; and
generating multiple instances of unicast traffic, where data of said instances is identical to data of said broadcast or multicast traffic and where each of said instances is destined for a corresponding wireless client device associated with said wireless local area network access point;
transmitting any of said instances that is destined for a wireless client device in active mode; and
buffering any of said instances that is destined for a wireless client device in power save mode.
2. The method of claim 1, further comprising:
retaining any of said buffered instances that is destined for a wireless client device in power save mode for a period that is at least as long as a product of a beacon interval of said access point and a listen interval parameter of said wireless client device in power save mode.
3. The method of claim 1, further comprising:
indicating in a traffic indication map the existence of each buffered instance that is destined for a wireless client device in power save mode.
4. The method of claim 3, further comprising:
not indicating in any delivery traffic indication message that said broadcast or multicast traffic has been received, even if one or more of the wireless client devices associated with said access point is in power save mode; and
not transmitting said broadcast or multicast traffic.
5. A method in a wireless client device, the method comprising:
recognizing that a wireless local area network access point with which said device is associated handles received broadcast and multicast traffic by generating multiple instances of unicast traffic, where data of said instances is identical to data of said broadcast and multicast traffic and where said instances are destined for corresponding wireless client devices associated with said wireless local area network access point; and
setting a “Receive DTIMs” parameter in said device to false when entering power save mode while still associated with said wireless local area network access point.
6. A wireless local area network access point comprising:
a wireless local area network controller able to receive broadcast or multicast traffic;
a memory; and
a processor coupled to said wireless local area network controller and to said memory, said processor able to generate multiple instances of unicast traffic, where data of said instances is identical to data of said broadcast or multicast traffic and where each of said instances is destined for a corresponding wireless client device associate with said access point, and where said processor is able to control said network controller to transmit any of said instances that is destined for a wireless client device in active mode, and where said processor is able to buffer in said memory any of said instances that is destined for a wireless client device in power save mode.
7. The wireless local area network access point of claim 6, wherein said access point is to retain any of said buffered instances that is destined for a wireless client device in power save mode for a period that is at least as long as a product of a beacon interval and a listen interval parameter of said wireless client device in power save mode.
8. The wireless local area network access point of claim 6, wherein said wireless local area network access point uses an IEEE 802.11 wireless local area network standard.
9. The wireless local area network access point of claim 6, wherein said wireless local area network access point is to indicate in a traffic indication map the existence of each buffered instance that is destined for a wireless client device in power save mode.
10. The wireless local area network access point of claim 6, wherein said wireless local area network access point is not to indicate in any delivery traffic indication message that said broadcast or multicast traffic has been received, even if one or more of the wireless client devices associated with said wireless local area network access point is in power save mode, and wherein said wireless local area network access point is not to transmit said broadcast or multicast traffic.
Patent Citations (65)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4707832(A) | 1987-11-01 | Glenn et al. | Examiner |
| US5991287(A) | 1999-11-01 | Diepstraten et al. | Examiner |
| US6067297(A) | 2000-05-01 | Beach et al. | Applicant |
| US6125369(A) | 2000-09-01 | Wu et al. | Applicant |
| US6192230(B1) | 2001-02-01 | van Bokhorst et al. | Examiner |
| US6370121(B1) | 2002-04-01 | Hausman | Examiner |
| US6438117(B1) | 2002-08-01 | Grilli et al. | Examiner |
| US6507349(B1) | 2003-01-01 | Balassanian | Applicant |
| US6574708(B2) | 2003-06-01 | Hayter et al. | Applicant |
| US6633924(B1) | 2003-10-01 | Wu et al. | Applicant |
| US6674738(B1) | 2004-01-01 | Yildiz et al. | Examiner |
| US6697415(B1) | 2004-02-01 | Mahany | Examiner |
| US6795409(B1) | 2004-09-01 | Youssefmir et al. | Examiner |
| US6842460(B1) | 2005-01-01 | Olkkonen et al. | Examiner |
| US6856603(B1) | 2005-02-01 | Vollmer et al. | Examiner |
| US6934870(B1) | 2005-08-01 | Amos | Examiner |
| US6952181(B2) | 2005-10-01 | Karr et al. | Examiner |
| US6982968(B1) | 2006-01-01 | Barratt et al. | Examiner |
| US6999769(B1) | 2006-02-01 | Henon | Applicant |
| US7043259(B1) | 2006-05-01 | Trott | Examiner |
| US7062294(B1) | 2006-06-01 | Rogard et al. | Examiner |
| US7120138(B2) | 2006-10-01 | Soomro et al. | Examiner |
| US7123253(B2) | 2006-10-01 | Stoll et al. | Applicant |
| US7126926(B1) | 2006-10-01 | Bjorklund et al. | Examiner |
| US7126945(B2) | 2006-10-01 | Beach | Applicant |
| US7142535(B2) | 2006-11-01 | Kubler et al. | Examiner |
| US7167713(B2) | 2007-01-01 | Anderson | Examiner |
| US7181190(B2) | 2007-02-01 | Abhishek et al. | Examiner |
| US7206594(B2) | 2007-04-01 | Shostak | Examiner |
| US7212832(B2) | 2007-05-01 | Yokota | Examiner |
| US7224970(B2) | 2007-05-01 | Smith et al. | Examiner |
| US7236470(B1) | 2007-06-01 | Bims | Applicant |
| US7236787(B1) | 2007-06-01 | Tamura et al. | Examiner |
| US7274929(B1) | 2007-09-01 | Banginwar | Applicant |
| US7359738(B2) | 2008-04-01 | Daniels et al. | Applicant |
| US7382757(B2) | 2008-06-01 | LoGalbo et al. | Examiner |
| US7420942(B2) | 2008-09-01 | Wang | Applicant |
| US7433669(B2) | 2008-10-01 | Rue | Examiner |
| US2002/0063472(A1) | 2002-05-01 | Irvin | Applicant |
| US2003/0174645(A1) | 2003-09-01 | Paratainen et al. | Applicant |
| US2003/0224840(A1) | 2003-12-01 | Frank et al. | Applicant |
| US2004/0013128(A1) | 2004-01-01 | Moreton et al. | Applicant |
| US2004/0072559(A1) | 2004-04-01 | Kakumaru et al. | Applicant |
| US2004/0103282(A1) | 2004-05-01 | Meier et al. | Applicant |
| US2004/0151149(A1) | 2004-08-01 | Song et al. | Applicant |
| US2004/0242258(A1) | 2004-12-01 | Kim | Applicant |
| US2005/0002395(A1) | 2005-01-01 | Kondo | Applicant |
| US2005/0009512(A1) | 2005-01-01 | Rue | Examiner |
| US2005/0020209(A1) | 2005-01-01 | Camp, Jr. | Applicant |
| US2005/0122936(A1) | 2005-06-01 | Son et al. | Examiner |
| US2005/0124294(A1) | 2005-06-01 | Wentink | Applicant |
| US2005/0128988(A1) | 2005-06-01 | Simpson et al. | Applicant |
| US2005/0147073(A1) | 2005-07-01 | Hietalahti et al. | Applicant |
| US2005/0201341(A1) | 2005-09-01 | Griswold | Applicant |
| US2005/0243737(A1) | 2005-11-01 | Dooley et al. | Applicant |
| US2005/0276237(A1) | 2005-12-01 | Segal et al. | Applicant |
| US2006/0098647(A1) | 2006-05-01 | Muehl et al. | Examiner |
| US2006/0142004(A1) | 2006-06-01 | He et al. | Applicant |
| EP615364(A) | 1994-09-01 | Applicant | |
| EP907262(A) | 1999-04-01 | Applicant | |
| EP1206070 | 2002-05-01 | Applicant | |
| EP1237334 | 2002-09-01 | Applicant | |
| EP1311086(A) | 2003-05-01 | Applicant | |
| EP1564930 | 2005-08-01 | Applicant | |
| EP1670179 | 2007-11-01 | Applicant |
Non-Patent Literature (33)
- “IEEE Standard Part 11: wireless LAN medium access control (MAC) and physical layer (PHY) specification. (ISO/IEC 8820-11, ANSI/IEEE Std 802. Nov. 1999) Chapter 11: MAC sublayer management entity” ISO/IEC 8802-11 ANSI/IEEE STD 802.11, Aug. 20, 1999, pp. 123-137, XP002207975.Applicant
- Eun-Sun Jung et al. “An energy efficient MAC protocol for Wireless LANs” Proceedings IEEE INFOCOM 2002. The Conference on Computer Communications. 21st Annual Joint Conference of the IEEE Computer and Communications Societies. New York, NY, Jun. 23-27, 2002.Applicant
- El Hoiydi A et al. “Lower Power MAC Protocols for Infrastructure Wireless Sensor Networks” Proceedings of the European Wireless, Feb. 24, 2004, pp. 1-8, XP002320821.Applicant
- “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 1: Basic Data Transport Functions”, ESTI TS 101 761-1 V1.3.1 Dec. 2001.Applicant
- “ETSI TS 101 761-2 V1.3.1 (200-01)”, chapter 5.2.6 ETSI: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 2: Radio Link Control (RLC) sublayer” Jan. 2002, 1-13, 92-97.Applicant
- “IEEE 802.11 1999 (R2003) pp. 401 407”, 1999 (revised 2003), 471-474.Applicant
- “IEEE 802.11 1999 (R2003) select pp. 1 to 137”, 7.2.3.1, 7.2.3.4, 7.2.3.6, 7.3.1.6, 7.3.2.6, 10.3.1.1, 10.3.2.2, 10.3.6.1, 10.3.7.1, 10.3.10.1 11.2.1 1999 (Revised 2003) , 1-8, 34-58, 98-137.Applicant
- “IEEE 802.11b-1999 p. 89”, 1999, 89.Applicant
- “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Higher-Speed Physical Layer Extension in the 2.4 GHz Band”, IEEE Tsd 802.11b-1999 2000.Applicant
- First Examination Report for EP 05108981.1, Nov. 25, 2005.Applicant
- Arevalo, Joseph , First Office Action for U.S. Appl. No. 11/041,124; Jul. 20, 2007.Applicant
- Arevalo, Joseph , Third Office Action for U.S. Appl. No. 11/041,124; Aug. 4, 2008.Applicant
- Arevalo, Joseph , Second Office Action for U.S. Appl. No. 11/041,124; Mar. 25, 2008.Applicant
- Choi, Nakjung et al., “Unicast-Friendly Multicast in IEEE 802.11 Wireless LANs”, Nakjung Choi, Jiho Ryu, Yongho Seok, Yanghee Choi, and Taekyoung Kwon, “Unicast-Friendly Multicast in IEEE 802.11 Wireless LANs,” IEEE CCNC 2006, Las Vegas, USA, Jan. 2006.Applicant
- Isopescu, C , Exam Report for EP 04106427, Aug. 28, 2006.Applicant
- Isopescu, C , “EESR”, Extended European Search Report for EP 04106427, May 25, 2005.Applicant
- Matar, G. , First Office Action for CA 2528376, Jun. 18, 2008.Applicant
- Mian, Ali , First Office Action for CA 2531384, Jun. 13, 2008.Applicant
- Muller, N , Examination Report for EP 05108981.1, Aug. 25, 2006.Applicant
- Rosken, Wilfried , Examination Report for EP 05100367.1, Oct. 4, 2006.Applicant
- Rosken, W , “EESR”, Extended European Search Report for EP 05100367.1, Jul. 5, 2005.Applicant
- Santande, Mohammadian , Second Examination Report for EP 05108981.1, Apr. 4, 2006.Applicant
- Santande, Mohammadian , “EESR”, Extended European Search Report for EP 05100368.9, Aug. 22, 2005.Applicant
- Santande, Mohammadian , “Search Report”, European Search Report for EP 05108981.1, Nov. 4, 2005.Applicant
- Sefcheck, Gregory B. , Notice of Allowance for U.S. Appl. No. 11/008,023, May 7, 2008.Applicant
- Sefcheck, Gregory B. , First Office Action for U.S. Appl. No. 11/008,023, Sep. 14, 2007.Applicant
- Yanxin, Li , First Office Action with translation for CN 2005100229007, Jul. 20, 2007.Applicant
- Zhang, Yu , First Office Action with translation for CN 2005101381232, Jan. 4, 2008.Applicant
- Zhang, Yu , First Office Action with translation for CN 2005100487901, Jan. 4, 2008.Applicant
- Rosken, Wilfried , “EESR”, Extended European Search Report for EP07124188.9, Feb. 19, 2008.Applicant
- Arevalo, Joseph , Final Office Action for U.S. Appl. No. 11/041,124, Jan. 7, 2009.Applicant
- Rosken, Wilfried , Examination Report for EP 07124188.9, Nov. 26, 2008.Applicant
- Arevalo, Joseph , non-final Office Action for U.S. Appl. No. 11/041,124, May 14, 2009.Applicant