Beacon based proximity services

A first wireless device including a receiver configured to receive a beacon transmitted by a second wireless device, where the beacon includes a service set identifier, and where the service set identifier is encoded to include a capability of the second wireless device; and a transmitter configured to transmit, to a server, the service set identifier received from the second wireless device, where the service set identifier is decodable by the server to retrieve the capability of the second wireless device from the service set identifier. The receiver is further configured to receive, from the server, the capability of the second wireless device subsequent to the server having decoded the service set identifier.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 11/542,394 filed on Oct. 3, 2006, (now U.S. Pat. No. 8,411,662) which claims the benefit of U.S. Provisional Application No. 60/723,299, filed on Oct. 4, 2005. The entire disclosures of the applications referenced above are incorporated herein by reference.

FIELD

The present invention relates to wireless networks. More particularly, the present invention relates to the wireless communication protocol IEEE 802.11

BACKGROUND

It is well known that wireless devices such as telephones, email devices, and PDA's have been enabled for local wireless network communication with Internet protocol backbone networks by way of protocols such as the several forms of IEEE 802.11.

Alternately, automatic connection and communication systems may create a Personal-Area Networks (PAN). Other wireless standards that may be used include IRDA, hiperlan/2, and HomeRF. When a PAN is established, such as between one VoiP mobile phone and another, the members of the PAN can communicate directly. The more generally preferred mode of operation for such a mobile telephone is connection to a local access point, whereby the user can contact any source available to the Internet for conversation or gaming.

In a local area network communication, the access point transmits information separately to each local wireless device. An advantage to using a point-to-point communication is that different information (e.g., customization) may be sent to each wireless device. Even if the same information is being sent to several recipients (e.g., ensuring uniformity of a game's state for all local users coordinated by a remote server), however, in a point-to-point communication with multiple recipients, the information is transmitted redundantly to each recipient. However, an access point, comprising a wireless communication module and access point server which connects to an IP network, game state information may be transmitted, daisy chain, along point to-point communications from an access point within range of only one wireless device, thereby extending the effective communication range of the access point.

IEEE 802.11 protocols comprise negotiation-of-device or device-type negotiation using Information Elements. In a specific example, a server may send to a client a device-type inquiry, to which a device-type response is made by the client. These information elements carry only device information.

It is well known that vendor specific information can be carried in the information elements (IE's). However, information in IE's which is vendor specific cannot be used by wireless devices which are made by another vendor. In addition, information in IE's which is vendor specific cannot be used by applications available via the wireless network.

There is a need for a system which is uses information elements for additional purposes.

SUMMARY

The present invention relates to providing new capabilities for the IEEE 802.11 beacon.

In 802.11, data frames carry information from higher layers. However, management and control frames must be provided that support data transfer. The beacon frame is a type of management frame. A wireless local network requires these management frames for stations to establish and maintain communications.

A typical beacon frame is about fifty bytes long. It contains a common frame header and cyclic redundancy checking field, including others. The beacon also contains a service set identifier (SSID). The SSID identifies a specific wireless local area network. Before associating with said network, a wireless device must have the same SSID as the access point.

In ad hoc networks, the communication is point-to-point, not through access points. Thus, one of the wireless devices must take on responsibility for sending the beacon.

It is an object of the invention to provide application protocols for local wireless networks and personal area networks that provide for connection of one wireless device to another and thereafter having the wireless devices exchange capabilities. Capabilities of the devices are those known in the art. This mode of the invention may not work if the peer wireless devices do not or cannot associate at that time. For example, a wireless device enabled for IEEE 802.11 communication can only associate to one other wireless device at a time. Under that current protocol, it is impossible to connect to another network or system to determine capabilities beyond those in the devices beacon.

The IEEE 802.11 beacon is able to transmit a 32-character network identifier. This network identifier is only intended to carry the name of the network. Actual capabilities of the network are carried in other IE's. The invention system comprises additional uses for the SSID to include reliable and secure capability encoding. The SSID in the system can be controlled by applications and transmitted with periodic broadcasting or point to point communication, so interoperable communication of application or user preferences/capabilities/membership can be transmitted and quickly determined by peers.

BRIEF DESCRIPTION OF DRAWINGS

There are no drawing figures.

DESCRIPTION

The following are specific examples of the invention system.

The IEEE 802.11 beacon SSID is adapted to serve as a capabilities encoding channel.

For example, encoded capabilities and preferences are incorporated into the SSID to determine:

Group membership: such as invited members of a conference or game playing group.

User preferences:

Device capabilities:

System location:

Game state: such as a point of play in a computer game. Encryption and security preferences:

Application software state: such as viewing a specific file.

The following are further examples of the invention system incorporating the use of SSID transmission of information:

Encoding of information where the information is encrypted.

Encoding of information: such as where information is integrity protected (checksum, secure hash, keyed hash, digital signature).

Encoding of information as a unique hash of capabilities.

Encoding as bit string with bits indicating capabilities.

Encoding where a bit string can have different encoding semantics based on receiver context.

Encoding used by peer mobile devices to alert user of proximity to another device.

Proximity used to indicate preferences of peer device user.

Proximity used as part of a game.

Encoding is encrypted to only allow access to information by approved peers.

Encoding is used as part of process to create encryption keys for subsequent communications.

After obtaining encoded SSID, device may use central server to assist in decoding.

Central server may return additional identity or location information.

Multiple different SSIDs can be used to define a single BSS.

Multiple different SSIDs can be used to define a single iBSS.

The above design options will sometimes present the skilled designer with considerable and wide ranges from which to choose appropriate apparatus and method modifications for the above examples. However, the objects of the present invention will still be obtained by that skilled designer applying such design options in an appropriate manner.

Claims

1. A first wireless device comprising:

a receiver configured to receive a beacon transmitted by a second wireless device, wherein the beacon includes a service set identifier, and wherein the service set identifier is encoded to include a capability of the second wireless device; and
a transmitter configured to transmit, to a server, the service set identifier received from the second wireless device,
wherein the service set identifier is decodable by the server to retrieve the capability of the second wireless device from the service set identifier, and
wherein the receiver is further configured to receive, from the server, the capability of the second wireless device subsequent to the server having decoded the service set identifier.

2. The first wireless device of claim 1, wherein the first wireless device is configured to communicate with the second wireless device in accordance with the capability of the second wireless device received from the server.

3. The first wireless device of claim 1, wherein the capability of the second wireless device encoded in the service set identifier comprises one or more of membership information, a user preference, a device capability, location information, an encryption and security preference, or a state of a software of the second wireless device.

4. The first wireless device of claim 1, wherein the service set identifier in the beacon received by the receiver includes an indication of a proximity of the second wireless device to the first wireless device.

5. The first wireless device of claim 1, wherein the capability of the second wireless device included in the service set identifier is based on a proximity of the second wireless device to the first wireless device.

6. The first wireless device of claim 1, wherein the first wireless device is configured to:

generate an encryption key based on the service set identifier, and
communicate with the second wireless device using the encryption key.

7. The first wireless device of claim 1, wherein the first wireless device communicates with the second wireless device via an ad-hoc network or an infrastructure network.

8. A method comprising:

receiving, at a first wireless device, a beacon transmitted by a second wireless device, wherein the beacon includes a service set identifier, and wherein the service set identifier is encoded to include a capability of the second wireless device; and
transmitting, from the first wireless device to a server, the service set identifier received from the second wireless device, wherein the service set identifier is decodable by the server to retrieve the capability of the second wireless device from the service set identifier; and
receiving, from the server, the capability of the second wireless device subsequent to the server having decoded the service set identifier.

9. The method of claim 8, further comprising communicating with the second wireless device in accordance with the capability of the second wireless device received from the server by the first wireless device.

10. The method of claim 8, wherein the capability encoded in the service set identifier comprises one or more of membership information, a user preference, a device capability, location information, an encryption and security preference, or a state of a software of the second wireless device.

11. The method of claim 8, further comprising receiving, from the service set identifier in the beacon received by the first wireless device, an indication of a proximity of the second wireless device to the first wireless device.

12. The method of claim 8, wherein the capability of the second wireless device included in the service set identifier is based on a proximity of the second wireless device to the first wireless device.

13. The method of claim 8, further comprising, at the first wireless device:

generating an encryption key based on the service set identifier, and
communicating with the second wireless device using the encryption key.

14. The method of claim 8, further comprising communicating with the second wireless device via an ad-hoc network or an infrastructure network.

Referenced Cited
U.S. Patent Documents
5735583 April 7, 1998 Katayama et al.
5738563 April 14, 1998 Comas et al.
5907566 May 25, 1999 Benson et al.
6182248 January 30, 2001 Armstrong et al.
6272120 August 7, 2001 Alexander
6287200 September 11, 2001 Sharma
6397357 May 28, 2002 Cooper
6587691 July 1, 2003 Granstam et al.
6600726 July 29, 2003 Nevo et al.
6690935 February 10, 2004 Calot et al.
6704866 March 9, 2004 Benayoun et al.
6707801 March 16, 2004 Hsu
6760587 July 6, 2004 Holtzman et al.
6785592 August 31, 2004 Smith et al.
6785892 August 31, 2004 Miller et al.
6788675 September 7, 2004 Yang
6793580 September 21, 2004 Sinclair et al.
6795701 September 21, 2004 Baker et al.
6799056 September 28, 2004 Curley et al.
6859460 February 22, 2005 Chen
6879574 April 12, 2005 Naghian et al.
6879812 April 12, 2005 Agrawal et al.
6909705 June 21, 2005 Lee et al.
6932698 August 23, 2005 Sprogis
6973580 December 6, 2005 Carroll et al.
7013391 March 14, 2006 Herle et al.
7024199 April 4, 2006 Massie et al.
7072323 July 4, 2006 Roberts et al.
7073129 July 4, 2006 Robarts et al.
7085257 August 1, 2006 Karves et al.
7087562 August 8, 2006 Abe et al.
7097562 August 29, 2006 Gagner
7136642 November 14, 2006 Massie et al.
7143171 November 28, 2006 Eriksson et al.
7162238 January 9, 2007 Massie et al.
7181544 February 20, 2007 Vangal et al.
7224964 May 29, 2007 Souissi et al.
7236772 June 26, 2007 Botzas
7251235 July 31, 2007 Wentink
7308263 December 11, 2007 Gallagher et al.
7324444 January 29, 2008 Liang et al.
7400722 July 15, 2008 Qi et al.
7435179 October 14, 2008 Ford
7440430 October 21, 2008 Jagadeesan et al.
7452278 November 18, 2008 Chen et al.
7656847 February 2, 2010 Mela et al.
7710982 May 4, 2010 Ohmuro et al.
7779334 August 17, 2010 Earle et al.
7817545 October 19, 2010 Ho et al.
7881284 February 1, 2011 Lin et al.
7899017 March 1, 2011 Yu et al.
7970384 June 28, 2011 Lambert et al.
8194600 June 5, 2012 Nagaraja
8194629 June 5, 2012 Agulnik et al.
8325659 December 4, 2012 Chen et al.
8374584 February 12, 2013 Lambert et al.
8411656 April 2, 2013 Liu
20020087370 July 4, 2002 Brueckheimer et al.
20020151366 October 17, 2002 Walker et al.
20020152388 October 17, 2002 Linnartz et al.
20020157044 October 24, 2002 Byrd
20020169539 November 14, 2002 Menard et al.
20020191560 December 19, 2002 Chen et al.
20020199124 December 26, 2002 Adkisson
20030065805 April 3, 2003 Barnes
20030069018 April 10, 2003 Matta et al.
20030088690 May 8, 2003 Zuckerman et al.
20030115320 June 19, 2003 Yarroll et al.
20030152093 August 14, 2003 Gupta et al.
20030169755 September 11, 2003 Ternovsky
20030182454 September 25, 2003 Huth et al.
20030224855 December 4, 2003 Cunningham
20030231189 December 18, 2003 Williams
20030231625 December 18, 2003 Calvignac et al.
20030235175 December 25, 2003 Naghian et al.
20040066751 April 8, 2004 Tseng et al.
20040081106 April 29, 2004 Bruhn
20040082383 April 29, 2004 Muncaster et al.
20040105415 June 3, 2004 Fujiwara et al.
20040120309 June 24, 2004 Kurittu et al.
20040127277 July 1, 2004 Walker et al.
20040174829 September 9, 2004 Ayyagari
20040185851 September 23, 2004 Nagai
20040196808 October 7, 2004 Chaskar et al.
20040203350 October 14, 2004 Shultz et al.
20040225932 November 11, 2004 Hoda et al.
20040236850 November 25, 2004 Krumm et al.
20040243887 December 2, 2004 Sharma et al.
20050025163 February 3, 2005 Christie
20050032577 February 10, 2005 Blackburn et al.
20050041660 February 24, 2005 Pennec et al.
20050041793 February 24, 2005 Fulton et al.
20050041796 February 24, 2005 Joseph et al.
20050058112 March 17, 2005 Lahey et al.
20050060547 March 17, 2005 Saito et al.
20050073980 April 7, 2005 Thomson et al.
20050079873 April 14, 2005 Caspi et al.
20050099977 May 12, 2005 Williams et al.
20050157661 July 21, 2005 Cho
20050177369 August 11, 2005 Stoimenov et al.
20050177639 August 11, 2005 Reunamaki et al.
20050181872 August 18, 2005 Acharya et al.
20050197189 September 8, 2005 Schultz
20050207342 September 22, 2005 Tanabe et al.
20050250487 November 10, 2005 Miwa et al.
20050250497 November 10, 2005 Ghosh et al.
20050268003 December 1, 2005 Wang et al.
20050286456 December 29, 2005 McNew et al.
20060041750 February 23, 2006 Carter et al.
20060045138 March 2, 2006 Black et al.
20060046709 March 2, 2006 Krumm et al.
20060063539 March 23, 2006 Beyer
20060135262 June 22, 2006 Kennedy et al.
20060166740 July 27, 2006 Sufuentes
20060172736 August 3, 2006 Nevo
20060205409 September 14, 2006 Chiou et al.
20060215576 September 28, 2006 Yu et al.
20060221857 October 5, 2006 Bushnell et al.
20060268711 November 30, 2006 Doradla et al.
20070026866 February 1, 2007 Krishnamurthi et al.
20070035513 February 15, 2007 Sherrard et al.
20070047547 March 1, 2007 Conner et al.
20070047697 March 1, 2007 Drewry et al.
20070060355 March 15, 2007 Amaitis et al.
20070060358 March 15, 2007 Amaitis et al.
20070076683 April 5, 2007 Chung et al.
20070082671 April 12, 2007 Feng et al.
20070086394 April 19, 2007 Yamada et al.
20070086401 April 19, 2007 Hong et al.
20070099703 May 3, 2007 Terebilo
20070197237 August 23, 2007 Powell et al.
20070202910 August 30, 2007 Brewer et al.
20070258415 November 8, 2007 Lu et al.
20070286111 December 13, 2007 Corson et al.
20080039015 February 14, 2008 Nakata et al.
20080052603 February 28, 2008 Wiatrowski et al.
20080069105 March 20, 2008 Costa et al.
20080082671 April 3, 2008 Meijer et al.
20080095112 April 24, 2008 Wiemann et al.
20080123608 May 29, 2008 Edge et al.
20080176561 July 24, 2008 Shao et al.
20080228547 September 18, 2008 Doss et al.
20090181728 July 16, 2009 Park
20090191878 July 30, 2009 Hedqvist et al.
20090222358 September 3, 2009 Bednarek
20090323648 December 31, 2009 Park et al.
20100093374 April 15, 2010 Dacosta
20100111066 May 6, 2010 Mehta
20100285776 November 11, 2010 de Froment
20110066369 March 17, 2011 Klassen et al.
20110066485 March 17, 2011 Rissanen
20110093876 April 21, 2011 Belz et al.
20110269431 November 3, 2011 Hardy et al.
20120095844 April 19, 2012 Barnes, Jr.
20120106728 May 3, 2012 Ghaffari et al.
20130096966 April 18, 2013 Barnes, Jr.
Other references
  • IEEE Standards Board.IEEE 802.11 Standard, 1999. 1999 Edition (R2003).
  • Newton, Harry: Newton's Telecom Dictionary: 15th Edition; Miller Freeman, Inc.; 1999; 3 pp.
  • “Universal Mobile Access: UMA Expands Beyond Dual-Mode Handsets”; The UMA Company; Jan. 200; 8 pages.
  • Meredith, John; “Voice Call Continuity in 3GPP”; CompactPCI and Advanced TCA Systems; Apr. 2006; 2 pages.
Patent History
Patent number: 9185732
Type: Grant
Filed: Mar 26, 2013
Date of Patent: Nov 10, 2015
Assignee: PICO MOBILE NETWORKS, INC. (Sunnyvale, CA)
Inventors: Saran Saund (Mountain View, CA), Paul A. Lambert (Mountain View, CA)
Primary Examiner: Andrew Lai
Assistant Examiner: Leon Andrews
Application Number: 13/850,875
Classifications
Current U.S. Class: Having Measuring, Testing, Or Monitoring Of System Or Part (455/67.11)
International Classification: H04J 3/00 (20060101); H04W 76/02 (20090101);