This present disclosure claims priority to U.S. Provisional Patent Application Ser. No. 61/490,452 filed May 26, 2011, the disclosure of which is incorporated by reference herein in its entirety.
The background description provided herein is for the purpose of generally presenting the context of the disclosure. Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims in this disclosure and are not admitted to be prior art by inclusion in this section.
Computing devices often communicate with peripheral devices or other computing devices via a wireless medium to exchange data or obtain services. To do so, computing devices often join or form a wireless network on a particular channel of the wireless medium in order to facilitate access of data or services of other devices. A computing device managing a wireless network typically invites these other devices to join a new or existing wireless network. Inviting another device to join a network, however, can be time intensive because inviting another device involves scanning different channels of the wireless medium (i.e., going off-channel) and transmitting invitation frames to the other device.
A computing device managing a wireless network that includes different generations of wireless devices (e.g., legacy devices), however, may not be able to go off-channel due to communication timing constraints. Earlier generations of wireless devices may support limited types or revisions of communication protocols, some of which require almost constant in-channel communication to be maintained by a device managing the wireless network. This in-channel communication may not permit a device managing a wireless network to go off-channel for an amount of time sufficient to communicate with other devices. As such, a computing device managing a wireless network that includes a legacy device may be prevented from inviting other devices to join the wireless network.
This summary is provided to introduce subject matter that is further described below in the Detailed Description and Drawings. Accordingly, this Summary should not be considered to describe essential features nor used to limit the scope of the claimed subject matter.
A method is described for transmitting a first frame on a first channel of a wireless medium that is effective to prevent a member device of a peer-to-peer group from attempting to access the wireless medium for a duration of time, transmitting a second frame on a second channel of the wireless medium that invites a wireless device operating off the first channel to join the peer-to-peer group, and returning to the first channel after transmitting the second frame to enable a next attempt of the member device to successfully access the wireless medium subsequent an expiration of the duration of time.
Another method is described for transmitting a first frame on a first channel of a wireless medium that is effective to prevent a legacy device of a peer-to-peer group from attempting to access the wireless medium for a duration of time, configuring a wireless interface to communicate on a second channel of the wireless medium, transmitting a second frame on the second channel of the wireless medium that invites a wireless device operating off-channel to join the peer-to-peer group, and configuring the wireless interface to communicate on the first channel of the wireless medium before or about when the duration of time expires effective to permit the legacy device to successfully access the wireless medium subsequent the expiration of the duration of time.
A System-on-Chip (SoC) is described that is configured to transmit a first frame on a first channel of a wireless medium that is effective to prevent a member device of a peer-to-peer group from attempting to access the wireless medium for a duration of time, transmit a second frame on a second channel of the wireless medium that invites a wireless device operating off the first channel to join the peer-to-peer group, and return to the first channel after transmitting the second frame to enable a next attempt of the legacy device to successfully access the wireless medium subsequent an expiration of the duration of time.
The details of one or more implementations are set forth in the accompanying figures and the detailed description below. In the figures, the left-most digit 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 indicate like elements.
Conventional techniques for inviting an off-channel device to join a peer-to-peer group can be limited or prevented when the peer-to-peer group includes a legacy device. This disclosure describes apparatuses and techniques for off-channel device invitation that permit a device managing a peer-to-peer group that includes a legacy device to go off-channel in order to invite other devices to join the peer-to-peer group. By so doing, the other devices operating off-channel can be invited to join the peer-to-peer group without scanning and/or listening to different channels of a wireless medium for these other devices, thereby minimizing an amount of time that the device managing the peer-to-peer group spends off-channel.
The following discussion describes an operating environment, techniques that may be employed in the operating environment, and a System-on-Chip (SoC) in which components of the operating environment can be embodied. In the discussion below, reference is made to the operating environment by way of example only.
Operating Environment
Each manager device 102 includes a wireless transmitter 114 and a wireless receiver 116 for providing a wireless interface to handle various communication protocols, such as for example IEEE 802.11-2007, IEEE 802.11k, IEEE 802.11n, and the like. Transmitter 114 and receiver 116 may be separate (shown) or combined (not shown) and may be hardware combined with or separate from firmware or software. Manager devices 102 also include processor(s) 118, computer-readable storage media 120 (CRM 120), and peer-to-peer manager 122 (P2P manager 122), which, in one implementation, is embodied on CRM 120. CRM 120 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useful to store data of applications and/or an operating system of the manager device 102. How P2P manager 122 is implemented and used varies and is described below.
Manager devices 102 may be configured as client devices in a wireless network having an infrastructure-based topology, such as connecting to an access point (AP) to obtain internet connectivity. Alternately or additionally, manager devices 102 may be configured to implement AP-like functionality when managing a peer-to-peer group of other devices as described below. In some cases, a manager device 102 may concurrently associate with an AP and a peer-to-peer group extending services or functionalities of either network to entities of both networks. In other cases, a manager device 102 may be configured as one of member devices 104 in a peer-to-peer group or network having another manager device 102.
Member devices 104 include multi-function printer 124, internet-protocol (IP) enabled television 126 (IP TV 126), network-attached storage (NAS) 128, and wirelessly-enabled camera 130 (camera 130). Other member devices contemplated include various computing devices and/or accessory devices, such as smart-phones, video cameras, digital picture frames, scanners, displays, speakers, human-input devices, and so on. Each member device 104 may provide services (e.g., capabilities or functions) or data that are accessible to a communicatively coupled manager device 102 or other member device 104. For example, tablet computer 110 is able to access print functions of multi-function printer 124 when connected wirelessly. Any of these devices may act as an access point, a peer-to-peer group member, or a client station, and may be dynamically configured to do so.
Each member device 104 includes wireless transceiver 132, which provides a wireless interface to handle various communication protocols, such as those mentioned above and elsewhere herein. Although shown as a single transceiver, wireless transceiver 132 may be implemented as a separate transmitter and receiver, and may be hardware combined with or separate from firmware or software. Member devices 104 also include member processor(s) 134, member computer-readable storage media 136 (member CRM 136), and peer-to-peer module 138 (P2P module 138), which, in one implementation, is embodied on member CRM 136. Member CRM 136 may include any suitable memory or storage device such as static RAM (SRAM), ROM, or Flash memory useful to store data of applications and/or an operating system of the member device 104.
P2P module 138 enables member device 104 to understand and implement peer-to-peer networking communications and functionalities, such as those defined by the Wireless Fidelity Alliance Peer-to-Peer Specification. For example, P2P module 138 may enable a member device 104 to transmit various frames, such as probe request frames, probe response frames, invitation request frames, or invitation response frames, which enable a member device 104 to join a peer-to-peer group on a same or different channel of a wireless medium.
When within range of laptop computer 112, member devices 104 may join P2P group 202, such as NAS 128 via wireless connection 212 and camera 130 via wireless connection 214. P2P group 202 also includes legacy member device 216 (legacy device 216), here illustrated as printer 218 associated with laptop computer 112 via wireless connection 220. Legacy device 216 may be configured similarly as member devices 104, having a wireless transceiver 132, member processor 134, and member CRM 136. Legacy device 216 differs from other member devices 104, however, in that legacy device 216 includes legacy station module 222 (legacy STA module 222). Legacy STA module 222 enables legacy device 216 to be configured as a client station of a wireless network. Legacy STA module 222, however, may not support peer-to-peer networking communication protocols or capabilities that are enabled by P2P module 138 of member devices 104. For instance, legacy device 216 may not understand P2P networking frames, such as notice-of-absence (NoA) frames, invitation frames, and the like. For example, legacy device 216 may not be capable of understanding P2P Information Elements (IEs) within frames such as probe requests, probe responses, beacons, and so on. Although legacy device 216 may not understand P2P communications, a manager device 102 (e.g., laptop computer 112) may implement AP-like functionality enabling legacy device 216 to join P2P group 202. Implementing this AP-like functionality for legacy devices may increase an amount of time a manager device 102 remains in-channel to communicate with the legacy devices.
As described above, various member devices 104 may join a peer-to-peer group or peer-to-peer network. Joining a peer-to-peer group may be initiated by either manager device 102 or member device 104, as either type of device may transmit probe requests on various channels of a wireless medium in an attempt to find other devices. In some cases, however, a peer-to-peer group may include a legacy device 216 that does not understand peer-to-peer networking communication protocols. Thus, manager device 102 (e.g., group owner) of the peer-to-peer group may be prevented from going off-channel, as a requirement to maintain in-channel communication with legacy device 216 may not yield sufficient time to do so. In such a case, techniques of off-channel device invitation permit manager device 102 to invite an off-channel device to join a peer-to-peer network by minimizing an amount of time spent off-channel. For example, laptop computer 112 can invite IP TV 126 to join P2P group 202 via wireless connection 224. These are but a few example aspects of implementing techniques of off-channel device association which are described below.
Techniques of Off-Channel Device Invitation
The following discussion describes techniques of off-channel device invitation. These techniques can be implemented using the previously described environments or entities, such as P2P manager 122 of
At 302, a first frame effective to prevent a member device of a peer-to-peer group from accessing a wireless medium is transmitted on a first channel of a wireless medium. In some cases, the member device may be a legacy device that is not capable of understanding peer-to-peer networking communications. The first frame may be a clear-to-send-to-self (CTS-to-self) frame or a null frame. In such cases, these frames may indicate that the wireless medium is unavailable for a particular amount of time. For example, a CTS-to-self frame or a null frame may indicate that the wireless medium is unavailable for up to 32 milliseconds. As the member device may not understand peer-to-peer networking communications, a peer-to-peer management frame, such as a notice-of-allowance (NoA) frame, may not be sufficient to prevent a device from attempting to access the wireless medium.
As an example, consider laptop computer 112 in the context of
At 304, a second frame inviting a wireless device operating off the first channel (e.g., off-channel) to join the peer-to-peer network is transmitted on a second channel of the wireless medium. This second frame may be transmitted without scanning the second channel for wireless devices. For instance, the second frame may be transmitted without listening to the second channel or broadcasting probe requests on the second channel. In some cases, the second frame may be a peer-to-peer management frame, such as an invitation request frame. In such cases, the wireless device may respond to the invitation request frame with an acknowledgment or an invitation response frame. The second channel may reside in a different frequency band of the wireless medium than the first channel. The second channel of the wireless medium may be randomly selected, iteratively selected, or directly selected if known, such as received by user input, referenced from a look-up table, or remembered from having previously been associated with a particular device.
In the context of the present example, assume that IP TV 126 is currently operating on channel 164 of the 5 GHz band as defined by IEEE 802.11. Also assume here that laptop computer 112 has previously associated with IP TV 126 and therefore knows that IP TV 126 can be found on channel 164. Here, laptop computer 112 transmits a peer-to-peer invitation request frame on channel 164 without scanning channel 164 for wireless devices. Responding to the invitation frame, IP TV 126 indicates to laptop computer 112 that it will join the peer-to-peer group on channel 6 of the 2.4 GHz band.
At 306, the first channel of the wireless medium is returned to enabling a next attempt of the member device to successfully access the wireless medium. The member device may attempt to access the wireless medium after a duration of time expires, such as the duration indicated by the first frame transmitted at 302. In some cases, the first channel of the wireless medium is returned to in less than or about 32 milliseconds, which may be about a maximum amount of time that a CTS-to-self frame or null frame may indicate.
Continuing the ongoing example, laptop computer 112 returns to channel 6 of the 2.4 GHz band from channel 164 of the 5 GHz band after transmitting the invitation request frame. Here, laptop computer 112 returns to channel 6 in less than 32 milliseconds since transmitting the null frame. Thus, laptop computer 112 is able to manage P2P group 202 when devices of the network begin requesting communicative access after the duration of time (e.g., 32 milliseconds) indicated by the null frame expires.
As another example, assume that laptop computer 112 had transmitted a frame indicating that access to wireless medium associated with P2P group 202 will be unavailable for 100 milliseconds. Laptop computer 112 would then have 100 milliseconds to transmit frames inviting off-channel devices to join P2P group 202 before returning to P2P group 202. In such a case, laptop computer 112 may transmit frames inviting off-channel devices on one or more different channels during the 100 milliseconds of off-channel time.
From operation 306, method 300 may return to operation 302 or proceed to operation 308. Returning to 302, another attempt can be made to invite an off-channel device to join the peer-to-peer group by repeating operations 302, 304, and 306. For instance, the operations may be repeated when another device is not on a particular channel of the wireless medium during an iteration of the method. Each iteration of method 300 may invite wireless devices from another different channel of a wireless medium until a desired device is added to the peer-to-peer group. For example, each iteration of method 300 may attempt to invite an off-channel device from a different channel or repeatedly from a same channel. In the case of repeated attempts on the same channel, after a particular number of attempts have been made (e.g., 5 to 10 attempts), method 300 may then proceed to another different channel.
At 308, the wireless device is configured for operation in the peer-to-peer group on the first channel of the wireless medium. Configuring the wireless device may include associating with and/or authenticating the wireless device to enable the device to communicate within the peer-to-peer network. Once configured for operation in the peer-to-peer network, data or services of the wireless device may be accessed by a device managing the peer-to-peer network or other member devices of the peer-to-peer network.
Concluding the present example, laptop computer 112 associates with, and subsequently authenticates, IP TV 126 via wireless connection 224. Once authenticated, IP TV 126 may display content of other devices of P2P group 202, such as laptop computer 112 and camera 130. Additionally, IP TV 126 may stream, download, and/or display content from Internet 206, as laptop computer 112 provides internet connectivity to the devices of P2P group 202.
At 402, a first frame is transmitted on a first channel of a wireless medium effective to prevent a legacy device of a peer-to-peer group from accessing the wireless medium for a duration of time. The first frame may be transmitted via a wireless interface configured to communicate on the first channel of the wireless medium. The legacy device, although part of the peer-to-peer group, may not understand peer-to-peer networking communications.
The peer-to-peer group may include peer-to-peer networking-enabled devices that understand peer-to-peer networking communications. In some cases, the first frame transmitted is a CTS-to-self frame or a null frame that can be understood by most or all member devices of the peer-to-peer group including legacy devices. In such cases, the CTS-to-self frame or the null frame may indicate that the wireless medium is unavailable for up to 32 milliseconds
As an example, consider laptop computer 112 again in the context shown in
At 404, a wireless interface is configured to communicate on a second channel of the wireless medium. Configuring the wireless interface to communicate on another channel may consume up to or about 2 to 2.5 milliseconds of time. In some cases the second channel may reside in a same frequency band of the wireless medium as the first channel. In other cases, the first and the second channels may reside in different frequency bands of the wireless medium. Continuing the ongoing example, P2P manager 122 reconfigures wireless transmitter 114 and wireless receiver 116 of laptop computer 112 to communicate on channel 11 as illustrated at 504.
At 406, a second frame inviting a wireless device operating off-channel to join the peer-to-peer group is transmitted on the second channel of the wireless medium. This second frame may be transmitted without scanning the second channel for wireless devices. In some cases, the second frame may be a peer-to-peer management frame, such as an invitation request frame. Transmitting the second frame may consume about 34 microseconds associated with a distributed coordination function interspace frame space (DIFS) interval. Additionally, the wireless device may respond to the invitation frame with an acknowledgment. Receiving this acknowledgement may consume about 16 microseconds of time associated with a short interspace frame space (SIFS) interval.
Continuing the ongoing example, P2P manager 112 causes laptop computer 112 to transmit invitation request frame 506 to IP TV 126 on channel 11 of the 2.4 GHz band. Here, laptop computer 112 transmits invitation request frame 506 without scanning channel 11 for other computing devices. Also assume here that IP TV 126 responds to invitation request frame 506 with acknowledgement 508 (ACK 508). Although not necessary, receiving ACK 508 indicates to laptop computer 112 that invitation request frame 506 was received by another device, in this case IP TV 126.
Optionally at 408, a third frame indicating that the wireless device will join the peer-to-peer group is received on the second channel of the wireless medium. The third frame may be an invitation response frame or another peer-to-peer networking frame indicating such. In some cases, the third frame may include other information such as an indication of a status of the wireless device, services provided by the device, a channel the device intends to move to, and so on. Receiving this third frame may consume about 34 microseconds associated with a DIFS interval. Additionally, an acknowledgement may be transmitted to the wireless device in response to receiving the frame. Transmitting this acknowledgement may consume about 16 microseconds of time associated with a SIFS interval.
In the context of the present example, laptop computer 112 receives invitation response frame 510 from IP TV 126 on channel 11. Invitation response frame 510 indicates to laptop computer 112 that IP TV 126 will join P2P group 202 on channel 6. Although not necessary, laptop computer 112 acknowledges receiving invitation response frame 510 by transmitting ACK 512 back to IP TV 126.
At 410, the wireless interface is configured to communicate on the first channel of the wireless medium. Configuring the wireless interface to communicate on the first channel may enable a next attempt of the legacy device to access the wireless medium to be granted. As described above, configuring the wireless interface to communicate on another channel may consume up to or about 2 to 2.5 milliseconds of time. The wireless interface can be configured to communicate on the first channel before or about when a duration of time expires, during which the legacy device is prevented from accessing the wireless medium. In some cases, returning to the first channel may be responsive to receiving the third frame at operation 408. In such cases, returning to the first channel may occur immediately after receiving the third frame, or shortly thereafter. Returning to the first channel in such a manner may be effective to permit a device managing a peer-to-peer group to go off-channel for device invitation while the legacy device is prevented from accessing the wireless medium.
By way of example, after transmitting a CTS-to-self frame having a duration of 32 milliseconds, operations 404, 406, 408, and 410 may be completed before a next attempt of a legacy device to access the wireless medium. Configuring the wireless interface at operations 404 and 410 may consume about or up to 5 milliseconds (2×2.5 milliseconds). Transmitting an invitation request frame and receiving an acknowledgment at operation 406 may consume about or up to 50 microseconds (DIFS interval+SIFS interval). Receiving an invitation response frame and transmitting an acknowledgment at operation 408 may consume about or up to 50 microseconds (DIFS interval+SIFS interval). Thus, operations 404, 406, 408, and 410 may complete in about or less than 6 milliseconds (5 milliseconds+100 microseconds) yielding at least 24 milliseconds of time in which to complete an invitation exchange or handshake procedure.
Continuing the ongoing example, P2P manager 122 configures wireless transmitter 114 and wireless receiver 116 of laptop computer 112 to communicate on channel 6 as illustrated at 514. Here, laptop computer 112 has spent time 516 off-channel inviting IP TV 126 to join P2P group 202. Time 516 may be about or less than the amount of time that CTS-to-self frame 502 prevents other devices, including printer 218, of P2P group 202 from attempting to access the wireless medium. Assume here that time 516 is about 30 milliseconds during which laptop computer 112 goes off-channel to invite IP TV 126 to join P2P group 202. As the duration of CTS-to-self frame 502 is 32 milliseconds, laptop computer 112 returns to channel 6 with time sufficient to enable communication within P2P group 202 (P2P activity 518) before any devices of the group attempt to access the wireless medium.
From operation 410, method 400 may return to operation 402 or proceed to operation 412. Returning to 402, wireless devices operating on other channels of the wireless medium may be invited to join the peer-to-peer group by repeating operations 402, 404, 406, 408, and/or 410 as necessary. For instance, the operations may be repeated when a frame indicating that a wireless device will join the peer-to-peer group is not received at operation 408 of a previous iteration of the method. Each iteration of method 400 may invite wireless devices from different channels of a wireless medium until a desired device is found. For example, each iteration of method 400 may attempt to invite an off-channel device from a different channel or repeatedly from a same channel. In the case of repeated attempts on the same channel, after a particular number of attempts have been made (e.g., 5 to 10 attempts), method 400 may then proceed to another different channel.
At 412, an association with the wireless device is established to add the wireless device to the peer-to-peer group. In some cases, the wireless device may be authenticated using any suitable security or authentication protocol. Once added to the peer-to-peer group, data or services of the wireless device may be accessed by a device managing the peer-to-peer group or other member devices of the peer-to-peer group. Alternately or additionally, the wireless device may access data or services of the peer-to-peer group, such as internet connectivity, multimedia data, media streams, and the like.
Concluding the present example, assume that IP TV 126 has moved to channel 6 to join P2P group 202. Here, laptop computer 112 proceeds with association 520 and authentication 522 of IP TV 126 on channel 6. Once associated and authenticated, IP TV 126 can engage in peer-to-peer communication 524 (P2P communication 524). As such, laptop computer 112 can now access services and data of IP TV 126 for various purposes, such as to display content, play media, and the like.
System-On-Chip
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 provide communicative coupling for a device, such as any of the above-listed devices. 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 wireless communication device that includes SoC 600 can also be implemented with many combinations of differing components. In some cases, these differing components may be configured to implement concepts described herein over a wireless connection or interface.
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 RAM, low-latency nonvolatile memory (e.g., Flash 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, communication components, other hardware, firmware, and/or software.
SoC 600 includes wireless transmitter 114, wireless receiver 116, and P2P manager 122 (embodied as disparate or combined components 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 environment 100 shown in
P2P manager 122, 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. P2P manager 122 may also be provided integral with other entities of the SoC, such as integrated with one or both of I/O logic controller 602 or any packet-based interface within SoC 600. Alternatively or additionally, P2P manager 122 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.
Although the subject matter has been described in language specific to structural features and/or methodological operations, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or operations described above, including orders in which they are performed.
Number | Name | Date | Kind |
---|---|---|---|
4337463 | Vangen | Jun 1982 | A |
5673291 | Dent | Sep 1997 | A |
6320919 | Khayrallah et al. | Nov 2001 | B1 |
6816452 | Maehata | Nov 2004 | B1 |
7239882 | Cook | Jul 2007 | B1 |
7342895 | Serpa et al. | Mar 2008 | B2 |
7551948 | Meier et al. | Jun 2009 | B2 |
7564826 | Sherman et al. | Jul 2009 | B2 |
7595768 | Li et al. | Sep 2009 | B2 |
7599671 | Kopikare et al. | Oct 2009 | B2 |
7626966 | Ruiter et al. | Dec 2009 | B1 |
7711004 | Xu | May 2010 | B2 |
7957340 | Choi et al. | Jun 2011 | B2 |
7966036 | Kojima | Jun 2011 | B2 |
8014329 | Gong | Sep 2011 | B2 |
8072913 | Desai | Dec 2011 | B2 |
8078111 | Jovicic et al. | Dec 2011 | B2 |
8149715 | Goel | Apr 2012 | B1 |
8170002 | Wentink | May 2012 | B2 |
8170546 | Bennett | May 2012 | B2 |
8189506 | Kneckt et al. | May 2012 | B2 |
8229087 | Sumioka et al. | Jul 2012 | B2 |
8254296 | Lambert et al. | Aug 2012 | B1 |
8274894 | Kneckt et al. | Sep 2012 | B2 |
8310967 | Goel | Nov 2012 | B1 |
8340034 | Lee et al. | Dec 2012 | B1 |
8472427 | Wheeler et al. | Jun 2013 | B1 |
8553561 | Chokshi et al. | Oct 2013 | B1 |
20020025810 | Takayama et al. | Feb 2002 | A1 |
20020049854 | Cox et al. | Apr 2002 | A1 |
20030040316 | Stanforth et al. | Feb 2003 | A1 |
20040105401 | Lee | Jun 2004 | A1 |
20040192222 | Vaisanen et al. | Sep 2004 | A1 |
20040233881 | Kang et al. | Nov 2004 | A1 |
20040264396 | Ginzburg et al. | Dec 2004 | A1 |
20040264397 | Benveniste | Dec 2004 | A1 |
20050018641 | Zhao et al. | Jan 2005 | A1 |
20050025104 | Fischer et al. | Feb 2005 | A1 |
20050025174 | Fischer et al. | Feb 2005 | A1 |
20050135360 | Shin et al. | Jun 2005 | A1 |
20050174962 | Gurevich | Aug 2005 | A1 |
20050186962 | Yoneyama et al. | Aug 2005 | A1 |
20050206554 | Yamaura | Sep 2005 | A1 |
20050250528 | Song et al. | Nov 2005 | A1 |
20050254423 | Berghoff | Nov 2005 | A1 |
20050281278 | Black et al. | Dec 2005 | A1 |
20060007863 | Naghian | Jan 2006 | A1 |
20060079232 | Omori et al. | Apr 2006 | A1 |
20060120338 | Hwang et al. | Jun 2006 | A1 |
20060199565 | Ammirata | Sep 2006 | A1 |
20060200862 | Olson et al. | Sep 2006 | A1 |
20060215601 | Vleugels et al. | Sep 2006 | A1 |
20060251198 | Ma et al. | Nov 2006 | A1 |
20060252418 | Quinn et al. | Nov 2006 | A1 |
20060264179 | Bonneville et al. | Nov 2006 | A1 |
20060268756 | Wang et al. | Nov 2006 | A1 |
20060268804 | Kim et al. | Nov 2006 | A1 |
20060282541 | Hiroki | Dec 2006 | A1 |
20060282667 | Kim et al. | Dec 2006 | A1 |
20060286935 | Utsunomiya et al. | Dec 2006 | A1 |
20070010237 | Jones et al. | Jan 2007 | A1 |
20070010247 | Mouna-Kingue et al. | Jan 2007 | A1 |
20070014314 | O'Neil | Jan 2007 | A1 |
20070109973 | Trachewsky | May 2007 | A1 |
20070178888 | Alfano et al. | Aug 2007 | A1 |
20070183443 | Won | Aug 2007 | A1 |
20070206519 | Hansen et al. | Sep 2007 | A1 |
20070206762 | Chandra et al. | Sep 2007 | A1 |
20070223430 | Desai et al. | Sep 2007 | A1 |
20070238482 | Rayzman et al. | Oct 2007 | A1 |
20070242645 | Stephenson et al. | Oct 2007 | A1 |
20070268862 | Singh et al. | Nov 2007 | A1 |
20070286298 | Choi et al. | Dec 2007 | A1 |
20070297388 | Appaji et al. | Dec 2007 | A1 |
20080056201 | Bennett | Mar 2008 | A1 |
20080069034 | Buddhikot et al. | Mar 2008 | A1 |
20080080446 | Chung | Apr 2008 | A1 |
20080095058 | Dalmases et al. | Apr 2008 | A1 |
20080095059 | Chu | Apr 2008 | A1 |
20080130595 | Abdel-Kader | Jun 2008 | A1 |
20080137580 | Axelsson et al. | Jun 2008 | A1 |
20080139212 | Chen et al. | Jun 2008 | A1 |
20080161031 | Tu | Jul 2008 | A1 |
20080170550 | Liu et al. | Jul 2008 | A1 |
20080181154 | Sherman | Jul 2008 | A1 |
20080187003 | Becker | Aug 2008 | A1 |
20080232287 | Shao et al. | Sep 2008 | A1 |
20080259846 | Gonikberg et al. | Oct 2008 | A1 |
20080261640 | Yoshida | Oct 2008 | A1 |
20080262991 | Kapoor et al. | Oct 2008 | A1 |
20080279163 | Desai | Nov 2008 | A1 |
20080320108 | Murty et al. | Dec 2008 | A1 |
20090010210 | Hiertz et al. | Jan 2009 | A1 |
20090137206 | Sherman et al. | May 2009 | A1 |
20090175250 | Mathur et al. | Jul 2009 | A1 |
20090196210 | Desai | Aug 2009 | A1 |
20090239471 | Tran et al. | Sep 2009 | A1 |
20090245133 | Gupta et al. | Oct 2009 | A1 |
20090245279 | Wan et al. | Oct 2009 | A1 |
20090247217 | Hsu et al. | Oct 2009 | A1 |
20090268652 | Kneckt et al. | Oct 2009 | A1 |
20090285264 | Aldana et al. | Nov 2009 | A1 |
20100011231 | Banerjea et al. | Jan 2010 | A1 |
20100029325 | Wang et al. | Feb 2010 | A1 |
20100061244 | Meier et al. | Mar 2010 | A1 |
20100069112 | Sun et al. | Mar 2010 | A1 |
20100130129 | Chang et al. | May 2010 | A1 |
20100138549 | Goel et al. | Jun 2010 | A1 |
20100165896 | Gong et al. | Jul 2010 | A1 |
20100238793 | Alfano et al. | Sep 2010 | A1 |
20100316027 | Rick et al. | Dec 2010 | A1 |
20100322213 | Liu et al. | Dec 2010 | A1 |
20110002226 | Bhatti | Jan 2011 | A1 |
20110007675 | Chiou et al. | Jan 2011 | A1 |
20110009074 | Hsu et al. | Jan 2011 | A1 |
20110097998 | Ko et al. | Apr 2011 | A1 |
20110103363 | Bennett | May 2011 | A1 |
20110161697 | Qi et al. | Jun 2011 | A1 |
20110194519 | Habetha | Aug 2011 | A1 |
20120099476 | Mahaffy et al. | Apr 2012 | A1 |
20120276938 | Wagholikar et al. | Nov 2012 | A1 |
20130176903 | Bijwe | Jul 2013 | A1 |
Number | Date | Country |
---|---|---|
1860827 | Nov 2007 | EP |
2006174162 | Jun 2006 | JP |
WO-2006043956 | Apr 2006 | WO |
WO-2006090254 | Aug 2006 | WO |
WO-2007008981 | Jan 2007 | WO |
WO-2007064822 | Jun 2007 | WO |
WO-20080707777 | Jun 2008 | WO |
WO-2009101567 | Aug 2009 | WO |
WO-2011056878 | May 2011 | WO |
WO-2013104989 | Jul 2013 | WO |
WO-2013119810 | Aug 2013 | WO |
Entry |
---|
“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. |
“Advisory Action”, U.S. Appl. No. 12/646,721, Aug. 13, 2013, 3 pages. |
“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. |
“Final Office Action”, U.S. Appl. No. 12/646,802, Nov. 15, 2012, 15 pages. |
“Final Office Action”, U.S. Appl. No. 12/646,721, Jun. 6, 2013, 16 pages. |
“Final Office Action”, U.S. Appl. No. 12/484,563, Apr. 24, 2012, 18 pages. |
“Final Office Action”, U.S. Appl. No. 12/616,454, Apr. 11, 2012, 19 pages. |
“Final Office Action”, U.S. Appl. No. 12/186,429, Oct. 13, 2011, 23 pages. |
“Final Office Action”, U.S. Appl. No. 12/542,845, Sep. 25, 2012, 23 pages. |
“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. |
Haas, et al.,“Gossip-Based Ad Hoc Routing”, IEEE/ACM Transactions on Networking, vol. 14, No. 3, Jun. 2006, pp. 479-491. |
“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. |
“International Search Report and Written Opinion”, PCT Application PCT/US2012/035597, Aug. 6, 2012, 13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/167,841, Jul. 15, 2011, 10 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/099,169, Mar. 28, 2013, 12 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/673,363, Nov. 29, 2013, 12 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/429,090, Oct. 24, 2013, 13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/484,563, Oct. 4, 2011, 13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/732,036, Aug. 9, 2012, 13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/646,721, Nov. 7, 2012, 15 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/646,721, May 10, 2012, 15 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/646,802, Mar. 29, 2012, 16 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/186,429, Apr. 25, 2011, 19 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/542,845, Apr. 4, 2012, 19 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/542,845, Oct. 23, 2013, 29 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/616,454, Dec. 22, 2011, 8 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/249,740, Mar. 26, 2013, 9 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/249,740, Oct. 16, 2013, 9 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/099,169, Oct. 4, 2013, 9 pages. |
“Notice of Allowance”, U.S. Appl. No. 12/167,841, Nov. 25, 2011, 11 pages. |
“Notice of Allowance”, U.S. Appl. No. 12/616,454, Aug. 22, 2012, 4 pages. |
“Notice of Allowance”, U.S. Appl. No. 12/484,563, Jul. 9, 2012, 6 pages. |
“Notice of Allowance”, U.S. Appl. No. 12/716,569, Apr. 19, 2012, 7 pages. |
“Notice of Allowance”, U.S. Appl. No. 12/732,036, Feb. 21, 2013, 8 pages. |
“Notice of Allowance”, U.S. Appl. No. 12/186,429, Jun. 6, 2013, 9 pages. |
“Part 11: Wireless LAN 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. |
“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. |
“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. |
“PCT Search Report and Written Opinion”, Application No. PCT/US2013/025144, Jun. 5, 2013, 10 pages. |
“PCT Search Report and Written Opinion”, Application No. PCT/US2011/054358, Dec. 16, 2011, 13 pages. |
“PCT Search Report and Written Opinion”, Application No. PCT/IB2013/000390, Aug. 21, 2013, 19 Pages. |
“Restriction Requirement”, U.S. Appl. No. 12/167,841, May 12, 2011, 6 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/186,429, Jul. 10, 2013, 2 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/716,569, Jul. 23, 2012, 2 pages. |
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. |
Mujtaba “TGn Sync Proposal Technical Specification”, IEEE 802.11-04 / Wireless LANs, May 2005, pp. 1-131. |
“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 1: Radio Resource Measurement of Wireless LANs; IEEE Std 802.11k—2008, Jun. 12, 2008, 244 pages. |
“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; IEEE Std. 802.11-2012, Mar. 29, 2012, 2793 pages. |
“Introduction to 802.11n Outdoor Wireless Networks”, InscapeData White Paper, Mar. 29, 2011, 9 pages. |
“IEEE Standard for Information Technology—Telecommunications and Information Exchange between Systems—Local and Metropolitan Area Networks—Specific Requirements”, IEEE Std. 802.11-2007, Jun. 12, 2007, 1232 pages. |
“Wi-Fi Peer-to-Peer (P2P) Technical Specification”, Wi-Fi Alliance Technical Committee P2P Task Group; Draft Version 1.14, Jun. 25, 2010, 154 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/722,354, Jan. 17, 2014, 17 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/099,169, Feb. 12, 2014, 11 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/249,740, Mar. 11, 2014, 6 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/673,363, Mar. 24, 2014, 4 pages. |
Number | Date | Country | |
---|---|---|---|
61490452 | May 2011 | US |