US20200088529A1 - Route safety score - Google Patents
Route safety score Download PDFInfo
- Publication number
- US20200088529A1 US20200088529A1 US16/693,102 US201916693102A US2020088529A1 US 20200088529 A1 US20200088529 A1 US 20200088529A1 US 201916693102 A US201916693102 A US 201916693102A US 2020088529 A1 US2020088529 A1 US 2020088529A1
- Authority
- US
- United States
- Prior art keywords
- route
- data
- vehicles
- vehicle
- determining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 16
- 238000013500 data storage Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 7
- 230000001413 cellular effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000004884 risky behavior Effects 0.000 description 2
- 238000012512 characterization method Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004557 technical material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3453—Special cost functions, i.e. other than distance or default speed limit of road segments
- G01C21/3492—Special cost functions, i.e. other than distance or default speed limit of road segments employing speed data or traffic data, e.g. real-time or historical
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
- G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
- G08G1/0112—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from the vehicle, e.g. floating car data [FCD]
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
- G08G1/0125—Traffic data processing
- G08G1/0133—Traffic data processing for classifying traffic situation
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
- G08G1/096805—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route
- G08G1/096827—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route where the route is computed onboard
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
- G08G1/096833—Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route
- G08G1/096838—Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route where the user preferences are taken into account or the user selects one route out of a plurality
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/123—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams
Definitions
- FIG. 1 is a block diagram illustrating an embodiment of a system including a vehicle event recorder.
- FIG. 2 is a block diagram illustrating an embodiment of a vehicle event recorder.
- FIG. 3 is a block diagram illustrating an embodiment of a vehicle data server.
- FIG. 4 is a diagram illustrating an embodiment of vehicles on a road segment.
- FIG. 5 is a flow diagram illustrating an embodiment of a process for determining a route based at least in part on a safety score.
- FIG. 6 is a flow diagram illustrating an embodiment of a process for determining a route safety score for a route.
- FIG. 7 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using speed data.
- FIG. 8 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using a speed distribution.
- the invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor.
- these implementations, or any other form that the invention may take, may be referred to as techniques.
- the order of the steps of disclosed processes may be altered within the scope of the invention.
- a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task.
- the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
- a system for scoring route safety comprises an input interface to receive data associated with a route segment, wherein the data comprises a speed data, and a processor to determine a segment safety score using a speed distribution, wherein the speed distribution is based at least in part on the speed data.
- the system for scoring route safety additionally comprises a memory coupled to the processor and configured to provide the processor with instructions.
- a system for scoring route safety receives a set of speed data.
- the set of speed data comprises data describing vehicle speeds at road locations.
- the speed data comprises data measured by one or more vehicle event recorders measuring vehicle speed.
- the system for scoring route safety receives map data including a set of route segments.
- route segments comprise short road segments (e.g., one quarter mile, one kilometer, one mile, one block, one freeway exit, etc.).
- the system for scoring route safety determines a safety score associated with each route segment.
- the safety score is based at least in part on a speed distribution of speed data within the route segment.
- a speed distribution comprises a standard deviation of measured speeds within the route segment.
- the safety score is based on event data, maneuver data, video data, lane change frequency data, climate data, topology data, road data, lane configuration data, speed data, or any other appropriate data.
- the system for scoring route safety receives a starting point and a destination point for a route and determines one or more possible routes to travel from the starting point to the destination point.
- the system determines the set of route segments comprised by each possible route and determines the route segment safety score associated with each route segment.
- a route safety score for each route can then be determined by combining the route segment safety scores associated with the route.
- the system for scoring route safety can then determine a preferred route of the one or more possible routes based at least in part on the route safety scores.
- a route is determined based on route safety scores, route driving times, traffic, driver preferences, or any other appropriate criteria.
- FIG. 1 is a block diagram illustrating an embodiment of a system including a vehicle event recorder.
- vehicle event recorder 102 comprises a vehicle event recorder mounted in a vehicle (e.g., a car or truck).
- vehicle event recorder 102 includes or is in communication with a set of sensors—for example, video recorders, audio recorders, accelerometers, gyroscopes, vehicle state sensors, proximity sensors, a global positioning system (e.g., GPS), outdoor temperature sensors, moisture sensors, laser line tracker sensors, or any other appropriate sensors.
- sensors for example, video recorders, audio recorders, accelerometers, gyroscopes, vehicle state sensors, proximity sensors, a global positioning system (e.g., GPS), outdoor temperature sensors, moisture sensors, laser line tracker sensors, or any other appropriate sensors.
- GPS global positioning system
- vehicle state sensors comprise a speedometer, an accelerator pedal sensor, a brake pedal sensor, an engine revolutions per minute (e.g., RPM) sensor, an engine temperature sensor, a headlight sensor, an airbag deployment sensor, driver and passenger seat weight sensors, an anti-locking brake sensor, an engine exhaust sensor, a gear position sensor, a cabin equipment operation sensor, or any other appropriate vehicle state sensors.
- vehicle event recorder 102 comprises a system for processing sensor data and detecting events.
- vehicle event recorder 102 comprises map data.
- vehicle event recorder 102 comprises a system for detecting risky behavior.
- vehicle event recorder 102 is mounted on vehicle 106 in one of the following locations: the chassis, the front grill, the dashboard, the rear-view mirror, or any other appropriate location. In some embodiments, vehicle event recorder 102 comprises multiple units mounted in different locations in vehicle 106 . In some embodiments, vehicle event recorder 102 comprises a communications system for communicating with network 100 .
- network 100 comprises a wireless network, a wired network, a cellular network, a Code Division Multiple Access (CDMA) network, a Global System for Mobile Communication (GSM) network, a Long-Term Evolution (LTE) network, a Universal Mobile Telecommunications System (UMTS) network, a Worldwide Interoperability for Microwave Access (WiMAX) network, a Dedicated Short-Range Communications (DSRC) network, a local area network, a wide area network, the Internet, or any other appropriate network.
- CDMA Code Division Multiple Access
- GSM Global System for Mobile Communication
- LTE Long-Term Evolution
- UMTS Universal Mobile Telecommunications System
- WiMAX Worldwide Interoperability for Microwave Access
- DSRC Dedicated Short-Range Communications
- network 100 comprises multiple networks, changing over time and location.
- different networks comprising network 100 comprise different bandwidth cost (e.g., a wired network has a very low cost, a wireless Ethernet connection has a moderate cost, a cellular data network has a high cost). In some embodiments, network 100 has a different cost at different times (e.g., a higher cost during the day and a lower cost at night).
- Vehicle event recorder 102 communicates with vehicle data server 104 via network 100 .
- Vehicle event recorder 102 is mounted to vehicle 106 .
- vehicle 106 comprises a car, a truck, a commercial vehicle, or any other appropriate vehicle.
- Vehicle data server 104 comprises a vehicle data server for collecting events and risky behavior detected by vehicle event recorder 102 .
- vehicle data server 104 comprises a system for collecting data from multiple vehicle event recorders. In some embodiments, vehicle data server 104 comprises a system for analyzing vehicle event recorder data. In some embodiments, vehicle data server 104 comprises a system for displaying vehicle event recorder data. In some embodiments, vehicle data server 104 is located at a home station (e.g., a shipping company office, a taxi dispatcher, a truck depot, etc.). In various embodiments, vehicle data server 104 is located at a colocation center (e.g., a center where equipment, space, and bandwidth are available for rental), at a cloud service provider, or any at other appropriate location.
- a home station e.g., a shipping company office, a taxi dispatcher, a truck depot, etc.
- vehicle data server 104 is located at a colocation center (e.g., a center where equipment, space, and bandwidth are available for rental), at a cloud service provider, or any at other appropriate location.
- events recorded by vehicle event recorder 102 are downloaded to vehicle data server 104 when vehicle 106 arrives at the home station.
- vehicle data server 104 is located at a remote location.
- events recorded by vehicle event recorder 102 are downloaded to vehicle data server 104 wirelessly.
- a subset of events recorded by vehicle event recorder 102 is downloaded to vehicle data server 104 wirelessly.
- vehicle event recorder 102 comprises a system for determining risky events.
- FIG. 2 is a block diagram illustrating an embodiment of a vehicle event recorder.
- vehicle event recorder 200 of FIG. 2 comprises vehicle event recorder 102 of FIG. 1 .
- vehicle event recorder 200 comprises processor 202 .
- Processor 202 comprises a processor for controlling the operations of vehicle event recorder 200 , for reading and writing information on data storage 204 , for communicating via wireless communications interface 206 , and for reading data via sensor interface 208 .
- processor 202 comprises a processor for determining a vehicle characterization, determining a vehicle identifier, determining a maintenance item, or for any other appropriate purpose.
- Data storage 204 comprises a data storage (e.g., a random access memory (RAM), a read only memory (ROM), a nonvolatile memory, a flash memory, a hard disk, or any other appropriate data storage).
- data storage 204 comprises a data storage for storing instructions for processor 202 , vehicle event recorder data, vehicle event data, sensor data, video data, driver scores, or any other appropriate data.
- communications interfaces 206 comprises one or more of a GSM interface, a CDMA interface, a LTE interface, a WiFiTM interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a BluetoothTM interface, an Internet interface, or any other appropriate interface.
- Sensor interface 208 comprises an interface to one or more vehicle event recorder sensors.
- vehicle event recorder sensors comprise an exterior video camera, an exterior still camera, an interior video camera, an interior still camera, a microphone, an accelerometer, a gyroscope, an outdoor temperature sensor, a moisture sensor, a laser line tracker sensor, vehicle state sensors, or any other appropriate sensors.
- vehicle state sensors comprise a speedometer, an accelerator pedal sensor, a brake pedal sensor, an engine revolutions per minute (RPM) sensor, an engine temperature sensor, a headlight sensor, an airbag deployment sensor, driver and passenger seat weight sensors, an anti-locking brake sensor, an engine exhaust sensor, a gear position sensor, a turn signal sensor, a cabin equipment operation sensor, or any other appropriate vehicle state sensors.
- RPM revolutions per minute
- sensor interface 208 comprises an on-board diagnostics (OBD) bus (e.g., society of automotive engineers (SAE) J1939, J1708/J1587, OBD-II, CAN BUS, etc.).
- OBD on-board diagnostics
- vehicle event recorder 200 communicates with vehicle state sensors via the OBD bus.
- vehicle event recorder 200 communicates with a vehicle data server via communications interfaces 206 .
- vehicle event recorder 200 transmits vehicle state sensor data, accelerometer data, speed data, maneuver data, audio data, video data, event data, or any other appropriate data to the vehicle data server.
- vehicle event recorder 200 receives an indication of a route from the vehicle data server.
- vehicle event recorder 200 receives a set of route segment safety scores from the vehicle data server and determines a route based at least in part on the set of route segment safety scores.
- FIG. 3 is a block diagram illustrating an embodiment of a vehicle data server.
- vehicle data server 300 comprises vehicle data server 104 of FIG. 1 .
- vehicle data server 300 comprises processor 302 .
- processor 302 comprises a processor for determining a route, determining a set of route segments, determining a route segment safety score, collecting speed data, determining a speed distribution, or for any other appropriate purpose.
- Data storage 304 comprises a data storage (e.g., a random access memory (RAM), a read only memory (ROM), a nonvolatile memory, a flash memory, a hard disk, or any other appropriate data storage).
- RAM random access memory
- ROM read only memory
- nonvolatile memory e.g., a flash memory, a hard disk, or any other appropriate data storage.
- data storage 304 comprises a data storage for storing instructions for processor 302 , vehicle event recorder data, vehicle event data, sensor data, video data, map data, machine learning algorithm data, or any other appropriate data.
- communications interfaces 306 comprises one or more of a GSM interface, a CDMA interface, a WiFi interface, an Ethernet interface, a USB interface, a Bluetooth interface, an Internet interface, a fiber optic interface, or any other appropriate interface.
- vehicle data server 300 receives events, maneuvers, data, or any other appropriate information from one or more vehicle event recorders.
- vehicle data server 300 determines a route based at least in part on a route safety score and communicates the route to one or more vehicle event recorders.
- vehicle data server 300 determines a set of route segment safety scores and communicates the set of route segment safety scores to one or more vehicle event recorders.
- FIG. 4 is a diagram illustrating an embodiment of vehicles on a road segment.
- four vehicles are traveling on a freeway.
- vehicles typically move at approximately the same speed.
- vehicles typically move at different speeds.
- vehicle 400 moves at 65 MPH on the freeway
- vehicle 402 moves at 60 MPH
- vehicle 404 moves at 55 MPH
- vehicle 406 moves at 40 MPH.
- each vehicle comprises a vehicle event recorder that reports its speed to a vehicle data server.
- a vehicle data server collects speed data from vehicles traveling on the road segment to determine a speed distribution.
- a speed distribution comprises a standard deviation of speed data.
- a speed distribution comprises a speed distribution of all vehicles on the road segment at a given time, a speed distribution of typical vehicle speed across time, a speed distribution of typical vehicle speed across the road segment, a speed distribution of all speed data recorded for the road segment, or any other appropriate speed distribution.
- FIG. 5 is a flow diagram illustrating an embodiment of a process for determining a route based at least in part on a safety score.
- the process of FIG. 5 is executed by a vehicle data server (e.g., vehicle data server 104 of FIG. 1 ).
- the process of FIG. 5 is executed by a vehicle event recorder (e.g., vehicle event recorder 102 of FIG. 1 ).
- a starting point and a destination point are received.
- a starting point and a destination point are received from a driver, from a system administrator, from a route plan, or from any other appropriate source.
- a set of possible routes is determined.
- the set of possible routes comprises all possible routes, all possible routes under a timing threshold, all possible routes within a desired region, or any other appropriate set of possible routes.
- a next route of the set of possible routes is selected.
- the next route comprises the first route.
- a route safety score for the route is determined.
- a route of the set of possible routes is selected.
- the route with the route safety score indicating the route is safest is selected.
- a lower route safety score indicates a safer route, and the route with the lowest route safety score is selected.
- the route is selected based on route safety scores, route driving times, traffic, driver preferences, or any other appropriate criteria.
- FIG. 6 is a flow diagram illustrating an embodiment of a process for determining a route safety score for a route.
- the process of FIG. 6 implements 506 of FIG. 5 .
- a route is received.
- a route comprises a start point, an end point, and a path from the start point to the end point.
- a set of route segments associated with the route is determined.
- the set of route segments comprises the set of route segments along the path from the start point to the end point.
- a next route segment of the set of route segments is selected.
- the first route segment of the set of route segments is selected.
- a route segment safety score for the route segment is determined. In some embodiments, determining a route segment safety score for the route segment comprises determining a route segment safety score using speed data. In some embodiments, determining a route segment safety score using speed data is performed by a vehicle data server. The vehicle data server stores determined route segment safety scores in a route segment safety score database. In some embodiments, the route segment safety score database is transmitted to a vehicle event recorder and the process of FIG. 6 is performed by a vehicle event recorder. In some embodiments, determining a route segment safety score comprises looking up a route segment safety score for the route segment in a safety score database. In 608 , it is determined whether there are more route segments (e.g., of the set of route segments).
- the route segment safety scores are combined to determine a route safety score. In some embodiments, combining the route segment safety scores comprises adding the route segment safety scores.
- FIG. 7 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using speed data.
- the process of FIG. 7 implements 606 of FIG. 6 .
- the process of FIG. 7 is executed by a vehicle data server.
- a route segment is received.
- a route segment comprises an indication of a route segment (e.g., a route segment indicator).
- data associated with the route segment is received, wherein the data comprises a speed data.
- receiving data associated with the route segment comprises retrieving vehicle data from a vehicle database.
- data is associated with a plurality of vehicles.
- data comprises data received at a plurality of locations within the segment. In some embodiments, data comprises data received at a plurality of times of day. In various embodiments, data comprises one or more of the following (e.g., in addition to a speed data): events, maneuvers, video data, lane change frequency, climate data, topology data, road data, number of lanes, or any other appropriate data.
- a route segment safety score is determined using a speed distribution, wherein the speed distribution is based at least in part on the speed data.
- the speed data comprises a set of vehicle speeds (e.g., vehicle speeds received from vehicle event recorders), and the speed distribution is determined from the speed data (e.g., by determining the standard deviation of the speed data). In some embodiments, the speed data comprises the speed distribution.
- FIG. 8 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using a speed distribution.
- the process of FIG. 8 implements 704 of FIG. 7 .
- a speed distribution standard deviation is determined.
- a speed distribution standard deviation is determined from speed data using the well-known formula (e.g., range or standard deviation or function of maximum speed and minimum speed, etc.).
- a speed distribution standard deviation is received.
- a segment safety score is determined based at least in part on the speed distribution standard deviation.
- determining a segment safety score comprises scaling the speed distribution standard deviation by a constant (e.g., multiplying by 100).
- the segment safety score is based at least in part on other data (e.g., events, maneuvers, video data, lane change frequency, climate data, topology data, road data, number of lanes, etc.). In some embodiments, the segment safety score comprises a linear combination of the speed distribution standard deviation and other data. In some embodiments, a higher safety score indicates that the route segment is less safe.
Landscapes
- Engineering & Computer Science (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Chemical & Material Sciences (AREA)
- Analytical Chemistry (AREA)
- Mathematical Physics (AREA)
- Traffic Control Systems (AREA)
Abstract
Description
- This application is a continuation of co-pending U.S. patent application Ser. No. 14/965,018 entitled ROUTE SAFETY SCORE filed Dec. 10, 2015 which is incorporated herein by reference for all purposes.
- Typically, it is difficult to determine how safe a route is that is taken while driving from point A to point B. Even more so in the event that a driver has no experience traveling the route.
- Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
-
FIG. 1 is a block diagram illustrating an embodiment of a system including a vehicle event recorder. -
FIG. 2 is a block diagram illustrating an embodiment of a vehicle event recorder. -
FIG. 3 is a block diagram illustrating an embodiment of a vehicle data server. -
FIG. 4 is a diagram illustrating an embodiment of vehicles on a road segment. -
FIG. 5 is a flow diagram illustrating an embodiment of a process for determining a route based at least in part on a safety score. -
FIG. 6 is a flow diagram illustrating an embodiment of a process for determining a route safety score for a route. -
FIG. 7 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using speed data. -
FIG. 8 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using a speed distribution. - The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
- A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
- A system for scoring route safety comprises an input interface to receive data associated with a route segment, wherein the data comprises a speed data, and a processor to determine a segment safety score using a speed distribution, wherein the speed distribution is based at least in part on the speed data. In some embodiments, the system for scoring route safety additionally comprises a memory coupled to the processor and configured to provide the processor with instructions.
- In some embodiments, a system for scoring route safety receives a set of speed data. The set of speed data comprises data describing vehicle speeds at road locations. In some embodiments, the speed data comprises data measured by one or more vehicle event recorders measuring vehicle speed. The system for scoring route safety receives map data including a set of route segments. In some embodiments, route segments comprise short road segments (e.g., one quarter mile, one kilometer, one mile, one block, one freeway exit, etc.). The system for scoring route safety determines a safety score associated with each route segment. In some embodiments, the safety score is based at least in part on a speed distribution of speed data within the route segment. In some embodiments, a speed distribution comprises a standard deviation of measured speeds within the route segment. In various embodiments, the safety score is based on event data, maneuver data, video data, lane change frequency data, climate data, topology data, road data, lane configuration data, speed data, or any other appropriate data.
- In some embodiments, the system for scoring route safety receives a starting point and a destination point for a route and determines one or more possible routes to travel from the starting point to the destination point. The system determines the set of route segments comprised by each possible route and determines the route segment safety score associated with each route segment. A route safety score for each route can then be determined by combining the route segment safety scores associated with the route. The system for scoring route safety can then determine a preferred route of the one or more possible routes based at least in part on the route safety scores. In various embodiments, a route is determined based on route safety scores, route driving times, traffic, driver preferences, or any other appropriate criteria.
-
FIG. 1 is a block diagram illustrating an embodiment of a system including a vehicle event recorder. In the example shown,vehicle event recorder 102 comprises a vehicle event recorder mounted in a vehicle (e.g., a car or truck). In some embodiments,vehicle event recorder 102 includes or is in communication with a set of sensors—for example, video recorders, audio recorders, accelerometers, gyroscopes, vehicle state sensors, proximity sensors, a global positioning system (e.g., GPS), outdoor temperature sensors, moisture sensors, laser line tracker sensors, or any other appropriate sensors. In various embodiments, vehicle state sensors comprise a speedometer, an accelerator pedal sensor, a brake pedal sensor, an engine revolutions per minute (e.g., RPM) sensor, an engine temperature sensor, a headlight sensor, an airbag deployment sensor, driver and passenger seat weight sensors, an anti-locking brake sensor, an engine exhaust sensor, a gear position sensor, a cabin equipment operation sensor, or any other appropriate vehicle state sensors. In some embodiments,vehicle event recorder 102 comprises a system for processing sensor data and detecting events. In some embodiments,vehicle event recorder 102 comprises map data. In some embodiments,vehicle event recorder 102 comprises a system for detecting risky behavior. In various embodiments,vehicle event recorder 102 is mounted onvehicle 106 in one of the following locations: the chassis, the front grill, the dashboard, the rear-view mirror, or any other appropriate location. In some embodiments,vehicle event recorder 102 comprises multiple units mounted in different locations invehicle 106. In some embodiments,vehicle event recorder 102 comprises a communications system for communicating withnetwork 100. In various embodiments,network 100 comprises a wireless network, a wired network, a cellular network, a Code Division Multiple Access (CDMA) network, a Global System for Mobile Communication (GSM) network, a Long-Term Evolution (LTE) network, a Universal Mobile Telecommunications System (UMTS) network, a Worldwide Interoperability for Microwave Access (WiMAX) network, a Dedicated Short-Range Communications (DSRC) network, a local area network, a wide area network, the Internet, or any other appropriate network. In some embodiments,network 100 comprises multiple networks, changing over time and location. In some embodiments, differentnetworks comprising network 100 comprise different bandwidth cost (e.g., a wired network has a very low cost, a wireless Ethernet connection has a moderate cost, a cellular data network has a high cost). In some embodiments,network 100 has a different cost at different times (e.g., a higher cost during the day and a lower cost at night).Vehicle event recorder 102 communicates withvehicle data server 104 vianetwork 100.Vehicle event recorder 102 is mounted tovehicle 106. In various embodiments,vehicle 106 comprises a car, a truck, a commercial vehicle, or any other appropriate vehicle.Vehicle data server 104 comprises a vehicle data server for collecting events and risky behavior detected byvehicle event recorder 102. In some embodiments,vehicle data server 104 comprises a system for collecting data from multiple vehicle event recorders. In some embodiments,vehicle data server 104 comprises a system for analyzing vehicle event recorder data. In some embodiments,vehicle data server 104 comprises a system for displaying vehicle event recorder data. In some embodiments,vehicle data server 104 is located at a home station (e.g., a shipping company office, a taxi dispatcher, a truck depot, etc.). In various embodiments,vehicle data server 104 is located at a colocation center (e.g., a center where equipment, space, and bandwidth are available for rental), at a cloud service provider, or any at other appropriate location. In some embodiments, events recorded byvehicle event recorder 102 are downloaded tovehicle data server 104 whenvehicle 106 arrives at the home station. In some embodiments,vehicle data server 104 is located at a remote location. In some embodiments, events recorded byvehicle event recorder 102 are downloaded tovehicle data server 104 wirelessly. In some embodiments, a subset of events recorded byvehicle event recorder 102 is downloaded tovehicle data server 104 wirelessly. In some embodiments,vehicle event recorder 102 comprises a system for determining risky events. -
FIG. 2 is a block diagram illustrating an embodiment of a vehicle event recorder. In some embodiments,vehicle event recorder 200 ofFIG. 2 comprisesvehicle event recorder 102 ofFIG. 1 . In the example shown,vehicle event recorder 200 comprisesprocessor 202.Processor 202 comprises a processor for controlling the operations ofvehicle event recorder 200, for reading and writing information ondata storage 204, for communicating viawireless communications interface 206, and for reading data viasensor interface 208. In various embodiments,processor 202 comprises a processor for determining a vehicle characterization, determining a vehicle identifier, determining a maintenance item, or for any other appropriate purpose.Data storage 204 comprises a data storage (e.g., a random access memory (RAM), a read only memory (ROM), a nonvolatile memory, a flash memory, a hard disk, or any other appropriate data storage). In various embodiments,data storage 204 comprises a data storage for storing instructions forprocessor 202, vehicle event recorder data, vehicle event data, sensor data, video data, driver scores, or any other appropriate data. In various embodiments, communications interfaces 206 comprises one or more of a GSM interface, a CDMA interface, a LTE interface, a WiFi™ interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a Bluetooth™ interface, an Internet interface, or any other appropriate interface.Sensor interface 208 comprises an interface to one or more vehicle event recorder sensors. In various embodiments, vehicle event recorder sensors comprise an exterior video camera, an exterior still camera, an interior video camera, an interior still camera, a microphone, an accelerometer, a gyroscope, an outdoor temperature sensor, a moisture sensor, a laser line tracker sensor, vehicle state sensors, or any other appropriate sensors. In various embodiments, vehicle state sensors comprise a speedometer, an accelerator pedal sensor, a brake pedal sensor, an engine revolutions per minute (RPM) sensor, an engine temperature sensor, a headlight sensor, an airbag deployment sensor, driver and passenger seat weight sensors, an anti-locking brake sensor, an engine exhaust sensor, a gear position sensor, a turn signal sensor, a cabin equipment operation sensor, or any other appropriate vehicle state sensors. In some embodiments,sensor interface 208 comprises an on-board diagnostics (OBD) bus (e.g., society of automotive engineers (SAE) J1939, J1708/J1587, OBD-II, CAN BUS, etc.). In some embodiments,vehicle event recorder 200 communicates with vehicle state sensors via the OBD bus. In some embodiments,vehicle event recorder 200 communicates with a vehicle data server via communications interfaces 206. In various embodiments,vehicle event recorder 200 transmits vehicle state sensor data, accelerometer data, speed data, maneuver data, audio data, video data, event data, or any other appropriate data to the vehicle data server. In some embodiments,vehicle event recorder 200 receives an indication of a route from the vehicle data server. In some embodiments,vehicle event recorder 200 receives a set of route segment safety scores from the vehicle data server and determines a route based at least in part on the set of route segment safety scores. -
FIG. 3 is a block diagram illustrating an embodiment of a vehicle data server. In some embodiments,vehicle data server 300 comprisesvehicle data server 104 ofFIG. 1 . In the example shown,vehicle data server 300 comprisesprocessor 302. In various embodiments,processor 302 comprises a processor for determining a route, determining a set of route segments, determining a route segment safety score, collecting speed data, determining a speed distribution, or for any other appropriate purpose.Data storage 304 comprises a data storage (e.g., a random access memory (RAM), a read only memory (ROM), a nonvolatile memory, a flash memory, a hard disk, or any other appropriate data storage). In various embodiments,data storage 304 comprises a data storage for storing instructions forprocessor 302, vehicle event recorder data, vehicle event data, sensor data, video data, map data, machine learning algorithm data, or any other appropriate data. In various embodiments, communications interfaces 306 comprises one or more of a GSM interface, a CDMA interface, a WiFi interface, an Ethernet interface, a USB interface, a Bluetooth interface, an Internet interface, a fiber optic interface, or any other appropriate interface. In various embodiments,vehicle data server 300 receives events, maneuvers, data, or any other appropriate information from one or more vehicle event recorders. In some embodiments,vehicle data server 300 determines a route based at least in part on a route safety score and communicates the route to one or more vehicle event recorders. In some embodiments,vehicle data server 300 determines a set of route segment safety scores and communicates the set of route segment safety scores to one or more vehicle event recorders. -
FIG. 4 is a diagram illustrating an embodiment of vehicles on a road segment. In the example shown, four vehicles are traveling on a freeway. In some embodiments, vehicles typically move at approximately the same speed. In some embodiments, vehicles typically move at different speeds. In the example shown,vehicle 400 moves at 65 MPH on the freeway,vehicle 402 moves at 60 MPH,vehicle 404 moves at 55 MPH, andvehicle 406 moves at 40 MPH. In some embodiments, each vehicle comprises a vehicle event recorder that reports its speed to a vehicle data server. In some embodiments, a vehicle data server collects speed data from vehicles traveling on the road segment to determine a speed distribution. In some embodiments, a speed distribution comprises a standard deviation of speed data. In various embodiments, a speed distribution comprises a speed distribution of all vehicles on the road segment at a given time, a speed distribution of typical vehicle speed across time, a speed distribution of typical vehicle speed across the road segment, a speed distribution of all speed data recorded for the road segment, or any other appropriate speed distribution. -
FIG. 5 is a flow diagram illustrating an embodiment of a process for determining a route based at least in part on a safety score. In some embodiments, the process ofFIG. 5 is executed by a vehicle data server (e.g.,vehicle data server 104 ofFIG. 1 ). In some embodiments, the process ofFIG. 5 is executed by a vehicle event recorder (e.g.,vehicle event recorder 102 ofFIG. 1 ). In the example shown, in 500, a starting point and a destination point are received. In various embodiments, a starting point and a destination point are received from a driver, from a system administrator, from a route plan, or from any other appropriate source. In 502, a set of possible routes is determined. In various embodiments, the set of possible routes comprises all possible routes, all possible routes under a timing threshold, all possible routes within a desired region, or any other appropriate set of possible routes. In 504, a next route of the set of possible routes is selected. In some embodiments, the next route comprises the first route. In 506, a route safety score for the route is determined. In 508, it is determined whether there are more routes (e.g., of the set of possible routes). In the event there are more routes, control passes to 504. In the event there are not more routes, control passes to 510. In 510, a route of the set of possible routes is selected. In some embodiments, the route with the route safety score indicating the route is safest is selected. In some embodiments, a lower route safety score indicates a safer route, and the route with the lowest route safety score is selected. In various embodiments, the route is selected based on route safety scores, route driving times, traffic, driver preferences, or any other appropriate criteria. -
FIG. 6 is a flow diagram illustrating an embodiment of a process for determining a route safety score for a route. In some embodiments, the process ofFIG. 6 implements 506 ofFIG. 5 . In the example shown, in 600, a route is received. In some embodiments, a route comprises a start point, an end point, and a path from the start point to the end point. In 602, a set of route segments associated with the route is determined. In some embodiments, the set of route segments comprises the set of route segments along the path from the start point to the end point. In 604, a next route segment of the set of route segments is selected. In some embodiments, the first route segment of the set of route segments is selected. In 606, a route segment safety score for the route segment is determined. In some embodiments, determining a route segment safety score for the route segment comprises determining a route segment safety score using speed data. In some embodiments, determining a route segment safety score using speed data is performed by a vehicle data server. The vehicle data server stores determined route segment safety scores in a route segment safety score database. In some embodiments, the route segment safety score database is transmitted to a vehicle event recorder and the process ofFIG. 6 is performed by a vehicle event recorder. In some embodiments, determining a route segment safety score comprises looking up a route segment safety score for the route segment in a safety score database. In 608, it is determined whether there are more route segments (e.g., of the set of route segments). In the event it is determined that there are more route segments, control passes to 604. In the event it is determined that there are not more route segments, control passes to 610. In 610, the route segment safety scores are combined to determine a route safety score. In some embodiments, combining the route segment safety scores comprises adding the route segment safety scores. -
FIG. 7 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using speed data. In some embodiments, the process ofFIG. 7 implements 606 ofFIG. 6 . In some embodiments, the process ofFIG. 7 is executed by a vehicle data server. In the example shown, in 700, a route segment is received. In some embodiments, a route segment comprises an indication of a route segment (e.g., a route segment indicator). In 702, data associated with the route segment is received, wherein the data comprises a speed data. In some embodiments, receiving data associated with the route segment comprises retrieving vehicle data from a vehicle database. In some embodiments, data is associated with a plurality of vehicles. In some embodiments, data comprises data received at a plurality of locations within the segment. In some embodiments, data comprises data received at a plurality of times of day. In various embodiments, data comprises one or more of the following (e.g., in addition to a speed data): events, maneuvers, video data, lane change frequency, climate data, topology data, road data, number of lanes, or any other appropriate data. In 704, a route segment safety score is determined using a speed distribution, wherein the speed distribution is based at least in part on the speed data. In some embodiments, the speed data comprises a set of vehicle speeds (e.g., vehicle speeds received from vehicle event recorders), and the speed distribution is determined from the speed data (e.g., by determining the standard deviation of the speed data). In some embodiments, the speed data comprises the speed distribution. -
FIG. 8 is a flow diagram illustrating an embodiment of a process for determining a route segment safety score using a speed distribution. In some embodiments, the process ofFIG. 8 implements 704 ofFIG. 7 . In the example shown, in 800, a speed distribution standard deviation is determined. In some embodiments, a speed distribution standard deviation is determined from speed data using the well-known formula (e.g., range or standard deviation or function of maximum speed and minimum speed, etc.). In some embodiments, a speed distribution standard deviation is received. In 802, a segment safety score is determined based at least in part on the speed distribution standard deviation. In some embodiments, determining a segment safety score comprises scaling the speed distribution standard deviation by a constant (e.g., multiplying by 100). In some embodiments, the segment safety score is based at least in part on other data (e.g., events, maneuvers, video data, lane change frequency, climate data, topology data, road data, number of lanes, etc.). In some embodiments, the segment safety score comprises a linear combination of the speed distribution standard deviation and other data. In some embodiments, a higher safety score indicates that the route segment is less safe. - Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/693,102 US20200088529A1 (en) | 2015-12-10 | 2019-11-22 | Route safety score |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/965,018 US10520321B1 (en) | 2015-12-10 | 2015-12-10 | Route safety score |
US16/693,102 US20200088529A1 (en) | 2015-12-10 | 2019-11-22 | Route safety score |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/965,018 Continuation US10520321B1 (en) | 2015-12-10 | 2015-12-10 | Route safety score |
Publications (1)
Publication Number | Publication Date |
---|---|
US20200088529A1 true US20200088529A1 (en) | 2020-03-19 |
Family
ID=69057433
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/965,018 Active US10520321B1 (en) | 2015-12-10 | 2015-12-10 | Route safety score |
US16/693,102 Pending US20200088529A1 (en) | 2015-12-10 | 2019-11-22 | Route safety score |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/965,018 Active US10520321B1 (en) | 2015-12-10 | 2015-12-10 | Route safety score |
Country Status (1)
Country | Link |
---|---|
US (2) | US10520321B1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11486720B2 (en) * | 2017-11-10 | 2022-11-01 | Volkswagen Aktiengesellschaft | Method and driver assistance system for improving ride comfort of a transportation vehicle and transportation vehicle |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004030450A (en) * | 2002-06-27 | 2004-01-29 | Kobe Steel Ltd | Traffic information guiding apparatus, traffic information guiding method, and system therefor |
US20040153362A1 (en) * | 1996-01-29 | 2004-08-05 | Progressive Casualty Insurance Company | Monitoring system for determining and communicating a cost of insurance |
US20080071465A1 (en) * | 2006-03-03 | 2008-03-20 | Chapman Craig H | Determining road traffic conditions using data from multiple data sources |
US20120109418A1 (en) * | 2009-07-07 | 2012-05-03 | Tracktec Ltd. | Driver profiling |
US20130226622A1 (en) * | 2012-02-08 | 2013-08-29 | Tomtom North America Inc. | Methods Using Speed Distribution Profiles |
US20160086285A1 (en) * | 2007-05-10 | 2016-03-24 | Allstate Insurance Company | Road Segment Safety Rating |
US20160292999A1 (en) * | 2015-03-31 | 2016-10-06 | Here Global B.V. | Method and apparatus for providing dynamic strength decay for predictive traffic |
US20170004705A1 (en) * | 2015-06-30 | 2017-01-05 | Here Global B.V. | Method and apparatus for identifying a bi-modality condition upstream of diverging road segments |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5331561A (en) * | 1992-04-23 | 1994-07-19 | Alliant Techsystems Inc. | Active cross path position correlation device |
US6882923B2 (en) * | 2002-10-17 | 2005-04-19 | Ford Global Technologies, Llc | Adaptive cruise control system using shared vehicle network data |
US9818136B1 (en) * | 2003-02-05 | 2017-11-14 | Steven M. Hoffberg | System and method for determining contingent relevance |
US6931309B2 (en) * | 2003-05-06 | 2005-08-16 | Innosurance, Inc. | Motor vehicle operating data collection and analysis |
EP1886202A4 (en) * | 2005-06-01 | 2011-09-21 | Allstate Insurance Co | Motor vehicle operating data collection and analysis |
US20070288132A1 (en) * | 2006-06-07 | 2007-12-13 | Raytheon Company | Cooperative swarm of unmanned vehicles |
US8606512B1 (en) * | 2007-05-10 | 2013-12-10 | Allstate Insurance Company | Route risk mitigation |
US10096038B2 (en) * | 2007-05-10 | 2018-10-09 | Allstate Insurance Company | Road segment safety rating system |
US20080320087A1 (en) * | 2007-06-22 | 2008-12-25 | Microsoft Corporation | Swarm sensing and actuating |
US20090234859A1 (en) * | 2008-03-17 | 2009-09-17 | International Business Machines Corporation | Swarm creation in a vehicle-to-vehicle network |
US20100188265A1 (en) * | 2009-01-23 | 2010-07-29 | Hill Lawrence W | Network Providing Vehicles with Improved Traffic Status Information |
US8676466B2 (en) * | 2009-04-06 | 2014-03-18 | GM Global Technology Operations LLC | Fail-safe speed profiles for cooperative autonomous vehicles |
US20130046562A1 (en) * | 2009-11-06 | 2013-02-21 | Jeffrey Taylor | Method for gathering, processing, and analyzing data to determine the risk associated with driving behavior |
US9187118B2 (en) * | 2011-12-30 | 2015-11-17 | C & P Technologies, Inc. | Method and apparatus for automobile accident reduction using localized dynamic swarming |
US8768734B2 (en) * | 2012-05-10 | 2014-07-01 | Hartford Fire Insurance Company | System and method for computing and sorting trip similarities using geo-spatial information |
US20150168174A1 (en) * | 2012-06-21 | 2015-06-18 | Cellepathy Ltd. | Navigation instructions |
US10154130B2 (en) * | 2013-08-23 | 2018-12-11 | Cellepathy Inc. | Mobile device context aware determinations |
US10049408B2 (en) * | 2014-04-15 | 2018-08-14 | Speedgauge, Inc. | Assessing asynchronous authenticated data sources for use in driver risk management |
-
2015
- 2015-12-10 US US14/965,018 patent/US10520321B1/en active Active
-
2019
- 2019-11-22 US US16/693,102 patent/US20200088529A1/en active Pending
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040153362A1 (en) * | 1996-01-29 | 2004-08-05 | Progressive Casualty Insurance Company | Monitoring system for determining and communicating a cost of insurance |
JP2004030450A (en) * | 2002-06-27 | 2004-01-29 | Kobe Steel Ltd | Traffic information guiding apparatus, traffic information guiding method, and system therefor |
US20080071465A1 (en) * | 2006-03-03 | 2008-03-20 | Chapman Craig H | Determining road traffic conditions using data from multiple data sources |
US20160086285A1 (en) * | 2007-05-10 | 2016-03-24 | Allstate Insurance Company | Road Segment Safety Rating |
US20120109418A1 (en) * | 2009-07-07 | 2012-05-03 | Tracktec Ltd. | Driver profiling |
US20130226622A1 (en) * | 2012-02-08 | 2013-08-29 | Tomtom North America Inc. | Methods Using Speed Distribution Profiles |
US20160292999A1 (en) * | 2015-03-31 | 2016-10-06 | Here Global B.V. | Method and apparatus for providing dynamic strength decay for predictive traffic |
US20170004705A1 (en) * | 2015-06-30 | 2017-01-05 | Here Global B.V. | Method and apparatus for identifying a bi-modality condition upstream of diverging road segments |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11486720B2 (en) * | 2017-11-10 | 2022-11-01 | Volkswagen Aktiengesellschaft | Method and driver assistance system for improving ride comfort of a transportation vehicle and transportation vehicle |
Also Published As
Publication number | Publication date |
---|---|
US10520321B1 (en) | 2019-12-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11059491B2 (en) | Driving abnormality detection | |
US9996756B2 (en) | Detecting risky driving with machine vision | |
EP3374981B1 (en) | Traffic estimation | |
US9341487B2 (en) | Automatic geofence determination | |
US10395540B2 (en) | Proximity event determination with lane change information | |
US10427655B2 (en) | Systems and methods for detecting surprising events in vehicles | |
US9947149B2 (en) | Proactive driver warning | |
US10068392B2 (en) | Safety score using video data but without video | |
EP3049761B1 (en) | Dynamic uploading protocol | |
US9650051B2 (en) | Autonomous driving comparison and evaluation | |
US10255528B1 (en) | Sensor fusion for lane departure behavior detection | |
CN108701405A (en) | Car-mounted device and road exception caution system | |
CN106575480B (en) | Information processing system, terminal device, program, mobile terminal device, and computer-readable non-volatile tangible recording medium | |
CN112673406B (en) | Method and terminal device for identifying abnormal vehicle parameters in vehicle queue | |
US9772195B2 (en) | Deleting unnecessary map data | |
KR20180097269A (en) | Image information acquisition device, vehicle and method for controlling thereof | |
US20230385665A1 (en) | Environmental condition-based risk level | |
US10040459B1 (en) | Driver fuel score | |
US20200088529A1 (en) | Route safety score | |
JP2019009617A (en) | Abnormality detection device, abnormality detection system, abnormality detection method, abnormality detection program, and recording medium | |
US10262477B1 (en) | Determination of road conditions using sensors associated with a vehicle | |
US10586404B1 (en) | Load imbalance factor estimation | |
US11514733B1 (en) | Extended time scale event detection | |
US9965907B1 (en) | Running characteristic for frequent data readings | |
CN106485914B (en) | Driving behavior recognition method for frequent overtaking on multi-vehicle road condition |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
AS | Assignment |
Owner name: GUGGENHEIM CREDIT SERVICES, LLC, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:LYTX, INC.;REEL/FRAME:063158/0500 Effective date: 20230329 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |