The present disclosure relates to a method of activating a telematics device, such as by using a health check process.
This section provides background information related to the present disclosure which is not necessarily prior art. Modern automotive vehicles may be equipped with a telematics system, which must be activated prior to the vehicle being sold to a customer. Activating such telematics systems may involve separately verifying operation and readiness of telematics sub-systems of the telematics system, such as a voice guidance system, a message exchange system and a user interface. Manipulation of buttons on a consul or control panel within the interior of a vehicle may be involved. Such manipulation of buttons may be time consuming when a large number of vehicles exist at a single location and/or activation of any telematics subsystem fails during an attempted activation. Activation may take place at a port of vehicle import, a factory parking lot, or a dealer vehicle center, as examples.
This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features. A method of registering a vehicle with a call center of a telematics system may entail turning a key within a vehicle ignition of a vehicle, invoking a call from a telematics control module within the vehicle to a server at a telematics call center, connecting the telematics control module within the vehicle to the server at the telematics service center, exchanging messages between the telematics control module and the telematics service center, inquiring if sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle from the server at the telematics service center was successful, and inquiring if sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle to the server at the telematics service center was successful.
The method may further entail inquiring whether the call was dropped when a negative response is received after inquiring if sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle to the server at the telematics service center was successful. Exchanging messages may entail sending a health check request from the telematics control module within the vehicle to the server at the telematics service center, and receiving a health check confirmation in the telematics control module within the vehicle from the server at the telematics service center. A health check request may be a request for specific types of information from the service center that pertains or relates to the vehicle from which the request came (e.g. if the vehicle needs service, if the vehicle is still an active participant or subscriber to the telematics system and eligible of being used within the telematics system).
The method may further entail confirming that exchanging messages has failed, inquiring if a message fail counter is less than a predetermined number, and when a message fail counter is less than a predetermined number, re-sending the health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving the health check confirmation in the telematics control module within the vehicle from the server at the telematics service center.
As another example, a method of registering a vehicle with a call center of a telematics system may entail turning a key within a vehicle ignition of a vehicle, invoking a call from a telematics control module within the vehicle to a server at a telematics call center, inquiring whether the call from a telematics control module within the vehicle to a server at a telematics call center is connected, determining that the call from a telematics control module within the vehicle to a server at a telematics call center is not connected, and inquiring whether a call failure counter is less than a predetermined number. The method may further entail determining that a call failure counter is less than the predetermined number, increasing the call failure counter by one, and setting a message failure counter to zero. The method may also entail determining that a call failure counter is not less than the predetermined number, and setting the call failure counter to zero.
Still yet, another method of registering a vehicle with a call center of a telematics system may entail turning a key within an ignition of a vehicle, invoking a call (e.g. a cell phone call) from a telematics control module within the vehicle to a server at a telematics call center, connecting the telematics control module within the vehicle to the server at the telematics service center, and exchanging messages between the telematics control module and the telematics service center. Exchanging messages may entail sending a health check request from the telematics control module within the vehicle to the server at the telematics service center, and receiving a health check confirmation in the telematics control module within the vehicle from the server at the telematics service center. A health check request may requests specific types of information from the service center that pertains or relates to the vehicle from which the request came (e.g. if the vehicle needs service, if the vehicle is still an active participant or subscriber to the telematics system and eligible of being used within the telematics system). The method may then further entail inquiring if sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle from the server at the telematics service center was successful, determining that sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle to the server at the telematics service center was successful, inquiring whether the call was not dropped when a positive response to inquiring if sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle to the server at the telematics service center was successful; and inquiring whether a call failure counter is less than a predetermined number, determining that a call failure counter is less than the predetermined number, increasing the call failure counter by one, and setting a message failure counter to zero, determining that a call failure counter is not less than the predetermined number, and setting the call failure counter to zero.
Further areas of applicability will become apparent from the description provided herein. The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
The drawings described herein are for illustrative purposes only of selected embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.
Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings.
Example embodiments will now be described more fully with reference to
A vehicle may be equipped with on-board components to permit full participation of a vehicle occupant in telematics system 12. For instance, with further reference including
Turning now to
If successful contact has been established by telematics control module 35, the logic proceeds to step 46 where message exchange may occur. Message exchange at step 46 may include telematics server 33 responding with specific communication tones, such as phone tones, to telematics control module 35 within vehicle 10, thus establishing message exchange. Thus, step 46 may represent exchanging messages between the telematics control module 35 and the telematics server 33 of telematics service center 32. Exchanging messages may further entail sending a “health check request” from the telematics control module 35 within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle from the server at the telematics service center. A health check request may be a request for specific types of information from the service center that pertain to or relate to a vehicle from which the request came (e.g. if the vehicle needs service, if the vehicle is still an active participant or subscriber to the telematics service and therefore eligible of participating in benefits of a telematics system). Stated slightly differently, a health check request may be a request for specific types of information from the service center that pertains or relates to the vehicle from which the request came (e.g. if the vehicle needs service, if the vehicle is still an active participant or subscriber to the telematics system and eligible of being used within the telematics system.
At step 48, the logic verifies that telematics control module 35, as part of in-vehicle telematics components, has established successful contacts with telematics server 33 of call center 32. Thus, step 48 may represent inquiring if sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle from the server at the telematics service center has been successful. Successful contact occurs when an acceptable series of tones are transmitted from telematics service center 32 to telematics control module 35. If successful contact is verified, the logic proceeds to step 50, where a telematics account for vehicle 10 is deemed to be successfully established. Upon successful establishment of vehicle 10 within a telematics database of telematics server 33, for example, of call center 32, the logic may end at step 52. The logic may then begin again at step 42 for another (i.e. a different vehicle). Registration of multiple vehicles may be conducted simultaneously using the logic of flowchart 40.
At step 44, if telematics control module 35 is unable to establish initial contact with then the logic proceeds to step 54, where the logic inquires if the call fail counter, which monitors the number of call failures from telematics control module 35 of in-vehicle telematics device to telematics server 33 of call center 32, is less than a predetermined number, such as six (6). Thus, step 54 may represent determining that a call failure counter is less than a predetermined number. The call failure counter may begin with zero (0) upon turning of key 29 in ignition 31 when logic of flowchart 40 is executed.
If the call fail counter is less than six (6), then the logic proceeds back to step 42. From step 42 another call from telematics control module 35 of vehicle 10 to telematics server 33 of call center 32 may be initiated. However, at step 54, if the call failure counter is not less than six (6), then the logic proceeds to step 58 where the call failure counter is set to zero (0) and the logic of flowchart 40 is not attempted until another turn of key 29 in ignition 31. Thus, step 58 may represent a determination that a call failure counter is not less than the predetermined number and setting the call failure counter to zero. Thus, a registration process may end at step 60 until another turn of key 29 in ignition 31 occurs.
Continuing with the logic of flowchart 40, after attempting message exchange at step 46, an inquiry into success of such message exchange at step 48 is made. If the reply to success of such an inquiry at step 48 is “no;” that is, an unsuccessful message exchange has occurred, the logic proceeds to step 62 where an inquiry is made as to whether the failure in communication established between the telematics control module 35 and the telematics server 33 was a dropped call. Thus, step 62 may represent inquiring whether the call was dropped when a negative response to inquiring if sending a health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving a health check confirmation in the telematics control module within the vehicle to the server at the telematics service center was successful. Dropping of such a cell phone call from telematics control module 35 of vehicle 10 to call center 32 may be for one or more reasons, such as interference from weather, interference from a building or geographic land features, as examples. If the response to the inquiry at step 62 is “yes,’ indicating that the call has been dropped, then the logic proceeds to step 56 where the call fail counter is increased by one (1) and a message fail counter is set to zero (0). Message fail counter may begin with zero (0), and not one (1), when logic of flowchart 40 is executed. Thus, step 56 may represent increasing the call failure counter by one and setting a message failure counter to zero. The logic may then proceed to step 54, which has been previously discussed. If the response to the inquiry at step 62 is “no,” indicating that the call has not been dropped, then the logic proceeds to step 64, where the logic determines that the call has not been dropped, but rather the message exchange has failed. At step 64 the message fail counter may be increased by one (1). Thus, step 64 may represent confirming that exchanging messages has failed and increasing the message fail counter by one (1). The logic may then proceed to step 66 where an inquiry is made if the message fail counter is less than three (3). Thus, step 66 may represent inquiring if a message fail counter is less than a predetermined number. If the message fail counter is not less than three (3), then the logic proceeds to step 56, which has been previously explained above; however, if the message fail counter is less than three (3), then the logic proceeds to step 68 and an attempt at message resend is made. In other words, step 68 may represent when a message fail counter is less than a predetermined number, re-sending the health check request from the telematics control module within the vehicle to the server at the telematics service center and receiving the health check confirmation in the telematics control module within the vehicle from the server at the telematics service center. The logic may then proceed to step 48 and any subsequent steps, which have been explained above.
The foregoing description of the embodiments has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the invention, and all such modifications are intended to be included within the scope of the invention.
Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those who are skilled in the art. Numerous specific details are set forth such as examples of specific components, devices, and methods, to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms and that neither should be construed to limit the scope of the disclosure. In some example embodiments, well-known processes, well-known device structures, and well-known technologies are not described in detail. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.
Number | Name | Date | Kind |
---|---|---|---|
6728612 | Carver et al. | Apr 2004 | B1 |
6947755 | Gould et al. | Sep 2005 | B1 |
7310521 | Laghrari | Dec 2007 | B2 |
7336943 | Crocker et al. | Feb 2008 | B2 |
20050130670 | Gould et al. | Jun 2005 | A1 |
20050186941 | Gault et al. | Aug 2005 | A1 |
20060079203 | Nicolini | Apr 2006 | A1 |
20070100519 | Engel | May 2007 | A1 |
20080027605 | Oesterling | Jan 2008 | A1 |
20080046149 | Breed | Feb 2008 | A1 |
20080147265 | Breed | Jun 2008 | A1 |
20080161989 | Breed | Jul 2008 | A1 |
20090292417 | Ishikawa | Nov 2009 | A1 |
Number | Date | Country | |
---|---|---|---|
20110208386 A1 | Aug 2011 | US |