Method for managing vehicle software configuration updates

• US 7,506,309 B2
• Filed: 03/23/2004
• Issued: 03/17/2009
• Est. Priority Date: 03/23/2004
• Status: Active Grant

• Current Assignee: General Motors LLC (General Motors Company)
• Original Assignee: General Motors Corporation (Motors Liquidation Co. GUC Trust)
• Inventors: Schaefer, Mark S.
• Primary Examiner(s): BULLOCK JR, LEWIS ALEXANDER
• Application Number:
  US10/806,920
• Publication Number:
  US 20050216903A1
• Time in Patent Office: 1,820 Days
• Field of Search: 717168-178, 717120-122, 701 29- 36, 455415-420, 702182-184, 702162-164, 707/8.203
• US Class Current: 717/120
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C

Abstract

The present invention provides a system and a method for managing a software configuration of a vehicle. Software configuration update data for a vehicle is requested from a central database from one of a call center or a telematics unit. Vehicle software configuration data representative of a vehicle software configuration is retrieved. A determination is made whether the software configuration update data corresponds with the vehicle software configuration data and a software module is sent from the call center to the telematics unit via a wireless network based on the determination. A computer usable medium with suitable computer program code is employed for managing the software configuration of the vehicle.

Claims

1. A method for remotely updating software stored in a memory device of a vehicle equipped with a telematics unit, the method comprising:

initiating remote communication between a call center and the telematics unit;

uploading from the telematics unit to the call center a vehicle software configuration for the software stored in the memory device;

comparing the vehicle software configuration with a standard stored in the call center; and

downloading via a wireless network from the call center to the telematics unit updated software to replace the software stored in the memory device when the vehicle software configuration differs from the standard stored in the call center.

2. A method as set forth in claim 1 including the step of identifying a trigger event prior to the step of initiating remote communication.

3. The method of claim 2, wherein the trigger event is selected from the group consisting of a predefined time period, an update flag generated by the call center, and a status check flag generated by the vehicle.

4. The method of claim 1, wherein uploading the vehicle software configuration further comprises retrieving vehicle software configuration data from the telematics unit.

5. The method of claim 1, further comprising determining the vehicle software configuration by querying a vehicle component.

6. The method of claim 1, further comprising the step of requesting a listing of software modules for the vehicle and wherein uploading the vehicle software configuration further comprises retrieving a listing of software modules installed in the vehicle.

7. The method of claim 6, wherein comparing the vehicle software configuration with the standard further includes determining whether the listing of software modules for the vehicle matches the listing of modules installed on the vehicle.

8. The method of claim 1, wherein uploading the vehicle software configuration further comprises:

requesting a first vehicle identification tag from the vehicle;

retrieving a second vehicle identification tag from the telematics unit;

determining whether the first vehicle identification tag corresponds with the second vehicle identification tag; and

storing the first vehicle identification tag in the telematics unit if the first vehicle identification tag does not match the second vehicle identification tag.

9. The method of claim 1, wherein the updated software comprises a software identification tag identifying a version of the updated software.