Managing the configuration of a vehicle

Generally described, aspects of the disclosed subject matter are directed to managing the configuration of a vehicle. In accordance with one embodiment, a method of modifying the configuration of a vehicle based on the vehicle's location is provided. The method includes receiving, from a remote Satellite Positioning System (“SPS”) device, positioning data that identifies the location of the vehicle. Then, the positioning data is used to identify one or more regulations that are applicable, given the location of the vehicle. Based on collected vehicle readings, a determination is made regarding whether the configuration of the vehicle should be modified. In turn, the method may cause the configuration of the vehicle to be modified to comply with the one or more regulations.

BACKGROUND

Increasingly, electronic components are being relied upon to facilitate the operation of a vehicle. These electronic components aid in the development of sophisticated vehicle subsystems such as collision detection, automated cruise control, global positioning navigation, and the like. In this regard, systems have been developed that allow electronic components in a vehicle to communicate in accordance with standard protocols. For example, a controller which may have been developed by an engine manufacturer may encapsulate and transmit data in accordance with a standard protocol. A cab-mounted vehicle controller developed by a different entity may receive and process the transmitted engine data. Since standard communication protocols exist, components made by different manufacturers are able to communicate. As a result of these and other advancements, an increasing amount of information generated by various vehicle systems may be monitored by a vehicle operator.

The increased availability of information allows a vehicle operator to more readily monitor vehicle conditions while driving. For example, tire pressure sensors may report readings that are presented on a dashboard display, thereby preventing a vehicle operator from having to manually check tire pressure. However, the increased availability of information can make operating the vehicle more complex and potentially distracting. In this regard, a vehicle operator may need to monitor multiple vehicle systems in order to ensure compliance with regulatory requirements (i.e., speed limits, weight restrictions, emission standards, lighting requirements, etc.). One deficiency of existing systems is the lack of automated assistance for configuring and operating a vehicle to ensure compliance with regulatory requirements that may vary depending on the vehicle's location.

SUMMARY

Generally described, aspects of the disclosed subject matter are directed to managing the configuration of a vehicle. In accordance with one embodiment, a method of modifying the configuration of a vehicle based on the vehicle's location is provided. The method includes receiving, from a remote Satellite Positioning System (“SPS”) device, positioning data that identifies the location of the vehicle. Then, the positioning data is used to identify one or more regulations that are applicable, given the location of the vehicle. Based on collected vehicle readings, a determination is made regarding whether the configuration of the vehicle should be modified. In turn, the method may cause the configuration of the vehicle to be modified to comply with the one or more regulations.

DETAILED DESCRIPTION

Embodiments of the disclosed subject matter will now be described with reference to the drawings where like numerals correspond to like elements. Embodiments of the present disclosure are generally directed to a vehicle configuration system suitable for use in vehicles, such as Class 8 trucks. Although exemplary embodiments of the disclosed subject matter may be described herein with reference to a truck, it will be appreciated that aspects of the disclosed subject matter have wide application, and therefore, may be suitable for use with many types of vehicles. Accordingly, the following descriptions and illustrations herein should be considered illustrative in nature, and thus, not limiting the claimed subject matter.

Prior to discussing the details of various aspects of the disclosed subject matter, it should be understood that the following description is presented largely in terms of logic and operations that may be performed by conventional electronic components. These electronic components, which may be grouped in a single location or distributed over a wide area, generally include processors, memory, storage devices, display devices, input devices (e.g., sensors), etc. It will be appreciated by one skilled in the art that the logic described herein may be implemented in a variety of configurations, including software, hardware, or combinations thereof. The hardware may include, but is not limited to, analog circuitry, digital circuitry, processing units, application specific integrated circuits (ASICs), and the like. In circumstances where the components are distributed, the components are accessible to each other via communication links.

Referring toFIG. 1, the following is intended to provide a general overview of an environment100in which aspects of the disclosed subject matter may be implemented. In this regard, the environment100depicted inFIG. 1includes the truck105and the SPS satellites110. In one embodiment, the configuration of the truck105is set and/or modified in order to comply with applicable regulatory requirements. In this regard, the SPS satellites110may periodically establish a communication link with the truck105and report location identifying information typically in terms of latitudinal and longitudinal coordinates. While various technologies may be used to identify the location and track the movement of the truck105, preferably the reporting of location information uses a satellite positioning system (“SPS”) such as the global positioning system (“GPS”) or differential global positioning system (“DGPS”). In this regard, those of ordinary skill in the art and others will appreciate from the following description that the disclosed subject matter may utilize a variety of satellite and/or radio frequency location tracking systems (e.g., GPS, Galileo, DGPS, GLOSNASS, WAAS, OMEGA, LORAN, VOR, etc.). Collectively, such systems will be referred to herein as positioning systems, for ease of description. Regardless of the nature of the positioning system, the received location identifying information may be used to identify the applicable regulatory requirements given the location of the truck105. As described in further detail below, aspects of the present disclosure may set and/or modify the configuration of the truck105in various ways to ensure compliance with regulatory requirements that may vary depending on the location of the truck105.

As further illustrated inFIG. 1, the truck105includes a plurality of configurable components which, in this example, include the engine115, lift axle120, and headlamps125. As known to those skilled in the art, the engine115provides power to affect movement of the truck105. To distribute the vehicle load, the truck105includes a lift axle120coupled to the wheels130that may be deployed or retracted. When deployed, the wheels130are positioned to contact the road surface, further distributing the vehicle load. If retracted, the wheels130are not positioned to contact the road surface and the vehicle load is distributed over the remaining axles. Moreover, the truck105includes the headlamps125which provide external vehicle lighting when activated.

The truck105may include conventional operator control inputs (not illustrated), for obtaining input that affect various vehicle components including the engine115, lift axle120, and headlamps125. These conventional operator control inputs may include, but are not limited to an accelerator pedal, shifting mechanism, brake pedal, dashboard, buttons, switches, knobs, etc. In one aspect, input received using these or other conventional operator controls may be adjusted to prevent a regulatory violation. To this end, location information reported by the SPS satellites110is used for automatically configuring the truck105. When the location of the truck105is known, the applicable regulations (i.e., weight limit restrictions, speed limits, emission idling standards, lighting requirements, etc.) may be identified and the configuration of the vehicle components modified accordingly.

One of ordinary skill in the art will appreciate that the truck105will include many more components than those depicted inFIG. 1. However, it is not necessary that all of these generally conventional components be shown or described. Moreover, whileFIG. 1depicts a truck105, another type of “vehicle” such as a car, boat, Recreational Vehicle (“RV”), vessel, etc., may be used to implement aspects of the present disclosure.

In one aspect, the present disclosure provides a configuration management system suitable for use in a vehicle such as truck105(FIG. 1). Generally described, the configuration management system monitors the operation and configuration of a vehicle to prevent violations of regulatory requirements. One suitable configuration management system will now be described. As best shown inFIG. 2, the configuration management system includes a configuration controller200that is communicatively connected to other vehicle controllers204-210, the sensors212-216, and the speed limit restrictor218via the vehicle-wide communication network202. Those skilled in the art and others will recognize that the vehicle-wide communication network202may be implemented using any number of different communication protocols such as, but not limited to, Society of Automotive Engineers' (“SAE”) J1587, SAE J1922, SAE J1939, SAE J1708, standards and combinations thereof. Alternatively, the aforementioned controllers204-210may be software control modules contained within one or more general-purpose controllers. It will be appreciated, however, that the disclosed subject matter is not limited to any particular type or configuration of controller, or to any specific control logic for governing operation of the vehicle.

The vehicle controllers depicted inFIG. 2include various controllers such as the engine controller204, transmission controller206, lift axle controller208, and lighting controller210. Generally described, the engine controller204manages functions and operations of various aspects of the engine115. For example, idling and emissions, fuel consumption, and engine speed may be monitored and managed by the engine controller204. Similarly, the transmission controller206manages aspects of a transmission (not shown) such as transmission shifting. In this regard, the speed limit restrictor218may be in communication with the engine controller204and transmission controller206. As described in further detail below, the speed limit restrictor218may be used to reduce the speed of the vehicle to prevent a regulatory violation. The lift axle controller208manages the deployment/retraction of the lift axle120(FIG. 1). Moreover, the lighting controller210manages the vehicle lighting such as the activation/deactivation of vehicle headlamps125, interior lighting, exterior lighting, among others.

The exemplary sensors212-216depicted inFIG. 2include the suspension sensors212, the speed sensor214, and the axle deployment sensor216, etc. The suspension sensors212may include weight measurement sensors and load monitoring sensors (not shown) that generate signals indicative of the weight and position of the vehicle's cargo loads. The vehicle sensors212-216may be used individually or in conjunction with each other. For example, the suspension sensors212may be used in coordination with the axle deployment sensor216in determining whether a vehicle is in compliance with applicable weight regulations.

With reference toFIG. 3, an exemplary component architecture of the configuration controller200will now be described. As best shown inFIG. 3, the controller200includes a memory300with a Random Access Memory (“RAM”), an Electronically Erasable, Programmable, Read-Only Memory (“EEPROM”), and any other suitable data storage means, a processor302, the SPS interface304, a network interface306, a configuration database308, and a configuration module310that includes logic for setting and/or modifying the configuration of a vehicle depending on the applicable regulatory requirements. By way of example only, the modifications to a vehicle's configuration performed by the configuration module310may include adaptive speed control, lift axle deployment/retraction, activating/deactivating vehicle lighting, adjusting the emission idle settings, just to name a few. In this regard, the processor302executes logic provided by the configuration module310in order to modify the configuration of the vehicle. To this end, the processor302and memory300are connected by an input/output (I/O) interface312for communicating with other vehicle devices, controllers, sensors, and the like.

As used herein, control units, control modules, program modules, etc., can contain logic for carrying out general or specific operational features. The logic can be implemented in hardware components, such as analog circuitry, digital circuitry, processing units, and combinations thereof, or software components having instructions which can be processed by the processing units, etc. Therefore, as used herein, the term “controller” can be used to generally describe these aforementioned components, and can be either hardware or software, or combinations thereof, that implement logic for carrying out various aspects of the present disclosure.

The SPS interface304is a component of the configuration controller200that is operative to receive and record SPS signals. More specifically, the SPS interface304includes an SPS communication circuitry that receives signals from SPS satellites110, pseudolites, or related devices and uses the signals to determine the location of the SPS communication circuitry and, thus, the vehicle (i.e., the truck105) that incorporates the configuration controller200. The term SPS is a generic reference to any satellite-pseudolite-based location determining system. In addition to performing SPS tracking, which utilizes SPS signals in order to determine a location, some exemplary systems may also use radio frequency identification (“RFID”) signals as an additional aid in determining the vehicle's location.

The configuration controller200may further include a network interface306for communicating with other devices or networks using IP-based communication protocols. The network interface306may include communication circuitry that permits communication over one or more of the wireless networks such as those using CDMA, GSM, IEEE 802.11 and IEEE 802.16, UMTS, WIMAX, etc. As described in further detail below, the network interface306may be used to obtain route data, regulation data, and component configuration data that is used in setting and/or modifying the configuration of the vehicle.

As briefly mentioned above, the configuration controller200may include a configuration database308that stores data relevant to setting the configuration of a vehicle. Now, with reference toFIG. 4, additional aspects of the configuration database308will be described. As illustrated inFIG. 4, the configuration database308stores different types of data that are relevant to setting and/or modifying the configuration of the vehicle including the route data400, regulation data402, and component configuration data404. The route data400may include, but is not limited to, information regarding road locations, directions, turn restrictions, and corresponding speed limits, etc. With the vehicle's location and the route data402, aspects of the present disclosure are able to identify a road that the vehicle is traveling and the corresponding speed limits.

The regulation data402maintained in the configuration database308may include sets of regulations imposed by particular jurisdictions. This information may include, but is not limited to, weight limit restrictions, height limits, emission idle standards, lighting regulations, among others. The regulation data402may be layered so that all regulations applicable to operating a vehicle at a particular location can be identified. Accordingly, the regulation data402may include information that describes regulations imposed by a national jurisdiction at one layer as well as local jurisdictions (i.e., state, county, city, etc.) at other layers.

The component configuration data404includes information that describes the proper configuration of various vehicle components, given certain variables. For example, the component configuration data404may indicate that the lift axle120should be deployed, given certain vehicle attributes (type of vehicle, number of axles, cargo type, etc.), the current vehicle weight, applicable weight regulations, among others. By way of other examples, the appropriate configuration of the vehicle's lights (i.e., headlamps, trailer lights, cab lights, etc.), emission idle settings, etc., given the appropriate variables, are defined in the component configuration data406. While specific examples have been described, those skilled in the art and others will recognize that the configuration database308may maintain other types of data without departing from the scope of the claimed subject matter.

In one embodiment, the configuration controller200interfaces with a host computing system410to obtain current data for storage locally in the configuration database308. In this regard, data that is relevant to setting and/or modifying the configuration of a vehicle across jurisdictions may be maintained at the host computing system410. The SPS interface304or the network interface306may be used to communicate over the network412with the host computing system410. In this regard, the network412may utilize IP-based protocols and be implemented as a local area network (“LAN”), wireless network, wide area network (“WAN”), such as the Internet, and combinations thereof. However, since IP-based protocols for network communication are well known to those skilled in the art, those protocols will not be described here. In any event, current data used for setting and/or modifying the configuration of a vehicle may be maintained at the host computing system410. As illustrated inFIG. 4, this data may be delivered to the configuration controller200and stored in the configuration database308.

As indicated above, the configuration controller200executes application logic embodied in the configuration module310to ensure that a vehicle is in compliance with regulations that may vary between locations. Now, with reference toFIG. 5, a configuration method500for setting and/or modifying the configuration of a vehicle to comply with applicable regulations will be described. As a preliminary matter, those skilled in the art will appreciate that a typical controller200is frequently designed to operate in a continual manner, i.e., once initialized and operating, the configuration controller200continually monitors the location and configuration of the vehicle. Accordingly, while the configuration method500depicted inFIG. 5includes a begin and end terminal, the method500operates continually, presumably until the configuration controller200is powered down.

As illustrated inFIG. 5, the configuration method500begins at block502where the configuration controller200starts collecting data that is relevant in setting and/or modifying the configuration of a vehicle. The data collected by the configuration controller200may be generated and transmitted from one or more remote controllers, sensors, and other devices. As mentioned briefly above, data collection may be initiated at vehicle startup and occur continually during operation of the vehicle. This data may be reported from a number of vehicle systems and transmitted to the configuration controller200, as discussed above with reference toFIG. 2. Data collected by the configuration controller200may include, but is not limited to, vehicle speed, weight and load information, lighting configuration, lift axle deployment/retraction information, idle emission settings, and the like. Moreover, the collection of position data generated by one or more remote devices, such as the SPS satellites110, may also be initiated at block502. As described in further detail below, data collected by the configuration controller200may be processed and used to set and/or modify the vehicle configuration in various ways.

At block504of the configuration method500, a set of regulatory requirements that apply, given the vehicle's current location, are identified. While in transit, a vehicle may cross national borders, state lines, and the like. Each of these jurisdictions may impose different regulatory requirements. In addition, speed limits vary depending on the location of a vehicle on a particular roadway. Using the vehicle's location, a set of applicable regulations (i.e., weight limits, speed limits, emission idling standards, lighting requirements, etc.) are identified. In particular, location data reported by the SPS satellites110may be used in performing a database lookup (in the configuration database308) to identify a set of regulations that are applicable given the location of the vehicle. In this regard, the data maintained in the configuration database308is accessed to identify the set of applicable regulations, at block504.

At block506of the configuration method500, a comparison is performed between actual vehicle readings collected by the configuration controller200relative to the applicable set of regulatory requirements. By performing this comparison, the compliance state of the vehicle with regard to regulations that may vary depending on a vehicle's location is tracked. In this regard, the identified compliance state is used to determine whether corrective action should be taken to modify the configuration of the vehicle and ensure that a regulation is not violated.

Now, with reference toFIG. 6, an exemplary compliance state machine600for tracking the state of a vehicle based on actual vehicle readings will be described. As illustrated inFIG. 6, the compliance state machine600may be in one of three potential states including the non-compliant state602, the compliant state604, and the overly compliant state606. The various states602-606of the vehicle as represented in the compliance state machine600can apply to individual readings as well as to the overall compliance state of the vehicle.

By comparing actual readings relative to a set of applicable regulations, a determination may be made that the vehicle is in the non-compliant state602. The following description provides exemplary scenarios in which the vehicle may be identified as being in the non-compliant state602by aspects of the present disclosure. In one embodiment, received positioning data is used to determine whether the vehicle is located in or about to enter a new jurisdiction that imposes different weight restrictions than a previous jurisdiction. If the vehicle weight is such that a regulation in a new jurisdiction will be violated, then the vehicle transitions608to the non-compliant state602. Upon transitioning to the non-compliant state602, in this example, a determination is made regarding whether the lift axle120(FIG. 1) should be deployed in order to transition610the vehicle to the compliant state604.

Generally described, a transition to the non-compliant state602may occur whenever the configuration of the vehicle should be modified to comply with a particular regulation. For example, certain jurisdictions (i.e., Canada) impose daytime headlamp restrictions where headlamps must be activated while operating the truck105. Similar to the description provided above, if the vehicle headlamps are not activated and a determination is made (based on received positioning data) that corrective action is needed to prevent a violation, then the vehicle will transition608to the non-compliant state602. By way of additional examples, if the vehicle state is below the designated speed limit, the vehicle's speed is identified as being in the compliant state604. In instances when the vehicle operator attempts to surpass the designated speed limit, the vehicle transitions608to the non-compliant state602.

In another embodiment, an engine's emission idle settings may need to change in order to comply with a local regulation. In this regard, certain jurisdictions (i.e., California) impose more stringent idle emission standards than other jurisdictions. Positioning data reported by the SPS satellites110may be used to determine whether the vehicle is located in or about to enter this type of jurisdiction. If the emission standards in a new jurisdiction will be violated, the vehicle may transition608to the non-compliant state602so that corrective action may be taken, as described in further detail below. On the other hand, upon leaving a jurisdiction that imposes more stringent idle emission standards, the vehicle may transition612to the overly compliant state606. In this instance and as described in further detail below, action may be taken to transition614the vehicle from the overly compliant state606to the compliant state604.

With reference again toFIG. 5, the configuration method500determines whether the vehicle is in the compliant state at decision block508. As described above with reference toFIG. 6, a vehicle may be in one of potentially three states including the non-compliant state602, the compliant state604, or the overly compliant state606. In instances when the vehicle is identified as being in the compliant state604, the result of the test performed at block508is “YES.” In this instance, the configuration method500proceeds to block518, where it terminates. If the vehicle is either in the non-compliant state602or the overly compliant state606, the result of the test performed at block508is “NO,” and the configuration method500proceeds to block510, described in further detail below.

At block510of the configuration method500, the vehicle operator is notified about a condition that caused the vehicle to transition to either the non-compliant state602or the overly compliant state606. Notifying the vehicle operator is an optional step that may not be performed in all instances. However, the vehicle operator will typically be notified and specifically informed regarding the condition that caused the vehicle to transition to the non-compliant state602or the overly compliant state606. In this regard, the vehicle operator may be notified through a dialogue that is presented on a dashboard display. However, other visual, auditory, or haptic feedback may be provided to notify the vehicle operator. In one embodiment, the vehicle operator may be given the opportunity to rectify the non-compliant or overly compliant condition before modifications are made automatically. In addition or alternatively, the vehicle operator may be allocated the authority to prevent aspects of the present disclosure from automatically modifying the configuration of the vehicle. In any event, it should be well understood that notifying the vehicle operator, at block510, is an optional step that may not be performed in all instances.

At decision block512of the configuration method500, a determination is made regarding whether the vehicle is in the non-compliant state602. If block512is reached, the vehicle is either in the non-compliant state602or the overly compliant state606as described above. In instances when the vehicle is in the overly compliant state606, the result of the test performed at block512is “NO,” and the configuration method500proceeds to block516, described in further detail below. On the other hand, if the vehicle is in the non-compliant state602, the result of the test performed at block512is “YES,” and the configuration method500proceeds to block514.

At block514of the configuration method500, logic for transitioning a vehicle from the non-compliant state602to the compliant state604is executed. If block514is reached, the vehicle is in the non-compliant state602, as described above. In this instance, the logic that is executed at block514may involve modifying the configuration of the vehicle in a number of different ways, as described in further detail below.

Now, with reference again toFIG. 6, exemplary modifications to a vehicle's configuration that may be implemented at block514to transition the vehicle from the non-compliant state602to the compliant state604will be described. In one embodiment, a vehicle lift axle120is automatically deployed in order to comply with weight regulations associated with a particular jurisdiction, roadway, etc. For example, a determination may be made (at block506described above) that a vehicle has or will enter a jurisdiction with different weight limit restrictions than a previous jurisdiction. In this instance, logic is executed to determine whether the lift axle120should be deployed given the new weight limit restrictions. As described above, the configuration controller200receives location identifying information of a vehicle from a positioning system. A lookup may be performed in the configuration database308to determine whether the lift axle120should be deployed in order to comply with the new weight limit restrictions. In instances when the lift axle120should be deployed, the configuration controller200transmits a message to the lift axle controller208, at block514, for the purpose of deploying the lift axle120and therefore modifying the configuration of the vehicle to prevent a regulatory violation.

In another embodiment, the speed limit restrictor218, or other substantially similar component is employed to limit the speed of a vehicle. In this regard, the route data400maintained in the configuration database308may be used to determine the speed limit that applies, given the location of the vehicle. This data may be compared to the actual vehicle speed collected by the configuration controller200to determine whether the vehicle operator is attempting to surpass the designated speed limit. To transition the vehicle to the compliant state602in this instance, the configuration controller200may transmit one or more messages to the speed limit restrictor218to prevent the speed limit from being exceeded.

In order to transition the vehicle from the non-compliant state602to the compliant state604, at block514, other types of logic may be executed. For example, a determination may be made (at block506described above) that a vehicle's headlamps should be activated or emission idle settings modified in order to comply with an applicable regulation. In this instance, the logic executed at block514causes the headlamps125to be activated and/or emission settings of the engine115to change. To modify the configuration of the vehicle in this way, one or more messages may be transmitted from the configuration controller200to the engine controller204and/or lighting controller210, as appropriate.

With reference again toFIG. 5, at block516of the configuration method500, logic for managing one or more overly compliant vehicle conditions is executed. If block516is reached, a vehicle was identified as being in the overly compliant state606. In this instance, logic may be executed for transitioning the vehicle from an overly compliant state606to the compliant state604. For example, certain jurisdictions may impose more stringent weight and/or emission idling standards than others. Upon leaving this type of jurisdiction, a vehicle may be in the overly compliant state606. In this instance, logic may be executed to transition the vehicle from the overly compliant state606to the compliant state604. The logic that is executed, at block516, may involve modifying the same vehicle components in ways that are converse to the description provided above with reference to block514. In an alternative embodiment, user input and/or system settings define how an overly compliant vehicle condition is handled at block516. In this regard, a vehicle operator may be prompted, when the vehicle is identified as being in the overly compliant state606, to provide input regarding the corrective action, if any, to implement. In addition or alternatively, a fleet operator or other entity may establish settings which provide logic for handling one or more overly compliant vehicle conditions. Then, once the logic for handling either a non-compliant vehicle condition (at block514) or an overly compliant vehicle condition (at block516) is executed, the configuration method500proceeds to block518, where it terminates.