US 8,655,279 B2Grant
Short-range wireless communication
Issue Date:2014-02-18
•20 Claims
•7 Drawing Sheets
Abstract
The present specification describes techniques and apparatus that enable wireless devices to communicate effectively at short ranges. In one implementation, the transmit power of a transmitting device is reduced to permit a receiving device to demodulate a signal.
Metadata
Assignee
- Marvell World Trade Ltd.
Inventor
- Raja Banerjea
Application Information
Application Number:US 13/656,482
Filing Date:2012-10-19
Priority Date:2008-06-16
Art Unit:2647
Classifications
IPC:
H04B7/00
Patent Drawings (7 sheets)
Description
RELATED APPLICATIONS
[0001] This application is a continuation of and claims priority to U.S. Utility application Ser. No. 12/478,446, filed on Jun. 4, 2009, which in turn claims priority to U.S. Provisional Patent Application Ser. No. 61/079,635 filed Jul. 10, 2008 and U.S. Provisional Patent Application Ser. No. 61/061,977, filed Jun. 16, 2008, the disclosure of which are incorporated by reference herein in their entirety. This application is further related to PCT Application serial number PCT/US09/46289, filed on Jun. 4, 2009, and national stage filings including Chinese Application serial number 200980122587.0, filed on Dec. 15, 2010, European Patent Office Application serial number 09789754.0, filed on Dec. 16, 2010, Japanese Application serial number 2011-0513586, filed on Nov. 11, 2010, and Korean Application serial number 10-2010-7027891, filed on Dec. 10, 2010.
BACKGROUND
[0002] Devices that communicate wirelessly often do not communicate effectively at short range—e.g., a range less than 1 meter. A user wishing to sync a cellular phone with a laptop computer, for example, may find that neither communicates effectively—or in some cases at all—when the devices are close to each other.
SUMMARY
[0003] A method is described for transmitting, through a network, a link-setup request for a device to transmit at a lower-than-nominal power; receiving, through the network and from the device, a link-setup response indicating a current transmit power of the device, the link-setup response having been received at a received power; determining, based on the received power of the link-setup response, a desired data-signal transmit power for the device; and transmitting, through the network, the desired data-signal transmit power to the device.
[0004] Another method is described for transmitting, from a first wireless-communication-capable device, a first signal at a first power and first modulation, the first signal indicating a request to use a transmission medium for a duration of time; and responsive to receiving a response indicating that the transmission medium is free to use for the duration of time or not receiving a response for a period sufficient to indicate that no potentially interfering device received the first signal, transmitting, from the first wireless-transmission-capable device, a second signal at a second power, a second modulation, and for less than or equal to the duration of time, the second signal transmitting data to a second wireless-communication-capable device, the second power being a lower power than the first power, and the second modulation being different than the first modulation.
[0005] A system on chip (SoC) is also described, the SoC configured to receive a link-setup request, the like-setup request requesting transmission of a data signal at a lower-than-nominal power; transmit a link-setup response in response to receiving the link-setup request, the link-setup response indicating a current transmit power; receive a desired data-signal transmit power in response to the link-setup response; transmit a request to use a transmission medium for a duration of time; and transmit, responsive to receiving an indication that the transmission medium is free to use for the duration of time or not receiving an indication for a period sufficient to indicate that no potentially interfering device received the request to use the transmission medium for the duration of time, the data signal at the desired data-signal transmit power for less than or equal to the duration of time.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.
[0007] FIG. 1 is an illustration of an example operating environment that is configured to enable short-range wireless communication.
[0008] FIG. 2 is a graph showing example communication effectiveness relative to proximity between wireless-communication devices.
[0009] FIG. 3 is a method for controlling transmit-power of devices during short-range wireless communications.
[0010] FIG. 4 illustrates example devices and transmission areas in which a lost-node problem can potentially occur in the context of low-power wireless communications.
[0011] FIG. 5 is a method for addressing a potential lost-node problem.
[0012] FIG. 6 illustrates an example system-on-chip (SoC) environment.
DETAILED DESCRIPTION
Overview
[0013] As noted in the Background above, devices that communicate wirelessly often fail to communicate effectively at short range. At short range, a signal receiver in a device may be incapable of demodulating a strong wireless signal. For current wireless LAN communication protocols, such as IEEE 802.11, the range at which communication becomes less effective is at about one meter or closer. At even shorter ranges, such as 0.2 meter or less, many devices following this or other communication protocols may not be able to communicate at all.
[0014] The present specification describes techniques and apparatus that enable wireless devices to communicate effectively at short ranges. In one implementation, the transmit power of a transmitting device is reduced to permit a receiving device to demodulate a signal.
[0015] In some cases a first device transmitting signals at lower power to a second device, however, can cause a third device to be unaware of the transmission between the first device and the second device. Such a situation is referred to herein as a “lost node”—e.g., when a third device (a node) is unaware of another device (the “lost node”), the third device may transmit a signal even if the lost node is also transmitting. The third device may transmit because it is not aware that other devices are using the same transmission medium. This transmission by the third device may interfere with the receiver of the receiving device or simply obscure the transmission of the “lost node”. To address this potential problem as well as for other positive effects, the present specification also describes techniques and apparatus that enable a device to determine that a low-power transmission is being or will be made. By so doing, devices can communicate effectively at short range without interference from other devices.
[0016] In the discussion that follows, an example operating environment is described. Example methods are also described that may be employed in the example operating environment as well as other environments. These methods are followed by an example System-on-Chip (SoC) embodiment in which components of FIG. 1 may be embodied. In the discussion below, reference will be made to the environment by way of example only and, therefore, implementations described below are not limited to the example environment.
EXAMPLE OPERATING ENVIRONMENT
[0017] FIG. 1 illustrates an example operating environment 100. The example operating environment 100 includes wireless-communication-capable devices 102, all of which are capable of transmitting and receiving wireless communications, such as those following wireless LAN or Bluetooth communication protocols. Devices 102 are shown to include a cellular phone 104, a set-top box 106, a television computing device 108, a desktop computing device 110, a laptop computing device 112, and a handheld tablet computer 114.
[0018] In this example environment, each of devices 102 includes a wireless transmitter 116, a wireless receiver 118, and a short-range wireless communicator 120. Wireless transmitter 116 is capable of transmitting a wireless-communication signal according to one or more communication protocols, such as those for a wireless LAN (Local Area Network) or a wireless PAN (Personal Area Network). These protocols may include those of the IEEE 802.11 and Bluetooth families of protocols.
[0019] Wireless receiver 118 is capable of receiving a wireless-communication signal according to one or more communication protocols, such as those noted for wireless transmitter 116. Wireless transmitter 116 and wireless receiver 118 may be separate (shown) or combined (often called a transceiver, not shown) and may be hardware combined with or separate from software. Wireless transmitter 116 and wireless receiver 118 are capable of modulating and demodulating a wireless signal, respectively.
[0020] Note that these various wireless-communication protocols may enable communication less effectively at short ranges, such as those of less than one meter. Even receivers that are relatively capable of handling high-power transmissions (and thus typical short-range transmissions) are often susceptible to some loss of effectiveness at short range. Consider graph 200 of FIG. 2 , which shows example communication effectiveness relative to proximity between wireless-communication devices. Graph 200 shows example communication effectiveness for current wireless LAN communication protocols of 802.11 and Bluetooth for some devices. Here the effectiveness of communication drops at about 0.4 meter for 802.11 and 0.25 meter for Bluetooth. Effectiveness of communication is shown as throughput in megabytes per second at 202, effectiveness for 802.11 is shown relative to meters proximity at 204, effectiveness for Bluetooth is shown relative to meters proximity at 206, with proximity in meters (not to scale) shown at 208.
[0021] Short-range wireless communicator 120 (also referred to as “communicator 120” for brevity) is capable of enabling a wireless device to communicate effectively at short range. Communicator 120 may act independently or in conjunction with various other entities, such as wireless transmitter 116 and wireless receiver 118. Communicator 120 may be separate from or integral with other entities of device 102 as well, such as by being firmware integrated into a System-on-Chip (SoC) having or communicating with wireless transmitter 116 and wireless receiver 118.
[0022] In environment 100 of FIG. 1 , communicator 120 includes a set of computer-executable instructions stored on computer-readable media 122. When executed by one or more processors 124, device 102 acts according to those instructions.
[0023] Communicator 120 is capable of making decisions and performing one or more tasks to enable devices to effectively communicate wirelessly at short range. In some embodiments this also includes addressing a “lost-node” separately from or in conjunction with lowering transmission power as described below in the sections entitled “Example Power-control Process” and “Lost Node”, as well as elsewhere herein.
EXAMPLE POWER-CONTROL PROCESS
[0024] The following discussion describes techniques that may be implemented utilizing the previously described environment. Aspects of the method may be implemented in hardware, firmware, software, or a combination thereof The methods are shown as a set of blocks that specify operations performed by one or more entities and are not necessarily limited to the orders shown for performing the operations by the respective blocks.
[0025] FIG. 3 depicts a method 300 for controlling transmit-power control for short-range wireless communications. In this example implementation, a data-receiving device, here laptop computing device 112, is attempting to communicate wirelessly at short range with a data-transmitting device, here cellular phone 104. Note that these two devices are examples of device 102 of FIG. 1 , and that both may include the elements shown for device 102 of FIG. 1 (e.g., communicator 120).
[0026] As illustrated, actions performed by a data-transmitting device are shown at 302 and actions of a data-receiving device are shown at 304, both separated by a vertical dashed line. The devices 104 and 112 shown are for illustration purposes, and are not intended to limit the types of data-transmitting and data-receiving devices. Note also that communications are made between both devices, and thus both transmit and receive. The data-transmitting device is the device that intends to transmit information over a wireless medium to the data-receiving device following link setup between the devices, described below.
[0027] At block 306, a data-receiving device transmits a link-setup request for a data-transmitting device to transmit at a lower-than-nominal power. The data-receiving device may transmit through various wireless local or personal area networks and using various protocols and modulations, such as those of the IEEE 802.11 family of protocols or the Bluetooth family of protocols to name a few. The data-receiving device may transmit the link-setup request using a different modulation or protocol than intended for future data communications. One such example is transmitting the link-setup request using robust modulation like direct sequence spread spectrum techniques (DSSS). Many of these robust modulations aid in setting up a communication link though they often have lower data throughput than the modulation used in future data transmissions. The link-setup request may also be sent at a lower-than-nominal power to reduce possible interference or saturation by the link-setup request.
[0028] At block 308, the data-transmitting device receives the link-setup request and responds with a link-setup response indicating a current transmit power of the data-transmitting device. In some cases the data-transmitting device also provides other information in the link-setup response, such as a link margin associated with the data-transmitting device. Link margin is a measure of the range of powers that the data-transmitting device may effectively demodulate a received signal.
[0029] At block 310, the data-receiving device receives the link-setup response from the data-transmitting device. This link-setup response indicates the current transmit power of the data-transmitting device at which the link-setup response was transmitted. This response is received at a particular power by the data-receiving device. With this information, the data-receiving device is able to determine a relationship between transmit power and received power. As noted in part above, the receiving device may also receive the link margin associated with the data-transmitting device.
[0030] At block 312, the data-receiving device determines a desired data-signal transmit power and transmits this desired data-signal transmit power to the data-transmitting device. This and other steps of this method may be performed by short-range wireless communicator 120, as well as wireless transmitter 116 and wireless receiver 118, all of which are shown in FIG. 1 . Note that both the data-receiving device and the data-transmitting device may include these entities.
[0031] Short-range wireless communicator 120 determines the desired data-signal transmit power based on the transmit power at which the link-setup response was transmitted by the data-transmitting device, the received power of the link-setup response, and a desired data-signal reception power. As noted above the link-setup response indicated the transmit power and the data-receiving device determined the power at which link-setup response was received. Communicator 120 determines the desired data-signal transmission power with this information. In some cases communicator 120 also determines this based on the data-receiving device's link margin, hardware capabilities of wireless receiver 118, and/or the modulation that the data signal is intended to be transmitted. In one implementation, communicator 120 determines the desired data-signal transmit power according to the following equation:
desiredtransmitPower=TPCresponseTxPower−RSSIRx+RSSIdesiredRate
desiredtransmitPower=TPCresponseTxPower−RSSIRx+RSSIdesiredRate
[0032] Here desiredtransmitPower is the desired transmit power at which the data-receiving device requests that the data-transmitting device transmit the data signal. The TPCresponseTxPower is the current transmit power of the data-transmitting device. RSSI stands for “Received Signal Strength Indication”. The RSSIRx is the received power of the received response. The RSSIdesiredRate is the desired received power. The desired power at which the data-signal is received is often based at least in part on the capabilities and configuration of the wireless receiver. Some wireless receivers receive data signals best at a particular power different from other wireless receivers, either independent of or based on the particular modulation of the data signal.
[0033] At block 314, the data-transmitting device receives the desired data-signal transmit power and transmits a data signal at the desired data-signal transmit power, which is received at the data-receiving device shown at block 316. At this point a link for communication is complete for data transmission based on the management transmissions communicated at blocks 306 through 312 and part of 314. In some cases, however, the data signal will be received by the data-receiving device having less than a maximum throughput for the modulation at which the data signal is sent. In such a case the method 300 proceeds along optional paths to blocks 318 and 320 as well as repeating some other actions of method 300.
[0034] As noted above, the data-receiving device at block 316 receives signals at a received power. Communicator 120 may then determine at block 318 that the received power has a less-than-maximum throughput for the modulation. Responsive to this determination and based on the received power of the data signal, communicator 120 determines a second desired data-signal transmit power at block 320. Communicator 120 may do so in a manner similar to the manner in which the first desired data-signal transmit power was determined.
[0035] One difference is that additional information has been gained, such as the received power of the data signal rather than the received power of a link-setup response. Responsive to determining this second desired data-signal transmit power, the data-receiving device transmits this second desired data-signal transmit power also at block 320. The data-transmitting device may use this information to transmit the data signal at the second desired data-signal transmit power at block 314. Note that these blocks may be repeated again if the data-receiving device determines that the received power is still at a less-than-maximum throughput.
[0036] Following the initial link setup, the data-receiving device, if it intends to adjust the transmission power of the data signal, may do so at block 320 using a directed probe response frame, such as those used in the IEEE 802.11 family of protocols.
[0037] This method may be responsive to either the data-receiving device, the data-transmitting device, or some third-party device determining that the nominal transmission power is potentially too high for maximum throughput between the data-receiving device and the data-transmitting device. One such case is when the data-receiving device determines that a data signal or setup signal from the data transmitting device is received at a power that does not permit a maximum throughput for the modulation of the signal. The data-receiving device may determine this through interference or saturation at its wireless receiver 118. It may also be determined by the data-transmitting device through delays or other information learned from communications from the data-receiving device or a third-party device.
[0038] The communication link established as part of method 300 can optionally be maintained, such as with closed-loop or open-loop control. Examples of open-loop control include ones that determine whether there has been a change in the received data-signal power and, responsive to this change, change a transmit power of the data-receiving device. Thus, communicator 120 may use an increase or decrease in received power of a data signal from the data-transmitting device to extrapolate that the data-receiving device will need to increase or decrease its transmission power in a similar manner. One case in which this occurs is when a device moves closer to or further away from the other device. In the example above a user may move the cellular phone 104 or the laptop computing device 112.
[0039] In more detail, communicator 120 may adjust transmission power of the data-receiving device or the data-transmitting device, depending on which device this particular communicator 120 resides in, using the following equation:
newtransmitPower=oldtransmitPower−oldRSSI+newRSSI
newtransmitPower=oldtransmitPower−oldRSSI+newRSSI
[0040] Here newtransmitPower is the new (second or later) desired transmit power at which the data-receiving device requests that the data-transmitting device transmits the data signal. The oldtransmitPower is the previous transmit power desired and requested. This is also the most-recent previous transmit power if the newtransmitPower is a third or later requested power. The oldRSSI is the previous (or in some cases average also) received power. The newRSSI is the current received power (or in some cases an average also).
[0041] Examples of closed-loop control include periodically re-performing some steps of the method 300 to determine a new desired data-signal transmit power or performing these steps responsive to determining a change in a throughput of a data signal. These steps include those performed at blocks 306, 310, and 312 and/or 318 and 320.
[0042] Lost Node
[0043] As noted in part above, in some cases a device that is transmitting a wireless signal may not be noticed by another device intending to transmit a signal. This signal from the other device may interfere with the signal of the unnoticed device (aka the “lost node”). This potential problem is exacerbated when a transmission is made at low power. To address this potential problem, the present specification describes techniques and apparatus that enable a device to determine that a low-power transmission will be made, which permit devices to effectively communicate at short range and often without interference by other devices.
[0044] FIG. 4 illustrates example devices and transmission areas in which a lost-node problem can potentially occur in the context of low-power transmission. Consider four examples of wireless-communication-capable devices 102 of FIG. 1 . The first two devices are within a low-power transmission area 402. These two devices are low-power-area transmitting device 404 and low-power-area receiving device 406. The second two devices are within a higher-power transmission area 408. These two devices are higher-power-area transmitting device 410 and higher-power-area receiving device 412.
[0045] Note that area 402 overlaps with area 408. This overlap illustrates that a device in area 408 may potentially transmit a signal that interferes with signals in area 402. Such interferences are possible if a device in area 408 is not aware of low-power transmission in area 402.
[0046] The following discussion describes techniques to mitigate this and other interferences. These techniques may be implemented utilizing the previously described environment of FIGS. 1 and 4 as well as others. Aspects of these methods may be implemented in hardware, firmware, software, or a combination thereof These methods are shown as a set of blocks that specify operations performed by one or more entities and are not necessarily limited to the orders shown for performing the operations by the respective blocks.
[0047] FIG. 5 depicts a method 500 in an example implementation in which a device can address a potential lost-node problem. At block 502, a device intending to transmit at low power transmits a signal requesting a transmission medium for a duration of time. This signal may be sent having a robust modulation signal to increase the likelihood that a device (e.g., an Access Point or some device that may transmit) will receive and understand the transmission. The signal may also or instead be sent at a high or nominal power to increase the likelihood that a device that may not notice a future low-power signal will notice and understand this signal.
[0048] As noted in more detail below, communicator 120 may determine the duration of time based on how long the data will take to transmit using the medium and at a particular low power. This duration may be for a particular amount or all of the data. These particular amounts may be as little as some number of data packets that in total are not sufficient to transmit all of the desired data. This data can be as small as a single data packet, in which case the duration of time is short. In such a case the method 500 may be repeated for each packet, packets, or other particular amount of data.
[0049] Again consider FIG. 4 . Here assume that cellular phone 406 intends to communicate at low power with desktop computing device 404, such as to sync up cellular phone 406's calendar with desktop computing device 404's calendar. Prior to doing so, cellular phone 406 (using communicator 120 and wireless transmitter 116 of FIG. 1 ) transmits a signal requesting a transmission medium so that the device can transmit a signal at low power. Here assume that cellular phone 406 transmits with wireless transmitter 116 and according to IEEE 802.11, with a robust modulation, and at nominal power. Examples of such a signal include a Request To Send (RTS) packet and a Clear To Send-Self (CTS-Self) packet.
[0050] At block 504, the transmitting device either receives a response from one or more third-party devices indicating that the requested medium is free to use or does not. If no response is received, the device proceeds along the “No” path to block 506. At block 506, the device waits some time period sufficient to indicate that no other devices received the request at block 504 or otherwise indicate that the medium is fee to use. After this wait period, the device proceeds to block 508.
[0051] At block 508 the device transmits at low power and for up to about the duration of time requested at block 504. If, however, the device receives a response indicating that the requested transmission medium is free to use, the device follows the “Yes” path to block 508 without a wait period. A response may include a Clear To Send (CTS) packet from other devices. Following the transmission at low power at block 508, the device may optionally proceed to block 510 to repeat the process. As noted in more detail below, the duration of time may be for a particular amount of data. If this amount of data is broken into pieces, or is small and discrete, such as a packet of data, then multiple pieces and multiple durations of time may be transmitted and requested.
[0052] Continuing the above example, assume that wireless receiver 118 of cellular phone 406 receives a signal from a device or access point (e.g., tablet computer 410) indicating that the other device or access point is granting the transmission medium. In some cases this signal in response to the request may be a CTS frame indicating that the medium is free to use. When sent from an access point, the response may indicate that the access point has set its NAV to not use the transmission medium for the duration of time. In any of these cases, communicator 120 receives this indication (demodulated by wireless receiver 118 and passed to communicator 120) and proceeds to block 508.
[0053] After receiving a response or waiting the period, cellular phone 406 transmits at low power (block 508). In this ongoing example, cellular phone 406's wireless receiver 118 receives the response indicating that the communication medium will not be used, after which communicator 120 permits cellular phone 406's wireless transmitter 116 to transmit at low power to desktop computing device 404 for the duration of time. If the duration is for a piece rather than all of the data, the device may repeat, following block 510, one or more parts of the method 500.
[0054] Note that the method of FIG. 5 may permit devices 404 and 406 to communicate at low power without interference from devices 410 and 412. Note also that this method may enable either or both of devices 410 and 412 to avoid interference from devices 404 and 406 as well, such as when a low-power transmission from cellular phone 406 may interfere with a transmission (high or low power) from tablet computer 410 that is intended for receipt by laptop computing device 412.
SYSTEM-ON-CHIP EXAMPLE
[0055] FIG. 6 illustrates an example System-on-Chip (SoC) 600, which can implement various embodiments described above. An SoC can be implemented in a fixed or mobile device, such as any one or combination of a media device, computer device, television set-top box, video processing and/or rendering device, appliance device, gaming device, electronic device, vehicle, workstation, and/or in any other type of device that may communicate wirelessly in a local or personal area network that may operate at short range. Examples of some of these are shown in FIG. 1 at 102.
[0056] SoC 600 can be integrated with electronic circuitry, a microprocessor, memory, input-output (I/O) logic control, communication interfaces and components, other hardware, firmware, and/or software needed to run an entire device. SoC 600 can also include an integrated data bus (not shown) that couples the various components of the SoC for data communication between the components. A device that includes SoC 600 can also be implemented with many combinations of differing components.
[0057] In this example, SoC 600 includes various components such as an input-output (I/O) logic control 602 (e.g., to include electronic circuitry) and a microprocessor 604 (e.g., any of a microcontroller or digital signal processor). SoC 600 also includes a memory 606, which can be any type of random access memory (RAM), a low-latency nonvolatile memory (e.g., flash memory), read only memory (ROM), and/or other suitable electronic data storage. SoC 600 can also include various firmware and/or software, such as an operating system 608, which can be computer-executable instructions maintained by memory 606 and executed by microprocessor 604. SoC 600 can also include other various communication interfaces and components, wireless LAN (WLAN) or PAN (WPAN) components, other hardware, firmware, and/or software.
[0058] SoC 600 may include wireless transmitter 116, wireless receiver 118, and short-range wireless communicator 120 (in either or multiple devices as noted above). Examples of these various components, functions, and/or entities, and their corresponding functionality, are described with reference to the respective components of the example environment 100 shown in FIG. 1 .
[0059] Communicator 120 in SoC 600, either independently or in combination with other entities, can be implemented as computer-executable instructions maintained by memory 606 and executed by microprocessor 604 to implement various embodiments and/or features described herein. Short-range wireless communicator 120 may also be provided integral with other entities of the SoC, such as integrated with one or both of wireless transmitter 116 and wireless receiver 118. Alternatively or additionally, communicator 120 and the other components can be implemented as hardware, firmware, fixed logic circuitry, or any combination thereof that is implemented in connection with the I/O logic control 602 and/or other signal processing and control circuits of SoC 600.
[0060] This specification describes techniques and apparatus that enable short-range wireless communication by reducing the transmission power of a transmitting device. This enables a receiving device to demodulate the signal without being interfered with by a too-powerful transmitted signal. The techniques described herein also address “lost-node” problems that may arise in lower-power transmissions and in other cases where a node is not detected.
[0061] Although the subject matter has been described in language specific to structural features and/or methodological steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or steps described above, including orders in which they are performed.
Claims
What is claimed is:
1. One or more computer-readable memory devices storing processor-executable instructions that, responsive to execution by a processor, implement a wireless communication module to:
transmit, from a first wireless-communication-capable device, a first signal indicating a request to use a wireless medium for a first duration of time, the first signal transmitted at a first power and with a first modulation; and
responsive to receiving, from a second wireless-communication-capable device, a response indicating that the wireless medium is free to use for the first duration of time, transmit, from the first wireless-transmission-capable device during the first duration of time for which use of the wireless medium is requested, a second signal transmitting data to a third wireless-communication-capable device, the second signal transmitted at a second power, with a second modulation, and for a second duration of time less than or equal to the first duration of time, the second signal being different from the first signal, the second power being less than the first power, and the second modulation being different than the first modulation.
2. The one or more computer-readable memory devices of claim 1, comprising additional processor-executable instructions that, responsive to execution by the processor, implement the wireless communication module to transmit the second signal to the third wireless-communication-capable device responsive to not receiving a response for a period sufficient to indicate that a potentially interfering device did not receive the first signal.
3. The one or more computer-readable memory devices of claim 1, wherein the first duration of time is based on an amount of time expected to be consumed by the first wireless-communication-capable device to transmit a particular amount of the data to the third wireless-communication-capable device using the second signal.
4. The one or more computer-readable memory devices of claim 1, wherein the first power is a nominal power or a high power of the first wireless-communication-capable device.
5. The one or more computer-readable memory devices of claim 1, wherein the first signal includes a Request-to-Send (RTS) frame or a Clear-to-Send-Self (CTS-Self) frame.
6. The one or more computer-readable memory devices of claim 1, wherein the response indicating that the wireless medium is free to use includes a Clear-to-Send (CTS) frame having the first modulation.
7. The one or more computer-readable memory devices of claim 6, wherein the CTS frame indicates that a network allocation vector (NAV) of a wireless network to which a potentially interfering device belongs is set to not use the wireless medium during the first duration of time.
8. A System-on-Chip (SoC) comprising:
an interface to a receiver configured to communicate via a wireless medium;
an interface to a transmitter configured to communicate via the wireless medium; and
a wireless communication module configured to:
transmit, via the transmitter, a first signal indicating a request to use a wireless medium for a first duration of time, the first signal transmitted at a first power and with a first modulation; and
responsive to receiving, from a second wireless-communication-capable device, a response indicating that the wireless medium is free to use for the first duration of time, transmit, via the transmitter during the first duration of time for which use of the wireless medium is requested, a second signal transmitting data to a third wireless-communication-capable device, the second signal transmitted at a second power, with a second modulation, and for a second duration of time less than or equal to the first duration of time, the second signal being different from the first signal, the second power being less than the first power, and the second modulation being different than the first modulation.
9. The SoC of claim 8, wherein the wireless communication module is further configured to transmit the second signal to the third wireless-communication-capable device responsive to not receiving a response for a period of time sufficient to indicate that a potentially interfering device did not receive the first signal.
10. The SoC of claim 8, wherein the first duration of time is based on an amount of time expected to be consumed by transmitting the data to the third wireless-communication-capable device using the second signal.
11. The SoC of claim 8, wherein the first modulation includes a direct-sequence spread spectrum (DSSS) modulation and the second modulation includes a modulation different from the DSSS modulation.
12. The SoC of claim 8, wherein the first signal includes a Request-to-Send (RTS) frame or a Clear-to-Send-Self (CTS-Self) frame indicating the first duration of time.
13. The SoC of claim 12, wherein the first signal and the second signal include packets or frames transmitted in compliance with the IEEE 802.11 standard.
14. The SoC of claim 8, wherein the SoC is embodied, in whole or part, as an access point, laptop computer, cellular phone, tablet computer, set-top box device, or a television.
15. A wireless-communication-capable device comprising:
a receiver configured to communicate via a wireless network;
a transmitter configured to communicate via the wireless network; and
a wireless communication module configured to:
transmit, via the transmitter, a first signal indicating a request to use the wireless network for a first duration of time, the first signal transmitted at a first power and with a first modulation; and
responsive to receiving, via the receiver and from a second wireless-communication-capable device, a response indicating that the wireless medium is free to use for the first duration of time, transmit, via the transmitter during the first duration of time for which use of the wireless medium is requested, a second signal transmitting data to a third wireless-communication-capable device, the second signal transmitted at a second power, with a second modulation, and for a second duration of time less than or equal to the first duration of time, the second signal being different from the first signal, the second power being less than the first power, and the second modulation being different than the first modulation.
16. The wireless-communication-capable device of claim 15, wherein the wireless communication module is further configured to transmit the second signal to the third wireless-communication-capable device responsive to not receiving a response for a period of time sufficient to indicate that a potentially interfering device did not receive the first signal.
17. The wireless-communication-capable device of claim 16, wherein the third wireless-communication-capable device resides in a low-power transmission area of the wireless network and the second wireless-communication-capable device resides in a high-power transmission area of the wireless network.
18. The wireless-communication-capable device of claim 15, wherein the second modulation scheme is an orthogonal frequency division multiplex (OFDM) modulation scheme or a complimentary code keying (CCK) modulation.
19. The wireless-communication-capable device of claim 15, wherein the first signal includes a Request-to-Send (RTS) frame or a Clear-to-Send-Self (CTS-Self) frame.
20. The wireless-communication-capable device of claim 15, wherein the response indicating that the wireless medium is free to use for the first duration of time includes a Clear-to-Send (CTS) frame having the first modulation.
Patent Citations (270)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4337463(A) | 1982-06-01 | Vangen | Applicant |
| US4805215(A) | 1989-02-01 | Miller | Applicant |
| US5347234(A) | 1994-09-01 | Gersbach et al. | Applicant |
| US5634207(A) | 1997-05-01 | Yamaji et al. | Applicant |
| US5673291(A) | 1997-09-01 | Dent | Applicant |
| US5708656(A) | 1998-01-01 | Noneman et al. | Applicant |
| US5847616(A) | 1998-12-01 | Ng et al. | Applicant |
| US5995819(A) | 1999-11-01 | Yamaji et al. | Applicant |
| US6167245(A) | 2000-12-01 | Welland et al. | Applicant |
| US6285262(B1) | 2001-09-01 | Kuriyama | Applicant |
| US6320919(B1) | 2001-11-01 | Khayrallah et al. | Applicant |
| US6347091(B1) | 2002-02-01 | Wallentin et al. | Applicant |
| US6366622(B1) | 2002-04-01 | Brown et al. | Applicant |
| US6374117(B1) | 2002-04-01 | Denkert et al. | Applicant |
| US6438364(B1) | 2002-08-01 | Waite | Applicant |
| US6452458(B1) | 2002-09-01 | Tanimoto | Applicant |
| US6509777(B2) | 2003-01-01 | Razavi et al. | Applicant |
| US6519461(B1) | 2003-02-01 | Andersson et al. | Applicant |
| US6535037(B2) | 2003-03-01 | Maligeorgos | Applicant |
| US6553229(B1) | 2003-04-01 | Dent | Applicant |
| US6640308(B1) | 2003-10-01 | Keyghobad et al. | Applicant |
| US6650195(B1) | 2003-11-01 | Brunn et al. | Applicant |
| US6675328(B1) | 2004-01-01 | Krishnamachari et al. | Applicant |
| US6741846(B1) | 2004-05-01 | Welland et al. | Applicant |
| US6754189(B1) | 2004-06-01 | Cloutier et al. | Applicant |
| US6816452(B1) | 2004-11-01 | Maehata | Applicant |
| US6816718(B2) | 2004-11-01 | Yan et al. | Applicant |
| US6934566(B2) | 2005-08-01 | Kang et al. | Applicant |
| US6946950(B1) | 2005-09-01 | Ueno et al. | Examiner |
| US6954708(B2) | 2005-10-01 | Rakshani et al. | Applicant |
| US7079811(B2) | 2006-07-01 | Lee et al. | Applicant |
| US7139540(B2) | 2006-11-01 | Wu et al. | Applicant |
| US7173431(B1) | 2007-02-01 | Lo et al. | Applicant |
| US7206840(B2) | 2007-04-01 | Choi et al. | Applicant |
| US7212798(B1) | 2007-05-01 | Adams et al. | Applicant |
| US7239882(B1) | 2007-07-01 | Cook | Applicant |
| US7257095(B2) | 2007-08-01 | Liu | Applicant |
| US7286009(B2) | 2007-10-01 | Andersen et al. | Applicant |
| US7298183(B2) | 2007-11-01 | Mirzaei et al. | Applicant |
| US7310023(B2) | 2007-12-01 | Cha et al. | Applicant |
| US7319849(B2) | 2008-01-01 | Womac | Applicant |
| US7342895(B2) | 2008-03-01 | Serpa et al. | Applicant |
| US7355416(B1) | 2008-04-01 | Darshan | Applicant |
| US7377441(B2) | 2008-05-01 | Wiklof et al. | Applicant |
| US7395040(B2) | 2008-07-01 | Behzad | Applicant |
| US7403018(B1) | 2008-07-01 | Lo et al. | Applicant |
| US7564826(B2) | 2009-07-01 | Sherman et al. | Applicant |
| US7595768(B2) | 2009-09-01 | Li et al. | Applicant |
| US7599671(B2) | 2009-10-01 | Kopikare et al. | Applicant |
| US7616935(B2) | 2009-11-01 | Fernandez-Corbaton et al. | Applicant |
| US7626966(B1) | 2009-12-01 | Ruiter et al. | Applicant |
| US7656205(B2) | 2010-02-01 | Chen et al. | Applicant |
| US7659003(B2) | 2010-02-01 | Aoki et al. | Examiner |
| US7672645(B2) | 2010-03-01 | Kilpatrick et al. | Applicant |
| US7689190(B2) | 2010-03-01 | Kerth et al. | Applicant |
| US7711004(B2) | 2010-05-01 | Xu | Applicant |
| US7826411(B2) | 2010-11-01 | Gonikberg et al. | Applicant |
| US7849333(B2) | 2010-12-01 | Schindler | Applicant |
| US7876786(B2) | 2011-01-01 | Bahl et al. | Applicant |
| US7881746(B2) | 2011-02-01 | Desai | Applicant |
| US7936714(B1) | 2011-05-01 | Karr et al. | Applicant |
| US7957340(B2) | 2011-06-01 | Choi et al. | Applicant |
| US7966036(B2) | 2011-06-01 | Kojima | Applicant |
| US7995544(B2) | 2011-08-01 | Benveniste | Examiner |
| US8000715(B2) | 2011-08-01 | Melpignano et al. | Applicant |
| US8014329(B2) | 2011-09-01 | Gong | Applicant |
| US8060017(B2) | 2011-11-01 | Schlicht et al. | Examiner |
| US8072913(B2) | 2011-12-01 | Desai | Applicant |
| US8077652(B2) | 2011-12-01 | William | Applicant |
| US8078111(B2) | 2011-12-01 | Jovicic et al. | Applicant |
| US8081038(B2) | 2011-12-01 | Lee et al. | Applicant |
| US8107391(B2) | 2012-01-01 | Wu et al. | Applicant |
| US8139670(B1) | 2012-03-01 | Son et al. | Applicant |
| US8149715(B1) | 2012-04-01 | Goel et al. | Applicant |
| US8150328(B2) | 2012-04-01 | Chaudhri et al. | Applicant |
| US8170002(B2) | 2012-05-01 | Wentink | Applicant |
| US8170546(B2) | 2012-05-01 | Bennett | Applicant |
| US8189506(B2) | 2012-05-01 | Kneckt et al. | Applicant |
| US8204015(B2) | 2012-06-01 | Chaudhri et al. | Applicant |
| US8229087(B2) | 2012-07-01 | Sumioka et al. | Applicant |
| US8254296(B1) | 2012-08-01 | Lambert | Applicant |
| US8274894(B2) | 2012-09-01 | Kneckt et al. | Applicant |
| US8275314(B1) | 2012-09-01 | Lin | Applicant |
| US8310967(B1) | 2012-11-01 | Goel | Applicant |
| US8315564(B2) | 2012-11-01 | Banerjea | Applicant |
| US8340034(B1) | 2012-12-01 | Lee | Applicant |
| US8364188(B2) | 2013-01-01 | Srinivasan et al. | Applicant |
| US8369782(B1) | 2013-02-01 | Lin et al. | Applicant |
| US8472427(B1) | 2013-06-01 | Wheeler et al. | Applicant |
| US8472968(B1) | 2013-06-01 | Kim | Applicant |
| US8532041(B1) | 2013-09-01 | Lambert et al. | Applicant |
| US8553561(B1) | 2013-10-01 | Chokshi et al. | Applicant |
| US8571479(B2) | 2013-10-01 | Banerjea | Applicant |
| US8577305(B1) | 2013-11-01 | Rossi et al. | Applicant |
| US8588705(B1) | 2013-11-01 | Tsui et al. | Applicant |
| US8600324(B1) | 2013-12-01 | Cousinard et al. | Applicant |
| US2002/0025810(A1) | 2002-02-01 | Takayama et al. | Applicant |
| US2002/0049854(A1) | 2002-04-01 | Cox et al. | Applicant |
| US2003/0040316(A1) | 2003-02-01 | Stanforth et al. | Applicant |
| US2003/0148750(A1) | 2003-08-01 | Yan et al. | Applicant |
| US2003/0198200(A1) | 2003-10-01 | Diener et al. | Applicant |
| US2004/0063403(A1) | 2004-04-01 | Durrant | Applicant |
| US2004/0105401(A1) | 2004-06-01 | Lee | Applicant |
| US2004/0110470(A1) | 2004-06-01 | Tsiden et al. | Applicant |
| US2004/0162106(A1) | 2004-08-01 | Monroe et al. | Applicant |
| US2004/0192222(A1) | 2004-09-01 | Vaisanen et al. | Applicant |
| US2004/0198297(A1) | 2004-10-01 | Oh et al. | Applicant |
| US2004/0214575(A1) | 2004-10-01 | Jovanovic | Applicant |
| US2004/0233881(A1) | 2004-11-01 | Kang et al. | Applicant |
| US2005/0018641(A1) | 2005-01-01 | Zhao et al. | Applicant |
| US2005/0025104(A1) | 2005-02-01 | Fischer et al. | Applicant |
| US2005/0025174(A1) | 2005-02-01 | Fischer et al. | Applicant |
| US2005/0058151(A1) | 2005-03-01 | Yeh | Examiner |
| US2005/0064840(A1) | 2005-03-01 | Heydari et al. | Applicant |
| US2005/0090218(A1) | 2005-04-01 | Ishida et al. | Applicant |
| US2005/0120119(A1) | 2005-06-01 | Bhanu et al. | Applicant |
| US2005/0135360(A1) | 2005-06-01 | Shin et al. | Applicant |
| US2005/0174962(A1) | 2005-08-01 | Gurevich | Applicant |
| US2005/0186962(A1) | 2005-08-01 | Yoneyama et al. | Applicant |
| US2005/0206554(A1) | 2005-09-01 | Yamaura | Applicant |
| US2005/0250528(A1) | 2005-11-01 | Song et al. | Applicant |
| US2005/0254423(A1) | 2005-11-01 | Berghoff | Applicant |
| US2005/0281278(A1) | 2005-12-01 | Black et al. | Applicant |
| US2006/0007863(A1) | 2006-01-01 | Naghian | Applicant |
| US2006/0049880(A1) | 2006-03-01 | Rein et al. | Applicant |
| US2006/0063509(A1) | 2006-03-01 | Pincu et al. | Applicant |
| US2006/0079232(A1) | 2006-04-01 | Omori et al. | Applicant |
| US2006/0114044(A1) | 2006-06-01 | Mintchev et al. | Applicant |
| US2006/0120338(A1) | 2006-06-01 | Hwang et al. | Applicant |
| US2006/0128308(A1) | 2006-06-01 | Michael et al. | Applicant |
| US2006/0128347(A1) | 2006-06-01 | Piriyapoksombut et al. | Applicant |
| US2006/0189359(A1) | 2006-08-01 | Kammer et al. | Applicant |
| US2006/0199565(A1) | 2006-09-01 | Ammirata | Applicant |
| US2006/0200862(A1) | 2006-09-01 | Olson et al. | Applicant |
| US2006/0215601(A1) | 2006-09-01 | Vleugels et al. | Applicant |
| US2006/0223474(A1) | 2006-10-01 | Yoshizaki et al. | Applicant |
| US2006/0239443(A1) | 2006-10-01 | Oxford et al. | Applicant |
| US2006/0251198(A1) | 2006-11-01 | Ma et al. | Applicant |
| US2006/0252418(A1) | 2006-11-01 | Quinn et al. | Applicant |
| US2006/0264179(A1) | 2006-11-01 | Bonneville et al. | Applicant |
| US2006/0268756(A1) | 2006-11-01 | Wang et al. | Applicant |
| US2006/0268804(A1) | 2006-11-01 | Kim et al. | Applicant |
| US2006/0281404(A1) | 2006-12-01 | Lee et al. | Applicant |
| US2006/0282541(A1) | 2006-12-01 | Hiroki | Applicant |
| US2006/0282667(A1) | 2006-12-01 | Kim et al. | Applicant |
| US2006/0286935(A1) | 2006-12-01 | Utsunomiya et al. | Applicant |
| US2007/0010237(A1) | 2007-01-01 | Jones et al. | Applicant |
| US2007/0010247(A1) | 2007-01-01 | Mouna-Kingue et al. | Applicant |
| US2007/0014314(A1) | 2007-01-01 | O'Neil | Applicant |
| US2007/0077908(A1) | 2007-04-01 | Vorenkamp et al. | Applicant |
| US2007/0081553(A1) | 2007-04-01 | Cicchetti et al. | Applicant |
| US2007/0103829(A1) | 2007-05-01 | Darshan et al. | Applicant |
| US2007/0109973(A1) | 2007-05-01 | Trachewsky | Applicant |
| US2007/0142080(A1) | 2007-06-01 | Tanaka et al. | Applicant |
| US2007/0173286(A1) | 2007-07-01 | Carter et al. | Applicant |
| US2007/0178888(A1) | 2007-08-01 | Alfano et al. | Applicant |
| US2007/0183443(A1) | 2007-08-01 | Won | Applicant |
| US2007/0200622(A1) | 2007-08-01 | Filoramo et al. | Applicant |
| US2007/0202814(A1) | 2007-08-01 | Ono et al. | Applicant |
| US2007/0206519(A1) | 2007-09-01 | Hansen et al. | Applicant |
| US2007/0206762(A1) | 2007-09-01 | Chandra et al. | Applicant |
| US2007/0223430(A1) | 2007-09-01 | Desai et al. | Applicant |
| US2007/0238482(A1) | 2007-10-01 | Rayzman et al. | Applicant |
| US2007/0242645(A1) | 2007-10-01 | Stephenson et al. | Applicant |
| US2007/0264959(A1) | 2007-11-01 | Carrez | Applicant |
| US2007/0268862(A1) | 2007-11-01 | Singh et al. | Applicant |
| US2007/0280471(A1) | 2007-12-01 | Fallahi et al. | Applicant |
| US2007/0286298(A1) | 2007-12-01 | Choi et al. | Applicant |
| US2007/0297388(A1) | 2007-12-01 | Appaji et al. | Applicant |
| US2008/0027033(A1) | 2008-01-01 | Gonda et al. | Applicant |
| US2008/0045162(A1) | 2008-02-01 | Rofougaran et al. | Applicant |
| US2008/0056201(A1) | 2008-03-01 | Bennett | Applicant |
| US2008/0069034(A1) | 2008-03-01 | Buddhikot et al. | Applicant |
| US2008/0076466(A1) | 2008-03-01 | Larsson | Examiner |
| US2008/0080446(A1) | 2008-04-01 | Chung | Applicant |
| US2008/0095058(A1) | 2008-04-01 | Dalmases et al. | Applicant |
| US2008/0095059(A1) | 2008-04-01 | Chu | Applicant |
| US2008/0111639(A1) | 2008-05-01 | Ryckaert et al. | Applicant |
| US2008/0129118(A1) | 2008-06-01 | Diab | Applicant |
| US2008/0130595(A1) | 2008-06-01 | Abdel-Kader | Applicant |
| US2008/0137580(A1) | 2008-06-01 | Axelsson et al. | Applicant |
| US2008/0139212(A1) | 2008-06-01 | Chen et al. | Applicant |
| US2008/0161031(A1) | 2008-07-01 | Tu | Applicant |
| US2008/0170550(A1) | 2008-07-01 | Liu et al. | Applicant |
| US2008/0181154(A1) | 2008-07-01 | Sherman | Applicant |
| US2008/0187003(A1) | 2008-08-01 | Becker | Applicant |
| US2008/0232287(A1) | 2008-09-01 | Shao et al. | Applicant |
| US2008/0259846(A1) | 2008-10-01 | Gonikberg et al. | Applicant |
| US2008/0261552(A1) | 2008-10-01 | Chung | Applicant |
| US2008/0261640(A1) | 2008-10-01 | Yoshida | Applicant |
| US2008/0262991(A1) | 2008-10-01 | Kapoor et al. | Applicant |
| US2008/0272818(A1) | 2008-11-01 | Ko | Applicant |
| US2008/0279163(A1) | 2008-11-01 | Desai | Applicant |
| US2008/0310067(A1) | 2008-12-01 | Diab et al. | Applicant |
| US2008/0320108(A1) | 2008-12-01 | Murty et al. | Applicant |
| US2009/0005061(A1) | 2009-01-01 | Ward et al. | Applicant |
| US2009/0010210(A1) | 2009-01-01 | Hiertz et al. | Applicant |
| US2009/0137206(A1) | 2009-05-01 | Sherman et al. | Applicant |
| US2009/0143043(A1) | 2009-06-01 | Yoshizaki et al. | Applicant |
| US2009/0168686(A1) | 2009-07-01 | Love et al. | Applicant |
| US2009/0168725(A1) | 2009-07-01 | Mishra | Applicant |
| US2009/0170497(A1) | 2009-07-01 | Miao et al. | Applicant |
| US2009/0175250(A1) | 2009-07-01 | Mathur et al. | Applicant |
| US2009/0190541(A1) | 2009-07-01 | Abedi | Applicant |
| US2009/0196210(A1) | 2009-08-01 | Desai | Applicant |
| US2009/0202013(A1) | 2009-08-01 | Sebastian | Applicant |
| US2009/0209288(A1) | 2009-08-01 | Rofougaran | Applicant |
| US2009/0239471(A1) | 2009-09-01 | Tran et al. | Applicant |
| US2009/0245133(A1) | 2009-10-01 | Gupta et al. | Applicant |
| US2009/0245279(A1) | 2009-10-01 | Wan et al. | Applicant |
| US2009/0247217(A1) | 2009-10-01 | Hsu et al. | Applicant |
| US2009/0268652(A1) | 2009-10-01 | Kneckt et al. | Applicant |
| US2009/0280762(A1) | 2009-11-01 | Park et al. | Applicant |
| US2009/0285264(A1) | 2009-11-01 | Aldana et al. | Applicant |
| US2009/0291640(A1) | 2009-11-01 | Bhattad et al. | Applicant |
| US2009/0311961(A1) | 2009-12-01 | Banerjea | Applicant |
| US2009/0312027(A1) | 2009-12-01 | Foschini et al. | Applicant |
| US2009/0321056(A1) | 2009-12-01 | Ran et al. | Applicant |
| US2010/0009675(A1) | 2010-01-01 | Wijting et al. | Examiner |
| US2010/0011231(A1) | 2010-01-01 | Banerjea et al. | Applicant |
| US2010/0029325(A1) | 2010-02-01 | Wang et al. | Applicant |
| US2010/0052796(A1) | 2010-03-01 | Menkhoff | Applicant |
| US2010/0061244(A1) | 2010-03-01 | Meier et al. | Applicant |
| US2010/0069112(A1) | 2010-03-01 | Sun et al. | Applicant |
| US2010/0080319(A1) | 2010-04-01 | Blocher et al. | Applicant |
| US2010/0082957(A1) | 2010-04-01 | Iwata | Applicant |
| US2010/0097952(A1) | 2010-04-01 | McHenry et al. | Applicant |
| US2010/0103867(A1) | 2010-04-01 | Kishiyama et al. | Applicant |
| US2010/0130129(A1) | 2010-05-01 | Chang et al. | Applicant |
| US2010/0138549(A1) | 2010-06-01 | Goel et al. | Applicant |
| US2010/0165896(A1) | 2010-07-01 | Gong et al. | Applicant |
| US2010/0216497(A1) | 2010-08-01 | Kawasaki | Applicant |
| US2010/0238793(A1) | 2010-09-01 | Alfano et al. | Applicant |
| US2010/0248734(A1) | 2010-09-01 | Yamazaki et al. | Applicant |
| US2010/0283654(A1) | 2010-11-01 | Waheed et al. | Applicant |
| US2010/0303026(A1) | 2010-12-01 | Chaudhri et al. | Applicant |
| US2010/0316027(A1) | 2010-12-01 | Rick et al. | Applicant |
| US2010/0322213(A1) | 2010-12-01 | Liu et al. | Applicant |
| US2011/0002226(A1) | 2011-01-01 | Bhatti | Applicant |
| US2011/0007675(A1) | 2011-01-01 | Chiou et al. | Applicant |
| US2011/0009074(A1) | 2011-01-01 | Hsu et al. | Applicant |
| US2011/0053522(A1) | 2011-03-01 | Rofougaran et al. | Applicant |
| US2011/0097998(A1) | 2011-04-01 | Ko et al. | Applicant |
| US2011/0103363(A1) | 2011-05-01 | Bennett | Applicant |
| US2011/0161697(A1) | 2011-06-01 | Qi et al. | Applicant |
| US2011/0164538(A1) | 2011-07-01 | Karr et al. | Applicant |
| US2011/0194519(A1) | 2011-08-01 | Habetha | Applicant |
| US2012/0025921(A1) | 2012-02-01 | Yang et al. | Applicant |
| US2012/0099476(A1) | 2012-04-01 | Mahaffy | Applicant |
| US2012/0276938(A1) | 2012-11-01 | Wagholikar et al. | Applicant |
| US2013/0045688(A1) | 2013-02-01 | Banerjea | Applicant |
| US2013/0057344(A1) | 2013-03-01 | Touzard et al. | Applicant |
| US2013/0176903(A1) | 2013-07-01 | Bijwe | Applicant |
| CN102067689 | 2011-05-01 | Applicant | |
| EP1860827 | 2007-11-01 | Applicant | |
| JP2006174162 | 2006-06-01 | Applicant | |
| JP200728568 | 2007-02-01 | Applicant | |
| JP2007028568 | 2007-02-01 | Applicant | |
| WO-0178252 | 2001-10-01 | Applicant | |
| WO-02082751 | 2002-10-01 | Applicant | |
| WO-02091623 | 2002-11-01 | Applicant | |
| WO-2006043956 | 2006-04-01 | Applicant | |
| WO-2006090254 | 2006-08-01 | Applicant | |
| WO-2007008981 | 2007-01-01 | Applicant | |
| WO-2007064822 | 2007-06-01 | Applicant | |
| WO-2008707777 | 2008-06-01 | Applicant | |
| WO-2009101567 | 2009-08-01 | Applicant | |
| WO-2011056878 | 2011-05-01 | Applicant | |
| WO-2013104989 | 2013-07-01 | Applicant | |
| WO-2013119810 | 2013-08-01 | Applicant |
Non-Patent Literature (102)
- Eun-Sun, et al.,“A Power Control MAC Protocol for Ad Hoc Networks”, Wireless Networks; The Journal of Mobile Communication, Computation, and Information, vol. 11, No. 1-2,Kluwer Academic Publishers, Jan. 1, 2005, pp. 55-66.Applicant
- “Advisory Action”, U.S. Appl. No. 12/190,251, Dec. 7, 2011, 3 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/534,361, Feb. 29, 2012, 13 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/190,251, Sep. 13, 2011, 15 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/323,292, Aug. 24, 2012, 26 pages.Applicant
- “Foreign Office Action”, European Patent Application No. 09789754.0, Jul. 12, 2012, 4 pages.Applicant
- “Foreign Office Action”, Japanese Application No. 2011-513586, Oct. 23, 2012, 7 pages.Applicant
- “Foreign Office Action”, EP Application No. 09789754.0, May 17, 2011, 8 pages.Applicant
- “Information Technology—Telecommunications and Information Exchange Between systems—Local and Metropolitan Area Networks—Specific Requirements”, IEEE Standard, Aug. 1, 2005, pp. 1-60.Applicant
- “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, IEEE Standard 802.11h-2003 (Amendment to IEEE Std 802.11-1993), Oct. 14, 2003, 80 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/534,361, Oct. 12, 2011, 11 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/190,251, Mar. 29, 2012, 11 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/759,336, Oct. 4, 2012, 13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/323,292, Dec. 21, 2011, 17 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/478,446, Dec. 28, 2011, 17 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/190,240, Jan. 6, 2012, 7 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/190,251, Mar. 29, 2011, 8 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/190,240, May 16, 2012, 4 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/190,251, Oct. 4, 2012, 6 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/478,446, Jun. 14, 2012, 6 pages.Applicant
- “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications”, Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—,IEEE, Apr. 2003, pp. 1-69.Applicant
- “PCT Search Report”, Application No. PCT/US2009/046289, Oct. 29, 2009, 13 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/759,336, Feb. 25, 2013, 11 pages.Applicant
- “Foreign Office Action”, Chinese Application No. 200980122587.0, Feb. 21, 2013, 17 pages.Applicant
- “Foreign Office Action”, European Patent Application No. 09789754.0, Mar. 11, 2013, 4 Pages.Applicant
- “Foreign Office Action”, Japanese Application No. 2011-513586, Apr. 9, 2013, 4 Pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/656,502, Feb. 21, 2013, 6 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/604,563, Apr. 5, 2013, 6 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 13/656,502, Jun. 25, 2013, 11 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/534,361, Feb. 14, 2013, 12 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/323,292, Jun. 28, 2013, 8 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/759,336, May 3, 2013, 9 pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/759,336, Jun. 5, 2013, 2 pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/759,336, Jun. 18, 2013, 2 pages.Applicant
- Jung, et al.,“A Power Control MAC Protocol for Ad Hoc Networks”, Wireless Networks; The Journal of Mobile Communication, Computation and Information, Kluwer Academic Publishers vol. 11, No. 1-2, Jan. 1, 2005, 12 Pages.Applicant
- “Foreign Notice of Allowance”, Japanese Application No. 2011-513586, Jul. 16, 2013, 2 pages.Applicant
- Qiao, et al.,“Interference Analysis and Transmit Power Control in IEEE 802.11a/h Wireless LANs”, IEEE/ACM Transactions on Networking, IEEE/ACM, New York, NY, US, vol. 15. No. 5, Oct. 1, 2007, 14 Pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 13/604,563, Sep. 26, 2013, 5 pages.Applicant
- Tinnirello, et al.,“Revisit of RTS/CTS Exchange in High-Speed IEEE 802.11 Networks”, World of Wireless Mobile and Multimedia Networks. 2005. Wowmom 2005. Sixth IEEE International Symposium on a Taormina-Giardini Naxos, Italy Jun. 13-16, 2005 Piscataway, NJ, USA,IEEE, Los Alamitos, CA, USA, Jun. 13, 2005, 10 Pages.Applicant
- “Search Report”, European Application No. 13169350.9, Aug. 13, 2013, 10 Pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/759,336, Aug. 14, 2013, 2 pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/323,292, Oct. 7, 2013, 2 pages.Applicant
- “Foreign Office Action”, Chinese Application No. 200980122587.0, Sep. 10, 2013, 11 Pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/429,090, Oct. 24, 2013, 13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/479,124, Sep. 27, 2013, 14 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/883,054, Nov. 22, 2013, 18 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/542,845, Oct. 23, 2013, 29 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/249,740, Oct. 16, 2013, 9 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/099,169, Oct. 4, 2013, 9 pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/323,292, Oct. 17, 2013, 2 pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/358,955, Oct. 11, 2013, 3 pages.Applicant
- “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol Specification (Release 10)”, 3GPP TS 36.331; V10.5.0; 3GPP Organizational Partners, 2012, 302 pages.Applicant
- “Advisory Action”, U.S. Appl. No. 12/646,721, Aug. 13, 2013, 3 pages.Applicant
- Mazzanti, et al.,“Analysis and Design of Injection-Locked LC Dividers for Quadrature Generation”, IEEE Journal of Solid-State Circuits, vol. 39, No. 9, Sep. 2004, pp. 1425-1433.Applicant
- “Draft Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements”, IEEE P802.11s/D1.03, Apr. 2007, 251 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/358,955, Mar. 18, 2013, 12 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/646,802, Nov. 15, 2012, 15 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/646,721, Jun. 6, 2013, 16 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/484,563, Apr. 24, 2012, 18 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/616,454, Apr. 11, 2012, 19 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/186,429, Oct. 13, 2011, 23 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/542,845, Sep. 25, 2012, 23 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/358,955, Feb. 17, 2012, 26 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/487,425, May 3, 2012, 9 pages.Applicant
- “Further Higher Data Rate Extension in the 2.4 GHz Band”, IEEE P802.11g/D8.2,DRAFT Supplement to STANDARD [for] Information Technology, Apr. 2003, 69 pages.Applicant
- Haas, et al.,“Gossip-Based Ad Hoc Routing”, IEEE/ACM Transactions on Networking, vol. 14, No. 3, Jun. 2006, pp. 479-491.Applicant
- “IEEE 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 Amendment”, IEEE Computer Society, Oct. 14, 2010, pp. 12-18, 23, 65-68.Applicant
- “International Search Report and Written Opinion”, PCT Application PCT/US2012/035597, Aug. 6, 2012, 13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/167,841, Jul. 15, 2011, 10 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/099,169, Mar. 28, 2013, 12 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/484,563, Oct. 4, 2011, 13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/732,036, Aug. 9, 2012, 13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/646,721, Nov. 7, 2012, 15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/646,721, May 10, 2012, 15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/235,333, Jun. 28, 2011, 16 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/646,802, Mar. 29, 2012, 16 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/186,429, Apr. 25, 2011, 19 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/542,845, Apr. 4, 2012, 19 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/358,955, Sep. 6, 2011, 24 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/358,955, Aug. 20, 2012, 33 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/487,425, Jan. 12, 2012, 7 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/616,454, Dec. 22, 2011, 8 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/249,740, Mar. 26, 2013, 9 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/167,841, Nov. 25, 2011, 11 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/616,454, Aug. 22, 2012, 4 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/235,333, Nov. 15, 2011, 5 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/484,563, Jul. 9, 2012, 6 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/716,569, Apr. 19, 2012, 7 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/732,036, Feb. 21, 2013, 8 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/358,955, Jul. 1, 2013, 8 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/186,429, Jun. 6, 2013, 9 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/487,425, Jul. 26, 2013, 9 pages.Applicant
- “Part 11: Wireless LN Medium Access Control (MAC) and Physical Layer (PHY) specifications”, IEEE Std 802.11b-1999/Cor 1-2001,Amendment 2: Higher-speed Physical Layer (PHY) extension in the 2.4 GHz band, Nov. 7, 2001, 23 pages.Applicant
- “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications”, IEEE Std 802.11a-1999,High-speed Physical Layer in the 5 GHz Band, 1999, 91 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2013/025144, Jun. 5, 2013, 10 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2011/054358, Dec. 16, 2011, 13 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/IB2013/000390, Aug. 21, 2013, 19 Pages.Applicant
- “Restriction Requirement”, U.S. Appl. No. 12/167,841, May 12, 2011, 6 pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/186,429, Jul. 10, 2013, 2 pages.Applicant
- “Supplemental Notice of Allowance”, U.S. Appl. No. 12/716,569, Jul. 23, 2012, 2 pages.Applicant
- Mujtaba “TGn Sync Proposal Technical Specification”, IEEE 802.11-04/0889r6,This document presents the technical specification for the MAC and the PHY layer of the TGn Sync proposal to IEEE 802.11 TGn, May 18, 2005, pp. 1-131.Applicant
- Mujtaba “TGn Sync Proposal Technical Specification”, IEEE 802.11-04/Wireless LANs, May 2005, pp. 1-131.Applicant