Vehicle total reset

Abstract

Method comprising: Determining that a vehicle (102) is a fleet vehicle (102), including determining a presence of a configuration bit indicating that the vehicle (102) is a fleet vehicle (102); Receiving an indication of a conclusion of a vehicle usage session as a fleet vehicle (102); and resetting, in response to the conclusion about the Vehicle usage session, several user-adjustable vehicle parameters to a default setting.

Description

BACKGROUND

[0001] Many vehicles are equipped with systems that allow customers to customize various aspects of their vehicles. For example, these systems may include systems that allow the user to configure a key to restrict vehicle functionality, e.g., to a maximum speed, audio volume, etc. DE 10 2012 024 635 A1 discloses a method for resetting vehicle settings of a rental vehicle to factory defaults when an unknown driver is detected by a personalization device. US 2010 / 0 036 560 A1 discloses that settings are reset to default values ​​upon return of a rental vehicle. Other systems include interactive display screen(s) that allow the user to load a customized image to be used as a background.Other examples include vehicles equipped with an infotainment system that allows the user to pair personal electronic devices with the vehicle. Data such as a personal contact list, call history, and digital music can be copied from the personal electronic devices. In other examples, a navigation system allows the user to save specific destinations or points of interest and record a history of vehicle locations on a map. Still further examples include vehicle systems that allow the user to save and recall vehicle settings, such as seat and mirror positions or default languages ​​used by the vehicle systems.

[0002] While these systems enhance the end customer's driving experience, they present a unique problem for fleet operators, such as car rental companies. For example, configurable systems for specific vehicles provide amenities for rental customers, but in some cases, a rental customer may load unwanted content into the vehicle. Consequently, future customers may find the vehicle's settings uncomfortable or, in some cases, offensive. For example, if the saved seating position was programmed closest to the steering wheel, future rental customers may find it uncomfortable when entering the vehicle. Additionally, the previous customer may have programmed one of the keys to limit the vehicle's maximum speed or audio volume, or may have loaded objectionable material, such as provocative music or images.

[0003] Although these systems typically allow customers to adjust or reset certain settings, due to the nature of the car rental business, it's not necessarily practical for a rental company to reset the vehicle's settings. Furthermore, implementing a commonly available means of overriding customizable vehicle systems that could inadvertently be used to defeat the system is not ideal.

[0004] Accordingly, there is a need for a vehicle and / or a method that makes it easier for fleet operators, such as rental companies, to quickly and easily reset the vehicle to the original factory settings, for example, when a rental customer returns the vehicle. SUMMARY

[0005] Various example illustrations described herein are directed to a method that may include determining that a vehicle is a fleet vehicle and detecting the presence of a configuration bit indicating that the vehicle is a fleet vehicle. Example methods may further include receiving an indication of a conclusion about a vehicle usage session as a fleet vehicle and, in response to the conclusion about vehicle usage, resetting a plurality of user-adjustable vehicle parameters to a default setting.

[0006] Another example method may include installing a configuration bit in a vehicle indicating that the vehicle is a fleet vehicle and providing a processor to the vehicle. The processor may be configured to reset a plurality of user-adjustable vehicle parameters to a default setting in response to the configuration bit and an indication of a conclusion of vehicle usage associated with the vehicle.

[0007] Example illustrations are also directed to a vehicle including a processor in communication with a plurality of user-adjustable vehicle settings, and a configuration bit stored in the vehicle indicating that the vehicle is a fleet vehicle. The processor may be configured to reset a plurality of user-adjustable vehicle parameters to a default setting in response to at least the configuration bit and an indication of a conclusion of vehicle usage associated with the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Although the claims are not limited to the illustrated embodiments, an appreciation of various aspects is best achieved through a discussion of various examples thereof. Illustrative embodiments will now be shown in more detail with reference to the drawings. Although the drawings represent the embodiments, the drawings are not necessarily to scale, and some features may be exaggerated to better illustrate and explain an innovative aspect of an embodiment. Furthermore, the embodiments described herein are not intended to be exhaustive or otherwise restrictive or limiting to the precise form and configuration shown in the drawings and disclosed in the following detailed description. Example embodiments of the present invention will be described in detail with reference to the drawings as follows. Fig. 1 is a schematic view of an exemplary system for resetting multiple vehicle settings; Fig. 2 is a process flow diagram of an exemplary method for resetting multiple vehicle settings; Fig. 3 is a process flow diagram for another exemplary method for resetting multiple vehicle settings; Fig. 4 is a process flow diagram for a method for resetting multiple vehicle settings according to another exemplary illustration. DETAILED DESCRIPTION

[0009] Now, illustrative embodiments will be shown in more detail with reference to the drawings. Although the drawings represent the embodiments, the drawings are not necessarily to scale, and some features may be exaggerated to better illustrate and explain an innovative aspect of an embodiment. Furthermore, the embodiments described herein are not intended to be exhaustive or otherwise limiting or restricting the precise form and configuration shown in the drawings and disclosed in the following detailed description.

[0010] Now, with reference to Fig. 1 schematically illustrates an example system 100 including a vehicle 102 configured to facilitate activation of a reset operation for the vehicle. The system 100 may generally facilitate a method for car rental companies to quickly and easily restore factory defaults to a vehicle when transferring a vehicle from one customer to another. The system 100 and associated methods, example illustrations, several of which are described further below, may generally include a configuration bit that temporarily identifies the vehicle as a fleet-use vehicle in some context, e.g., as a rental vehicle. In some example illustrations, the configuration bit may include data or information executable on a processor associated with the vehicle, e.g.,a vehicle electronic control unit (ECU) or the like. In other example approaches, a configuration bit may be installed into a vehicle via a key or other removable hardware. When the configuration is active on the vehicle, a unique sequence of inputs is used to restore the factory defaults of major systems of the vehicle. The sequence of inputs is designed to be simple and quick to implement. Additionally, they may also be designed to be intentionally actuated, i.e., designed to be unlikely to be accidentally triggered during normal operation of the vehicle 102. In other example illustrations, the vehicle may be reset using a remote signal generated by a fleet operator, e.g., a car rental company, or by means of a wireless device and / or application.

[0011] In Fig. 1, an exemplary vehicle 102 is illustrated. The vehicle 102 may, for example, be in communication with a call center 122, a database 120, and a mobile rental fleet application 130. The vehicle may be in communication with the call center 122 via one or more mobile communication devices 124 and / or a diagnostic data link 126. The data link 126, in turn, may be in communication with a service tool 128. The call center 122, the database 120, and / or the mobile rental fleet application 130 may be linked to other system components via communication links, including, by way of example only, networks such as Internet Protocol (IP) packet core networks configured to transmit and switch packets sent over the networks. Alternatively or additionally, other network types may be employed.

[0012] The vehicle 102 may generally include a body control module 104, an instrument panel 106, a driver seat module 108, and an auxiliary protocol interface module 110. Other elements of the vehicle 102 may include a lock switch 112a and an unlock switch 112b (which may be provided as a single lock / unlock switch 112), an ignition switch 114a and an associated key or card device 114b, a radio frequency (RF) module 116, and a total reset transmitter 118.

[0013] In the Fig. 2 to 4, exemplary methods and processes that may be used in connection with the vehicle 102 are described in further detail. As in Fig. For example, as shown in Figure 2, the rental company could use vehicle hardware, e.g., the ignition switch 114 and the door lock switch 112, to trigger a total reset. Using the key 114b, the rental company employee can enter a predetermined pattern using the switches 112, 114 within a predetermined period of time. For example, a rental company employee can simply turn the ignition switch 114a from RUN to OFF to RUN to OFF and then LOCK and UNLOCK the vehicle using the lock / unlock switch 112. Each step within the sequence would need to be completed within a specified period of time (e.g., 2 seconds) to trigger a reset.Furthermore, such a pattern as the exemplary approach described here is extremely unlikely to ever be entered inadvertently or accidentally, given the need to operate the ignition switch and the door lock switch in the cooperative manner described.

[0014] In this example approach, the sequence will only trigger a full reset if the FLEET_CONFIG bit is set to "TRUE." The FLEET_CONFIG bit can be set to "TRUE" at the assembly plant and can remain TRUE until one of the following conditions is met: • The vehicle's odometer reaches a predetermined number of miles (e.g., 50,000 miles or any other predetermined limit associated with a fleet's lifetime); • a FLEET_CONFIG bit has been TRUE for a specified period of time (e.g., 12 months or any other predetermined time limit generally associated with an expected period of use for the vehicle 102 in a fleet, such as a rental fleet); • a maintenance tool sets the FLEET_CONFIG bit to FALSE (Note: in an example approach, a maintenance tool may not set the FLEET_CONFIG bit to TRUE to protect the integrity of the system and prevent inadvertent or malicious installation of the FLEET_CONFIG bit); • A call center that maintains a database of rental vehicles and remotely transmits a signal to the vehicle. A wireless interface can be either cellular, Wi-Fi, or Bluetooth, for example. The cellular signal could be generated by a mobile application on a smartphone.

[0015] The above conditions may generally be associated with the conclusion about the use of a vehicle in a fleet. Other factors or conditions may be employed alternatively or in addition to those described above. Accordingly, one or more of the above factors, or any other factors, may be used to determine a conclusion about a vehicle usage session as a fleet vehicle. As described further below, in response to at least the conclusion about vehicle usage, several user-adjustable vehicle parameters may generally be reset to a default setting.Furthermore, in some example approaches, additional signals or inputs may be used in combination with the above conditions such that simply expiring the conditions does not automatically reset the vehicle, but rather places the vehicle 102 in a condition where a total reset command can be initiated.

[0016] In Fig. 2, an exemplary process 200 of initiating a total reset using a vehicle control pattern will now be described in further detail. The process 200 may generally begin at block 202, where the process 200 queries whether a fleet configuration bit related to the vehicle 102, e.g., the aforementioned FLEET_CONFIG bit, is present. If the configuration bit is not present, the process 200 proceeds to block 204. At block 204, the process 200 determines that the vehicle 102 will have default functionality. More specifically, default functionality may generally permit selective or remote resetting of various vehicle parameters.

[0017] Where process 200 determines that a fleet configuration bit is present at block 202, process 200 proceeds to block 206. At block 206, process 200 asks if a clear fleet configuration request is present. For example, the clear fleet configuration request may be present if a user or administrator has decided to deactivate a fleet status of vehicle 102. In such a case, process 200 may proceed to block 208. At block 208, process 200 sets a fleet configuration status of vehicle 102 to false. In other words, block 208 generally resets the status of vehicle 102; it is no longer considered a "fleet" vehicle, and selective / remote resetting of vehicle parameters is no longer permitted.

[0018] Where the process 200 determines at block 206 that a delete fleet configuration request is not present, the process 200 proceeds to block 210. At block 210, the process 200 asks whether an odometer reading associated with the vehicle 102 exceeds a predetermined amount x. For example, the vehicle 102 may initially be set to a predetermined amount x, and a fleet vehicle beyond such an odometer reading is expected to no longer be used in fleet service. If the odometer reading exceeds the predetermined value x, the process 200 returns to block 208. Alternatively, if the odometer reading of the vehicle 102 is still below a predetermined fleet service threshold x, the process 200 proceeds to block 212. At block 212, the process 200 asks whether an elapsed time associated with the vehicle 102, e.g., an expected fleet service interval, has expired.If the predetermined elapsed time has exceeded y, the process 200 returns to block 208. If the elapsed time associated with the vehicle 102 is still below a predetermined expected fleet deployment threshold y, the process 200 may proceed to block 214.

[0019] Beginning with block 214, one or more vehicle switches or buttons may be used to initiate a vehicle control pattern configured to initiate a total reset of the vehicle 102. In the example below, an example vehicle control pattern is entered using only a door lock / unlock switch 112 and an ignition switch 114, although any other vehicle buttons or controls that are advantageous may be employed. In one example approach, at block 214, the process 200 asks whether the ignition switch of the vehicle 102 is in a run or off position. If the ignition switch is in the off position, the process 200 proceeds to block 220, where a timer is reset to zero and started. Proceeding to block 222, the process 200 asks whether a predetermined period of time measured by the timer, beginning at block 220, has expired.Block 222 therefore generally directs process 200 back to block 218 where the reset timer is cleared and then exits if the timer associated with the ignition switch detection has expired.

[0020] Alternatively, if the timer has not expired, the process 200 proceeds to block 224, where the process 200 asks if a first flag is present. If a first flag has been established, e.g., as described below at block 234, the process 200 proceeds to block 226, where the process 200 asks if the vehicle has been locked. If the flag is not present at block 224, the process 200 proceeds to block 228, where the process 200 asks if the ignition switch has been moved from off to running. If the ignition switch has been turned from off to running at block 228, the process 200 proceeds to block 234, where the first flag is set.

[0021] The process 200 may then proceed from block 234 to block 236, where the timer initially set at block 220 is reset. If the vehicle has been locked, the process 200 proceeds at block 226 to block 230, where the timer is restarted and reset. The process 200 may then proceed to question block 232, which asks if a predetermined time associated with the process 200 has expired. If the predetermined time period has expired, the process 200 returns to block 218, and the process 200 then exits. Alternatively, if the timer has not expired at block 232, the process 200 proceeds to block 238. At block 238, the process 200 inputs a final question to determine if the vehicle has been unlocked. If the vehicle 102 has been unlocked within the time period determined by the timer of block 232, the process 200 proceeds to block 240.Blocks 214-238 of process 200 generally ensure that a predetermined pattern is entered using the ignition switch and the lock / unlock switch within a predetermined period of time. Using a pattern that requires at least alternating activation of various vehicle switches within a relatively short period of time, e.g., a few seconds, can generally help eliminate the likelihood of inadvertent activation of a vehicle total reset command.

[0022] At block 240, several default settings are established for the vehicle 102. By way of example only, settings such as user-specific buttons or other hardware, images stored in the vehicle, music, seat position and mirror settings, Bluetooth devices, phone books, contact lists, call histories, navigation destinations or stops, a customized list of system settings, a valet mode setting, and a user-selected language may all be included among the various settings that may be reset. The process 200 may then terminate.

[0023] In Fig. 3, a sequence of remote inputs provided by a key fob (FOB) can now be used to trigger a vehicle reset. For example, FOB inputs could trigger a reset if the FLEET_CONFIG bit is TRUE. For example, the user could trigger a reset by pressing and holding the UNLOCK button on the FOB for a specified period of time (e.g., 8 seconds).

[0024] In Fig. 3, an exemplary process 304 of initiating a total reset using a key fob or other RF transmitter associated with the vehicle 102 will now be described in further detail. The process 300 may generally begin at block 302, where the process 300 asks whether a fleet configuration bit related to the vehicle 102, e.g., the aforementioned FLEET_CONFIG bit, is present. If the configuration bit is not present, the process 300 proceeds to block 304. At block 304, the process 300 determines that the vehicle 102 will have default functionality. More specifically, default functionality may generally allow selective or remote resetting of various vehicle parameters.

[0025] Where process 300 determines that a fleet configuration bit is present at block 302, process 300 proceeds to block 306. At block 306, process 300 asks if a clear fleet configuration request is present. For example, the clear fleet configuration request may be present if a user or administrator has decided to deactivate a fleet status of vehicle 102. In such a case, process 300 may proceed to block 308. At block 308, process 300 sets a fleet configuration status of vehicle 102 to false. In other words, block 308 generally resets the status of vehicle 102; it is no longer considered a "fleet" vehicle, and selective / remote resetting of vehicle parameters is no longer permitted.

[0026] Where the process 300 determines at block 306 that a delete fleet configuration request is not present, the process 300 proceeds to block 310. At block 310, the process 300 asks whether an odometer reading associated with the vehicle 102 exceeds a predetermined amount x. For example, the vehicle 102 may initially be set to a predetermined amount x, and beyond such an odometer reading, a fleet vehicle is expected to no longer be used in fleet service. If the odometer reading exceeds the predetermined value x, the process 300 returns to block 308. If the odometer reading of the vehicle 102 is still below a predetermined fleet service threshold x, the process 300 proceeds to block 312. At block 312, the process 300 asks whether an elapsed time associated with the vehicle 102, e.g., an expected fleet service interval, has expired.If the predetermined elapsed time has exceeded y, the process 300 returns to block 308. If the elapsed time associated with the vehicle 102 is still below a predetermined expected fleet deployment threshold y, the process 300 may proceed to block 314.

[0027] Proceeding to block 314, process 300 may then query whether a remote unlock associated with a vehicle key registered with vehicle 102 has been activated. If the signal is present, process 300 may proceed to block 316, where the timer is started. Alternatively, if the remote unlock signal has not been received, process 300 may return to block 310.

[0028] Proceeding to block 318, process 300 asks whether the remote unlock signal has been activated for a predetermined time T. If the remote unlock signal has been present for the predetermined time T, process 300 proceeds to block 320. Alternatively, process 300 returns from block 318 to block 310.

[0029] At block 320, process 200 asks whether the timer activated at block 316 has expired. If the timer has expired, meaning that the key fob command, such as a remote unlock button, has been held down for the predetermined time T, process 300 proceeds to block 340. Alternatively, process 300 may return to block 318.

[0030] At block 340, several default settings are established for the vehicle 102. For example only, settings such as user-specific buttons or other hardware, images stored in the vehicle, music, seat position and mirror settings, Bluetooth devices, phone books, contact lists, call histories, navigation destinations or stops, a customized list of system settings, a valet mode setting, and a user-selected language may all be included among the various settings that may be reset. Process 300 may then terminate.

[0031] In Fig. 4, a separate single transmitter could now be provided to rental companies, alternatively or in addition to other hardware / methods for providing a total vehicle reset, which could be used to reset multiple vehicles universally with a single button press. The transmitter could be in the form of an application loaded onto a phone offering a cloud-based service for the user to manage their vehicle fleet.

[0032] An example process 400, as in Fig.4, may also initiate a full reset using a full reset command associated with multiple vehicles 102. The process 400 may generally begin at block 402, where the process 400 asks if a fleet configuration bit related to the vehicle 102, e.g., the FLEET_CONFIG bit mentioned above, is present. If the configuration bit is not present, the process 400 proceeds to block 404. At block 404, the process 400 determines that the vehicle 102 will have default functionality. More specifically, default functionality may generally allow selective or remote resetting of various vehicle parameters.

[0033] Where process 400 determines that a fleet configuration bit is present at block 402, process 400 proceeds to block 406. At block 406, process 400 asks if a fleet configuration clear request is present. For example, the fleet configuration clear request may be present if a user or administrator has decided to deactivate a fleet status of vehicle 102. In such a case, process 400 may proceed to block 408. At block 408, process 400 sets a fleet configuration status of vehicle 102 to false. In other words, block 408 generally resets the status of vehicle 102; it is no longer considered a "fleet" vehicle, and selective / remote resetting of vehicle parameters is no longer permitted.

[0034] Where the process 400 determines at block 406 that a delete fleet configuration request is not present, the process 400 proceeds to block 410. At block 410, the process 400 asks whether an odometer reading associated with the vehicle 102 exceeds a predetermined amount x. For example, the vehicle 102 may initially be set to a predetermined amount x, and a fleet vehicle beyond such an odometer reading is expected to no longer be used in fleet service. If the odometer reading exceeds the predetermined value x, the process 400 returns to block 408. Alternatively, if the odometer reading of the vehicle 102 is still below a predetermined fleet service threshold x, the process 400 proceeds to block 412. At block 412, the process 400 asks whether an elapsed time associated with the vehicle 102, e.g., an expected fleet service interval, has expired.If the predetermined elapsed time has exceeded y, the process 400 returns to block 408. If the elapsed time associated with the vehicle 102 is still below a predetermined expected fleet deployment threshold y, the process 400 may proceed to block 414.

[0035] Proceeding to block 414, process 400 asks whether a total reset command has been received (i.e., the question is "true" or "T"). For example, a total reset command may be provided by a mobile device, computer, or other application associated with vehicle 102, e.g., initiated by call center 122, mobile application 130, or any other method of providing a remote command to vehicle 102. Where the total reset command is present, process 400 may proceed to block 440. Alternatively, process 400 may return to block 406.

[0036] At block 440, several default settings are established for the vehicle 102. For example only, settings such as user-specific buttons or other hardware, images stored in the vehicle, music, seat position and mirror settings, Bluetooth devices, phone books, contact lists, call histories, navigation destinations or stops, a customized list of system settings, a valet mode setting, and a user-selected language may all be included among the various settings that may be reset. Process 400 may then terminate.

[0037] In some example approaches, the example methods described herein may employ a computer or computer-readable storage medium that implements the various methods and processes described herein, e.g., processes 200, 300, and / or 400. In general, computer systems and / or devices, such as the processor and user input device, may employ any of a variety of computer operating systems, including, but not limited to, versions and / or variants of the Microsoft Windows® operating system, the Unix operating system (e.g., the Solaris® operating system distributed by Oracle Corporation of Redwood Shores, California, USA), the AIX UNIX operating system distributed by International Business Machines of Armonk, New York, USA, the Linux operating system, the Mac OS X and iOS operating systems distributed by Apple Inc.in Cupertino, California, USA, and the Android operating system developed by the Open Handset Alliance.

[0038] Computing devices generally include computer-executable instructions, where the instructions can be executed by one or more of the computing devices listed above. Computer-executable instructions can be compiled from or interpreted from computer programs created using a variety of programming languages ​​and / or technologies, including, but not limited to, Java™, C, C++, Visual Basic, Java Script, Perl, etc. In general, a processor (e.g., a microprocessor) receives instructions from, e.g., memory, a computer-readable medium, etc., and executes those instructions to thereby perform one or more processes, including one or more of the processes described herein. Such instructions and other data can be stored and transmitted using a variety of computer-readable media.

[0039] A computer-readable medium (also referred to as a processor-readable medium) includes any non-transitory (e.g., tangible) medium that participates in providing data (e.g., instructions) that can be read by a computer (e.g., by a processor of a computer). Such a medium may take many forms, including, but not limited to, non-volatile media and volatile media. Non-volatile media may include, for example, optical or magnetic disks and other persistent storage. Volatile media may include, for example, dynamic random-access memory (DRAM), which typically forms main memory. Such instructions may be carried by one or more transmission media, including coaxial cable, copper wire, and optical fiber, including those comprising a system bus coupled to a processor of a computer.Common forms of computer-readable media include, for example, a floppy disk, a diskette, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM, a DVD, any other optical medium, punched cards, paper tape, any other physical medium with hole patterns, a RAM, a PROM, an EPROM, a flash EEPROM, any other memory chip or memory cartridge, or any other medium from which a computer can read.

[0040] Databases, data collections, or other data stores described herein may include various types of mechanisms for storing, retrieving, and accessing various types of data, including a hierarchical database, a set of files in a file system, an application database in a proprietary format, a relational database management system (RDBMS), etc. Each such data store is generally embodied in a computing device employing a computer operating system, such as one of those mentioned above, and is accessed via a network using any one or more of a variety of methods. A file system may be accessible by a computer operating system and may include files stored in a variety of formats.An RDBMS generally uses the Structured Query Language (SQL), in addition to a language for creating, storing, manipulating, and executing stored procedures, such as the PL / SQL language mentioned above.

[0041] In some examples, system elements may be implemented as computer-readable instructions (e.g., software) on one or more computing devices (e.g., servers, PCs, etc.) stored on associated computer-readable media (e.g., disks, memory, etc.). A computer program product may include such instructions stored on computer-readable media for performing the functions described herein.

[0042] The exemplary illustrations are not limited to the examples described above. Rather, a multitude of variations and modifications are possible, which also incorporate the ideas of the exemplary illustrations and therefore fall within the scope of protection. Accordingly, it is understood that the above description is not intended to be limiting, but rather illustrative.

[0043] With respect to the processes, systems, methods, heuristics, etc. described herein, it is understood that although the steps of such processes, etc., have been described as occurring according to a certain ordered sequence, such processes could be practiced with described steps performed in a different order than the order described herein. Further, it is understood that certain steps could be performed concurrently, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating particular embodiments and should not be construed in any way as limiting the claimed invention.

[0044] Accordingly, it is to be understood that the above description is not intended to be limiting, but illustrative. Upon review of the above description, many other embodiments and applications than the examples given would become apparent. The scope of the invention should be determined not with reference to the above description, but instead with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. It is anticipated and intended that future developments will occur in the art discussed herein and that the disclosed systems and methods will be incorporated into such future embodiments. In summary, it should be understood that the invention is susceptible of modification and variation and is limited only by the following claims.

[0045] All terms used in the claims are intended to be given their broadest reasonable interpretations and ordinary meanings as understood by those skilled in the art, unless an explicit statement to the contrary is made herein. In particular, the use of singular articles such as "a," "an," "the," "the," and variations thereof is intended to indicate one or more of the recited elements, unless a claim expressly states a contrary limitation.

Claims

[1] Method comprising: Determining that a vehicle (102) is a fleet vehicle (102), including determining a presence of a configuration bit indicating that the vehicle (102) is a fleet vehicle (102); Receiving an indication of a conclusion of a vehicle usage session as a fleet vehicle (102); and resetting, in response to the conclusion about the Vehicle usage session, several user-adjustable vehicle parameters to a default setting. [2] The method of claim 1, wherein resetting the plurality of user-adjustable vehicle parameters includes remotely resetting the plurality of user-adjustable vehicle parameters. [3] The method of claim 2, further comprising setting up the remote reset as a remote reset with a key fob or a wireless device. [4] The method of claim 2, further comprising establishing the remote reset as a remote reset with a wireless device in communication with a remote database (120) including a plurality of fleet vehicles (102). [5] The method of claim 1, wherein resetting the plurality of user-adjustable vehicle parameters includes entering vehicle control patterns using a plurality of vehicle control inputs. [6] The method of claim 5, wherein the plurality of vehicle control inputs include a door lock / unlock switch (112) and / or an ignition switch (114a). [7] The method of claim 1, further comprising setting the configuration bit as stored in a memory of the vehicle (102). [8] The method of claim 1, further comprising setting the configuration bit to expire after a predetermined event. [9] The method of claim 8, wherein the predetermined event is a vehicle mileage limit or a time limit. [10] A method comprising: Installing a configuration bit in a vehicle (102), the configuration bit indicating that the vehicle (102) is a fleet vehicle (102); and providing a processor for the vehicle (102) configured to reset a plurality of user-adjustable vehicle parameters to a default setting in response to the configuration bit and an indication of a conclusion of vehicle usage associated with the vehicle (102). [11] The method of claim 10, wherein resetting the plurality of user-adjustable vehicle parameters includes remotely resetting the plurality of user-adjustable vehicle parameters. [12] The method of claim 11, further comprising setting up the remote reset as a remote reset with a key fob or a wireless device. [13] The method of claim 10, wherein resetting the plurality of user-adjustable vehicle parameters includes entering a vehicle control pattern using a plurality of vehicle control inputs. [14] The method of claim 13, wherein the plurality of vehicle control inputs include a door lock / unlock switch (112) and / or an ignition switch (114a). [15] The method of claim 10, further comprising receiving the indication of the conclusion about vehicle usage; and resetting, in response to the received indication, a plurality of user-adjustable vehicle parameters to the default setting. [16] Vehicle (102) comprising: a processor in communication with a plurality of user-adjustable vehicle settings; and a configuration bit stored in the vehicle (102), the configuration bit indicating that the vehicle (102) is a fleet vehicle (102); wherein the processor is configured to reset a plurality of user-adjustable vehicle parameters to a default setting in response to at least the configuration bit and an indication of a conclusion of vehicle usage associated with the vehicle (102). [17] The vehicle (102) of claim 16, wherein the processor is configured to reset the plurality of user-adjustable vehicle parameters in response to a remote signal. [18] The vehicle (102) of claim 17, further comprising a key fob in wireless communication with the vehicle (102), the key fob configured to transmit the remote signal. [19] The vehicle (102) of claim 16, wherein the processor is configured to reset the plurality of user-adjustable vehicle parameters to a default setting in response to at least one vehicle control pattern input using a plurality of vehicle control inputs. [20] The vehicle (102) of claim 19, wherein the plurality of vehicle control inputs include a door lock / unlock switch (112) and / or an ignition switch (114a).

Images