There is an increased trend for wireless devices to employ location-based services that determine the location of a user in order to provide the user with information and services associated with their location. Often, the location-based service relies on a geographical location of the wireless device which may be obtained automatically through a satellite-based receiver in the wireless device or inferred from a location tracking application. In some instances, the user loses the ability to guard the privacy of their location when utilizing a wireless device configured with services that may determine and track their location automatically.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
A user of a wireless device controls the distribution of a location associated with the user's wireless device in order to guard the privacy of the user's location. The user of the wireless device shares its location through a location sharing mechanism. The user awaits requests from other wireless devices for the user's location and, at the user's discretion, the request may be granted or denied through an electronic consent. The on demand nature of the request assures that the user has control over the distribution of the location rather than having the location broadcasted automatically to other wireless devices without the user's knowledge or control.
In addition, once a requesting user of a wireless device obtains the location of another user of a wireless device, the requesting user may use the location to search for and select meeting places in the vicinity of the known location. The requesting user may then transmit these meeting places to the other user for their consideration.
These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory only and are not restrictive of aspects as claimed.
Generally, embodiments of an on demand location sharing technology and technique that enables a user to privately share the location of their wireless device is described herein. A location is the geographical position on earth of a wireless device. The location of a wireless device is based on a known coordinate system (e.g., WGS84) that is used in a particular positioning system. Examples of such positioning systems may include the global positioning system (GPS) and the global system for mobile communications (GSM). For example, the location of a wireless device having a satellite receiver (e.g., GPS receiver) may be determined from the satellite receiver and expressed in terms of longitude, latitude, and altitude, or in similar terms. Alternatively, a wireless device not having a satellite receiver may determine its location using radio signal transmissions from the client device to a neighboring cell tower or access point. Other techniques for determining the location of a wireless device may be employed as well.
The on demand location sharing technique transmits a location request message, from user A, to request the location of user B. User A and user B are both users of a wireless device. User B may share its location by communicating an affirmative location response message or deny the request by communicating a NO THANKS message. Once User A obtains an affirmative location response message, User A may search for meeting places within the vicinity of User B's location. User A may transmit selected meeting places through a share a place message that is transmitted to User B. User B may view the meeting places and a means may be provided for User B to obtain directions to a meeting place of interest. Additionally, either user may manually elect to transmit their location at a particular point in time to another user through a share my location message.
In an embodiment, the on demand location sharing technique includes a location sharing procedure. The location sharing procedure facilitates the messaging between users to retrieve the location of a client device. In addition, the location sharing procedure facilitates searching for meeting places in the vicinity of a desired location. In an embodiment, the search for meeting places may be facilitated using a search engine located on a web server accessed through a networked communication framework.
In one or more embodiments, the location sharing procedure may be part of a messaging client application, such as an instant messaging application, a short message service (SMS), or the like. In one or more embodiments, the location sharing procedure may utilize other procedures, such as a mapping procedure to generate maps of a location, and a user interface procedure that generates graphical user interfaces containing windows, icons, menus, and related text to obtain user input or to display information.
Attention now turns to a more detailed description of the on demand location sharing technology.
The client devices 102 are in communication with the server device 104 through a communication framework that may include various types of communications media as shown by the arrows which may involve the uni-directional or bi-directional exchange of information.
The server device 104 may contain a messenger service 106 that facilitates the transmission of communications between the client devices 102. The messenger service 106 may be an instant messaging service, such as without limitation, the Windows Live® Messenger, that provides the transport mechanism for transmitting messages between the client devices 102. In addition, the server device 104 may contain other computing components, such as processor 108, a memory 110, and a communication interface 112.
The client device 102 may contain a location share procedure 116 that facilities the on demand location sharing. The client device 102 may also contain a mapping procedure 120, a user interface procedure 122, and a messenger client application 126. The mapping procedure 120 facilitates the display of a map or other visual representations illustrating a desired location on the client device 102. The user interface procedure 122 facilitates retrieving input from the user of the client device 102 and displaying graphical menus, windows, and icons to the user of a client device 102. The messenger client application 126 may be used to facilitate the transmission of communication messages between the client devices 102. In an embodiment, the messenger client application 126 interacts with the messaging service 106 to transmit the communication messages to other client devices 102 coupled to the server device 104.
The location share procedure 116, the mapping procedure 120, and the user interface procedure 122 may be embodied in software, as programs, procedures, or modules, in hardware, or a combination thereof. In addition, the client device 102 may contain other computing components, such as a processor 124, a memory 128, and a communications interface 132. A more detailed description of the components of the system 100 is described below with respect to
Although the system 100 shown in
The various components of system 100 may be communicatively coupled via various types of communications medium as indicated by various lines or arrows. The components may coordinate operations between each other. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications medium. The information may be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.
Katie's client device receives the location request message which may be displayed 164 along with several menu options for a response back to Joe. Katie may select the YES option 166 which engages the location share procedure 116 to prepare and transmit an affirmative location response message containing Katie's location which is considered Katie's electronic consent. Alternatively, Katie may select the NO THANKS option 168 which may engage the location share procedure 116 to prepare and transmit a NO THANKS response message.
In the exemplary illustration in
Upon Joe's activation of the SHARE option 204, Katie's client device 154 may receive a listing of one or more suggested meeting places 208 along with a DIRECTIONS option 210. Upon Katie's activation of the DIRECTIONS option 210, the location share procedure 116 on Katie's client device 154 may display a map illustrating the location of the selected meeting place along with directions from Katie's location 212.
Although the communication exchanges shown in
Attention now turns to a more detailed description of the technology and techniques employed in the communication exchanges shown above.
Upon activation of the location share procedure 116, a user interface 156, such as a menu may be displayed, as shown in
Otherwise (step 226—No), if the location share procedure 116 receives a location request message (step 228—Yes), the location share procedure 116 follows the process flow shown in
It should be noted that the process flow illustrated in any one of
Referring now to
The messenger server 322 and the web server(s) 325 may be embodied in a hardware device or a software module, or as a combination thereof. Examples of such hardware devices may include, but are not limited to, a computer (e.g., server, personal computer, laptop, etc.), a cell phone, a personal digital assistant, or any type of computing device, and the like having the capability of communicating with a communication medium. The messenger server 322 and the web server(s) 325 may also be embodied as a software module having instructions that communicate through a communication medium. The server device 104 may be implemented as a messenger server 322 capable of facilitating any type of messaging service, such as electronic mail, instant messaging, or short message service messages, text messages, and the like.
The communications framework 318 facilitates communications between the devices and servers connected therewith. The communications framework 318 may be embodied utilizing any combination of communication mediums and networking structures, such as wired or wireless networks, utilizing any type of communication protocols. In an embodiment, the communications framework 318 may include a wireless carrier network 324, a gateway 326, and a network 328. The wireless carrier network 324 facilitates wireless communication between the wireless devices 316. The wireless carrier network 324 may be coupled to a gateway 326 which in turn is coupled to one or more networks 328. The gateway 326 facilitates communication between different networks. The network 328 facilitates communication between the computing devices 320 in communication therewith and the wireless devices 316. One or more networks 328 may be coupled to the gateway 326 using any type of communication medium or combination thereof, such as wired or wireless communication mediums. The messenger server 322 and the web server 325 may be coupled to a network 328 through any type of communication medium or combination thereof, such as wired or wireless communication mediums.
It should be appreciated that the computing environment shown in
The memory 340 may be a computer readable medium or storage medium that may store executable procedures, applications, and data. It may be any type of memory device (e.g., random access memory, read-only memory, etc.), magnetic storage, volatile storage, non-volatile storage, floppy, disk, drive, tape, optical storage, DVD, CD, and the like. The memory 340 may also include one or more external storage devices or remotely located storage devices. The memory 340 may contain instructions and data as follows:
Likewise, the wireless device shown in
Some embodiments may comprise an article of manufacture. An article of manufacture may comprise a storage medium to store logic. Examples of a storage medium may include one or more types of computer-readable storage media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or re-writeable memory, and so forth. Examples of the logic may include various software elements, such as software components, programs, procedure, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. In one embodiment, for example, an article of manufacture may store executable computer program instructions, that when executed by a computer, cause the computer to perform methods and/or operations in accordance with the described embodiments. The executable program instructions may include any suitable type of code, such as source code, complied code, interpreted code, executable code, static code, dynamic code, and the like. The executable program instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a computer to perform a certain function. The instructions may be implemented in any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Number | Name | Date | Kind |
---|---|---|---|
6405123 | Rennard et al. | Jun 2002 | B1 |
6615131 | Rennard et al. | Sep 2003 | B1 |
7139820 | O'Toole et al. | Nov 2006 | B1 |
7203502 | Wilson et al. | Apr 2007 | B2 |
7451186 | Morinigo et al. | Nov 2008 | B2 |
7532899 | Wilson et al. | May 2009 | B2 |
7707256 | Rollin et al. | Apr 2010 | B2 |
8577990 | Ge | Nov 2013 | B2 |
8769149 | Sidi et al. | Jul 2014 | B2 |
8909248 | Phillips et al. | Dec 2014 | B2 |
9002957 | Turner et al. | Apr 2015 | B2 |
20020077080 | Greene | Jun 2002 | A1 |
20020102989 | Calvert et al. | Aug 2002 | A1 |
20020169650 | Dougherty et al. | Nov 2002 | A1 |
20040039579 | Chithambaram et al. | Feb 2004 | A1 |
20040192299 | Wilson et al. | Sep 2004 | A1 |
20040203603 | Pierce et al. | Oct 2004 | A1 |
20040203901 | Wilson et al. | Oct 2004 | A1 |
20050124293 | Alicherry et al. | Jun 2005 | A1 |
20060099970 | Morgan et al. | May 2006 | A1 |
20060123008 | Stillion et al. | Jun 2006 | A1 |
20060227047 | Rosenberg | Oct 2006 | A1 |
20070087731 | Karlsson et al. | Apr 2007 | A1 |
20070202844 | Wilson et al. | Aug 2007 | A1 |
20080139218 | Duan | Jun 2008 | A1 |
20080268870 | Houri | Oct 2008 | A1 |
20080287112 | Mullen | Nov 2008 | A1 |
20090047972 | Neeraj | Feb 2009 | A1 |
20090049154 | Ge | Feb 2009 | A1 |
20090100037 | Scheibe | Apr 2009 | A1 |
20090170525 | Baghdasaryan | Jul 2009 | A1 |
20090286513 | Wilson et al. | Nov 2009 | A1 |
20090292782 | Kim et al. | Nov 2009 | A1 |
20090319616 | Lewis et al. | Dec 2009 | A1 |
20100279713 | Dicke | Nov 2010 | A1 |
20100323716 | Jaffri | Dec 2010 | A1 |
20110070865 | Nelson et al. | Mar 2011 | A1 |
20110111726 | Kholaif et al. | May 2011 | A1 |
20110143774 | McNamara et al. | Jun 2011 | A1 |
20110170693 | Thomson et al. | Jul 2011 | A1 |
Number | Date | Country |
---|---|---|
2010009328 | Jan 2010 | WO |
Entry |
---|
Perez, Sarah, “Glympse: Real-Time, Private Location-Tracking May be the Winning Formula”,Retrieved at<<http://www.readwriteweb.com/archives/glympse—real-time—private—location-tracking—comes—to—facebook—twitter.php>>, Apr. 16, 2010, pp. 3. |
Sacramento, et al., “A Privacy Service for Location-Based Collaboration among Mobile Users”, Retrieved at <<http://www.scielo.br/pdf/jbcos/v14n4/a05v14n4.pdf>>, Dec. 29, 2009, pp. 17. |
Muthukrishnan, et al., “WLAN Location Sharing through a Privacy Observant Architecture”, Retrieved at <<http://doc.utwente.nl/59910/1/Muthukrishnan06wlan.pdf>>, 2006, pp. 10. |
Hendrix, Phil, “Location: The Epicenter of Mobile Innovation in 2010”, Retrieved at <<http://pro.gigsom.com/2010/02/location-the-epicenter-of-mobile-innovation/>>, Feb. 2010, pp. 60. |
“Google Latitude”. Retrieved at <<http://www.google.com/mobile/latitude/>>, 2011, pp. 2. |
“Foursquare”, Retrieved at <<http://www.foursquare.com/>>, 2011, pp. 1. |
“Facebook Places”, Retrieved at <<http://www.facebook.com/places/>>, 2011, pp. 1. |
“Gowalla”, Retrieved at <<http://www.gowalla.com/>>, 2011, pp. 1. |
“Loopt”, Retrieved at <<http://www.loopt.com/>>, 2011, pp. 1. |
“Where”, Retrieved at <<http://where.com/locations/ttngj4e7/places/>>, 2011, pp. 1. |
“Shopkick”, Retrieved at <<http://www.shopkick.com/>>, 2011, pp. 1. |
“Brightkite”, Retrieved at <<http://www.brightkite.com/>>, 2011, pp. 1. |
Number | Date | Country | |
---|---|---|---|
20120265823 A1 | Oct 2012 | US |