This invention relates to dissemination of application data, in particular Global Positioning System (GPS) ephemeris position data about GPS satellites, through management-packet communication using Wireless Local Area Networks (WLAN).
The reception of GPS satellite position data, used to create a position data (i.e., ephemeris data) in hybrid GPS/WLAN devices, may have problems indoors and in urban canyons. There is a need to wirelessly communicate such application data in coverage problem areas. Most, but not all, wireless communication in a WLAN is done by connection between an access point and stations. It would seem natural to consider connection-based solutions to these coverage problems.
Connection-based solutions for Assisted GPS (A-GPS) for GPS/WLAN devices exist, often disseminating the ephemeris via an (Internet Protocol) IP network from a server. They tend to be inconvenient, requiring the user to connect to a wired network in the home or office, or to use a wireless broadband connection in the home, office, or a hotspot. Many people do not have subscriptions. And explicit connection and download are cumbersome and time consuming.
Another connection-based solution is A-GPS via cellular Secure User Plane Location (SUPL) connection requiring cellular network subscription with tariffs, adding cost. This typically limits A-GPS capability to a single device (usually the user's personal phone) that is not available to the user's other devices, which may not have cellular network capability.
These connection-based solutions often rely on a web-based assistance server that is vulnerable to loss of connection to the server, web attacks on the server such as denial of service, and/or server failure through the financial insolvency of the server provider. Such connections usually require access permission, often involving log-on and/or an authentication processes.
Application data, such as an ephemeris of Global Positioning System (GPS) satellite positions, may be shared, without connection to a Wireless Local Access Network (WLAN), by management-packet communication between a station near an access point, and/or between access points, and/or between stations. The WLAN may be compatible with at least one wireless communication protocol that may comply with a version of an Institute for Electrical and Electronic Engineers (IEEE) 802.11 standard.
Management-packet communication of application data uses only management frames or packets to wirelessly communication the application data. It does not use standard connection based communications. The station does not need to connect or even know there is an access point nearby. The transfer of the application data requires no log-on, no authentication, no access permission and no need for the Internet. A station passing close to the access point suffices to transfer the ephemeris.
Two basic approaches may be implemented, a push and a pull approach. The push approach communicates the application data without a request. The pull approach first communicates a request and then communicates the application data in response to the request. The receiving device, whether an access point or a station, may respond with its application data if the beacon makes the request or with a request for the application data, if the beacon notes its availability.
An integrated circuit may support management-packet communications with a processor configured to support the WLAN and use management frames to communicate application data. The integrated circuit may be part of the access point and/or of the station. The processor may be further configured to use a beacon frame and/or its Information Element to communicate the application data, its availability, and/or request the application data.
The processor may include at least one instance of a finite state machine, a computer and/or a computer accessible memory configured for access by the computer to retrieve a program system to perform management-packet communication. Other embodiments include a computer readable memory and/or a server configured to communicate the program system and/or an installation package for installing the program system.
This invention relates to dissemination of application data, in particular, Global Positioning System (GPS) ephemeris position data about GPS satellites through management-packet communication using Wireless Local Area Networks (WLAN). As will be described below, in one embodiment, management-packet communication may occur without connecting to the WLAN. The ephemeris may be shared using the WLAN by performing management-packet communication between a station near an access point, and/or between a first and a second access point, and/or between a first and a second station. Management-packet communication may use only the management packets or frames of a wireless communications protocol employed by the WLAN. This use may involve only a part of the management frame, such as the information element of a beacon frame.
Referring to the drawings more particularly by reference numbers,
Management-packet communication 8 of the application data 71 may not use typical connection-based communications. The station 10 may not need to connect to a nearby access point 20. The transfer of the application data 71 requires no log-on, no authentication, no access permission and no need for access to the Internet. A station 10 passing close to the access point 20 suffices to transfer the ephemeris 70.
Management-packet communication 8 may be supported by an integrated circuit 30 including a processor 50 configured to support the WLAN 2 and use a management frame 69, such as a beacon frame 60 for management-packet communication 8. The processor 50 may be configured to operate an application 51 based upon the application data 71. The application 51 may be a form of GPS enabled navigator and/or use a GPS position. The integrated circuit 30 may be part of the access point 20 and/or of the station 10. The processor 50 may be further configured to use an Information Element 62 in the beacon frame 60 to perform management-packet communication 8 the application data 71, the availability of the application data, and/or the request for the application data.
The first access point 20 has received 6 the position data 72 for the GPS satellite 4 as shown in
The application data 71 may also include a quality estimate 74 that may indicate whether the ephemeris 70 and/or the position data 72 was directly received 6 from the GPS satellite 4. The quality measure 74 may also indicate how many transfers have been made since the data was received 6 from the GPS satellite 4. The quality estimate 74 may also indicate whether the original source of the GPS position data 72 and/or the ephemeris 70 may be from the Internet, possibly indicating the source on the Internet.
The application data 71 may include an estimate of the time in a local time zone and/or an estimate of a standard time such as Greenwich Mean Time and/or an estimate of a network time used in a WLAN and/or LAN. Similarly the application data 71 may include a location estimate that may or may not be derived from GPS position data 72 or the ephemeris 70.
An example of a push approach to management-packet communication 8 is shown in
The availability information 64 of the ephemeris 70 may be indicated within a beacon frame 60. The ephemeris 70 and/or the position data 72 may be sent in information elements 62 included in one or more of the beacon frames 60.
In alternative embodiments, the pull approach may occur between two stations 10 or two access points 20 with a similar transaction diagram to that shown in
Before proceeding, some background in the Open System Interconnection (OSI) model of communications is useful. Communications in the IEEE 802 family of standards are based upon the OSI model, which has seven layers, of which the following are relevant: the physical (second from the bottom) layer, the presentation (sixth) layer and the application (seventh and highest) layer. The physical layer typically deals with messaging conventions of the wireless communication protocol 80. The presentation layer normally provides the communication context for the sharing of the application data 71 for the applications 51 on the application layer. Management-packet communication 8 essentially moves the sharing of the application data 71 down to the physical layer, below the level of connection-based communications.
To summarize some of the preceding discussion, management-packet communication 8 may be supported by the integrated circuit 30 including the processor 50 configured to support the WLAN 2 and the management-packet communication 8. The integrated circuit 30 may be part of the access point 20 and/or of the station 10 as shown in
As used herein, the computer 54 may include at least one instruction processor and at least one data processor, with at least one of the data processors instructed by at least one of the instruction processors to at least partly implement management-packet communication 8 using the program system 90. These operations may be at least partly illustrated the program steps of
As used herein, ad hoc or peer to peer messaging 132 occurs when there is no access point 20 available to direct the WLAN 2 communications between those stations 10. Most implementations of ad hoc messaging involve the stations 10 each temporarily acting as an access point 20 by sending the beacon frame 60. This station 10 will be referred to as an access station. The other stations 10 may respond with probe requests 66 and the temporary access station 10 may respond to those probe requests 66, possibly with the next beacon frame 60, creating similar exchanges to those shown and discussed earlier regarding
The program system 90 may include at least one of the following: Program step 100 supporting management-packet communication 8 between at least one of the stations 10, and at least one of the access points 20. Program step 102 supporting management-packet communication 8 between two access points 20. Program step 104 supporting management-packet communication 8 between two of the stations 10. Any of these program steps may further support sharing the ephemeris 70 and/or the position data 72. Support for management-packet communication 8 as found in at least one of these program steps may include management-packet communication 8 in the push mode illustrated in
The program system 90 may support operating the integrated circuit 30 of
The preceding embodiments provide examples and are not meant to constrain the scope of the following claims.
This application claims the benefit of the priority date of the U.S. provisional patent application Ser. No. 61/332,640, filed May 7, 2010 entitled Management-Packet Communications of GPS Satellite Positions, which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6108558 | Vanderspool | Aug 2000 | A |
6801782 | McCrady et al. | Oct 2004 | B2 |
7057557 | Lee | Jun 2006 | B2 |
7065369 | Tang et al. | Jun 2006 | B2 |
7215966 | Joshi | May 2007 | B2 |
7574216 | Leitch et al. | Aug 2009 | B2 |
7800531 | Wang et al. | Sep 2010 | B2 |
7877100 | Rick et al. | Jan 2011 | B2 |
8026850 | Seong et al. | Sep 2011 | B2 |
8160609 | Alles et al. | Apr 2012 | B2 |
8184038 | Ekbal et al. | May 2012 | B2 |
8233457 | Chen et al. | Jul 2012 | B1 |
8335173 | Hart et al. | Dec 2012 | B2 |
8370629 | Ngo et al. | Feb 2013 | B1 |
20020194266 | Brebner et al. | Dec 2002 | A1 |
20030103475 | Heppe et al. | Jun 2003 | A1 |
20030118015 | Gunnarsson et al. | Jun 2003 | A1 |
20050124319 | Williams et al. | Jun 2005 | A1 |
20050124355 | Cromer et al. | Jun 2005 | A1 |
20060052115 | Khushu | Mar 2006 | A1 |
20060148486 | Kim et al. | Jul 2006 | A1 |
20070025296 | Jung et al. | Feb 2007 | A1 |
20070103303 | Shoarinejad | May 2007 | A1 |
20070121560 | Edge | May 2007 | A1 |
20070276583 | Dobeck et al. | Nov 2007 | A1 |
20080109885 | Sim et al. | May 2008 | A1 |
20080291883 | Seok | Nov 2008 | A1 |
20090079622 | Seshadri et al. | Mar 2009 | A1 |
20090093956 | Wu et al. | Apr 2009 | A1 |
20090121927 | Moshfeghi | May 2009 | A1 |
20090224967 | Wang et al. | Sep 2009 | A1 |
20100135178 | Aggarwal et al. | Jun 2010 | A1 |
20120269170 | Chen et al. | Oct 2012 | A1 |
Number | Date | Country |
---|---|---|
0320913 | Jun 1989 | EP |
1253437 | Oct 2002 | EP |
1587255 | Oct 2005 | EP |
WO 2005006593 | Jan 2005 | WO |
Number | Date | Country | |
---|---|---|---|
61332640 | May 2010 | US |