Patent Application
20210366209
The illustrative embodiments generally relate to methods and apparatuses for driver-tuned diagnostics and reporting.
Vehicles have a variety of onboard diagnostic reporting codes, which provide diagnostic data and state-indicators for various vehicle systems. With the volume and variety of information flowing over a vehicle controller area network (CAN) bus, many sources can put this information to good use.
This information used to be primarily used for vehicle diagnostics, where a mechanic or other technician would plug a device into an onboard diagnostic (OBD) port. The OBD port gave the device, typically a diagnostic tool, access to the CAN bus. The tool could then pull useful information off the bus.
More recently, insurance companies and other services have begun to use OBD ports to access vehicle information. By recording and reporting a set of data from the bus, this can allow companies to determine how a particular vehicle is being used. These devices are typically set to observe a standard set of conditions, such as, for example, engine speed, vehicle speed, braking aggressiveness, etc.
In a first illustrative embodiment, a system includes a processor configured to determine a vehicle-specific parameter including a vehicle-specific modifier for modifying a vehicle-state reporting trigger. The processor is further configured to detect an occurrence of the vehicle-state reporting trigger that has been modified based on the vehicle-specific parameter, such that the reporting trigger triggers a report based on a different vehicle-state than an unmodified predefined version of the reporting trigger. Also, the processor is configured to report the occurrence to an occupant, responsive to the detection.
In a second illustrative embodiment, a system includes a processor configured to determine instances of an unmodified vehicle-state reporting trigger occurring while a known driver is driving. The processor is further configured to determine whether a predefined incident occurs within a threshold measurement following determining the instance. The processor is also configured to aggregate data logging a plurality of determined instances of the reporting trigger and whether the predefined incident occurred within the threshold time or distance following the reporting trigger. Further, the processor is configured to define a user-specific modifier for the vehicle-state reporting trigger based on the aggregated data and change a reporting threshold from the vehicle-state reporting trigger to a modified vehicle-state reporting trigger modified by the user-specific modifier responsive to defining the modifier.
In a third illustrative embodiment, a system includes a processor configured to receive a driver profile for an identified driver. The processor is also configured to obtain vehicle-state reporting trigger modifiers associated with the profile. Further, the processor is configured to modify a set of predefined on-board reporting triggers based on the trigger modifiers. The processor is also configured to detect the occurrence of a modified on-board reporting trigger and issue a report responsive to the occurrence.
As required, detailed embodiments are disclosed herein; however, it is to be understood that the disclosed embodiments are merely illustrative and may be incorporated in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the claimed subject matter.
In the illustrative embodiment 1 shown in
The processor is also provided with a number of different inputs allowing the user to interface with the processor. In this illustrative embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24, screen 4, which may be a touchscreen display, and a BLUETOOTH input 15 are all provided. An input selector 51 is also provided, to allow a user to swap between various inputs. Input to both the microphone and the auxiliary connector is converted from analog to digital by a converter 27 before being passed to the processor. Although not shown, numerous vehicle components and auxiliary components in communication with the VCS may use a vehicle network (such as, but not limited to, a CAN bus) to pass data to and from the VCS (or components thereof).
Outputs to the system can include, but are not limited to, a visual display 4 and a speaker 13 or stereo system output. The speaker is connected to an amplifier 11 and receives its signal from the processor 3 through a digital-to-analog converter 9. Output can also be transmitted to a remote BLUETOOTH device such as PND 54 or a USB device such as vehicle navigation device 60 along the bi-directional data streams shown at 19 and 21 respectively.
In one illustrative embodiment, the system 1 uses the BLUETOOTH transceiver 15 to communicate 17 with a user's nomadic device 53 (e.g., cell phone, smart phone, PDA, or any other device having wireless remote network connectivity). The nomadic device (hereafter referred to as ND) 53 can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, tower 57 may be a Wi-Fi access point.
Exemplary communication between the ND 53 and the BLUETOOTH transceiver 15 is represented by signal 14.
Pairing the ND 53 and the BLUETOOTH transceiver 15 can be instructed through a button 52 or similar input. Accordingly, the CPU is instructed that the onboard BLUETOOTH transceiver will be paired with a BLUETOOTH transceiver in a nomadic device.
Data may be communicated between CPU 3 and network 61 utilizing, for example, a data-plan, data over voice, or DTMF tones associated with ND 53. Alternatively, it may be desirable to include an onboard modem 63 having antenna 18 in order to communicate 16 data between CPU 3 and network 61 over the voice band. The ND 53 can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, the modem 63 may establish communication 20 with the tower 57 for communicating with network 61. As a non-limiting example, modem 63 may be a USB cellular modem and communication 20 may be cellular communication.
In one illustrative embodiment, the processor is provided with an operating system including an API to communicate with modem application software. The modem application software may access an embedded module or firmware on the BLUETOOTH transceiver to complete wireless communication with a remote BLUETOOTH transceiver (such as that found in a nomadic device). Bluetooth is a subset of the IEEE 802 PAN (personal area network) protocols. IEEE 802 LAN (local area network) protocols include Wi-Fi and have considerable cross-functionality with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle. Another communication means that can be used in this realm is free-space optical communication (such as IrDA) and non-standardized consumer IR protocols.
In another embodiment, the ND 53 includes a modem for voice band or broadband data communication. In the data-over-voice embodiment, a technique known as frequency division multiplexing may be implemented when the owner of the nomadic device can talk over the device while data is being transferred. At other times, when the owner is not using the device, the data transfer can use the whole bandwidth (300 Hz to 3.4 kHz in one example). While frequency division multiplexing may be common for analog cellular communication between the vehicle and the internet, and is still used, it has been largely replaced by hybrids of Code Domain Multiple Access (CDMA), Time Domain Multiple Access (TDMA), Space-Domain Multiple Access (SDMA) for digital cellular communication. If the user has a data-plan associated with the nomadic device, it is possible that the data-plan allows for broadband transmission and the system could use a much wider bandwidth (speeding up data transfer). In yet another embodiment, the ND 53 is replaced with a cellular communication device (not shown) that is installed to vehicle 31. In still another embodiment, the ND 53 may be a wireless local area network (LAN) device capable of communication over, for example (and without limitation), an 802.11g network (i.e., Wi-Fi) or a Wi-Max network.
In one embodiment, incoming data can be passed through the nomadic device via a data-over-voice or data-plan, through the onboard BLUETOOTH transceiver and into the vehicle's internal processor 3. In the case of certain temporary data, for example, the data can be stored on the HDD or other storage media 7 until such time as the data is no longer needed.
Additional sources that may interface with the vehicle include a personal navigation device 54, having, for example, a USB connection 56 and/or an antenna 58, a vehicle navigation device 60 having a USB 62 or other connection, an onboard GPS device 24, or remote navigation system (not shown) having connectivity to network 61. USB is one of a class of serial networking protocols. IEEE 1394 (FireWire™ (Apple), i.LINK™ (Sony), and Lynx™ (Texas Instruments)), EIA (Electronics Industry Association) serial protocols, IEEE 1284 (Centronics Port), S/PDIF (Sony/Philips Digital Interconnect Format) and USB-IF (USB Implementers Forum) form the backbone of the device-device serial standards. Most of the protocols can be implemented for either electrical or optical communication.
Further, the CPU could be in communication with a variety of other auxiliary devices 65. These devices can be connected through a wireless 67 or wired 69 connection. Auxiliary device 65 may include, but are not limited to, personal media players, wireless health devices, portable computers, and the like.
Also, or alternatively, the CPU could be connected to a vehicle based wireless router 73, using for example a Wi-Fi (IEEE 803.11) 71 transceiver. This could allow the CPU to connect to remote networks in range of the local router 73.
In addition to having exemplary processes executed by a vehicle computing system located in a vehicle, in certain embodiments, the exemplary processes may be executed by a computing system in communication with a vehicle computing system. Such a system may include, but is not limited to, a wireless device (e.g., and without limitation, a mobile phone) or a remote computing system (e.g., and without limitation, a server) connected through the wireless device. Collectively, such systems may be referred to as vehicle associated computing systems (VACS). In certain embodiments, particular components of the VACS may perform particular portions of a process depending on the particular implementation of the system. By way of example and not limitation, if a process has a step of sending or receiving information with a paired wireless device, then it is likely that the wireless device is not performing that portion of the process, since the wireless device would not “send and receive” information with itself. One of ordinary skill in the art will understand when it is inappropriate to apply a particular computing system to a given solution.
In each of the illustrative embodiments discussed herein, an exemplary, non-limiting example of a process performable by a computing system is shown. With respect to each process, it is possible for the computing system executing the process to become, for the limited purpose of executing the process, configured as a special purpose processor to perform the process. All processes need not be performed in their entirety, and are understood to be examples of types of processes that may be performed to achieve elements of the invention. Additional steps may be added or removed from the exemplary processes as desired.
With respect to the illustrative embodiments described in the figures showing illustrative process flows, it is noted that a general purpose processor may be temporarily enabled as a special purpose processor for the purpose of executing some or all of the exemplary methods shown by these figures. When executing code providing instructions to perform some or all steps of the method, the processor may be temporarily repurposed as a special purpose processor, until such time as the method is completed. In another example, to the extent appropriate, firmware acting in accordance with a preconfigured processor may cause the processor to act as a special purpose processor provided for the purpose of performing the method or some reasonable variation thereof.
The problem with conventional tracking devices is that they do not accommodate different vehicle configurations. For example, while 4000 revolutions per minute (RPM) might be excessive for a light duty truck, it is a common engine speed for a high-performance vehicle. Devices configured to record a standard set of data may read a high engine speed in a high-performance vehicle as “bad performance,” when that speed is typical for such a vehicle and is not inappropriate use at all. But, in the interest of avoiding the cost and difficulty, if not impossibility, of individually configuring these devices, some companies using the devices have stuck to using a standard set of data and have accepted this sort of error as an acceptable cost of doing business. This may cause drivers to avoid using the devices, however, unless they are driving a vehicle to which the “stock” device configuration is relevant.
While devices that track vehicle and driver performance data in real time may be useful, these devices do not accommodate variations in vehicle configuration, and thus the devices may treat certain performance variables as being inappropriate, even if those variables represent suitable behavior for a given vehicle make, model or configuration.
Further, vehicles often come equipped with advanced control systems, to be engaged when driving situations dictate. Again, the onboard devices do not recognize these repurposings, and thus may read performance under such modes as “bad behavior” or “bad driving habits.”
For example, a light duty truck may normally not be operated at engine speeds in excess of 4000 RPM. This may be true for many vehicles, so a device-maker may install code to report data when engine speed exceeds 4000 RPM. For a performance sports car, this may be completely inappropriate, but the device may be vehicle-agnostic, and have no way of accommodating these changes. The device may also issue alerts at certain levels, which could become very annoying if a vehicle was frequently, but also appropriately, operated above a tolerance threshold.
In the truck example, the truck may have a “tow” setting, which can be engaged when towing heavy loads. This may keep the engine in a lower gear, and the engine may operate at higher speeds. If the “tow” setting is engaged, this could be completely appropriate behavior, but since the device has no way of knowing about the “tow” setting or accommodating the “tow” setting, the device may read all towing behavior as bad driving habits. This can cause a user to either stop using the vehicle for towing or stop using the device because of the perception (correctly observed) that the device does not accommodate intended use.
The illustrative embodiments allow for dynamic reconfiguration of the reporting settings for reporting diagnostic and other vehicle data. Reporting conditions can be set for individual vehicle makes, models and even configurations. Reporting conditions can also be varied based on feature engagement, allowing for one-off usage situations to be accommodated by the settings.
By allowing varied per-vehicle reporting settings that are dynamically updateable and configurable, based on, for example, changing perceptions of what is “safe” for a given vehicle, vehicle customizations and vehicle operating conditions (internal and external), the illustrative concepts and embodiments provide opportunities to improve the utility and functionality of diagnostic reporting systems. The novel, uncommon and atypical examples and concepts described herein demonstrate potential improvements achievable through use of those examples, concepts, and the like.
In this example, the process detects 201 that a report gathering device has been installed in an onboard diagnostic (OBD) port. In other examples, the vehicle may be equipped with onboard reporting (as a native function) or the process can detect an application executing that is requesting reporting on vehicle states. Since applications and devices may need vehicle states for a variety of reasons, the reporting tool provider may elect to identify when reporting variables should be tunable. Once the process knows that a tunable set of variables is appropriate, the process can retrieve 203 a vehicle identifier. This identifier can identify stock vehicle characteristics or a specific vehicle. In the stock characteristics example, the process may not provide quite the same level of refinement, but the process should still be able to report off more reasonable, vehicle-tuned trigger variables, than it would if a simple, universal set of trigger variables was used.
The process may also gather other data, such as custom aftermarket parts. Since some of these may not have a way of electronically registering with a vehicle (e.g., upgraded brake pads), the process may be reliant on a mechanic or installer to update a vehicle record. In an alternative version, the user could input the aftermarket parts, if the user wanted those parts to be considered for reporting tuning purposes. Since the part record will be uploaded, the process may only have to receive this data once.
The process then sends 205 the identifier and any additional part information to the remote configuration server. In another example, the process may have a predefined variable library onboard, from which the process could retrieve variables associated with various configurations for tuning reporting. This could be initially installed or installed after a first request was sent to a remote server. In still another example, the process could have a set of modifiers stored onboard (or remotely retrieved), representing how baseline triggers should be modified based on a certain set of variables. Storing at least some information, representing changes to triggers when existing features are engaged, for example, can save time when those temporary features are engaged, but is not a necessity.
The process, in this example, receives 207 a set of vehicle trigger configurations, that represent appropriate reporting conditions based on the specific vehicle. In this example, the process may identify an entire set, but in another example the process could have sent an initial set of baseline triggers (as provided by the device or app builder), and then the process could have tuned or replaced those triggers, based on vehicle features and options, as well as make and model, and that tuned set could be returned. The process then uses the received tuned reporting variables to reconfigure 209 reporting conditions and/or triggers for recording or reporting data.
If, though, the vehicle is Model Xi and Make Y (representing a first option package, for example, including larger wheels), the process may not have a specific configuration for the larger wheels. In this instance, the process may choose 305 the closest projected equivalent vehicle (likely Model X Make Y) and use the base configuration for the closest known vehicle.
The process could also make a record of the fact that a potentially sub-optimal package was chosen, and if there is a data upgrade in the future to reflect data tuned to the specific option package, the remote server could push an update to the vehicle or wait for another request and then provide the newly tuned triggers included in a response. Thus, the process can continually improve reporting triggers so that users feel confident that any tracking or reporting reflects data considerations designed for a vehicle (or close equivalent to) that they are driving.
In some examples, there may be additional aftermarket options, and this may be indicated in the received vehicle identifier or obtained from a vehicle record determinable by the identifier. If there is 309 other data available, the process may apply 311 a part conversion for that data. Or, in some other examples, the process may select a replacement value for the part.
If conversion is used, the process can vary a wide set of numbers associated with multiple vehicles based on an incremental improvement achieved with a part. That is, since the vehicles do not all have the same tuned baseline variable (see the example of the truck and sports car above), simply replacing a number because of an aftermarket part (e.g., upgraded tires) may not be universally appropriate or achieve the best results (in some cases, it may). In some instances, the part may represent a modifier, which may modify the tuned value (e.g., adjust 2500 RPM to 2750 RPM based on a 1.1 modifier) and thus the modification based on the part may be applicable across various vehicles. This can help prevent a manufacturer from having to test every single aftermarket part on every single make and model of vehicle on which it can be installed, but may still achieve a reasonable improved tunable variable value when the aftermarket part is installed.
Once any modifications, if any, have been made, the process may return 313 the configuration. This configuration may also include, for example, variances to trigger values that should be used when a temporary vehicle feature is engaged. The process can know which features are available based on the vehicle identifier, and thus the configuration can include variable values for use when those features are engaged (see, for example, the preceding towing example).
If the process previously received override data (replacement data) or a modifier 403 when the trigger configuration data was received, the process may use that saved modification or replacement data to replace the typical trigger, responsive to the engagement of the feature. So, for example, if the towing was engaged, the process may replace RPM measurements with higher RPM measurements as suitable measurements, or at least corresponding to certain gears, in accordance with behavior expected and appropriate when towing a load with the tow feature engaged.
If the process lacks an onboard modifier, the process may send 407 the fact of the feature engagement to a remote server, requesting a modifier or replacement corresponding to the feature. Not all features will have modifiers, and some modifiers will only modify a limited number of trigger variables. If there is a modifier or replacement value for the engaged feature, the process receives 409 this modifier and applies the received replacement or trigger modifier.
In this example, the process detects 501 proximity to a specific POI or a POI of a given type. The granularity of this detection can be triggered based on the data available, and in some instances geo-fences around areas (neighborhoods, schools, etc.) may be used as a proxy for a POI. This is a mere example of the sort of dynamic trigger adjustment that can be enabled by the illustrative embodiments, by making variable values available, the process can adjust those values off of a variety of environmental external variables (e.g., road type, road conditions, weather, POI, etc.) as well as internal variables (single passenger, multiple passengers, children present, etc.).
In this example, the process detects the POI as a temporary situation, and the process has in indicator that POIs in general, or POIs of a type, or a specific POI, has an adjusted vehicle data reporting variable potentially associated therewith. For example, the process could be configured to report based on schools, a specific school, or anything classified as a government building.
The process also determines 503 if there is an onboard modification associated with the POI. The onboard modification could be included in a basic parameter set that is defined for common POIs, could be included in a set previously obtained for a particular POI or POI type, etc.
If there is a parameter set defined for a particular POI onboard, the process can apply a variance to one or more vehicle data reporting trigger values associated with that POI (e.g., exhaust type, speed, etc.) The variance or adjustment can include replacement of a trigger value or adjustment of a trigger value, as previously explained herein.
The processor can also send a request, reporting 505 the POI, to a remote server if there is no onboard adjustment. Not all POIs may require adjustment, and sometimes the adjustment may be tuned to timing (e.g., school-based adjustments may not apply on nights and weekends). If the process receives 509 a parameter set or variance responsive to sending the POI information, the process can add 511 the data to a local set (for later use if the POI or other temporary situation is again encountered) and the process can then adjust 507 the trigger variable(s) based on the value(s) or adjustment(s).
While it is possible to configure a reporting system to react to a particular vehicle or location, the process may also configure a system based on additional real-time information. For example, the process may consider a time of year, weather, or other environmental conditions. The process may further relate driver skill levels to values, such that more skilled drivers are given more variance before an anomalous condition is reported. In a similar manner, the process could set tighter boundaries for a less skilled driver. If there was visual or audible feedback if a boundary parameter was crossed, for example, the feedback could cause a less skilled driver to drive more carefully, and/or let a more skilled driver that even the reasonable limits of that person's skill had been possibly reached.
If a driver knows that the system reacts to their particular parameters, and to what is considered “safe” driving under current conditions, they may be more likely to pay attention to any warnings or reports. This is as opposed to systems which rely on “stock” reporting, where many drivers may dismiss the results because they are overbroad, overly cautious and/or not tuned for that driver or at least the current environment. Even factors such as road conditions could be considered, where a new, safe road could be given more lenience than a broken old road, a road full of potholes, or an unpaved road.
The process and similar processes can vary configurations by driver skill, environment, etc. Driver skill can include both generalized skill levels (e.g., new vs. experienced) and specific skill sets (e.g., winter driver, off-road driver, SUV driver, etc.). So, for example, when a sedan driver who lived in a warm climate drives a sedan in the warm climate, they may be considered an experienced driver with sedan handling skills. When the same driver buys a new SUV and drives it in snow, they may be considered a “new” driver, either as a class (e.g., sedan, compact, SUV, etc.) or with respect to certain constraints (e.g., braking, speeds, turn speeds, etc.). Since highly customized driver profiles can be achieved with a minimal degree of effort, results of reporting can be significantly improved that recognize both driver and/or conditional effects and expectations.
Development of a driver profile to a modified version from a standard version can occur by detecting unmodified reporting conditions and then determining if a driver continues to successfully drive (for a time or distance, for example) without incident. The incident can be correlated to the detected condition, and does not always have to be as drastic as an accident. For example, if high-acceleration followed by hard braking is considered “unsafe,” the system could detect occurrences of high-acceleration and when hard braking subsequently occurred. So, for example, if limited or no hard-braking occurred following high acceleration for a time period, the system might modify what it considers to be “reportable high-acceleration” for a given driver.
The process then determines if the current driver is a “standard” driver 603. In this example, a standard driver is a person of intermediate skill, or a daily commuter with less than 10 years driving experience, for example. In another example, a driver may only be a “standard” driver for a limited time until a baseline set of parameters is applied to that driver (by an insurer, for example).
If there are any particular modifiers to be applied to a driver, the process applies 605 the modifiers as indicated by a driver profile. For example, a certain driver may be a hard braker, but may also have never been in an accident for 20 years, so hard braking for an “experienced” driver may be less sensitive to reporting, or, in another example, that person's profile may indicate that they have a personal variance for hard-braking reporting because they still tend to avoid accidents (e.g., tending to indicate that the hard braking is not because of imminent collision, but rather a driving style).
The process may also apply vehicular modifiers as discussed above, tuning the reporting to the particular vehicle being driven. A further step may include applying environmental modifiers. Using the hard braking example, the hard braker may be given relaxed reporting parameters under dry conditions, but may have more stringent reporting parameters under wet or snowy conditions. Even if the hard braker tends to avoid accidents in these conditions, the higher likelihood of incident may warrant stricter reporting. Or, in another example, city driving may warrant stricter reporting conditions, because of the higher likelihood of pedestrians, animals, bikers, and other vehicles. Thus, environments can separately and/or coordinately impact reporting parameters.
In this situation shown, the process now determines if the detected condition should be reported 611. In some instances, it may be reasonable to pre-load a set of variables and configurations when a drive begins or when an environment changes, but if there is a large set of constantly changing parameters, the process may want to load the data live (as shown) when a given condition is detected. This is a tradeoff between data usage vs accuracy, so each provider can tune the system as appropriate.
If the report is still appropriate, the process reports 613 the condition. If the report is not appropriate, because of the modifiers and/or configuration, the process still saves 615 a log. While not necessary, the log can help determine if reporting was too lax for a given driver and/or a certain condition/environment. That is, if the hard braking were not reported in winter, and the hard braker had an accident, the process may change the reporting to stricter conditions under winter weather. Sufficient changes like this on multiple profiles can cause a change in an underlying determination (e.g., all hard brakers receive stricter guidelines in winter, eventually). Reporting based on logs can be done within a threshold time or distance from logging the condition (as opposed to reporting a condition that occurred days or miles before, for example).
If a profile exists 703 for a driver, the profile in this example will include a general level of skill for the driver and/or any special characteristics, if those are to be considered. That could include, for example, professional experience, load experience (e.g., trailering), condition experience, environment experience, etc. The generalized skill level could be, for example, without limitation, new driver, 10 years experience, 20 years experience, elderly driver, etc. The process will load 705 the existing profile for a driver that already has a profile, and can use the conditional indicators included with that profile to make a driver-specific reporting configuration modification.
If there is not currently a profile for a driver, the process may create 707 a profile to be associated with the driver. This profile can be stored onboard, remotely (e.g., the cloud), on a mobile device, etc. The profile may default 711 to a “standard” profile with no special skills, but if an override 709 command is detected, the process can use input data to modify 713 the profile. For example, a fleet manager or an insurance company may load a set of predefined data that indicates driver skill level both generally and/or with respect to specific variables.
For the given condition, the process may access 803 a driver profile and determine if there are any specialized variable modifiers or values 805 associated with the given condition. In one example, the driver may simply be rated as experienced or new under the condition, and a full set of modified values associated with the rating may apply. In another example, the driver may have individual modifiers based on experience with some or all of the actual maneuvers considered by the reporting system. If there is no modifier or value, the process may load 809 a baseline value or modifier. If there is a specific modifier, the process may load 807 the particular modifier or value.
Two possible ways (non-exhaustively) of implementing a tailored reporting system include using strict defined values and modified values. Both will be described below, along with some of the variances in the results.
In a defined value system, various variables may each have a reporting value associated therewith. For example, in a system that is not tailored at all, an RPM maximum for an automatic vehicle may be 3500. This can be exceeded by fast acceleration or by many high performance vehicles, so if a degree of tuning is introduced, a high performance vehicle may have a new maximum defined value of 4500. Defined values are easy to accommodate and fast to implement, because they do not need to consider as many factors. For example, by simply observing a number of the high performance models over a short period of time, it may be observed that the 4500 RPM value makes a more reasonable threshold. The same can be said for any number of values related to vehicles, trim, components, user skill levels, weather/environment, etc.
If more nuance and tailoring is of interest, however, a decision must be made about tradeoffs between a defined value system and a modified value system. In a modified value system, one or more variables (weather, skill, trim, etc.) may have a modifier associated therewith, instead of a defined value. That is, instead of saying a high performance vehicle RPM value should be 4500, the system may instead apply a 1.5× modifier. This way, if a baseline 3000 RPM value is varied, the modified high performance value also varies.
The modified value system also works better with multiple variables. If “snow” had an RPM value of 2400 associated therewith, and high performance had a value of 4500 associated therewith, and a user was driving a high-performance vehicle in snow, it is not always clear which value should be used. A low risk scenario would use the 2500, but that could irritate or falsely report danger for high skilled drivers in high performance vehicles. On the other hand, 4500 RPM might not be safe in snow, even in a high performance vehicle. Using the modified value system, if snow has an RPM modifier of 0.8 and high performance has an RPM modifier of 1.5, then combined the new max RPM before reporting for the high performance vehicle in snow would be 3000×0.8×1.5=3600. This is still “better” than the stock value, but also accommodates the snow.
Either system can be used, each has tradeoffs and it will be appreciated by a implementer which is the better system for a given implementation (e.g., insurance companies may want the “lower risk” system whereas a logistics manager seeking to maximize speed while maintaining safety may want to “push the envelope”).
A third option is a blended system, which can work based on modified values, but certain variables may have absolutes. For example, if a high performance vehicle had an RPM modifier of 1.5, and a skilled driver received a 1.2 modifier for all values, then in the snow example the new RPM maximum would be 4320. At the same time, it may be determined that acceleration in that particular vehicle in snow may be dangerous above 4000 RPM, regardless of driver, and so “snow” may have a maximum value of 4000 associated therewith. Thus, regardless of how many positive values are associated with a driver, any RPM over 4000 in that vehicle in snow will be reported. This blended system can leverage good parts of both solutions, and while still not necessarily the “lowest risk” system of reporting, it may more realistically accommodate expected behaviors.
Here, the process detects 903 a given condition, which may be a somewhat persistent condition such as weather, city/country-side, traffic levels, highway/surface roads, etc. Since the condition is likely to persist (how long may be known or approximated from a planned route and/or additional data such as weather patterns or city-size), it may be reasonable to preload a value or modifier (or multiples of either) associated with a given condition.
The process loads a baseline for a “standard” driver, in case there is no profile or modified value present. The baseline value is then sent 907 to a process such as that of
Then, in this example, the vehicle receives 909 the modified values and/or modifiers, and uses the received data to retune 911 the parameters. The resulting parameters are now tuned to the condition and reporting will be triggered off of the tuned values. At the same time, if there is an incident 913 (e.g., an accident), the process can report 915 the incident along with current conditional settings, which can help modify and tune the system for future usage. The feedback can be used to tune values and modifiers so that conditions approach optimal values over time, while still accommodating for trim, skill, conditions, etc. instead of using a single trigger per condition approach.
The illustrative embodiments allow for dynamic redefinition of vehicle data reporting trigger values, so that more accurate vehicle data reporting can be obtained. The data can be tuned to a vehicle and to situations, so that driver behavior can be tracked and modeled in a manner that more accurately reflects whether or not the behavior was optimal or desired.
While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined in logical manners to produce situationally suitable variations of embodiments described herein.
This application is a continuation of U.S. application Ser. No. 16/117,283 filed Aug. 30, 2018, the disclosure of which is hereby incorporated in its entirety by reference herein.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16117283 | Aug 2018 | US |
| Child | 17398078 | US |
