Patent Grant
8781870
Personal information management (PIM) systems are widely employed for personal and professional use. Increasingly, individuals access these systems from a variety of locations using a variety of devices. The data in a PIM system will often include location information—messages specifying where meetings are to occur, calendared appointments with designated locations, tasks to occur at specific locations, addresses associated with contacts, etc. Furthermore, there is an increasing array of navigation and other location tools that allow a user to determine their location (e.g., on a map) in real time. Because location information can take so many forms and come from diverse sources, it can be challenging for a PIM system user to effectively make productive use of location information.
Accordingly, the present description provides a method of prompting a user to perform PIM-related acts based on dynamic location data. The method includes receiving a current location of the user and selecting a PIM item from the user's system having an associated location. The user's current location is compared to the location of the PIM item. Based on the comparison, a suggested user fulfillment action for the PIM item is suggested to the user. The description further provides a method for identifying, for a calendar item of the user, other items in the user's PIM system having information of potential relevance to the location (e.g., meeting location) of the calendar item.
The above 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 limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
Microsoft Exchange Server is an example of a commercially available product that may be used to implement PIM server 22, though any suitable PIM platform may be employed. In many cases, the PIM server will be configured to actively synchronize with and/or to “push” PIM items out to a client device, such as a mobile phone or a vehicle navigation system. Furthermore, standalone PIM applications may be employed in addition to or instead of the client/server arrangement depicted in
Computing system 50 also includes a data-holding subsystem 54, which may include one or more physical devices configured to hold data and/or instructions executable by a logic subsystem to implement the location-aware PIM methods and processes described herein. For example, data-holding subsystem 54 may hold PIM items and software applications for interacting with the PIM items. When location-aware PIM methods and processes described herein are implemented, the state of the data-holding subsystem may be transformed (e.g., to hold different data). The data-holding subsystem may include removable media and/or built-in devices. The data-holding subsystem may include optical memory devices, semiconductor memory devices, and/or magnetic memory devices, among others. The data-holding subsystem may include devices with one or more of the following characteristics: volatile, nonvolatile, dynamic, static, read/write, read-only, random access, sequential access, location addressable, file addressable, and content addressable. In some embodiments, a logic subsystem and data-holding subsystem may be integrated into one or more common devices, such as an application specific integrated circuit or a system on a chip.
A display subsystem 56 may also be provided, for example to display a calendar view, contacts list, etc. in a PIM application, or to otherwise provide visual output. More generally, when employed, a display subsystem may be used to present a visual representation of data held by a data-holding subsystem. As the herein described methods and processes change stored data, and thus transform the state of the data-holding subsystem, the state of the display subsystem may likewise be transformed to visually represent changes in the underlying data. The display subsystem may include one or more display devices utilizing virtually any type of technology. Such display devices may be combined with a logic subsystem and/or a data-holding subsystem in a shared enclosure, or such display devices may be peripheral display devices.
Referring now to
Continuing with
Referring to step 64, the PIM item is selected from the data store containing the user's PIM information. In the example of
As further shown at step 64, the selected PIM item may be a calendar item having a scheduled time. Indeed, the exemplary method can be applied in connection with a meeting occurring in the near future. For example, at 9:30 a.m., the user might be driving in their car en route to a meeting that is scheduled to begin at 10:00 a.m. In such a situation, method 60 may include prompting the user to send a pre-created message in certain circumstances.
For example, as shown at step 70, the suggested user fulfillment action may be to send a message indicating the user will be late to the appointment. Furthermore, the pre-created message may be dynamically adjusted, in terms of the amount of “lateness” specified, based on the location comparison at step 66. For example, based on GPS data received by an in-dash navigation system, the step 66 comparison could be used to infer an approximate arrival time of 10:10 a.m. for the example meeting discussed above. The system would then prompt the user, along the following lines: “Would you like to send a message indicating you will be 10 minutes late?” If the user indicates his or her assent to the prompt (step 72), the method includes automatically preparing and sending the pre-created message (step 74).
The particular format and wording of the prompted lateness message may of course take any appropriate form, though in many cases it will be desirable that the user action required be minimal. For example, the assent at step 72 can be a simple voice command, a press of a single hard or soft button, etc. In addition, the automatic preparation and sending at step 74 may involve automatically sending the pre-created message to all of the meeting participants associated with the calendar item.
Optional step 76 and optional step 78 provide additional examples of fulfillment actions that can be issued/suggested in the event that the PIM item selected at step 64 is a calendar item having a scheduled time. Referring again to the example of the 10:00 a.m. meeting, the location comparison of step 66 may prompt the user to send a pre-created message to the other participant(s) suggesting an alternate location. This may occur for example, in response to the location comparison showing that the user's current location is outside a predetermined range of where the meeting is to occur (indicating for example, that the original location is unfeasible or that the user would arrive unacceptably late). Alternatively, location information associated with one or more other participants may be used to select an alternate location. Furthermore, as shown at step 78, the prompted user fulfillment action may be to propose a rescheduling of the meeting. As with step 76, the suggestion to send a rescheduling message may be based on the comparison location indicating that the user's current location is outside a predetermined range of where the meeting is to occur.
It should be further appreciated that traffic data, incident data, and the like may be provided along with or as part of the location data received by a user. In one example, traffic data may be used to predict arrival times to meetings or other scheduled calendar items. In the example above, data pertaining to congestion and/or traffic accidents can be received by the system and used in formulating/sending the predefined messages relating to arriving late, rescheduling, suggesting alternate locations, etc. Traffic and incident data can also be used to dynamically adjust reminders to the user. For example, heightened traffic flow could be used, independently or in combination with the user's current location, to dynamically adjust the time at which a meeting reminder is communicated to the user. In general, data pertaining to traffic, incidents, etc. may operate as an additional or alternative input to one or more of the operations/determinations depicted at step 62, step 64, step 66 and step 68.
Referring again to step 64, method 60 may be implemented so that the selected PIM item is a task item specifying a task the user is to perform. Often, a location will be associated with a task-type PIM item. For example, although tasks like “grocery shopping” or “renew driver's license” can be performed at various times, they are often associated with specific locations. Accordingly, if the comparison location at step 66 indicates the user is near a location where one of their tasks can be performed, the suggested fulfillment action may include prompting the user to perform the task, as shown at step 80. In addition, assuming the user responds affirmatively to such prompting, the method may include accommodating this newly-added or reordered action by shifting other scheduled items (e.g., meetings). Furthermore, this shifting or adjustment may be performed based on location data, and/or on data pertaining to traffic, incidents, etc.
In addition to prompting user action based on dynamic location information, the systems and methods described herein may be employed to aid a user in identifying PIM system information that may contain useful location information. Meetings are often scheduled in PIM systems without a location being specified. In other cases, meeting participants exchange communications after the meeting has been scheduled, in order to specify or change the meeting location. In fact, location-relevant communications are often sent shortly before a meeting is to begin.
Once the calendar item is selected, the method includes automatically identifying location-relevant information for the calendar item. Typically, this includes a search for items in the user's PIM system that are likely to contain information of potential relevance to the location of the calendar item (e.g., the location where a meeting is to take place). Furthermore, the search for relevant items can include filtering incoming items or other items that are not yet stored in the user's PIM system. An example of this is to prospectively search for incoming messages from the organizer of a meeting during a period leading up to the meeting (e.g., a half hour prior to the meeting.) A message from the meeting organizer that is sent in this timeframe is likely (or may be deemed by the system to be likely) to involve a change or update to the meeting location. Accordingly, as discussed in more detail below, one example implementation of method 100 is to immediately identify such an incoming message and provide a high-priority notification to the user.
Accordingly, method 100 may further include applying a search filter to the user's PIM system using one or more of the properties of the calendar item, as shown at step 104. Then, at step 106, one or more PIM items are identified from the search filter output. The identified items may include various types of PIM items (messages, calendar items, contacts, tasks, etc.) that are identified as containing or including information that is potentially relevant to the location of the calendar item selected at step 102.
Steps 104 and 106 may be illustrated through various examples. In many cases, the location information sought by the user will be in a message in the user's PIM system. The search filter can look for messages from meeting participants (e.g., obtained from the participant property) with particular emphasis on the meeting organizer. Past appointments with one or more of the meeting participants can be retrieved, on the probability/possibility that the calendar item selected at step 102 will occur in the same place as one of the past appointments. Keywords from the description property of the calendar item can be matched against keywords from PIM items in the system. These are but a few examples, virtually limitless possibilities exist. Also, as indicated at step 106 and referenced in some of the above examples, the search may yield PIM items other than just messages—other calendar items, contacts, tasks, etc. may contain potentially relevant location information. As shown at step 108, the method may further include providing user notification of the identified PIM item or items.
Referring again to the example in which an organizer of a meeting sends an email, text message or other message in a short time window prior to a meeting, the selection may occur at step 102 automatically in response to detecting an upcoming calendar event. Returning again to the example of driving to a 10:00 a.m. meeting, the search filter of step 104 can be enabled automatically at a predetermined time before the meeting. For purposes of illustration in this example, assume the 10:00 a.m. meeting is selected a half hour prior, such that the search filter of step 104 is automatically enabled and begins searching at 9:30 a.m. for location-relevant PIM items. As previously indicated, in this situation a prospective filter might be desirable, so as to provide the driver with an urgent or other high-priority notification of a communication from the meeting organizer or another participant, as shown at step 108. In one example, the driver might have the system configured so that an in-dash navigation/PIM device provides an audible alert in the event of such a message.
In other example implementations of the method, the search and identification of step 104 and step 106 is applied to locate pre-existing PIM items in the user's system, as opposed to screening for high-priority incoming items. In this manner, the calendar item selected at step 102 acts as a search actuator, in the sense that the calendar item and its selection provide a mechanism for search initiation. Indeed, as shown at step 102, a manual user initiation may be employed to select the calendar item that actuates the search and identify actions of step 104 and step 106. In one example, the user simply selects a calendar item in their PIM system. Additionally, or alternatively, the visual representation of the calendar item or PIM user interface may include a button or other actuator for triggering the automatic search and identify functions.
Referring now to
Regardless of the particular selection mechanism, the method continues at step 134 with determining a location associated with the calendar item being scheduled. The location may be determined via user entry or other methods. In the case of rescheduling, the location for the rescheduled meeting typically is known, and the known location would therefore be used at step 134.
At step 136, the method includes searching the PIM system and identifying one or more existing PIM items that have locations that are within a predetermined proximal range (e.g., distance) of the calendar item being scheduled. As indicated, the identified PIM item may be an existing calendar item or an existing task item, although other types of PIM items can be used as well. At step 138, the method includes determining a date/time—i.e., a day and/or time—of the PIM item or PIM items identified in step 136. For example, step 138 might that the user has a meeting at 3:00 p.m. on the following Wednesday, and that the meeting is less than a mile away from the location of the calendar item being scheduled. At step 140, the method includes proposing a date/time for the calendar item being scheduled. The proposed date/time is selected and proposed to the user based on it being conflict-free and within a desired time of the existing PIM item (e.g., on the same day, or within a predetermined amount of time before or after the time of existing item). In the above illustration, the proposed date/time could be selected to be adjacent the 3:00 p.m. meeting, for example. Furthermore, the determination and proposals described in the exemplary method may be made based on previously recorded data relating to location, traffic, incidents, etc., for example as received via a portable or in-dash navigation system.
As indicated, step 136, step 138 and step 140 may include identifying multiple existing PIM items having locations that are within a predetermined proximal range of the location of the calendar item being scheduled. In such a case, the method may further include proposing multiple proposed date/times for the calendar item being scheduled. Alternatively, even in the case of a single item being identified at step 136, the method may include proposing multiple options to the user for the date/time of the item being scheduled. Furthermore, in some cases it will be desirable to prioritize the multiple proposed date/times based on various criteria.
It is to be understood that the configurations and/or approaches described herein are exemplary in nature, and that these specific embodiments or examples are not to be considered in a limiting sense, because numerous variations are possible. The specific routines or methods described herein may represent one or more of any number of processing strategies. As such, various acts illustrated may be performed in the sequence illustrated, in other sequences, in parallel, or in some cases omitted. Likewise, the order of the above-described processes may be changed.
The subject matter of the present disclosure includes all novel and nonobvious combinations and subcombinations of the various processes, systems and configurations, and other features, functions, acts, and/or properties disclosed herein, as well as any and all equivalents thereof.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6477374 | Shaffer et al. | Nov 2002 | B1 |
| 7752188 | Lagerstedt et al. | Jul 2010 | B2 |
| 20060218029 | Chin | Sep 2006 | A1 |
| 20070055561 | Perrella et al. | Mar 2007 | A1 |
| 20080086455 | Meisels et al. | Apr 2008 | A1 |
| 20080195312 | Aaron et al. | Aug 2008 | A1 |
| 20080319652 | Moshfeghi | Dec 2008 | A1 |
| 20090006994 | Forstall et al. | Jan 2009 | A1 |
| 20090036148 | Yach | Feb 2009 | A1 |
| 20090164110 | Basir | Jun 2009 | A1 |
| 20090239552 | Churchill et al. | Sep 2009 | A1 |
| Entry |
|---|
| “Use GPS and Web Maps for Location-Aware Apps”, Retrieved at <<http://msdn.microsoft.com/en-us/magazine/2009.01.wm6gps.aspx>>, Feb. 10, 2009, pp. 6. |
| “GPS software for cell phones, update Nov. 2008”, Retrieved at <<http://www.gps-practice-and-fun.com/gps-software-for-cell-phones-update.html, Feb. 10, 2009, pp. 6. |
| Number | Date | Country | |
|---|---|---|---|
| 20100287024 A1 | Nov 2010 | US |
