Actionable event determination based on vehicle diagnostic data

Patent metadata

Field	Value
Publication number	US-11734968-B2
Application number	US-202117564383-A
Country	US
Kind code	B2
Filing date	Dec 29, 2021
Priority date	Oct 3, 2017
Publication date	Aug 22, 2023
Grant date	Aug 22, 2023

Abstract

The present disclosure is generally related to systems and methods for determining an actionable event associated with a vehicle. The systems and methods can determine the event based on vehicle diagnostic data, and can report the event to a user via an appropriate interface. The systems and methods can also determine a recommended action to address the event, and can facilitate completion of the action upon approval by the user.

First claim

What is claimed:

1. A vehicle diagnostic method implemented by one or more processors, the method comprising:
receiving, via an interface of a data processing system installed in a vehicle, vehicle diagnostic data sensed by at least one of a plurality of sensors associated with the vehicle;
identifying, based on an analysis of the vehicle diagnostic data, a trigger event associated with the vehicle,
determining a priority level associated with the trigger event;
generating an event data message corresponding to the trigger event, the event data message formatted as output compatible with a given output interface;
determining, based on the priority level associated with the trigger event, a notification time associated with the event data message; and
in response to determining that a current time corresponds to the notification time associated with the event data message:
transmitting the event data message to the given output interface to cause the output interface to output information associated with the event data message as an interface output.

2. The method of claim 1 , wherein determining the notification time associated with the event data message based on the priority level associated with the trigger event comprises:
in response to determining that the priority level associated with the trigger event corresponds to an urgent trigger event:
determining the notification time associated with the event data message is a first time.

3. The method of claim 2 , in response to determining that the priority level associated with the trigger event corresponds to an urgent trigger event, further comprising:
selecting a first output interface as the given output interface to output the information associated with the event data message.

4. The method of claim 3 , wherein determining the notification time associated with the event data message based on the priority level associated with the trigger event comprises:
in response to determining that the priority level associated with the trigger event corresponds to a non-urgent trigger event:
determining the notification time associated with the event data message is a second time that is subsequent to the first time.

5. The method of claim 4 , in response to determining that the priority level associated with the trigger event corresponds to a non-urgent trigger event, further comprising:
selecting a second output interface as the given output interface to output the information associated with the event data message, wherein the second output interface differs from the first output interface.

6. The method of claim 5 , wherein the first output interface comprises an audio-based or text-based interface of the vehicle, and wherein the second output interface comprises an audio-based or text-based interface of a mobile computing device presented.

7. The method of claim 1 , wherein identifying the trigger event associated with the vehicle comprises:
analyzing the vehicle diagnostic data to predict a future maintenance activity of the vehicle, and
associating the future maintenance activity with the trigger event associated with the vehicle.

8. The method of claim 1 , wherein identifying the trigger event associated with the vehicle comprises:
analyzing the vehicle diagnostic data to determine a vehicular state of the vehicle;
continuously monitoring the vehicle diagnostic data to determine a state change of the vehicular state of the vehicle; and
associating the state change of the vehicular state of the vehicle with the trigger event associated with the vehicle.

9. The system of claim 1 , further comprising:
determining a recommended action associated with the trigger event, wherein the information associated with the event data message includes the recommended action.

10. The method of claim 9 , wherein the recommended action includes a recommendation to schedule a maintenance appointment for the vehicle.

11. The method of claim 10 , further comprising:
determining, based on calendar information of at least a user associated with the vehicle, a recommended time and/or day to schedule the maintenance appointment for the vehicle, wherein the recommended action further includes the recommended time and/or day to schedule the maintenance appointment for the vehicle.

12. A vehicle diagnostic system operational in a vehicular environment, the vehicle diagnostic system comprising:
at least one processor; and
memory storing instructions that, when executed, cause the at least one processor to:
receive, via an interface of a data processing system installed in a vehicle,

vehicle diagnostic data sensed by at least one of a plurality of sensors associated with the vehicle;
identify, based on an analysis of the vehicle diagnostic data, a trigger event associated with the vehicle,
determine a priority level associated with the trigger event;
generate an event data message corresponding to the trigger event, the event data message formatted as output compatible with a given output interface;
determine, based on the priority level associated with the trigger event, a notification time associated with the event data message; and
in response to determining that a current time corresponds to the notification time associated with the event data message:
transmit the event data message to the given output interface to cause the output interface to output information associated with the event data message as an interface output.

13. The system of claim 12 , wherein the instructions to determine the notification time associated with the event data message based on the priority level associated with the trigger event comprise instructions to:
in response to determining that the priority level associated with the trigger event corresponds to an urgent trigger event:
determine the notification time associated with the event data message is a first time.

14. The system of claim 13 , in response to determining that the priority level associated with the trigger event corresponds to an urgent trigger event, wherein the instructions further cause the at least one processor to:
select a first output interface as the given output interface to output the information associated with the event data message.

15. The system of claim 14 , wherein the instructions to determine the notification time associated with the event data message based on the priority level associated with the trigger event comprise instructions to:
in response to determining that the priority level associated with the trigger event corresponds to a non-urgent trigger event:
determine the notification time associated with the event data message is a second time that is subsequent to the first time.

16. The system of claim 15 , in response to determining that the priority level associated with the trigger event corresponds to a non-urgent trigger event, wherein the instructions further cause the at least one processor to:
select a second output interface as the given output interface to output the information associated with the event data message, wherein the second output interface differs from the first output interface.

17. The system of claim 16 , wherein the first output interface comprises an audio-based or text-based interface of the vehicle, and wherein the second output interface comprises an audio-based or text-based interface of a mobile computing device presented.

18. A non-transitory computer-readable storage medium storing instructions that, when executed, cause at least one processor to perform veh

Assignees

• Google Llc

Inventors

• Ramic Haris

Classifications

• G06F3/165 Primary

  Management of the audio stream, e.g. setting of volume, audio stream path · CPC title

• G06F3/167 Primary

  Audio in a user interface, e.g. using voice commands for navigating, audio feedback · CPC title

• G07C5/08 Primary

  Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time · CPC title

• G07C5/0808

  Diagnosing performance data (testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005) · CPC title

• G07C5/0833 Primary

  using audio means · CPC title