Method and apparatus for off-channel invitation

Information

  • Patent Grant
  • 9078108
  • Patent Number
    9,078,108
  • Date Filed
    Monday, May 12, 2014
    10 years ago
  • Date Issued
    Tuesday, July 7, 2015
    8 years ago
Abstract
A wireless medium often supports communications of multiple devices on different respective channels of the wireless medium. In some aspects described herein, a first frame is transmitted on a first channel of a wireless medium effective to prevent a member device of a peer-to-peer group from attempting to access the wireless medium, a second frame inviting a wireless device to join the peer-to-peer group is transmitted on a second channel of the wireless medium, and the first channel of the wireless medium is returned to thereby enabling a next attempt of the member device to access the wireless medium.
Description
BACKGROUND

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.


SUMMARY

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.





BRIEF DESCRIPTION OF THE DRAWINGS

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.



FIG. 1 illustrates an operating environment having wireless devices in accordance with one or more aspects.



FIG. 2 illustrates an example of devices of FIG. 1 communicating in accordance with one or more aspects.



FIG. 3 illustrates a method of inviting an off-channel wireless device to join a peer-to-peer group.



FIG. 4 illustrates a method of configuring a wireless interface for off-channel device invitation.



FIG. 5 illustrates an example flow diagram of communications in accordance with one or more aspects.



FIG. 6 illustrates a System-on-Chip (SoC) environment for implementing aspects of the techniques described herein.





DETAILED DESCRIPTION

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



FIG. 1 illustrates an example operating environment 100 having network manager devices 102 (manager devices 102) and network member devices 104 (member devices 104), each of which are capable of communicating data, packets, and/or frames over a wireless connection 106, such as a wireless-local-area network (WLAN). Manager devices 102 include smart-phone 108, tablet computer 110, and laptop computer 112. Although not shown, other configurations of manager devices 102 are also contemplated such as a desktop computer, server, mobile-internet device (MID), mobile gaming console, mobile hotspot, access point, and so on.


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.



FIG. 2 illustrates an example of device environment 200 that includes a peer-to-peer group 202 (P2P group 202) managed by laptop computer 112. In this particular example, laptop computer 112 manages (e.g., owns) P2P group 202 by managing how and when devices of P2P group 202 communicate with each other. Additionally, access point 204, while operating in an infrastructure mode, provides laptop computer 112 with connectivity to Internet 206 or other networks via backhaul link 208, which may be either wired or wireless (e.g., a wireless-wide-area network). While associated with access point 204 via wireless connection 210, laptop computer 112 may extend access and/or connectivity with Internet 206 to devices of a peer-to-peer group being managed by laptop computer 112, such as member devices of P2P group 202.


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 FIG. 1 embodied on a manager device 102. These techniques include methods illustrated in FIGS. 3 and 4, each of which is shown as a set of operations performed by one or more entities. These methods are not necessarily limited to the orders shown for performing the operations. Further, these methods may be used in conjunction with one another, in whole or in part, whether performed by the same entity, separate entities, or any combination thereof. In portions of the following discussion, reference will be made to operating environment 100 of FIG. 1 and entities of FIG. 2 by way of example. Such reference is not to be taken as limited to operating environment 100 but rather as illustrative of one of a variety of examples.



FIG. 3 depicts a method 300 for inviting an off-channel wireless device to join a peer-to-peer group, including operations performed by P2P manager 122 of FIG. 1.


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 FIG. 2, which shows laptop computer 112 managing P2P group 202. Assume here that P2P group 202 is operating on channel 6 of the 2.4 GHz band as defined by IEEE 802.11. Also assume here that a user decides to display content of laptop computer 112 via IP TV 126, which is not currently associated with P2P group 202. Here, P2P manager 122 transmits a null frame to member devices of P2P group 202 indicating that communicative access to P2P group 202 will be unavailable for 32 milliseconds. This null frame is effective to prevent the member devices of P2P group 202 from attempting to communicate within, or access resources of, P2P group 202 for at least 32 milliseconds.


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.



FIG. 4 depicts a method 400 configuring a wireless interface for off-channel device invitation, including operations performed by P2P manager 122 of FIG. 1.


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 FIG. 2, which shows P2P group 202 including NAS 128, camera 130, and printer 218, which is a legacy device 216. Assume here that P2P group 202 is operating on channel 6 of the 2.4 GHz band. As illustrated in FIG. 5, which illustrates an example communication flow associated with operations method 400, P2P manager 122 causes laptop computer 112 to transmit CTS-to-self frame 502 to members of P2P group 202 (not shown) on channel 6. Assume here that a duration of CTS-to-self frame 502 is set to 32 milliseconds.


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



FIG. 6 illustrates a System-on-Chip (SoC) 600, which can implement various embodiments described above. A SoC can be implemented in any suitable device, such as a video game console, IP enabled television, smart-phone, desktop computer, laptop computer, access point, wireless router, tablet computer, server, network-enabled printer, set-top box, printer, scanner, camera, picture frame, and/or any other type of device that may implement wireless connective technology.


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 FIG. 1 and FIG. 2.


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.

Claims
  • 1. A method comprising: transmitting, via a wireless interface configured to communicate on a first channel of a wireless medium, a first frame effective to prevent a member device of a peer-to-peer group operating on the first channel from attempting to access the wireless medium for a duration of time;configuring the wireless interface to communicate on a second channel of the wireless medium;transmitting, via the wireless interface configured to communicate on the second channel, a second frame inviting a wireless device operating off-channel to join the peer-to-peer group on the first channel;receiving, via the wireless interface configured to communicate on the second channel, a third frame from the wireless device indicating that the wireless device will join the peer-to-peer group on the first channel of the wireless medium; andconfiguring the wireless interface to communicate on the first channel of the wireless medium before or when the duration of time expires effective to grant a next attempt of the member device to access the wireless medium subsequent the expiration of the duration of time.
  • 2. The method as recited in claim 1, further comprising associating, via the wireless interface configured to communicate on the first channel, with the wireless device effective to add the wireless device to the peer-to-peer group operating on the first channel.
  • 3. The method as recited in claim 1, wherein the member device of the peer-to-peer group is a legacy device that is not capable of understanding peer-to-peer networking communications.
  • 4. The method as recited in claim 1, wherein the second frame inviting the wireless device to join the peer-to-peer group transmits without scanning the second channel of the wireless medium for other wireless devices.
  • 5. The method as recited in claim 1, wherein the first frame is a clear-to-transmit-to-self (CTS-to-self) frame or a null frame that indicates the duration of time and the duration of time is less than 32 milliseconds.
  • 6. The method as recited in claim 1, wherein the first channel is in a first frequency band of the wireless medium and the second channel is in a second frequency band of the wireless medium.
  • 7. One or more computer-readable storage devices comprising processor-executable instructions that, responsive to execution by a processor, implement a peer-to-peer manager to: transmit, via a wireless interface configured to communicate on a first channel of a wireless medium, a first frame effective to prevent a member device of a peer-to-peer group operating on the first channel from attempting to access the wireless medium for a duration of time;configure the wireless interface to communicate on a second channel of the wireless medium;transmit, via the wireless interface configured to communicate on the second channel and without scanning the second channel for wireless devices, a second frame inviting a wireless device operating off-channel to join the peer-to-peer group on the first channel;receive, via the wireless interface configured to communicate on the second channel, a third frame from the wireless device indicating that the wireless device will join the peer-to-peer group on the first channel of the wireless medium; andconfigure the wireless interface to communicate on the first channel of the wireless medium before or when the duration of time expires effective to grant a next attempt of the member device to access the wireless medium subsequent the expiration of the duration of time.
  • 8. The one or more computer-readable storage devices as recited in claim 7, wherein the second frame inviting the wireless device to join the peer-to-peer group is a peer-to-peer invitation request frame and the third frame indicating that the wireless device will join the peer-to-peer group is a peer-to-peer invitation response frame.
  • 9. The one or more computer-readable storage devices as recited in claim 7, wherein the first frame is a clear-to-transmit-to-self (CTS-to-self) frame or a null frame.
  • 10. The one or more computer-readable storage devices as recited in claim 7, wherein the first channel and the second channel of the wireless medium are in a same frequency band of the wireless medium.
  • 11. The one or more computer-readable storage devices as recited in claim 7, wherein the peer-to-peer manager is further implemented to configure, via the wireless interface configured to communicate on the first channel, the wireless device for operation in the peer-to-peer group operating on the first channel.
  • 12. The one or more computer-readable storage devices as recited in claim 7, wherein the wireless interface is a wireless local area network (WLAN) interface compliant with an IEEE 802.11 standard.
  • 13. An apparatus comprising: a wireless interface to communicate via a wireless medium; anda peer-to-peer manager to perform operations comprising: transmitting, via the wireless interface and on a first channel of the wireless medium, a first frame effective to prevent a legacy device of a peer-to-peer group from attempting to access the wireless medium for a duration of time, the legacy device not capable of understanding peer-to-peer networking communications;configuring the wireless interface to communicate on a second channel of the wireless medium;transmitting, via the wireless interface and on the second channel, a second frame inviting a wireless device operating off-channel to join the peer-to-peer group on the first channel;configuring the wireless interface to communicate on a third channel of the wireless medium;transmitting, via the wireless interface and on the third channel, a third frame inviting another wireless device operating off-channel to join the peer-to-peer group on the first channel; andconfiguring the wireless interface to communicate on the first channel of the wireless medium before or when the duration of time expires effective to enable the legacy device to access the wireless medium subsequent the expiration of the duration of time.
  • 14. The apparatus as recited in claim 13, wherein the operations further comprise transmitting, prior to configuring the wireless interface to communicate on the first channel, via the wireless interface and in response to not receiving an acknowledgement of the second frame in a predetermined amount of time, a fourth frame inviting the wireless device to join the peer-to-peer group on the first channel.
  • 15. The apparatus as recited in claim 13, wherein the second frame inviting the wireless device to join the peer-to-peer group is transmitted without scanning the second channel of the wireless medium for wireless devices.
  • 16. The apparatus as recited in claim 13, wherein the peer-to-peer group operates in accordance with a Wireless Fidelity Alliance Peer-to-Peer Specification.
  • 17. The apparatus as recited in claim 13, wherein the apparatus comprises one of a smart phone, tablet computer, laptop computer, desktop computer, gaming console, access point, wireless router, or internet-enabled device.
  • 18. The apparatus as recited in claim 13, wherein the second channel or third channel is in a same frequency band of the wireless medium as the first channel.
  • 19. The apparatus as recited in claim 13, wherein the first frame is a clear-to-transmit-to-self (CTS-to-self) frame or a null frame that indicates the duration of time and the duration of time is less than 32 milliseconds.
  • 20. The apparatus as recited in claim 13, wherein the peer-to-peer group operates in accordance with a Wireless Fidelity Alliance Peer-to-Peer Specification.
RELATED APPLICATIONS

This present disclosure is a continuation of and claims priority to U.S. Pat. No. 8,750,278 filed May 23, 2012 which in turn claims priority to U.S. Provisional Patent Application Ser. No. 61/490,452 filed May 26, 2011, the disclosures of which are incorporated by reference herein in their entirety.

US Referenced Citations (307)
Number Name Date Kind
4337463 Vangen Jun 1982 A
4805215 Miller Feb 1989 A
5347234 Gersbach et al. Sep 1994 A
5634207 Yamaji et al. May 1997 A
5673291 Dent Sep 1997 A
5708656 Noneman et al. Jan 1998 A
5847616 Ng et al. Dec 1998 A
5995819 Yamaji et al. Nov 1999 A
6035210 Endo et al. Mar 2000 A
6167245 Welland et al. Dec 2000 A
6285262 Kuriyama Sep 2001 B1
6320919 Khayrallah et al. Nov 2001 B1
6347091 Wallentin et al. Feb 2002 B1
6366622 Brown et al. Apr 2002 B1
6374117 Denkert et al. Apr 2002 B1
6438364 Waite Aug 2002 B1
6452458 Tanimoto Sep 2002 B1
6509777 Razavi et al. Jan 2003 B2
6519461 Andersson et al. Feb 2003 B1
6535037 Maligeorgos Mar 2003 B2
6553229 Dent Apr 2003 B1
6640308 Keyghobad et al. Oct 2003 B1
6650195 Brunn et al. Nov 2003 B1
6675328 Krishnamachari et al. Jan 2004 B1
6741846 Welland et al. May 2004 B1
6741862 Chung et al. May 2004 B2
6754189 Cloutier et al. Jun 2004 B1
6760671 Batcher et al. Jul 2004 B1
6816452 Maehata Nov 2004 B1
6816718 Yan et al. Nov 2004 B2
6934566 Kang et al. Aug 2005 B2
6946950 Ueno et al. Sep 2005 B1
6954708 Rakshani et al. Oct 2005 B2
7079811 Lee et al. Jul 2006 B2
7139540 Wu et al. Nov 2006 B2
7173431 Lo et al. Feb 2007 B1
7206840 Choi et al. Apr 2007 B2
7212798 Adams et al. May 2007 B1
7239882 Cook Jul 2007 B1
7257095 Liu Aug 2007 B2
7286009 Andersen et al. Oct 2007 B2
7298183 Mirzaei et al. Nov 2007 B2
7310023 Cha et al. Dec 2007 B2
7319849 Womac Jan 2008 B2
7342895 Serpa et al. Mar 2008 B2
7355416 Darshan Apr 2008 B1
7377441 Wiklof et al. May 2008 B2
7395040 Behzad Jul 2008 B2
7403018 Lo et al. Jul 2008 B1
7529548 Sebastian May 2009 B2
7551948 Meier et al. Jun 2009 B2
7564826 Sherman et al. Jul 2009 B2
7580397 Arai et al. Aug 2009 B2
7595768 Li et al. Sep 2009 B2
7599671 Kopikare et al. Oct 2009 B2
7616935 Fernandez-Corbaton et al. Nov 2009 B2
7626966 Ruiter et al. Dec 2009 B1
7656205 Chen et al. Feb 2010 B2
7659003 Aoki et al. Feb 2010 B2
7672645 Kilpatrick et al. Mar 2010 B2
7689190 Kerth et al. Mar 2010 B2
7711004 Xu May 2010 B2
7826411 Gonikberg et al. Nov 2010 B2
7849333 Schindler Dec 2010 B2
7876786 Bahl et al. Jan 2011 B2
7881746 Desai Feb 2011 B2
7881755 Mishra et al. Feb 2011 B1
7898948 DiGirolamo et al. Mar 2011 B2
7936714 Karr et al. May 2011 B1
7957340 Choi et al. Jun 2011 B2
7966036 Kojima Jun 2011 B2
7995544 Benveniste Aug 2011 B2
8000715 Melpignano et al. Aug 2011 B2
8014329 Gong Sep 2011 B2
8060017 Schlicht et al. Nov 2011 B2
8072913 Desai Dec 2011 B2
8077652 Thesling Dec 2011 B2
8078111 Jovicic et al. Dec 2011 B2
8081038 Lee et al. Dec 2011 B2
8107391 Wu et al. Jan 2012 B2
8139670 Son et al. Mar 2012 B1
8140075 Watanabe Mar 2012 B2
8149715 Goel et al. Apr 2012 B1
8150328 Chaudhri et al. Apr 2012 B2
8170002 Wentink May 2012 B2
8170546 Bennett May 2012 B2
8187662 Blinn et al. May 2012 B2
8189506 Kneckt et al. May 2012 B2
8203985 Gong et al. Jun 2012 B2
8204015 Chaudhri et al. Jun 2012 B2
8229087 Sumioka et al. Jul 2012 B2
8254296 Lambert Aug 2012 B1
8274894 Kneckt et al. Sep 2012 B2
8275314 Lin Sep 2012 B1
8310967 Goel Nov 2012 B1
8315564 Banerjea Nov 2012 B2
8340034 Lee Dec 2012 B1
8364188 Srinivasan et al. Jan 2013 B2
8369782 Lin et al. Feb 2013 B1
8472427 Wheeler et al. Jun 2013 B1
8472968 Kim Jun 2013 B1
8532041 Lambert et al. Sep 2013 B1
8553561 Chokshi et al. Oct 2013 B1
8571479 Banerjea Oct 2013 B2
8577305 Rossi et al. Nov 2013 B1
8588705 Tsui et al. Nov 2013 B1
8600324 Cousinard et al. Dec 2013 B1
8649734 Lin et al. Feb 2014 B1
8655279 Banerjea Feb 2014 B2
8737370 Wentink May 2014 B2
8750278 Wagholikar et al. Jun 2014 B1
8767771 Shukla et al. Jul 2014 B1
8817662 Mahaffy et al. Aug 2014 B2
8817682 Goel et al. Aug 2014 B1
8861469 Lee et al. Oct 2014 B1
8891497 Vleugels et al. Nov 2014 B1
9036517 Bijwe May 2015 B2
20020025810 Takayama et al. Feb 2002 A1
20020049854 Cox et al. Apr 2002 A1
20020102941 Kuiri et al. Aug 2002 A1
20030040316 Stanforth et al. Feb 2003 A1
20030148750 Yan et al. Aug 2003 A1
20030198200 Diener et al. Oct 2003 A1
20030214430 Husted et al. Nov 2003 A1
20040013128 Moreton et al. Jan 2004 A1
20040063403 Durrant Apr 2004 A1
20040105401 Lee Jun 2004 A1
20040110470 Tsien et al. Jun 2004 A1
20040162106 Monroe et al. Aug 2004 A1
20040192222 Vaisanen et al. Sep 2004 A1
20040198297 Oh et al. Oct 2004 A1
20040214575 Jovanovic Oct 2004 A1
20040233881 Kang et al. Nov 2004 A1
20040264372 Huang Dec 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
20050058151 Yeh Mar 2005 A1
20050064840 Heydari et al. Mar 2005 A1
20050090218 Ishida et al. Apr 2005 A1
20050120119 Bhanu et al. Jun 2005 A1
20050135360 Shin et al. Jun 2005 A1
20050174962 Gurevich Aug 2005 A1
20050186962 Yoneyama et al. Aug 2005 A1
20050195786 Shpak Sep 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
20060049880 Rein et al. Mar 2006 A1
20060063509 Pincu et al. Mar 2006 A1
20060079232 Omori et al. Apr 2006 A1
20060114044 Mintchev et al. Jun 2006 A1
20060120338 Hwang et al. Jun 2006 A1
20060128308 Michael et al. Jun 2006 A1
20060128347 Piriyapoksombut et al. Jun 2006 A1
20060189359 Kammer et al. Aug 2006 A1
20060199565 Ammirata Sep 2006 A1
20060200862 Olson et al. Sep 2006 A1
20060215601 Vleugels et al. Sep 2006 A1
20060223474 Yoshizaki et al. Oct 2006 A1
20060239443 Oxford et al. Oct 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
20060281404 Lee et al. Dec 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
20070026810 Love et al. Feb 2007 A1
20070032211 Kopikare et al. Feb 2007 A1
20070060057 Matsuo et al. Mar 2007 A1
20070077908 Vorenkamp et al. Apr 2007 A1
20070081553 Cicchetti et al. Apr 2007 A1
20070103829 Darshan et al. May 2007 A1
20070109973 Trachewsky May 2007 A1
20070142080 Tanaka et al. Jun 2007 A1
20070173286 Carter et al. Jul 2007 A1
20070178888 Alfano et al. Aug 2007 A1
20070183443 Won Aug 2007 A1
20070200622 Filoramo et al. Aug 2007 A1
20070202814 Ono et al. 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
20070264959 Carrez Nov 2007 A1
20070268862 Singh et al. Nov 2007 A1
20070280471 Fallahi et al. Dec 2007 A1
20070284441 Walczyk et al. Dec 2007 A1
20070286298 Choi et al. Dec 2007 A1
20070297388 Appaji et al. Dec 2007 A1
20080027033 Gonda et al. Jan 2008 A1
20080045162 Rofougaran et al. Feb 2008 A1
20080056201 Bennett Mar 2008 A1
20080069034 Buddhikot et al. Mar 2008 A1
20080076466 Larsson Mar 2008 A1
20080080446 Chung Apr 2008 A1
20080095058 Dalmases et al. Apr 2008 A1
20080095059 Chu Apr 2008 A1
20080100494 Yamaura May 2008 A1
20080111639 Ryckaert et al. May 2008 A1
20080129118 Diab Jun 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
20080238679 Rofougaran et al. Oct 2008 A1
20080259846 Gonikberg et al. Oct 2008 A1
20080261552 Chung Oct 2008 A1
20080261640 Yoshida Oct 2008 A1
20080262991 Kapoor et al. Oct 2008 A1
20080272818 Ko Nov 2008 A1
20080279163 Desai Nov 2008 A1
20080310067 Diab et al. Dec 2008 A1
20080320108 Murty et al. Dec 2008 A1
20090005061 Ward et al. Jan 2009 A1
20090010210 Hiertz et al. Jan 2009 A1
20090137206 Sherman et al. May 2009 A1
20090143043 Yoshizaki et al. Jun 2009 A1
20090168686 Love et al. Jul 2009 A1
20090168725 Mishra Jul 2009 A1
20090170497 Miao et al. Jul 2009 A1
20090175250 Mathur et al. Jul 2009 A1
20090190541 Abedi Jul 2009 A1
20090196210 Desai Aug 2009 A1
20090196227 Bahr Aug 2009 A1
20090202013 Sebastian Aug 2009 A1
20090209288 Rofougaran 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
20090258603 Ghaboosi et al. Oct 2009 A1
20090268652 Kneckt et al. Oct 2009 A1
20090280762 Park et al. Nov 2009 A1
20090285264 Aldana et al. Nov 2009 A1
20090291640 Bhattad et al. Nov 2009 A1
20090311961 Banerjea Dec 2009 A1
20090312027 Foschini et al. Dec 2009 A1
20090321056 Ran et al. Dec 2009 A1
20100009675 Wijting et al. Jan 2010 A1
20100011231 Banerjea et al. Jan 2010 A1
20100029325 Wang et al. Feb 2010 A1
20100052796 Menkhoff Mar 2010 A1
20100061244 Meier et al. Mar 2010 A1
20100062799 Ishii et al. Mar 2010 A1
20100069112 Sun et al. Mar 2010 A1
20100080319 Blocher et al. Apr 2010 A1
20100082957 Iwata Apr 2010 A1
20100097952 McHenry et al. Apr 2010 A1
20100103867 Kishiyama et al. Apr 2010 A1
20100124213 Ise et al. May 2010 A1
20100130129 Chang et al. May 2010 A1
20100138549 Goel et al. Jun 2010 A1
20100165896 Gong et al. Jul 2010 A1
20100216497 Kawasaki Aug 2010 A1
20100238793 Alfano et al. Sep 2010 A1
20100248734 Yamazaki et al. Sep 2010 A1
20100283654 Waheed et al. Nov 2010 A1
20100293293 Beser Nov 2010 A1
20100303026 Chaudhri et al. Dec 2010 A1
20100311342 Arbel Dec 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
20110021240 Hiltunen et al. Jan 2011 A1
20110053522 Rofougaran et al. Mar 2011 A1
20110069689 Grandhi et al. Mar 2011 A1
20110097998 Ko et al. Apr 2011 A1
20110103363 Bennett May 2011 A1
20110142014 Banerjee et al. Jun 2011 A1
20110161697 Qi et al. Jun 2011 A1
20110164538 Karr et al. Jul 2011 A1
20110194519 Habetha Aug 2011 A1
20120020319 Song et al. Jan 2012 A1
20120025921 Yang et al. Feb 2012 A1
20120039176 Eshan et al. Feb 2012 A1
20120099476 Mahaffy et al. Apr 2012 A1
20120250576 Rajamani et al. Oct 2012 A1
20120276938 Wagholikar et al. Nov 2012 A1
20120327779 Gell et al. Dec 2012 A1
20130045687 Banerjea Feb 2013 A1
20130045688 Banerjea Feb 2013 A1
20130057344 Touzard et al. Mar 2013 A1
20130114548 Banerjea May 2013 A1
20130176903 Bijwe Jul 2013 A1
20130227152 Lee et al. Aug 2013 A1
20140004794 Contaldo Jan 2014 A1
20140044106 Bhagwat Feb 2014 A1
20140073251 Banerjea Mar 2014 A1
20140362735 Mahaffy Dec 2014 A1
Foreign Referenced Citations (20)
Number Date Country
102067689 May 2011 CN
1860827 Nov 2007 EP
2299642 Mar 2011 EP
2456275 May 2012 EP
2006174162 Jun 2006 JP
200728568 Feb 2007 JP
2007028568 Feb 2007 JP
WO-0178252 Oct 2001 WO
WO-02082751 Oct 2002 WO
WO-02091623 Nov 2002 WO
WO-2006043956 Apr 2006 WO
WO-2006090254 Aug 2006 WO
WO-2007008981 Jan 2007 WO
WO-2007064822 Jun 2007 WO
WO-2008070777 Jun 2008 WO
WO-2008150122 Dec 2008 WO
WO-2009101567 Aug 2009 WO
WO-2011056878 May 2011 WO
WO-2013104989 Jul 2013 WO
WO-2013119810 Aug 2013 WO
Non-Patent Literature Citations (139)
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/190,251, Dec. 7, 2011, 3 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/186,429, Oct. 13, 2011, 23 pages.
“Final Office Action”, U.S. Appl. No. 12/190,251, Sep. 13, 2011, 15 pages.
“Final Office Action”, U.S. Appl. No. 12/323,292, Aug. 24, 2012, 26 pages.
“Final Office Action”, U.S. Appl. No. 12/358,955, Feb. 17, 2012, 26 pages.
“Final Office Action”, U.S. Appl. No. 12/358,955, Mar. 18, 2013, 12 pages.
“Final Office Action”, U.S. Appl. No. 12/484,563, Apr. 24, 2012, 18 pages.
“Final Office Action”, U.S. Appl. No. 12/487,425, May 3, 2012, 9 pages.
“Final Office Action”, U.S. Appl. No. 12/534,361, Feb. 29, 2012, 13 pages.
“Final Office Action”, U.S. Appl. No. 12/542,845, Sep. 25, 2012, 23 pages.
“Final Office Action”, U.S. Appl. No. 12/616,454, Apr. 11, 2012, 19 pages.
“Final Office Action”, U.S. Appl. No. 12/646,721, Jun. 6, 2013, 16 pages.
“Final Office Action”, U.S. Appl. No. 12/646,802, Nov. 15, 2012, 15 pages.
“Final Office Action”, U.S. Appl. No. 12/759,336, Feb. 25, 2013, 11 pages.
“Foreign Office Action”, CN Application No. 200980122587.0, Sep. 10, 2013, 11 Pages.
“Foreign Notice of Allowance”, JP Application No. 2011-513586, Jul. 16, 2013, 2 pages.
“Foreign Office Action”, CN Application No. 200980122587.0, Jan. 24, 2014, 10 Pages.
“Foreign Office Action”, CN Application No. 200980122587.0, Feb. 21, 2013, 17 pages.
“Foreign Office Action”, EP Application No. 09789754.0, May 17, 2011, 8 pages.
“Foreign Office Action”, European Patent Application No. 09789754.0, Mar. 11, 2013, 4 Pages.
“Foreign Office Action”, European Patent Application No. 09789754.0, Jul. 12, 2012, 4 pages.
“Foreign Office Action”, JP Application No. 2011-513586, Apr. 9, 2013, 4 Pages.
“Foreign Office Action”, JP Application No. 2011-513586, Oct. 23, 2012, 7 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.
“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.
“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.
“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.
“Information Technology—Telecommunications and Information Exchange Between systems—Local and Metropolitan Area Networks—Specific Requirements”, IEEE Standard, Aug. 1, 2005, pp. 1-60.
“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.
“International Search Report and Written Opinion”, Application No. PCT/US2013/025144, Jun. 5, 2013, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/IB2013/001962, Feb. 6, 2014, 11 Pages.
“International Search Report and Written Opinion”, Application No. PCT/US2012/035597, Aug. 6, 2012, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2009/046289, Oct. 29, 2009, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2011/054358, Dec. 16, 2011, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/IB2013/000390, Aug. 21, 2013, 19 Pages.
“Introduction to 802.11n Outdoor Wireless Networks”, InscapeData White Paper, Mar. 29, 2011, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/429,071, Mar. 28, 2014, 8 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/167,841, Jul. 15, 2011, 10 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/190,240, Jan. 6, 2012, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/190,251, Mar. 29, 2012, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/190,251, Mar. 29, 2011, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/235,333, Jun. 28, 2011, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/323,292, Dec. 21, 2011, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/358,955, Sep. 6, 2011, 24 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/358,955, Aug. 20, 2012, 33 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/478,446, Dec. 28, 2011, 17 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/487,425, Jan. 12, 2012, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/534,361, Oct. 12, 2011, 11 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/542,845, Apr. 4, 2012, 19 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. 12/646,721, May 8, 2014, 17 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, May 21, 2014, 19 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/732,036, Aug. 9, 2012, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/759,336, Oct. 4, 2012, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/883,054, Nov. 22, 2013, 18 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/099,169, Oct. 4, 2013, 9 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/479,124, Sep. 27, 2013, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/604,563, Apr. 5, 2013, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/656,482, Mar. 19, 2013, 19 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/656,502, Feb. 21, 2013, 6 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/722,354, Jan. 17, 2014, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/757,276, Jan. 30, 2014, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/911,979, Jan. 31, 2014, 19 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/923,949, Dec. 17, 2013, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 12/167,841, Nov. 25, 2011, 11 pages.
“Notice of Allowance”, U.S. Appl. No. 12/186,429, Jun. 6, 2013, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 12/190,240, May 16, 2012, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 12/190,251, Oct. 4, 2012, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 12/235,333, Nov. 15, 2011, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 12/323,292, Jun. 28, 2013, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 12/358,955, Jul. 1, 2013, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 12/478,446, Jun. 14, 2012, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 12/484,563, Jul. 9, 2012, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 12/487,425, Jul. 26, 2013, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 12/534,361, Feb. 14, 2013, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 12/616,454, Aug. 22, 2012, 4 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/759,336, May 3, 2013, 9 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/479,124, Jan. 30, 2014, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/604,563, Sep. 26, 2013, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/656,482, Sep. 3, 2013, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 13/656,502, Jun. 25, 2013, 11 pages.
“Notice of Allowance”, U.S. Appl. No. 13/673,363, Mar. 24, 2014, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 13/722,354, May 15, 2014, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 13/923,949, Mar. 31, 2014, 6 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.
“Restriction Requirement”, U.S. Appl. No. 12/167,841, May 12, 2011, 6 pages.
“Search Report”, European Application No. 13169350.9, Aug. 13, 2013, 10 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/323,292, Oct. 17, 2013, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/323,292, Oct. 7, 2013, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/358,955, Oct. 11, 2013, 3 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/716,569, Jul. 23, 2012, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/759,336, Jun. 5, 2013, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/759,336, Jun. 18, 2013, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 12/759,336, Aug. 14, 2013, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/479,124, Apr. 18, 2014, 5 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/656,482, Nov. 29, 2013, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/656,482, Dec. 19, 2013, 2 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.
Haas,“Gossip-Based Ad Hoc Routing”, IEEE/ACM Transactions on Networking, vol. 14, No. 3, Jun. 2006, pp. 479-491.
Jung,“A Power Control MAC Protocol for Ad Hoc Networks”, In Proceedings of MOBICOM 2002, Sep. 23, 2002, pp. 36-47.
Jung,“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.
Mazzanti,“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.
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.
Qiao,“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.
Tinnirello,“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.
“Final Office Action”, U.S. Appl. No. 12/646,721, Nov. 28, 2014, 19 pages.
“Final Office Action”, U.S. Appl. No. 12/646,802, Dec. 17, 2014, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/622,916, Sep. 10, 2014, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/735,458, Sep. 24, 2014, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/466,687, Oct. 3, 2014, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/735,458, Jan. 12, 2015, 4 pages.
Deering, “Version 6 (IPv6) Specification”, RFC2460, Dec. 1998, 35 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 13/735,458, Apr. 20, 2015, 2 pages.
“Final Office Action”, U.S. Appl. No. 14/466,687, Apr. 30, 2015, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/646,802, Apr. 8, 2015, 19 pages.
“Notice of Allowance”, U.S. Appl. No. 13/622,916, Mar. 30, 2015, 4 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/622,916, May 7, 2015, 2 pages.
Provisional Applications (1)
Number Date Country
61490452 May 2011 US
Continuations (1)
Number Date Country
Parent 13479124 May 2012 US
Child 14275615 US