HK1149676B

HK1149676B - A communication method and communication system

Info

Publication number: HK1149676B
Application number: HK11103765.4A
Authority: HK
Inventors: 安德烈‧科瑟洛博瓦; 大卫‧艾伯特‧伦德格伦
Original assignee: 美国博通公司
Priority date: 2009-04-08
Filing date: 2011-04-14
Publication date: 2014-03-28

Description

Communication method and communication system

Technical Field

The present invention relates to communication systems, and more particularly, to a method and system for dynamic wireless node acquisition for LBS servers, clients, and reference databases (reference databases).

Background

Mobile Location services, also called Location Based Services (LBS), are value-added services provided by mobile communication networks. Knowing the user's location enables obtaining various LBS applications such as enhanced911 (E-911) based, location 411 based, location based messages and/or buddy finding. Improving the positioning method for determining the position of a user bound to an associated communication device, such as a mobile phone, has been a driving force behind the LBS market. Positioning of mobile devices is provided using various methods, such as Satellite-based systems, including Global Navigation Satellite Systems (GNSS) such as the GPS, GLONASS, and GALILEO. The GNSS is a system using earth-orbiting constellations (earth-orbiting constellations) of a plurality of satellites, each of which broadcasts GNSS signals indicating precise position and range information (ranging information).

Other drawbacks and disadvantages of the prior art will become apparent to one of ordinary skill in the art upon examination of the following system of the present invention as described in conjunction with the accompanying drawings.

Disclosure of Invention

The present invention, in various aspects, is directed to a method and system for dynamic wireless node acquisition for LBS server, client and reference database (reference database), substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.

According to an aspect of the invention, the invention proposes a communication method, the method comprising:

performing, by one or more processors and/or circuits in a Global Navigation Satellite System (GNSS) enabled mobile device, the steps of:

transmitting a device Radio Frequency (RF) environment report to a location server;

receiving a profile from the location server; and

generating a new RF environment report based on the received acquisition profile.

Preferably, the device RF environment report includes a status of one or more radio transceivers (radios) encountered, a status of power and/or storage resources of the GNSS enabled mobile device, and/or a change in location.

Preferably, the acquisition profile includes information that the location server desires to receive a desired RF environment report from the GNSS enabled mobile device.

Preferably, the location server determines the acquisition profile of the GNSS enabled mobile device based on the RF environment report and a reference database.

Preferably, the method further comprises capturing RF environment data from the received captured material.

Preferably, the method further comprises time and location tagging the captured RF environment data.

Preferably, the method further comprises generating the new device RF environment report using the time and location tagged RF environment data.

Preferably, the method further comprises sending the generated new device RF environment report to the location server.

Preferably, said reference database is updated in dependence of said received new device RF environment report.

Preferably, the location server locates the GNSS enabled mobile device in accordance with the updated reference database.

According to still another aspect of the present invention, there is provided a communication system including:

one or more processors and/or circuitry in a Global Navigation Satellite System (GNSS) enabled mobile device, wherein the one or more processors and/or circuitry are to:

receiving a profile from the location server; and

Preferably, the one or more processors and/or circuits are operable to capture RF environment data from the received capture material.

Preferably, the one or more processors and/or circuits are operable to time and location stamp the captured RF environment data.

Preferably, the one or more processors and/or circuits are operable to generate the new device RF environment report using the time and location tagged RF environment data.

Preferably, the one or more processors and/or circuits are operable to send the generated new device RF environment report to the location server.

The following detailed description of specific embodiments is provided to facilitate an understanding of various advantages, aspects, and novel features of the invention as they may be better understood when considered in connection with the accompanying drawings.

Drawings

FIG. 1 is a schematic diagram of an exemplary communication system for dynamically acquiring wireless nodes of an LBS server, client and reference database in accordance with an embodiment of the present invention;

FIG. 2 is an exemplary LBS client device that dynamically generates and provides RF environment reports to an LBS server based on RF environment acquisition profiles in accordance with an embodiment of the present invention;

FIG. 3 is a schematic block diagram of an exemplary LBS server that dynamically acquires wireless nodes using device RF environment reports from LBS client devices in accordance with an embodiment of the present invention;

fig. 4 is a flow chart of an exemplary process for dynamic wireless node acquisition for LBS servers, clients and reference databases, in accordance with an embodiment of the invention.

Detailed Description

Various embodiments of the present invention propose a method and system for dynamic wireless node acquisition for LBS servers, clients, and reference databases (reference databases). In various embodiments of the present invention, a GNSS enabled mobile device may be operable to transmit a device RF environment report to a location server. The GNSS enabled LBS client device is then operable to receive the acquisition profile from the location server. The device RF environment report includes various RF information encountered by the GNSS enabled LBS client device. For example, the encountered RF information includes status information of one or more wireless transceivers (radios), status information of the power and/or storage resources of the GNSS enabled LBS client device, and/or location change (positioning variable). The received acquisition profile includes information of a desired RF environment report that the location server desires the GNSS enabled LBS client device to provide. The location server determines a capture profile for the GNSS enabled LBS client device based on the received RF environment report and a reference database, the reference database being coupled to the A-GNSS server. A GNSS enabled LBS client device is operable to capture desired RF environment data from the received acquisition profile. The LBS client software is shown to time and location stamp the captured RF environment data. The GNSS enabled LBS client device is operable to generate a new device RF environment report using the time and location tagged RF environment data. Sending the generated new device RF environment report to a location server. The location server is operable to communicate with the a-GNSS server to update the reference database in accordance with the new device RF environment report received. The location server may use the updated reference database to locate relevant mobile devices such as GNSS enabled LBS client devices, if desired.

Fig. 1 is a schematic diagram of an exemplary communication system for dynamically acquiring wireless nodes of an LBS server, client and reference database, in accordance with an embodiment of the invention. Referring to fig. 1, a communication system 100 is shown. The communication system 100 includes a plurality of LBS client devices 110 (LBS client devices 110a-110e are shown), an LBS server 120, an assisted GNSS server 122 (including a reference database 122a), a Satellite Reference Network (SRN)130, a GNSS satellite architecture 140, a bluetooth network 150, a Wireless Local Area Network (WLAN)160, a cellular network 170, a Worldwide Interoperability for Microwave Access (WiMAX) network 180, and a broadcast network 190. The GNSS satellite architecture 140 includes a plurality of GNSS satellites, of which GNSS satellites 140a-140c are shown. WLAN150 includes a plurality of WLAN access points, such as WLAN Access Points (APs) 160a and 160 b. Cellular network 170 and WiMAX network 180 include a plurality of Base Stations (BSs), of which base stations 180a-180b and base stations 190a-190b are shown. The broadcast network 190 includes a plurality of broadcast towers such as broadcast tower 190 a.

The LBS client device, such as LBS client device 110a, may comprise suitable logic, circuitry, interfaces and/or code that may be operable to communicate radio frequency signals with a communication network, such as bluetooth network 150. Depending on the capabilities of the device, LBS client device 110a may be used to acquire RF environment data for various wireless nodes encountered, such as WLAN APs 160a-160b, broadcast station 190a, BSs 170a-170b, and/or BSs 180a-180 b. The captured RF environment data includes RF environment information that the LBS client device 110a has encountered and/or is encountering. The captured RF data may include RF environment information that may be used to dynamically acquire and/or locate encountered wireless nodes for the LBS server 120, associated LBS clients, and a reference database 122a, the reference database 122a being integrated into the assisted GNSS server 122 or connected to the GNSS server 122. The captured RF environment information includes, for example, the status of wireless transceivers (radio, or wireless signals) encountered, such as 2G or 3G cellular wireless transceivers, WiMAX wireless transceivers, GNSS wireless transceivers, WiFi wireless transceivers, FM wireless transceivers, and/or bluetooth wireless transceivers; power and/or status of stored information for the LBS client device 110 a; and/or information such as speed, heading, and location change of the LBS client device 110 a. Assuming that LBS client device 110a is a GNSS enabled device, LBS client device 110a is operable to receive GNSS Radio Frequency (RF) signals from visible GNSS satellites, such as GNSS satellites 140a-140 c. The received GNSS RF signals are used to calculate a position fix for the LBS client device 110 a. In this regard, the LBS client device 110a is used to time and location stamp the captured RF environment data. The LBS client device 110a is used to generate a device RF environment report using the time and location tagged RF environment data and send to the LBS server 120. In this regard, the LBS client device 110a is configured to receive an assigned device capture profile (profile) from the LBS server 120. The assigned device capture profile includes desired RF environment data or information that the LBS client device 110a is expected to collect and/or provide to the reference database 122a of the assisted GNSS server 122. The LBS client device 110a is used to capture desired RF environment data from the assigned device capture profile. The desired RF environment data captured is time-lapse and location-tagged. The LBS client device 110a is used to generate a new device RF environment report using the time and location stamped expected RF environment data. The LBS client device 110a is configured to send the new generated device RF environment report to the LBS server 120 to optimize LBS performance, e.g., the new generated device RF environment report may be a dynamic capture wireless node of the LBS server 120 and associated LBS client. The new device RF environment report generated is used to establish and/or optimize (refine) the reference database 122a of the assisted GNSS server 122 over time (over time) to enable the captured wireless node to be accurately located for use as a reference node for locating a relevant mobile wireless device, such as the LBS client device 110a, to obtain LBS services.

The LBS server 120 may comprise suitable logic, apparatus, and/or code that may enable re-acquisition of location information for an associated user. The LBS server 120 is used to receive multiple device RF environment reports from the relevant LBS client device, such as LBS client device 110 a. The device RF environment report from an LBS client device, such as LBS client device 110a, includes time and location stamped RF environment information indicating wireless nodes encountered or detected by the LBS client device. The LBS server 120 is operable to communicate with the assisted GNSS server 122 to compare the received device RF environment report with a portion of the reference database proximate the detected wireless node.

The LBS server 120 is used to generate device capture profiles assigned to the LBS client device 110a based on the reported RF environment information and the status of the reference database 122 a. For example, assuming that the reported RF environment information indicates that the LBS client device 110a has sufficient power and/or memory and is in an area not widely set by the reference database 122a, the LBS server 120 may command the LBS client device 110a to forcibly capture or map (map) the device RF environment data for that area in the generated capture profile. However, conversely, assuming that the reported RF environment information indicates that the LBS client device 110a has less power and/or memory and is in a sufficiently mapped area such that the reference database 122a does not require additional information at the present time, the LBS client device 110a may be instructed to capture or map the device RF environment data in a reduced manner (augmented manager) or simply not. Thus, the generated capture profile includes the desired device RF environment information that the LBS server 120 wishes the client device 110a to provide.

In an exemplary embodiment of the invention, the generated capture profile includes information such as the state of the reference database 122a (coverage, update, depth), and/or the sampling rate at which the reference database data is captured at the current and/or future location. In addition, the generated capture profile also includes information such as the duration of time each relevant wireless transceiver continues to be sampled and when the LBS client device 110a should upload a device RF environment report (in time vs next possible access). Assuming that the LBS client device 110a does not have sufficient resources, such as battery power, the LBS client device 110a may defer updating the RF environment report until sufficient battery power is available. The LBS server 120 is used to send the generated capture profile to the LBS client device 110 a. In response, the LBS server 120 is used to receive a new device RF environment report, which is created by the LBS client device 110a based on the assigned capture profile. The LBS server 120 may be configured to communicate the received new device RF environment report to the assisted GNSS server 122 in order to build and/or refine the reference database 122 a.

The assisted GNSS server 122 may comprise suitable logic, circuitry and/or code that may be enabled to access a Satellite Reference Network (SRN)130 to acquire GNSS satellite data by tracking a GNSS constellation at the SRN 130. The assisted GNSS server 122 is configured to build a reference database 122a using the collected GNSS satellite data. The reference database 122a may comprise suitable logic, circuitry and/or code that may enable storage of reference positions that may be utilized to provide GNSS assistance data to an associated user in support of LBS services. In this regard, the assisted GNSS server 122 is operable to communicate with the LBS server 120 and provide reference location information in the vicinity of one or more wireless nodes indicated by the LBS server 120. The assisted GNSS server 122 is used to further receive location information from the LBS server 120 in the vicinity of one or more wireless nodes to augment the reference database 122 a. The received location information for one or more wireless nodes is retrieved by the LBS server 120 from a device RF environment report received from an autocorrelation LBS client device, such as LBS client device 110 a. The assisted GNSS server 122 may be operable to communicate information in an exemplary format (format) that is compatible with telecommunication networks such as GSM/UMTS, WiMAX, WiFi and/or Bluetooth. For example, the assisted GNSS server 122 may be compatible with the GSM/UMTS standards by supporting messages in the RRLP format, the PCAP interface, and/or OMA SUPLv1.0. The assisted GNSS server 122 is configured to communicate with the LBS server 120 through a user interface or a control interface, so as to achieve seamless connection with the LBS server 120.

A GNSS satellite such as GNSS satellite 140a may comprise suitable logic, circuitry, interfaces and/or code that may be operable to broadcast satellite navigation information to a plurality of GNSS satellites on earth. GNSS receivers, including GPS, GALEO and/or GLONASS receivers, may be internally integrated with or externally connected to GNSS enabled communication devices such as the LBS client devices 110a-110 e. Broadcast satellite navigation information such as ephemeris may be used to calculate, for example, position, velocity, and/or clock information for the GNSS receiver. In this regard, the computed position information of the GNSS clock and the GNSS receiver is used to time-stamp and position-stamp the device RF environment information at the GNSS receiver.

The SRN130 may comprise suitable logic, circuitry, and/or code that may enable continuous collection and distribution of data for GNSS satellites. The SRN130 includes a plurality of GNSS reference tracking stations around the earth to provide assisted GNSS coverage of home networks and visited networks (visited networks) at any time, allowing users of GNSS enabled devices, such as LBS client devices 110a-110d, to enjoy relevant LBS services while roaming anywhere in the world.

The GNSS satellites 140a-140 may comprise suitable logic, circuitry and/or code that may be operable to generate and broadcast satellite navigation information in the form of suitable Radio Frequency (RF) signals to a plurality of GNSS enabled devices, such as the LBS client devices 110a-110 e. In this regard, the RF environment information, such as GNSS RF signal strength, received by the LBS client devices 110a-110e is time and location stamped for reporting to the LBS server 120.

The bluetooth network 150 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to provide data services to a plurality of bluetooth enabled mobile devices, such as the LBS client device 110 a. The bluetooth network 150 is used to transmit various data services such as location-based services in the form of bluetooth RF signals through bluetooth devices such as the LBS client device 110 a. In this regard, RF environment information, such as bluetooth RF signal strength, transmitted by the LBS client device 110a is time and location stamped for reporting to the LBS server 120.

The wireless LAN160 may comprise suitable logic, circuitry, interfaces and/or code that may enable the use of wireless LAN technology to provide data services to a plurality of wireless LAN enabled communication devices, such as the LBS client device 110 b. Exemplary wireless LAN technologies include, for example, IEEE std802.11, 802.11a, 802.11b, 802.11d, 802.11e, 802.11n, 802.11v, and/or 802.11 u. The wireless LAN160 is used to transmit various data services such as Location Based Services (LBS) in the form of WLAN RF signals through the wireless LAN AP and WLAN-enabled devices such as the LBS client device 110 a. In this regard, RF environment information such as WLAN RF signal strength and/or location information of an associated WLAN AP such as WLAN AP160a transmitted by the LBS client device is time and location stamped for reporting to the LBS server 120.

The cellular network 170 may comprise suitable logic, devices, interfaces and/or code that may enable the provision of data services to a plurality of associated mobile devices, such as the LBS client devices 110a-110e, using cellular communication techniques. Cellular communication technologies include, for example, global system for mobile communications (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), enhanced data rates for GSM evolution (EDGE), enhanced GPRS (egprs), and/or 3GPP Long Term Evolution (LTE). The cellular network 170 is used to communicate various data services, such as location-based services, with associated mobile devices, such as the LBS client device 110a, in the form of cellular RF signals, through associated base stations, such as BS170 a. In this regard, RF environment data, such as cellular RF signal strength received by LBS client device 110a and/or location information of the relevant BS, such as BS170a, is time and location stamped for reporting to LBS server 120.

The WiMAX network 180 may comprise suitable logic, devices, interfaces and/or code that may be operable to provide data services to a plurality of associated mobile devices such as the LBS client devices 110a-110e using WiMAX technology. WiMAX network 180 is used to communicate various data services, such as location-based services, with associated mobile devices, such as LBS client device 110a, in the form of WiMAX RF signals through an associated base station, such as BS180 a. In this regard, RF environment data such as WiMAX RF signal strength received by LBS client device 110a and/or location information of the relevant BS such as BS180a are time and location stamped for reporting to LBS server 120.

The broadcast network 190 may comprise suitable logic, circuitry and/or code that may be enabled to allocate a single carrier frequency to broadcast programs (broadcastprograms) of a plurality of associated mobile devices, such as the LBS client devices 110a-110 e. The broadcast network 190 is used to transmit broadcast programs in the form of corresponding RF signals using various broadcast technologies such as FM, DAB, DVB-H, DVB-SH, and/or DVB-T. In this regard, RF environment data such as WiMAX RF signal strength received by LBS client device 110a and/or location information of the relevant BSs such as broadcast base station 190a are time and location stamped for reporting to LBS server 120.

In an exemplary operation, an LBS client device, such as LBS client device 110a, is used to capture encountered RF environment data using LBS client software. The captured RF environment data includes RF environment information, such as RF signal strength received from the bluetooth network 150 and/or WiMAX network 180, which may be used to dynamically capture and/or detect encountered wireless nodes for the reference database 122a of the LBS server 120, related LBS clients, and assisted GNSS server 122. The LBS client device 110a is used to time and location tag the captured RF environment data to generate a device RF environment report. The generated device RF environment report indicates wireless nodes encountered or detected by the LBS client device. The generated device RF environment report may be transmitted to the LBS server 120.

The LBS server 120 is operable to communicate with the assisted GNSS server 122 to obtain a portion of a reference database in the vicinity of the detected wireless node as indicated by the received device RF environment report. The LBS client device 110a is operable to compare the received device RF environment report with a portion of the reference database 122a in the vicinity of the detected wireless node. The LBS server 120 may be configured to identify desired RF environment information for the assisted GNSS server 122 to build and/or optimize the reference database 122 a. The LBS server 120 is used to generate the capture profile assigned to the LBS client device 110 a. The generated capture profile includes instructions that instruct the LBS client device 110a to respond to encountered wireless nodes in order to capture and/or provide the identified desired RF environment information for the reference database 122 a. The LBS server 120 is used to send the generated capture profile to the LBS client device 110 a. The LBS client device 110a is used to capture and/or collect RF environment data from the received capture profile. The captured RF environment data is time and location stamped to generate a new device RF environment report. The LBS client device 110a is operable to send the generated new device RF environment report to the LBS server 120. The LBS server 120 is configured to transmit corresponding location information of encountered wireless nodes to the assisted GNSS server 122 in order to build and/or augment the reference database 122a to optimize LBS performance.

Fig. 2 is an exemplary LBS client device that dynamically generates and provides RF environment reports to an LBS server based on RF environment acquisition profiles, in accordance with an embodiment of the present invention. Referring to fig. 2, an LBS client device 200 is shown. The LBS client device 200 includes a processor 201, GNSS wireless transceiver 202, WLAN wireless transceiver 204, bluetooth wireless transceiver 206, cellular wireless transceiver 208, WiMAX wireless transceiver 210, FM wireless transceiver 212, device RF environment database 214, and memory 216. The processor 201 includes LBS client software 201 a.

The processor 201 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to manage and/or control the operation of associated components such as the GNSS radio 202, the WLAN radio 204, the Bluetooth radio 206, the cellular radio 208, the WiMAX radio 210, the FM radio 212, the device RF environment database 214 and/or the memory 216, depending on the respective application. For example, the processor 201 may be configured to activate or deactivate one or more associated wireless transceivers, such as the GNSS wireless transceiver 202 and/or the cellular wireless transceiver 208, based on a need to conserve power. The processor 201 is used to run the LBS client software 201a through its experience with the active wireless transceiver module (e.g., WLAN wireless transceiver 204) to capture RF environment data. The LBS client software 201a is application software installed in the LBS client apparatus 200. LBS client software 201a is used to detect and mark in time and location the characteristics of RF nodes encountered by the LBS client device during communication. The captured RF environment data includes RF environment information about the activated wireless transceiver. For example, assuming that the GNSS radio 202, the WLAN radio 204, and the cellular radio 208 are active, the processor 201 is configured to capture RF environment information associated with corresponding communications on the GNSS radio 202, the WLAN radio 204, and the cellular radio 208, respectively. The captured RF environment information includes, for example, the status of encountered wireless transceivers, such as GNSS wireless transceivers, WLAN wireless transceivers, and 2G or 3G cellular wireless transceivers, the power level of the LBS client device 200 and/or the status of stored information, information such as velocity, direction (heading), and location change of the LBS client device 200, and/or location information of the relevant wireless nodes, such as WLAN AP160a and/or BS170 a. The location information of the relevant wireless node includes specific physical location information, such as a location-related identification code, location parameters, and/or the location of the relevant wireless node. Processor 201 is configured to dynamically capture a wireless node, such as BS170a, from the captured RF environment information. The processor 201 is configured to time and location tag the captured RF environment information using the relevant GNSS location and store in the device RF environment database 214. The processor 201 is used to generate device RF environment reports using data in the device RF environment database 214, if needed. The processor 201 is used to send the generated device RF environment report to the LBS server 120. The processor 201 is used to receive the assigned device capture profile from the LBS server 120. The assigned device capture profile includes instructions to transmit desired RF environment data or information from the LBS server 120. The processor 201 is used to run LBS client software 201a to capture desired RF environment data from assigned device capture profiles. The processor 201 is used to time and location tag the desired RF environment information captured and stored in the device RF environment database 214. The processor 201 is used to generate a new device RF environment report using the captured desired RF environment information and notify the LBS server 120 in order to optimize LBS performance. For example, the newly generated device RF environment report provides information to the LS server to dynamically capture wireless nodes that may be used as reference nodes for locating LBS client devices 200 for LBS services.

The GNSS radio 202 may comprise suitable logic, interfaces and/or code that may be operable to detect or track GNSS radio frequency signals received from visible GNSS satellites such as the GNSS satellites 140a-140 c. In this regard, the detected or tracked GNSS RF signal strengths are captured by LBS client software as RF environment information for the device RF environment database 214.

The WLAN wireless transceiver 204 may comprise suitable logic, interfaces and/or code that may enable transmitting and receiving WLAN Radio Frequency (RF) signals. The WLAN radio frequency signals are transmitted in a format compatible with various WLAN standards, such as IEEE std802.11, 802.11a, 802.11b, 802.11d, 802.11e, 802.11n, 802.11v, and/or 802.11 u. The WLAN wireless transceiver 204 is used to receive continuous, aperiodic or periodic WLAN radio frequency signals from, for example, the WLAN AP160a in the WLAN 160. In this regard, the status of the received WLAN RF signals, such as the strength of the received WLAN RF signals and/or location information of the WLAN ap160a, may be captured by the LBS client software as RF environment information for the device RF environment database 214. The state may be captured continuously, aperiodically or periodically.

The bluetooth wireless transceiver 206 may comprise suitable logic, interfaces and/or code that may enable transmitting and receiving bluetooth Radio Frequency (RF) signals. The bluetooth wireless transceiver 206 is configured to receive bluetooth radio frequency signals from the bluetooth network 150. In this regard, the status of the received bluetooth RF signal, such as the strength of the received bluetooth RF signal, may be captured by the LBS client software as RF environment information for the device RF environment database 214. The state may be captured continuously, aperiodically or periodically.

The cellular wireless transceiver 208 may comprise suitable logic, devices, interfaces and/or code that may be operable to transmit and receive wireless cellular radio frequency signals, such as 2G/2.5G/3G/4G RF signals. The cellular wireless transceiver 208 is used to receive cellular RF signals from the BS170a in the cellular network 170. In this regard, the status of the received cellular RF signals, such as the strength of the received cellular RF signals and/or the location information of BS170a, may be captured by the LBS client software as RF environment information for the device RF environment database 214. The status may provide an indication of whether the traffic is light or heavy. The state may be captured continuously, aperiodically or periodically. The captured location information of BS170a includes location related parameters such as cell ID (cell ID), Radio Network Controller (RNC) ID, and/or base station ID.

The WiMAX wireless transceiver 210 may comprise suitable logic, devices, interfaces and/or code that may be operable to transmit and receive wireless WiMAX radio signals. The WiMAX wireless transceiver 210 is used to receive WiMAX RF signals from the BS180a in the WiMAX network 180. In this regard, the status of the received WiMAX RF signals, such as the strength of the received WiMAX RF signals and/or the location information of BS180a, may be captured by the LBS client software as RF environment information for the device RF environment database 214. The status may provide an indication of whether the traffic is light or heavy. The state may be captured continuously, aperiodically or periodically. The captured location information for BS180a includes location related parameters such as a base station ID.

The FM radio transceiver 212 transmits and receives FM radio signals from, for example, a broadcast station 190a in the broadcast network 190. The received FM RF signal includes RDS data over the FM band. In this regard, the strength of the received FM RF signal and/or the location information of the broadcast station 190a may be captured by the LBS client software as RF environment information for the device RF environment database 214.

The device RF environment database 214 may comprise suitable logic, circuitry, and/or code that may enable storage of RF environment data captured via RF procedures (expeiencies) of the LBS client device 200. The stored environment data is time and location stamped. The device RF environment database 214 is used to provide corresponding RF environment data for generating device RF environment reports that are provided to the LBS server 120. The device RF environment database 214 is used to manage and update the stored RF environment data.

The memory 216 may comprise suitable logic, circuitry, and/or code that may enable storage of information such as executable instructions and data for use by the processor 201 and/or other associated components such as the GNSS radio 201. Memory 216 includes RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage.

In operation, the processor 201 is operable to manage and/or control the operation of the associated components, such as the GNSS radio 202, the WLAN radio 204, and the cellular radio 208, depending on the respective application. One or more associated wireless transceivers, such as the GNSS wireless transceiver 202 and/or the cellular wireless transceiver 208, may be activated or deactivated whenever desired. The processor 201 is used to capture RF environment data of its RF processes (expeiences) using LBS client software 201 a. The captured RF environment is used to dynamically capture a wireless node, such as BS170 a. The processor 201 is used to time and location tag the captured RF environment information and store it in the device RF environment database 214. The device RF environment report may be generated using data in the device RF environment database 214 whenever needed. The processor 201 is used to send the generated device RF environment report to the LBS server 120 and in turn receive the assigned device capture profile. The assigned device capture profile includes instructions to transmit desired RF environment data or information from the LS server 120. The processor 201 is used to capture desired RF environment data by the LBS client software 201a according to the assigned device capture profile. The desired information captured is time and location stamped and stored in the device RF environment database 214. New device RF environment reports are generated using the captured desired RF environment information and notified to the LBS server 120 in order to optimize LBS performance.

Fig. 3 is a schematic block diagram of an exemplary LBS server using device RF environment reports from LBS client devices to dynamically acquire wireless nodes, in accordance with an embodiment of the invention. Referring to fig. 3, an LBS server 300 is illustrated. The LBS server 300 includes a processor 302, a client location database 304, and a memory 306.

The processor 302 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to manage and/or control the operation of the client location database 304 and the memory 306. The processor 302 is configured to receive a plurality of device RF environment reports from an associated LBS client device, such as LBS client device 110 a. The received device RF environment report includes RF environment information indicating wireless nodes encountered or detected by the corresponding LBS client device. The processor 302 is configured to communicate with the assisted GNSS server 122 to compare the received device RF environment report with a corresponding portion of the reference database 122a in the vicinity of the detected node. The processor 302 is configured to generate a device capture profile for each received device RF environment report based on the corresponding reported RF environment information and the status of the reference database 122 a. Assuming that the reported RF environment information indicates, for example, that LBS client device 110a has sufficient power and/or memory and is in an area not widely provisioned with reference database 122a, processor 302 may generate a capture profile and instruct LBS client device 110a to force capture or map (map) of the device RF environment data for that area. Conversely, assuming that the reported RF environment information indicates that the LBS client device 110a has less power and/or memory and is in an area where the reference database 122a has much current data, the processor 302 may generate a capture profile instructing the LBS client device 110a to capture or map the device RF environment data in a reduced manner (in reduced manager). The generated capture profile includes information such as the duration of time each relevant wireless transceiver continues to be sampled and the time that the LBS client device 110a should upload the device RF environment report to the LBS server. The processor 302 is used to send the generated capture profile assigned to the LBS client device 110a and to receive a new device RF environment report from the LBS client device 110a including the desired RF environment data. The processor 302 is configured to dynamically capture wireless nodes from new RF environment reports received. The processor 302 is configured to communicate the captured wireless nodes with the assisted-GNSS server 122 at any time so that the captured wireless nodes are accurately located. The processor 302 is configured to use the properly located wireless node to locate a corresponding mobile wireless device, such as the LBS client device 110a, for LBS services.

The location database 304 may comprise suitable logic, circuitry, and/or code that may enable storage of location information for associated communication devices, such as wireless nodes and LBS client devices. The stored location information may be provided to the relevant communication device when it is desired to support LBS services. The location database 304 is used to manage and update the stored location data.

The memory 306 may comprise suitable logic, circuitry, and/or code that may enable storage of information such as executable instructions and data for use by the processor 302 and/or other associated components such as the location database 304. Memory 306 includes RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage.

In an exemplary embodiment of the invention, processor 302 receives a device RF environment report from an associated LBS client device, such as LBS client device 110 a. One or more wireless nodes may be captured from the received device RF environment report. Processor 302 is configured to compare the received device RF environment report to a reference database in the vicinity of the captured wireless node. Generating device capture profiles for the received device RF environment reports based on the reported RF environment information and the status of the reference database 122 a. The generated capture profile includes instructions to transmit the particular RF environment information that LBS client device 110a desires to capture. The generated capture profile is sent to the LBS client device 110 a. In response, the processor 302 is configured to receive a new device RF environment report that includes the desired RF environment data from the LBS client device 110 a. The processor 302 is configured to communicate with the assisted GNSS server 122 to pinpoint wireless nodes captured in the received new RF environment report. The processor 302 is configured to store the precisely located wireless node in the location database 304 to locate a corresponding mobile wireless device, such as the LBS client device 110a, for LBS services

Fig. 4 is a flow chart of an exemplary process for dynamic wireless node acquisition for LBS servers, clients and reference databases, in accordance with an embodiment of the invention. Referring to FIG. 4, exemplary steps begin at step 402. In step 402, LBS client device 200 is used to capture RF environment data through its RF process (expeience) using LBS client software 201. The captured RF environment data is time and location stamped by the LBS client software 201. The LBS client device 200 is used to generate a device RF environment report using the time and location tagged RF environment data. The LBS client device 200 is used to send the generated device RF environment report to the LBS server 300. The LBS server 300 is operable to receive a device RF environment report including the captured wireless nodes at step 404. In step 406, the LBS server 300 is used to compare the received device RF environment report with a reference database of captured wireless node proximities. In step 408, the LBS server 300 is used to generate capture profiles assigned to the LBS client device 200 based on the received device RF environment reports and the status of the reference database 122 a. The generated capture profile is then sent to the LBS client device 200. In step 410, the LBS client device 200 is used to capture RF environment data from the received capture profile. The captured RF environment data is time and location stamped. In step 412, the LBS client device 200 is used to generate and send a new device RF environment report to the LBS server 300 using the captured RF environment data. In step 414, the LBS server 300 is used to communicate with the assisted GNSS server to update the reference database 122a with the received new LBS client report.

The present invention provides a method and system for dynamic wireless node acquisition for a GNSS enabled mobile device, such as LBS client device 110a, with reference to a database by an LBS server client for sending a device RF environment report to the LBS server 120. The LBS client device 110a is used to receive the capture profile from the LBS server 120. The device RF environment report includes a plurality of encountered RF information about the LBS client device 110 a. For example, encountered RF information includes status information including one or more wireless transceivers (radios), status information of power and/or storage resources of the LBS client device 110a, and/or location changes. The received acquisition profile includes information specifying the desired RF environment report that the LBS server 120 desires to receive from the LBS client device. The LBS server 120 determines the acquisition profile assigned to the LBS client device 110a from the RF environment reports received from the LBS client device 110a and the reference database 122a of the assisted GNSS server 122. The LBS client device 110a is used to capture the desired RF environment data from the received acquisition profile. The acquired desired RF environment data is time and location stamped by the LBS client software 201 a. The LBS client device 110a is used to generate a new device RF environment report using the time and location tagged RF environment data. The generated new device RF environment report is sent to the LBS server 120. The LBS server 120 is operable to communicate with the assisted GNSS server 122 to update the reference database 122a in accordance with the new device RF environment report received. The LBS server 120 may use the updated reference database to locate relevant mobile devices such as the LBS client device 110, if desired.

Another embodiment of the present invention provides a machine and/or computer readable storage and/or medium, having stored thereon a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, enabling the machine and/or computer to implement the method and system for dynamic wireless node acquisition for LBS server client reference database described herein.

In general, the invention can be implemented in hardware, software, firmware, or a combination thereof. The present invention can be realized in an integrated manner in at least one computer system or in a separate manner by placing different components in a plurality of interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware, software, and firmware may be a specialized computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

The present invention can also be implemented by a computer program product, which comprises all the features enabling the implementation of the methods of the invention and which, when loaded in a computer system, is able to carry out these methods. The computer program in the present document refers to: any expression, in any programming language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a) conversion to another language, code or notation; b) reproduced in different formats to implement specific functions.

While the invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the spirit and scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.

Claims

1. A method of communication, the method comprising:

performing, by one or more processors and/or circuits in a global navigation satellite system enabled mobile device, the steps of:

sending a device radio frequency environment report to a location server, wherein the device radio frequency environment report comprises the state of the power and/or storage resources of the global navigation satellite system-enabled mobile device and the change of the location;

receiving acquisition profile (profile) from the location server, wherein the location server determines the acquisition profile of the global navigation satellite system enabled mobile device based on the device radio frequency environment report and a reference database, the acquisition profile comprising a command regarding radio frequency environment data acquisition of an area in which the global navigation satellite system enabled mobile device is located, the command being based on the state of the power and/or storage resources and whether the reference database is sufficiently set in the area in which the global navigation satellite system enabled mobile device is located; and

and generating a new equipment radio frequency environment report according to the received captured data.

2. The method of claim 1, further comprising capturing radio frequency environment data from the received acquisition profile; time and location tagging the captured radio frequency environment data; and generating the new device radio frequency environment report using the time and location tagged radio frequency environment data, the new device radio frequency environment report indicating wireless nodes detected by the global navigation satellite system enabled mobile device.

3. A communication system, comprising:

one or more processors and/or circuitry in a global navigation satellite system enabled mobile device, wherein the one or more processors and/or circuitry are to:

sending a device radio frequency environment report to a location server, wherein the device radio frequency environment report comprises the state of the power and/or storage resources of the global navigation satellite system-capable mobile device and the location change;

receiving an acquisition profile (profile) from the location server, wherein the location server is configured to determine the acquisition profile of the global navigation satellite system enabled mobile device based on the device radio frequency environment report and a reference database, the acquisition profile comprising a command regarding radio frequency environment data acquisition of an area in which the global navigation satellite system enabled mobile device is located, the command being based on the power and/or state of storage resources and whether the reference database is sufficiently set in the area in which the global navigation satellite system enabled mobile device is located; and

4. The system according to claim 3, wherein said one or more processors and/or circuits are operable to capture radio frequency environment data from said received capture profile; time and location tagging the captured radio frequency environment data; and generating the new device radio frequency environment report using the time and location tagged radio frequency environment data, the new device radio frequency environment report indicating that the captured radio frequency environment data includes wireless nodes detected by the global navigation satellite system enabled mobile device.