WO2017069733A1 - Enhanced lane behavior detection - Google Patents

Enhanced lane behavior detection Download PDF

Info

Publication number
WO2017069733A1
WO2017069733A1 PCT/US2015/056340 US2015056340W WO2017069733A1 WO 2017069733 A1 WO2017069733 A1 WO 2017069733A1 US 2015056340 W US2015056340 W US 2015056340W WO 2017069733 A1 WO2017069733 A1 WO 2017069733A1
Authority
WO
WIPO (PCT)
Prior art keywords
behavior detection
detection value
lane behavior
data
lane
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.)
Ceased
Application number
PCT/US2015/056340
Other languages
French (fr)
Inventor
Kwaku O. Prakah-Asante
Basavaraj Tonshal
Yifan Chen
Padma Aiswarya KOLISETTY
Hsin-Hsiang Yang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ford Global Technologies LLC
Original Assignee
Ford Global Technologies LLC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ford Global Technologies LLC filed Critical Ford Global Technologies LLC
Priority to CN201580083971.XA priority Critical patent/CN108137049A/en
Priority to MX2018003076A priority patent/MX2018003076A/en
Priority to RU2018114476A priority patent/RU2710125C2/en
Priority to US15/757,993 priority patent/US20180251136A1/en
Priority to DE112015006813.9T priority patent/DE112015006813T5/en
Priority to PCT/US2015/056340 priority patent/WO2017069733A1/en
Priority to GB1807685.1A priority patent/GB2558158A/en
Publication of WO2017069733A1 publication Critical patent/WO2017069733A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W30/00Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
    • B60W30/10Path keeping
    • B60W30/12Lane keeping
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/14Means for informing the driver, warning the driver or prompting a driver intervention
    • B60W50/16Tactile feedback to the driver, e.g. vibration or force feedback to the driver on the steering wheel or the accelerator pedal
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W40/00Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
    • B60W40/08Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
    • B60W40/09Driving style or behaviour
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/14Means for informing the driver, warning the driver or prompting a driver intervention
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/163Wearable computers, e.g. on a belt
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/016Input arrangements with force or tactile feedback as computer generated output to the user
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02Alarms for ensuring the safety of persons
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/16Anti-collision systems
    • G08G1/167Driving aids for lane monitoring, lane changing, e.g. blind spot detection

Definitions

  • Lane Behavior Warning (LBW) systems provide a way for vehicle drivers to adjust their driving behavior if their lane behavior is erratic. Such systems may indicate erratic lane driving behavior so that a vehicle driver can take corrective action. However, not all vehicles include LBW systems, and thus have no way to indicate erratic lane behavior. BRIEF DESCRIPTION OF THE DRAWINGS
  • Figure 1 is a block diagram of an example system including a wearable device providing output indicating lane behavior.
  • Figure 2 is a block diagram of an example process for providing an indication of lane behavior.
  • FIG. 1 illustrates a system 100 including a wearable device 140 communicatively coupled to a vehicle 101 computing device 105.
  • the computing device 105 is programmed to receive collected data 115 from one or more data collectors 110, e.g., vehicle 101 sensors, concerning various metrics related to the vehicle 101.
  • the metrics may include a velocity of the vehicle 101, vehicle 101 acceleration and/or deceleration, data related to vehicle 101 path or steering, biometric data related to a vehicle 101 operator, e.g., heart rate, respiration, pupil dilation, body temperature, state of consciousness, etc.
  • Further examples of such metrics may include measurements of vehicle systems and components (e.g. a steering system, a powertrain system, a brake system, internal sensing, external sensing, etc.).
  • the computing device 105 may be programmed to collect data 115 from the vehicle 101 in which it is installed, sometimes referred to as a host vehicle 101, and/or may be programmed to collect data 115 about a second vehicle 101, e.g., a target vehicle.
  • the computing device 105 is generally programmed for communications on a controller area network (CAN) bus or the like.
  • the computing device 105 may also have a connection to an onboard diagnostics connector (OBD-II). Via the CAN bus, OBD-II, and/or other wired or wireless mechanisms, the computing device 105 may transmit messages to various devices in a vehicle and/or receive messages from the various devices, e.g., controllers, actuators, sensors, etc., including data collectors 110.
  • OBD-II onboard diagnostics connector
  • the CAN bus or the like may be used for communications between devices represented as the computing device 105 in this disclosure.
  • the computing device 105 may be programmed for communicating with the network 120, which, as described below, may include various wired and/or wireless networking technologies, e.g., cellular, Bluetooth, wired and/or wireless packet networks, etc.
  • the computing device 105 may be programmed to generate a lane departure warning.
  • the computing device 105 may receive collected data 115 relating to a vehicle 101 speed, acceleration, deceleration, steering angle, steering angle rate of change, braking, etc., and/or data 115 relating to a roadway, e.g., that the vehicle 101 is crossing land makers, is varying a lateral distance from lane markers, etc.
  • the computer 105 may, e.g., in a known manner, determine that a lane departure is imminent and/or that the vehicle 101 is at a risk of an unintended lane departure over a predetermined threshold, whereupon a lane departure warning may be generated.
  • the computing device 105 may further store instructions to determine whether the vehicle 101 is about to leave a current land and, upon such determination, to actuate one or more vehicle mechanisms without driver intervention, e.g., braking, steering, throttle, etc.
  • the computing device 105 may include or be connected to an output mechanism to indicate a potential lane departure, e.g., sounds and/or visual indicators provided via the vehicle 101 HMI.
  • the data store 106 may be of any known type, e.g., hard disk drives, solid-state drives, servers, or any volatile or non-volatile media.
  • the data store 106 typically stores the collected data 115 sent from the data collectors 110.
  • Collected data 115 may include a variety of data collected in a vehicle 101. Examples of collected data 115 are provided above, and moreover, data 115 is generally collected using one or more data collectors 110, and may additionally include data calculated therefrom in the computer 105, and/or at the server 125. In general, collected data 115 may include any data that may be gathered by the data collectors 110 and/or computed from such data.
  • the system 100 may further include a network 120 connected to a server 125 and a data store 130.
  • the computer 105 may further be programmed to communicate with one or more remote sites such as the server 125, via a network 120, such remote site possibly including a data store 130.
  • the network 120 represents one or more mechanisms by which a vehicle computer 105 may communicate with a remote server 125.
  • the network 120 may be one or more of various wired or wireless communication mechanisms, including any desired combination of wired (e.g., cable and fiber) and/or wireless (e.g., cellular, wireless, satellite, microwave, and radio frequency) communication mechanisms and any desired network topology (or topologies when multiple communication mechanisms are utilized).
  • Exemplary communication networks include wireless communication networks (e.g., using Bluetooth, IEEE 802.11, etc.), local area networks (LAN) and/or wide area networks (WAN), including the Internet, providing data communication services.
  • the server 125 may be programmed to determine an appropriate action for one or more vehicles 101, and to provide direction to the computer 105 to proceed accordingly.
  • the server 125 may be one or more computer servers, each generally including at least one processor and at least one memory, the memory storing instructions executable by the processor, including instructions for carrying out various steps and processes described herein.
  • the server 125 may include or be communicatively coupled to a data store 130 for storing collected data 115, records relating to potential incidents generated as described herein, lane departure profiles, etc. Further, the server 125 may store information related to particular vehicle 101 and additionally one or more other vehicles 101 operating in a geographic area, traffic conditions, weather conditions, etc., within a geographic area, with respect to a particular road, city, etc.
  • the server 125 could be programmed to provide alerts to a particular vehicle 101 and/or other vehicles 101.
  • a wearable device 140 may be any one of a variety of computing devices including a processor and a memory, as well as communication capabilities that is programmed to be worn on a driver’s body.
  • the wearable device 140 may be a watch, a smart watch, a vibrating apparatus, etc. that includes capabilities for wireless communications using IEEE 802.11, Bluetooth, and/or cellular communications protocols. Further, the wearable device 140 may use such communications capabilities to communicate via the network 120 and also directly with a vehicle computer 105, e.g., using Bluetooth.
  • the wearable device 140 may include at least one data collector 145.
  • the data collector 145 may be a motion sensor, e.g., an accelerometer, a gyroscope, a global position sensor, or some other motion sensor.
  • the device 140 may be programmed to, using measurements from the data collector 145, determine the wrist and/or arm movement of the a vehicle 101 occupant wearing the device 140 to, e.g., determine steering wheel movement of the vehicle 101, thereby providing data 115 to a user device 150 to determine lane behavior.
  • the data collector 145 may also collect data on the position of the wearable device 140 lateral to the forward motion of the vehicle 101.
  • the system 100 may include a user device 150.
  • the user device 150 may be any one of a variety of computing devices including a processor and a memory, e.g., a smartphone, a tablet, a personal digital assistant, etc. the user device 150 may use the network 120 to communicate with the vehicle computer 105 and the wearable device 140.
  • the wearable device 140 may send data to the user device 150 for processing.
  • the user device 150 generally includes a processor 155, a data store 156, and a plurality of data collectors 160.
  • the data collectors 160 may include, e.g., a location sensor, a camera, an audio-video collector, etc.
  • the user device 150 may use the collected data 115 to develop a lane behavior profile for a vehicle 101 occupant.
  • the lane behavior profile may incorporate the occupant’s driving habits and characteristics, e.g., age, experience driving, etc., as well as the collected data 115, e.g. road condition, movement of the vehicle 101, etc. For example, more sensitive lane behavior warning thresholds may be established for a novice or less-experienced driver.
  • the lane behavior profile may be used by the user device 150 to detect lane behavior, e.g., to generate a lane behavior warning for the vehicle 101 occupant.
  • the user device 150 may create respective lane behavior profiles for respective vehicle 101 drivers, and may store the profiles in the data store 156.
  • Data collectors 110, 160 may include a variety of devices. For example, various controllers in a vehicle may operate as data collectors 110, 160 to provide data 115 via the CAN bus and/or the network 120, e.g., data 115 relating to vehicle speed, acceleration, system and/or component functionality, etc., of any number of vehicles 101. Further, sensors or the like, global positioning system (GPS) equipment, etc., could be included in a vehicle 101 and/or the user device 150 and configured as data collectors 110, 160 to provide data directly to the computer 105, e.g., via a wired or wireless connection. Sensor data collectors 110 could include mechanisms such as RADAR, LIDAR, sonar, etc.
  • GPS global positioning system
  • data collectors 110, 160 could include cameras, breathalyzers, motion detectors, etc., i.e., data collectors 110, 160 to provide data 115 for evaluating a condition or state of a vehicle 101 operator.
  • FIG. 2 illustrates an example process 200 employing the wearable device 140 and the data collector 145.
  • the process 200 begins in a block 205 where the processor 155 executes programming to collect data from the data collector 145.
  • the process 200 may alternatively be executed in the wearable device 140 or the vehicle computer 105.
  • the data may include wrist and/or arm movement collected by the data collector 145, e.g. an accelerometer. Characteristic movement of the wrist and/or arm of the occupant may indicate steering movement and subsequent movement of the vehicle 101 within a lane. Erratic lane behavior may be caused from and/or detected according to increased variability of the wrist and arm movement on the vehicle steering wheel, e.g., using device 140 accelerometer data as described below.
  • the data sent to the processor 155 may be raw data, i.e., values that have not been transformed, modified, or otherwise processed, sent from the data collector 145, and/or data processed by the wearable device 140.
  • the wearable device 140 and the user device 150 may constitute a distributed processing system.
  • the processor 155 is programmed to collect data from the data collector 160 on the user device 150.
  • the processor 155 can be programmed to collect location data, e.g. global position system (GPS) data, of the user device 150 to determine a change in lateral movement of the vehicle 101.
  • GPS global position system
  • a motion detector data collector 145 could be used to determine lateral movement the wearable device 140, i.e., a component of movement of the device 140 that is substantially perpendicular to a longitudinal axis and/or direction of travel of the vehicle 101. Changes in the lateral position of the user device 150 may indicate movement of the vehicle 101 in a lane, and may be used in generating a lane behavior warning. Furthermore, the user device 150 may collect data 115 from the data collectors 1 10 in the vehicle 101.
  • the processor 155 is programmed to determine a Lane Behavior Detection (LBD) value.
  • LBD Lane Behavior Detection
  • the LBD value characterizes the occupant' s lane behavior based on the wrist and/or arm movement of the wearable device 140 and the change in lateral position movement of the user device 150.
  • the LBD value may be determined by recursive computation of the mean and standard deviation of the accelerometer data from the wearable device 140. For example, the LBD value based on the acceleration data may be determined based on the following equations:
  • a k is the current accelerometer value from the wearable device 140
  • a is a tunable gain between 0 and I that may be predetermined and stored in the data store 156 and/or the server 125
  • k is an index that starts at 1 and signifies the index of the current value, is the mean of the accelerometer values collected
  • LBD k is the LRD value.
  • the LBD value LBD k may be normalized to a value between 0 and 1.
  • the LBD value may be determined for respective periods of time, and may be aggregated and normalized into a value between 0 and 1 to obtain a personalized driver lane behavior character stored in the data store 156 and/or the server 125.
  • a higher LBD value e.g. greater than 0,8 and/or 2-3 standard deviations above a mean LBD value
  • a lower LBD value may indicate steady driving.
  • a LBD value may be determined from recursi ve computation of the mean and standard deviation of the change in lateral position of the vehicle 101 as determined by the user device 150.
  • the LBD value based on the change in lateral data may be determined based on the following equations:
  • a is the tunable gain as described above, is the mean of the change in lateral position value from 1 to k,
  • LBD k is the variance of the lateral position value, and LBD k is determined as in Equation 4 by taking the square root of the variance The LBD value
  • LBD k may be normalized to a value between 0 and 1.
  • the LBD values computed may be used separately or comparatively tracked to, e.g., provide an estimate of the certainty of the most current LBD value.
  • the processor 155 may be programmed to determine a mean LBD value, being the arithmetic average of a set of LBD values over a specified period of time.
  • the wearable device 140 and the user device 150 may be used in any vehicle 101, even a vehicle 101 that does not have a conventional lane negotiation alert system.
  • the processor 155 may use data 115 from the wearable device 140, the user device data collectors 160, and/or the vehicle 101 to determine the LBD value.
  • the processor 155 is programmed to determine whether the LBD value is above a predetermined threshold.
  • the threshold may be determined from a normalized standard deviation of the accelerometer data 115 from the wearable device 140, e.g., 2-3 standard deviations from a mean acceleration value of the wearable device 140, or may be stored on the server 125 and collected by the user device 150.
  • the threshold may be adjusted to account for the specific vehicle occupant, or may be set at a specific value for a specific vehicle 101.
  • the processor 155 may be programmed to use the current LBD value or the mean LBD value. If the LBD value is below the threshold, the process 200 returns to the block 205 to collect more data. Otherwise, the process 200 continues in a block 225.
  • the processor 155 provides an instruction to the wearable device 140 to actuate one or more output mechanisms.
  • the output mechanisms may include haptic output, e.g. a vibration, audio output, and/or visual output, e.g. flashing lights, flashing colors, etc.
  • the one or more output mechanism may be selected according to the occupant. For example, an occupant who is hard of hearing may have a stronger vibration output, while another occupant may prefer a visual output.
  • the driver of the vehicle 101 in the context of the present system 100 can correct their driving behavior, e.g., take evasive and/or avoidance action earlier.
  • the output mechanisms may be actuated before, after, and/or in conjunction with a lane departure warning produced by the computing device 105.
  • the process 200 then ends.
  • the adverb“substantially” modifying an adjective means that a shape, structure, measurement, value, calculation, etc. may deviate from an exact described geometry, distance, measurement, value, calculation, etc., because of imperfections in materials, machining, manufacturing, sensor measurements, computations, processing time, communications time, etc.
  • Computing devices 105 generally each include instructions executable by one or more computing devices such as those identified above, and for carrying out blocks or steps of processes described above.
  • Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, JavaTM, C, C++, Visual Basic, Java Script, Perl, HTML, etc.
  • a processor e.g., a microprocessor
  • receives instructions e.g., from a memory, a computer-readable medium, etc., and executes these instructions, thereby performing one or more processes, including one or more of the processes described herein.
  • Such instructions and other data may be stored and transmitted using a variety of computer-readable media.
  • a file in the computing device 105 is generally a collection of data stored on a computer readable medium, such as a storage medium, a random access memory, etc.
  • a computer-readable medium includes any medium that participates in providing data (e.g., instructions), which may be read by a computer. Such a medium may take many forms, including, but not limited to, non-volatile media, volatile media, etc.
  • Non-volatile media include, for example, optical or magnetic disks and other persistent memory.
  • Volatile media include dynamic random access memory (DRAM), which typically constitutes a main memory.
  • DRAM dynamic random access memory
  • Computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, or any other medium from which a computer can read.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Mathematical Physics (AREA)
  • Business, Economics & Management (AREA)
  • Emergency Management (AREA)
  • Traffic Control Systems (AREA)
  • Image Analysis (AREA)
  • Indicating Or Recording The Presence, Absence, Or Direction Of Movement (AREA)

Abstract

A lane behavior detection value that is a measure of wrist movement of a vehicle occupant is determined. A mechanism in a wearable device is actuated when the lane behavior detection value exceeds a threshold.

Description

ENHANCED LANE BEHAVIOR DETECTION
BACKGROUND
[0001] Lane Behavior Warning (LBW) systems provide a way for vehicle drivers to adjust their driving behavior if their lane behavior is erratic. Such systems may indicate erratic lane driving behavior so that a vehicle driver can take corrective action. However, not all vehicles include LBW systems, and thus have no way to indicate erratic lane behavior. BRIEF DESCRIPTION OF THE DRAWINGS
[0002] Figure 1 is a block diagram of an example system including a wearable device providing output indicating lane behavior.
[0003] Figure 2 is a block diagram of an example process for providing an indication of lane behavior. DETAILED DESCRIPTION
[0004] Figure 1 illustrates a system 100 including a wearable device 140 communicatively coupled to a vehicle 101 computing device 105. The computing device 105 is programmed to receive collected data 115 from one or more data collectors 110, e.g., vehicle 101 sensors, concerning various metrics related to the vehicle 101. For example, the metrics may include a velocity of the vehicle 101, vehicle 101 acceleration and/or deceleration, data related to vehicle 101 path or steering, biometric data related to a vehicle 101 operator, e.g., heart rate, respiration, pupil dilation, body temperature, state of consciousness, etc. Further examples of such metrics may include measurements of vehicle systems and components (e.g. a steering system, a powertrain system, a brake system, internal sensing, external sensing, etc.). The computing device 105 may be programmed to collect data 115 from the vehicle 101 in which it is installed, sometimes referred to as a host vehicle 101, and/or may be programmed to collect data 115 about a second vehicle 101, e.g., a target vehicle. [0005] The computing device 105 is generally programmed for communications on a controller area network (CAN) bus or the like. The computing device 105 may also have a connection to an onboard diagnostics connector (OBD-II). Via the CAN bus, OBD-II, and/or other wired or wireless mechanisms, the computing device 105 may transmit messages to various devices in a vehicle and/or receive messages from the various devices, e.g., controllers, actuators, sensors, etc., including data collectors 110. Alternatively or additionally, in cases where the computing device 105 actually comprises multiple devices, the CAN bus or the like may be used for communications between devices represented as the computing device 105 in this disclosure. In addition, the computing device 105 may be programmed for communicating with the network 120, which, as described below, may include various wired and/or wireless networking technologies, e.g., cellular, Bluetooth, wired and/or wireless packet networks, etc.
[0006] The computing device 105 may be programmed to generate a lane departure warning. For example, the computing device 105 may receive collected data 115 relating to a vehicle 101 speed, acceleration, deceleration, steering angle, steering angle rate of change, braking, etc., and/or data 115 relating to a roadway, e.g., that the vehicle 101 is crossing land makers, is varying a lateral distance from lane markers, etc. Based on such collected data 115 and possibly also a lane departure profile of a vehicle 101 driver as discussed below, the computer 105 may, e.g., in a known manner, determine that a lane departure is imminent and/or that the vehicle 101 is at a risk of an unintended lane departure over a predetermined threshold, whereupon a lane departure warning may be generated. The computing device 105 may further store instructions to determine whether the vehicle 101 is about to leave a current land and, upon such determination, to actuate one or more vehicle mechanisms without driver intervention, e.g., braking, steering, throttle, etc. Further, the computing device 105 may include or be connected to an output mechanism to indicate a potential lane departure, e.g., sounds and/or visual indicators provided via the vehicle 101 HMI. The data store 106 may be of any known type, e.g., hard disk drives, solid-state drives, servers, or any volatile or non-volatile media. The data store 106 typically stores the collected data 115 sent from the data collectors 110. [0007] Collected data 115 may include a variety of data collected in a vehicle 101. Examples of collected data 115 are provided above, and moreover, data 115 is generally collected using one or more data collectors 110, and may additionally include data calculated therefrom in the computer 105, and/or at the server 125. In general, collected data 115 may include any data that may be gathered by the data collectors 110 and/or computed from such data.
[0008] The system 100 may further include a network 120 connected to a server 125 and a data store 130. The computer 105 may further be programmed to communicate with one or more remote sites such as the server 125, via a network 120, such remote site possibly including a data store 130. The network 120 represents one or more mechanisms by which a vehicle computer 105 may communicate with a remote server 125. Accordingly, the network 120 may be one or more of various wired or wireless communication mechanisms, including any desired combination of wired (e.g., cable and fiber) and/or wireless (e.g., cellular, wireless, satellite, microwave, and radio frequency) communication mechanisms and any desired network topology (or topologies when multiple communication mechanisms are utilized). Exemplary communication networks include wireless communication networks (e.g., using Bluetooth, IEEE 802.11, etc.), local area networks (LAN) and/or wide area networks (WAN), including the Internet, providing data communication services.
[0009] The server 125 may be programmed to determine an appropriate action for one or more vehicles 101, and to provide direction to the computer 105 to proceed accordingly. The server 125 may be one or more computer servers, each generally including at least one processor and at least one memory, the memory storing instructions executable by the processor, including instructions for carrying out various steps and processes described herein. The server 125 may include or be communicatively coupled to a data store 130 for storing collected data 115, records relating to potential incidents generated as described herein, lane departure profiles, etc. Further, the server 125 may store information related to particular vehicle 101 and additionally one or more other vehicles 101 operating in a geographic area, traffic conditions, weather conditions, etc., within a geographic area, with respect to a particular road, city, etc. The server 125 could be programmed to provide alerts to a particular vehicle 101 and/or other vehicles 101.
[0010] A wearable device 140 may be any one of a variety of computing devices including a processor and a memory, as well as communication capabilities that is programmed to be worn on a driver’s body. For example, the wearable device 140 may be a watch, a smart watch, a vibrating apparatus, etc. that includes capabilities for wireless communications using IEEE 802.11, Bluetooth, and/or cellular communications protocols. Further, the wearable device 140 may use such communications capabilities to communicate via the network 120 and also directly with a vehicle computer 105, e.g., using Bluetooth. The wearable device 140 may include at least one data collector 145. The data collector 145 may be a motion sensor, e.g., an accelerometer, a gyroscope, a global position sensor, or some other motion sensor. The device 140 may be programmed to, using measurements from the data collector 145, determine the wrist and/or arm movement of the a vehicle 101 occupant wearing the device 140 to, e.g., determine steering wheel movement of the vehicle 101, thereby providing data 115 to a user device 150 to determine lane behavior. The data collector 145 may also collect data on the position of the wearable device 140 lateral to the forward motion of the vehicle 101.
[0011] The system 100 may include a user device 150. The user device 150 may be any one of a variety of computing devices including a processor and a memory, e.g., a smartphone, a tablet, a personal digital assistant, etc. the user device 150 may use the network 120 to communicate with the vehicle computer 105 and the wearable device 140. The wearable device 140 may send data to the user device 150 for processing. The user device 150 generally includes a processor 155, a data store 156, and a plurality of data collectors 160. The data collectors 160 may include, e.g., a location sensor, a camera, an audio-video collector, etc.
[0012] The user device 150 may use the collected data 115 to develop a lane behavior profile for a vehicle 101 occupant. The lane behavior profile may incorporate the occupant’s driving habits and characteristics, e.g., age, experience driving, etc., as well as the collected data 115, e.g. road condition, movement of the vehicle 101, etc. For example, more sensitive lane behavior warning thresholds may be established for a novice or less-experienced driver. The lane behavior profile may be used by the user device 150 to detect lane behavior, e.g., to generate a lane behavior warning for the vehicle 101 occupant. The user device 150 may create respective lane behavior profiles for respective vehicle 101 drivers, and may store the profiles in the data store 156.
[0013] Data collectors 110, 160 may include a variety of devices. For example, various controllers in a vehicle may operate as data collectors 110, 160 to provide data 115 via the CAN bus and/or the network 120, e.g., data 115 relating to vehicle speed, acceleration, system and/or component functionality, etc., of any number of vehicles 101. Further, sensors or the like, global positioning system (GPS) equipment, etc., could be included in a vehicle 101 and/or the user device 150 and configured as data collectors 110, 160 to provide data directly to the computer 105, e.g., via a wired or wireless connection. Sensor data collectors 110 could include mechanisms such as RADAR, LIDAR, sonar, etc. sensors that could be deployed to measure a distance between the vehicle 101 and other vehicles or objects. Yet other data collectors 110, 160 could include cameras, breathalyzers, motion detectors, etc., i.e., data collectors 110, 160 to provide data 115 for evaluating a condition or state of a vehicle 101 operator.
[0014] Figure 2 illustrates an example process 200 employing the wearable device 140 and the data collector 145. The process 200 begins in a block 205 where the processor 155 executes programming to collect data from the data collector 145. The process 200 may alternatively be executed in the wearable device 140 or the vehicle computer 105. In particular, the data may include wrist and/or arm movement collected by the data collector 145, e.g. an accelerometer. Characteristic movement of the wrist and/or arm of the occupant may indicate steering movement and subsequent movement of the vehicle 101 within a lane. Erratic lane behavior may be caused from and/or detected according to increased variability of the wrist and arm movement on the vehicle steering wheel, e.g., using device 140 accelerometer data as described below. The data sent to the processor 155 may be raw data, i.e., values that have not been transformed, modified, or otherwise processed, sent from the data collector 145, and/or data processed by the wearable device 140. Thus, the wearable device 140 and the user device 150 may constitute a distributed processing system. [0015] Next, in a block 210, the processor 155 is programmed to collect data from the data collector 160 on the user device 150. For example, the processor 155 can be programmed to collect location data, e.g. global position system (GPS) data, of the user device 150 to determine a change in lateral movement of the vehicle 101. In another example, a motion detector data collector 145 could be used to determine lateral movement the wearable device 140, i.e., a component of movement of the device 140 that is substantially perpendicular to a longitudinal axis and/or direction of travel of the vehicle 101. Changes in the lateral position of the user device 150 may indicate movement of the vehicle 101 in a lane, and may be used in generating a lane behavior warning. Furthermore, the user device 150 may collect data 115 from the data collectors 1 10 in the vehicle 101.
[0Θ16] Next, in a block 215, the processor 155 is programmed to determine a Lane Behavior Detection (LBD) value. The LBD value characterizes the occupant' s lane behavior based on the wrist and/or arm movement of the wearable device 140 and the change in lateral position movement of the user device 150. The LBD value may be determined by recursive computation of the mean and standard deviation of the accelerometer data from the wearable device 140. For example, the LBD value based on the acceleration data may be determined based on the following equations:
Figure imgf000007_0001
where ak is the current accelerometer value from the wearable device 140, a: is a tunable gain between 0 and I that may be predetermined and stored in the data store 156 and/or the server 125, k is an index that starts at 1 and signifies the index of the current value, is the mean of the accelerometer values collected
Figure imgf000007_0003
between I and fe, is the variance of the accelerometer value, and LBDk is
Figure imgf000007_0002
the LRD value. The LBD value LBDk may be normalized to a value between 0 and 1.
[0017] The LBD value may be determined for respective periods of time, and may be aggregated and normalized into a value between 0 and 1 to obtain a personalized driver lane behavior character stored in the data store 156 and/or the server 125. A higher LBD value (e.g. greater than 0,8 and/or 2-3 standard deviations above a mean LBD value) may indicate erratic lane behavior with a larger amount of lateral movement within the lane, e.g., a novice driver or a driver applying techniques for vehicles with loose steering. A lower LBD value (e.g. less than 0.3) may indicate steady driving. Similarly, a LBD value may be determined from recursi ve computation of the mean and standard deviation of the change in lateral position of the vehicle 101 as determined by the user device 150. For example, the LBD value based on the change in lateral data may be determined based on the following equations:
Figure imgf000008_0001
where lk is the current lateral position value, a is the tunable gain as described above, is the mean of the change in lateral position value from 1 to k,
Figure imgf000008_0003
Figure imgf000008_0002
is the variance of the lateral position value, and LBDk is determined as in Equation 4 by taking the square root of the variance The LBD value
Figure imgf000008_0004
LBDk may be normalized to a value between 0 and 1.
[0018] The LBD values computed may be used separately or comparatively tracked to, e.g., provide an estimate of the certainty of the most current LBD value. The processor 155 may be programmed to determine a mean LBD value, being the arithmetic average of a set of LBD values over a specified period of time. Thus, the wearable device 140 and the user device 150 may be used in any vehicle 101, even a vehicle 101 that does not have a conventional lane negotiation alert system. The processor 155 may use data 115 from the wearable device 140, the user device data collectors 160, and/or the vehicle 101 to determine the LBD value.
[0019] Next, in a block 220, the processor 155 is programmed to determine whether the LBD value is above a predetermined threshold. The threshold may be determined from a normalized standard deviation of the accelerometer data 115 from the wearable device 140, e.g., 2-3 standard deviations from a mean acceleration value of the wearable device 140, or may be stored on the server 125 and collected by the user device 150. The threshold may be adjusted to account for the specific vehicle occupant, or may be set at a specific value for a specific vehicle 101. The processor 155 may be programmed to use the current LBD value or the mean LBD value. If the LBD value is below the threshold, the process 200 returns to the block 205 to collect more data. Otherwise, the process 200 continues in a block 225.
[0020] In the block 225, the processor 155 provides an instruction to the wearable device 140 to actuate one or more output mechanisms. The output mechanisms may include haptic output, e.g. a vibration, audio output, and/or visual output, e.g. flashing lights, flashing colors, etc. The one or more output mechanism may be selected according to the occupant. For example, an occupant who is hard of hearing may have a stronger vibration output, while another occupant may prefer a visual output. Thus, the driver of the vehicle 101 in the context of the present system 100 can correct their driving behavior, e.g., take evasive and/or avoidance action earlier. The output mechanisms may be actuated before, after, and/or in conjunction with a lane departure warning produced by the computing device 105. The process 200 then ends.
[0021] As used herein, the adverb“substantially” modifying an adjective means that a shape, structure, measurement, value, calculation, etc. may deviate from an exact described geometry, distance, measurement, value, calculation, etc., because of imperfections in materials, machining, manufacturing, sensor measurements, computations, processing time, communications time, etc.
[0022] Computing devices 105 generally each include instructions executable by one or more computing devices such as those identified above, and for carrying out blocks or steps of processes described above. Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, Java™, C, C++, Visual Basic, Java Script, Perl, HTML, etc. In general, a processor (e.g., a microprocessor) receives instructions, e.g., from a memory, a computer-readable medium, etc., and executes these instructions, thereby performing one or more processes, including one or more of the processes described herein. Such instructions and other data may be stored and transmitted using a variety of computer-readable media. A file in the computing device 105 is generally a collection of data stored on a computer readable medium, such as a storage medium, a random access memory, etc.
[0023] A computer-readable medium includes any medium that participates in providing data (e.g., instructions), which may be read by a computer. Such a medium may take many forms, including, but not limited to, non-volatile media, volatile media, etc. Non-volatile media include, for example, optical or magnetic disks and other persistent memory. Volatile media include dynamic random access memory (DRAM), which typically constitutes a main memory. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, or any other medium from which a computer can read.
[0024] With regard to the media, processes, systems, methods, etc. described herein, it should be understood that, although the steps of such processes, etc. have been described as occurring according to a certain ordered sequence, such processes could be practiced with the described steps performed in an order other than the order described herein. It further should be understood that certain steps could be performed simultaneously, that other steps could be added, or that certain steps described herein could be omitted. For example, in the process 200, one or more of the steps could be omitted, or the steps could be executed in a different order than shown in Figure 2. In other words, the descriptions of systems and/or processes herein are provided for the purpose of illustrating certain embodiments, and should in no way be construed so as to limit the disclosed subject matter.
[0025] Accordingly, it is to be understood that the present disclosure, including the above description and the accompanying figures and below claims, is intended to be illustrative and not restrictive. Many embodiments and applications other than the examples provided would be apparent to those of skill in the art upon reading the above description. The scope of the invention should be determined, not with reference to the above description, but should instead be determined with reference to claims appended hereto and/or included in a non-provisional patent application based hereon, along with the full scope of equivalents to which such claims are entitled. It is anticipated and intended that future developments will occur in the arts discussed herein, and that the disclosed systems and methods will be incorporated into such future embodiments. In sum, it should be understood that the disclosed subject matter is capable of modification and variation.

Claims

1. A system, comprising a computer including a processor and a memory, the memory storing instructions executable by the computer to:
determine a lane behavior detection value that is a measure of wrist movement of a vehicle occupant; and
actuate a mechanism in a wearable device when the lane behavior detection value exceeds a threshold.
2. The system of claim 1, wherein the instructions include instructions to determine the lane behavior detection value based at least in part on the arm movement of the vehicle occupant.
3. The system of claim 1, wherein the mechanism is a haptic output mechanism.
4. The system of claim 1, wherein the instructions include instructions to determine the lane behavior detection value in a handheld user device.
5. The system of claim 4, wherein the instructions include instructions to determine the lane behavior detection value in the handheld user device and the wearable device.
6. The system of claim 1, wherein the instructions include instructions to determine the lane behavior detection value based at least in part on location data of a handheld user device.
7. The system of claim 1, further comprising at least one of an accelerometer, a gyroscope, and a global position system.
8. The system of claim 1, wherein the wearable device includes an accelerometer.
9. The system of claim 1, wherein the instructions include instructions to determine a mean lane behavior detection value from a set of previous lane behavior detection values.
10. The system of claim 9, wherein the instructions include instructions to actuate the mechanism when the mean lane behavior detection value exceeds the threshold.
11. A method, comprising:
determining a lane behavior detection value that is a measure of wrist movement of a vehicle occupant; and
actuating a mechanism in a wearable device when the lane behavior detection value exceeds a threshold.
12. The method of claim 11, further comprising determining the lane behavior detection value based at least in part on the arm movement of the vehicle occupant.
13. The method of claim 11, wherein the mechanism is a haptic output mechanism.
14. The method of claim 11, further comprising determining the lane behavior detection value in a handheld user device.
15. The method of claim 14, further comprising determining the lane behavior detection value in the handheld user device and the wearable device.
16. The method of claim 11, further comprising determining the lane behavior detection value based at least in part on location data of a handheld user device.
17. The method of claim 11, further comprising at least one of an accelerometer, a gyroscope, and a global position system.
18. The method of claim 11, wherein the wearable device includes an accelerometer.
19. The method of claim 11, further comprising determining a mean lane behavior detection value from a set of previous lane behavior detection values.
20. The method of claim 19, further comprising actuating the mechanism when the mean lane behavior detection value exceeds the threshold.
PCT/US2015/056340 2015-10-20 2015-10-20 Enhanced lane behavior detection Ceased WO2017069733A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN201580083971.XA CN108137049A (en) 2015-10-20 2015-10-20 Enhance track behavioral value
MX2018003076A MX2018003076A (en) 2015-10-20 2015-10-20 IMPROVED BEHAVIOR DETECTION IN LANE.
RU2018114476A RU2710125C2 (en) 2015-10-20 2015-10-20 System and method for improved behaviour detection within lane
US15/757,993 US20180251136A1 (en) 2015-10-20 2015-10-20 Enhanced lane behavior detection
DE112015006813.9T DE112015006813T5 (en) 2015-10-20 2015-10-20 Improved detection of the tracking behavior
PCT/US2015/056340 WO2017069733A1 (en) 2015-10-20 2015-10-20 Enhanced lane behavior detection
GB1807685.1A GB2558158A (en) 2015-10-20 2015-10-20 Enhanced lane behavior detection

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2015/056340 WO2017069733A1 (en) 2015-10-20 2015-10-20 Enhanced lane behavior detection

Publications (1)

Publication Number Publication Date
WO2017069733A1 true WO2017069733A1 (en) 2017-04-27

Family

ID=58557863

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/056340 Ceased WO2017069733A1 (en) 2015-10-20 2015-10-20 Enhanced lane behavior detection

Country Status (7)

Country Link
US (1) US20180251136A1 (en)
CN (1) CN108137049A (en)
DE (1) DE112015006813T5 (en)
GB (1) GB2558158A (en)
MX (1) MX2018003076A (en)
RU (1) RU2710125C2 (en)
WO (1) WO2017069733A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080174451A1 (en) * 2007-01-23 2008-07-24 International Business Machines Corporation Method and system for improving driver safety and situational awareness
US8405522B2 (en) * 2010-09-30 2013-03-26 Ford Global Technologies, Llc Lane departure haptic warning with compensation for road-caused vibration
US9135803B1 (en) * 2014-04-17 2015-09-15 State Farm Mutual Automobile Insurance Company Advanced vehicle operator intelligence system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1098179C (en) * 2000-04-30 2003-01-08 王正键 Intelligent motor vehicle driver monitoring instrument for running safety and its monitoring method
US7908060B2 (en) * 2007-07-31 2011-03-15 International Business Machines Corporation Method and system for blind spot identification and warning utilizing portable and wearable devices
RU106589U1 (en) * 2011-02-11 2011-07-20 Общество с ограниченной ответственностью "Научно-производственный центр "Динамика" HARDWARE AND SOFTWARE COMPLEX OF DRIVING QUALITY CONTROL
HK1204132A1 (en) * 2012-01-13 2015-11-06 Pulse Function F6 Limited Telematics system with 3d inertial sensors

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080174451A1 (en) * 2007-01-23 2008-07-24 International Business Machines Corporation Method and system for improving driver safety and situational awareness
US8405522B2 (en) * 2010-09-30 2013-03-26 Ford Global Technologies, Llc Lane departure haptic warning with compensation for road-caused vibration
US9135803B1 (en) * 2014-04-17 2015-09-15 State Farm Mutual Automobile Insurance Company Advanced vehicle operator intelligence system

Also Published As

Publication number Publication date
GB2558158A (en) 2018-07-04
US20180251136A1 (en) 2018-09-06
GB201807685D0 (en) 2018-06-27
MX2018003076A (en) 2018-06-11
RU2710125C2 (en) 2019-12-24
RU2018114476A3 (en) 2019-11-21
RU2018114476A (en) 2019-11-21
CN108137049A (en) 2018-06-08
DE112015006813T5 (en) 2018-05-24

Similar Documents

Publication Publication Date Title
US9539999B2 (en) Vehicle operator monitoring and operations adjustments
US10037031B2 (en) Vehicle operation states
CN105774805B (en) System for estimating lane and method thereof
US10528833B1 (en) Health monitoring system operable in a vehicle environment
CN104887253B (en) Driver fatigue detection
US9925841B2 (en) Active vehicle suspension
MX2014015331A (en) Affective user interface in an autonomous vehicle.
JP7051424B2 (en) Anomaly detection device
US10435036B2 (en) Enhanced curve negotiation
US10589741B2 (en) Enhanced collision avoidance
US20190139404A1 (en) Method, device and system for wrong-way driver detection
JP2012059058A (en) Risk estimation device and program
JP2017191502A (en) Driving support system
US10562450B2 (en) Enhanced lane negotiation
JP5688811B2 (en) Driver state estimation device
JP5688809B2 (en) Driver state estimation device
US20180251136A1 (en) Enhanced lane behavior detection
JP2012018527A (en) Vehicle state recording device
JP5688810B2 (en) Driver state estimation device
US10493913B2 (en) Enhanced rear obstacle detection

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15906817

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15757993

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: MX/A/2018/003076

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 112015006813

Country of ref document: DE

ENP Entry into the national phase

Ref document number: 201807685

Country of ref document: GB

Kind code of ref document: A

Free format text: PCT FILING DATE = 20151020

WWE Wipo information: entry into national phase

Ref document number: 2018114476

Country of ref document: RU

122 Ep: pct application non-entry in european phase

Ref document number: 15906817

Country of ref document: EP

Kind code of ref document: A1