Handheld electronic devices, such as personal digital assistants (PDAs), mobile phones, digital cameras, and the like, offer mobility and a variety of services to their respective users. While they are typically configured to transmit and receive data to and from other devices via a wired or wireless connection, most mobile communication devices can also provide Internet access, maintain a personal address book, provide messaging capabilities, capture digital images, and place phone calls. Many devices, in particular smart phones and PDAs, provide a calendaring and/or “to-do list” function that allows the user to calendar appointments and to enter tasks directly into the device or into a service in a remote server. The calendaring function can be configured to provide a reminder of an appointment or task to the user at or near the time the appointment has been scheduled.
Many mobile communication devices can also identify their respective locations within a certain range depending on the device and location identifying technique. Some devices can use a sophisticated position determining system, such as a Global Positioning System (GPS). The GPS is a satellite-based radio navigation system that uses signals from three or four satellites to compute the current latitude, longitude and elevation of a GPS receiver in the device anywhere on earth down to within a few meters. Other devices can use a location identifying technique based on which base station is servicing the device, that is, the location of the device is within a range of the base station from which a call is made. Other devices can use location identifying techniques based on triangulation between the device and at least two base stations.
The device's location, typically represented by geospatial coordinates, can be used in a variety of ways. For example, a mapping service can use the device's current location to provide street directions from the current location to a desired destination location. In addition, a street address or name corresponding to the geospatial coordinates can be associated with a task or an appointment that is scheduled to be performed at or near the location. For example, the user can associate a task on the to-do list, e.g., “pick up medicine,” with the street address or geospatial coordinates associated with a task location, e.g., the user's pharmacy. When the device detects that the user is within a certain distance of the task location, e.g., the pharmacy, the device can display a message reminding the user to perform the task, e.g., “pick up medicine.” Alternatively, a reminder can be issued when the device detects that the user is near the task location and is traveling in a trajectory leading to the task location.
Location-based task reminders are useful for prompting the user to perform tasks that are located nearby. Typically, the reminders are generated when the user comes within a predetermined fixed distance of the task location and or when the user is traveling in a trajectory leading to the task location within the predetermined distance. This can be problematic, however, when the user does not routinely travel within the predetermined distance of task location. For example, if the user routinely travels a particular route and the task location is not located within the predetermined distance of the route, the user may never receive a task reminder unless he breaks away from the familiar route and travels within the predetermined distance of the task location. As a result, the user might forget to perform the task or miss an appointment.
To address this problem, some services allow the user to enter a reminder distance when the user calendars the task and task location. This approach, however, may not be helpful if the user is unfamiliar with the task location, or if another person other than the user is calendaring the task for the user. In any event, requiring the user to provide information in addition to the task/appointment and task location can be time-consuming and inconvenient.
Accordingly, an apparatus for providing a task reminder of a task to be performed at a task location is described. According to one exemplary embodiment, the apparatus includes a monitoring module configured to receive location information of a user of a mobile device; a data store for storing information that includes a task and a task location; and a reminder module configured to provide a reminder for the task based on a current location of the user and on a comparison of an estimated probability of the user traveling in a trajectory leading toward or away from the task location.
Accordingly, a method for providing a task reminder of a task to be performed at a task location are described. According to one exemplary embodiment, the method includes receiving location information identifying a location of a user via a mobile communication device associated with the user, receiving information that identifies a task, receiving information that identifies a task location, and providing a reminder for the task based on a current location of the user and on a comparison of an estimated probability of the user traveling in a trajectory leading toward or away from the task location.
The accompanying drawings provide visual representations which will be used to more fully describe the representative embodiments disclosed here and can be used by those skilled in the art to better understand the representative embodiments and their inherent advantages. In these drawings, like reference numerals identify corresponding elements, and:
Various aspects will now be described in connection with exemplary embodiments, including certain aspects described in terms of sequences of actions that can be performed by elements of a computing device or system. For example, it will be recognized that in each of the embodiments, at least some of the various actions can be performed by specialized circuits or circuitry (e.g., discrete and/or integrated logic gates interconnected to perform a specialized function), by program instructions being executed by one or more processors, or by a combination of both. Thus, the various aspects can be embodied in many different forms, and all such forms are contemplated to be within the scope of what is described.
According to an exemplary embodiment, intelligent, situation-sensitive task reminders are generated for a user of a mobile communication device. In one embodiment, a task reminder for a task is generated before the user arrives at a position where the user would tend to veer away from a task location associated with the task. By providing the task reminder before the user arrives at that position, the user can choose to deviate from the routine route (which leads away from the task location) and travel in a trajectory that leads toward the task location.
In one embodiment, the historical travel information of the user in relation to a position is analyzed to determine whether a task reminder should be generated. According to an exemplary embodiment, the historical travel information is used to calculate the respective probabilities of the user traveling from the position in a trajectory leading away from and toward the task location. When the probability of traveling away from the task location exceeds the probability of traveling toward the task location by a threshold value, a task reminder can be generated. In one embodiment, the task reminder is generated when the position is within a predetermined distance of the user's current position.
According to an exemplary embodiment, the system 100 includes means for monitoring a location of a user 120 via a mobile communication device 110 associated with the user 120 at predetermined time intervals, such as a monitoring module 200 that is in communication with the devices 110 and with the reminder server 300 over the network 10. In an exemplary embodiment, the monitoring module 200 monitors the location of the user 120 in order to track the historical travel information of the user 120.
The system further includes means for receiving user specified task information, which includes a task and a task location, and means for storing user-specific information that includes the historical travel information of the user 120 and the user specified task information. For example, in an exemplary embodiment, the monitoring module 200 is configured to store and manage the user-specific information in a data store 220.
The monitoring module 200 can be a personal computer or other device capable of collecting, storing and managing data. The monitoring module 200 can include a communication interface (not shown) to receive and transmit data over the network 10. In one embodiment, the monitoring module 200 monitors the location of the device 110 at predetermined time intervals in order to track the user's historical travel information 222. The historical travel information 222 can include the number of times the user 120 is present at or near a location, the amount of time the user 120 is present at or near the location, the number of times the user 120 has changed his or her position between at least two locations, and/or the number of times the user 120 has entered or exited a region. The historical travel information 222 is stored in the data store 220 along with the task information 224.
The reminder server 300 can be a personal computer or other device capable of processing data. The reminder server 300 includes a communication interface 302 to transmit and receive data over the network 10. In one embodiment, the reminder server 300 is configured to retrieve user-specific information from the data store 220 over the network 10 via the monitoring module 200.
The system 100 further includes means for generating a reminder of a task based on the user's historical travel information. For example, according to an exemplary embodiment, the reminder server 300 includes a reminder module 310 which is communicatively coupled to the communication interface 302. The reminder module 310 is configured to determine whether it would be useful to generate a task reminder for the user 120 based on the user's current position and the user's historical travel patterns in a region including the user's current position and the task location.
In one embodiment, a task reminder is generated when the reminder module 310 identifies a reminder position near the user's current position. In an exemplary embodiment, a reminder position is a position where an estimated probability of the user 120 traveling from the reminder position at a particular time in a trajectory leading away from the task location exceeds an estimated probability of the user 120 traveling from the reminder position at that same time in a trajectory leading toward the task location by a threshold value. When the reminder module 310 identifies a position that satisfies the criteria for a reminder position, the task reminder is generated and transmitted to the user 120.
The system 100 illustrated in
In another embodiment, shown in
In one embodiment, the user 120 specifies the task information 224 using a network enabled device, such as the mobile communication device 110, and sends the task information 224 to the reminder module 310 in the reminder server 300 or to the monitoring module 200 over the network 10 via the communication interface 118. The task information 224 is then organized in a task list 226. In one embodiment, the task list 226 includes at least one task and a reference to the associated task information. The tasks can be sorted in the order in which they were received, by priority/importance, by time frame, or by any other suitable factor.
Referring again to
In one embodiment, the monitoring module 200 monitors the device's location and collects the historical travel information 222 of the user by querying the position locator system 112 in the device 110 at a fixed time interval or sampling interval. For example, the monitoring module 200 can collect the travel information 222 every two minutes. In another embodiment, the monitoring module 200 can collect the information 222 at a sampling interval proportional to a velocity or expected velocity of the mobile communication device 110. For example, if the mobile communication device 110 is installed in a car, the sampling interval can be based on the average velocity of the car.
For each of the plurality of cells, the monitoring module 200 collects transition information associated with a cell. In one embodiment, the transition information includes a number of times the user 120 moves from the cell to any other cell, or remains within the same cell, during consecutive sampling intervals. For example, consider an exemplary region that is represented by a plurality of contiguous, non-overlapping cells 600 illustrated in
According to an exemplary embodiment, after the historical travel information 222 is stored, the reminder module 310 considers a first task on the task list 226 (block 504). A target cell evaluator module 312 in the reminder module 310, shown in
In
In another embodiment, the target cell evaluator module 312 further identifies the plurality of target cells 650 based on a current travel pattern of the user 120. In this embodiment, the target cell evaluator module 312 considers a previous position of the user 120, P0, and the current position of the user 120, P1, in determining which cells 600 are identified as target cells 650. In an exemplary embodiment, illustrated in
Referring again to
In one embodiment, illustrated in
In another embodiment, illustrated in
Referring again to
For example, referring again to
Referring again to
In an exemplary embodiment, the transition information associated with the target cell 650 is used to calculate the forward probability. As stated above, the transition information for a cell includes the number of times the user 120 moves from the cell to any other cell, including the same cell, during consecutive sampling intervals. In one embodiment, the forward probability can be the sum of the number of times the user 120 has traveled from the target cell 650 to any of the forward cells 660 divided by a total number of transitions from the target cell 650.
For example, let the transition information illustrated in
In the embodiment described above, the forward probability is calculated from the transition information that reflects the number of times the user 120 moves from the target cell 650 directly to any of the forward cells. In other words, the forward probability reflects the probability of the user 120 moving from the target cell 650 to any of the forward cells 660 in one sampling interval or step. In another embodiment, the forward probability can be based on the number of times the user 120 travels from the target cell 650 to any of the forward cells 660 via one or more cells 600. In other words, the forward probability can reflect the probability of the user 120 arriving at a forward cell 660 in two or more steps.
In this embodiment, transition probabilities between cells 600 can be represented in a transition-probability matrix, M, where the rows of the matrix are “from” cells and the columns of the matrix are “to” cells, and the elements of the transition-probability matrix are the transition probabilities. That is, element M[u, v] is the probability of transitioning from cell “u” to cell “v” in one step.
Let N be a number of steps and let the task cell 620 have coordinates (X, Y), then:
In this embodiment, the forward probability can reflect a more accurate estimate of the user's 120 travel tendencies because a horizon greater than a single step is considered. Such probabilities would capture the probabilities of the user 120 arriving at a forward cell 660, even when the user 120 passes through a backward cell 670 or non-backward or forward cell 600, respectively, to get to the forward cell 660.
Referring again to
In an exemplary embodiment, the target cell evaluator 312 then subtracts the forward probability from the backward probability (block 910) and compares the difference to the threshold value (block 912). If the difference is greater than the threshold value, the target cell evaluator module 312 designates the target cell 650 as a reminder position (block 914). Conversely, if the difference is less than the threshold value, the target cell 650 is not so designated (block 916).
Referring again to
When the target cell evaluator module 312 determines that the target cell 650 is a reminder position (block 510), the reminder module 310 can call a message generator module 314, shown in
If the user 120 is using or has recently used the device 110, e.g., by taking pictures or sending messages to others, the message generator module 314 can send a message that includes the task reminder to the user 120 during use or immediately after the user 120 has stopped actively using the device 110. Otherwise, the message generator module 314 can wait until the user 120 is available. In one embodiment, when the task reminder for a task has been sent, the message generator module 314 is configured to prevent a subsequent task reminder for the same task to be sent unless a predetermined time period has expired and/or a distance between the user 120 and the task cell 620 has not reduced to zero, but has exceed a threshold distance that is greater than the predetermined distance.
After the task reminder has been sent or when the reminder module 310 determines that all target cells 650 have been analyzed (block 514) without generating a reminder, the reminder module 310 determines whether more tasks remain on the task list 226 to be processed (block 516). If no other tasks remain, the process returns to monitoring the device's location (block 502). Otherwise, the next task is considered (block 518) and the process repeats at block 507 where the first target cell 650 is considered with respect to the next task.
As mentioned above, the tasks on the task list 226 can be listed in order of importance, time for completion, or any other suitable factor. Accordingly, the task reminder process can be performed for tasks according to their respective importance or completion time. The reminder module 310 can perform the process for a task with a highest priority, or it can process each of the tasks in order of decreasing priority.
Although the process above in
In another exemplary embodiment, the process can be performed once for a task associated with a plurality of task locations. In this embodiment, the process for determining whether the target cell 650 is a reminder position considers each of the task locations together. For example,
Once the forward cells 660 and backward cells 670 have been identified, the target cell evaluator module 312 considers a first of the plurality of task cells 620 (block 1104) and calculates a forward probability of the user 120 traveling from the target cell 650 in a trajectory leading toward the first task cell 620 (block 1106). In one embodiment, the forward probability is calculated by summing a number of times the user 120 has transitioned from the target cell 650 to any of the forward cells 660 associated with the first task cell 620 and dividing the sum by a total number of transitions from the target cell 650.
The target cell evaluator 312 then identifies one or more strong backward cells (block 1108). In this embodiment, a strong backward cell is a backward cell associated with the first task cell 620 that is not also identified as a forward cell 660 for any of the other task cells 620. The target cell evaluator module 312 then calculates a strong backward probability of the user 120 traveling from the target cell 650 in a trajectory leading away from the first task cell 620 (block 1110). In one embodiment, the strong backward probability is calculated by summing a number of times the user 120 has transitioned from the target cell 650 to any of the strong backward cells 660 associated with the first task cell 620 and dividing the sum by a total number of transitions from the target cell 650.
In an exemplary embodiment, the target cell evaluator 312 then subtracts the forward probability from the strong backward probability (block 1112) and compares the difference to the threshold value (block 1114). If the difference is greater than the threshold value, the target cell evaluator module 312 designates the target cell 650 as a reminder position (block 1116). Conversely, if the difference is less than the threshold value, the target cell evaluator module 312 determines whether more task cells 620 need to be analyzed (block 1118). If such is the case, the next task cell is considered (block 1120) and the process repeats at block 1106 where the forward probability for the next task cell 620 is calculated. When all the task cells 620 have been analyzed (block 1118) and none have resulted in a target cell designation, the target cell 650 is a reminder position (block 1122).
In another embodiment, instead of considering a task cell 650 individually, the target cell evaluator module 312 aggregates the task cells 650 and calculates an aggregate forward probability by summing the number of times the user 120 has transitioned from the target cell 650 to any of the one or more forward cells 660 associated with any task cell 620 and dividing the sum by the total transitions. Similarly, an aggregate backward probability is calculated by summing the number of times the user 120 has transitioned from the target cell 650 to any of the one or more backward cells 670 associated with any task cell 620 and dividing the sum by the total transitions. The aggregate forward probability is then subtracted from the aggregate backward probability and the difference is compared to the threshold value.
As stated above, when a reminder position is identified, the reminder module generates and sends a message including the task reminder to the user 120. In one embodiment, when the task reminder is sent, the device 110 receives the message via the communication interface 118 and the message is displayed to the user 120 on the device's user interface 121. The user 120 can respond to the task reminder explicitly and implicitly. In one embodiment, the user 120 can respond positively by explicitly “accepting” the reminder using the mobile communication device 110. Alternatively, or in addition to, the user 120 can implicitly respond positively by traveling to the task location within a certain time period after receiving the message and optionally remaining at or near the task location for a period of time. Similarly, the user 120 can respond negatively by explicitly “rejecting” the reminder or by moving away from the task location.
According to an exemplary embodiment, the reminder module 310 can receive or monitor the user's response to the task reminder and adjust the threshold value based on the user's response. For example, in one embodiment, the threshold value can be lowered when the user 120 responds positively to the reminder and can be increased when the user 120 responds negatively to the reminder. In another embodiment, the reminder module 310 can adjust the threshold value based on the importance of the task, as indicated explicitly or by name. For example, the threshold value can be lowered as the importance of the task increases. In yet another embodiment, the threshold value can be based on the time frame in which the task is to be completed where the threshold value is lowered as the time frame becomes smaller.
The executable instructions of a computer program as illustrated in
As used here, a “computer readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.
More specific examples (a non-exhaustive list) of the computer readable medium can include the following: a wired network connection and associated transmission medium, such as an ETHERNET transmission system, a wireless network connection and associated transmission medium, such as an IEEE 802.11(a), (b), or (g) or a BLUETOOTH transmission system, a wide-area network (WAN), a local-area network (LAN), the Internet, an intranet, a portable computer diskette, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or Flash memory), an optical fiber, a portable compact disc (CD), a portable digital video disc (DVD), and the like.
It will be appreciated by those of ordinary skill in the art that the concepts and techniques described here can be embodied in various specific forms without departing from the essential characteristics thereof. The presently disclosed embodiments are considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims, rather than the foregoing description, and all changes that come within the meaning and range of equivalence thereof are intended to be embraced.
The present application is a continuation of U.S. patent application Ser. No. 14/147,066, filed on Jan. 3, 2014, now U.S. Pat. No. 9,449,489, entitled “APPARATUS AND METHOD FOR PROVIDING A TASK REMINDER BASED ON USER LOCATION”, which is a continuation of U.S. patent application Ser. No. 13/766,859, filed on Feb. 14, 2013, now U.S. Pat. No. 8,648,715, entitled “APPARATUS AND METHOD FOR PROVIDING A TASK REMINDER BASED ON TRAVEL HISTORY”, which is a continuation of U.S. patent application Ser. No. 13/397,731, filed on Feb. 16, 2012, now U.S. Pat. No. 8,400,293, entitled “APPARATUS AND METHOD FOR PROVIDING A TASK REMINDER BASED ON TRAVEL HISTORY”, which is a continuation of U.S. patent application Ser. No. 12/409,854, filed on Mar. 24, 2009, now U.S. Pat. No. 8,138,912, entitled “APPARATUS AND METHOD FOR PROVIDING A TASK REMINDER BASED ON TRAVEL HISTORY”, which is a continuation of U.S. patent application Ser. No. 11/536,306, filed on Sep. 28, 2006 now U.S. Pat. No. 7,528,713, entitled “APPARATUS AND METHOD FOR PROVIDING A TASK REMINDER BASED ON TRAVEL HISTORY”, which is related to U.S. patent application Ser. No. 11/536,232, filed on Sep. 28, 2006 now U.S. Pat. No. 7,649,454, entitled “METHOD AND SYSTEM FOR PROVIDING A TASK REMINDER”, filed concurrently with U.S. patent application Ser. No. 11/536,306 and commonly owned and herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5748098 | Grace | May 1998 | A |
5938721 | Dussell et al. | Aug 1999 | A |
6177905 | Welch | Jan 2001 | B1 |
6266612 | Dussell et al. | Jul 2001 | B1 |
6411899 | Dussell et al. | Jun 2002 | B2 |
6484033 | Murray | Nov 2002 | B2 |
6515585 | Yamamoto | Feb 2003 | B2 |
6611754 | Klein | Aug 2003 | B2 |
6680675 | Suzuki | Jan 2004 | B1 |
6819256 | Hampton | Nov 2004 | B2 |
6879838 | Rankin et al. | Apr 2005 | B2 |
6943671 | McGee et al. | Sep 2005 | B2 |
6944539 | Yamada et al. | Sep 2005 | B2 |
6957076 | Hunzinger | Oct 2005 | B2 |
7003525 | Horvitz et al. | Feb 2006 | B1 |
7084758 | Cole | Aug 2006 | B1 |
7155456 | Abbott, III et al. | Dec 2006 | B2 |
7395507 | Robarts et al. | Jul 2008 | B2 |
7512889 | Newell et al. | Mar 2009 | B2 |
7533082 | Abbott et al. | May 2009 | B2 |
7614001 | Abbott et al. | Nov 2009 | B2 |
7764167 | Reeves et al. | Jul 2010 | B2 |
7958457 | Brandenberg et al. | Jun 2011 | B1 |
20020067308 | Robertson | Jun 2002 | A1 |
20020086680 | Hunzinger | Jul 2002 | A1 |
20020120351 | Tuomela et al. | Aug 2002 | A1 |
20030224762 | Lau et al. | Dec 2003 | A1 |
20030225589 | Eaton et al. | Dec 2003 | A1 |
20040176107 | Chadha | Sep 2004 | A1 |
20040192311 | Koskinen et al. | Sep 2004 | A1 |
20040203847 | Knauerhase et al. | Oct 2004 | A1 |
20040230685 | Seligmann | Nov 2004 | A1 |
20050009573 | Tokkonen | Jan 2005 | A1 |
20050102098 | Montealegre et al. | May 2005 | A1 |
20060077055 | Basir | Apr 2006 | A1 |
20060219780 | Swartz | Oct 2006 | A1 |
20060225076 | Longobardi | Oct 2006 | A1 |
20070072629 | Bae | Mar 2007 | A1 |
20070159322 | Garratt Campbell | Jul 2007 | A1 |
20070230282 | May et al. | Oct 2007 | A1 |
20070250257 | Almy | Oct 2007 | A1 |
20070254669 | Katz | Nov 2007 | A1 |
20070255786 | Mock et al. | Nov 2007 | A1 |
20070270166 | Hampel | Nov 2007 | A1 |
20080079566 | Singh et al. | Apr 2008 | A1 |
20080082651 | Singh et al. | Apr 2008 | A1 |
20090036148 | Yach | Feb 2009 | A1 |
20090327169 | Kamar et al. | Dec 2009 | A1 |
20140089243 | Oppenheimer | Mar 2014 | A1 |
Entry |
---|
Bhawalkar, P., et al., “ScheduleNanny: Using GPS to Learn the User's Significant Locations, Travel Times and Schedule,” [online] Sep. 2004 [retrieved on Apr. 21, 2006] Retrieved from the Internet: <URL: http://arxiv.org/ftp/cs/papers/0409/0409003.pdf> 8 pages. |
Number | Date | Country | |
---|---|---|---|
20170076580 A1 | Mar 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14147066 | Jan 2014 | US |
Child | 15270706 | US | |
Parent | 13766859 | Feb 2013 | US |
Child | 14147066 | US | |
Parent | 13397731 | Feb 2012 | US |
Child | 13766859 | US | |
Parent | 12409854 | Mar 2009 | US |
Child | 13397731 | US | |
Parent | 11536306 | Sep 2006 | US |
Child | 12409854 | US |