System and method for permission to access mobile location information

Information

  • Patent Grant
  • 9648454
  • Patent Number
    9,648,454
  • Date Filed
    Monday, July 6, 2015
    9 years ago
  • Date Issued
    Tuesday, May 9, 2017
    7 years ago
Abstract
A location query service is disclosed. The service provides requestors with a location of a device. The service receives a location query from a requestor, retrieves location information associated with the network user, and returns the location information to the requestor. Before returning the location information to the requestor, the service is configured, in some embodiments, to authenticate that the requestor is authorized by the network user to receive the network user's location information. Methods for providing a location query service also are disclosed.
Description
TECHNICAL FIELD

The present invention relates to the field of wireless networks, and in particular, to wireless networks that track the location of wireless network devices.


BACKGROUND

In compliance with regulations promulgated by the Federal Communications Commission (FCC), wireless networks will soon provide services that are able to determine the location of all network users. These federally mandated services, known as enhanced wireless 911 (E911) services, will require wireless telephones to provide 911 call centers, or Public Safety Answering Points (PSAPs), with vital information necessary to locate and identify a caller in an emergency. To comply with E911 standards, wireless network providers will track the location and identity information of all wireless callers, with the purpose of providing such information to emergency personnel when a caller dials 911 from a wireless telephone. The FCC's wireless E911 rules require certain Commercial Mobile Radio Services (CMRS) carriers to begin transmission of enhanced location and identity information in two phases. Phase I requires carriers to transmit a caller's telephone number and general location to a PSAP. Phase II requires carriers to provide more precise location information to the PSAP.


Under the FCC rules, wireless networks and the corresponding wireless handheld devices, such as cellular telephones, will provide both the identity and location of the caller to a 911 dispatcher. To provide a caller's identity, the wireless handheld device will furnish a mobile identification number (MIN), indicating in most instances the telephone number of the device. The wireless network and wireless handheld devices will provide the location of callers using a network-based location system (e.g., triangulation), global positioning systems (GPSs) within the handheld devices, or a combination of the two systems.


Although, in large part, wireless network providers will implement the location tracking systems to comply with the FCC standards, once completed, the providers will have the ability to offer other location-based services supported by the E911 infrastructure. Indeed, beyond the needs of PSAPs in emergency situations, there are many instances in which it is helpful to know the location of a network user. For example, a service dispatcher monitoring the activities of his service technicians may wish to determine the exact locations of his technicians to facilitate efficient scheduling. Although, with conventional mobile telephone networks, the dispatcher could call and ask the technician for his location, the dispatcher may prefer to ascertain the location information without interrupting the technician's activities.


Other location tracking systems provide the ability to determine a person's location without communicating with (or interrupting) the person. However, these solutions require dedicated networks and network devices. For instance, although a global positioning system can provide a person's location without contacting the person, the system requires that the party requesting the location information (referred to herein as the “requestor”) have communication hardware that receives the location information from the person's GPS receiver. For example, in a typical fleet vehicle tracking system, the fleet manager must purchase and maintain a central processor that communicates with the GPS receiver in each vehicle.


SUMMARY

The present invention is a location query service for use with a wireless network that tracks the location of network devices. The service provides requestors with the locations of network users, based on the locations of the users' wireless network devices. The service enables a requestor to obtain a network user's location without requiring communication with the user. In addition, the service relieves a requestor of the burden of purchasing and maintaining dedicated location tracking equipment by taking advantage of existing communication infrastructures, such as global computer networks, Public Switched Telephone Networks (PSTNs), and wireless networks (with their soon-to-be-implemented location systems).


According to an exemplary embodiment of the present invention, the location query service receives a location query from a requestor for a network user, retrieves the location information of the network user, and returns the location information to the requestor. Preferably, the requestor is an authorized requestor and the service authenticates that the requestor is authorized before returning the location information to the requestor. Within the query, the requestor provides an identification of the network user, such as a name, telephone number, Internet address, or electronic mail (email) address. The service of the present invention supports a variety of communication methods through which a requestor can submit a location query, for example, voice calls through the Public Switched Telephone Network (PSTN) to an interactive voice response unit (IVRU), personal computer access through a global computer network, and cellular telephone access through a global computer network.


In processing location queries, an exemplary embodiment of the present invention gives the network user control of who can receive his location information. The network user provides the service with a list of authorized requestors who may receive the user's location information. The service authenticates that a requestor is authorized before forwarding location information.


In an alternative exemplary embodiment of the present invention, the location query service prompts a network user each time an unauthorized requestor asks for location information. An unauthorized requestor is a requestor who is not designated on a network user's list of authorized requestors and who has not been pre-approved to receive the user's location information. With these “off-list” requests, the network user permits or denies access for unauthorized (off-list) requestors on an individual basis, while automatically permitting access by authorized (on-list) requestors.


In an exemplary embodiment, the system of the present invention includes a user wireless network and a location server. The user wireless network is in communication with a plurality of network devices-operated by a plurality of network users. The user wireless network is also in communication with a location system for determining the location of each network device. The location server is in communication with the wireless network and with a plurality of requestors. The location server accommodates a variety of interfaces in communicating with the plurality of requestors. For example, for Internet protocol (IP) communication, the location server communicates with the plurality of requestors through a global computer network, e.g., the Internet. As another example, for voice communication, the location server communicates with the plurality of requestors through a PSTN.


According to an exemplary method of the present invention, the location server receives a location query for a network user from a requestor, retrieves the user's location from the location system, and forwards the location back to the requestor. Preferably, the location server also confirms that the requestor is authorized to receive the user's location. In an alternative exemplary embodiment, if the location system provides the location in a “raw” form, not easily understood by the typical requestor (e.g., x-y position coordinates), the method further includes translating the location from the raw form to a “displayable” form (e.g., a street address, building name, or area name). The system component that executes this translation function is a mapping converter. The mapping converter can be provisioned in several locations within the system, from the requestor's device to the devices of the plurality of requestors.


Accordingly, it is an object of the present invention to provide a requestor with the location of a wireless network user.


Another object of the present invention is to provide a wireless network user with the ability to automatically furnish specified requestors with the location of the network user.


Another object of the present invention is to provide a wireless network user with the ability to approve or deny access to the user's location information by a requestor who has not been pre-approved.


These and other objects of the present invention are described in greater detail in the detailed description of the invention, the appended drawings, and the attached claims.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic diagram of a system architecture that provides the location query service according to an exemplary embodiment of the present invention.



FIG. 2 is a flow chart tracing the steps for providing a location query service according to an exemplary embodiment of the present invention.



FIG. 3 is a schematic diagram of a system architecture that provides the location query service according to an alternative exemplary embodiment, in which a device's location is periodically recorded in a location database 300.



FIG. 4 is a schematic diagram of a system architecture that provides the location query service according to an alternative exemplary embodiment of the present invention, with the mapping converter provisioned in alternative locations.





DETAILED DESCRIPTION

The present invention is a location query service for use with a wireless network that tracks the locations of network users. The location query service provides a requestor with the location of a network user. In providing this service, the present invention contemplates future enhanced digital cellular networks, in which network users will use digital cellular handheld devices to access data from a global computer network, and in which digital cellular network providers will track the location of each network user.


Referring to FIG. 1, the primary components of an exemplary embodiment of the present invention include a location server 100 and a user wireless network 102. User wireless network 102 is in communication with a plurality of network devices 104. Location server 100 is in communication with user wireless network 102 and with a plurality of requestors 106. The plurality of requestors 106 employ any suitable means to communicate with location server 100, but preferably use at least one of a PC requestor 108, a wireless requestor 110, and a wireline requestor 112. For communication between location server 100 and PC requestor 108, the present invention includes a global computer network 114. For communication between location server 100 and wireless requestor 110 (which has IP messaging capabilities), the present invention includes a requestor wireless network 116 and global computer network 114 for IP messaging, and requestor wireless network 116 and a PSTN 118 for voice communication. For communication between location server 100 and wireline requestor 112, the present invention includes PSTN 118.


According to an exemplary embodiment of the present invention, user wireless network 102 is in communication with a location system 120 that provides the locations of the plurality of network devices 104. Location system 120 includes one or both of handheld location systems 122 and a network-based location system 124. Handheld location systems 122 are provisioned in wireless handheld devices 104. Network-based location systems 124 are part of user wireless network 102.


Location system 120 provides the location information, e.g., position coordinates, of a handheld device, which indicates where a network user is located. Location system 120 can be a part of the wireless network or can be contained in the handheld devices. In an exemplary embodiment of the present invention, as shown in FIG. 1, location system 120 is both a part of the wireless network and is also contained in the handheld devices. For example, suitable methods of determining location as a part of the wireless network include Wireless Access Protocol (WAP) location services, Time Difference of Arrival (TDOA) location systems, Angle of Arrival (AOA) location systems, and other systems using triangulation across cell sites or cell sectors. An example of a suitable location system in the handheld devices is a GPS.


If location system 120 provides location information in raw form, a further exemplary embodiment of the present invention includes a mapping converter 126. An example of information in raw form would be GPS coordinates, with which the typical telephone user is unfamiliar. As used herein, “raw” refers to location information in a rudimentary form, such that a typical telephone user would find it difficult to understand. “Displayable” refers to location information easily understood by a typical network user. Although displayable may imply a visual communication, as used herein, the term extends to other forms of communication, such as audio-based communication. Mapping converter 126 includes a cross-referenced database that allows mapping converter 126 to translate raw location information into displayable location information. For example, the database of mapping converter 126 could include an entry associating coordinates “R-S” (raw information) with the description “101 Park Place” (displayable information).


Although shown as a separate component of the system in FIG. 1, mapping converter 126 could be integral to a component described above. One of ordinary skill in the art would understand that the functions and structure of mapping converter 126 could be located in several different places, anywhere from location system 120 to the communication devices of the requestors 106. For example, mapping converter 126 could be located within network-based location system 124. As another example, mapping converter 126 could also be located within location server 100. Regardless of where mapping converter 126 is provisioned, the desired end result is to deliver displayable location information to the plurality of requestors 106.


Location server 100 executes the service logic of the present invention, including receiving location queries from requestors 106, confirming the access levels of requestors 106, obtaining the location information of wireless network devices 104, and returning the location information to requestors 106. Although shown as a separate component in FIG. 1, one of ordinary skill in the art would appreciate that location server 100 could be a part of another system component, such as user wireless network 102, PSTN 118, or global computer network 114.


In a representative embodiment, location server 100 consists of two components. The first component is a locating mechanism (such as location system 120) that determines locations of network devices 104 using various technologies (e.g., GPS, triangulation, radio signal delay, and cell sector) and combinations thereof. The location mechanism can reside in a network device (e.g., GPS) or within user wireless network 102. The location mechanism produces x-y coordinates that are typically transmitted to the second component of location server 100, which could be in the same box or could be connected via an IP network. The second component of location server 100 integrates the coordinate information into various mapping systems and provides an interface to other applications through various protocols, of which IP is the most common.


In an exemplary embodiment of the present invention, location server 100 is in communication with a memory storage 128. Memory storage 128 is a database or other memory storage device that can record relationships between device identifications (e.g., MINs) and network user identifications. In addition, memory storage contains authorized requestor lists for each device identification. Although FIG. 1 shows memory storage 128 as a separate component of the system accessible to location server 100, memory storage 128 could be contained within location server 100.


Wireless handheld devices 104 operate over user wireless network 102. Familiar examples include pagers and cellular telephones. As a minimum, wireless handheld devices 104 provide network users with wireless communication and cooperate with user wireless network 102 to provide the location of the device. This cooperation may simply involve wireless transmissions to user wireless network 102 that enable network-based location system 124 to ascertain the locations of devices 104. Or, in conjunction with network-based location system 124, wireless handheld devices 104 may include handheld location systems 122, such as GPSs integral to the devices. To facilitate the alternative exemplary embodiment in which a network user responds to off-list requests, wireless handheld devices 104 include messaging capabilities that can communicate a request for access, the identification of the unauthorized requestor, and a response by the network user. For example, such messaging capabilities can be audio-based, text-based, or graphical. Preferably, wireless handheld devices 104 are WAP-compatible thin clients having thin browsers adapted to access global computer network 114 and to communicate with, location server 100.


Global computer network 114 provides communication between TCP/IP requestor devices and location server 100. Preferably, global computer network 114 is the Internet. Also, preferably, network 114 provides a user-friendly interface, e.g., a graphical user interface, through which a requestor can submit a location query. With a graphical user interface (GUI), the requestor device, such as PC requestor 108, is provisioned with software that cooperates with the GUI. Global computer network 114 also preferably supports communication with WAP-compatible wireless devices, such as wireless requestor 110. With these WAP-compatible wireless devices, requestor wireless network 116 provides communication between wireless requestor 110 and global computer network 114.


PSTN 118 provides communication between PSTN devices and location server 100. Along with requestor wireless network 116, PSTN 118 also provides communication: between wireless requestors and location server 100. Location server 100 preferably supports a number of different protocols, at least one of which is IP. PSTN 118 preferably includes a Voice XML (Extensible Markup Language) server, which allows PSTN 118 to interface with location server 100 and provides a common markup language for supporting voice browsing applications. The Voice XML server could include, for example, an IVRU allowing a requestor to use a touch-tone pad to navigate the application.


The plurality of requestors 106 communicate with location server 100 using a device compatible with location server 100 or compatible with an interface between the requestors 106 and location server 100. Global computer network 114 and PSTN 118 are examples of these types of interfaces. Compatible devices include personal computers and IP wireless devices for global computer network 114, and standard wireline telephones for PSTN 118.


Together, the above components provide the location query service as outlined in the flowchart of FIG. 2, according to an exemplary embodiment of the present invention. While the system operation described herein and illustrated in the diagram and flowchart contains many specific details, these specific details should not be construed as limitations on the scope of the invention, but rather as examples of exemplary embodiments thereof. As would be apparent to one of ordinary skill in the art, many other variations on the system operation are possible, including differently grouped and ordered method steps. Accordingly, the scope of the invention should be determined not by the embodiments illustrated, but by the appended claims and their equivalents.


As shown in step 200, a requestor submits a location query to location server 100. The query includes at least an identification of the requestor and an identification of the network user about whom the requestor desires location information. Optionally, the query also includes a password, which enables a location query service provider to allow access to the service only by requestors who pay for the service. Alternatively, only the network user pays for the service and gives her authorized requestors a password to gain access to the service.


The requestor submits the query using any number of communications media supported by location server 100 and the requestor's individual communication device. For example, if the requestor uses a personal computer 108 linked to location server 100 through global computer network 114, the requestor could initiate the query using a graphical user interface. As another example, if the requestor uses a text messaging wireless device 110 linked to location server 100 through requestor wireless network 116 and global computer network 114, the requestor could initiate the query using a menu driven interface or a series of key sequence inputs. As another example, if the requestor uses a wireline telephone, the requestor could interact with an IVRU using the requestor's touch-tone keys to initiate the query.


In an exemplary embodiment, the present invention accommodates the variety of ways in which a requestor can identify the network user that the requestor wishes to locate. For example, the requestor can give a telephone number, name, Internet address, or email address of the network user. In response, location server 100, global computer network 114, PSTN 118, or a separate system component consults a database cross referencing this information and translates the given identification into an identification of the network user's wireless device (e.g., the MIN). As described later in this process, location server 100 provides location system 120 with this device identification to search for the location of the device.


Once location server 100 has received the query, in step 202, location server 100 determines whether the requestor is an authorized requestor and whether the network user in question accepts requests from unauthorized off-list requestors to view the network user's location information. Location server 100 determines if the requestor is an authorized requestor by consulting memory storage 128, which contains a list that the network user provides. The list indicates which people (requestors) have access to the network user's location information. Although shown as a separate system component in FIG. 1, memory storage 128 could be a part of location server 100, such that the list is stored in location server 100.


Along with the access list, the network user specifies a user preference dictating whether the network user will entertain requests to release her location information to requestors not on the access list. The user preference is also preferably stored in memory storage 128, but can be stored in any location accessible to location server 100. Location server 100 consults this user preference if the requestor is not on the access list.


If the requestor is unauthorized and the network user does not accept individual requests to release location information, in step 204a, location server 100 returns a message to the requestor reporting that the location query has been denied.


If the requestor is unauthorized, but the network user does entertain requests to release location information, in step 204b, location server 100 asks the network user if the requestor can receive the network user's location information. In asking for approval, location server 100 provides the network user with the identity of the requestor. If the network user chooses not to release her location information to the requestor, in step 204c, location server 100 returns a message to the requestor reporting that the location query has been denied.


If, in step 204b, the network user chooses to release her location information to the requestor, in step 204d, location server 100 proceeds with determining the location information of the wireless device. Likewise, if originally in step 202, location server determines that the requestor is on the access list and is authorized, location server 100 proceeds with determining the location information of the wireless device in step 204d.


In step 204d, location server 100 asks user wireless network 102 for the location information of the network user. In this inquiry, location server 100 includes the identification of the device corresponding to the network user.


In step 206a, user wireless network 102 uses location system 120 to determine the location of the specified network device. User wireless network 102 monitors wireless handheld devices that are powered on. In most instances, a network user simply turns on his wireless handheld device and, if it is a text messaging device, leaves the network interface open, perhaps to a web page. The initial accessing of the web page or the completion of any other wireless transmission (e.g., placing of a wireless telephone call) provides user wireless network 102 with location and identity information. In addition, each time the web page automatically refreshes, or each time the network user enters a browse command, user wireless network 102 receives updated location information. Thus, after location server 100 asks user wireless network 102 for the location of the network user, location system 120 of user wireless network 102 waits for the next transmission by the network device and determines the location information from that transmission. Alternatively, instead of having location server 100 query user wireless network 102 for location information regarding a specific mobile device, location system 120 could be configured to continuously track devices and push location information to location server 100.


As another way to avoid a prolonged wait for the transmission providing the location information, in an alternative exemplary embodiment, as shown in FIG. 3, the present invention periodically records a device's location in a location database 300. Therefore, instead of activating location system 120 only in response to a request from location server 100, location system 120 of user wireless network 102 periodically updates location database 300 and always has location information available when location server 100 makes a request. In such a case, as shown in step 206b, location server 100 checks location database 300 for the location information of the network user. Although maintaining a database that is periodically updated for all network devices requires considerable amounts of data storage, this alternative embodiment provides a more immediate response to the requestor.


In steps 206a or 206b, location system 120 of user wireless network 102 provides the location information in either raw or displayable forms. If location system 120 provides raw location information, such as x-y coordinates, the method of the present invention preferably further includes translating the raw data to a displayable message, easily comprehended by a typical requestor. Mapping converter 126 executes this translation and the method of the present invention varies depending upon where mapping converter 126 is provisioned (as described below and shown in FIG. 4).


In step 208, if location system 120 provides raw location information and mapping converter 126 is provisioned in user wireless network 102, user wireless network 102 translates the raw location information to a displayable form before returning the location information to location server 100. If location system 120 provides the location information in displayable form, or if location system 120 provides the location information in raw form and user wireless network 102 does not have a mapping converter, user wireless network 102 simply forwards the location information.


In step 210, user wireless network 102 returns the location information, whether raw or displayable, to location server 100. In step 212, if the location information is in raw form and location server 100 contains mapping converter 126, location server 100 translates the location information to displayable form. Finally, in step 214, location server 100 returns the location information of the network user back to the requestor.


Specific Examples of Exemplary Embodiments

The benefits of the present invention apply to numerous situations in which a requestor wants to know the location of a network user. The most applicable situations involve network users that require a certain degree of supervision by another (the requestor). Examples of these types of network users include parolees, the elderly, and children. In each case, the present invention provides a location query service by making use of a wireless device that the network user would otherwise already be using for its primary purpose, e.g., a cellular telephone used for personal voice communication.


As another specific example, the present invention could be implemented in the context of an instant messaging service. A user could have an instant messaging service configured to display only the friends of that user who are in the same city as the user. When a friend's name appears on the user's instant messaging screen, the user may want the option to query for the location of the friend to determine, for example, whether the friend is near enough to have lunch and, if so, to select a restaurant that is conveniently located for the friend and the user. Using the present invention to obtain the location information would save the user from having to send a message to the friend asking for the location of the friend. The location query of the present invention could be explicit or implicit, occurring in the background of the instant messaging service, as a result of a configuration option or an action in the application.


The foregoing disclosure of embodiments of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many variations and modifications of the embodiments described herein will be obvious to one of ordinary skill in the art in light of the above disclosure. The scope of the invention is to be defined only by the claims appended hereto, and by their equivalents.

Claims
  • 1. A system storing logic that, when executed by the system, causes the system to perform operations comprising: receiving, a request, the request being for disclosing, to a requestor, location information associated with a mobile device;determining, in response to receiving the request, whether the requestor is authorized to receive the location information associated with the mobile device;in response to determining that the requestor is unauthorized to receive the location information associated with the mobile device, determining whether a user associated with the mobile device accepts requests for disclosing the location information associated with the mobile device to unauthorized requestors;in response to determining that the user associated with the mobile device accepts requests for disclosing the location information associated with the mobile device to unauthorized requestors, determining whether the user of the mobile device will allow the requestor to receive the location information associated with the mobile device; andin response to determining that the user of the mobile device will allow the requestor to receive the location information associated with the mobile device, providing the location information associated with the mobile device for disclosure to the requestor.
  • 2. The system of claim 1, wherein determining whether the user associated with the mobile device accepts requests for disclosing the location information associated with the mobile device to unauthorized requestors is based on a preference associated with the mobile device.
  • 3. The system of claim 1, wherein determining whether the requestor is authorized to receive the location information associated with the mobile device comprises verifying whether the requestor is on an authorized user access list associated with the user of the mobile device.
  • 4. The system of claim 1, wherein the location information associated with the mobile device is provided by a location system that is communicatively coupled to the mobile device.
  • 5. The system of claim 1, wherein the location information associated with the mobile device is provided by a location system that is co-located with the mobile device.
  • 6. The system of claim 1, wherein the location information associated with the mobile device is provided by a location system that is co-located with the system.
  • 7. A method comprising: receiving, by a system, a request to disclose, to a requestor, location information associated with a mobile device;determining, by the system, in response to receiving the request, whether the requestor is authorized to receive the location information associated with the mobile device;in response to determining that the requestor is unauthorized to receive the location information associated with the mobile device, determining whether a user associated with the mobile device accepts requests for disclosing the location information associated with the mobile device to unauthorized requestors;in response to determining that the user associated with the mobile device accepts requests for disclosing the location information associated with the mobile device to unauthorized requestors, determining, by the system, whether the user of the mobile device will allow the requestor to receive the location information associated with the mobile device; andin response to determining that the user of the mobile device will allow the requestor to receive the location information associated with the mobile device, providing, by the system, the location information associated with the mobile device for disclosure to the requestor.
  • 8. The method of claim 7, wherein determining whether the user associated with the mobile device accepts requests for disclosing the location information associated with the mobile device to unauthorized requestors is based on a preference associated the mobile device.
  • 9. The method of claim 7, wherein determining whether the requestor is authorized to receive the location information associated with the mobile device comprises verifying whether the requestor is on an authorized user access list associated with the user of the mobile device.
  • 10. The method of claim 7, wherein providing the location information associated with the mobile device for disclosure to the requestor comprises: retrieving the location information from a location system communicatively coupled to the mobile device; andsending the location information to an application for disclosure to the requestor.
  • 11. The method of claim 10, wherein the mobile device includes the location system.
  • 12. The method of claim 10, wherein the location system is located on a server communicatively coupled to the mobile device.
  • 13. A method comprising: receiving, by a system, a request to disclose, to a requestor, location information associated with a user, wherein the request comprises an identification associated with the user;determining, by the system, based at least in part on the identification associated with the user, a mobile device associated with the user;determining, by the system, in response to receiving the request, whether the requestor is authorized to receive the location information;in response to determining that the requestor is unauthorized to receive the location information, determining, by the system, whether the user associated with the mobile device accepts requests for disclosing the location information to unauthorized requestors;in response to determining that the user associated with the mobile device accepts requests for disclosing the location information to unauthorized requestors, determining, by the system, whether the user associated with the mobile device will allow the requestor to receive the location information; andin response to determining that the user associated with the mobile device will allow the requestor to receive the location information associated with the mobile device, providing, by the system, the location information for disclosure to the requestor.
  • 14. The method of claim 13, wherein determining whether the user associated with the mobile device accepts requests for disclosing the location information associated with the mobile device to unauthorized requestors is based on a preference provided by the user associated with the mobile device.
  • 15. The method of claim 13, wherein determining whether the requestor is authorized to receive the location information comprises verifying whether the requestor is on an authorized user access list associated with the user of the mobile device.
  • 16. The method of claim 13, wherein providing the location information for disclosure to the requestor comprises: retrieving the location information from a location system communicatively coupled to the mobile device; andsending the location information to an application for disclosure to the requestor.
  • 17. The method of claim 16, wherein the mobile device includes the location system.
  • 18. The method of claim 16, wherein the location system is located on a server communicatively coupled to the mobile device.
CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation U.S. application Ser. No. 13/936,251, filed Jul. 8, 2013, now U.S. Pat. No. 9,078,094, which is a continuation of U.S. application Ser. No. 13/289,297, filed Nov. 4, 2011, now U.S. Pat. No. 8,483,724, which is a continuation of Ser. No. 12/909,401, filed Oct. 21, 2010, now U.S. Pat. No. 8,064,930, which is a continuation of U.S. application Ser. No. 12/580,616, filed Oct. 16, 2009, now U.S. Pat. No. 7,844,284, which is a continuation of U.S. application Ser. No. 11/589,688, filed Oct. 30, 2006, now U.S. Pat. No. 7,636,575, which is a continuation of U.S. application Ser. No. 09/739,315, filed Dec. 19, 2000, now U.S. Pat. No. 7,130,630, the entireties of which are herein incorporated by reference.

US Referenced Citations (324)
Number Name Date Kind
4445118 Taylor et al. Apr 1984 A
4757267 Riskin Jul 1988 A
4893335 Fuller et al. Jan 1990 A
5127042 Gillig et al. Jun 1992 A
5128981 Tsukamoto et al. Jul 1992 A
5303393 Noreen et al. Apr 1994 A
5321242 Heath, Jr. Jun 1994 A
5375161 Fuller et al. Dec 1994 A
5440758 Grube et al. Aug 1995 A
5444444 Ross Aug 1995 A
5451757 Heath, Jr. Sep 1995 A
5511111 Serbetcioglu et al. Apr 1996 A
5512908 Herrick Apr 1996 A
5528248 Steiner et al. Jun 1996 A
5544222 Robinson et al. Aug 1996 A
5566235 Hetz Oct 1996 A
5588037 Fuller et al. Dec 1996 A
5588042 Comer Dec 1996 A
5596625 LeBlanc Jan 1997 A
5610970 Fuller et al. Mar 1997 A
5610973 Comer Mar 1997 A
5625364 Herrick et al. Apr 1997 A
5657375 Connolly et al. Aug 1997 A
5663734 Krasner Sep 1997 A
5673299 Fuller et al. Sep 1997 A
5694453 Fuller et al. Dec 1997 A
5696815 Smyk Dec 1997 A
5701301 Weisser, Jr. Dec 1997 A
5712899 Pace, II Jan 1998 A
5713075 Threadgill et al. Jan 1998 A
5720033 Deo Feb 1998 A
5727057 Emery et al. Mar 1998 A
5729537 Billstrom Mar 1998 A
5751760 Fuller et al. May 1998 A
5771283 Chang et al. Jun 1998 A
5790953 Wang et al. Aug 1998 A
5794210 Goldhaber et al. Aug 1998 A
5812763 Teng Sep 1998 A
5819155 Worthy et al. Oct 1998 A
5825283 Camhi Oct 1998 A
5825775 Chin et al. Oct 1998 A
5835907 Newman Nov 1998 A
5838774 Weisser, Jr. Nov 1998 A
5848131 Shaffer et al. Dec 1998 A
5852775 Hidary Dec 1998 A
5875401 Rochkind Feb 1999 A
5889953 Thebaut et al. Mar 1999 A
5903636 Malik May 1999 A
5949865 Fusinato Sep 1999 A
5949867 Sonnenberg Sep 1999 A
5959577 Fan et al. Sep 1999 A
5961593 Gabber et al. Oct 1999 A
5963866 Palamara et al. Oct 1999 A
5968176 Nessett et al. Oct 1999 A
6011975 Emery et al. Jan 2000 A
6021126 White et al. Feb 2000 A
6028921 Malik et al. Feb 2000 A
6047327 Tso et al. Apr 2000 A
6055637 Hudson et al. Apr 2000 A
6060993 Cohen May 2000 A
6076080 Morscheck et al. Jun 2000 A
6085086 La Porta et al. Jul 2000 A
6091956 Hollenberg Jul 2000 A
6101381 Tajima et al. Aug 2000 A
6112186 Bergh et al. Aug 2000 A
6119000 Stephenson et al. Sep 2000 A
6122520 Want et al. Sep 2000 A
6133853 Obradovich et al. Oct 2000 A
6138003 Kingdon et al. Oct 2000 A
6138119 Hall et al. Oct 2000 A
6157829 Grube et al. Dec 2000 A
6182226 Reid et al. Jan 2001 B1
6183003 Matsuhashi et al. Feb 2001 B1
6184829 Stilp Feb 2001 B1
6185426 Alperovich et al. Feb 2001 B1
6208854 Roberts et al. Mar 2001 B1
6208857 Agre et al. Mar 2001 B1
6208866 Rouhollahzadeh et al. Mar 2001 B1
6229477 Chang et al. May 2001 B1
6230188 Marcus May 2001 B1
6233329 Urban et al. May 2001 B1
6243581 Jawanda Jun 2001 B1
6249577 Baldwin Jun 2001 B1
6259405 Stewart et al. Jul 2001 B1
6311069 Havinis et al. Oct 2001 B1
6317718 Fano Nov 2001 B1
6321092 Fitch et al. Nov 2001 B1
6324349 Nakano et al. Nov 2001 B2
6324396 Vasa et al. Nov 2001 B1
6332127 Bandera et al. Dec 2001 B1
6340935 Hall Jan 2002 B1
6353664 Cannon et al. Mar 2002 B1
6369754 Levanon Apr 2002 B1
6374246 Matsuo Apr 2002 B1
6377810 Geiger Apr 2002 B1
6381465 Chern et al. Apr 2002 B1
6385591 Mankoff May 2002 B1
6404876 Smith et al. Jun 2002 B1
6411899 Dussell et al. Jun 2002 B2
6414635 Stewart et al. Jul 2002 B1
6418308 Heinonen et al. Jul 2002 B1
6421411 Hsieh Jul 2002 B1
6421441 Dzuban Jul 2002 B1
6427073 Kortesalmi et al. Jul 2002 B1
6442391 Johansson et al. Aug 2002 B1
6442687 Savage Aug 2002 B1
6449497 Kirbas et al. Sep 2002 B1
6463533 Calamera et al. Oct 2002 B1
6466862 DeKock et al. Oct 2002 B1
6470378 Tracton et al. Oct 2002 B1
6470447 Lambert et al. Oct 2002 B1
6473626 Nevoux et al. Oct 2002 B1
6477382 Mansfield et al. Nov 2002 B1
6484148 Boyd Nov 2002 B1
6491217 Catan Dec 2002 B2
6496931 Rajchel et al. Dec 2002 B1
6505046 Baker Jan 2003 B1
6505048 Moles et al. Jan 2003 B1
6505049 Dorenbosch Jan 2003 B1
6505163 Zhang et al. Jan 2003 B1
6516203 Enzmann et al. Feb 2003 B1
6519530 Crockett et al. Feb 2003 B2
6522876 Weiland et al. Feb 2003 B1
6526275 Calvert Feb 2003 B1
6526506 Lewis Feb 2003 B1
6529159 Fan et al. Mar 2003 B1
6545596 Moon Apr 2003 B1
6546257 Stewart Apr 2003 B1
6559769 Anthony et al. May 2003 B2
6560442 Yost et al. May 2003 B1
6560448 Baldwin et al. May 2003 B1
6560461 Fomukong et al. May 2003 B1
6574548 DeKock et al. Jun 2003 B2
6590885 Jorgensen Jul 2003 B1
6594482 Findikli et al. Jul 2003 B1
6594483 Nykanen et al. Jul 2003 B2
6614781 Elliott et al. Sep 2003 B1
6618474 Reese Sep 2003 B1
6618593 Drutman et al. Sep 2003 B1
6622016 Sladek et al. Sep 2003 B1
6625457 Raith Sep 2003 B1
6628928 Crosby et al. Sep 2003 B1
6628938 Rachabathuni et al. Sep 2003 B1
6640184 Rabe Oct 2003 B1
6647257 Owensby Nov 2003 B2
6647269 Hendrey et al. Nov 2003 B2
6650901 Schuster et al. Nov 2003 B1
6654607 Shobatake et al. Nov 2003 B1
6662014 Walsh Dec 2003 B1
6675017 Zellner et al. Jan 2004 B1
6677894 Sheynblat et al. Jan 2004 B2
6678265 Kung et al. Jan 2004 B1
6701160 Pinder et al. Mar 2004 B1
6711474 Treyz et al. Mar 2004 B1
6716101 Meadows et al. Apr 2004 B1
6725048 Mao et al. Apr 2004 B2
6732101 Cook May 2004 B1
6738808 Zellner May 2004 B1
6748217 Hunzinger et al. Jun 2004 B1
6754482 Torabi Jun 2004 B1
6754504 Reed Jun 2004 B1
6779020 Henrick Aug 2004 B1
6782259 Bamburak et al. Aug 2004 B2
6799049 Zellner et al. Sep 2004 B1
6816720 Hussain et al. Nov 2004 B2
6819929 Antonucci et al. Nov 2004 B2
6826414 Reynolds et al. Nov 2004 B1
6829475 Lee et al. Dec 2004 B1
6834050 Madour et al. Dec 2004 B1
6834341 Bahl et al. Dec 2004 B1
6850758 Paul et al. Feb 2005 B1
6867733 Sandhu et al. Mar 2005 B2
6868074 Hanson Mar 2005 B1
6874011 Spielman et al. Mar 2005 B1
6876858 Duvall et al. Apr 2005 B1
6879584 Thro et al. Apr 2005 B2
6882641 Gallick et al. Apr 2005 B1
6898433 Rajaniemi et al. May 2005 B1
6934558 Sainton et al. Aug 2005 B1
6937869 Rayburn Aug 2005 B1
6940950 Dickinson et al. Sep 2005 B2
6954147 Cromer et al. Oct 2005 B1
6954526 Glenn et al. Oct 2005 B1
6954649 Kotzin Oct 2005 B2
6961583 Moles et al. Nov 2005 B2
6961584 Leedom, Jr. Nov 2005 B2
6963557 Knox Nov 2005 B2
6975874 Bates et al. Dec 2005 B1
6996211 Reynolds et al. Feb 2006 B2
6999779 Hashimoto Feb 2006 B1
7005985 Steeves Feb 2006 B1
7023995 Olsson Apr 2006 B2
7039431 Mukherjee May 2006 B2
7043231 Bhatia et al. May 2006 B2
7051196 Angelo et al. May 2006 B2
7069319 Zellner et al. Jun 2006 B2
7079627 Crago et al. Jul 2006 B2
7085555 Zellner et al. Aug 2006 B2
7085578 Barclay et al. Aug 2006 B2
7093286 King Aug 2006 B1
7103368 Teshima Sep 2006 B2
7103460 Breed Sep 2006 B1
7106843 Gainsboro et al. Sep 2006 B1
7110749 Zellner et al. Sep 2006 B2
7116977 Moton et al. Oct 2006 B1
7123693 Nelson et al. Oct 2006 B2
7124101 Mikurak Oct 2006 B1
7181017 Nagel et al. Feb 2007 B1
7181225 Moton et al. Feb 2007 B1
7181529 Bhatia et al. Feb 2007 B2
7190960 Wilson et al. Mar 2007 B2
7203502 Wilson et al. Apr 2007 B2
7212829 Lau et al. May 2007 B1
7224978 Zellner et al. May 2007 B2
7224987 Bhela et al. May 2007 B1
7236799 Wilson et al. Jun 2007 B2
7245925 Zellner Jul 2007 B2
7260186 Zhu et al. Aug 2007 B2
7260378 Holland et al. Aug 2007 B2
7284232 Bates et al. Oct 2007 B1
7299034 Kates Nov 2007 B2
7305350 Bruecken Dec 2007 B1
7330464 Brouwer et al. Feb 2008 B2
7366522 Thomas Apr 2008 B2
7383052 Moton, Jr. et al. Jun 2008 B2
7412234 Zellner Aug 2008 B2
7418503 Zellner et al. Aug 2008 B2
7428411 Zellner Sep 2008 B2
7433673 Everson et al. Oct 2008 B1
7509133 Zellner et al. Mar 2009 B2
7529359 Gallant et al. May 2009 B2
7552467 Lindsay Jun 2009 B2
7593712 Moton et al. Sep 2009 B2
7603110 Zellner et al. Oct 2009 B2
7606938 Roese et al. Oct 2009 B2
7636575 Enzmann et al. Dec 2009 B2
7664488 Zellner et al. Feb 2010 B2
7664509 Zellner et al. Feb 2010 B2
7668537 De Vries Feb 2010 B2
7680590 Sanqunetti Mar 2010 B2
7685629 White et al. Mar 2010 B1
7796998 Zellner et al. Sep 2010 B1
7873369 Zellner et al. Jan 2011 B2
7894801 Zellner et al. Feb 2011 B2
7941130 Moton et al. May 2011 B2
7966026 Zellner et al. Jun 2011 B2
8010126 Moton et al. Aug 2011 B2
8041817 Zellner et al. Oct 2011 B2
8086224 Zellner et al. Dec 2011 B2
8165568 Zellner et al. Apr 2012 B2
8185130 Zellner et al. May 2012 B2
8494501 Zellner et al. Jul 2013 B2
8755777 Zellner et al. Jun 2014 B2
20010034709 Stoifo et al. Oct 2001 A1
20020035605 McDowell et al. Mar 2002 A1
20020035699 Crosbie Mar 2002 A1
20020037709 Bhatia et al. Mar 2002 A1
20020037722 Hussain et al. Mar 2002 A1
20020037731 Mao et al. Mar 2002 A1
20020037744 Bhatia et al. Mar 2002 A1
20020037750 Hussain et al. Mar 2002 A1
20020038362 Bhatia et al. Mar 2002 A1
20020038386 Bhatia et al. Mar 2002 A1
20020052781 Aufricht et al. May 2002 A1
20020070879 Gazit et al. Jun 2002 A1
20020077083 Zellner et al. Jun 2002 A1
20020077084 Zellner et al. Jun 2002 A1
20020077118 Zellner et al. Jun 2002 A1
20020077897 Zellner et al. Jun 2002 A1
20020077987 Hasegawa et al. Jun 2002 A1
20020090932 Bhatia et al. Jul 2002 A1
20020095312 Wheat Jul 2002 A1
20020102993 Hendrey et al. Aug 2002 A1
20020107027 O'Neil Aug 2002 A1
20020173317 Nykanen et al. Nov 2002 A1
20030046405 O'Neill et al. Mar 2003 A1
20030109245 McCalmont et al. Jun 2003 A1
20030195698 Jones Oct 2003 A1
20030229592 Florance et al. Dec 2003 A1
20040097243 Zellner et al. May 2004 A1
20040203900 Cedervall et al. Oct 2004 A1
20040203903 Wilson et al. Oct 2004 A1
20040205198 Zellner et al. Oct 2004 A1
20050272445 Zellner et al. Dec 2005 A1
20060030335 Zellner et al. Feb 2006 A1
20060030339 Zhovnirovsky et al. Feb 2006 A1
20060089134 Moton et al. Apr 2006 A1
20060094447 Zellner et al. May 2006 A1
20060099966 Moton et al. May 2006 A1
20060105784 Zellner et al. May 2006 A1
20060167986 Trzyna et al. Jul 2006 A1
20060189327 Zellner et al. Aug 2006 A1
20060195570 Zellner et al. Aug 2006 A1
20070010260 Zellner Jan 2007 A1
20070015495 Winter et al. Jan 2007 A1
20070027621 Operowsky et al. Feb 2007 A1
20070042789 Moton et al. Feb 2007 A1
20070047523 Jiang Mar 2007 A1
20070063875 Hoffberg Mar 2007 A1
20070105565 Enzmann et al. May 2007 A1
20070124721 Cowing et al. May 2007 A1
20070136603 Kuecuekyan Jun 2007 A1
20070142060 Moton et al. Jun 2007 A1
20070250920 Lindsay Oct 2007 A1
20080096529 Zellner Apr 2008 A1
20080132252 Altman et al. Jun 2008 A1
20080261571 Zellner et al. Oct 2008 A1
20080261624 Moton et al. Oct 2008 A1
20080299957 Zellner et al. Dec 2008 A1
20090047937 Zellner et al. Feb 2009 A1
20090259588 Lindsay Oct 2009 A1
20090325551 Zellner et al. Dec 2009 A1
20100105417 Zellner et al. Apr 2010 A1
20100131584 Johnson May 2010 A1
20100151815 Zellner et al. Jun 2010 A1
20100296510 Zellner Nov 2010 A1
20110143708 Zellner et al. Jun 2011 A1
20110312341 Moton et al. Dec 2011 A1
20120034930 Zellner et al. Feb 2012 A1
20120123869 Zellner et al. May 2012 A1
20120196572 Zellner et al. Aug 2012 A1
20120264452 Zellner et al. Oct 2012 A1
20120276873 Zellner et al. Nov 2012 A1
20120289251 Moton et al. Nov 2012 A1
Foreign Referenced Citations (13)
Number Date Country
000964542 Dec 1999 EP
0964542 Dec 1999 EP
1194628 Aug 1989 JP
3128540 May 1991 JP
7234789 Sep 1995 JP
7288514 Oct 1995 JP
7319706 Dec 1995 JP
8044568 Feb 1996 JP
8087296 Apr 1996 JP
9819484 May 1998 WO
WO 9819484 May 1998 WO
9927716 Jun 1999 WO
WO 9927716 Jun 1999 WO
Non-Patent Literature Citations (60)
Entry
BellSouth “The Real Yellow Pages”, Greater Atlanta A-L, 2004 BellSouth Advertising & Publishing Corp.
BellSouth “The Real Yellow Pages”, Greater Atlanta M-Z, 2004 BellSouth Advertising & Publishing Corp.
Petronis, Scott, “Mapping Technology: The Common Thread,” Wireless Review, vol. 17, No. 3, pp. 10-14, Feb. 1, 2000, ISSN: 1099-9248.
Microsoft Mobility Developer Conference 2003.
3rd Generation Partnership Project: Technical Specification Group Services and System Aspects; Functional Stage 2 Description of Location Services in UMTS (1999).
“Open Wave Announces Availability to End-to-End Set of Location Services for Wireless Internet,” http://www.openwave.com/us/news—room/press—releases/2001/20010320, 2001.
“Wireless Application Protocol”, WAP Forum, Oct. 1999, Wireless Internet Today, pp. 1-20.
Mark Moeglein, et al., “An Introduction to Snap Track Server-Aided GPS Technology,” available at http://www.snaptrack.com/atwork.html, Sep. 21, 1998, pp. 333-342.
“Signal Soft Wireless Location Services”, available at http://signalsoftcorp.com/products/location—manager.html, Copyright 1999, earliest capture by Wayback Machine Internet Archive on Aug. 29, 1999, no publication date provided.
U.S. Office Action dated Oct. 14, 2014 in U.S. Appl. No. 13/936,251.
U.S. Notice of Allowance dated Feb. 26, 2015 in U.S. Appl. No. 13/936,251.
U.S. Office Action dated Feb. 23, 2012 in U.S. Appl. No. 13/289,297.
U.S. Office Action dated Jun. 13, 2012 in U.S. Appl. No. 13/289,297.
U.S. Office Action dated Nov. 26, 2012 in U.S. Appl. No. 13/289,297.
U.S. Notice of Allowance dated Mar. 14, 2013 in U.S. Appl. No. 13/289,297.
U.S. Office Action dated Mar. 30, 2011 in U.S. Appl. No. 12/909,401.
U.S. Notice of Allowance dated Jul. 15, 2011 in U.S. Appl. No. 12/909,401.
U.S. Office Action dated Mar. 29, 2010 in U.S. Appl. No. 12/580,616.
U.S. Notice of Allowance dated Sep. 16, 2010 in U.S. Appl. No. 12/580,616.
U.S. Office Action dated Sep. 25, 2007 in U.S. Appl. No. 11/589,688.
U.S. Office Action dated Apr. 3, 2008 in U.S. Appl. No. 11/589,688.
U.S. Advisory Action dated Oct. 6, 2008 in U.S. Appl. No. 11/589,688.
U.S. Office Action dated Apr. 29, 2009 in U.S. Appl. No. 11/589,688.
U.S. Office Action dated Oct. 6, 2009 in U.S. Appl. No. 11/589,688.
U.S. Notice of Allowance dated Nov. 5, 2009 in U.S. Appl. No. 11/589,688.
U.S. Office Action dated Jun. 21, 2004 in U.S. Appl. No. 09/739,315.
U.S. Office Action dated Feb. 9, 2005 in U.S. Appl. No. 09/739,315.
U.S. Office Action dated Feb. 3, 2006 in U.S. Appl. No. 09/739,315.
U.S. Notice of Allowance dated Aug. 30, 2006 in U.S. Appl. No. 09/739,315.
U.S. Notice of Allowance dated Sep. 27, 2006 in U.S. Appl. No. 09/739,315.
U.S. Office Action dated Aug. 30, 2005 in U.S. Appl. No. 10/704,775.
U.S. Office Action dated Jan. 9, 2006 in U.S. Appl. No. 10/704,775.
U.S. Office Action dated May 29, 2009 in U.S. Appl. No. 10/704,775.
U.S. Notice of Allowance dated Oct. 16, 2009 in U.S. Appl. No. 10/704,775.
U.S. Office Action dated Jun. 1, 2010 in U.S. Appl. No. 12/648,424.
U.S. Notice of Allowance dated Sep. 21, 2010 in U.S. Appl. No. 12/648,424.
U.S. Office Action dated May 16, 2003 in U.S. Appl. No. 09/740,372.
U.S. Office Action dated Oct. 30, 2003 in U.S. Appl. No. 09/740,372.
U.S. Office Action dated Apr. 15, 2004 in U.S. Appl. No. 09/740,372.
U.S. Office Action dated Nov. 2, 2004 in U.S. Appl. No. 09/740,372.
U.S. Advisory Action dated Feb. 15, 2005 in U.S. Appl. No. 09/740,372.
U.S. Notice of Allowance dated Jun. 24, 2005 in U.S. Appl. No. 09/740,372.
U.S. Office Action dated Dec. 13, 2005 in U.S. Appl. No. 09/740,372.
U.S. Notice of Allowance dated Jan. 27, 2006 in U.S. Appl. No. 09/740,372.
U.S. Notice of Allowance dated May 15, 2006 in U.S. Appl. No. 09/740,372.
U.S. Office Action dated Mar. 10, 2006 in U.S. Appl. No. 11/252,039.
U.S. Office Action dated Feb. 6, 2007 in U.S. Appl. No. 11/252,039.
U.S. Office Action dated Sep. 13, 2007 in U.S. Appl. No. 11/252,039.
U.S. Office Action dated Mar. 18, 2008 in U.S. Appl. No. 11/252,039.
U.S. Notice of Allowance dated Jun. 15, 2009 in U.S. Appl. No. 11/252,039.
U.S. Office Action dated Jul. 27, 2010 in U.S. Appl. No. 12/552,767.
U.S. Notice of Allowance dated Oct. 10, 2010 in U.S. Appl. No. 12/552,767.
U.S. Office Action dated Jul. 11, 2011 in U.S. Appl. No. 13/031,721.
U.S. Notice of Allowance dated Dec. 23, 2011 in U.S. Appl. No. 13/031,721.
U.S. Office Action dated Jul. 3, 2012 in U.S. Appl. No. 13/437,076.
U.S. Notice of Allowance dated Nov. 28, 2012 in U.S. Appl. No. 13/437,076.
U.S. Notice of Allowance dated Mar. 8, 2013 in U.S. Appl. No. 13/437,076.
U.S. Office Action dated Sep. 5, 2013 in U.S. Appl. No. 13/947,150.
U.S. Notice of Allowance dated Dec. 19, 2013 in U.S. Appl. No. 13/947,150.
U.S. Notice of Allowance dated May 13, 2014 in U.S. Appl. No. 13/947,150.
Related Publications (1)
Number Date Country
20150312714 A1 Oct 2015 US
Continuations (6)
Number Date Country
Parent 13936251 Jul 2013 US
Child 14792499 US
Parent 13289297 Nov 2011 US
Child 13936251 US
Parent 12909401 Oct 2010 US
Child 13289297 US
Parent 12580616 Oct 2009 US
Child 12909401 US
Parent 11589688 Oct 2006 US
Child 12580616 US
Parent 09739315 Dec 2000 US
Child 11589688 US