Mobile device alert generation system and method
Summary by NHIP
Pattern-based mobile alert system
The method obtains location data for multiple users to determine a shared location pattern. It detects a specific user's current location and provides an alert when that location matches the determined pattern.
Claim Score by NHIP
Abstract
A computer-implemented method for providing an alert regarding mobile device location is provided. The method includes obtaining location data corresponding to locations of a mobile device over a period of time. A location pattern is determined based on the location data. The current location of the mobile device is detected at a time based on the determined pattern, and an alert is provided regarding the current location of the mobile device. A system for providing alerts regarding mobile device location is also provided.

Term
5 yearsleft in the term
Expires 18 September 2031, including 157 days of term adjustment.
- Priority
- Filed
- Granted
- Today
- Expires
16 claims: 4 independent, 12 dependent
- 1A computer-implemented method for providing an alert regarding mobile device location, the method comprising:obtaining location data corresponding to locations of a plurality of mobile device users over a period of time;obtaining identifying information corresponding to the plurality of mobile device users and a particular mobile device user;comparing the identifying information of the plurality of mobile device users with the identifying information of the particular mobile device user;determining a location pattern of the plurality of mobile device users based on the location data in response to the identifying information of the plurality of mobile device users corresponding to the identifying information of the particular user;detecting a current location of the particular mobile device user;and providing an alert based on the current location of the particular mobile device user and the determined location pattern.
- 12Broadest claimClaim Score 51, average(NHIP)A computer-implemented method for providing an alert regarding mobile device location, the method comprising:obtaining location data corresponding to locations of a plurality of mobile device users over a period of time;obtaining identifying information corresponding to the plurality of mobile device users and a particular mobile device user;comparing the identifying information of the plurality of mobile device users with the identifying information of the particular mobile device user;determining a location pattern of the plurality of mobile device users based on the location data in response to the identifying information of the plurality of mobile device users not corresponding to the identifying information of the particular user;detecting a current location of the particular mobile device user;and providing an alert based on the current location of the particular mobile device user and the determined location pattern.
- 13A computer-implemented method for providing an alert regarding mobile device location, the method comprising:obtaining location data corresponding to locations of a plurality of mobile device users over time;obtaining location data corresponding to locations of a particular mobile device user over time;determining a location pattern of the plurality of mobile device users based on the location data;obtaining an event schedule specifying types of events corresponding to at least one venue;determining event preferences of the plurality of mobile device users and the particular mobile device user by determining types of events attended by the plurality of mobile device users and the types of events attended by the particular mobile device user based on the location data and the event schedule;comparing an event preference of the plurality of mobile device users with an event preference of the particular mobile device user;detecting a current location of the particular mobile device user;and providing an alert based on the current location of the particular mobile device user, the determined location pattern, and the comparison.
- 16A system for providing an alert regarding mobile device location comprising at least one computing device including at least one memory comprising instructions operable to enable the at least one computing device to perform a procedure comprising:obtaining location data corresponding to locations of a plurality of mobile device users over a period of time;obtaining identifying information corresponding to the plurality of mobile device users and a particular mobile device user;comparing the identifying information of the plurality of mobile device users with the identifying information of the particular mobile device user;determining a location pattern of the plurality of mobile device users based on the location data in response to the identifying information of the plurality of mobile device users corresponding to the identifying information of the particular user;detecting a current location of the particular mobile device user;and providing an alert based on the current location of the particular mobile device user and the determined location pattern.
Independent claims4
49 paragraphs in 5 sections, as filed
CROSS REFERENCE TO RELATED APPLICATION(S)
This application claims the benefit of U.S. provisional application No. 61/406,125, filed Oct. 23, 2010, which is incorporated by reference as if fully set forth.
BACKGROUND
Mobile communication devices such as cellular telephones, smart phones and the like are frequently enabled to receive signals from Global Positioning System (GPS) satellites for estimating device location coordinates. Also, many mobile communication devices have the ability to perform network scans to determine radio signal information, including identifiers associated with nearby cellular base transceiver stations, and radio access points such as WiFi™ and Bluetooth™ access points. Further, mobile communication devices are frequently enabled to perform signal strength estimates and other signal measurements of incoming signals. Cellular base transceiver stations and radio access points are primarily used for providing voice and data service to a mobile device, but due to their relative permanence can also be used for determining device location.
A number of techniques exist to translate terrestrial signal information into location, including cell triangulation and trilateration techniques, such as Time Difference of Arrival (“TDOA”), Enhanced Observed Time Difference (“EOTD”), Advanced Forward Link Trilateration (“AFLT”) and Enhanced Cell Identification (“E-CID”). Such methods are considered terrestrial counterparts to the GPS satellite-based system which uses a form of triangulation based on satellite positioning. A mobile device may be configured for determining its own location, or in some cases, a remote system in communication with a mobile device via a network can be configured to determine a mobile device's location using translation techniques such as those described above.
It would be desirable to leverage known location determining processes to provide alerts to users and applications regarding the location of particular mobile communication devices. It would be further desirable that such functionality be provided with a high level of automation to enhance user experience.
SUMMARY
According to an embodiment of the invention, a computer-implemented method for providing an alert regarding mobile device location is provided. The method includes obtaining location data corresponding to locations of a mobile device over a period of time. A location pattern is determined based on the location data. The current location of the mobile device is detected at a time based on the determined pattern, and an alert is provided regarding the current location of the mobile device.
According to another embodiment of the invention, a computer-implemented method for providing an alert regarding mobile device location is provided. The method includes obtaining location data corresponding to locations of a plurality of mobile device users over a period of time. A location pattern of the plurality of mobile device users is determined based on the location data. A current location of a particular mobile device user is detected, and an alert is provided based on the current location of the particular mobile device user and the determined location pattern.
According to another embodiment of the invention, a computer-implemented method for providing an alert regarding mobile device location is provided. The method includes detecting requests for location data corresponding to the location of one or more mobile devices over a period of time. A request pattern is determined based on the requests for location data. A current location of the one or more mobile devices is detected at a time based on the determined request pattern. An alert is provided rendering accessible the current location at the time based on the determined request pattern.
According to another embodiment of the invention, a computer-implemented method for providing an alert regarding mobile device location is provided. The method includes detecting requests from a plurality of users for location data corresponding to the location of a plurality of mobile devices. A request pattern of the plurality of users is determined based on the requests for location data. A current location of a particular mobile device is detected at a time based on the determined request pattern, and an alert is provided rendering accessible the current location of the particular mobile device.
According to another embodiment of the invention, a computer-implemented method for providing an alert regarding mobile device location is provided. The method includes receiving identifying information of a user corresponding to one or more environmental conditions. The user is detected at a particular location. Mapping data is received defining positioning of the one or more environmental conditions, and an alert is provided to the user regarding the environmental condition in response to the one or more environmental conditions corresponding to the detected particular location.
According to another embodiment of the invention, a system for providing an alert regarding mobile device location including one or more computing devices with one or more memories comprising instructions operable to enable the one or more computing devices to perform a procedure. The procedure includes obtaining location data corresponding to locations of a mobile device over a period of time and determining a location pattern based on the location data. A current location of the mobile device is detected at a time based on the determined pattern, and an alert is provided regarding the current location of the mobile device.
Elements described with respect to a particular invention embodiment in the above summary or in the below detailed description can be used in the performance of a method or implementation of a system in one or more other invention embodiments described herein.
BRIEF DESCRIPTION OF THE DRAWING(S)
The foregoing summary as well as the following detailed description will be readily understood in conjunction with the appended drawings which illustrate embodiments of the invention. In the drawings:
<figref idrefs="DRAWINGS">FIG. 1</figref> is a schematic illustration of an exemplary operating environment in which a coordination system is operable.
<figref idrefs="DRAWINGS">FIGS. 2-6</figref> are flow charts showing computer-implemented methods for providing alerts regarding mobile device location.
<figref idrefs="DRAWINGS">FIG. 7</figref> is a plan view of an example city streetscape for illustrating methods according to invention embodiments.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)
Referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, a schematic illustration is shown of an exemplary operating environment <b>10</b> in which mobile device communication systems, in the form of mobile devices <b>12</b> and a coordination system <b>30</b>, can be used. The mobile devices <b>12</b> and coordination system <b>30</b> each include one or more computing devices and one or more memory devices, which computing devices and memory devices can be integrally constructed or connected in any suitable manner. It is to be understood that a system or server as described herein comprises a computer system, as is known in the art.
Each mobile device <b>12</b> preferably provides a platform which enables an operating system <b>14</b> and a module of instructions <b>16</b> preferably residing in a memory of the mobile device <b>12</b>. The mobile device <b>12</b>, preferably a wireless transmitting and receiving device with cellular telephone functionality, includes a transceiver <b>18</b> for communication with cellular base transceiver stations <b>60</b>, <b>62</b> (“base stations”) and a user interface <b>20</b>, preferably including a display and one or more audio speakers. The transceiver <b>18</b> can be configured to communicate with any suitable wireless stations or devices. The mobile device <b>12</b> can alternatively include a plurality of transceivers for communication with a plurality of wireless stations or devices of differing protocols. A GPS receiver <b>22</b> is preferably provided to receive signals from GPS satellites <b>70</b> for determining a location of the mobile device <b>12</b>.
The coordination system <b>30</b> includes a processor or processors and memory or memories which enable operation of an operating system <b>32</b>, an alert module <b>40</b>, and databases <b>36</b>, <b>38</b>, <b>42</b>. Preferably, collected mobile device location data is stored in a location database <b>36</b>, map data corresponding to roads, addresses, building dimensions, and other definable geographic data are stored in a map database <b>38</b>, and user account information for particular users is stored in a user account database <b>42</b>. The coordination system <b>30</b> is configured to collect data indicative of mobile device location of the mobile devices <b>12</b> via a telecommunication network <b>72</b>, which can include the Internet and other networks, and to associate the mobile devices <b>12</b> with particular users associated with accounts in the user account database <b>42</b>. The location data is preferably received in the form of tuples. Each tuple preferably includes one or more location coordinates and one or more time stamps respectively associated with the one or more location coordinates. Each tuple also preferably includes an identification (“ID”) relating the tuple to a particular mobile device and a precision indication indicating the precision and/or accuracy of the one or more location coordinates.
The tuples or other suitable mobile device location data can be received by the coordination system <b>30</b> in the form of one or more short message service (“SMS”) messages received from the mobile devices <b>12</b> via a short message service center (“SMSC”) <b>74</b>, which can be integrated with the telecommunication network <b>72</b> or otherwise provided. Alternatively, location data can be sent by the mobile devices <b>12</b> using internet protocol (“TCP/IP”) and received by the coordination system <b>30</b> via an internet protocol (“IP”) gateway <b>76</b>, which can be integrated with the telecommunication network <b>72</b> or otherwise provided. The coordination system <b>30</b> can alternatively query a remote position determining entity (“PDE”) <b>78</b>, a Gateway Mobile Location Center (“GMLC”), or other system for disseminating location data associated with mobile devices, which PDE <b>78</b>, GMLC or other system can be provided as a service by a telecommunication carrier or other party, and which system can deliver data to the coordination system <b>30</b> via internet protocol through the IP gateway <b>76</b> or via other suitable protocol. The coordination system <b>30</b> can alternatively receive mobile device location data in any suitable manner.
One or more external application servers <b>73</b> can communicate with the coordination system <b>30</b> or a mobile device <b>12</b> and execute applications which use location data provided by the mobile devices <b>12</b> or the coordination system <b>30</b> to provide content or services to a user of a particular mobile device <b>12</b> or other users requiring data regarding a particular mobile device <b>12</b>. Similarly, local applications <b>17</b> can use such location data to provide content or services to a user of a particular mobile device <b>12</b> or other users.
Referring to <figref idrefs="DRAWINGS">FIG. 2</figref>, a method <b>200</b> for providing an alert regarding mobile device location is shown. The method <b>200</b> is described with reference to components shown in the operating environment <b>10</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, wherein the coordination system <b>30</b> is preferably configured to perform the method <b>200</b> and includes memory for storing instructions for performing the method <b>200</b>. The method <b>200</b> can alternatively be performed via other suitable systems or devices. For example, the mobile device <b>12</b> can be configured to execute an application for performing the method <b>200</b> via the instructions module <b>16</b>.
The method <b>200</b> includes obtaining location data corresponding to locations of a mobile device such as the mobile device <b>12</b> over a period of time (step <b>202</b>) and determining a location pattern based on the location data (step <b>204</b>). A current location of the mobile device <b>12</b> is detected at a time based on the determined pattern (step <b>206</b>), and an alert is provided regarding the current location of the mobile device (step <b>208</b>). Location data is obtained, for example, by the coordination system <b>30</b> and stored in the location database <b>36</b>, and the location pattern is determined, for example, by the alert module <b>40</b> and stored in the location database <b>36</b>. The current location is detected, for example, by the coordination system <b>30</b>, responsive to the pattern determined by the alert module <b>40</b>, via data received via a mobile device's GPS receiver <b>22</b>, a remote position determining entity (“PDE”) <b>78</b>, a Gateway Mobile Location Center (“GMLC”), or other system for disseminating location data. The location alert is provided, for example, by the alert module <b>40</b> to a user via a user system <b>52</b> through the network <b>72</b>.
The mobile device <b>12</b> preferably corresponds to a subject user such as a child, a pet, or any person or animal which under certain circumstance may require monitoring. The subject user possesses the mobile device <b>12</b> or the mobile device <b>12</b> is attached to the subject user to permit the subject user's location to be monitored by a supervising user via a user system <b>52</b>, which can include any suitable network-connectable computing device. The supervising user preferably includes a parent, guardian or other person with supervisory or oversight responsibility for a particular subject user. In the case that the subject user is a pet, the supervising user can be a pet owner. The alert is preferably scheduled and provided to the supervising user as a data transmission. A user can be both a subject user and a supervising user, for example in the case of two spouses with mutual oversight responsibilities for each other.
The alert can alternatively be provided to a particular application, such as a social networking application. For example, the instruction module <b>16</b> of the mobile device <b>12</b> or the coordination system <b>30</b> executing the method <b>200</b> can provide the alert to a social networking application executed on a remote application server <b>73</b> via the network <b>72</b>, which social networking application is accessible by a user system <b>52</b> to permit access by a supervising user to information contained in the alert. In another example, the instruction module <b>16</b> of the mobile device <b>12</b> executing the method <b>200</b> can provide the alert to a locally executed application <b>17</b> configured to transmit the alert via suitable protocol to the user system <b>52</b>.
Prior to scheduling or transmitting alerts, a suggestion can be provided, for example by the coordination system <b>30</b> or an application executed on the mobile device <b>12</b>. The suggestion can be provided to the supervising user via a user system <b>52</b> in the form of a query as to whether the supervising user desires to receive an alert regarding the current position of the subject user at a particular time. A suggestion can further be provided to the subject user for example via mobile device <b>12</b>, in the form of a query as to whether the subject user desires to permit the supervising user to receive an alert regarding the current position of the subject user. The coordination system <b>30</b>, the mobile device <b>12</b> or other suitable system can provide the alert in response to receiving acceptance of the suggestion from the subject user and/or the supervising user.
For purposes of illustration of methods described herein, a plan view of an example city streetscape <b>900</b> is shown in <figref idrefs="DRAWINGS">FIG. 7</figref>. The streetscape <b>900</b> includes city blocks <b>902</b> separated by streets <b>904</b> permitting travel of vehicles <b>906</b>. Various building structures are provided on the city blocks <b>902</b> including physical locations corresponding to homes <b>908</b>, an office building <b>910</b>, a retail store <b>912</b>, a fitness club <b>914</b>, playing courts <b>916</b>, a supermarket <b>918</b>, a restaurant <b>920</b>, a parking lot <b>922</b>, and a library <b>924</b>. A user <b>8</b>, carrying a mobile device <b>12</b>, walks or drives a vehicle <b>906</b> within the streetscape <b>900</b>.
The location pattern can be determined by determining the mobile device <b>12</b> is at a particular location during a particular time period of a day for a predetermined number of days. The alert can be provided based on the determined particular time period of the day, and preferably, the alert is provided substantially during such particular time period of day or a predetermined length of time thereafter. In an example pursuant to the method <b>200</b>, a subject user is detected via a location enabled mobile device to be present at a particular location (e.g. the fitness club <b>914</b>) from about 7:00 pm to about 9:00pm each Monday for 3 consecutive Mondays. In response to this detected behavior, the subject user's position is detected at various times between 7:00 pm and 9:00pm each Monday thereafter. If the subject user is not present at the fitness club <b>914</b> between 7:00pm and 9:00pm on a Monday, an alert reporting the subject user's current location to a supervising user is transmitted at about 8:00pm or one or more other times between 7:00pm and 9:00pm. Alternatively, the alert including the current location can be transmitted between about 7:00pm and 9:00pm each Monday regardless of whether if the subject user is present at the fitness club <b>914</b>. In such manner a supervising user such as the subject user's spouse can learn whether or not the subject user has arrived at the fitness club <b>914</b> as expected.
The location pattern can alternatively be determined by determining the mobile device <b>12</b> leaves a particular location during a particular time period of a day for a predetermined number of days. The alert can be provided based on the determined particular time period of the day, and preferably the alert is provided substantially during such particular time period of the day or a predetermined length of time thereafter. In an example pursuant to the method <b>200</b>, a subject user is detected via a location enabled mobile device to leave a first location corresponding to the user's place of work (e.g. office building <b>910</b>) between 6:00pm and 7:00pm for 5 consecutive workdays, Monday through Friday. In response to this detected behavior, an alert reporting the subject user's location to a supervising user is transmitted to a supervising user one or more times at or about 7:00pm or soon thereafter each workday, Monday through Friday. In such manner, a supervising user such as the subject user's spouse can learn whether the subject user is still at work at the office building <b>910</b> at 7:00pm on a given day.
Referring to <figref idrefs="DRAWINGS">FIG. 3</figref>, a method <b>300</b> for providing an alert regarding mobile device location is shown. The method <b>300</b> is described with reference to components shown in the operating environment <b>10</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, wherein the coordination system <b>30</b> is preferably configured to perform the method <b>300</b> and includes memory for storing instructions for performing the method <b>300</b>. The method <b>300</b> can alternatively be performed via other suitable systems or devices. For example, a mobile device <b>12</b> can be configured to execute an application for performing the method <b>300</b>. The method <b>300</b> includes obtaining location data corresponding to locations of a plurality of mobile device users over a period of time via the users' mobile devices (step <b>302</b>) and determining a location pattern of the plurality of mobile device users based on the location data (step <b>304</b>). A current location of a particular mobile device user is detected via the user's mobile device (step <b>306</b>), and an alert is provided based on the current location of the particular mobile device user and the determined location pattern (step <b>308</b>). The method <b>300</b> enables patterns in similar or dissimilar users' location behaviors to be used to create pertinent alerts for a particular user. To determine similarity between users, identifying information for the mobile device users is preferably obtained.
Location data is obtained, for example, by the coordination system <b>30</b> and stored in the location database <b>36</b>, and the location pattern is determined, for example, by the alert module <b>40</b> and stored in the location database <b>36</b>. The current location is detected, for example, by the coordination system <b>30</b>, responsive to the pattern determined by the alert module <b>40</b>, via data received via a mobile device's GPS receiver <b>22</b>, a remote position determining entity (“PDE”) <b>78</b>, a Gateway Mobile Location Center (“GMLC”), or other system for disseminating location data. The location alert is provided, for example, by the alert module <b>40</b> to a user via a user system <b>52</b> through the network <b>72</b>.
In performing the method <b>300</b>, identifying information corresponding to the plurality of mobile device users and the particular mobile device user is preferably obtained. The identifying information of each mobile device user preferably includes a plurality of user identifying criteria including one or more of a user address, city of residence, state of residence, age, gender, income level, education level, music preference, and occupation. Alternatively, the identifying information can include any suitable user identifying criteria. The identifying information of the plurality of mobile device users is compared with the identifying information of the particular mobile device user. The location pattern of the plurality of mobile device users is determined in response to the identifying information of the plurality of mobile device users corresponding to, or alternatively not corresponding to, the identifying information of the particular user. The identifying information of the mobile device users corresponds when at least one element of the identifying information matches. For example, location data from a plurality of users having an income level approximately equal to the income level of the particular user is used in determining the location pattern used to trigger an alert based on a current location of the particular user's mobile device. In another example, location data from a plurality of users having music preferences different from the music preferences of a particular user is used in determining the location pattern which is used to trigger an alert based on a current location of the particular user's mobile device.
The identifying information can be manually entered or uploaded to the coordination system <b>30</b> at any suitable time by a particular user via a mobile device <b>12</b>, user system <b>52</b> or other system to create a profile for a particular mobile device user which can be stored in the user account database <b>42</b>. Identifying information is preferably provided to the coordination system <b>30</b> via a web or WAP interface. In the case that the mobile device user is a child or otherwise under the care of a supervising user, the supervising user preferably provides the identifying information.
Alternatively, identifying information can be automatically gathered via connections to one or more other systems, such as an application server <b>73</b> via the network <b>72</b>. The application server <b>73</b> can include, for example, a social networking application server hosting a social networking application enabling an online social network. The coordination system <b>30</b> is preferably configured to access and interface with an online social network supported by the social networking application to obtain a mobile device user's identifying information.
In performing the method <b>300</b>, the location pattern can be determined by determining the plurality of users are at a particular location during a particular time period of a day for a predetermined number of days. The alert is thereafter provided in response to the current location of the particular mobile device being at the particular location during the particular time period of the day. Alternatively, the alert is provided in response to the current location of the particular mobile device being a predetermined distance from the particular location during the particular time period of the day. The alert can be provided to the particular user whose location is being detected or another user such as a supervising user (e.g. parent, spouse) desiring location information regarding the particular user (e.g. child, spouse). The alert can alternatively be provided to a local or remote application for example in one of the manners described above. The alert can include the location of the particular user, for example in the case where the alert is transmitted to a supervising user. Alternatively, the alert can include a notification of a particular location, preferably nearby the current location of the particular user, in the form of a suggestion that the particular user travel to or stay at the particular location, for example in the case where a particular user wants to be directed to a location frequented by users with like identifying information.
Prior to scheduling or transmitting alerts, a suggestion can be provided to the particular user, or alternatively another user, in the form of a query as to whether the user desires to receive an alert regarding the current position of the particular user. An acceptance of the suggestion indicating a desire to receive the alert can be obtained from the particular user, or alternatively the other user (e.g. a supervising user). The alert can thereafter be provided to the particular user or other user in response to receiving the acceptance of the suggestion.
In an example pursuant to the method <b>300</b>, a plurality of users determined to be schoolmates of a particular user (e.g. Billy) are detected to go to a particular library each Friday afternoon between 3:00pm and 5:00pm over a period of weeks. Based on Billy's schoolmates' location pattern including Friday afternoon visits to the library, an alert is scheduled to fire when Billy arrives at the particular library <b>924</b>. When Billy arrives at the library <b>924</b> between 3:00pm and 5:00pm, the alert is transmitted to Billy's mother notifying her that Billy is at the library. Alternatively, Billy's mother can be notified if Billy is not present at the library between 3:00pm and 5:00pm.
In another example pursuant to the method <b>300</b>, information including an event schedule with event type listings for a particular location (e.g. Bloom's Saloon <b>920</b>) is obtained. A particular user (e.g. Kelly) is determined to frequently go to the particular location (e.g. Bloom's Saloon <b>920</b>) when a particular type of event is occurring (e.g. bluegrass music is playing), but not when another type of event is occurring (e.g. heavy metal music is playing). One night, a group of users are determined to be in attendance at Bloom's Saloon <b>920</b> who have been determined to have previously attended Bloom's Saloon <b>920</b> on nights when heavy metal music is playing, but not when bluegrass music is playing. The event preferences (e.g. music preferences) of Kelly and the group of users are compared. An alert is transmitted to Kelly that Kelly may not be interested in attending Bloom's Saloon <b>920</b> in view of the differing musical tastes of the group of users, and preferably in response to Kelly's current location being at or within a predetermined distance from Bloom's Saloon <b>920</b>. An alert is alternatively transmitted to Kelly informing Kelly that she may or may not be interested in attending other nearby venues in view of the like or differing musical tastes of groups of users present at such other venues. Accordingly, an alert can be provided as a recommendation or suggestion that a particular mobile device user be present (or not be present) at a particular location corresponding to or a predetermined distance from the particular user's current location in response to an event preference of the particular mobile device user substantially matching (or not matching) an event preference of a plurality of other mobile device users. In this example, user identifying information in the form of the event preferences is therefore derived from determined locations of the users and information regarding events occurring at such locations.
Referring to <figref idrefs="DRAWINGS">FIG. 4</figref>, a method <b>400</b> for providing an alert regarding mobile device location is shown. The method <b>400</b> is described with reference to components shown in the operating environment <b>10</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, wherein the coordination system <b>30</b> is preferably configured to perform the method <b>400</b> and includes memory for storing instructions for performing the method <b>400</b>. The method <b>400</b> can alternatively be performed via other suitable systems or devices. For example, a mobile device <b>12</b> can be configured to execute an application for performing the method <b>400</b>. The method <b>400</b> includes detecting requests for location data corresponding to the location of one or more mobile devices over a period of time (step <b>402</b>) and determining a request pattern based on the requests for location data (step <b>404</b>). A current location of the one or more mobile devices is detected at a time based on the determined request pattern (step <b>406</b>), and an alert is provided rendering accessible the current location at the time based on the determined request pattern (step <b>408</b>).
Requests for location data are detected, for example, by the coordination system <b>30</b> and stored in the user database <b>42</b>, and the request pattern is determined, for example, by the alert module <b>40</b> and stored in the user database <b>42</b>. The current location is detected, for example, by the coordination system <b>30</b>, responsive to the pattern determined by the alert module <b>40</b>, via data received via a mobile device's GPS receiver <b>22</b>, a remote position determining entity (“PDE”) <b>78</b>, a Gateway Mobile Location Center (“GMLC”), or other system for disseminating location data. The alert is provided, for example, by the alert module <b>40</b>, rendering accessible the current location to a user or application via the network <b>72</b>.
The one or more mobile devices preferably correspond to at least a first user. Preferably the detected requests originate from a second user, such as a supervising user, and the alert renders the current location of the first user accessible to the second user. The request pattern is preferably determined by detecting a request originating from the second user occurring during a particular time period of a day for a predetermined number of days, and the alert is preferably provided on a later day during the particular time period of the day. The request pattern can alternatively be determined by detecting a request originating from the second user positioned at a particular location a predetermined number of times, and providing the alert to the second user in response to later detecting the second user at the particular location. The alert can alternatively be provided to a local or remote application for example in one of the manners described above.
In an example pursuant to the method <b>400</b>, a request from a user (e.g. Monica) for her dog's location is detected each day, wherein a location aware mobile device is attached to the dog. Monica's request is detected as occurring each day upon Monica's arrival at her place of work (e.g. office building <b>910</b>). Thereafter, an alert is transmitted to Monica every workday upon detecting Monica's mobile device at Monica's place of work at the office building <b>910</b>. For example, the coordination system <b>30</b> can be configured to schedule an alert via the alert module <b>40</b> to be transmitted to Monica's mobile device <b>12</b> immediately upon detecting the mobile device <b>12</b> at the office building <b>910</b>.
Referring to <figref idrefs="DRAWINGS">FIG. 5</figref>, a method <b>500</b> for providing an alert regarding mobile device location is shown. The method <b>500</b> is described with reference to components shown in the operating environment <b>10</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, wherein the coordination system <b>30</b> is preferably configured to perform the method <b>500</b> and includes memory for storing instructions for performing the method <b>500</b>. The method <b>500</b> can alternatively be performed via other suitable systems or devices. For example, a mobile device <b>12</b> can be configured to execute an application for performing the method <b>500</b>. The method <b>500</b> includes detecting requests from a plurality of users for location data corresponding to the location of a plurality of mobile devices (step <b>502</b>) and determining a request pattern of the plurality of users based on the requests for location data (step <b>504</b>). A current location of a particular mobile device is detected at a time based on the determined request pattern (step <b>506</b>), and an alert is provided rendering accessible the current location of the particular mobile device (step <b>508</b>).
Requests for location data are detected, for example, by the coordination system <b>30</b> and stored in the user database <b>42</b>, and the request pattern is determined, for example, by the alert module <b>40</b> and stored in the user database <b>42</b>. The current location is detected, for example, by the coordination system <b>30</b>, responsive to the pattern determined by the alert module <b>40</b>, via data received via a mobile device's GPS receiver <b>22</b>, a remote position determining entity (“PDE”) <b>78</b>, a Gateway Mobile Location Center (“GMLC”), or other system for disseminating location data. The alert is provided, for example, by the alert module <b>40</b>, rendering accessible the current location to a user or application via the network <b>72</b>.
Identifying information corresponding to the plurality users and a particular user is preferably obtained. Identifying information of the plurality of users is compared with the identifying information of the particular user, for example via the alert module <b>40</b>. The request pattern of the plurality of users is determined in response to the identifying information of the plurality of users corresponding to the identifying information of the particular user, whereby request data from users having identifying information which matches in a predetermined manner the identifying information of the particular user is used to define the request pattern used to determine the timing of the alert. The particular user is provided with the alert rendering accessible the current location of the particular mobile device. The alert can alternatively be provided to a local or remote application, for example in one of the manners described above, which application is preferably accessible by the particular user. For example, the particular user can correspond to a supervising user such as a parent, the particular mobile device can be carried by a supervised subject user such as a child of the parent, the other plurality of users can correspond for example to other supervising users such as other parents, and the plurality of mobile devices can correspond to other supervised users such as children of the other parents.
Prior to scheduling or transmitting alerts, a suggestion can be provided to the particular user in the form of a query as to whether the user desires to receive an alert regarding the current position of a particular mobile device. An acceptance of the suggestion indicating a desire to receive the alert can be obtained from the particular user. The alert can thereafter be provided to the particular user in response to receiving such acceptance.
In an example pursuant to the method <b>500</b>, a particular user Margaret has a 13 year old child. A plurality of other users also have 13 year old children. The other users schedule an alert to automatically check locations of their respective children at about 10:00pm on all school nights. The scheduling of the alert can be performed for example by a request to the coordination system <b>30</b>. In response to the alert scheduled by the other users, a suggestion is provided to Margaret to schedule an alert to occur at about 10:00pm on school nights including a current location of her child. The suggestion and alert can be provided in a transmission for example by the coordination system <b>30</b> via the alert module <b>40</b> to a device or system operated by Margaret.
Referring to <figref idrefs="DRAWINGS">FIG. 6</figref>, a method <b>600</b> for providing an alert regarding mobile device location is shown. The method <b>600</b> is described with reference to components shown in the operating environment <b>10</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, wherein the coordination system <b>30</b> is preferably configured to perform the method <b>600</b> and includes memory for storing instructions for performing the method <b>600</b>. The method <b>600</b> can alternatively be performed via other suitable systems or devices. For example, a mobile device <b>12</b> can be configured to execute an application for performing the method <b>600</b>. The method <b>600</b> includes receiving identifying information of a user corresponding to one or more environmental conditions (step <b>602</b>) and detecting the user at a particular location (step <b>604</b>). Mapping data is received defining positioning of the one or more environmental conditions (step <b>606</b>), and an alert is provided to the user in response to the one or more environmental conditions corresponding to the detected particular location (step <b>608</b>). The mapping data preferably includes geographic information system (GIS) mapping data. The user is preferably detected at the particular location a predetermined number of times to establish a pattern prior to providing an alert corresponding to the particular location.
In an example pursuant to the method <b>600</b>, an indication is received from a particular user (e.g. Paul) that he is allergic to pollen. Paul is detected to travel to a particular location corresponding to a particular location, his place of work, retail store <b>912</b>, a predetermined number of times evidencing a pattern of travel to the particular location. Mapping data (e.g. GIS mapping data) is received indicating that today there is a high concentration of pollen in the air near the retail store <b>912</b>. Based on Paul's indication and the mapping data, an alert is provided to Paul indicating that his work is near an area with a high concentration of allergen (e.g. pollen). The indication from Paul and the mapping data can be received for example by the coordination system <b>30</b>, and the coordination system <b>30</b> can transmit the alert to Paul through the network <b>72</b> via his mobile device <b>12</b> indicating that his place of work is near a high concentration of pollen.
While embodiments of the invention have been described in detail above, the invention is not limited to the specific embodiments described above, which should be considered as merely exemplary. Further modifications and extensions of the invention may be developed, and all such modifications are deemed to be within the scope of the invention as defined by the appended claims.
Contents5
8 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8
Every citation, both waysCites: the store holds 114 of 115
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2019122536A1 | Cited by | United States of America | Search report |
| US10455389B2 | Cited by | United States of America | Search report |
| US9510152B2 | Cited by | United States of America | Applicant |
| US2019122536A1 | Cited by | United States of America | Search report |
| US2023419817A1 | Cited by | United States of America | Search report |
| US10861319B2 | Cited by | United States of America | Search report |
| US2022366776A1 | Cited by | United States of America | Search report |
| US2019122536A1 | Cited by | United States of America | Search report |
| US11741826B2 | Cited by | United States of America | Search report |
| US12159525B2 | Cited by | United States of America | Search report |
| US2014279508A1 | Cited by | United States of America | Pre-grant |
| US9197995B1 | Cited by | United States of America | Applicant |
| US11443614B2 | Cited by | United States of America | Search report |
| US2001022558A1 | Cites | United States of America | Applicant |
| US2001029425A1 | Cites | United States of America | Applicant |
| US2001044310A1 | Cites | United States of America | Applicant |
| US2002116266A1 | Cites | United States of America | Applicant |
| US2002193150A1 | Cites | United States of America | Applicant |
| US2003008668A1 | Cites | United States of America | Search report |
| US2003064788A1 | Cites | United States of America | Applicant |
| US2003216960A1 | Cites | United States of America | Applicant |
| US2004122734A1 | Cites | United States of America | Applicant |
| US2004147267A1 | Cites | United States of America | Applicant |
| US2004185822A1 | Cites | United States of America | Applicant |
| US2004186776A1 | Cites | United States of America | Applicant |
| US2004214584A1 | Cites | United States of America | Applicant |
| US2004259573A1 | Cites | United States of America | Applicant |
| US2005079877A1 | Cites | United States of America | Search report |
| US2005202830A1 | Cites | United States of America | Search report |
| US2006058036A1 | Cites | United States of America | Search report |
| US2007049290A1 | Cites | United States of America | Search report |
| US2008153512A1 | Cites | United States of America | Search report |
| US2010190513A1 | Cites | United States of America | Search report |
| US2010255856A1 | Cites | United States of America | Search report |
| US2011143772A1 | Cites | United States of America | Search report |
| US2011256881A1 | Cites | United States of America | Search report |
| US2012009904A1 | Cites | United States of America | Search report |
| US2012083285A1 | Cites | United States of America | Search report |
| US4788711A | Cites | United States of America | Applicant |
| US5223844A | Cites | United States of America | Applicant |
| US5278539A | Cites | United States of America | Applicant |
| US5535431A | Cites | United States of America | Search report |
| US5604787A | Cites | United States of America | Applicant |
| US5610821A | Cites | United States of America | Applicant |
| US5628050A | Cites | United States of America | Applicant |
| US5724243A | Cites | United States of America | Applicant |
| US5732383A | Cites | United States of America | Applicant |
| US5815802A | Cites | United States of America | Applicant |
| US5833479A | Cites | United States of America | Applicant |
| US5907293A | Cites | United States of America | Applicant |
| US5948040A | Cites | United States of America | Applicant |
| US5959577A | Cites | United States of America | Applicant |
| US5959945A | Cites | United States of America | Applicant |
| US6031455A | Cites | United States of America | Applicant |
| US6052598A | Cites | United States of America | Applicant |
| US6091956A | Cites | United States of America | Applicant |
| US6115611A | Cites | United States of America | Applicant |
| US6134454A | Cites | United States of America | Applicant |
| US6236933B1 | Cites | United States of America | Applicant |
| US6240294B1 | Cites | United States of America | Applicant |
| US6243039B1 | Cites | United States of America | Applicant |
| US6256577B1 | Cites | United States of America | Applicant |
| US6278375B1 | Cites | United States of America | Applicant |
| US6351221B1 | Cites | United States of America | Applicant |
| US6381465B1 | Cites | United States of America | Applicant |
| US6400956B1 | Cites | United States of America | Applicant |
| US6437696B1 | Cites | United States of America | Applicant |
| US6501947B1 | Cites | United States of America | Applicant |
| US6519465B2 | Cites | United States of America | Applicant |
| US6587835B1 | Cites | United States of America | Applicant |
| US6615130B2 | Cites | United States of America | Applicant |
| US6631267B1 | Cites | United States of America | Applicant |
| US6647257B2 | Cites | United States of America | Applicant |
| US6647269B2 | Cites | United States of America | Applicant |
| US6701234B1 | Cites | United States of America | Applicant |
| US6731238B2 | Cites | United States of America | Applicant |
| US6731940B1 | Cites | United States of America | Applicant |
| US6745021B1 | Cites | United States of America | Applicant |
| US6772213B2 | Cites | United States of America | Applicant |
| US6795710B1 | Cites | United States of America | Applicant |
| US6813502B2 | Cites | United States of America | Applicant |
| US6816720B2 | Cites | United States of America | Applicant |
| US6834195B2 | Cites | United States of America | Applicant |
| US6873850B2 | Cites | United States of America | Applicant |
| US6885874B2 | Cites | United States of America | Applicant |
| US6895238B2 | Cites | United States of America | Applicant |
| US6914525B2 | Cites | United States of America | Applicant |
| US6941126B1 | Cites | United States of America | Applicant |
| US6952645B1 | Cites | United States of America | Applicant |
| US6961562B2 | Cites | United States of America | Applicant |
| US6985696B2 | Cites | United States of America | Applicant |
| US7039387B2 | Cites | United States of America | Applicant |
| US7054612B2 | Cites | United States of America | Applicant |
| US7079850B2 | Cites | United States of America | Applicant |
| US7123926B2 | Cites | United States of America | Applicant |
| US7149533B2 | Cites | United States of America | Applicant |
| US7184744B1 | Cites | United States of America | Applicant |
| US7194249B2 | Cites | United States of America | Applicant |
| US7202814B2 | Cites | United States of America | Applicant |
| US7248961B2 | Cites | United States of America | Applicant |
6 members in 1 office
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 40612510 | United States of America | P | |
| 40612510 | United States of America | P | |
| 201113087250 | United States of America | A | |
| 61406125 | – | – | – |
| US20100406125P | – | – | – |
| US201113087250 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| US2012100866A1 | United States of America | A1 | |
| US8725174B2This record | United States of America | B2 | |
| US2014247126A1 | United States of America | A1 | |
| US9196149B2 | United States of America | B2 | |
| US2016080909A1 | United States of America | A1 | |
| US9510156B2 | United States of America | B2 |
79 transactions on the USPTO file
Allowed after 1 non-final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Workflow - Request for CPA - BeginBCPA | BCPA | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Sent to Classification ContractorPGPC | PGPC | |
| Payment of additional filing fee/PreexamFLFEE | FLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
19 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee payment procedureENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.)FEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Certificate of correctionCC | CC | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 08725174
- Publication, DOCDB
- 8725174
- Publication, EPODOC
- US8725174
- Application
- 13087250
- Application, DOCDB
- 201113087250
- Application, EPODOC
- US201113087250
Titles
- English
- Mobile device alert generation system and method
Patent term adjustment
- A delay
- +190 daysthe office missed an examination deadline
- Applicant delay
- −33 days
- Net adjustment
- 157 days
Classification
- CPC, 5
- H04W4/021
- H04W4/029
- G08B21/18
- H04W4/02
- H04W68/00
- IPC, 6
- H04W4 021
- H04W24 00
- H04M1 725
- H04M3 42
- H04W4 02
- H04W4 029
- USPC, 3
- 455456300
- 455412200
- 455414100