Remote vehicle system configuration, control, and telematics

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/900,804, entitled REMOTE VEHICLE SYSTEM CONFIGURATION CONTROL, AND TELEMATICS, filed November 2020, now allowed; which is a continuation of and claims priority' to U.S. patent application Ser. No. 16/269,321, entitled REMOTE VEHICLE SYSTEM CONFIGURATION, CONTROL, AND TELEMATICS, filed Feb. 6, 2019, now U.S. Pat. No. 10,720,045; which is a continuation of and claims priority to U.S. patent application Ser. No. 15/862,630, entitled REMOTE VEHICLE SYSTEM CONFIGURATION, CONTROL, AND TELEMATICS, filed Jan. 4, 2018, now U.S. Pat. No. 10,249,182, issued Apr. 2, 2019. Each of the above-referenced patent documents is incorporated by reference in its entirety as if fully set forth herein, including Specification, Figures, Claims, and all other matter.

FIELD OF THE DISCLOSURE

This disclosure relates generally to the field of wireless configuring and reconfiguring vehicle control systems, to wireless user control of vehicle systems, and to telematics information exchange between vehicles and remote servers.

BACKGROUND

Vehicle control systems are typically aftermarket electronic systems installed in vehicles for consumers' convenience The functionality provided by such systems may include remote start capability, control of security and convenience features, climate control, and others. Telematics systems include systems that allow monitoring of the vehicle usage and performance, and communicating with the vehicle and the user of the vehicle.

A need in the art exists for improved techniques for initially configuring and later reconfiguring vehicle control systems, for improved techniques for communicating with vehicle control systems, and for improved communication techniques with telematics systems.

SUMMARY

This document describes embodiments, variants, and examples implementing novel techniques for addressing one or more of the needs identified above, and/or other needs. Selected embodiments described in this document include methods, apparatus, and articles of manufacture that enable wireless configuration, reconfiguration, and user control of vehicle systems; and improved connectivity to remote servers.

In an embodiment, a vehicle control system (VCS) for installation in a vehicle includes a processor; an external wireless radio frequency (RF) interface; a memory module comprising non-volatile programmable memory and storing instructions for execution by the processor; an interface to vehicle systems; a remote start module; and a bus coupling the processor to the external wireless RF interface, the memory module, the vehicle systems interface, and the remote start module. The processor is configured to execute the instructions to read vehicle information that identifies the vehicle, to transmit through the external wireless RF interface the vehicle information to a user control and communication device (UCCD) to enable the UCCD to obtain configuration parameters for installation of the VCS in the vehicle, to receive through the external wireless RF interface the configuration parameters from the UCCD, to store the configuration parameters in the non-volatile programmable memory, and to configure the VCS in accordance with the configuration parameters.

In an embodiment, method of operating a vehicle control system (VCS) installed in a vehicle includes: reading vehicle information that identifies the vehicle from a memory of the vehicle; transmitting the vehicle information through an external wireless RF interface of the VCS to a user control and communication device (UCCD) to enable the UCCD to obtain configuration parameters for installation of the VCS in the vehicle; receiving through the external wireless RF interface the configuration parameters from the UCCD; storing the configuration parameters received from the UCCD in a non-volatile programmable memory of the VCS; and configuring the VCS in accordance with the configuration parameters.

In an embodiment, an article of manufacture includes at least one non-volatile machine-readable storage medium with program code stored in the at least one non-volatile machine-readable storage medium. When the program code is executed by a processor of a vehicle control system (VCS) installed in a vehicle, it configures the VCS to read vehicle information that identifies the vehicle from a memory of the vehicle; to transmit the vehicle information through an external wireless RF interface of the VCS to a user control and communication device (UCCD) to enable the UCCD to obtain configuration parameters for installation of the VCS in the vehicle; to receive through the external wireless RF interface the configuration parameters from the UCCD; to store the configuration parameters received from the UCCD in a non-volatile programmable memory of the VCS; and to configure the VCS in accordance with the configuration parameters.

In an embodiment, a mobile communication device stores machine-executable instructions, wherein the instructions configure the mobile communication device to: pair with a vehicle control system (VCS) installed in a vehicle through a radio frequency (RF) link; request vehicle information for configuring the VCS in the vehicle; transmit the vehicle information to a remote server; receive from the remote server information for configuring the VCS for the vehicle; receive from a user of the UCCD responses regarding configuration of the VCS in the vehicle: and transmit to the VCS through the RF link configuration parameters based on the responses and the information regarding configuration of the VCS.

Various features and aspects will he better understood with reference to the following description, drawings, and appended claims (if any).

BRIEF DESCRIPTION OF THE FIGURES

<figref idref="DRAWINGS">FIG. 1</figref> illustrates selected components of a Vehicle Control System in communication with a User Control and Communication Device (such as a smart phone or tablet), configured in accordance with selected aspects described in this document;

<figref idref="DRAWINGS">FIG. 2</figref> illustrates selected steps of a process for configuring the Vehicle Control System for a particular vehicle and features, in accordance with selected aspects described in this document;

<figref idref="DRAWINGS">FIG. 3</figref> illustrates selected steps of a process for changing parameter configuration of the Vehicle Control System, in accordance with selected aspects described in this document; and

<figref idref="DRAWINGS">FIG. 4</figref> illustrates selected steps of a process for controlling vehicle features through the User Control and Communication Device.

DETAILED DESCRIPTION

The words “embodiment,” “variant,” “example,” and similar words and expressions as used in this document refer to a particular apparatus, process, or article of manufacture, and not necessarily to the same apparatus, process, or article of manufacture. Thus, “one embodiment” (or a similar word/expression) used in one place or context may refer to a particular apparatus, process, or article of manufacture; the same or a similar expression in a different place or context may refer to a different apparatus, process, or article of manufacture. The expression “alternative embodiment” and similar words and phrases are used to indicate one of a number of different possible embodiments, variants, or examples. The number of possible embodiments, variants, or examples is not necessarily limited to two or any other quantity. Characterization of an item as “exemplary” means that the item is used as an example. Such characterization does not necessarily mean that the embodiment, variant, or example is a preferred one; the embodiment, variant, or example may but need not be a currently preferred embodiment, variant, or example. All embodiments, variants, and examples are described for illustration purposes and are not necessarily strictly limiting.

The words “couple,” “connect,” and similar words/expressions with their inflectional morphemes, as well as similar words and phrases, do not necessarily import an immediate or direct connection, but include within their meaning connections through mediate elements.

The expression “processing logic” should be understood as selected steps decision blocks and/or hardware/software/firmware for implementing the selected steps/decision blocks. “Decision block” means a step in which a decision is made based on some condition, and subsequent process flow is selected based on whether the condition is met or not.

Some definitions have been explicitly provided above. Other and further explicit and implicit definitions and clarifications of definitions may be found throughout this document.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates selected components of a vehicle control system (“VCS”) <b>100</b> in communication with a user control and communication device (“UCCD”) <b>150</b> and a remote server (“RS”) <b>180</b>. The VCS <b>100</b> may be for example, a remote start system (such as remote start systems of Directed Electronics, Inc.). The UCCD <b>150</b> may be for example, a portable handheld communication device such as a smartphone, a tablet, and a personal digital assistant; a computer such as laptop computer and a desktop computer. The “user” of the UCCD <b>150</b> may be the user of the vehicle, and/or the installer who installs/configures/re-configures the VCS <b>100</b> in the vehicle. The UCCD may execute an application (“app”) for communicating with the VCS <b>100</b> and the RS <b>180</b>. The application may be for allowing the user of the vehicle to control the vehicle, and/or to allow an installer to install/initialize/configure/re-configure the VCS <b>100</b>. The RS <b>180</b> may be, for example, a cloud-based system; it may be configured to receive and analyze telematics data and provide functionality responsive to the telematics data, such as service reminders and warnings regarding the state of the vehicle.

The VCS <b>100</b> includes a bus <b>105</b> that provides communication/networking capability between and among the components of the VCS <b>100</b>. The bus <b>105</b> may be, for example, a bus in accordance with one of the Controller Area Network standards, aka “CAN bus”; or a processor-based system bus.

The VCS <b>100</b> includes a processing module <b>107</b>, for example, a microprocessor and supporting electronics. The VCS <b>100</b> also includes a memory module <b>109</b> that can store instructions executable by the processing module <b>107</b>; the memory module <b>109</b> may include one or more memories of same or different types, such as ROMs, PROMs, EPROMS, EEPROMS, flash memories, optical disks, magnetic storage devices, and/or other memories. In embodiments, the memory module <b>109</b> includes at least some programmable, non-volatile memory.

The VCS <b>100</b> also includes an interface or interfaces <b>110</b> to vehicle control modules, for example, the following: an engine computer (engine control module or LCM); a transmission computer (transmission control module or TCM); built-in vehicle firmware; built-in security features of the vehicle: a telematics module and data storage for data that includes the vehicle's usage and performance data, such as OBD II data (which data storage may instead be included in a telematics module.

The VCS <b>100</b> also includes a remote start module <b>115</b>, which allows starting of the vehicle by the VCS <b>100</b>, in response to appropriate commands, for example, remote start commands received from a user of the UCCD <b>150</b>, The remote start module <b>115</b> may also interact with the vehicle control modules through the interfaces <b>110</b>, which the remote start module <b>115</b> may access through the bus <b>105</b>.

The VCS <b>100</b> additionally includes add-on security module <b>120</b>. which may connect to and monitor various sensors (e.g., shock/vibration, proximity, intrusion), and which may operate and/or control various convenience features (e.g., power windows, power locks, power seats, steering wheel telescoping and tilt positions, audio system presets and other audio system controls).

The VCS <b>100</b> further includes an external communication interface <b>125</b>, which can be, for example, a Bluetooth interface. The interface <b>125</b> can provide communications between the UCCD <b>150</b> and the various components of the VCS <b>100</b> the remote start module <b>115</b>, the interfaces <b>110</b> and the devices connected to the interfaces <b>110</b>, the security module <b>120</b>, and other VCS <b>100</b> components). The external communication interface <b>125</b> may also serve as a bridge between the UCCD <b>150</b> and the bus <b>105</b>, and thus enable the UCCD <b>150</b> to communicate with other devices connected to the bus <b>105</b> directly (e.g., the remote start module <b>115</b>, the add-on security module <b>120</b>) and indirectly through the interfaces <b>110</b> (e.g., the engine control module, transmission control module, built-in vehicle firmware, built-in security features of id e vehicle, telematics module, usage and performance data storage).

In embodiments, the interface <b>125</b> may be another type of RF interface that enables vehicle communications to longer distances, for example, 1500 feet or one mile, and even longer distances: the other type of RF interface may operate, for example, on the 900 MHz band. In embodiments, the interface <b>125</b> is a Bluetooth interface, and the VCS <b>100</b> further includes another type of RF interface that enables vehicle communications to longer distances. for example, 1500 feet or one mile, and even longer distances; the other type of RF interface may operate, for example, on the 900 MHz band. In embodiments, the interface <b>125</b> is a Bluetooth interface and further includes the other type of RE interface and/or a cellular interflice that can communicate with the UCCD <b>150</b> and/or the remote server <b>180</b>. In embodiments, however, the VCS <b>100</b> communicates with the RS <b>180</b> via the UCCD <b>150</b>.

If the VCS <b>100</b> is an aftermarket system, it likely needs to he configured to operate properly when installed in a particular vehicle. If the VCS <b>100</b> is an OEM system, it may also need to be configured for the vehicle. <figref idref="DRAWINGS">FIG. 2</figref> illustrates selected steps of a process <b>200</b> for configuring the VCS <b>100</b> for the particular vehicle and selected features of the VCS <b>100</b>.

At flow point <b>201</b>, the VCS <b>100</b> is physically installed in the vehicle and connected to its various systems, such as the power supply; sensors; ECM; TCM; vehicle firmware; built-in security features of the vehicle; telematics module; data storage for data that includes the vehicle's usage and performance data and other telematics data; controls for various convenience features (e.g., power windows, power locks, power seats, steering wheel telescoping and tilt positions, audio system presets and other audio system controls). Power from the vehicle is provided to the VCS <b>100</b>. Additionally, the UCCD <b>150</b> (e.g., a smartphone or tablet) is powered up and is located within such range that it can communicate with the VCS <b>100</b> (e.g., through the external interface <b>125</b>), and executes the installer application provided for the purpose of configuring the VCS <b>100</b> in the vehicle.

In step <b>205</b>, the VCS <b>100</b> is put into a pairing mode with the UCCD <b>150</b>. For example, the ignition of the vehicle can be turned on, and a valet button of the VCS <b>100</b> may be held down fur a predetermined period of time, to cause the VCS <b>100</b> to enter into the pairing mode, such as the Bluetooth pairing mode; the VCS <b>100</b> and/or the UCCD <b>150</b> may signal the user that the pairing has been accomplished. Thus, after the step <b>205</b>, the UCCD <b>150</b> (here, the installer's device) can communicate with the VCS <b>100</b>.

In step <b>210</b>, the VCS <b>100</b> accesses the vehicle's systems (e.g., the ECM/TCM/firmware) to read the information sufficient to configure the functionality of the VCS <b>100</b> for the vehicle. The information typically includes at least the Vehicle Identification Number (“VIN”) or equivalent information from which make, model, year, trim level, and vehicle options can be determined.

In step <b>215</b>, the VCS <b>100</b> transmits to the UCCD <b>150</b> the information read in the previous step.

In step <b>220</b>, the UCCD <b>150</b> communicates with the remote server (or one of the remote servers) <b>180</b> to obtain access to the database from which the make/model/trim/options and/or other information pertinent to the configuration of the VCS <b>100</b> is determined, based on the information from the step <b>210</b>. The database may be a proprietary one, accessible only with appropriate authorization or credentials. After the installer's log-in (verifying the authorization/credentials), the remote server <b>180</b> reads the vehicle's information from the UCCD <b>150</b> and responds to the UCCD <b>150</b> with the information needed to configure the VCS <b>100</b> for the vehicle; the information may include identification of the correct firmware for the vehicle, and/or the correct firmware itself.

In step <b>225</b>, the installer's app running on the UCCD <b>150</b> guides the installer in configuring the VCS <b>100</b>, based oil the information received from the remote server <b>180</b>. The installer may be presented with choices and requests for information and for selections. The installer's responses may be stored on the UCCD <b>150</b>.

In step <b>230</b>, the installer's app executing on the UCCD <b>150</b> sends the installer's responses and/or appropriate information derived from the responses and the information obtained from the RS <b>180</b> database (the configuration parameters) to the VCS <b>100</b>.

In step <b>235</b>, the VCS <b>100</b> stores the configuration parameters of the VCS <b>100</b> in a memory of the VCS <b>100</b>, such as the non-volatile memory of the memory module <b>109</b>.

In step <b>240</b>, the VCS <b>100</b> configures itself for the vehicle, based on the configuration parameters. In this step, the VCS <b>100</b> may also write information into the vehicle's firmware or other systems, to complete the matchup between the VCS <b>100</b> and the vehicle.

The process may then terminate at flow point <b>299</b>.

The user of the vehicle and/or the installer may wish to change some of the configuration parameters at a later time, that is, after the initial installation. This might he the case, for example, if the user decides to purchase additional Femmes of the VCS <b>100</b> or related services, to add accessories, to increase runtime for remote start, or for other reasons. The process for re-installing the VCS <b>100</b> or changing the configuration parameters may be quite similar to the process <b>200</b> for initially configuring the VCS <b>100</b>. <figref idref="DRAWINGS">FIG. 3</figref> illustrates selected steps of a process <b>300</b> for changing the parameter configuration. The process <b>300</b> may use the installer's app or the end-user's app (the app of the user of the vehicle) executing on the UCD <b>100</b>, if the end-user's app includes the appropriate functionality. To summarize, the VCS <b>100</b> and the UCCD <b>150</b> are put into a pairing mode (step <b>305</b>), the app guides the end-user or the installer in re-configuring the VCS <b>100</b> (step <b>310</b>), by presenting choices and requests for information and for selections. The end-user's or the installer's responses are stored on the UCCD <b>150</b>. The UCCD <b>150</b> verifies the validity/permission for the new parameters with the remote server <b>180</b> (step <b>315</b>, for example, verifying authorization for addition of new features/services or deletion of old ones). If verified (decision block <b>320</b>), the UCCD <b>150</b> transmits the new configuration parameters to the VCS <b>100</b> (step <b>325</b>); if not verified, the process ends (flow point <b>399</b>), to be repeated as needed or desired. When the VCS <b>100</b> receives the new configuration parameters sent in the step <b>325</b>, the VCS <b>100</b> stores the changed parameters in the non-volatile memory of the memory module <b>109</b> (step <b>330</b>), and re-configures itself and possibly also the vehicle based on the changed parameters (step <b>335</b>). The process then terminates in the flow point <b>399</b>, to be repeated as needed or desired.

Note that in the process <b>300</b> there is no need to obtain the vehicle information from the database of the remote server <b>180</b>, because the vehicle information is known from the time of the initial information. But in embodiments, the process also obtains the vehicle information and uses it as in the process <b>200</b>.

Once the VCS <b>100</b> is installed and configured, the end-user can control the vehicle using the end-user's UCCD <b>150</b>, running an end-user application. The end-user app, once opened, may automatically pair with the VCS <b>100</b>, through the Bluetooth or similar transceiver on the UCCD <b>150</b> and the external interface <b>125</b> of the VCS <b>100</b>; the app may then display a command interface that allows the end-user to input commands, which the app transmits to the VCS <b>100</b>. The commands may include controls of the security features of the vehicle (e.g., turn the security system on/off, clear an alarm), convenience features such as the remote start and temperature control, lights flashing and horn on/off, location interrogate (for receiving the vehicle's position at the UCCD <b>150</b>, and others. <figref idref="DRAWINGS">FIG. 4</figref> illustrates selected steps of a process <b>400</b> for controlling the vehicle features through the UCCD <b>150</b> app and the VCS <b>100</b>.

At flow point <b>401</b>, the VCS <b>100</b> is installed in the vehicle, configured (e.g., through the process <b>200</b>)), and powered up (as it would typically be regardless of the presence or position of the vehicle's key). Additionally, the VCS <b>100</b> is connected to the UCCD <b>150</b> through the external interface <b>125</b> (or one or more of the interfaces <b>125</b>); and the end-user app is available on the powered up UCCD <b>150</b>, which is within communication range of the VCS <b>100</b>. Note that the communication range may include any cellular service accessible location, when the interface <b>125</b> is or includes a cellular interface that can communicate with the UCCD <b>150</b>.

In step <b>405</b>, the user activates the app on the UCCD <b>150</b>, for example, by tapping on the app's icon.

In step <b>410</b>, the app establishes a communication link (such as a cellular link, a Bluetooth another RF link) with the interface <b>125</b> of the VCS <b>100</b>. This may be done automatically upon activation of the app, or require some deliberate action of the end-user.

In step <b>415</b>, the user issues a command from the app/UCCD <b>150</b>, for example, by tapping on a particular icon of the app. In response, the app sends a corresponding signal to the VCS <b>100</b>. The signal corresponds to the icon and may instruct the VCS <b>100</b>, for example, to start the vehicle remotely, to turn on the climate control system of the vehicle and/or set the temperature of the climate control system, to activate the horn and/or siren, to flash headlights, to lock/unlock the vehicle's doors, to activate panic mode of the vehicle, and to perform any other function for which the vehicle and the VCS <b>100</b> are configured; these, of course, are just examples of the available functionalities.

In stop <b>420</b> the VCS <b>100</b> receives the command.

In step <b>425</b>, the VCS <b>100</b> performs the function corresponding to the command.

In step <b>430</b>, the VCS <b>100</b> sends to the UCCD <b>150</b> an acknowledgement of the performance of the command.

At flow point <b>499</b> the process terminates, to be repeated as needed or desired.

The presence of the communication link between the VCS <b>100</b> and the UCCD <b>150</b> with the end-user app allows the VCS <b>150</b> to communicate with the remote server <b>180</b>, for example, transmitting to the remote server <b>180</b> telematics data and receiving data and firmware updates from the remote server <b>180</b>. Thus, in operation, the end-user app may run on the UCCD <b>150</b>, at least occasionally (e.g., continuously, continually, at predetermined times or intervals, at random times), establishing the RF link (such as the Bluetooth link or 900 MHz link) with the VCS <b>100</b>. When the link is established, the VCS <b>100</b> may transmit to the app/UCCD <b>150</b> telematics and/or other data, for subsequent transmission from the app/UCCD <b>150</b> to the remote server <b>180</b>; and the app/UCCD <b>150</b> may transmit to the VCS <b>100</b> data and/or firmware updates and or interrogation request from the remote server <b>180</b>.

The features described throughout this document may he present individually, or in any combination or permutation, except where the presence or absence of specific features (elements/limitations) is inherently required, explicitly indicated, or otherwise made clear from the description. This applies whether or not features appear related to specific embodiments.

Although the process steps and decisions (if decision blocks are present) may be described serially in this document, certain steps and/or decisions may he performed by same and/or separate elements in conjunction or in parallel, asynchronously or synchronously, in a pipelined manner, or otherwise. There is no particular requirement that the steps and decisions be performed in the same order in which this description lists them or the Figures show them, except where a specific order is inherently required, explicitly indicated, or is otherwise made clear from the context. Furthermore, not every illustrated step and decision block may be required in every embodiment in accordance with the concepts described in this document, while some steps and decision blocks that have not been specifically illustrated may be desirable or necessary in some embodiments in accordance with the concepts. It should be noted, however, that specific embodiments/variants/examples use the particular order(s) in which the steps and decisions (if applicable) are shown and/or described.

The instructions (machine executable code) corresponding to the method steps of the embodiments, variants, and examples disclosed in this document may be embodied directly in hardware, in software, in firmware, or in combinations thereof. A software module may be stored in volatile memory, flash memory, Read Only Memory (ROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), hard disk, a CD-ROM, a DVD-ROM, or other form of non-transitory storage medium known in the art. Exemplary storage medium or media may he coupled to one or more processors so that the one or more processors can read information from, and write information to, the storage medium or media. In an alternative, the storage medium or media may be integral to one or more processors.

This document describes in detail the inventive apparatus, methods, and articles of manufacture for configuring/reconfiguring and using a vehicle control system. This was done for illustration purposes and, therefore, the foregoing description is not necessarily intended to limit the spirit and scope of the invention(s) described. Neither the specific embodiments of the invention(s) as a whole, nor those of its (or their, as the case may be) features necessarily limit the general principles underlying the invention(s). The specific features described herein may be used in some embodiments, but not in others, without departure from the spirit and scope of the invention(s) as set forth herein. Various physical arrangements of components and various step sequences also fall within the intended scope of the invention(s). Many additional modifications are intended in the foregoing disclosure, and it will be appreciated by those of ordinary skill in the pertinent art that in some instances some features will be employed in the absence of a corresponding use of other features. The embodiments described above are illustrative and not necessarily limiting, although they or their selected features may be limiting for some claims. The illustrative examples therefore do not necessarily define the metes and bounds of the invention(s) and the legal protection afforded the invention(s).