System and method for contact information access

• US 10,503,724 B2
• Filed: 03/03/2016
• Issued: 12/10/2019
• Est. Priority Date: 03/03/2016
• Status: Active Grant

• Current Assignee: Toyota Motor Engineering & Manufacturing North America Incorporated (Toyota Motor Corporation)
• Original Assignee: Toyota Motor Engineering & Manufacturing North America Incorporated (Toyota Motor Corporation)
• Inventors: Ochiai, Yuichi, Nagata, Katsumi, Sasaki, Akira
• Primary Examiner(s): Vu, Bai D
• Application Number:
  US15/060,420
• Publication Number:
  US 20170255667A1
• Time in Patent Office: 1,377 Days
• Field of Search: None
• CPC Class Codes: G06F 16/2291 User-Defined Types; Storage management thereof
• CPC Class Codes: G06F 16/235 Update request formulation
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 50/00 Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism healthcare informatics G16H

Abstract

Methods, systems, and apparatus for information access and response for an occupant in a vehicle. The system includes a communication device connected to a network and coupled to the vehicle. The vehicle includes an internal database for storing multiple contacts in a contact list. The internal database is coupled to an electronic control unit. The electronic control unit is coupled to the communication device and configured to obtain a new contact attribute from a communication, and determine that the new contact attribute belongs to a new contact. The electronic control unit is configured to obtain one or more other contact attributes for the new contact, and generate the new contact. The electronic control unit is configured to store the new contact in the contact list.

Claims

1. An information access and response system for a vehicle, comprising:

a network access device configured to receive a communication from a communication device via a first form of communication;

a memory for storing a plurality of contacts in a contact list;

an electronic control unit (ECU) coupled to the network access device and the memory, the electronic control unit configured to;

extract a contact attribute from the received communication;

determine that the contact attribute matches a contact attribute of a contact in the contact list;

determine that the contact is to receive a reply to the received communication using a second form of communication;

determine that the contact has a second contact attribute that identifies a response destination where the reply is to be sent and that is associated with the second form of communication;

determine that the response destination is available to receive the reply via the second form of communication before sending the reply;

generate the reply to the received communication; and

send the reply to the response destination via the second form of communication.

2. The system of claim 1, wherein the received communication is a calendar, email or invitation and the contact attribute from the received communication is a first name, a last name, a phone number or an email address.

3. The system of claim 1, wherein to generate the reply the ECU is configured to:

receive user input for the reply from a user interface, wherein the user input is text input into the user interface; and

insert the user input into the reply.

4. The system of claim 1, further comprising:

a navigation unit configured to obtain vehicle information including a current location of the vehicle, a vehicle speed, and a destination location,

wherein the ECU is further configured to;

extract from the received communication an expected arrival time, and

determine an estimated arrival time based on the vehicle information,

wherein the ECU determines that the contact is to receive the reply to the received communication when the estimated arrival time is later than the expected arrival time.

5. The system of claim 4, wherein the received communication is a calendar appointment or meeting notice and the expected arrival time is an appointment or meeting time.

6. The system of claim 4, wherein to extract the expected arrival time and the contact attribute the ECU is configured to:

parse the received communication for the expected arrival time and the contact attribute; and

identify the expected arrival time and the contact attribute by matching one or more formats or patterns that indicate a date, a time, a phone number, a first name, a last name, or an email address.

7. The system of claim 6, wherein the one or more formats or patterns are user configurable and set by user input.

8. The system of claim 4, wherein the reply includes a difference between the estimated arrival time and the expected arrival time.

9. The system of claim 1, further comprising:

an external database that is configured to provide a lookup service that identifies one or more response destinations that are available or unavailable;

wherein the electronic control unit is configured to determine that the response destination is available to receive the reply via the second form of communication using the lookup service.

10. A vehicle comprising:

a network access device configured to receive a communication from a personal device via a first form of communication;

a vehicle speed sensor configured to detect vehicle speed data;

a memory configured to store a plurality of contacts in a contact list;

a navigation unit configured to obtain a current location of the vehicle; and

an electronic control unit (ECU) connected to the navigation unit and configured to;

extract a contract attribute, an expected arrival time and a destination location from the received communication,

determine that the contact attribute matches a contact attribute of a contact in the contact list,

determine an estimated arrival time based on the vehicle speed data, the current location of the vehicle and the destination location,

determine that the estimated arrival time is later than the expected arrival time,

determine that the contact is to receive a reply to the received communication,

determine that the contact has a second contact attribute that identifies a response destination where the reply is to be sent and that is associated with a second form of communication,

determine that the response destination is available to receive the reply via the second form of communication,

generate the reply to the received communication, and

automatically communicate the reply to the response destination using the second form of communication.

11. The vehicle of claim 10, wherein the received communication is a calendar invitation, an email, an SMS message, or an instant message.

12. The vehicle of claim 10, wherein the ECU is further configured to:

receive user input for the reply from a user interface, the user input being text input into the user interface, and

insert the user input into the reply.

13. The vehicle of claim 10, wherein the reply includes a difference between the estimated arrival time and the expected arrival time.

14. The vehicle of claim 10, wherein the ECU is further configured to automatically generate the reply based on a template response and at least one of the estimated arrival time, the current location of the vehicle, or a time/distance until arrival.

15. A method for automatically responding to a communication, the method comprising:

obtaining, by a processor and from a memory, a contact list that includes a contact;

obtaining, by the processor, a communication from a personal device via a first form of communication;

extracting, by the processor and from the communication, an expected arrival time and contact information;

determining, by the processor, that the contact information matches a contact attribute of the contact;

determining, by the processor, that the contact is to receive a reply to the received communication;

determining, by the processor, that the contact has a second contact attribute that identifies a response destination where the reply is to be sent and that is associated with a second form of communication;

determining, by the processor, that the response destination is available to receive the reply via the second form of communication;

generating, by the processor, the reply to the received communication; and

sending the reply to the response destination using the second form of communication.

16. The method of claim 15, wherein the reply includes at least one of an estimated time or distance to arrival or a Uniform Resource Locator (URL) that links to map information with a current location of the vehicle.

17. The method of claim 15, wherein the communication is a calendar appointment or meeting notice and the expected arrival time is an appointment or meeting time.

18. The method of claim 15, further comprising calculating a difference between an estimated arrival time and the expected arrival time, and

wherein the reply includes the difference between the estimated arrival time and the expected arrival time.