IP Library Granted Patent US 9,529,584
Granted Patent B2
US 9,529,584 · App. 14/073,346 · Granted Dec 27, 2016

System and method for preparing vehicle for remote reflash event

Inventor: Russ Eling (LaSalle, CA)
Assignee: GENERAL MOTORS LLC
G06F8/67G06F8/665G07C5/008H04L67/12H04W4/001H04W4/046
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,529,584
App. No.
14/073,346
Granted
Dec 27, 2016
Kind
B2
Abstract

Implementations of the present disclosure contemplate utilizing the communicative connections between a telematics service provider (TSP) and a telematics unit in a vehicle to schedule a remote reflash event, issue instructions to the vehicle to prepare for the remote reflash event, and to administer the remote reflash event. A TSP may determine that the vehicle is presently running software for which an update is desirable. Thereafter, the TSP may transmit instructions to the vehicle to make preparations for the remote reflash event. In some implementations, the instructions may cause the vehicle to obtain a higher level of battery charge during its next drive cycle or charging event in anticipation of the remote reflash event.

Claims (44)

1. A method, implemented at a server operated by a telematics service provider (TSP), for preparing a vehicle equipped with a telematics unit for a remote reflash event, the method comprising:

determining that the vehicle is a candidate for a remote reflash event;

scheduling a remote reflash event for the vehicle; and

transmitting, to the telematics unit, a notification of the scheduled remote reflash event;

wherein the notification of the scheduled remote reflash event operates as an instruction to the vehicle charging system to charge a battery at the vehicle to a pending reflash stored energy level exceeding a default stored energy level, which is specified for the battery when a reflash event is not pending, during a drive cycle that occurs prior to the remote reflash event.

2. The method of claim 1 , the method further comprising:

receiving, at the server, information specifying criteria for a candidate for a remote reflash event; and

receiving, at the server, information indicating characteristics of embedded software installed at the vehicle;

wherein the determining that the vehicle is a candidate for a remote reflash event comprises determining, by the server based on the information specifying criteria for a candidate for a remote reflash event and information indicating characteristics of embedded software installed at the vehicle, that the vehicle is a candidate for a remote reflash event.

3. The method of claim 2 , wherein the information specifying criteria for a candidate for a remote reflash event comprises information selected from one of the group consisting of: information identifying a version of embedded software configured to be executed by an electronic control unit (ECU), information identifying a vehicle make, and information identifying a vehicle model.

4. The method of claim 3 , wherein the information identifying the version of embedded software configured to be executed by the ECU is accompanied by information indicating a classification of the version; and

wherein the classification of the version indicates that an original equipment manufacturer considers installation of the version to be one of the group consisting of: mandatory, recommended, or optional.

5. The method of claim 1 , the method further comprising:

determining characteristics of the remote reflash event; and

based on the characteristics of the remote reflash event, calculating the pending reflash stored energy level.

6. The method of claim 5 , wherein the characteristics of the remote reflash event include one of the group consisting of: the amount of data to be transferred to the telematics unit during the remote reflash event, the size of an embedded software file to be transferred to the telematics unit during the remote reflash event, and the amount of electrical power required by the vehicle to execute the remote reflash event.

7. The method of claim 1 , wherein scheduling the remote reflash event comprises allocating wifi bandwidth at a remote reflashing station to the remote reflash event.

8. The method of claim 1 , wherein the notification of the remote reflash event facilitates prompting a user to confirm the remote reflash event and transmission of a confirmation received from the user to the server.

9. The method of claim 1 , wherein scheduling the remote reflash event comprises:

transmitting, to the telematics unit, instructions to prompt a user of the vehicle to indicate a time interval during which the remote reflash event may be administered; and

receiving, from the telematics unit, information indicating a time interval selected by the user.

10. The method of claim 9 , wherein scheduling the remote reflash event further comprises:

transmitting, to the telematics unit, instructions to prompt the user of the vehicle to indicate a location at which the remote reflash event may be administered; and

receiving, from the telematics unit, information indicating a location selected by the user.

11. The method of claim 1 , the method further comprising:

administering the remote reflash event;

wherein data transmitted to the telematics unit during administration of the remote reflash event is transmitted via one of the group consisting of: a WLAN connection, a WPAN connection, and a long-range wireless connection.

12. The method of 11 , the method further comprising:

receiving a confirmation that the remote reflash event has been successfully completed, wherein the confirmation includes a stored energy level of the battery measured subsequent to the completion of the remote reflash event;

determining that the stored energy level of the battery is indicative of one of the group consisting of: the inability to start the vehicle and the inability of the vehicle to complete anticipated travel; and

transmitting a message.

13. A method, implemented at a telematics unit in a vehicle, for preparing the vehicle for a remote reflash event, the method comprising:

receiving a notification of a pending remote reflash event from a server of a telematics service provider wherein the notification of a pending remote reflash event operates as an instruction to the vehicle charging system to charge a battery at the vehicle to a pending reflash stored energy level exceeding a default stored energy level, which is specified for the battery when a reflash event is not pending, during a drive cycle that occurs prior to the remote reflash event; and

charging the battery in accordance with the notification.

14. The method of claim 13 , the method further comprising:

prior to receiving a notification of a pending remote reflash event, receiving a request for information pertaining to software installed at the vehicle and transmitting information pertaining to software installed at the vehicle to the server at the telematics service provider.

15. The method of claim 13 , wherein the pending reflash stored energy level is calculated according to one of the group consisting of: the amount of data to be transferred to the telematics unit during the remote reflash event and the expected amount of electrical power required by the vehicle to execute the remote reflash event.

16. A system for preparing a vehicle for a remote reflash event, the system comprising:

a server operated by a telematics service provider, the server configured to determine that the vehicle is a candidate for a remote reflash event, to schedule the remote reflash event, to transmit a notification of the remote reflash event to the vehicle, and to transmit instructions for preparing for the remote reflash event to the vehicle; and

the vehicle, wherein the vehicle is equipped with a telematics unit configured to receive a notification of the remote reflash event, to receive instructions for preparing for the remote reflash event, and to transmit a confirmation that the remote reflash event has been completed and a post-reflash stored energy level to the server,

wherein the instructions for preparing for the remote reflash event comprise instructions to take action to increase the state of charge of a battery at the vehicle during a drive cycle that occurs prior to the remote reflash event to a pending reflash stored energy level exceeding a default stored energy level specified for the battery when a reflash event is not pending.

17. The system of claim 16 , wherein the server is further configured to determine characteristics of the remote reflash event and based on the characteristics of the remote reflash event, calculate the pending reflash stored energy level.

18. The system of claim 17 , wherein the telematics unit is further configured to transmit a confirmation that the remote reflash event has been completed and a post-reflash stored energy level to the server.

19. The system of claim 18 , wherein the server is further configured to determine whether the post-reflash stored energy level is potentially indicative of an undesirable condition and to transmit a message if the post-reflash stored energy level is potentially indicative of an undesirable condition.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Nov 7, 2014
From: WILMINGTON TRUST COMPANY
To: GENERAL MOTORS LLC
Reel/Frame 034183/0436 →
SECURITY INTEREST Recorded Jun 12, 2014
From: GENERAL MOTORS LLC
To: WILMINGTON TRUST COMPANY
Reel/Frame 033135/0305 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 6, 2013
From: ELING, RUSS
To: GENERAL MOTORS LLC
Reel/Frame 031556/0179 →
Continuity (1)
Related Publication 20150128123A1 · May 7, 2015