System and method for updating vehicle computing platform configuration information

Information

  • Patent Grant
  • 8751104
  • Patent Number
    8,751,104
  • Date Filed
    Wednesday, June 15, 2011
    14 years ago
  • Date Issued
    Tuesday, June 10, 2014
    11 years ago
Abstract
A vehicle includes a computing platform configured with first configuration information, an identification module that receives driver identification information and determines whether to enable the computing platform based on the identification information, and a communication module that establishes communications between the computing platform and an off-vehicle information store storing second configuration information if the computing platform is enabled. The vehicle also includes an update module that updates the computing platform with the second configuration information if the second configuration information is different than the first configuration information.
Description
TECHNICAL FIELD

This disclosure relates to systems and methods for updating vehicle computing platform configuration information.


BACKGROUND

A vehicle may have a computer that communicates with the internet. Sensitive information may reside with the computer. Unauthorized use of the vehicle may lead to unauthorized access of the information.


SUMMARY

First configuration information of a vehicle computing platform may be updated by determining whether to enable the computing platform based on driver identification information, establishing communications between the computing platform and an off-vehicle information store storing second configuration information if the computing platform is enabled, and updating the computing platform with the second configuration information if the second configuration information is different than the first configuration information.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a computer system for a vehicle in accordance with an embodiment of the invention and shows the communicative relationship between a central processor, passive anti-theft system, and ignition system.



FIG. 2 is an illustration of the vehicle, a network, and a remote server for storing configuration information and shows the vehicle communicating default configuration information to the remote server via the network.



FIG. 3 is an illustration of an update terminal, a network, and the remote server and shows updated configuration information being submitted to the remote server via the network, modified by the remote server in accordance with a policy, and returned to the update terminal via the network.



FIG. 4 is an illustration of the vehicle, network, and remote server of FIG. 2 and shows that at vehicle start-up, the vehicle and remote server cooperate to determine whether the remote server has updated configuration information.



FIG. 5 is a perspective view of the dash panel of the vehicle of FIG. 1 and shows a monitor with the updated configuration information.





DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.


In some embodiments, a two level authentication system in which the second level is optional based on customer preference and level of security is provided. An immobilizer transponder, passive keyless entry transponder, or remote keyless entry transmitter may be used to authenticate the holder of a token as a valid user for the system. In addition, an optional pin code may be used for enhanced authentication. Keyboard entry of a pin number may be from radio preset selection buttons or other convenient buttons provided for this or other combined features. Such token/pin authentication enables the appropriate function, features, content, and data for a valid user.



FIG. 1 is a block diagram of integrated system 10 of vehicle 12. Processor 14 provides an occupant of vehicle 12 with a common access point to various vehicle components and data. Processor 14 receives input from wireless keyboard 16, microphone 18, and camera 20. Processor 14 also receives input via display screen 22, e.g., touchscreen, and displays various information via display screen 22. Processor 14 is also connected with the sound system for vehicle 12. The sound system includes audio head unit 24, amplifier 26, and speakers 28. The volume of speakers 28 may be remotely controlled with remote volume switch 30. Processor 14 receives signals via antenna 32 and transmits and receives wireless data via transceiver 34.


Consumer port 36, e.g., USB port, permits an occupant to exchange information with vehicle 12. GPS sensor 38, together with processor 14, determines the current location of vehicle 12.


Car area network 40 is connected with processor 14, speed sensor 42, ignition system 44, and passive anti-theft system 46. Speed sensor 42 determines, in conventional fashion, the speed of vehicle 12. In alternative embodiments, some or all of the elements connected directly with processor 14 may be connected with car area network 40 and thus communicate with processor 14 via car area network 40.


Passive anti-theft system 46 prevents unauthorized use of vehicle 12 and processor 14. As described below, passive anti-theft system 46 may prevent ignition system 44 from starting vehicle 12 and may also prevent the operation of processor 14.


Keys 48, 50 include embedded identifying information 49, 51 respectively. Passive anti-theft system 46 uses identifying information 49, 51 to determine whether keys 48, 50 are associated with vehicle 12 and to distinguish between keys 48, 50.


If key 48 is inserted into key slot 52, key slot 52 senses identifying information 49. Identifying information 49 includes a vehicle identifier, e.g., “Z”, that indicates key 48 is for use with vehicle 12. This vehicle identifier, e.g., “Z”, is shared between keys 48, 50. That is, in this example, identifying information 51 of key 50 will also include the vehicle identifier “Z”. On the basis of the vehicle identifier, passive anti-theft system 46 determines that key 48, or key 50, is for use with vehicle 12. Identifying information 49 also includes a driver identifier, e.g., “4”, that indicates key 48 is different from key 50. This driver identifier, e.g., “4”, is not shared between keys 48, 50. That is, in this example, identifying information 51 of key 50 will include a different driver identifier, e.g., “5”. On the basis of the driver identifier, passive anti-theft system 46 distinguishes between key 48 and key 50 and thus distinguishes between Driver A who normally uses key 48 and Driver B who normally uses key 50. As described below, if processor 14 is informed as to which driver is to drive vehicle 12, processor 14 can check to see if Driver A or Driver B has updated their respective configuration information and, if so, update system 10 with any updated configuration information.


If key 48 is inserted into key slot 52, passive anti-theft system 46 determines that key 48 is associated with a particular driver, e.g., Driver A, and may be used to start ignition system 44. If, instead, key 50 is inserted in key slot 52, passive anti-theft system 46 determines that key 50 is associated with a different particular driver, e.g., Driver B, and may be used to start ignition system 44.


If key 48 is inserted in key slot 52, passive anti-theft system 46 enables processor 14 such that Driver A will have use of processor 14 and access to data on processor 14 specific to Driver A. If, instead, key 50 is inserted in key slot 52, passive anti-theft system 46 enables processor 14 such that Driver B will have use of processor 14 and access to data on processor 14 specific to Driver B.


Identifying information 49, 51 need not be embedded with keys 48, 50. In some embodiments, identifying information 49, 51 may be provided by key fobs or other devices. In some embodiments, additional identifying information may be required prior to enabling ignition system 44 or processor 14. For example, a driver may need to input an additional identifying code via touch display 22.



FIG. 2 is an illustration of vehicle 12, remote location 54, and network 56. During assembly, processor 14 (FIG. 1) is loaded with factory set configuration information 53 which determines, inter alia, the appearance and functionality of display screen 22. Configuration information 53 is uploaded and stored at remote location 54 via network 56. In the example of FIG. 2, configuration information 53 specifies audio channels 1, 2, and 3, a red background, and three (3) buttons for display 22. Configuration information 53 also includes a part number for a component of vehicle 12, e.g., HVAC#: 35X71. As described below, this component information may be used to verify that requested configuration information is directed to an authorized vehicle.



FIG. 3 is an illustration of update terminal 57, remote location 54, and network 56. In the example of FIG. 3, Driver A accesses remote location 54 via network 56 and submits updated configuration information 58 including audio channel, background, and number of button information for display 22. Remote location 54 checks to see whether updated configuration information 58 complies with policy 60 regarding the number of buttons for display 22. In the example of FIG. 3, policy 60 permits a maximum of 5 buttons for display 22. If updated configuration information 58 violates policy 60, remote location 54 will modify updated configuration information 58 such that it complies with policy 60. In the example of FIG. 3, updated configuration information specifies audio channels 3, 5, and 7, a blue background, and twenty-five (25) buttons for display 22. Policy 60, however, limits the number of buttons to five (5). Remote location 54 will modify updated configuration information 58 such that it includes only five (5) buttons. Modified configuration information 62 will be stored at remote location 54 and returned to Driver A via network 56.


In alternative embodiments, remote location 54 may reject updated configuration information 58 if it does not comply with policy 60. As such, remote location 54 is able to control the configuration information associated with processor 14 and display 22.



FIG. 4 is an illustration of vehicle 12, remote location 54, and network 56. Upon the next authorized start-up of vehicle 12 by Driver A, following the process described with respect to FIG. 3, processor 14 will communicate with remote location 54, via wireless access point 34 (FIG. 1), through network 56 to determine whether factory installed configuration information 53 is to be updated. Processor 14 will request from remote location 54 an indicator as to whether the configuration information has changed, and, if so, processor 14 will download modified configuration information 62 and configure processor 14 and display 22 based on modified configuration information 62 during the use of vehicle 12 by Driver A.


In the absence of any update to configuration information 53 by Driver B, upon the next authorized start-up of vehicle 12 by Driver B, processor 14 will reconfigure processor 14 and display 22 based on configuration information 53 during the use of vehicle 12 by Driver B.


In some embodiments, prior to the download of updated configuration information, remote location 54 may request the part number of a vehicle component, e.g., HVAC#: 35X71, to confirm that the vehicle requesting the configuration information is authorized to do so. Remote location 54 may compare the received vehicle component number and compare it to that stored and uploaded by the factory. If the numbers match, remote location 54 may allow the download of any updated configuration information to occur. If the numbers do not match, remote location 54 may deny the request to download any updated configuration information.


In some embodiments, driver behavior may be used to determine whether to prevent access or disable some or all of the functionality of system 10. For example, speed sensor 42 may indicate that the vehicle speed exceeds all legal limits, e.g., 100 m.p.h., suggesting unauthorized use of vehicle 12. Under such circumstances, passive anti-theft system may disable some or all of the functionality of processor 14 to protect information residing in processor 14. It is contemplated that other techniques may be used to monitor driver behavior, e.g., frequency of stop and start, intensity of breaking or acceleration, etc.



FIG. 5 is a perspective view of the dash panel of vehicle 12 and shows display 22 with modified configuration information 62, e.g., display unit 22 is shown with audio channels 3, 5, and 7 and five (5) buttons.


While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention.

Claims
  • 1. A vehicle comprising: a computing platform configured with first configuration information;an identification module configured to (i) receive from a token identification information for a driver, (ii) selectively enable the computing platform such that the first configuration information is accessible to the driver based on the identification information, (ii) monitor subsequent driving behavior, and (ii) selectively prevent access to the computing platform, if enabled, based on the driving behavior without disabling the vehicle to protect configuration information on the computing platform;a communication module configured to, if the computing platform is enabled, establish communications between the computing platform and an off-vehicle information store remote from the token storing second configuration information; andan update module configured to update the computing platform with the second configuration information if the second configuration information is different than the first configuration information.
  • 2. A method for updating first configuration information of a vehicle computing platform comprising: receiving from a token identification information for a driver;selectively enabling the computing platform such that the first configuration information is accessible to the driver based on the identification information;establishing communications between the computing platform and an off-vehicle information store remote from the token storing second configuration information if the computing platform is enabled;updating the computing platform with the second configuration information if the second configuration information is different than the first configuration information;monitoring subsequent driving behavior; andselectively preventing access to the computing platform, if enabled, based on the driving behavior without disabling the vehicle to protect configuration information on the computing platform.
  • 3. A method for updating first configuration information of a vehicle computing platform comprising: selectively enabling the computing platform such that the first configuration information is accessible to a driver based on identification information from a token;establishing communications between the computing platform and an off-vehicle information store remote from the token storing second configuration information if the computing platform is enabled;updating the computing platform with the second configuration information if the second configuration information is different than the first configuration information;monitoring subsequent driving behavior; andselectively preventing access to the computing platform, if enabled, based on the driving behavior without disabling the vehicle to protect configuration information on the computing platform.
CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of application Ser. No. 11/742,091, filed Apr. 30, 2007, the contents of which are hereby incorporated by reference.

US Referenced Citations (73)
Number Name Date Kind
4754255 Sanders et al. Jun 1988 A
5525977 Suman Jun 1996 A
5808374 Miller et al. Sep 1998 A
6148212 Park et al. Nov 2000 A
6266589 Boies et al. Jul 2001 B1
6323761 Son Nov 2001 B1
6445084 Daiss et al. Sep 2002 B1
6532298 Cambier et al. Mar 2003 B1
6549115 Daiss et al. Apr 2003 B1
6711474 Treyz et al. Mar 2004 B1
6759943 Lucy et al. Jul 2004 B2
6830123 Ohki et al. Dec 2004 B2
6999858 Walker et al. Feb 2006 B2
7038596 Nakajima May 2006 B2
7085635 Boman et al. Aug 2006 B2
7170400 Cowelchuk et al. Jan 2007 B2
7419027 Bihya Sep 2008 B2
7454545 Kohno et al. Nov 2008 B2
7483772 Oesterling et al. Jan 2009 B2
7564342 Klein Jul 2009 B2
7685162 Heider et al. Mar 2010 B2
7801507 Benco et al. Sep 2010 B2
7979177 Hermann et al. Jul 2011 B2
8050815 Perry et al. Nov 2011 B2
8577548 Miller et al. Nov 2013 B2
20020049538 Knapton et al. Apr 2002 A1
20020096572 Chene et al. Jul 2002 A1
20020135466 Bunyan Sep 2002 A1
20030078709 Yester et al. Apr 2003 A1
20030181822 Victor Sep 2003 A1
20040010358 Oesterling et al. Jan 2004 A1
20040019416 Chen et al. Jan 2004 A1
20040085189 Nagai et al. May 2004 A1
20040092253 Simonds et al. May 2004 A1
20040124968 Inada et al. Jul 2004 A1
20040158373 Nakaya Aug 2004 A1
20040225557 Phelan et al. Nov 2004 A1
20050030184 Victor Feb 2005 A1
20050134477 Ghabra et al. Jun 2005 A1
20050137757 Phelan et al. Jun 2005 A1
20050159853 Takahashi et al. Jul 2005 A1
20050182538 Phelan et al. Aug 2005 A1
20050216144 Baldassa Sep 2005 A1
20050237150 Sun et al. Oct 2005 A1
20050288837 Wiegand et al. Dec 2005 A1
20060001523 Underdahl et al. Jan 2006 A1
20060047419 Diendorf et al. Mar 2006 A1
20060049962 Okada Mar 2006 A1
20060106515 Phelan et al. May 2006 A1
20060111817 Phelan et al. May 2006 A1
20060122749 Phelan et al. Jun 2006 A1
20060195483 Heider et al. Aug 2006 A1
20060200008 Moore-Ede Sep 2006 A1
20060212195 Veith et al. Sep 2006 A1
20070082706 Campbell et al. Apr 2007 A1
20070139170 Higuchi Jun 2007 A1
20070158128 Gratz et al. Jul 2007 A1
20070200663 White et al. Aug 2007 A1
20080077298 Hattori et al. Mar 2008 A1
20080228358 Wang et al. Sep 2008 A1
20080245598 Gratz et al. Oct 2008 A1
20080269979 Hermann et al. Oct 2008 A1
20080319602 McClellan et al. Dec 2008 A1
20090024273 Follmer et al. Jan 2009 A1
20090027177 Hodder Jan 2009 A1
20090030770 Hersh et al. Jan 2009 A1
20090069954 Aladesuyi Mar 2009 A1
20090079555 Aguirre De Carcer et al. Mar 2009 A1
20090082928 Witkowski et al. Mar 2009 A1
20090189736 Hayashi Jul 2009 A1
20090195370 Huffman et al. Aug 2009 A1
20100004818 Phelan Jan 2010 A1
20100161171 Valentine et al. Jun 2010 A1
Related Publications (1)
Number Date Country
20110238237 A1 Sep 2011 US
Continuations (1)
Number Date Country
Parent 11742091 Apr 2007 US
Child 13160797 US