Systems and methods for a vehicle smart calendar

• US 8,442,758 B1
• Filed: 02/27/2012
• Issued: 05/14/2013
• Est. Priority Date: 02/27/2012
• Status: Active Grant

• Current Assignee: Toyota Motor Corporation
• Original Assignee: Toyota Motor Engineering & Manufacturing North America Incorporated (Toyota Motor Corporation)
• Inventors: Rovik, Christopher Lee, Lota, Charan S., Restauri, Donald Anthony III
• Primary Examiner(s): Cheung, Mary
• Assistant Examiner(s): WONG, YUEN H
• Application Number:
  US13/406,463
• Time in Patent Office: 442 Days
• Field of Search: 701/424, 701/426
• US Class Current: 701/424
• CPC Class Codes: G01C 21/343 Calculating itineraries, i.e. routes leading from a starting point to a series of categorical destinations using a global route restraint, round trips, touristic trips travelling salesman problem G06Q10/04; optimisation of routes G06Q10/047
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

Systems and methods for a vehicle smart calendar are described. One embodiment includes obtaining information related to a user preference, a user schedule, and third party information and receiving a communication directly from a vehicle computing device of a vehicle, the communication including authenticating information for a user. Some embodiments include, in response to authenticating the user, automatically providing, by a remote computing device, a reminder for an event on the user schedule to the vehicle computing device, a predetermined time prior to the event.

Claims

1. A vehicle for providing a vehicle smart calendar comprising:

vehicle computing device that stores logic that, when executed by a computing device, causes the vehicle computing device to perform at least the following;

retrieve remotely stored schedule information from a user-specific electronic calendar for a user, the remotely stored schedule information comprising an upcoming event scheduled at a for a predetermined future time and at a predetermined location;

compare the remotely stored schedule information to a current time and a current vehicle location;

determine whether the upcoming event is associated with an accessory;

in response to determining that the upcoming event is associated with an accessory, determine whether the accessory is currently located in the vehicle;

in response to determining that the accessory is not currently located in the vehicle, determine a current location of the accessory;

calculate a travel time to the accessory and then to the predetermined location from the current vehicle location;

determine, from the travel time, a preferred time for departure to reach the accessory and the upcoming event before the future time;

provide a reminder of the upcoming event at a predetermined time prior to the preferred time for departure; and

provide routing data to the accessory and then to the predetermined location from the current vehicle location.

2. The vehicle of claim 1, wherein the travel time comprises an estimated time to retrieve the accessory prior to arriving at the predetermined location.

3. The vehicle of claim 1, wherein the routing data comprises directions from the current vehicle location to the location of the vehicle accessory and from the location of the vehicle accessory to the predetermined location.

4. The vehicle of claim 1, wherein the logic further causes the vehicle to provide at least the following:

generate a user interface for providing the remotely stored schedule information, the user interface comprising a user option to edit the remotely stored schedule information;

receive a user input for editing the remotely stored schedule information; and

facilitate a communication directly between the vehicle and a remote computing device that stores the remotely stored schedule information to update the remotely stored schedule information.

5. The vehicle of claim 1, wherein the logic further causes the vehicle to perform at least the following:

receive a mobile calendar directly from a mobile phone device, the mobile calendar being different than the remotely stored schedule information; and

update the remotely stored schedule information with the mobile calendar.

6. The vehicle of claim 1, wherein calculating the travel time comprises utilizing at least one of the following:

third party weather data, third party traffic data, and third party road condition data.

7. A method for providing a vehicle smart calendar comprising:

retrieving remotely stored schedule information for a user, the remotely stored schedule information comprising an upcoming event scheduled at a future time and at a predetermined location;

determining that the upcoming event is associated with an accessory;

determining that the accessory is currently located remote from a current vehicle location of a vehicle;

in response to determining that the accessory is located remote from the vehicle, determining a current location of the accessory;

calculating a travel time from the current vehicle location to the current location of the accessory and from the current location of the accessory to the predetermined location;

determining, from the travel time, a preferred time for departure to reach the accessory and the upcoming event before the future time;

providing, by a vehicle computing device, a reminder of the upcoming event at a predetermined time prior to the preferred time for departure; and

providing routing data from the current vehicle location, to the location of the accessory, and then to the predetermined location.

8. The method of claim 7, wherein determining that the accessory is currently located remote from the vehicle, comprises at least one of the following:

determining that a radio frequency identifier (RFID) signal is absent; and

receiving a user input that the accessory is currently remote from the vehicle.

9. The method of claim 8, wherein determining the location of the accessory comprises at least one of the following:

receiving a positioning signal that identifies the location of the accessory;

receiving a user input identifying the location of the accessory; and

determining a vehicle location at a time when the accessory was removed from the vehicle.

10. The method of claim 7, further comprising:

determining an action item for the user from the remotely stored schedule information;

determining, from context of the action item, an action item location where the action item may be completed; and

determining a time to complete the action item, based on the action item location and the upcoming event; and

providing the user with an action item reminder for completing the action item.

11. The method of claim 10, further comprising providing routing data to complete the action item at the action item location.

12. The method of claim 10, further comprising generating a user interface for providing information related to the action item and the upcoming event.

13. A system for providing a vehicle smart calendar comprising:

a memory component that stores logic that, when executed by a processor, causes the processor to perform at least the following;

retrieve remotely stored schedule information for a user, the remotely stored schedule information comprising an upcoming event scheduled at a future time and at a predetermined location;

determine that the upcoming event is associated with an accessory;

determine that the accessory is currently located remote from a current vehicle location of a vehicle;

in response to determining that the accessory is located remote from the vehicle, determine a current location of the accessory;

calculate a travel time from the current vehicle location to the current location of the accessory and from the current location of the accessory to the predetermined location;

determine, from the travel time, a preferred time for departure to reach the accessory and the upcoming event before the future time;

provide, by a vehicle computing device, a reminder of the upcoming event at a predetermined time prior to the preferred time for departure; and

provide routing data from the current vehicle location, to the location of the accessory, and then to the predetermined location.

14. The system of claim 13, wherein determining that the accessory is currently located remote from the vehicle, comprises at least one of the following:

determining that a radio frequency identifier (RFID) signal is absent; and

receiving a user input that the accessory is currently remote from the vehicle.

15. The system of claim 14, wherein determining the location of the accessory comprises at least one of the following:

receiving a positioning signal that identifies the location of the accessory;

receiving a user input identifying the location of the accessory; and

determining a vehicle location at a time when the accessory was removed from the vehicle.

16. The system of claim 13, wherein the logic further causes the processor to perform at least the following:

determine an action item for the user from the remotely stored schedule information;

determine, from context of the action item, an action item location where the action item may be completed; and

determine a time to complete the action item, based on the action item location and the upcoming event; and

provide the user with an action item reminder for completing the action item.

17. The system of claim 13, wherein the logic further causes the processor to provide routing data to complete the action item at the action item location.

18. The system of claim 13, wherein the logic further causes the processor to generate a user interface for providing information related to the action item and the upcoming event.