Method and system for vehicle software configuration update management

• US 20050216902A1
• Filed: 03/23/2004
• Published: 09/29/2005
• Est. Priority Date: 03/23/2004
• Status: Abandoned Application

• Current Assignee: General Motors LLC (General Motors Company)
• Original Assignee: General Motors Corporation (General Motors Company)
• Inventors: Schaefer, Mark S.
• Application Number:
  US10/806,868
• Publication Number:
  US 20050216902A1
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/61 Installation

Abstract

The present invention provides a system and method of managing a software configuration update of a vehicle. A first software module is identified and vehicle configuration data representative of a first vehicle software configuration is retrieved. A determination is made whether the first software module is compatible with the first vehicle software configuration at a call center. A second vehicle software configuration is sent from the call center to a 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 update of the vehicle.

Claims

1. A method of managing a software configuration update of a vehicle, the method comprising:

identifying a first software module;

retrieving a vehicle configuration data representative of a first vehicle software configuration;

determining whether the first software module is compatible with the first vehicle software configuration at a call center; and

sending a second vehicle software configuration from the call center to a telematics unit via a wireless network based on the determination.

2. The method of claim 1, wherein identifying the first software module comprises identifying the first software module responsive to a trigger event.

3. The method of claim 2, wherein the trigger event is one of a software request flag generated by the telematics unit or a software install flag generated by the telematics unit.

4. The method of claim 1, wherein retrieving the vehicle configuration data comprises one of retrieving the vehicle configuration data from the telematics unit or retrieving the vehicle configuration data from a call center database.

5. The method of claim 1, wherein determining whether the first software module is compatible with the first vehicle software configuration comprises:

identifying a second software module associated with the first vehicle software configuration; and

determining whether the first software module is compatible with the second software module.

6. The method of claim 5, wherein sending the second vehicle software configuration comprises sending the first software module from the call center to the telematics unit.

7. The method of claim 5, wherein sending the second vehicle software configuration comprises sending a third software module to the telematics unit wherein the third software module is a different version of the first software module.

8. The method of claim 5, wherein sending the second vehicle software configuration comprises sending a fourth module to the telematics unit wherein the fourth module is a different version of the second module.

9. The method of claim 1, wherein the first software module includes a stub function identifying a software interdependency with a second software module.

10. A computer readable medium storing a computer program for managing a software configuration update of a vehicle, comprising:

computer readable code for identifying a first software module;

computer readable code for retrieving a vehicle configuration data representative of a first vehicle software configuration;

computer readable code for determining whether the first software module is compatible with the first vehicle software configuration at a call center; and

computer readable code for sending a second vehicle software configuration from the call center to a telematics unit via a wireless network based on the determination.

11. The computer readable medium of claim 10, wherein the computer readable code for identifying the first software module comprises computer readable code for identifying the first software module responsive to a trigger event.

12. The computer readable medium of claim 11, further comprising computer readable code for selecting the trigger event from one of a software request flag generated by the telematics unit or a software install flag generated by the telematics unit.

13. The computer readable medium of claim 10 wherein the computer readable code for retrieving the vehicle configuration data comprises computer readable code for one of retrieving the vehicle configuration data from the telematics unit or retrieving the vehicle configuration data from a call center database.

14. The computer readable medium of claim 10, wherein computer readable code for determining whether the first software module is compatible with the first vehicle software configuration comprises:

computer readable code for identifying a second software module associated with the first vehicle software configuration; and

computer readable code for determining whether the first software module is compatible with the second software module.

15. The computer readable medium of claim 14, wherein the computer readable code for sending the second vehicle software configuration comprises computer readable code for sending the first software module from the call center to the telematics unit.

16. The computer readable medium of claim 14, wherein the computer readable code for sending the second vehicle software configuration comprises computer readable code for sending a third software module to the telematics unit wherein the third software module is a different version of the first software module.

17. The computer readable medium of claim 14, wherein the computer readable code for sending the second vehicle software configuration comprises computer readable code for sending a fourth module to the telematics unit wherein the fourth module is a different version of the second module.

18. The computer readable medium of claim 10, further comprising computer readable code for interpreting a stub function of the first software module to identity a software interdependency between the first software module and a second software module.

19. A system for managing a software configuration update of a vehicle, the system comprising:

means for identifying a first software module;

means for retrieving a vehicle configuration data representative of a first vehicle software configuration;

means for determining whether the first software module is compatible with the first vehicle software configuration at a call center; and

sending a second vehicle software configuration from the call center to a telematics unit via a wireless network based on the determination.

20. The system of claim 19, wherein the means for identifying the first software module comprises means for identifying the first software module responsive to a trigger event.

21. The system of claim 20, further comprises means for selecting the trigger event from one of a software request flag generated by the telematics unit or a software install flag generated by the telematics unit.

22. The system of claim 19, wherein the means for retrieving the vehicle configuration data comprises means for one of retrieving the vehicle configuration data from the telematics unit or retrieving the vehicle configuration data from a call center database.

23. The system of claim 19, wherein means for determining whether the first software module is compatible with the first vehicle software configuration comprises:

means for identifying a second software module associated with the first vehicle software configuration; and

means for determining whether the first software module is compatible with the second software module.

24. The system of claim 23, wherein the means for sending the second vehicle software configuration comprises means for sending the first software module from the call center to the telematics unit.

25. The system of claim 23, wherein the means for sending the second vehicle software configuration comprises means for sending a third software module to the telematics unit wherein the third software module is a different version of the first software module.

26. The system of claim 23, wherein the means for sending the second vehicle software configuration comprises means for sending a fourth module to the telematics unit wherein the fourth module is a different version of the second module.

27. The system of claim 19, further comprising means for interpreting a stub function of the first software module to identity a software interdependency between the first software module and a second software module.