Pre-association discovery

Information

  • Patent Grant
  • 9332488
  • Patent Number
    9,332,488
  • Date Filed
    Friday, August 22, 2014
    10 years ago
  • Date Issued
    Tuesday, May 3, 2016
    8 years ago
Abstract
The present disclosure describes techniques for pre-association discovery. In some aspects a frame having information useful to identify a service provided by a wireless device is received, the service provided by the wireless device is identified based on the information of the frame and known service identification information, and the identified service is associated with the wireless device effective to enable use of the identified service.
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 application and are not admitted to be prior art by inclusion in this section.


Computing devices often rely on peripheral devices to provide services which can increase or extend capabilities of a computing device. These peripheral devices typically include an interface for communicating with a computing device over a wireless connection. While this wireless connection allows a peripheral device to provide a service without being physically cabled to the computing device, finding and configuring a peripheral device over a wireless connection can be difficult. Complex software protocols for finding peripherals within a wireless network are often slow, fail to differentiate between peripheral types, and incapable of fully configuring a peripheral device once found. Configuring a peer-to-peer wireless connection to a peripheral can be a complex, multi-step process that is reliant on user configuration of the computing device and/or the peripheral device. A peripheral connection process that is complex, time consuming, or reliant on user interaction may compromise a user's experience with the computing device and/or peripheral device.


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 receiving a frame having information useful to identify a service provided by a wireless device from which the frame was received, identifying the service provided by the wireless device based on the information of the frame and known service identification information, and associating the identified service with the wireless device effective to enable use of the identified service.


Another method is described for broadcasting a frame including information identifying a service that is accessible via a wireless network, receiving a request to associate with the wireless network from a wireless device capable of accessing the service, and granting the request to associate with the wireless network to enable the wireless device to access the service over the wireless network.


Still another method is described for receiving a request for a service, configuring a wireless interface to receive beacons identifying services accessible via respective wireless networks, receiving one or more of the beacons identifying services accessible, determining which service accessible via the respective wireless networks corresponds with the request for the service, and causing the wireless interface to associate with one of the wireless networks through which the corresponding service is accessible to fulfill the request for the service.





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 wirelessly in accordance with one or more aspects.



FIG. 3 illustrates a method of identifying a service provided by a wireless device.



FIG. 4 illustrates a method of enabling a wireless device to access a service via a wireless network.



FIG. 5 illustrates a method of causing a wireless interface to associate with a wireless network through which a service is accessible.



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





DETAILED DESCRIPTION

Conventional techniques for finding and configuring a peripheral device over a wireless connection are typically complex, time consuming, and reliant on manual configuration of a computing device and/or the peripheral device. This disclosure describes apparatuses and techniques for pre-association discovery that often permit services accessible via wireless networks to be discovered and accessed more-quickly or with little or no manual configuration. These services can be identified based on a frame received, thereby precluding the need to pre-configure a connection with a wireless network of the device providing the service.


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 host computing devices 102 (host devices 102) and client computing devices 104 (client 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). Host computing devices 102 include smart-phone 108, tablet computer 110, and laptop computer 112. Although not shown, other configurations of host computing devices 102 are also contemplated such as a desktop computer, a server, mobile-internet device (MID), mobile gaming console, and so on.


Each of host devices 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 the 802.11 family of protocols. 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. Host devices 102 also include processor(s) 118, computer-readable storage media 120 (CRM 120), and wireless-service manager 122 (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), read-only memory (ROM), or Flash memory useful to store data of applications and/or an operating system of the host device 102. How manager 122 is implemented and used varies and is described below.


Client devices 104 include printer 124, scanner 126, network-attached storage (NAS) 128, and multi-function printer 130. Other client devices contemplated include various peripheral and/or accessory devices, such as cameras, digital picture frames, displays, televisions, speakers, and so on. Each client device 104 provides one or more services (e.g., capabilities or functions) that are accessible to a communicatively coupled host device 102. For example, tablet computer 110 is able to access print functions of printer 124 when connected by wire or wirelessly. Any of these devices may act as an access point or a client station of a wireless network, and may be dynamically configured to do so.


Each of client devices 104 includes wireless transceiver 132 providing 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. Client devices 104 also include client processor(s) 134, client computer-readable storage media 136 (client CRM 136), and service discovery module 138 (discovery module 138), which, in one implementation, is embodied on client CRM 136. Client 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 client device 104. How discovery module 138 is implemented and used varies and is described below.



FIG. 2 illustrates an example of device environment 200 that includes a WLAN network 202 (network 202) managed by access point 204. Access point 204 provides 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 network 202, smart-phone 108 and laptop computer 112 have internet access and/or connectivity with other networks for which access point 204 acts as a gateway.


Client devices 104, when within range of access point 204 may also associate with network 202, such as NAS 128, which is shown within network 202. NAS 128 may stream music, download video, or sync data with an online storage account (not shown) via Internet 206 when associated with network 202. Alternately or additionally, when associated with network 202, services of a client device 104 may be accessible to host devices 102 also associated with network 202.


As described above, client devices 104 may act as either a client station or an access point. In some cases, printer 124, NAS 128, and multifunction printer 130, may each be configured to act as an access point. In such a case, techniques of pre-association discovery allow host devices 102 to communicate directly with client devices 104. For example, smart-phone 108 can communicate directly with printer 124 over wireless network 210 or NAS 128 over wireless network 212. Additionally, laptop computer 112 can communicate directly with multifunction printer 130 over wireless network 214. These are but a few examples of implementing techniques of pre-association discovery which are described below.


Techniques of Pre-Association Discovery


The following discussion describes techniques of pre-association discovery. These techniques can be implemented using the previously described environments, such as manager 122 of FIG. 1 embodied on a host device 102 and/or discovery module 138 of FIG. 1 embodied on a client device 104. These techniques include methods illustrated in FIGS. 3, 4, and 5, 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 identifying a service provided by a wireless device, including operations performed by manager 122 of FIG. 1.


At 302, a wireless interface is configured to receive frames broadcast by wireless devices. In some cases, a previously-associated wireless network is disassociated from prior to the configuration. The wireless interface may be configured to scan or listen for frames or beacons of the other wireless devices, such as WLAN beacons or management frames.


As an example, consider smart-phone 108 in the context of FIG. 2, which shows smart-phone 108 within wireless network 202. Assume here that smart-phone 108 is associated with wireless network 202 and browsing content of Internet 206, when a user decides to print a webpage. Here, manager 122 causes a wireless interface (e.g., wireless transmitter 114/wireless receiver 116) of smart-phone 108 to disassociate from wireless network 202. Manager 122 then configures the wireless interface to receive frames or beacons from other wireless devices, such as printer 124, NAS 128, and multifunction printer 130.


At 304, a frame is received from a wireless device, the frame having information useful to identify a service provided by the wireless device. The frame may include a dedicated field to store the identification information or other information of the frame may be encoded with the identification information. In some cases, the frame is a beacon or management frame of a WLAN network provided by the wireless device and the information useful to identify the service is within a service set identity (SSID) field. In such a case, data of the SSID field may be patterned or encoded such that a portion of the SSID data is useful to identify the service.


For example, an SSID field of 32 bytes can be provisioned or portioned such that a network name is stored in the first 24 bytes and the identification information is stored in the remaining 8 bytes. These remaining 8 bytes can then be encoded to identify a class, a type, or functionality of the service provided by the wireless device. Note that the SSID field can be portioned into any suitable number of sub-fields having various numbers of bytes without departing from the spirit or intent of the present disclosure.


In the context of the present example, smart-phone 108 receives a beacon from printer 124. Assume here that the beacon contains an SSID field that is portioned as described above, with the last 8 bytes of the SSID field describing print services provided by printer 124. Smart-phone 108 may also receive similar packets from NAS 128, which provides data storage and/or multifunction printer 130, which provides printing and scanning.


At 306, the service provided by the wireless device is identified based on the information of the frame and known service identification information (known information). In some cases, the service is identified by comparing or matching the information of the frame with the known information. In such a case, a regular expression pattern matching algorithm may be used. The known information may be complimentary or reciprocal to the information of the frame defining services for a given byte pattern or encoding, such as the SSID pattern described above. If a service is not identified, additional information may be downloaded or received from a user to supplement the known information.


Continuing the ongoing example, manager 122 compares the last 8 bytes of the SSID field with known information to identify print services of printer 124. Assume here that manager 122 is also able to identify services provided by NAS 128 and multifunction printer 130 by comparing bytes of their respective SSIDs with the known information.


At 308, the identified service is associated with the wireless device effective to enable use of the identified service via the wireless interface. In some cases, the identified service is associated with a wireless network provided by the wireless device. For instance, the identified service can be associated with the name of the network provided by the wireless device as described by the SSID field. Once associated, the identified service can be accessed when the wireless interface connects with a wireless network of the wireless device providing the service. Optionally, additional services may be discovered by returning to block 304 and repeating an iteration of blocks 304, 306, and 308.


In the context of the present example, manager 122 associates the identified print services of printer 124 with the SSID of a wireless network provided by printer 124. Here, manager 122 repeats operations of blocks 304, 306, and 308, associating identified data storage services with a SSID of NAS 128, and other identified print and scan services with a SSID of multifunction printer 130.


At 310, access of the identified service is initiated by causing the wireless interface to associate with a wireless network provided by the wireless device. Once associated with the wireless network of the wireless device, the identified service can be accessed.


Concluding the present example, manager 122 causes the wireless interface of smart-phone 108 to associate with wireless network 210 of printer 124. Once associated with wireless network 210, applications of smart-phone 108 can access the print services of printer 124 and print the webpage. Additionally, manager 122 can cause the wireless interface of smart-phone 108 to associate with wireless network 212 or wireless network 214 to access data or scanning services.



FIG. 4 depicts a method 400 for enabling a wireless device to access a service via a wireless network, including operations performed by discovery module 138 of FIG. 1.


At 402, a wireless interface is configured to provide a wireless network. The wireless network may be any suitable type of network, such as a WLAN network implementing protocols compliant with an IEEE 802.11 specification. In some cases, the wireless interface enters an access point mode to provide the wireless network.


As an example, consider NAS 128 in the context shown in FIG. 2, which shows NAS 128 within wireless network 202. Assume here that a wireless interface (e.g., transceiver 132) of NAS 128 is operating in a client mode and associated with wireless network 202. Discovery module 138 configures the wireless interface of NAS 128 to operate in an access point mode to provide wireless network 212.


At 404, a frame is broadcast that includes information identifying a service accessible via the wireless network. The frame can be a beacon or management frame transmitted to identify or manage the wireless network. By broadcasting the frame, the service accessible via the wireless network may be discovered by wireless devices within range. In some cases, the information identifying the service is located within a field of the frame or beacon, such as an SSID field. In such a case, bytes of the SSID field can be encoded such that a portion of the SSID is useful to identify the service.


For example, multiple devices within a wireless network may have SSIDs sharing a common, or invariant, portion which identifies a network name. Each of these devices may then have a unique, or variant, portion of the SSID to identify different services provided by each device. In the context of the present example, discovery module 138 causes the wireless interface of NAS 128 to broadcast a beacon with an SSID identifying data storage services accessible via wireless network 212.


At 406, a request to associate with the wireless network is received from a wireless device capable of accessing the service. The request may be received from any wireless device within range of the wireless interface. In some cases, the wireless device has information that is complimentary or reciprocal to the information identifying the service accessible via the wireless network.


Continuing the ongoing example, a request to associate with wireless network 212 is received from smart-phone 108. Assume here that smart-phone 108 is attempting to backup user data stored within CRM 120 and is within range of wireless network 212.


At 408, the request to associate with the wireless network is granted effective to enable the wireless device to access the service over the wireless network. Once the request to associate with the wireless network is granted, the wireless device may communicate or otherwise interact with the service accessible over the wireless network. In some cases, the request to associate may be denied if the wireless device is unable to provide an encryption key (for an encrypted network) or pass authentication. In the context of the ongoing example, discovery module 138 grants the request of smart-phone 108 to associate with wireless network 214.


At 410, data related to the service is received from the wireless device in response to enabling access to the service. The data received may be any suitable type of data, such as print data, data for storage, multimedia data, a request for scanning service, and so on. Concluding the present example, NAS 128 receives user data from smart-phone 108 to store. Once complete, either or both of NAS 128 or smart-phone 108 may disassociate from wireless network 212 and associate with wireless network 202 for access to Internet 206.



FIG. 5 depicts a method 500 for causing a wireless interface to associate with a wireless network through which a service is accessible, including operations performed by manager 122 of FIG. 1.


At 502, a request for a service is received. The request for service can be received from an application or operating system component. In some cases, the request for service is received responsive to user interaction, such as a user input requesting printing or scanning of content. As an example, consider laptop computer 112 in the context of FIG. 2, which shows laptop computer 112 within wireless network 202. Assume here that a user of laptop computer 112 selects to print slides of a presentation. Manager 122 receives, in response to the user print selection, a request for print services from the presentation editing application of laptop computer 112.


At 504, a wireless interface is configured to scan for beacons identifying services accessible via respective wireless networks. In some cases, a previously-associated wireless network is disassociated from prior to the configuration. The wireless interface may be configured to scan or listen for frames or beacons of the other wireless devices, such as WLAN beacons or management frames.


In the context of the present example, manager 122 causes a wireless interface (e.g., wireless transmitter 114/wireless receiver 116) of laptop computer 112 to disassociate from wireless network 202. Manager 122 then configures the wireless interface to receive frames or beacons from other wireless devices, such as printer 124, NAS 128, and multifunction printer 130.


At 506, beacons identifying services accessible via the respective wireless networks are received. The beacons may include a field storing information identifying the services or other information of the frame may be encoded with the information identifying the services. In some cases, the beacon is a frame of a WLAN network provided by a respective wireless device and the information identifying the service is within a service set identity (SSID) field. In such a case, data of the SSID field may be patterned or encoded such that a portion of the SSID data is useful to identify the service.


Continuing the ongoing example, laptop computer 112 receives beacons from printer 124, NAS 128, and multifunction printer 130, each of which identify services provided by a respective device by use of the SSID field. Assume here that the SSID field of each beacon is portioned into three parts: an invariant network name sub-field of 24 bytes, a variant medium-access controller (MAC) address sub-field of 6 bytes, and a variant service identifier sub-field of 2 bytes.


This results in a beacon broadcast by printer 124 having an SSID of “ServicesNet-04A91B-04”, where “ServicesNet” is a network name shared by printer 124, NAS 128, and multifunction printer 130. Additionally, “04A91B” are hexadecimal values of the MAC address of printer 124 useful to distinguish printer 124 from other printers, and “04” is an encoded value of the print services accessible from printer 124. NAS 128 and multifunction printer 130 both have similar SSIDs, with varying MAC address and service identifier sub-fields. As noted above, this is but one configuration of an SSID field, as any suitable number and/or size of sub-fields may be used.


At 508, services accessible via the respective wireless networks, which correspond to the request for service are determined. A regular expression matching algorithm may be used to determine which services accessible correspond to the service request. In some cases, information from the beacons identifying the accessible services is compared with the request for service to make the determination. For instance, if the request for service is a scanning request, known indexing information of a scanning service can be compared with a service identifier sub-field of an SSID.


Once the corresponding services are determined, a list of the corresponding services can be presented via a user interface for selection. Additionally, signal strength of a wireless network through which a service is accessible may be used to determine a distance to a device providing the service. Using this information, the corresponding services in the list presented to the user can be arranged based on the distance to the device providing the service.


In the context of the current example, manager 122 determines that print services accessible via wireless networks 210 and 214 correspond to the request for print service. Here, manager 122 also determines that multifunction printer 130 is closer based on the relative signal strengths of wireless networks 210 and 214. A user interface is then presented by manager 122 listing wireless networks 210 and 214 as providing print services, with wireless network 214 at the top of the list due to proximity.


At 510, a wireless interface is caused to associate with a wireless network through which a corresponding service is accessible. Once associated with the wireless network of the wireless device, the corresponding service can be accessed to fulfill the request for service. Additionally, after accessing the corresponding service, the wireless interface may re-associate with a previously-associated network to resume activity over that network.


Concluding the present example, manager 122 causes the wireless interface of laptop computer 112 to associate with wireless network 214 responsive to selection through the user interface. Once associated with wireless network 214, the request for print service is fulfilled by communicating print data of the slides to multifunction printer 130. Manager 122 then causes the wireless interface of laptop computer 112 to disassociate from wireless network 214, at which point the wireless interface can re-associate with wireless network 202 for access to Internet 206.


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, desktop computer, laptop computer, 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 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.


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. 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, 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 system comprising: a wireless interface communicating in accordance with a wireless networking protocol; one or more processors implemented at least partially in hardware; a memory storing processor-executable instructions that, responsive to execution by the one or more processors, implement a wireless-service manager to perform operations comprising: receiving, via the wireless interface, a data frame from a wireless device, the data frame including a service set identity (SSID) field comprising: a first sub-field that includes information useful to identify a name of a wireless network with which the wireless device is associated a second sub-field that includes information useful to identify a service provided by the wireless device the service provided by the wireless device being a service other than access to the wireless network; a third sub-field that includes information useful to identify the wireless device, the third sub-field including at least a portion of the wireless device's media-access controller (MAC) address; identifying, based on the information included in the SSID field of the data frame and known service identification information, the service provided by the wireless device; and associating the identified service with the wireless device effective to enable use of the identified service via the wireless interface of the system.
  • 2. The system as described in claim 1, wherein the operations performed by the wireless-service manager further comprise causing the wireless interface to scan for data frames broadcast by the wireless device or other wireless devices.
  • 3. The system as described in claim 1, wherein the operations performed by the wireless-service manager further comprise causing the wireless interface to associate with the wireless network with which the wireless device is associated effective to initiate access of the identified service.
  • 4. The system as described in claim 1 wherein, during the acts of receiving or identifying, the wireless interface is not associated with the wireless network with which the wireless device is associated.
  • 5. The system as described in claim 1, wherein the service provided by the wireless device includes one of a printing service, a scanning service, a data storage service, a streaming media service, or a media presentation service.
  • 6. The system as described in claim 1, wherein the wireless interface is a wireless local area network (WLAN) interface configured in accordance with an IEEE 802.11 standard.
  • 7. One or more computer-readable memory devices comprising computer-executable instructions that, responsive to execution by one or more processors, implement a wireless-service manager to: receive, via a wireless interface, a data frame from a wireless device, the data frame including a service set identity (SSID) field comprising: a first sub-field that includes information useful to identify a name of a wireless network with which the wireless device is associated;a second sub-field that includes information useful to identify a service provided by the wireless device, the service provided by the wireless device being a service other than network access;a third sub-field that includes information useful to identify the wireless device, the third sub-field including at least a portion of the wireless device's media-access controller (MAC) address;identify, based on the information included in the SSID field and known service identification information, the service provided by the wireless device; andassociate the identified service with the wireless device effective to enable use of the identified service via the wireless interface.
  • 8. The one or more computer-readable memory devices of claim 7, wherein the wireless-service manager is further implemented to configure the wireless interface to scan for data frames identifying services accessible via respective wireless devices.
  • 9. The one or more computer-readable memory devices of claim 7, wherein during the acts of receiving or identifying, the wireless interface is not associated with the wireless network with which the wireless device is associated.
  • 10. The one or more computer-readable memory devices of claim 7, wherein the wireless-service manager is further implemented to cause the wireless interface to associate with the wireless network with which the wireless device is associated effective to initiate access of the identified service.
  • 11. The one or more computer-readable memory devices of claim 7, wherein the wireless interface is configured to operate in accordance with an IEEE 802.11 standard.
  • 12. The one or more computer-readable memory devices of claim 7, wherein the service provided by the wireless device includes one of a printing service, a scanning service, a data storage service, a streaming media service, or a media presentation service.
  • 13. The one or more computer-readable memory devices of claim 7, wherein the data frame received from the wireless device is a beacon broadcast by the wireless device.
  • 14. A system-on-chip comprising: one or more processors implemented at least partially in hardware;a memory storing processor-executable instructions that, responsive to execution by the one or more processors, implement a wireless-service manager to perform operations comprising: broadcasting, from a wireless interface of a device providing the wireless network, a data frame including a service set identity (SSID) field comprising: a first sub-field that includes information identifying a name of the wireless network provided by the device;a second sub-field that includes information identifying a service that is provided by the device and accessible via the wireless network, the service provided by the device and accessible via the wireless network being a service other than network access;a third sub-field that includes information useful to identify the device, the third sub-field including at least a portion of the wireless interface's media-access controller (MAC) address;receiving a request to associate with the wireless network from a wireless device capable of accessing the service identified by the data frame; andgranting the request to associate with the wireless network effective to enable the wireless device to access the service via the wireless network provided by the wireless interface.
  • 15. The system-on-chip as described in claim 14, wherein the service provided by the device and accessible via the wireless network comprises one of a printing service, a scanning service, a data storage service, a streaming media service, or a media presentation service.
  • 16. The system-on-chip as described in claim 14, wherein the operations performed by the wireless-service manager further comprise, in response to enabling access to the service, receiving data or a request related to the service from the wireless device.
  • 17. The system-on-chip as described in claim 14, wherein the wireless interface communicates in accordance with an IEEE 802.11 specification and is configured as an access point to provide the wireless network through which the service is accessible.
  • 18. The system-on-chip as described in claim 14, wherein the information of the second sub-field includes eight bytes of encoded information that identify the service provided by the device and accessible via the wireless network.
  • 19. The system-on-chip as described in claim 14, wherein the third sub-field includes six hexadecimal values of the wireless interface's MAC address.
  • 20. The system as described in claim 1, wherein the information of the first sub-field includes invariant information that identifies the wireless network as a shared wireless network by which multiple wireless devices providing respective services are accessible.
RELATED APPLICATIONS

This present disclosure is a continuation of and claims priority to U.S. Utility patent application Ser. No. 13/249,740 filed Sep. 30, 2011 which claims priority to U.S. Provisional Patent Application Ser. No. 61/405,052 filed Oct. 20, 2010, the disclosure of which are incorporated by reference herein in their entirety.

US Referenced Citations (330)
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
6445342 Thomas et al. Sep 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
6829313 Xu Dec 2004 B1
6922433 Tamura Jul 2005 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
7180901 Chang et al. Feb 2007 B2
7200799 Wang et al. Apr 2007 B2
7206840 Choi et al. Apr 2007 B2
7212798 Adams et al. May 2007 B1
7213194 Nieminen May 2007 B2
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
7447163 Thomson et al. Nov 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
7944867 Usuba May 2011 B2
7957340 Choi et al. Jun 2011 B2
7965710 Choi Jun 2011 B1
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 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
9078108 Wagholikar et al. Jul 2015 B1
9125216 Choi et al. Sep 2015 B1
9288764 Banerjea et al. Mar 2016 B1
9294997 Shukla et al. Mar 2016 B1
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 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
20050043027 Emeott et al. Feb 2005 A1
20050047386 Yi Mar 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
20050233704 Maekawa Oct 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
20070237122 Liu et al. Oct 2007 A1
20070238482 Rayzman et al. Oct 2007 A1
20070242645 Stephenson et al. Oct 2007 A1
20070263587 Savoor et al. Nov 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
20090080390 Zhou et al. Mar 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
20090316667 Hirsch 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
20100039974 Toshimitsu 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
20100077275 Yu 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
20110292925 Ho et al. Dec 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 Apr 2012 A1
20120244805 Haikonen et al. Sep 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
Foreign Referenced Citations (25)
Number Date Country
101044714 Sep 2007 CN
102067689 May 2011 CN
1860827 Nov 2007 EP
2299642 Mar 2011 EP
2456275 May 2012 EP
2005303821 Oct 2005 JP
2006014312 Jan 2006 JP
2006148471 Jun 2006 JP
2006174162 Jun 2006 JP
200728568 Feb 2007 JP
2007028568 Feb 2007 JP
5776128 Jul 2015 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-2008707777 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 (161)
Entry
Ekici et al., IEEE 802,11a Throughput Performance with Hidden Nodes, Jun. 2008, IEEE Communication Letters, vol. 12, No. 6, All.
Toshiba, SSID (Service Set Identifier), Aug. 2003, Version 1.0, All.
Ed Roth, ESS and BSS Service Sets, Sep. 2002, Windows IT Pro, All.
“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. 11/945,183, Nov. 9, 2010, 2 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. 11/945,183, Sep. 13, 2010, 12 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, Apr. 23, 2014, 22 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. 13169350.9, May 9, 2014, 3 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; Amendement 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. 11/945,183, Apr. 5, 2010, 8 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/536,506, Apr. 25, 2014, 12 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/622,916, Sep. 10, 2014, 10 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.
“Non-Final Office Action”, U.S. Appl. No. 14/089,515, May 13, 2014, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 11/945,183, Feb. 23, 2011, 7 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.
“Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems; Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands”, IEEE Std 802.16e, Feb. 28, 2006, 822 pages.
“Part 16: Air Interface for Fixed Broadband Wireless Access Systems”, IEEE Std. 802.16, Oct. 1, 2004, 857 pages.
“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, et al., “Gossip-Based Ad Hoc Routing”, IEEE/ACM Transactions on Networking, vol. 14, No. 3, Jun. 2006, pp. 479-491.
Jung, et al., “A Power Control MAC Protocol for Ad Hoc Networks”, Wireless Networks; The Journal of Mobile Communication, Computation and Information, Kluwer Academic Publishers vol. 11, No. 1-2, Jan. 1, 2005, 12 Pages.
Jung, et al., “A Power Control MAC Protocol for Ad Hoc Networks”, In Proceedings of MOBICOM 2002, Sep. 23, 2002, pp. 36-47.
Mazzanti, et al., “Analysis and Design of Injection-Locked LC Dividers for Quadrature Generation”, IEEE Journal of Solid-State Circuits, vol. 39, No. 9, Sep. 2004, pp. 1425-1433.
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, et al., “Interference Analysis and Transmit Power Control in IEEE 802.11a/h Wireless LANs”, IEEE / ACM Transactions on Networking, IEEE / ACM, New York, NY, US, vol. 15. No. 5, Oct. 1, 2007, 14 Pages.
Tinnirello, et al., “Revisit of RTS / CTS Exchange in High-Speed IEEE 802.11 Networks”, World of Wireless Mobile and Multimedia Networks. 2005. Wowmom 2005. Sixth IEEE International Symposium on a Taormina-Giardini Naxos, Italy Jun. 13-16, 2005 Piscataway, NJ, USA,IEEE, Los Alamitos, CA, USA, Jun. 13, 2005, 10 Pages.
“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/735,458, Sep. 24, 2014, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/275,615, Oct. 6, 2014, 28 pages.
“Notice of Allowance”, U.S. Appl. No. 13/735,458, Jan. 12, 2015, 4 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 13/735,458, Apr. 20, 2015, 2 pages.
“Foreign Office Action”, JP Application No. 2013-534930, Feb. 10, 2015, 3 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.
“Notice of Allowance”, U.S. Appl. No. 14/275,615, Feb. 27, 2015, 7 pages.
Deering,“Version 6 (IPv6) Specification”, RFC2460, Dec. 1998, 35 pages.
“Foreign Decision for Grant”, Japan Application No. 2013-534930, Jun. 9, 2015, 2 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/293,640, Jul. 17, 2015, 17 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/622,916, May 7, 2015, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/622,916, Jul. 10, 2015, 2 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/275,615, Jun. 5, 2015, 4 pages.
“Foreign Office Action”, CN Application No. 201180050795.1, Sep. 1, 2015, 8 Pages.
“Foreign Office Action”, KR Application No. 10-2013-7012920, Sep. 11, 2015, 13 Pages.
“Notice of Allowance”, U.S. Appl. No. 12/646,802, Oct. 28, 2015, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 14/293,640, Nov. 12, 2015, 12 pages.
Related Publications (1)
Number Date Country
20140362735 A1 Dec 2014 US
Provisional Applications (1)
Number Date Country
61405052 Oct 2010 US
Continuations (1)
Number Date Country
Parent 13249740 Sep 2011 US
Child 14466687 US