US9020522B2

Method and system for optimizing uploading of location data for location based services

Summary by NHIP

Opportunistic Transport Selection

The mobile device identifies a second transport to upload cached location data based on determined resources. This selection occurs when data usage associated with the second transport meets specific criteria compared to the first transport.

Claim Score by NHIP

Read claim 11, the broadest

Abstract

A mobile device may be operable to collect location data for a RF node and cache the collected location data in the mobile device. Resources that may be utilized for improving the uploading of the cached location data to a location server may be determined by the mobile device. The cached location data may be communicated, to the location server for updating a location database, by the mobile device utilizing the determined resources. The mobile device may determine and utilize an opportunistic transport based on a data usage and/or an access. The mobile device may store a subset of the location database locally for comparing with the cached location data for redundancy. The compared location data may be transmitted by the mobile device to the location server for updating the location database if the compared location data are not redundant data.

US9020522B2, drawing sheet 1 — Sheet 1 of 6

Term

5.8 yearsleft in the term

Expires 5 July 2032, including 832 days of term adjustment.

20 claims: 2 independent, 18 dependent

1
A method for communication in a mobile device, the method comprising:identifying, by said mobile device, a first transport to upload collected location data to a location server;caching, by said mobile device, said collected location data corresponding to a node of a communication network in said mobile device;identifying, by said mobile device, a plurality of resources for uploading said cached collected location data to said location server;identifying, by said mobile device, a second transport to upload said cached collected location data to said location server based upon a resource from among said identified plurality of resources, said second transport being characterized as improving uploading of said cached collected location data to said location server as compared to uploading said cached collected location data using said first transport;and communicating, by said mobile device, said cached collected location data to said location server utilizing said second transport.
11
Broadest claimClaim Score 57, broad(NHIP)A system for communication, comprising:one or more processors or circuits for use in a mobile device, said one or more processors or circuits being configured to: identify a first transport to upload collected location data to a location server;cache said collected location data corresponding to a node of a communication network in said mobile device;identify a plurality of resources for uploading said cached collected location data to said location server;identify a second transport to unload said cached collected location data to said location server based upon a resource from among said identified plurality resources, said second transport being characterized as improving uploading of said cached collected location data to said location server as compared to uploading said cached collected location data using said first transport;and communicate said cached collected location data to said location server utilizing said second transport.

Independent claims2

47 paragraphs in 6 sections, as filed

0001This patent application makes reference to, claims priority to, and claims benefit from U.S. Provisional Application Ser. No. 61/304,101, which was filed on Feb. 12, 2010.

0002The above stated application is hereby incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

0003Certain embodiments of the invention relate to communication systems. More specifically, certain embodiments of the invention relate to a method and system for optimizing uploading of location data for location based services.

BACKGROUND OF THE INVENTION

0004Location-based services (LBS) are emerging as a new type of value-added service provided by mobile communication network. LBS are mobile services in which the user location information is used in order to enable various LBS applications such as, for example, enhanced 911 (E-911), location-based 411, location-based messaging and/or location-based friend finding services. A location of a mobile device may be determined in different ways such as, for example, using network-based technology, using terminal-based technology, and/or hybrid technology, which is a combination of the former technologies. Many positioning technologies such as, for example, time of arrival (TOA), observed time difference of arrival (OTDOA), enhanced observed time difference (E-OTD) as well as the global navigation satellite system (GNSS) such as GPS, GLONASS, Galileo, Compass, and/or assisted-GNSS (A-GNSS), may be utilized to estimate the location (latitude and longitude) of the mobile device and convert it into a meaningful X, Y coordinate for LBS applications. A-GNSS technology combines satellite positioning and communication networks such as mobile networks to reach performance levels allowing the wide deployment of Location-Based Services.

0005Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with the present invention as set forth in the remainder of the present application with reference to the drawings.

BRIEF SUMMARY OF THE INVENTION

0006A system and/or method for optimizing uploading of location data for location based services, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.

0007Various advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an exemplary communication system that is operable to optimize uploading of location data for location based services, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating an exemplary mobile device that is operable to optimize uploading of location data for location based services, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram illustrating an exemplary location server that is operable to optimize uploading of location data for location based services, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 4</figref> is a flow chart illustrating exemplary steps for optimizing uploading of location data for location based services, in accordance with an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

0012Certain embodiments of the invention can be found in a method and system for optimizing uploading of location data for location based services. In various embodiments of the invention, a mobile device may be operable to collect location data for a RF node and cache the collected location data locally in the mobile device for deferred uploading. Resources that may be utilized for improving the uploading of the cached location data to a location server may be determined by the mobile device. The cached location data may be communicated to the location server by the mobile device utilizing the determined resources. The location server may comprise a location database which may then be updated utilizing the location data received from the mobile device. In this regard, the mobile device may be operable to determine an opportunistic transport based on a data usage and/or an access. The cached location data may be communicated to the location server by the mobile device utilizing the determined opportunistic transport. In this regard, for example, in instances when the data usage associated with the opportunistic transport is less than a particular cellular data usage, the opportunistic transport may be selected by the mobile device for communicating the cached location data to the location server. In instances when the access to the opportunistic transport by the mobile device becomes available, the opportunistic transport may be selected by the mobile device for communicating the cached location data to the location server.

0013A subset of the location database may be stored locally in the mobile device. The mobile device may be operable to acquire the stored subset of the location database from the location server, for example. The cached location data may be compared with the subset of the location database stored in the mobile device for redundancy check. The compared location data may be communicated by the mobile device to the location server based on a result of the comparison. In this regard, for example, in instances when the comparison result indicates that the location data are not redundant data, the location data may be transmitted by the mobile device to the location server for updating the location database. In instances when the result of the comparison indicates that the location data are redundant data, the location data may not be transmitted to the location server. The mobile device may be operable to acquire the subset of the location database based on, for example, a capacity of a memory in the mobile device and/or access capability of the mobile device.

0014<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an exemplary communication system that is operable to optimize uploading of location data for location based services, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 1</figref>, there is shown a communication system 100. The communication system 100 comprises a plurality of mobile devices 110, of which mobile devices 110a-110c are illustrated, a location server 120 comprising a location database 122, a communication network 130, a LBS server 140, a GNSS reference network 150 and a GNSS infrastructure 160. The communication network 130 may comprise a plurality of RF nodes, of which RF nodes 170a-170c are illustrated. The GNSS infrastructure 160 may comprise a plurality of GNSS satellites, of which GNSS satellites 160a-160c are illustrated.

0015Each of the mobile devices 110a-110c such as the mobile device 110a may comprise suitable logic, circuitry, interfaces and/or code that may be operable to communicate radio signals across the communication network 130, for example, via the RF nodes 170a-170c. The mobile device 110a may be operable to receive GNSS broadcast signals from a plurality of visible GNSS satellites such as GNSS satellites 160a-160c in the GNSS infrastructure 160. The mobile device 110a may collect and report device-assisted location data, for example, for a RF node such as the RF node 170a to the location server 120 for updating the location database 122.

0016Instead of uploading collected location data continuously, the mobile device 110a may be operable to cache the collected location data for the RF node such as the RF node 170a locally in the mobile device 110a for deferred uploading. Resources that may be utilized for improving the uploading of the cached location data may be determined by the mobile device 110a. The cached location data may be communicated to a location server such as the location server 120 by the mobile device 110a utilizing the determined resources. In this regard, for example, the mobile device 110a may be operable to determine an opportunistic transport based on a data usage and/or an access. An opportunistic transport may be an alternative transport which may be accessed and utilized by the mobile device 110a to communicate the cached location data to the location server 120. For example, the opportunistic transport may be a WiFi access point at high speed with flat low rate or free of charge while current cellular data usage charge for the mobile device 110a to upload the location data may be high, for example, due to roaming. The cached location data may be communicated to the location server 120 by the mobile device 110a utilizing the determined opportunistic transport. In this regard, for example, in instances when the data usage associated with the opportunistic transport is less than a particular cellular data usage, the opportunistic transport may be selected by the mobile device 110a for communicating the cached location data to the location server 120 so that the data usage may be reduced. In instances when the access to the opportunistic transport by the mobile device 110a becomes available, the opportunistic transport may be selected by the mobile device 110a for communicating the cached location data to the location server 120. In this regard, for example, while the mobile device 110a is on a 2G wireless network, the mobile device 110a may not upload the cached location data unless the mobile device 110a can access the WiFi access point or a 3G wireless network.

0017A subset of the location database may be stored locally in a memory in the mobile device 110a. The mobile device 110a may be operable, for example, to acquire the stored subset of the location database from the location server 120. For example, the acquired subset of the location database may comprise the location data for the RF nodes 170a and 170b which are within a region of the mobile device 110a. The cached location data may be compared with the subset of the location database stored in the mobile device 110a for redundancy check. The compared location data may be communicated by the mobile device 110a to the location server 120 based on a result of the comparison. In this regard, for example, in instances when the comparison result indicates that the location data such as, for example, the location data for the RF node 170c are not redundant data, the location data for the RF node 170c may be transmitted by the mobile device 110a to the location server 120 for updating the location database 122. In instances when the comparison result indicates that the location data such as, for example, the location data for the RF node 170a are redundant data, the location data for the RF node 170a may not be transmitted to the location server 120. Accordingly, the data usage for uploading the location data may be reduced by communicating or transmitting only non-redundant or new data to the location server 120 for updating the location database 122. The mobile device 110a may be operable to acquire the subset of the location database based on, for example, a capacity of the memory in the mobile device 110a and/or access capability of the mobile device 110a. In this regard, for example, the mobile device 110a may have limited amount of memory for storing the location database. In this instance, only a limited subset of the location database 122 may be acquired from the location server 120 by the mobile device 110a accordingly. The mobile device 110a, for example, may not be enabled to have access to WiFi access points to collect location data for WiFi access points. In this instance, the subset of the location database 122 associated with the WiFi access points may not be acquired from the location server 120 by the mobile device 110a accordingly.

0018The location server 120 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to access the GNSS reference network 150 to collect GNSS satellite data by tracking GNSS constellations through the GNSS reference network 150. The location server 120 may be operable to utilize the collected GNSS satellite data to generate GNSS assistance data (A-GNSS data) comprising, for example, ephemeris data, LTO data, reference positions and/or time information. The location server 120 may be operable to collect and/or retrieve location information or data from associated users such as the RF nodes 170a-170c and/or the mobile devices 110a-110c. For example, the location server 120 may be operable to receive location information of the RF node 170a from the mobile devices 110a-110c. The received location data may be stored in the location database 122 so that it may be shared among associated mobile devices 110a-110c such as the mobile device 110a. The location server 120 may be operable to communicate the stored location data as A-GNSS data to the mobile device 110a, when need.

0019The location server 120 may be operable to send a subset of the location database 122 to the mobile device 110a when acquired by the mobile device 110a. The subset of the location database sent to the mobile device 110a may be used by the mobile device 110a to determine whether the location data collected by the mobile device 110a are redundant data comparing to the subset of the location database. In instances when the location data collected by the mobile device 110a are redundant data, the location data may not be transmitted to the location server 120 for updating the location database 122.

0020The communication network 130 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to provide voice and data services to various mobile devices such as the mobile devices 110a-110c by using wireless and/or wired communication technologies such as, for example, WCDMA, UMTS, HSDPA, CDMA, EV-DO, GSM, GPRS, EDGE, EGPRS, LTE, Bluetooth, WiMAX, WiFi, FM, mobile TV and Ethernet. The communication network 130 may be operable to provide communication among the location server 120, the LBS server 140 and a plurality of served mobile devices such as the mobile devices 110a-110c. The communication network 130 may comprise a plurality of RF nodes such as, for example, the RF nodes 170a-170c. The RF node 170a is a RF network device that may comprise, for example, a cell station, a wireless access point (AP) and/or a FM station.

0021The LBS server 140 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to provide location based services (LBS). The LBS server may be operable to retrieve information such as, for example, local hotel addresses or a map of the vicinity of areas of interest. The LBS server 140 may be operable to communicate the retrieved information with various communication devices such as the mobile device 110a based on an associated position or location.

0022The GNSS reference network 150 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to collect and/or distribute data for GNSS satellites 160a-160c on a continuous basis. The GNSS reference network 150 may comprise a plurality of GNSS reference tracking stations or receivers located around the world to provide A-GNSS coverage all the time in both a home network and/or any visited network. The GNSS reference network 150 may be communicatively coupled to the location server 120. The collected GNSS data or information may be utilized by the location server 120 to enhance LBS performance.

0023Each of the GNSS satellites 160a-160c such as the satellite 160a may comprise suitable logic, circuitry, interfaces and/or code that may be operable to generate and broadcast satellite navigational information. The broadcast satellite navigation information may be collected by the mobile devices 110a-110c, for example. The broadcast satellite navigational information may be collected by the GNSS reference network 150 to be utilized by the location server 120 to enhance LBS performance. The GNSS satellites 160a-160c may comprise, for example, GPS, GLONASS, Galileo and/or Compass satellites.

0024In operation, the mobile device 110a may collect device-assisted location data, for a RF node such as the RF node 170a to the location server 120 for updating the location database 122. The mobile device 110a may be operable to cache the collected location data for the RF node 170a locally in the mobile device 110a for deferred uploading. Resources that may be utilized for improving the uploading of the cached location data to the location server 120 may be determined by the mobile device 110a. The cached location data may be communicated to the location server 120 by the mobile device 110a utilizing the determined resources. In this regard, the mobile device 110a may be operable to determine an opportunistic transport based on a data usage and/or an access. The cached location data may be communicated to the location server 120 by the mobile device 110a utilizing the determined opportunistic transport. In this regard, in instances when the data usage associated with the opportunistic transport is less than a particular cellular data usage, the opportunistic transport may be selected by the mobile device 110a for communicating the cached location data to the location server 120 so that the data usage may be reduced. In instances when the access to the opportunistic transport by the mobile device 110a becomes available, the opportunistic transport may be selected by the mobile device 110a for communicating the cached location data to the location server 120.

0025A subset of the location database may be stored locally in a memory in the mobile device 110a. The mobile device 110a may be operable, for example, to acquire the stored subset of the location database such as the location data for the RF nodes 170a and 170b from the location server 120. The cached location data may be compared with the subset of the location database stored in the mobile device 110a for redundancy check. The compared location data may be communicated by the mobile device 110a to the location server 120 based on a result of the comparison. In instances when the comparison result indicates that the location data such as the location data for the RF node 170c are not redundant data, the location data for the RF node 170c may be transmitted by the mobile device 110a to the location server 120 for updating the location database 122. In instances when the comparison result indicates that the location data such as the location data for the RF node 170a are redundant data, the location data for the RF node 170a may not be transmitted to the location server 120. The mobile device 110a may be operable to acquire the subset of the location database based on a capacity of the memory in the mobile device 110a and/or access capability of the mobile device 110a.

0026The location server 120 may be operable to send a subset of the location database 122 to the mobile device 110a when acquired by the mobile device 110a. The subset of the location database which is sent to the mobile device 110a may be used by the mobile device 110a to determine whether the location data collected by the mobile device 110a are redundant data comparing to the subset of the location database. In instances when the location data collected by the mobile device 110a are redundant data, the location data may not be transmitted to the location server 120 for updating the location database 122. The location server 120 may be operable to update the location database 122 utilizing the location data received from the mobile device 110a.

0027<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating an exemplary mobile device that is operable to optimize uploading of location data for location based services, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 2</figref>, there is shown a mobile device 200. The mobile device 200 may comprise a location module 202, an antenna 204, a host processor 208 and a memory 210.

0028The location module 202 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to collect device-assisted location data and provide or report the collected location data to the location server 120 for updating the location database 122. In an exemplary embodiment of the invention, the location module 202 may be operable to cache the collected location data for a RF node such as the RF node 170a locally in the location module 202 for deferred uploading. Resources that may be utilized for improving the uploading of the cached location data to a location server such as the location server 120 may be determined by the location module 202. The cached location data may be communicated to the location server 120 by the location module 202 utilizing the determined resources. In this regard, the location module 202 may be operable to determine an opportunistic transport based on a data usage and/or an access. The cached location data may be communicated to the location server 120 by the location module 202 utilizing the determined opportunistic transport. In this regard, for example, in instances when the data usage associated with the opportunistic transport is less than a particular cellular data usage, the opportunistic transport may be selected by the location module 202 for communicating the cached location data to the location server 120 so that the data usage may be reduced. In instances when the access to the opportunistic transport by the location module 202 becomes available, the opportunistic transport may be selected by the location module 202 for communicating the cached location data to the location server 120.

0029A subset of the location database may be stored locally in the memory 210. The location module 202 may be operable, for example, to acquire the stored subset of the location database such as, for example, the location data for the RF nodes 170a and 170b from the location server 120. The cached location data may be compared with the subset of the location database stored in the memory 210 for redundancy check. The compared location data may be communicated by the location module 202 to the location server 120 based on a result of the comparison. In this regard, for example, in instances when the comparison result indicates that the location data such as, for example, the location data for the RF node 170c are not redundant data, the location data for the RF node 170c may be transmitted by the location module 202 to the location server 120 for updating the location database 122. In instances when the comparison result indicates that the location data such as, for example, the location data for the RF node 170a are redundant data, the location data for the RF node 170a may not be transmitted to the location server 120. The location module 202 may be operable to acquire the subset of the location database based on, for example, a capacity of the memory 210 and/or access capability of the location module 202.

0030The antenna 204 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to communicate radio signals over the communication network 130 using various wireless access technologies.

0031The host processor 208 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to process signals from the antenna 204 and/or the location module 202. The host processor 208 may manage and/or control operations of the antenna 204 and/or the location module 202. The host processor 208 may be operable to communicate signals with the communication network 130 via the antenna 204. The host processor 208 may also be operable to receive A-GNSS data from the location server 120 over the antenna 204.

0032The memory 210 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store information such as executable instructions, data and/or database that may be utilized by the host processor 208 and the location module 202. The memory 210 may be operable to locally store a subset of the location database. The memory 210 may comprise RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage.

0033In operation, the location module 202 may be operable to collect the location data for the RF node 170a and cache the collected location data locally in the location module 202 for deferred uploading. Resources that may be utilized for improving the uploading of the cached location data to the location server 120 may be determined by the location module 202. The cached location data may be communicated to the location server 120 by the location module 202 for updating the location database 122 utilizing the determined resources. In this regard, the location module 202 may be operable to determine an opportunistic transport based on a data usage and/or an access. The cached location data may be communicated to the location server 120 by the location module 202 utilizing the determined opportunistic transport. In instances when the data usage associated with the opportunistic transport is less than a particular cellular data usage, the opportunistic transport may be selected by the location module 202 for communicating the cached location data to the location server 120 so that the data usage may be reduced. In instances when the access to the opportunistic transport by the location module 202 becomes available, the opportunistic transport may be selected by the location module 202 for communicating the cached location data to the location server 120.

0034A subset of the location database may be stored locally in the memory 210. The location module 202 may be operable, for example, to acquire the stored subset of the location database such as the location data for the RF nodes 170a and 170b from the location server 120. The cached location data may be compared with the subset of the location database stored in the memory 210 for redundancy check. The compared location data may be communicated by the location module 202 to the location server 120 based on a result of the comparison. In instances when the comparison result indicates that the location data such as the location data for the RF node 170c are not redundant data, the location data for the RF node 170c may be transmitted by the location module 202 to the location server 120 for updating the location database 122. In instances when the comparison result indicates that the location data such as the location data for the RF node 170a are redundant data, the location data for the RF node 170a may not be transmitted to the location server 120. The location module 202 may be operable to acquire the subset of the location database based on a capacity of the memory 210 and/or access capability of the location module 202.

0035<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram illustrating an exemplary location server that is operable to optimize uploading of location data for location based services, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 3</figref>, there is shown a location server 300. The location server 300 may comprise a server processor 302, a location database 304 and a server memory 306.

0036The server processor 302 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to manage and/or control operations of the location database 304 and/or the server memory 306. The server processor 302 may be operable to communicate with the GNSS reference network 150 so as to collect GNSS satellite data by tracking GNSS constellations through the GNSS reference network 150. The server processor 302 may utilize the collected GNSS satellite data to build the location database 304, which may be coupled internally or externally to the location server 300. The server processor 302 may be operable to receive location information or data from associated users such as the mobile devices 110a-110c. The received location information or data may be stored in the location database 304 to share among associated users.

0037In an exemplary embodiment of the invention, the server processor 302 may be operable to send a subset of the location database 304 to the mobile device 110a when acquired by the mobile device 110a. The subset of the location database, which is sent to the mobile device 110a, may be used by the mobile device 110a to determine whether the location data for a RF node such as the RF node 170a collected by the mobile device 110a are redundant data by comparing the collected location data to the subset of the location database. In instances when the location data for the RF node 170a collected by the mobile device 110a are redundant data, the collected location data may not be transmitted to the server process 302 for updating the location database 304.

0038The location database 304 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store location information of associated reference devices such as, for example, the RF nodes 170a-170c. The stored location information may be provided to associated communication devices such as the mobile device 110a to support LBS applications such as location-based access control. In an exemplary embodiment of the invention, the location database 304 may be updated utilizing the location data received from the mobile devices 110a-110c. A subset of the location database 304 may be sent by the server processor 302 to the mobile device 110a for comparison.

0039The server memory 306 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store information such as executable instructions and data that may be utilized by the server processor 302 and/or other associated component units such as, for example, the location database 304. The server memory 306 may comprise RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage.

0040In operation, the server processor 302 may be operable to update the location database 304 utilizing location data received from the mobile device 110a. The server processor 302 may send a subset of the location database 304 to the mobile device 110a when acquired by the mobile device 110a. The subset of the location database, which is sent to the mobile device 110a, may be used by the mobile device 110a to determine whether the location data for the RF node 170a collected by the mobile device 110a are redundant data by comparing the collected location data to the subset of the location database. In instances when the location data for the RF node 170a collected by the mobile device 110a are redundant data, the collected location data may not be transmitted to the server process 302 for updating the location database 304.

0041<figref idref="DRAWINGS">FIG. 4</figref> is a flow chart illustrating exemplary steps for optimizing uploading of location data for location based services, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 4</figref>, the exemplary steps start at step 401. In step 402, the location module 202 in the mobile device 200 may be operable to collect location data for a RF node 170a for updating a location database 122 in a location server 120. In step 403, the collected location data is cached in the location module 202 for deferred uploading. In step 404, the location module 202 may be operable to determine resources that may be utilized for improving the uploading of the cached location data to the location server 120. In step 405, the cached location data in the location module 202 may be communicated or transmitted by the location module 202 to the location server 120 for updating the location database 122 utilizing the determined resources. The exemplary steps may proceed to the end step 406.

0042In various embodiments of the invention, a mobile device 200 may be operable to collect location data for a RF node 170a and cache the collected location data locally in a location module 202 in the mobile device 200 for deferred uploading. Resources that may be utilized for improving the uploading of the cached location data to a location server 120 may be determined by the mobile device 110a. The cached location data may be communicated to the location server 120 by the mobile device 110a utilizing the determined resources. The location server 120 may comprise a location database 122 which may then be updated utilizing the location data received from the mobile device 110a. In this regard, the mobile device 110a may be operable to determine an opportunistic transport based on a data usage and/or an access. The cached location data may be communicated to the location server 120 by the mobile device 110a utilizing the determined opportunistic transport. In this regard, for example, in instances when the data usage associated with the opportunistic transport is less than a particular cellular data usage, the opportunistic transport may be selected by the mobile device 110a for communicating the cached location data to the location server 120. In instances when the access to the opportunistic transport by the mobile device 110a becomes available, the opportunistic transport may be selected by the mobile device 110a for communicating the cached location data to the location server 120.

0043A subset of the location database may be stored locally in the memory 210 in the mobile device 200. The mobile device 110a may be operable to acquire the stored subset of the location database from the location server 120, for example. The cached location data may be compared with the subset of the location database stored in the memory 210 for redundancy check. The compared location data may be communicated by the mobile device 110a to the location server 120 based on a result of the comparison. In this regard, for example, in instances when the result of the comparison indicates that the location data are not redundant data, the location data may be transmitted by the mobile device 110a to the location server 120 for updating the location database 122. In instances when the comparison result indicates that the location data are redundant data, the location data may not be transmitted to the location server 120. The mobile device 200 may be operable to acquire the subset of the location database based on, for example, a capacity of the memory 210 in the mobile device 200 and/or access capability of the location module 202 in the mobile device 200.

0044Other embodiments of the invention may provide a non-transitory computer readable medium and/or storage medium, and/or a non-transitory machine readable medium and/or storage 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, thereby causing the machine and/or computer to perform the steps as described herein for optimizing uploading of location data for location based services.

0045Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system or in a distributed fashion where different elements are spread across several 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 and software may be a general-purpose 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.

0046The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any 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) reproduction in a different material form.

0047While the present 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 without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.

Contents6

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US2003004952A1	Cites	United States of America	Search report
US2003032435A1	Cites	United States of America	Search report
US2003202104A1	Cites	United States of America	Search report
US2003225893A1	Cites	United States of America	Applicant
US2004004737A1	Cites	United States of America	Search report
US2005209927A1	Cites	United States of America	Search report
US2008298238A1	Cites	United States of America	Search report
US2009069021A1	Cites	United States of America	Search report
US2009276517A1	Cites	United States of America	Search report
US2010030972A1	Cites	United States of America	Search report
US2010036595A1	Cites	United States of America	Search report
US2010248640A1	Cites	United States of America	Search report
US2011080890A1	Cites	United States of America	Search report
US7092999B2	Cites	United States of America	Search report
US20030004952A1	Cites	United States of America	Search report
US20030032435A1	Cites	United States of America	Search report
US20030202104A1	Cites	United States of America	Search report
US20030225893A1	Cites	United States of America	Applicant
US20040004737A1	Cites	United States of America	Search report
US20050209927A1	Cites	United States of America	Search report
US20080298238A1	Cites	United States of America	Search report
US20090069021A1	Cites	United States of America	Search report
US20090276517A1	Cites	United States of America	Search report
US20100030972A1	Cites	United States of America	Search report
US20100036595A1	Cites	United States of America	Search report
US20100248640A1	Cites	United States of America	Search report
US20110080890A1	Cites	United States of America	Search report

2 members in 1 office; this record represents the family

This recordMember, by publication datePriority claim

Priority claims6

Priority claims
Document	Office	Kind	Date
30410110	United States of America	P	2010-02-12
30410110	United States of America	P	2010-02-12
73287410	United States of America	A	2010-03-26
61304101	–	–	–
US20100304101P	–	–	–
US20100732874	–	–	–

Members2

Family members, oldest first
Document	Office	Kind
US2011201348A1	United States of America	A1	2011-08-18
US9020522B2This record	United States of America	B2	2015-04-28

72 transactions on the USPTO file

Allowed after 2 non-final rejections, 2 final rejections and 1 RCE.

Non-final rejections: 2
Final rejections: 2
RCEs: 1
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2022-10-21	Payment of Maintenance Fee, 8th Year, Large EntityM1552	M1552
2018-10-29	Payment of Maintenance Fee, 4th Year, Large EntityM1551	M1551
2015-07-21	Post Issue Communication - Certificate of CorrectionN423	N423
2015-04-28	Recordation of Patent Grant MailedPGM/	PGM/
2015-04-28	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2015-04-08	Issue Notification MailedAllowedWPIR	WPIR
2015-03-26	Dispatch to FDCD1935	D1935
2015-03-26	Printer Rush- No mailingTCPB	TCPB
2015-03-26	Mail Response to 312 Amendment (PTO-271)MN271	MN271
2015-03-24	Application Is Considered Ready for IssuePILS	PILS
2015-03-24	Response to Amendment under Rule 312N271	N271
2015-03-23	Pubs Case Remand to TCPUBTC	PUBTC
2015-03-20	Amendment after Notice of Allowance (Rule 312)AllowedA.NA	A.NA
2015-03-20	Response to Reasons for AllowanceREAS	REAS
2015-03-20	Issue Fee Payment VerifiedN084	N084
2015-03-20	Issue Fee Payment ReceivedIFEE	IFEE
2014-12-22	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2014-12-19	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2014-12-16	Reasons for AllowanceEX.R	EX.R
2014-11-10	Date Forwarded to ExaminerFWDX	FWDX
2014-11-06	Response after Non-Final ActionA...	A...
2014-08-13	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2014-08-11	Non-Final RejectionNon-final rejectionCTNF	CTNF
2014-05-14	Date Forwarded to ExaminerFWDX	FWDX
2014-05-14	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2014-05-13	Request for Continued Examination (RCE)RCEX	RCEX
2014-05-13	Request for Extension of Time - GrantedXT/G	XT/G
2014-05-13	Workflow - Request for RCE - BeginBRCE	BRCE
2014-04-17	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2014-04-16	Advisory Action (PTOL-303)CTAV	CTAV
2014-04-15	Date Forwarded to ExaminerFWDX	FWDX
2014-04-14	PILOT- Request for After Final Consideration ProgramRAFC	RAFC
2014-04-14	Response after Final ActionA.NE	A.NE
2014-01-14	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2014-01-11	Final RejectionFinal rejectionCTFR	CTFR
2013-11-18	Mail Miscellaneous Communication to ApplicantMM327	MM327
2013-11-12	Miscellaneous Communication to Applicant - No Action CountM327	M327
2013-11-04	Date Forwarded to ExaminerFWDX	FWDX
2013-11-04	Mail Interview Summary - Applicant Initiated - TelephonicMEXAT	MEXAT
2013-11-01	Case Docketed to Examiner in GAUDOCK	DOCK
2013-02-20	Mail Notice of Withdrawn ActionMW/AC	MW/AC
2013-02-04	Withdrawing/Vacating Office Action LetterW/AC	W/AC
2013-02-04	Interview Summary- Applicant InitiatedEXIA	EXIA
2013-02-04	Interview Summary - Applicant Initiated - TelephonicEXAT	EXAT
2012-12-20	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2012-12-17	Final RejectionFinal rejectionCTFR	CTFR
2012-09-25	Date Forwarded to ExaminerFWDX	FWDX
2012-09-18	Response after Non-Final ActionA...	A...
2012-09-18	Request for Extension of Time - GrantedXT/G	XT/G
2012-08-21	Mail Applicant Initiated Interview SummaryMEXIA	MEXIA
2012-08-15	Interview Summary- Applicant InitiatedEXIA	EXIA
2012-05-18	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2012-05-15	Request for first action interviewRFAI	RFAI
2012-05-15	Non-Final RejectionNon-final rejectionCTNF	CTNF
2012-05-09	Case Docketed to Examiner in GAUDOCK	DOCK
2012-05-07	Case Docketed to Examiner in GAUDOCK	DOCK
2012-02-10	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2012-02-07	Correspondence Address ChangeC.AD	C.AD
2011-08-19	Email NotificationEML_NTR	EML_NTR
2011-08-18	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2011-08-16	Case Docketed to Examiner in GAUDOCK	DOCK
2010-09-01	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2010-07-07	Case Docketed to Examiner in GAUDOCK	DOCK
2010-04-28	Application Dispatched from OIPEOIPE	OIPE
2010-04-08	Sent to Classification ContractorPGPC	PGPC
2010-04-08	Filing ReceiptFLRCPT.O	FLRCPT.O
2010-03-29	Cleared by OIPE CSRL194	L194
2010-03-26	Information Disclosure Statement consideredIDSC	IDSC
2010-03-26	Electronic Information Disclosure StatementEIDS.	EIDS.
2010-03-26	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2010-03-26	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2010-03-26	Initial Exam Team nnIEXX	IEXX

13 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2022-10-21	Maintenance fee paymentMAFP	MAFP
2019-03-22	AssignmentAS	AS
2018-10-29	AssignmentAS	AS
2018-10-29	Maintenance fee paymentMAFP	MAFP
2018-10-04	AssignmentAS	AS
2017-02-03	AssignmentAS	AS
2017-02-01	AssignmentAS	AS
2017-02-01	AssignmentAS	AS
2016-02-11	AssignmentAS	AS
2016-02-11	AssignmentAS	AS
2015-08-11	Certificate of correctionCC	CC
2015-04-08	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2010-04-16	AssignmentAS	AS

Method and system for optimizing uploading of location data for location based services

Summary by NHIP

Claim Score by NHIP

Abstract