System and method for evaluating driver performance using crowdsourced data
By using vehicle sensor monitoring and telematics technology, driver performance can be comprehensively evaluated, solving the problem of limited data in traditional systems and enabling more accurate insurance rate setting and driver behavior improvement.
Patent Information
- Application Number
- CN202110506329.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-08-14
- Filing Date
- 2021-05-10
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2041-05-10
AI Technical Summary
Traditional driver monitoring systems provide limited data through the OBD port, making it impossible to comprehensively monitor driver performance, especially collision warning data, which leads to inaccurate insurance rates and driver assessments.
By monitoring various driver behaviors through vehicle sensors, such as following distance, lane changes, and sudden acceleration, and combining this with telematics technology, driver performance is reported to the central office to facilitate insurance rate setting and driver training.
It provides a more comprehensive assessment of driver performance, helping insurance companies set more accurate rates and providing drivers with real-time feedback to improve driving habits and enhance safety.
Smart Images

Figure CN114132332B_ABST
Abstract
Description
Background Art
[0001] The information provided in this section is for the purpose of generally presenting the background of the present disclosure. To the extent described in this section, the work of the presently named inventors and aspects of the description that may not constitute prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art to the present disclosure.
[0002] The driving performance of a particular driver may be valuable to the driver's employer, especially if the driver operates a vehicle owned by the employer. Driver performance is useful, for example, in warning or penalizing reckless drivers, setting insurance rates, and assessing insurability. These actions may rely on recorded driving history and aggregated category statistics.
[0003] Traditional driver monitoring systems generate data by monitoring the on-board diagnostic (OBD) port, which provides only limited information. For example, the OBD port may only monitor driving speed, which may be correlated to local speed limits to determine a particular driver's speeding habits. Current systems may not have access to other useful data from the vehicle, such as collision warning data. Summary of the invention
[0004] One aspect of the present disclosure is to provide a driver monitoring system that is configured to monitor the performance of a driver of a first vehicle system that wirelessly communicates with the driver monitoring system. The driver monitoring system includes: a vehicle database that includes multiple vehicle records associated with multiple vehicle systems; and a vehicle server that includes a driver behavior module, which is configured to receive first event data captured by multiple sensors in the first vehicle system from the first vehicle system. The first event data includes a first event time and a first event location. The server identifies a first driver behavior associated with the first event data. The vehicle server is also configured to use the first event time and the first event location to identify multiple neighboring vehicles near the first vehicle system in the vehicle database, and determine an average value associated with the first driver behavior from the vehicle records associated with the multiple neighboring vehicles.
[0005] In one embodiment, the driver monitoring system is configured to compare the first driver behavior to a threshold value and, in response to the comparison, send a warning message to the driver.
[0006] In another embodiment, the driver monitoring system sends a warning message if the driver is a customer of the insurance provider.
[0007] In yet another embodiment, the threshold is a speed limit associated with a road determined by the first event location.
[0008] In yet another embodiment, the driver monitoring system is configured to determine whether the first driver behavior exceeds an average by a threshold.
[0009] In another embodiment, in response to determining that the first driver behavior exceeds the average by more than a threshold, the driver monitoring system sends a warning message to the driver.
[0010] In yet another embodiment, the driver monitoring system sends a warning message if the driver is a customer of the insurance provider.
[0011] In another embodiment, the vehicle server also includes a behavior characterization module and a risk assessment module, the behavior characterization module is configured to receive a first driver behavior from the driver behavior module and characterize the first driver behavior as at least one of a plurality of behavior categories, the risk assessment module is configured to analyze the driver behavior characterized by at least one of the plurality of behavior categories and determine a driver profile from the at least one characterized driver behavior, and the driver profile may include a risk assessment of the driver for the vehicle system.
[0012] In one embodiment, in response to determining that the first driver behavior exceeds a threshold, the driver monitoring system increases an insurance premium associated with the driver.
[0013] In another embodiment, in response to determining that the first driver behavior exceeds the threshold, the driver monitoring system sends a message to an owner of the vehicle system notifying the owner that the driver has exceeded the threshold.
[0014] Another aspect of the present disclosure is to provide a method for monitoring the performance of a driver of a first vehicle system that wirelessly communicates with a driver monitoring system. The method includes: i) storing a plurality of vehicle records associated with the plurality of vehicle systems in a vehicle database; ii) receiving, in a vehicle server of the driver monitoring system, first event data captured by a plurality of sensors in the first vehicle system from the first vehicle system, the first event data including a first event time and a first event location; iii) identifying a first driver behavior associated with the first event data; iv) using the first event time and the first event location to identify a plurality of neighboring vehicles near the first vehicle system in the vehicle database; and v) determining an average value associated with the first driver behavior from the vehicle records associated with the plurality of neighboring vehicles.
[0015] In one embodiment, the method further includes comparing the first driver behavior to a threshold value, and in response to the comparison, sending a warning message to the driver.
[0016] In another embodiment, if the driver is a customer of the insurance provider, a warning message is sent.
[0017] In yet another embodiment, the threshold is a speed limit associated with a road determined by the first event location.
[0018] In yet another embodiment, the method further includes determining whether the first driver behavior exceeds the average by a threshold.
[0019] In another embodiment, the method further includes sending a warning message to the driver in response to determining that the first driver behavior exceeds the average by more than a threshold.
[0020] In yet another embodiment, if the driver is a customer of the insurance provider, a warning message is sent.
[0021] In another embodiment, the method further includes: i) characterizing the first driver behavior as at least one of a plurality of behavior categories; and ii) analyzing the driver behavior characterized by at least one of the plurality of behavior categories, and determining a driver profile from at least one characterized driver behavior, wherein the driver profile may include a risk assessment of the driver to the vehicle system.
[0022] In one embodiment, the method further includes increasing an insurance premium associated with the driver in response to determining that the first driver behavior exceeds a threshold.
[0023] In another embodiment, the method further includes, in response to determining that the first driver behavior exceeds the threshold, sending a message to an owner of the vehicle system notifying the owner that the driver has exceeded the threshold.
[0024] The present invention also includes the following scheme:
[0025] Solution 1. A driver monitoring system configured to monitor the performance of a driver of a first vehicle system in wireless communication with the driver monitoring system, the driver monitoring system comprising:
[0026] a vehicle database comprising a plurality of vehicle records associated with a plurality of vehicle systems; and
[0027] a vehicle server including a driver behavior module configured to receive, from the first vehicle system, first event data captured by a plurality of sensors in the first vehicle system, the first event data including a first event time and a first event location, and the driver behavior module configured to identify a first driver behavior associated with the first event data;
[0028] Wherein, the vehicle server is also configured to use the first event time and the first event location to identify multiple neighboring vehicles near the first vehicle system in the vehicle database, and determine an average value associated with the first driver behavior from vehicle records associated with the multiple neighboring vehicles.
[0029] Option 2. A driver monitoring system according to Option 1, wherein the driver monitoring system is configured to compare the first driver behavior with a threshold value and, in response to the comparison, send a warning message to the driver.
[0030] Option 3. The driver monitoring system of Option 2, wherein the driver monitoring system sends the warning message if the driver is a customer of an insurance provider.
[0031] Embodiment 4. A driver monitoring system according to Embodiment 2, wherein the threshold is a speed limit associated with a road determined by the first event location.
[0032] Embodiment 5. The driver monitoring system of embodiment 1, wherein the driver monitoring system is configured to determine whether the first driver behavior exceeds the average value by a threshold value.
[0033] Embodiment 6. The driver monitoring system of embodiment 5, wherein in response to determining that the first driver behavior exceeds the average value by more than the threshold value, the driver monitoring system sends a warning message to the driver.
[0034] Embodiment 7. The driver monitoring system of embodiment 6, wherein the driver monitoring system sends the warning message if the driver is a customer of an insurance provider.
[0035] Solution 8. According to the driver monitoring system of Solution 6, the vehicle server further includes:
[0036] a behavior characterization module configured to receive the first driver behavior from the driver behavior module and characterize the first driver behavior as at least one of a plurality of behavior categories; and
[0037] A risk assessment module is configured to analyze driver behavior characterized by at least one of the plurality of behavior categories and determine a driver profile from the at least one characterized driver behavior, the driver profile being able to include a risk assessment of the driver to the vehicle system.
[0038] Embodiment 9. A driver monitoring system according to embodiment 8, wherein in response to determining that the first driver behavior exceeds the threshold, the driver monitoring system increases an insurance premium associated with the driver.
[0039] Option 10. A driver monitoring system according to Option 8, wherein, in response to determining that the first driver behavior exceeds the threshold, the driver monitoring system sends a message to an owner of the vehicle system, the message notifying the owner that the driver has exceeded the threshold.
[0040] Embodiment 11. A method for monitoring performance of a driver of a first vehicle system in wireless communication with a driver monitoring system, the method comprising:
[0041] storing a plurality of vehicle records associated with a plurality of vehicle systems in a vehicle database;
[0042] In a vehicle server of the driver monitoring system, receiving, from the first vehicle system, first event data captured by a plurality of sensors in the first vehicle system, the first event data including a first event time and a first event location;
[0043] identifying a first driver behavior associated with the first event data;
[0044] identifying a plurality of neighboring vehicles in the vehicle database proximate to the first vehicle system using the first event time and the first event location; and
[0045] An average value associated with the first driver behavior is determined from the vehicle records associated with the plurality of neighboring vehicles.
[0046] Option 12. The method according to Option 11 further includes comparing the first driver behavior with a threshold value, and sending a warning message to the driver in response to the comparison.
[0047] Option 13. The method according to Option 12, wherein the warning message is sent if the driver is a customer of an insurance provider.
[0048] Option 14. The method of Option 12, wherein the threshold is a speed limit associated with a road determined by the first event location.
[0049] Option 15. The method according to Option 10 also includes determining whether the first driver behavior exceeds the average value by a threshold.
[0050] Option 16. The method according to Option 15 further includes sending a warning message to the driver in response to determining that the first driver behavior exceeds the average value by more than the threshold.
[0051] Option 17. The method according to Option 16, wherein the warning message is sent if the driver is a customer of an insurance provider.
[0052] Scheme 18. The method according to Scheme 16 further comprises:
[0053] characterizing the first driver behavior as at least one of a plurality of behavior categories; and
[0054] A driver behavior characterized by at least one of the plurality of behavior categories is analyzed, and a driver profile is determined from the at least one characterized driver behavior, the driver profile being able to include a risk assessment for the driver of the vehicle system.
[0055] Option 19. The method according to Option 18 further includes increasing an insurance premium associated with the driver in response to determining that the first driver behavior exceeds the threshold.
[0056] Option 20. The method according to Option 18 further includes, in response to determining that the first driver behavior exceeds the threshold, sending a message to an owner of the vehicle system, the message notifying the owner that the driver has exceeded the threshold.
[0057] Further areas of applicability of the present disclosure will become apparent from the detailed description, the claims and the accompanying drawings.The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0058] The present disclosure will become more fully understood from the detailed description and accompanying drawings, in which:
[0059] Figure 1 is an overview of a driver monitoring system according to an embodiment of the present disclosure.
[0060] Figure 2 is a functional block diagram of an exemplary vehicle system including a driver monitoring system in accordance with the principles of the present disclosure.
[0061] Figure 3 The flow of sensor information from a vehicle system to a vehicle communication server is shown in accordance with the principles of the present disclosure.
[0062] Figure 4 is a flow chart illustrating sensor data processing operations in a vehicle system according to the principles of the present disclosure.
[0063] Figure 5 is a flow chart illustrating driver alert operation in a vehicle system according to the principles of the present disclosure.
[0064] Figure 6 is a flow chart illustrating evaluation of driver performance in a server according to the principles of the present disclosure.
[0065] Fig. 7A and 7B is a flow chart illustrating evaluating driver performance in a vehicle communication server using crowd-sourced data from multiple vehicle systems in accordance with the principles of the present disclosure.
[0066] Among the drawings, reference numerals may be repeated to identify similar and / or identical elements. DETAILED DESCRIPTION
[0067] Advanced onboard diagnostic and communication systems (e.g., GM's OnStar) enable vehicle manufacturers to offer driver monitoring systems that execute algorithms for evaluating driver performance, setting insurance rates, and assessing the driver's insurability based on a greater number of parameters than are available through the OBD port.
[0068] The present disclosure describes a system for monitoring one or more driver habits, such as following distance (or tailgating), lane changes, sudden acceleration, sudden deceleration, swerving, etc. The disclosed system monitors information from multiple vehicle sensors to assess the driver's tailgating habits. The driver monitoring system uses telematics technology to report the monitored information to a central office (e.g., employer, insurance company, etc.) for subsequent use in, for example, disciplining or training the driver or setting insurance rates.
[0069] Advantageously, the unique disclosed system uses vehicle sensors to identify a driver's tailgating habits, speeding habits, lane changing habits, and uses the habit data to assess driver performance and for insurance purposes. The disclosed system may do one or more of the following:
[0070] a) monitor and report the number of collision warning alerts generated by the collision warning system;
[0071] b) monitoring variables provided by the collision warning system to identify the driver's following distance (tailgating) habits;
[0072] c) Periodically transmit the following distance data to the server for analysis and processing;
[0073] d) In response to the following distance metric falling below a threshold, the server may send a warning to the driver that insurance rates may increase.
[0074] e) in response to the following distance metric remaining below a threshold for longer than a predetermined time, the server may initiate an increase in insurance premiums for the driver;
[0075] f) Following distance metrics may include: average predicted stopping time, average following distance and / or a combination factor of vehicle speed, following distance and predicted stopping time;
[0076] g) For drivers who are currently uninsured, when the following distance metric is below a threshold for a predetermined period of time, the server may provide the driver with an insurance product;
[0077] h) Collect camera / sensor data for the time before and after the collision warning is activated, send the data to a server, and alert the vehicle owner of the collision warning activation.
[0078] i) data can be retrieved by the vehicle owner to review or replay events (i.e., gaming cinematic mode);
[0079] j) Contacting the driver directly via the telematics system (direct communication mode) without providing any option to answer or disconnect. For example, the server warns the owner of risky driving behavior and connects the owner of the vehicle operator via the telematics system. The driver cannot ignore this because the owner's voice is played on the vehicle's speakers. This action can be performed only when the vehicle is driving in a safe environment (i.e., when the vehicle is ignited, when the vehicle is moving in a stable state, in a non-crowded environment, not reversing, etc.).
[0080] In an advantageous embodiment, the present disclosure describes a system for monitoring driver habits based on crowdsourced data from two or more vehicles within a predetermined distance of each other. The driver monitoring system is configured to receive vehicle data from the plurality of vehicles and calculate an indicator related to a measure of driver performance and transmit the information to one or more persons who may be associated with the received vehicle data.
[0081] As an example, the disclosed driver monitoring system can collect crowdsourced data from multiple vehicles to determine average vehicle speed and other driving behaviors. The driver monitoring system monitors information received from the vehicle computing system to evaluate the speed of two or more vehicles within a predetermined distance. This information can be reported to the owner of the vehicle or an insurance provider to set insurance rates.
[0082] The driver monitoring system may perform one or more of the following processes: i) receiving vehicle speed data from two or more vehicles within a predetermined distance; ii) comparing the speed data from the two or more vehicles to a predetermined threshold; iii) reporting to the owner or insurance provider if at least one vehicle exceeds the threshold; and iv) executing a vehicle algorithm that periodically transmits specific vehicle data to a server for analysis and processing.
[0083] In response to the first vehicle speed or the speed limit of the road segment traveled by the first vehicle and crowdsourced data from nearby vehicles, the server can determine whether the first vehicle is within an acceptable driving behavior parameter threshold and send a warning to the driver that the insurance rate may increase. In response to the driving behavior parameter threshold, the server can initiate an increase in the insurance premium for the driver.
[0084] The driver monitoring system uses crowdsourced vehicle data from other vehicles near the first vehicle to evaluate driver performance. Each vehicle sends location, time, vehicle speed and speed limit information to the server. The server can gather data from those vehicles in the same location to obtain statistics for the road section. This allows the server to evaluate the driver based on the driving mode that exists at the location at that time. The server can evaluate the driver relative to other vehicles traveling at the location at the same time, and calculate the driver behavior metric based on the crowdsourced data. If the driver operates the vehicle significantly differently from other drivers at the location, the server can modify the driver behavior metric. The driver behavior metric may be useful for indicating whether the driver is driving faster or slower than nearby vehicles or moving similarly to surrounding vehicles.
[0085] Figure 1 1 is an overview of a driver monitoring system 5 for disabling vehicle functions according to an embodiment of the present disclosure. The driver monitoring system 5 includes a plurality of vehicle systems 10A, 10B, and 10C, a vehicle communication server (VCS) 40, and a vehicle backend database (DB) 45. Each of the vehicle systems 10A-10C includes a wireless access point (AP) 15A, 15B, and 15C, which enables the vehicle systems 10A-10C to communicate with the VCS 40 via an IP network 30 (e.g., the Internet) and a wireless access point 20. In a typical case, the wireless access point 20 is a base station of a cellular network, and the wireless access point 15 in the vehicle system 10 is a cellular mobile transceiver.
[0086] According to the principles of the present disclosure, a vehicle communication server (VCS) 40 may send instructions to vehicle systems 10A-10C via wireless communication links 25A-25C, respectively, that securely retrieve selected vehicle data from a plurality of vehicle sensors using authentication and integrity protocols. For example, the VCS 40 may send a digitally signed cryptographic token to the AP 15A via the wireless communication link 25A to enable a control module in the vehicle system 10A to collect sensor data and upload the sensor data to the VCS 40 via the wireless communication link 25A.
[0087] Figure 21 is a functional block diagram of an exemplary vehicle system 10 (i.e., any of the vehicle systems 10A-10C) including a driver monitoring system according to the principles of the present disclosure. Although the present disclosure shows and describes the vehicle system 10 for a hybrid vehicle, the present disclosure is also applicable to non-hybrid vehicles that include only an internal combustion engine. Although the present disclosure uses a vehicle as an exemplary embodiment, the present disclosure is also applicable to non-automotive embodiments, such as boats and aircraft.
[0088] The engine 102 combusts an air / fuel mixture to produce drive torque. An engine control module (ECM) 106 controls the engine 102 based on one or more driver inputs. For example, the ECM 106 may control actuation of engine actuators such as an electronically controlled throttle, one or more spark plugs, one or more fuel injectors, a valve actuator, a camshaft phaser, an exhaust gas recirculation (EGR) valve, one or more intake air flow boost devices, and other suitable engine actuators.
[0089] The engine 102 may output torque to a transmission 110. A transmission control module (TCM) 114 controls operation of the transmission 110. For example, the TCM 114 may control gear selection within the transmission 110 and one or more torque transmitting devices (eg, a torque converter, one or more clutches, etc.).
[0090] The vehicle system 10 may include one or more electric motors. For example, the electric motor 118 may be implemented within the transmission 110, such as Figure 2 The electric motor may be used as a generator or a motor at a given time. When used as a generator, the electric motor converts mechanical energy into electrical energy. The electrical energy may charge the battery 126 via a power control device (PCD) 130. When used as a motor, the electric motor generates torque that supplements or replaces the torque output by the engine 102. Although an example of an electric motor is provided, the vehicle may include zero or more than one electric motor.
[0091] A power inverter control module (PIM) 134 may control the electric motor 118 and the PCD 130. The PCD 130 applies power (e.g., DC) from the battery 126 to the electric motor 118 (e.g., AC) based on a signal from the PIM 134, and the PCD 130 provides power output by the electric motor 118 to, for example, the battery 126. The PIM 134 may be referred to as a power inverter module (PIM) in various implementations.
[0092] The steering control module 140 controls the steering / rotation of the vehicle's wheels, for example, based on driver rotation of a steering wheel within the vehicle and / or steering commands from one or more vehicle control modules. A steering wheel angle sensor (SWA) monitors the rotational position of the steering wheel and generates SWA 142 based on the position of the steering wheel. As an example, the steering control module 140 can control vehicle steering via an EPS motor 144 based on the SWA 142. However, the vehicle may include another type of steering system. An electronic brake control module (EBCM) 150 can selectively control the vehicle's brakes 154.
[0093] The modules of the vehicle can share parameters via a controller area network (CAN) 162. The CAN 162 may also be referred to as a vehicle area network. For example, the CAN 162 may include one or more data buses. A given control module may make various parameters available to other control modules via the CAN 162.
[0094] The driver input may include, for example, an accelerator pedal position (APP) 166 that may be provided to the ECM 106. A brake pedal position (BPP) 170 may be provided to the EBCM 150. A position 174 of the park, reverse, neutral, drive lever (PRNDL) may be provided to the TCM 114. An ignition state 178 may be provided to a body control module (BCM) 180. For example, the ignition state 178 may be input by the driver via an ignition key, button, or switch. At a given time, the ignition state 178 may be one of off, auxiliary, run, or start.
[0095] According to an exemplary embodiment of the present disclosure, the vehicle system 10 further includes an advanced computing module 185, a sensor module 188, a map module 190, and a wireless transceiver (XCVR) module 195. Figure 2 In the wireless transceiver module 195 corresponds to Figure 1 The wireless access points 15A-15C in the vehicle system 10. The sensor module 188 may include multiple sensors that support, for example, basic cruise control, full-speed range adaptive cruise control, and / or semi-autonomous or truly autonomous driving. These sensors may include, but are not limited to, an onboard GPS receiver, multiple radar detectors, and multiple cameras that detect objects (e.g., other vehicles) near the vehicle system 10, a light detection and ranging (LiDAR) system, a wheel speed sensor, a steering wheel angle (SWA) sensor, multiple accelerometers, and the like.
[0096] The sensors in the sensor module 188 can be used to detect a number of driver events. For example, radar detectors and cameras can determine following distance (i.e., potential tailgating). Cameras can detect lane markings and determine if and how often the vehicle system 10 changes lanes, drifts through the center of the road into oncoming traffic, drifts onto the shoulder of the road, lane centering performance, etc. Accelerometers can detect sudden acceleration, sudden deceleration (i.e., braking), and sudden or exaggerated lateral movement, indicating a sudden turn or sharp turn.
[0097] In the vehicle system 10, an embedded microprocessor executing program instructions in an associated embedded memory controls the operation of each electronic vehicle subsystem. Hereinafter, the microprocessor and memory in each subsystem may be collectively referred to as an electronic control unit (ECU) module. The steering control module 140, the engine control module 106, the sensor module 188, and the electronic brake control module 150 are all examples of vehicle subsystems. A dedicated embedded ECU module controls each of these vehicle subsystems.
[0098] The advanced computing module 185 comprises a high-performance computing platform that controls many high-level functions and low-level functions of the vehicle system 10. In a typical embodiment, the advanced computing module 185 can be implemented as a microprocessor and associated memory. Like the ECU module in the vehicle subsystem, the advanced computing module 185 also executes a core program that controls the overall operation of the advanced computing module 185.
[0099] In accordance with the principles of the present disclosure, the advanced computing module 185 uses information from the sensor module 188 (e.g., wheel speed data, steering wheel angle sensor data, brake status data, LiDAR system data, radar data, camera images, GPS data, accelerometer data, etc.) to determine the speed, direction, and position of the vehicle system 10. The advanced computing module 185 uses the information used to send commands to, for example, the steering control module 140, the engine control module 106, and the electronic brake control module 150 to control the speed, braking, and / or direction of the vehicle system 10. The advanced computing module 185 is also responsible for communicating with the VCS 40 and uploading vehicle sensor data requested by the VCS 40 in order to monitor and evaluate driver performance.
[0100] Figure 3The flow of sensor information from the vehicle system 10 to the vehicle communication server (VCS) 40 according to the principles of the present disclosure is shown. In the vehicle system 10, the advanced computing module 185 can poll multiple sensors for sensor data useful for evaluating the performance of the driver. For example, the vehicle sensor 311 can be one or more accelerometers, the vehicle sensor 312 can be a wheel speed sensor, and the vehicle sensor 313 can be a vehicle camera. The advanced computing module 185 then uploads the polled sensor data to the VCS 40.
[0101] The VCS 40 includes a plurality of data processing modules, including a driver behavior module 320, a behavior characterization module 330, and a risk assessment module 340. The driver behavior module 320 of the VCS 40 receives the captured sensor data and can identify one or more driver behaviors 321-323. As an example, the driver behavior module 320 can analyze the sensor data to identify driver behavior 321, which includes, for example, sharp turns, sudden braking, and / or sudden acceleration. The driver behavior module 320 can also analyze the sensor data to identify driver behavior 322, which includes, for example, low-speed driving, high-speed driving, and speed curves. Finally, the driver behavior module 320 can analyze the sensor data to identify driver behavior 323, which includes, for example, tailgating, lane changes, drifting onto lane markings, drifting onto the shoulder of the road, etc.
[0102] The behavior characterization module 330 of VCS 40 can then analyze the identified driver behaviors 321-323 to characterize the identified driver behaviors 321-323 into categories associated with the driver, including micro-behavior categories 331, macro-behavior categories 332, and historical behavior record categories 333 associated with the driver. Micro-behavior categories 331 can include speeding, reckless driving, distracted driving, etc. Macro-behavior categories 332 can include time, space, and spatio-temporal hot zones. These can include time periods when the driver is engaged in more dangerous driving and / or roads where the driver is engaged in more dangerous driving. Historical behavior record categories 333 classify driver behaviors according to patterns, occurrences, frequencies, etc.
[0103] The driving behaviors listed above are merely exemplary and should not be construed as limiting the scope of the present disclosure or the appended claims. Driving behaviors may also include speed profiles, lane change profiles, lane following behaviors (maintaining a consistent distance relative to lane markings), unprompted lane changes, and lane changes on curves with respect to surrounding traffic. Other driving behaviors may include safety alert activations that are captured regardless of whether the system is enabled, such as forward collision alerts, front or rear cross traffic alerts, lane keeping alerts, side collision alerts, and parking assist alerts. Driving behaviors may also include miss detections, the number of anti-lock braking system events relative to other events in the same time and / or space region, and the number of traction and / or stability control system events relative to other events in the same time and / or space region. Driving behaviors may also include distractions caused by the use of an infotainment system, the number of red light violations, the number of traffic sign violations, the number of road rule violations (e.g., no red lights, no U-turns), the number of wrong lane driving events, unsafe driving in parking lots (e.g., crossing aisles), and failure to yield to pedestrians. In vehicle systems equipped with a monitoring system that captures driver gaze data, driving behavior can include extended off-road looks, detection of driver drowsiness, distraction, intoxication or strong emotions, failure to look at traffic signals, failure to look at oncoming traffic before turning, and failure to look both ways before crossing. Driver behavior can also include detection of smartphone use (including talking or texting), eating, smoking, fighting, singing, etc., as well as in-cabin distractions (e.g., children, pets) detected from in-cabin cameras and microphones.
[0104] The risk assessment module 340 of the VCS 40 may use the micro-behavior category 331, the macro-behavior category 332, and the historical behavior record category 333 to determine a driver profile that may include a risk assessment of the driver of the vehicle system 10. The risk assessment module 340 may use an open regression model to assess insurance risk. For example, the VC risk assessment module 340 may use the RFS principle to characterize each of the selected risk exposure behaviors, in which: i) the most recent value (V R ) indicates the most recent time when the driver exhibited a specific behavior; ii) frequency value (V F ) indicates how often the driver exhibits the behavioral characteristic; and iii) a severity value (V M ) indicates how serious the behavior is.
[0105] The risk assessment module 340 may calculate the implicit occurrence rate (f m ) is quantized as:
[0106] r(f m , driver) = w RV R + w F V F + w M V M ,
[0107] The weighting factor (w R ,w F ,w M ) is equal to 1.
[0108] The risk assessment module 340 may build a logistic regression model to relate insurance risk to these risk exposure characteristics:
[0109]
[0110] The VCS 40 may be configured to monitor sensor data to make insurance decisions. For example, the VCS 40 may identify that the driver has a low-risk driving style (e.g., large average following distance, infrequent lane changes). The VCS 40 may automatically generate an insurance quote and send it to the driver. The quote may include a favorable rate due to the low-risk driving style.
[0111] If the VCS 40 identifies the driving style as more risky, the VCS 40 may not generate a quote. In addition, if the driver is currently an insurance customer, the VCS 40 may warn the driver that insurance rates may be increased unless driving habits change. The VCS 40 may use sensor information to generate a driver rating and send the driver the driver rating to provide feedback to encourage careful driving. The VCS 40 may present the driver rating information in an application on a mobile device used by the driver.
[0112] Figure 4 4 is a flow chart illustrating sensor data processing operations in a vehicle system 10 according to the principles of the present disclosure. In the vehicle system 10, various sensors in the sensor module 188 continuously detect N events in real time. As an example, in 411, an accelerometer may detect a sudden deceleration or acceleration (Event 1 Detection). In 412, a radar or camera may detect an object near the front of the vehicle system 10 as it moves (Event 2 Detection). In 413, a camera may detect a lane marker closer to the vehicle system 10 (Event N Detection).
[0113] Next, the sensor or advanced computing module 185 may characterize the detected events. For example, in 421, the advanced computing module 185 may characterize detected event 1 as sudden braking. In 422, the advanced computing module 185 may characterize detected event 2 as tailgating. In 423, the advanced computing module 185 may characterize detected event N as crossing the center lane line (i.e., drifting into the oncoming traffic lane). In 430, the advanced computing module 185 collects all event data and, in 440, sends the event data to the VCS 40.
[0114] Figure 5 is a flow chart illustrating driver alert operation in the vehicle system 10 according to the principles of the present disclosure. Figure 5 The operation of the advanced computing module 185 when the incoming call mode is supported is shown. In the uninterrupted incoming call mode, the vehicle owner can contact the driver directly. In 510, the advanced computing module 185 determines whether the incoming call mode is enabled. If no in 510, in 520, the advanced computing module 185 receives a message from the VCS 40 via the telematics system (e.g., via the wireless transceiver module 195). In 530, the advanced computing module 185 displays the received message on the instrument panel screen.
[0115] If yes in 510, then in 540, the advanced computing module 185 selects a pre-synthesized announcement corresponding to the detected event. In 550, the advanced computing module 185 plays the pre-synthesized announcement through the vehicle speakers. The driver does not have the option to answer or disconnect. The owner's voice can be automatically played through the speakers. Therefore, if the vehicle owner is warned of dangerous driving behavior and the vehicle operator is contacted directly through the telematics system, the driver cannot ignore the owner.
[0116] Figure 6 is a flow chart illustrating evaluation of driver performance in a vehicle communication server (VCS) 40 according to the principles of the present disclosure. At 605, the VCS 40 receives sensor data from the vehicle system 10, and at 610, the VCS 40 evaluates the driver performance and generates a Figure 3 and Figure 4 . In 615, the VCS 40 determines whether the selected driver is a current customer of the insurance company that is evaluating the driver's performance. If no in 615, in 620, the VCS 40 determines whether the selected driver metric is less than a threshold. For example, the VCS 40 may determine whether the number of tailgating events in a specified period (e.g., day, week, month) is below a threshold. If no in 620, the process ends. If yes in 620, the VCS 40 may generate an insurance offer at a preferred rate and send the offer to the driver, and the process ends.
[0117] If yes in 615, then in 630, the VCS 40 determines whether the selected driver metric is less than a threshold. If yes in 630, then in 645, the VCS 40 may reward or incentivize the driver for "being a good driver." If no in 630, in 635, the VCS 40 may send a warning message to inform the driver that the driver has had too many events (e.g., too many tailgating events) within a defined period of time. In 640, the VCS 40 may also increase the driver's insurance premium.
[0118] Fig. 7A and 7B 1 is a flow chart showing the use of crowdsourced data from multiple vehicle systems 10 to evaluate driver performance in a vehicle communication server (VCS) 40 according to the principles of the present disclosure. Most of the above discussion focuses on monitoring the driver performance of a selected driver using sensor data from the same vehicle system operated by the selected driver. However, these principles are easily adapted to monitor the performance of a selected driver using crowdsourced data from nearby vehicles that are driving on the same road and at approximately the same time as the selected driver. In this way, the VCS 40 can compare the performance of the selected driver with the average performance of other drivers to detect specific driver behaviors. These driver behaviors can include driving much faster or slower than nearby vehicles, changing lanes (or drifting on lane markings) much more frequently than nearby vehicles, braking suddenly much more frequently than nearby vehicles, etc.
[0119] exist Fig. 7A and 7B In the flowchart, VCS 40 is described to monitor driver performance based on crowdsourced vehicle speed. However, those skilled in the art will appreciate that this is by way of example only and should not be construed as limiting the scope of the present disclosure. In alternative embodiments, VCS 40 can be easily adapted to monitor driver performance based on other crowdsourced data (e.g., lane changes, sudden braking).
[0120] In 705, the VCS 40 receives vehicle data from vehicle A (e.g., vehicle system 10A). In 710, the VCS 40 determines the speed and position of vehicle A based on the received vehicle data. The vehicle data also includes a timestamp that indicates when the sensors in vehicle A measured the speed and position data. In 715, the VSC 40 retrieves the applicable speed limit information from the vehicle DB 45 based on the vehicle A position.
[0121] At 720, the VCS 40 determines whether the speed of vehicle A exceeds the applicable speed limit. If no at 720, the VCS 40 returns to 705 and continues to monitor vehicle data from vehicle A. If yes at 720, the VCS 40 may identify selected crowdsourced data of other vehicle systems 10 corresponding to the same location and time window of vehicle A in the DB 45 at 725. At 730, the VCS 40 receives the vehicle data of the identified vehicle system. At 735, the VCS 40 uses the received crowdsourced data to determine a crowdsourced vehicle speed (e.g., an average speed) based on the crowdsourced vehicle data from the identified vehicle system.
[0122] In 740, the VCS 40 determines whether the speed of vehicle A is greater than the crowdsourced speed by more than a predetermined threshold. If yes in 740, then in 745, the VCS 40 may send a warning to the driver of vehicle A that the insurance rate may increase. In 750, the VCS 40 may determine whether the speed of vehicle A is within the acceptable driver behavior threshold, even if the speed of vehicle A is greater than the crowdsourced speed by more than the threshold. If yes in 750, the VCS 40 may return to 745 and simply issue a warning. If no in 750 or no in 740, the VCS 40 may initiate an increase or decrease in the insurance premium for the driver of vehicle A.
[0123] The foregoing description is essentially only illustrative, and is in no way intended to limit the present disclosure, its application or use. The broad teachings of the present disclosure can be implemented in various forms. Therefore, although the present disclosure includes specific examples, the true scope of the present disclosure should not be so limited, because after studying the drawings, the specification and the appended claims, other modifications will become apparent. It should be understood that, without changing the principles of the present disclosure, one or more steps in the method can be performed in different orders (or simultaneously). In addition, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the present disclosure can be implemented in the features of any one of the other embodiments and / or combined with the features of any one of the other embodiments, even if the combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and the replacement of one or more embodiments with each other remains within the scope of the present disclosure.
[0124] Various terms are used to describe the spatial and functional relationships between elements (e.g., between modules, circuit elements, semiconductor layers, etc.), including "connected", "engaged", "coupled", "adjacent", "next to", "on top", "above", "below", and "disposed". Unless explicitly described as "directly", when the relationship between a first and a second element is described in the above disclosure, the relationship can be a direct relationship without other intermediate elements between the first and second elements, but can also be an indirect relationship with one or more intermediate elements between the first and second elements (spatially or functionally). As used herein, the phrase at least one of A, B, and C should be interpreted as meaning a logical (A or B or C) using a non-exclusive logical "or", and should not be interpreted as meaning "at least one of A, at least one of B, and at least one of C".
[0125] In the drawings, the direction of the arrows, as indicated by the arrows, generally represents the flow of information (such as data or instructions) of interest to the illustration. For example, when element A and element B exchange various information, but the information sent from element A to element B is relevant to the illustration, the arrow may be directed from element A to element B. This unidirectional arrow does not imply that no other information is sent from element B to element A. In addition, for information sent from element A to element B, element B may send a request for the information or a confirmation of receipt of the information to element A.
[0126] In this application, including the definitions below, the term "module" or the term "controller" may be replaced with the term "circuit". The term "module" may refer to, be part of, or include: an application specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or group) that executes code; a memory circuit (shared, dedicated, or group) that stores code executed by the processor circuit; other suitable hardware components that provide the functionality; or a combination of some or all of the above, such as in a system on a chip.
[0127] The module may include one or more interface circuits. In some examples, the interface circuit may include a wired or wireless interface connected to a local area network (LAN), the Internet, a wide area network (WAN), or a combination thereof. The functions of any given module of the present disclosure may be distributed in multiple modules connected via interface circuits. For example, multiple modules may allow load balancing. In a further example, a server (also referred to as a remote or cloud) module may perform some functions on behalf of a client module.
[0128] The term "code" as used above may include software, firmware and / or microcode, and may refer to a program, a routine, a function, a class, a data structure and / or an object. The term "shared processor circuit" includes a single processor circuit that executes some or all code from multiple modules. The term "group processor circuit" includes a processor circuit that executes some or all code from one or more modules in combination with an additional processor circuit. References to multi-processor circuits include multi-processor circuits on discrete dies, multi-processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term "shared memory circuit" includes a single memory circuit that stores some or all code from multiple modules. The term "group memory circuit" includes a memory circuit that stores some or all code from one or more modules in combination with additional memory.
[0129] The term "memory circuit" is a subset of the term "computer-readable medium". The term "computer-readable medium" as used herein does not include transient electrical or electromagnetic signals propagated through a medium (such as on a carrier wave); therefore, the term "computer-readable medium" may be considered to be both tangible and non-transitory. Non-limiting examples of non-transitory tangible computer-readable media are non-volatile memory circuits (such as flash memory circuits, erasable programmable read-only memory circuits, or mask read-only memory circuits), volatile memory circuits (such as static random access memory circuits or dynamic random access memory circuits), magnetic storage media (such as analog or digital magnetic tape or hard drives), and optical storage media (such as CDs, DVDs, or Blu-ray discs).
[0130] The apparatus and methods described in this application may be implemented in part or in whole by a special purpose computer created by configuring a general purpose computer to perform one or more specific functions implemented in a computer program. The above-mentioned function blocks, flow chart components and other elements are used as software specifications, which can be converted into a computer program by routine work of a skilled technician or programmer.
[0131] The computer program includes processor executable instructions stored on at least one non-transitory tangible computer readable medium. The computer program may also include or rely on stored data. The computer program may include a basic input / output system (BIOS) that interacts with the hardware of the special-purpose computer, device drivers that interact with specific devices of the special-purpose computer, one or more operating systems, user applications, background services, background applications, etc.
[0132] A computer program may include: (i) descriptive text to be parsed, such as HTML (Hypertext Markup Language), XML (Extensible Markup Language), or JSON (JavaScript Object Notation); (ii) assembly code; (iii) object code generated by a compiler from source code; (iv) source code executed by an interpreter; (v) source code compiled and executed by a just-in-time compiler, etc. By way of example only, source code may be written using syntax from languages including C, C++, C#, Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5 (Hypertext Markup Language 5th Revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, and Python®.
Claims
1. A driver monitoring system configured to monitor the performance of a driver of a first vehicle system in wireless communication with the driver monitoring system, the driver monitoring system comprising: a vehicle database including a plurality of vehicle records associated with a plurality of vehicle systems; as well as Vehicle server, including: a driver behavior module configured to receive, from the first vehicle system, first event data captured by a plurality of sensors in the first vehicle system, the first event data comprising a first event time and a first event location, and the driver behavior module configured to identify a first driver behavior associated with the first event data; a behavior characterization module configured to receive the first driver behavior from the driver behavior module and characterize the first driver behavior as at least one of a plurality of behavior categories; and a risk assessment module configured to analyze driver behavior characterized by at least one of the plurality of behavior categories and determine a driver profile from the at least one characterized driver behavior, the driver profile being able to include a risk assessment of the driver to the vehicle system; wherein the vehicle server is further configured to use the first event time and the first event location to identify a plurality of neighboring vehicles in the vicinity of the first vehicle system in the vehicle database, and to determine an average value associated with the first driver behavior from vehicle records associated with the plurality of neighboring vehicles, wherein the driver monitoring system is configured to determine whether the first driver behavior exceeds the average by a threshold value; wherein in response to determining that the first driver behavior exceeds the average by more than the threshold, the driver monitoring system sends a warning message to the driver, and Wherein the driver monitoring system is configured to compare the first driver behavior to a second threshold and, in response to the comparison, send a warning message to the driver. 2 . The driver monitoring system of claim 1 , wherein the driver monitoring system sends the warning message if the driver is a customer of an insurance provider. 3 . The driver monitoring system of claim 1 , wherein the second threshold is a speed limit associated with a road determined by the first event location. 4 . The driver monitoring system of claim 1 , wherein the driver monitoring system sends the warning message if the driver is a customer of an insurance provider.
5. The driver monitoring system according to claim 1, wherein: In response to determining that the first driver behavior exceeds the average by more than the threshold, the driver monitoring system increases an insurance premium associated with the driver.
6. The driver monitoring system according to claim 1, wherein: In response to determining that a first driver behavior exceeds the average by more than the threshold, the driver monitoring system sends a message to an owner of the vehicle system, the message notifying the owner that the driver has exceeded the threshold.
7. A method of monitoring performance of a driver of a first vehicle system in wireless communication with a driver monitoring system, the method comprising: storing a plurality of vehicle records associated with a plurality of vehicle systems in a vehicle database; In a vehicle server of the driver monitoring system, receiving, from the first vehicle system, first event data captured by a plurality of sensors in the first vehicle system, the first event data including a first event time and a first event location; identifying a first driver behavior associated with the first event data, characterizing the first driver behavior as at least one of a plurality of behavior categories, and analyzing driver behavior characterized by at least one of the plurality of behavior categories and determining a driver profile from the at least one characterized driver behavior, the driver profile being able to include a risk assessment for the driver of the vehicle system; identifying in the vehicle database a plurality of neighboring vehicles proximate to the first vehicle system using the first event time and the first event location; as well as determining an average value associated with the first driver behavior from the vehicle records associated with the plurality of neighboring vehicles, wherein the method further comprises determining whether the first driver behavior exceeds the average value by an excess threshold; The method further includes, in response to determining that the first driver behavior exceeds the average value by more than the threshold value, sending a warning message to the driver, and The method further comprises comparing the first driver behavior with a second threshold and, in response to the comparison, sending a warning message to the driver.
8. The method of claim 7, wherein the warning message is sent if the driver is a customer of an insurance provider.
9. The method according to claim 7, wherein: The second threshold is a speed limit associated with a road determined by the first event location.
10. The method of claim 7, wherein the warning message is sent if the driver is a customer of an insurance provider.
11. The method of claim 7, further comprising increasing an insurance premium associated with the driver in response to determining that the first driver behavior exceeds the average by more than the threshold.
12. The method of claim 7 further comprising, in response to determining that the first driver behavior exceeds the average by more than the threshold, sending a message to an owner of the vehicle system, the message notifying the owner that the driver has exceeded the threshold.
