CLOUD-BASED CONNECTIVITY ENERGY BUDGET MANAGER

• US 20180357838A1
• Filed: 06/12/2017
• Published: 12/13/2018
• Est. Priority Date: 06/12/2017
• Status: Active Grant

• Current Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Original Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Inventors: ROBERTS, David Randolph, STANKO, Robert, ROCKWELL, Mark Anthony, ROCCI, Benjamin M., KROZAL, Christian
• Granted Patent: US 10,510,194 B2
• Time in Patent Office: Days
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/0808 Diagnosing performance data testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005
• CPC Class Codes: G07C 5/0841 Registering performance data recording measured values G01D; information storage G11B
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

A storage maintains energy estimates corresponding to function requests for vehicles. A processor of a server is programmed to receive a function request for a vehicle, and direct the vehicle to perform the function request responsive to determining, according to battery information received from the vehicle and an energy estimate corresponding to the function request, that the vehicle has sufficient energy to perform the function request.

Claims

1. A system comprising:

a storage configured to maintain diagnostic data, cadence trigger criteria defining a periodic transmission of the diagnostic data, and priority trigger criteria defining out-of-cadence transmission of the diagnostic data; and

a processor programmed to

periodically send diagnostic data accumulated since a previous cadence transmission to a remote server per the cadence trigger criteria, and

send out-of-cadence diagnostic data meeting the priority trigger criteria to the remote server.

2. The system of claim 1 wherein the processor is further programmed to delete the diagnostic data accumulated since a previous cadence responsive to sending of the diagnostic data.

3. The system of claim 1 wherein the cadence trigger criteria specify to periodically send the diagnostic data upon completion of a predefined number of vehicle key cycles.

4. The system of claim 1 wherein the cadence trigger criteria specify to periodically send the diagnostic data upon passage of a predefined number of days.

5. The system of claim 1 wherein the priority trigger criteria specify to send diagnostic data from the storage indicative of ‘

Active’

diagnostic codes as the out-of-cadence diagnostic data.

6. The system of claim 1 wherein the priority trigger criteria specify to send diagnostic data from the storage indicative of ‘

Pending’

diagnostic codes as the out-of-cadence diagnostic data.

7. The system of claim 1 wherein the processor is further programmed to delete the out-of-cadence diagnostic data from the storage to avoid resending the out-of-cadence diagnostic data in a next cadence transmission.

8. A method comprising:

storing, to a telematics controller, diagnostic trouble code (DTC) data received from other controllers via a vehicle bus;

sending, from the telematics controller, DTC data meeting priority trigger criteria to a remote server;

deleting the DTC data sent per the priority trigger criteria;

periodically sending, from the controller, all stored DTC data to the remote server per cadence trigger criteria; and

deleting the DTC data sent per the cadence trigger criteria.

9. The method of claim 8 further comprising setting the cadence trigger criteria to periodically send the diagnostic data upon completion of a predefined number of vehicle key cycles.

10. The method of claim 8 further comprising setting the cadence trigger criteria to periodically send the diagnostic data upon passage of a predefined number of days.

11. The method of claim 8 further comprising setting the priority trigger criteria to send the diagnostic data indicative of ‘

Active’

DTCs.

12. The method of claim 8 further comprising setting the priority trigger criteria to send the diagnostic data indicative of ‘

Pending’

DTCs.

13. A non-transitory computer-readable medium comprising instructions that, when executed by a processor of a telematics controller, cause the telematics controller to:

store diagnostic trouble code (DTC) data received from other controllers via a vehicle bus;

send, from the telematics controller, DTC data meeting priority trigger criteria to a remote server;

delete the DTC data sent per the priority trigger criteria;

periodically send, from the controller, all stored DTC data to a remote server per cadence trigger criteria; and

delete the DTC data sent per the cadence trigger criteria.

14. The medium of claim 13 further comprising instructions to cause the telematics controller to set the cadence trigger criteria to periodically send the diagnostic data upon completion of a predefined number of vehicle key cycles.

15. The medium of claim 13 further comprising instructions to cause the telematics controller to set the cadence trigger criteria to periodically send the diagnostic data upon passage of a predefined number of days.

16. The medium of claim 13 further comprising instructions to cause the telematics controller to set the priority trigger criteria to send the diagnostic data indicative of ‘

Active’

DTCs.

17. The medium of claim 13 further comprising instructions to cause the telematics controller to set the priority trigger criteria to send the diagnostic data indicative of ‘

Pending’

DTCs.