This invention relates to wireless communication systems and, in particular, to new types of a Network Allocation Vector (NAV) to protect wireless transmissions from interfering by deferring other devices.
In some communications systems, a Network Allocation Vector (NAV) is used to protect wireless transmissions from interfering by preventing other devices from transmitting when another device is transmitting.
For example, in the IEEE 802.11 standard, a NAV is a single value indicating a single time period. For example, it can indicate a number of micro-seconds. The NAV is set according to the duration and ID field provided in polling messages or request-to-send or clear-to-send (RTS/CTS) frames. These polling messages or RTS/CTS frames are sent before transmission of data frames that are to be protected. Each device on the network receives this information for data to be transmitted. The ID field indicates which device is the intended recipient device of the data. Devices, other than the one which has the indicated ID, then set the NAV for the duration of the frame plus some subsequent time for acknowledgements and inter-frame time. The NAV settings indicate to these devices a time period to defer transmissions. Therefore, only one device will transmit data at a time. Accordingly, the transmission between the targeted devices is protected.
Using the current NAV setting in IEEE 802.11, the transmission of the beacons and other isochronous or periodic traffic can not be guaranteed as only one time block is protected even though there are multiple data blocks to be sent at periodic time intervals. Typically, Access Point (AP) and Quality of Service (QoS) devices such as audio/video (AV) devices are given higher priorities to transmit in a network. When there are multiple APs or high priority devices present, however, the contention can delay the desired transmission resulting in degraded quality of services. Further, in the current 802.11 NAV setting, there is no way to schedule such transmission of multiple devices for multiple time periods.
The system, method, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this invention as expressed by the claims which follow, its more prominent features will now be discussed briefly.
In one embodiment, there is a method of reserving bandwidth for disjoint time intervals in a wireless network, the method comprising transmitting a first control packet comprising parameters for a disjoint network allocation vector (NAV), the parameters indicative of a plurality of disjoint time blocks during which transmissions by one or more other devices in the wireless network are to be deferred.
In another embodiment there is a method of reserving bandwidth for disjoint time intervals in a wireless network, the method comprising receiving a control packet comprising parameters for a disjoint network allocation vector (NAV), the parameters indicative of a target device and a plurality of disjoint time blocks during which transmissions by one or more devices other than the target device are to be deferred; determining that a receiving device is not the target device; setting the disjoint NAV vector; and deferring transmissions of data packets during one or more of the plurality of disjoint time blocks.
In another embodiment there is a method of reserving bandwidth for disjoint time intervals in a wireless network, the method comprising receiving a first control packet comprising parameters for a disjoint network allocation vector (NAV), the parameters indicative of a target device and a plurality of disjoint time blocks during which transmissions by one or more devices other than the target device are to be deferred; determining that a receiving device is the target device; and receiving data packets during one or more of the plurality of the disjoint time blocks.
In another embodiment there is a system for reserving bandwidth for disjoint time intervals in a wireless network, the system comprising a processor configured to generate a control packet comprising parameters for a disjoint network allocation vector (NAV), the parameters indicative of a plurality of disjoint time blocks during which transmissions by one or more other devices in the wireless network are to be deferred.
In another embodiment there is a system for reserving bandwidth for disjoint time intervals in a wireless network, the system comprising a processor configured to receive a control packet comprising parameters for a disjoint network allocation vector (NAV), the parameters indicative of a target device and a plurality of disjoint time blocks during which transmissions by one or more devices other than the target device are to be deferred; determine if a receiving device is the target device; set the disjoint NAV vector if the receiving device is not the target device; defer transmissions of data packets during one or more of the plurality of disjoint time blocks if the disjoint NAV vector is set; and receive data packets during one or more of the plurality of the disjoint time blocks if the receiving device is the target device.
Disclosed herein is a system and method for reserving wireless medium for disjoint time intervals using new types of Network Allocation Vectors (NAV). This new NAV setting scheme can protect isochronous (e.g., periodic) transmissions, such as regular beacon transmissions and AV transmissions, to enhance Quality of Service (QoS). This new NAV setting can also protect non-periodic transmissions. A new NAV setting is used to reserve time blocks for disjoint transmissions. In one embodiment, periodic traffic is protected by disjoint NAV settings. In an exemplary embodiment, non-periodic traffic is protected for multiple time periods by disjoint NAV settings. In some embodiments, constraints on a duration, period and number of reservations are introduced. In an exemplary embodiment, disjoint NAV settings are used to protect transmission in a wireless local area network (WLAN). In some embodiments, the disjoint NAV settings are transmitted over the network or channel in a RTS and/or CTS message or polling message. In other embodiments, the disjoint NAV may be transmitted in a control packet.
Exemplary implementations of embodiments of a WLAN will now be described.
In certain embodiments, the access point 101 includes a receiver of wireless signals, and the wireless station 103 includes a sender of the wireless signals. In other embodiments, the access point 101 includes a sender of wireless signals, and the wireless station 103 includes a receiver of the wireless signals. In some of such embodiments, the wireless signals include audio content. In other embodiments, the wireless signals include video content. In yet another embodiment, the wireless signals include text content such as a publication. The access point 101 can be a sink of video and/or audio data implemented, such as, in a high definition television (HDTV) set in a home wireless network environment. The wireless station 103 can be a source of compressed or uncompressed video or audio. Examples of the wireless station 103 include a desktop computer, a laptop computer, a set-top box, a DVD player or recorder, a digital camera, a camcorder, and so forth. In some embodiments, the content can be protected content.
It should be noted, that while the network has been described above including certain features, the network may include fewer or additional features. For example, the WLAN configuration 100 may include fewer or more wireless stations 103 and fewer or more AP 101. Further, some stations 103 may be wired to an AP 101. Some stations 103 may be associated with multiple APs 101. The WLAN may operate in a frequency from about 2.4 GHz to about 60 GHz. Further the network may not include a backbone 105 (e.g., mesh network) or may include multiple backbones 105.
The upper layers 210, 218 represent one or more layers that are above the MAC layers 208, 216, respectively, and send command and/or data messages to the MAC layers. In certain embodiments (e.g., OSI or TCP/IP models), the upper layer 210, 218 includes a network layer. In certain embodiments, the network layer includes an IP protocol that performs the basic task of getting data packets from source to destination. In other embodiments (e.g., five-layer TCP/IP model), the upper layer 210, 218 further includes a transport layer and an application layer. In other embodiments, (e.g., seven-layer OSI model), the upper layer 210, 218, in addition to the transport layer and the application layer, further includes a session layer and a presentation layer.
In the wireless transmitter 202, the upper layer 210 provides data (e.g., text, graphics, or audio data) and/or command messages to the MAC layer 208. In certain embodiments, the MAC layer 208 can include a packetization module (not shown) which puts the data and/or command messages into the form of one or more data packets. The MAC layer 208 then passes the data packets to the PHY layer 206. The PHY/MAC layers of the transmitter 202 add PHY and MAC headers to the data packets. The PHY layer 206 transmits wireless signals including the data packets to the receiver 204 via the RF module 207 over the wireless channel 201.
In the wireless receiver 204, the PHY layer 214 receives the transmitted wireless signals including the data packets via the RF module 217. The PHY/MAC layers 214, 216 then process the received data packets to extract one or more data/command messages. The extracted data/command messages are passed to the upper layer 210 where the messages are further processed and/or transferred to other modules or devices to be displayed (text or graphics) or played (audio), for example.
It should be noted though the transmitter 202 and receiver 204 have been described above in one embodiment, other embodiments may include additional or fewer features. For example the receiver 204 and/or transmitter 202 may include additional or fewer layers. Further, the antenna may be associated with a different layer than shown. In other embodiments, some layers may be integrated with each other. In yet other embodiments, the transmitter 202 and or receiver 204 may not include an antenna.
I. Disjoint NAV
In certain embodiments, the disjoint NAV can define periodic time blocks 411 of an exemplary embodiment of a timeline 400 as shown in
In one exemplary embodiment, the time duration is the duration of time of a transmission between two devices (e.g., a transmitter and a target receiver). In some embodiments, the interval time is the time between the start of consecutive time blocks. In some embodiments, the number of occurrences is the number of time blocks included in this NAV.
It should be noted that other embodiments of disjoint NAV may include additional or fewer parameters than those described above.
II. Constraints on Disjoint NAV
In an exemplary embodiment, constraints can be placed on an AV NAV. In certain embodiments, such constraints can include:
T_min<Time Duration<T_max;
Iv_min<Interval Time<Iv_max;
Number of occurrences<N; and
Duty cycle=Time Duration/Interval Time<D.
In such embodiments, the Time Duration reserved for transmission is set within a range of T_min and T_max; the Interval Time is in the range of Iv_min and Iv_max; the number of occurrences is less than N; and the duty cycle, the fraction of the time duration to the interval time, is less than D.
In some embodiments, constraints can be associated with the priority of a device or its load of traffic. For example, in an exemplary embodiment, only an access point (AP) of the wireless network is allowed to set disjoint NAV and/or only AV devices are allowed to set AV NAV. In one embodiment, these constraints prevent devices from reserving the network or channel for too long and/or too frequently. Further, these constraints can be adjusted for different applications. For example, in a network with three devices, the duty cycle may be set such that D=⅓. In this example, one device cannot occupy the channel for longer than ⅓ of the total transmission time, thereby guaranteeing availability of equal amounts of transmission time for each device.
It should be noted that in some embodiments, additional or fewer constraints may be placed on the parameters of a disjoint NAV than described above.
III. Beacon Protection
In some embodiments, the disjoint NAV can be used to protect isochronous or periodic transmissions of beacons by providing the disjoint NAV in a first RTS message 511 and/or a first CTS message 512 of an exemplary embodiment of a timeline 500 as shown in
IV. Setting the AV NAV for Isochronous Traffic
As shown in an exemplary embodiment of a timeline 600 in
In an exemplary embodiment, devices can scan traffic on the network or channel for a time T before starting a new transmission. In this embodiment, the devices can detect an RTS/CTS message indicative of existing isochronous traffic and set the NAV before transmitting so that the device does not make new transmissions that may interfere with the existing transmissions. This may guarantee QoS. In some embodiments, the time period of one transmission for a device is limited to a time period T. In this embodiment, the scanning time period and the maximum single transmission time period are the same, so if there is existing protected periodic traffic on the network or channel, at least one RTS/CTS will be transmitted during the scanning period T.
V. Combination of Disjoint NAV and AV NAV
In certain embodiments, both general (e.g., non-periodic) disjoint NAV and AV NAV can be combined into and transmitted as a single disjoint NAV vector. As shown in an exemplary embodiment of a timeline 700 in
VI. Transmitter
If the channel is determined to be not idle (e.g. there is existing traffic and/or there is no available time slot), the process 800 loops back to the state 820, where the channel is again scanned for existing traffic. If the channel is determined to be idle, the process 800 proceeds to a state 840, where the transmitter transmits a RTS message that includes parameters for a disjoint NAV and an ID for a target device or receiver. The parameters define or specify a plurality of disjoint time blocks during which transmissions by devices other than a target device are to be deferred. For general (e.g., non-periodic) disjoint NAVs, examples of which are shown in
The process 800 proceeds to a decision state 850, where the transmitter determines whether a CTS message is received from the target device or receiver. If the transmitter determines that it has not received the CTS message, the process 800 loops back to the state 820, where the channel is again scanned for existing traffic. If the transmitter determines that it has received the CTS message, the process 800 proceeds to a state 860, where the transmitter transmits a packet, e.g., another RTS message or other data, at a reserved time block. The process 800 then proceeds to a decision state 870, where the transmitter determines whether there is another packet to transmit. If there is no other packet to transmit, the process 800 ends at end state 890. If there is another packet to transmit, the process 800 proceeds to a decision state 880, where the transmitter determines whether there is another time block reserved for the additional packet. If the answer is no (no reserved time block), the process 800 loops back to the state 820, where the channel is again scanned for existing traffic. If the answer is yes (reserved time block), the process 800 loops back to the state 840, where the transmitter transmits another RTS, thereby alerting non-target devices. In some embodiments, the RTS includes additional NAV parameters for reserving time blocks. In one such embodiment, the RTS includes the same NAV parameters as sent previously. In another embodiment, the RTS includes no NAV parameters. The states 840, 850 and 860 for transmitting packets during reserved disjoint time blocks are repeated until it is determined that all packets have been sent during reserved time blocks at the decision states 870 and 880. When all packets have been sent, the process 800 ends at state 890.
If the channel is determined to be not idle (e.g. there is existing traffic and/or there is no available time slot), the process 900 loops back to the state 920, where the channel is again scanned for existing traffic. If the channel is determined to be idle, the process 900 proceeds to a state 940, where the transmitter transmits an RTS message that includes parameters for a disjoint NAV and an ID for a target device or receiver. The parameters define or specify a plurality of disjoint time blocks during which transmissions by devices other than a target device are to be deferred. For general (e.g., non-periodic) disjoint NAVs, examples of which are shown in
The process 900 proceeds to a decision state 950, where the transmitter determines whether a CTS message is received from the target device or receiver. If the transmitter determines that it has not received the CTS message, the process 900 loops back to the state 920, where the channel is again scanned for existing traffic. If the transmitter determines that it has received the CTS message, the process 900 proceeds to a state 960, where the transmitter transmits a packet, e.g., another RTS message or other data, at a reserved time block. The process 900 then proceeds to a decision state 970, where the transmitter determines whether there is another packet to transmit. If there is no other packet to transmit, the process 900 ends at end state 990. If there is another packet to transmit, the process 900 proceeds to a decision state 980, where the transmitter determines whether there is another time block reserved for the additional packet. If the answer is no (no reserved time block), the process 900 loops back to the state 920, where the channel is again scanned for existing traffic. If the answer is yes (reserved time block), the process 900 loops back to the state 960 to transmit another data packet. The state 960 for transmitting packets during reserved disjoint time blocks is repeated until it is determined that all packets have been sent during reserved time blocks at the decision states 970 and 980. When all packets have been sent, the process 900 ends at state 990.
VII. Receiver
If it is determined that the receiver did not receive the RTS/CTS message indicative of a disjoint NAV at the state 1010, the process 1000 proceeds to a decision state 1060, where it is queried whether one or more additional RTS/CTS messages indicative of the disjoint NAV are skipped or not received for K consecutive time periods or time intervals (e.g., superframes), for a preset time period, or before another scheduled event (e.g., a next reserved disjoint time block). If the answer is yes, the process 1000 proceeds to a state 1080, where the receiver's NAV reservations are cleared, and, the process 1000 ends at state 1090. If the answer at decision state 1060 is no, the process 1000 proceeds to a decision state 1070, where it is queried whether the NAV for the receiver is empty (e.g., not set). If yes (the NAV is empty), the process 1000 ends at the state 1090. If the answer to the query at the state 1070 is no (the NAV is not empty), the process 1000 loops back to the state 1010 where it is determined if another RTS/CTS message indicative of the disjoint NAV is received. On the other hand, if it is determined at the state 1010 that the receiver has received an RTS/CTS message indicative of a disjoint NAV, the process 1000 proceeds to a decision state 1020, where the receiver determines whether it is the target receiver, e.g., by comparing its own ID with the ID for a target included in the RTS/CTS message. It should be noted that in some embodiments, states 1060, 1070, and 1080 are omitted. For example, such embodiments may be used for a receiver corresponding to a transmitter implementing process 900 of
A. Non-Target Receiver
If the receiver determines that it is not the target receiver at the decision state 1020 (e.g., its ID does not match with the ID for a target), the process 1000 proceeds to a state 1030, where the receiver sets its NAV vector with the parameters received via the RTS/CTS message at the state 1010. The process 1000 then proceeds to a state 1050. In one exemplary embodiment of process 1000, such as one without states 1060, 1070, and 1080 of
B. Target Receiver
If the receiver determines that it is the target receiver at the decision state 1020 (e.g., its ID matches with the ID for a target), the process 1000 proceeds to a state 1040, where the target receiver transmits a CTS message indicative of the disjoint NAV to the transmitter. In some embodiments, the CTS message indicative of the disjoint NAV includes all or part of the parameters for the disjoint NAV that the receiver receives via the RTS/CTS message at the state 1010. In other embodiment, the CTS message includes no disjoint NAV parameters. The process 1000 then proceeds to a state 1055. In one exemplary embodiment of process 1000, such as one without states 1060, 1070, and 1080 of
While the above processes 800, 900, and 1000 are described in the detailed description as including certain steps and states and are described in a particular order, it should be recognized that these processes may include additional steps or may omit some of the steps described. Further, each of the steps of the processes does not necessarily need to be performed in the order it is described.
Various media reservation schemes based on disjoint NAV scheme disclosed herein enables various features including, but not limited to:
Protecting disjoint transmissions from interference;
Protecting beacon transmissions from drifting;
Ensuring Quality of Service of AV traffic; and
Providing fairness constraints.
Conclusion
The aforementioned example embodiments described above can be implemented in many ways, such as program instructions for execution by a processor, as logic circuits, as an application specific integrated circuit, as firmware, etc. For example, the physical (PHY) layer 206, the media access control (MAC) layer 208, and/or the upper layer 210 can be implemented as one or more software or firmware applications, computer-implemented methods, program products stored on a computer useable medium, for execution on one or more processors (e.g., CPU, microcontroller) or other computing devices in a wireless station.
While the above detailed description has shown, described, and pointed out the fundamental novel features of the invention as applied to various embodiments, it will be understood that various omissions and substitutions and changes in the form and details of the system illustrated may be made by those skilled in the art, without departing from the intent of the invention.
This application claims the benefit of U.S. Provisional Application No. 61/077,820, filed on Jul. 2, 2008, which is incorporated herein by reference in its entirety. This application is related to a copending application entitled SYSTEM AND METHOD FOR BANDWIDTH RESERVATION PROTOCOL FOR SPATIAL REUSE IN A WIRELESS COMMUNICATION NETWORK, U.S. application Ser. No. 12/179,457 which has been filed on Jul. 24, 2008, and also to a copending application entitled SYSTEM AND METHOD FOR RANDOM ACCESS SCHEME IN A WIRELESS AD-HOC NETWORK, U.S. application Ser. No. 12/172,858 which has been filed on Jul. 14, 2008, the entire disclosures of which applications are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5615212 | Ruszczyk et al. | Mar 1997 | A |
5886993 | Ruszczyk et al. | Mar 1999 | A |
6198728 | Hulyalkar et al. | Mar 2001 | B1 |
6795421 | Heinonen et al. | Sep 2004 | B1 |
6807158 | Krishnamurthy et al. | Oct 2004 | B2 |
6813277 | Edmon et al. | Nov 2004 | B2 |
6868072 | Lin et al. | Mar 2005 | B1 |
6925064 | Hester et al. | Aug 2005 | B2 |
7088702 | Shvodian | Aug 2006 | B2 |
7127254 | Shvodian et al. | Oct 2006 | B2 |
7184767 | Gandolfo | Feb 2007 | B2 |
7197025 | Chuah | Mar 2007 | B2 |
7251235 | Wentink | Jul 2007 | B2 |
7280518 | Montano et al. | Oct 2007 | B2 |
7280801 | Dahl | Oct 2007 | B2 |
7339916 | Kwon et al. | Mar 2008 | B2 |
7356341 | Nanda | Apr 2008 | B2 |
7359398 | Sugaya | Apr 2008 | B2 |
7385943 | Niddam | Jun 2008 | B2 |
7388833 | Yuan et al. | Jun 2008 | B2 |
7400899 | Shin et al. | Jul 2008 | B2 |
7447180 | Jeong et al. | Nov 2008 | B2 |
7474686 | Ho | Jan 2009 | B2 |
7480266 | Murty et al. | Jan 2009 | B2 |
7486650 | Trainin | Feb 2009 | B2 |
7539930 | Ginzburg et al. | May 2009 | B2 |
7545771 | Wentink et al. | Jun 2009 | B2 |
7561510 | Imamura et al. | Jul 2009 | B2 |
7570656 | Raphaeli et al. | Aug 2009 | B2 |
7590078 | Nanda | Sep 2009 | B2 |
7623542 | Yonge et al. | Nov 2009 | B2 |
7634275 | Odman | Dec 2009 | B2 |
7664132 | Benveniste | Feb 2010 | B2 |
7680150 | Liu et al. | Mar 2010 | B2 |
7787487 | Liu | Aug 2010 | B2 |
7860054 | Benveniste | Dec 2010 | B2 |
7881340 | Farrag et al. | Feb 2011 | B2 |
7924805 | Nishibayashi et al. | Apr 2011 | B2 |
7974261 | Lane et al. | Jul 2011 | B2 |
8072961 | Takano | Dec 2011 | B2 |
8089946 | Broomer | Jan 2012 | B2 |
8179867 | Seok | May 2012 | B2 |
8194626 | Moorti et al. | Jun 2012 | B2 |
8437317 | Jang et al. | May 2013 | B2 |
8532221 | Liu et al. | Sep 2013 | B2 |
20030003905 | Shvodian | Jan 2003 | A1 |
20030137970 | Odman | Jul 2003 | A1 |
20030137993 | Odman | Jul 2003 | A1 |
20030152059 | Odman | Aug 2003 | A1 |
20030214967 | Heberling | Nov 2003 | A1 |
20040047319 | Elg | Mar 2004 | A1 |
20040053621 | Sugaya | Mar 2004 | A1 |
20040199686 | Karaoguz | Oct 2004 | A1 |
20040203474 | Miller et al. | Oct 2004 | A1 |
20040214571 | Hong | Oct 2004 | A1 |
20040218683 | Batra et al. | Nov 2004 | A1 |
20040264475 | Kowalski | Dec 2004 | A1 |
20050058151 | Yeh | Mar 2005 | A1 |
20050130634 | Godfrey | Jun 2005 | A1 |
20050135318 | Walton et al. | Jun 2005 | A1 |
20050232275 | Stephens | Oct 2005 | A1 |
20060002428 | Trainin | Jan 2006 | A1 |
20060050742 | Grandhi et al. | Mar 2006 | A1 |
20060166683 | Sharma et al. | Jul 2006 | A1 |
20060176908 | Kwon et al. | Aug 2006 | A1 |
20060193279 | Gu et al. | Aug 2006 | A1 |
20060268800 | Sugaya et al. | Nov 2006 | A1 |
20060285516 | Li et al. | Dec 2006 | A1 |
20070116035 | Shao et al. | May 2007 | A1 |
20070160009 | Joshi | Jul 2007 | A1 |
20070280180 | Dalmases et al. | Dec 2007 | A1 |
20080159208 | Kloker et al. | Jul 2008 | A1 |
20080279204 | Pratt, Jr. et al. | Nov 2008 | A1 |
20080291873 | Benveniste | Nov 2008 | A1 |
20090052389 | Qin et al. | Feb 2009 | A1 |
20090086706 | Huang et al. | Apr 2009 | A1 |
20090092086 | Lee et al. | Apr 2009 | A1 |
20090275292 | Chang | Nov 2009 | A1 |
20090285163 | Zhang et al. | Nov 2009 | A1 |
20090323611 | Singh et al. | Dec 2009 | A1 |
20100046453 | Jones, IV et al. | Feb 2010 | A1 |
20100046518 | Takagi et al. | Feb 2010 | A1 |
20100220601 | Vermani et al. | Sep 2010 | A1 |
20100310003 | Lauer et al. | Dec 2010 | A1 |
20110002319 | Husen et al. | Jan 2011 | A1 |
20110064013 | Liu et al. | Mar 2011 | A1 |
20110090855 | Kim | Apr 2011 | A1 |
20110176627 | Wu et al. | Jul 2011 | A1 |
20110235513 | Ali | Sep 2011 | A1 |
20110255618 | Zhu et al. | Oct 2011 | A1 |
20110317630 | Zhu et al. | Dec 2011 | A1 |
20120008490 | Zhu | Jan 2012 | A1 |
20120082200 | Verikoukis et al. | Apr 2012 | A1 |
20120087358 | Zhu et al. | Apr 2012 | A1 |
20120140615 | Gong | Jun 2012 | A1 |
20120218947 | Merlin et al. | Aug 2012 | A1 |
20120314694 | Hsieh | Dec 2012 | A1 |
20140010144 | Liu et al. | Jan 2014 | A1 |
Entry |
---|
Harada, Hiroshi, Unified and flexible millimeter wave WPAN systems supported by common mode. IEEE 802.15-07-0761-10-003c, Slides 1-62, Sep. 2007. |
IEEE 802.16e™'—2005, Standard for Local and Metropolitan Area Networks—Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems; Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands and Corrigendum 1;—Feb. 28, 2006, pp. 1-864. |
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—2007 (Revision of IEEE Std 802.-1999), IEEE Computer Society, 1232 pages, (Jun. 12, 2007). |
IEEE P802.11e/D13.0, “Amendment: Medium Access Control (MAC) Quality of Service (QoS) Enhancements,” Jan. 2005, pp. 1-198. |
IEEE Wireless LAN Edition (2003), A compilation based on IEEE Std. 802.11TM-1999 (R 2003) and its Amendments. |
International Search Report dated Jan. 9, 2009 for Application No. PCT/KR08/004793, filed Aug. 19, 2008. |
Kim et al., QoS enhancement scheme of EDCF in IEEE 802.11e wireless LANs, Electronics Letters 40(17): 1091-1092, Aug. 19, 2004. |
Mujtaba et al., TGn Sync Proposal Technical Specification, IEEE 802.11-04-08 89r7, Jul. 2005. |
U.S. Office Action dated Aug. 21, 2007 in U.S. Appl. No. 11/044,600, filed Jan. 26, 2005. |
U.S. Office Action dated Aug. 7, 2008 in U.S. Appl. No. 11/044,600, filed Jan. 26, 2005. |
U.S. Office Action dated Jan. 15, 2008 in U.S. Appl. No. 11/044,600, filed Jan. 26, 2005. |
U.S. Office Action dated Jan. 25, 2007 in U.S. Appl. No. 11/044,600, filed Jan. 26, 2005. |
U.S. Office Action dated Jun. 27, 2006 in U.S. Appl. No. 11/044,600, filed Jan. 26, 2005. |
U.S. Office Action dated Jun. 9, 2009 in U.S. Appl. No. 11/589,519, filed Oct. 30, 2006. |
U.S. Non-Final Office Action mailed Oct. 26, 2011 for U.S. Appl. No. 12/455,438. |
Mirkovic, J. et al., “A MAC Protocol With Multi-User MIMO Support for Ad-Hoc WLANs”, The 18th Annual IEEE International Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC'07), IEEE, 2007, pp. 1-5, United States. |
Stacey, R. et al., “DL MU-MIMO Ack Protocol (IEEE 802.11-09/1172r0)”, IEEE, Nov. 16, 2009, pp. 1-8, United States. |
IEEE Computer Society, “IEEE Std 802®-2001 (R2007), IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture”, IEEE, Feb. 7, 2002, pp. i-36, New York, United States 4. |
Camp, J.D. et al., “The IEEE 802.11s Extended Service Set Mesh Networking Standard”, IEEE Communications Magazine, vol. 46, No. 8, IEEE, Aug. 2008, pp. 1-6, United States. |
U.S. Final Office Action mailed May 12, 2010 for U.S. Appl. No. 11/589,519. |
U.S. Notice of Allowance mailed Jan. 24, 2011 for U.S. Appl. No. 11/589,519. |
U.S. Final Office Action for U.S. Appl. No. 12/821,940 mailed Aug. 21, 2012. |
U.S. Final Office Action mailed Apr. 12, 2012 for U.S. Appl. No. 12/455,438. |
U.S. Non-Final Office Action mailed May 29, 2012 for U.S. Appl. No. 12/821,940. |
U.S. Notice of Allowance mailed Oct. 21, 2013 for U.S. Appl. No. 12/455,438. |
U.S. Restriction Requirement for U.S. Appl. No. 13/030,070 mailed Nov. 5, 2013. |
U.S. Restriction Requirement for U.S. Appl. No. 13/253,926 mailed Oct. 10, 2013. |
Morioka, Y. et al., “Multi-RTS Proposal”, IEEE 802.11-10/1124r01, Sep. 12, 2010, Slides 1-14, IEEE, USA. |
U.S. Non-Final Office Action mailed Jul. 11, 2013 for U.S. Appl. No. 12/455,438. |
U.S. Non-Final Office Action for U.S. Appl. No. 13/177,386 mailed Dec. 17, 2013. |
U.S. Non-Final Office Action for U.S. Appl. No. 13/253,926 mailed Nov. 25, 2013. |
U.S. Non-Final Office Action for U.S. Appl. No. 12/821,940 mailed Jun. 24, 2014. |
U.S. Non-Final Office Action for U.S. Appl. No. 13/030,070 mailed May 15, 2014. |
U.S. Final Office Action for U.S. Appl. No. 13/253,926 mailed Apr. 29, 2014. |
Number | Date | Country | |
---|---|---|---|
20100002639 A1 | Jan 2010 | US |
Number | Date | Country | |
---|---|---|---|
61077820 | Jul 2008 | US |