GB2560096A - Collision mitigation and avoidance - Google Patents
Collision mitigation and avoidance Download PDFInfo
- Publication number
- GB2560096A GB2560096A GB1800316.0A GB201800316A GB2560096A GB 2560096 A GB2560096 A GB 2560096A GB 201800316 A GB201800316 A GB 201800316A GB 2560096 A GB2560096 A GB 2560096A
- Authority
- GB
- United Kingdom
- Prior art keywords
- target
- targets
- computing device
- confidence level
- block
- 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.)
- Withdrawn
Links
- 230000000116 mitigating effect Effects 0.000 title description 7
- 238000000034 method Methods 0.000 claims abstract description 124
- 238000004590 computer program Methods 0.000 claims description 3
- 238000005259 measurement Methods 0.000 abstract description 11
- 230000033001 locomotion Effects 0.000 abstract description 6
- 238000004422 calculation algorithm Methods 0.000 abstract description 4
- 230000008569 process Effects 0.000 description 93
- 238000004891 communication Methods 0.000 description 12
- 230000001133 acceleration Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 230000008859 change Effects 0.000 description 6
- 239000013598 vector Substances 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 230000000007 visual effect Effects 0.000 description 4
- 238000002485 combustion reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003044 adaptive effect Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002265 prevention Effects 0.000 description 2
- 230000003466 anti-cipated effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000003754 machining Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000005226 mechanical processes and functions Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT 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/00—Purposes 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/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/095—Predicting travel path or likelihood of collision
- B60W30/0956—Predicting travel path or likelihood of collision the prediction being responsive to traffic or environmental parameters
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT 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/00—Purposes 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/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/095—Predicting travel path or likelihood of collision
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT 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/00—Purposes 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/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/09—Taking automatic action to avoid collision, e.g. braking and steering
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT 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/00—Purposes 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/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/095—Predicting travel path or likelihood of collision
- B60W30/0953—Predicting travel path or likelihood of collision the prediction being responsive to vehicle dynamic parameters
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/16—Anti-collision systems
- G08G1/164—Centralised systems, e.g. external to vehicles
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/16—Anti-collision systems
- G08G1/166—Anti-collision systems for active traffic, e.g. moving vehicles, pedestrians, bikes
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT 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
- B60W2554/00—Input parameters relating to objects
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT 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
- B60W2554/00—Input parameters relating to objects
- B60W2554/80—Spatial relation or speed relative to objects
- B60W2554/801—Lateral distance
Landscapes
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Transportation (AREA)
- Mechanical Engineering (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Traffic Control Systems (AREA)
Abstract
A collision avoidance method includes determining a confidence level of a potential collision for each target based on the targets heading angle and distance from a host vehicle 725. A threat number is determined for each target when its respective confidence level is above a threshold 730. A vehicle component, which may be a warning device, steering, braking or accelerator, is actuated based on the threat number 735. Targets may be categorised as oncoming 710 or straight crossing 715. The number of targets may be filtered to a predetermined maximum number and the furthest target may be dropped if a closer target if a closer target is identified 720. The confidence levels may range from 0, a low probability of collision, to 4, a high probability of collision and the confidence level. Previous measurements of position, speed and heading may be used in a motion tracking algorithm to predict future positions of the targets.
Description
(71) Applicant(s):
Ford Global Technologies, LLC Fairlane Plaza South, Suite 800,
330 Town Center Drive, Dearborn 48126-2738, Michigan, United States of America (51) INT CL:
B60W 30/095 (2012.01) (56) Documents Cited:
EP 3249630 A2 US 20160109571 A1 US 20140297171 A1 US 20090045928 A1 (58) Field of Search:
INT CL B60W
JP 2012014257 A US 20160052515 A1 US 20090192710 A1
Other: WPI, EPODOC, Patent Fulltext.
(72) Inventor(s):
Wangdong Luo Nanjun Liu Kun Deng Alex Maurice Miller (74) Agent and/or Address for Service:
Harrison IP Limited
Ebor House, Millfield Lane, Nether Poppleton, YORK, YO26 6QY, United Kingdom (54) Title of the Invention: Collision mitigation and avoidance Abstract Title: Vehicular collision avoidance (57) A collision avoidance method includes determining a confidence level of a potential collision for each target based on the target’s heading angle and distance from a host vehicle 725. A threat number is determined for each target when its respective confidence level is above a threshold 730. A vehicle component, which may be a warning device, steering, braking or accelerator, is actuated based on the threat number 735. Targets may be categorised as oncoming 710 or straight crossing 715. The number of targets may be filtered to a predetermined maximum number and the furthest target may be dropped if a closer target if a closer target is identified 720. The confidence levels may range from 0, a low probability of collision, to 4, a high probability of collision and the confidence level. Previous measurements of position, speed and heading may be used in a motion tracking algorithm to predict future positions of the targets.
identify targets for OCTAP '710
Identify forgets for SCP 715
FIG. 7
1/11
2/11
3/11
4/11
'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXmXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX^^i*
5/11
6/11
7/11
8/11 c800 \ (START
Identify c tar 8( | ...................... incoming r |
1 | |
Determine distance and heading angle for the target 810 |
YES
Determine target not to be OCTAP target 825
NO
YES
Determine target to be OCTAP | 1 | |
Determine target to be | ||
forget Type 1 | OCTAP target Type 0 | |
840 | 850 |
Determine to'
OCTAP arget
9/11
YES
10/11
1000^ /
x*
NO
11/11
Intellectual
Property
Office
Application No. GB1800316.0
RTM
Date :23 June 2018
The following terms are registered trade marks and should be read as such wherever they occur in this document:
Visual Basic pi8
Intellectual Property Office is an operating name of the Patent Office www.gov.uk/ipo
COLLISION MITIGATION AND AVOIDANCE
BACKGROUND [0001] Vehicle collisions often occur at intersections. Collision mitigation between a host vehicle and a target may be difficult and expensive to implement. For example, determining a threat assessment for the target may require data from a plurality of sensors. Each of the plurality of sensors may require additional computation from a vehicle computer, increasing the difficulty of performing collision mitigation for multiple targets. Furthermore, performing the threat assessment for several targets can be computationally costly for the vehicle computer, especially when certain targets may have a lower risk of a collision.
BRIEF DESCRIPTION OF THE DRAWINGS [0002] Figure 1 is a block diagram of an example system for collision prevention and mitigation.
[0003] Figure 2 illustrates an example intersection with a host vehicle and a plurality of targets.
[0004] Figure 3 illustrates example measurements taken by the host vehicle of the target.
[0005] Figure 4 illustrates other example measurements taken by the host vehicle of the target.
[0006] Figure 5 illustrates another example intersection with a plurality of longitudinally oncoming targets.
[0007] Figure 6 illustrates another example intersection with a plurality of laterally moving targets.
[0008] Figure 7 is a block diagram of an example process for performing a threat assessment on a plurality of targets.
[0009] Figure 8 is a block diagram of an example process for identifying longitudinally oncoming targets.
[0010] Figure 9 is a block diagram of an example process for identifying laterally moving targets.
[0011] Figure 10 is a block diagram of an example process for selecting a predetermined number of targets for threat assessment.
[0012] Figure 11 is a block diagram of an example process for determining a confidence level for each target.
DETAILED DESCRIPTION [0013] A system includes a computer programmed to determine respective confidence levels of a potential collision for each of a plurality of targets based on each target’s heading angle and distance from a host vehicle. The computer is programmed to determine a threat number for each target when its respective confidence level is above a threshold. The computer is programmed to actuate a vehicle component based on the threat number.
[0014] The computer can be programmed to determine whether each of the targets is one of a laterally moving target and a longitudinally oncoming target.
[0015] The computer can be programmed to determine whether the target heading angle is within a first heading angle range.
[0016] The computer can be programmed to determine, for one of the targets, whether the target heading angle is within a second heading angle range and the target was previously determined to have a confidence level above the threshold.
[0017] The computer can be programmed to determine whether the distance is below a distance threshold.
[0018] The computer can be programmed to select a predetermined maximum number of targets based on the distance. The computer can be programmed to remove a farthest target from the selected targets upon identifying a closer target. The computer can be programmed to increase a confidence counter for one of the targets when the target was previously one of the selected targets. The computer can be programmed to increase the confidence level for one of the targets based on the confidence counter of the target.
[0019] The computer can be programmed to determine the confidence level based on a previously determined confidence level.
[0020] A method includes determining a respective confidence level of a potential collision for each of a plurality of targets based on each target’s heading angle and distance from a host vehicle. The method includes determining a threat number for each target when its respective confidence level is above a threshold The method includes actuating a vehicle component based on the threat number.
[0021] The method can include determining whether each of the targets is one of a laterally moving target and a longitudinally oncoming target.
[0022] The method can include determining whether the target heading angle is within a first heading angle range.
[0023] The method can include determining, for one of the targets, whether the target heading angle is within a second heading angle range and the target was previously determined to have a confidence level above the threshold.
[0024] The method can include determining whether the distance is below a distance threshold.
[0025] The method can include selecting a predetermined maximum number of targets based on the distance. The method can include removing a farthest target from the selected targets upon identifying a closer target. The method can include increasing a confidence counter for one of the targets when the target was previously one of the selected targets. The method can include increasing the confidence level for one of the targets based on the confidence counter of the target.
[0026] The method can include determining the confidence level based on a previously determined confidence level.
[0027] A computing device in a vehicle can be programmed to determine a confidence level of a potential collision, based on a target heading angle and respective distances between a host vehicle and one or more targets. The computing device can be further programmed to determine a threat number for each target when the confidence level is above a threshold. The computing device can actuate a vehicle component based on the threat number.
[0028] Further disclosed is a computing device programmed to execute any of the above method steps. Yet further disclosed is a vehicle comprising the computing device. Yet further disclosed is a computer program product, comprising a computer readable medium storing instructions executable by a computer processor, to execute any of the above method steps. [0029] By determining the threat number for targets with confidence levels above the threshold, the computing device reduces the total number of targets on which the threat assessment is performed. Thus, the total computations performed by the computing device is reduced, and the computing device can more quickly identify potential collisions.
[0030] Figure 1 illustrates a system 100 for collision prevention and mitigation. Unless indicated otherwise in this disclosure, an “intersection” is defined as a location where two or more vehicles’ current or potential future trajectories cross. Thus, an intersection could be at any location on a surface where two or more vehicles could collide, e.g. a road, a driveway, a parking lot, an entrance to a public road, driving paths, etc. Accordingly, an intersection is determined by identifying a location where two or more vehicles may meet, i.e., collide. Such determination uses potential future trajectories of a host vehicle 101 as well as nearby other vehicles and/or other objects.
[0031] A computing device 105 in the vehicle 101 is programmed to receive collected data 115 from one or more sensors 110. For example, vehicle 101 data 115 may include a location of the vehicle 101, a location of a target, etc. Location data may be in a known form, e.g., geocoordinates such as latitude and longitude coordinates obtained via a navigation system, as is known, that uses the Global Positioning System (GPS). Further examples of data 115 can include measurements of vehicle 101 systems and components, e.g., a vehicle 101 velocity, a vehicle 101 trajectory, etc.
[0032] The computing device 105 is generally programmed for communications on a vehicle 101 network, e.g., including a communications bus, as is known. Via the network, bus, and/or other wired or wireless mechanisms (e.g., a wired or wireless local area network in the vehicle 101), the computing device 105 may transmit messages to various devices in a vehicle 101 and/or receive messages from the various devices, e.g., controllers, actuators, sensors, etc., including sensors 110. Alternatively or additionally, in cases where the computing device 105 actually comprises multiple devices, the vehicle network 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 125, which, as described below, may include various wired and/or wireless networking technologies, e.g., cellular, Bluetooth®, Bluetooth® Low Energy (BLE), wired and/or wireless packet networks, etc.
[0033] 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 may store the collected data 115 sent from the sensors 110.
[0034] Sensors 110 may include a variety of devices. For example, as is known, various controllers in a vehicle 101 may operate as sensors 110 to provide data 115 via the vehicle 101 network or bus, e.g., data 115 relating to vehicle speed, acceleration, position, subsystem and/or component status, etc. Further, other sensors 110 could include cameras, motion detectors, etc., i.e., sensors 110 to provide data 115 for evaluating a location of a target, projecting a path of a target, evaluating a location of a roadway lane, etc. The sensors 110 could also include short range radar, long range radar, LIDAR, and/or ultrasonic transducers.
[0035] 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 are generally collected using one or more sensors 110, and may additionally include data calculated therefrom in the computing device 105, and/or at the server 130. In general, collected data 115 may include any data that may be gathered by the sensors 110 and/or computed from such data. [0036] The vehicle 101 may include a plurality of vehicle components 120. As used herein, each vehicle component 120 includes one or more hardware components adapted to perform a mechanical function or operation—such as moving the vehicle, slowing or stopping the vehicle, steering the vehicle, etc. Non-limiting examples of components 120 include a propulsion component (that includes, e.g., an internal combustion engine and/or an electric motor, etc.), a transmission component, a steering component (e.g., that may include one or more of a steering wheel, a steering rack, etc.), a brake component, a park assist component, an adaptive cruise control component, an adaptive steering component, and the like.
[0037] The computing device 105 may actuate the components 120 to, e.g., brake and/or slow and/or stop the vehicle 101, to avoid targets, etc. The computing device 105 may be programmed to operate some or all of the components 120 with limited or no input from a human operator, i.e., the computing device 105 may be programmed to operate the components 120. When the computing device 105 operates the components 120, the computing device 105 can ignore input from the human operator with respect to components 120 selected for control by the computing device 105, which provides instructions, e.g., via a vehicle 101 communications bus and/or to electronic control units (ECUs) as are known, to actuate vehicle 101 components, e.g., to apply brakes, change a steering wheel angle, etc. For example, if the human operator attempts to turn a steering wheel during steering operation, the computing device 105 may ignore the movement of the steering wheel and steer the vehicle 101 according to its programming.
[0038] When the computing device 105 operates the vehicle 101, the vehicle 101 is an “autonomous” vehicle 101. For purposes of this disclosure, the term “autonomous vehicle” is used to refer to a vehicle 101 operating in a fully autonomous mode. A fully autonomous mode is defined as one in which each of vehicle 101 propulsion (typically via a powertrain including an electric motor and/or internal combustion engine), braking, and steering are controlled by the computing device 105 and not a human operator. A semi-autonomous mode is one in which at least one of vehicle 101 propulsion (typically via a powertrain including an electric motor and/or internal combustion engine), braking, and steering are controlled at least partly by the computing device 105 as opposed to a human operator.
[0039] The system 100 may further include a network 125 connected to a server 130 and a data store 135. The computer 105 may further be programmed to communicate with one or more remote sites such as the server 130, via the network 125, such remote site possibly including a data store 135. The network 125 represents one or more mechanisms by which a vehicle computer 105 may communicate with a remote server 130. Accordingly, the network 125 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®, BLE, IEEE 802.11, vehicle-to-vehicle (V2V) such as Dedicated Short Range Communications (DSRC), etc.), local area networks (LAN) and/or wide area networks (WAN), including the Internet, providing data communication services.
[0040] Figure 2 illustrates an example intersection between a host vehicle 101 and a plurality of targets 200. The example of Figure 2 includes two targets 200a, 200b. The host vehicle 101 is moving in a roadway lane and is about to turn across adjacent roadway lanes. The computing device 105 can use data 115 from the sensors 110 to identify the targets 200a, 200b as potentially colliding with the host vehicle 101.
[0041] The target 200a is moving longitudinally toward the host vehicle 101, i.e., the target 200a is a “longitudinally oncoming” or “oncoming” target 200. Thus, the host vehicle 101 may collide with the target 200a when the host vehicle 101 moves in a turn across the roadway lane of the target 200a. That is, the host vehicle 101 crosses a path of the target 200a. This scenario when the host vehicle 101 is crossing the path of the oncoming target 200a is an “OnComing Turn Across Path” (OCTAP) scenario. The computing device 105 can identify targets 200 such as the target 200a as OCTAP targets 200, as described below.
[0042] The target 200b is moving laterally toward the host vehicle 101, i.e., the target 200b is a “laterally moving” target 200. Thus, the host vehicle 101 may collide with the target 200b when the host vehicle 101 moves straight in the current roadway lane and a path of the target 200b crosses the path of the host vehicle 101. This scenario is a “Straight Crossing Path” (SCP) scenario. The computing device 105 can identify targets 200 such as the target 200b as SCP targets, as described below.
[0043] Figure 3 illustrates example measurements of the target 200 measured by the host vehicle 101. The computing device 105 can define a vehicle coordinate system (VCS) with an origin O at a center of a front end of the host vehicle 101. The VCS defines rectangular coordinates that are specified according to orthogonal directions: a lateral direction designated with the variable y, and a longitudinal direction, designated with the variable x. The computing device 105 can predict the position, speed, and acceleration of the host vehicle 101 and the target 200 in both the lateral and longitudinal directions. The computing device 105 can determine the position, speed, and acceleration relative to the ground, defined as “Over-TheGround” (OTG) values.
[0044] The OTG heading angle Θ is the direction of travel of the target 200 relative to the longitudinal axis. The heading angle Θ can be defined in terms of the target 200 lateral velocity Vty and the target 200 longitudinal velocity Vtx:
Θ = atan
(1) [0045] The computing device 105 can actuate the sensors 110 to collect data 115 to determine a longitudinal distance xt between the host vehicle 101 and the target 200. The computing device 105 can use the distance xt to determine a likelihood of the target 200 colliding with the host vehicle 101.
[0046] Figure 4 illustrates other measurements that the computing device 105 can take of the target 200. The computing device 105 can determine the OTG target 200 velocity Vt :
ft = rt + K + fixf | (2) |
V = Vxi + Vyj | (3) |
vt = Vtxi + VtyJ | (4) |
where vt is the target 200 velocity relative to the host vehicle 101, V is the OTG host vehicle 101 velocity vector, Ω is a host vehicle 101 turn rate vector (i.e., a yaw rate vector), r is a target 200 position vector relative to the host vehicle 101, vtx, vty are the components of the relative target 200 velocity in the longitudinal and the lateral directions, Vx, Vy are the components of the OTG host vehicle 101 velocity vector, and i,j are unit vectors in the longitudinal and lateral directions, respectively.
[0047] Figure 5 illustrates an example OCTAP scenario. The example of Figure 5 includes the host vehicle 101 and two oncoming targets 200a, 200b. The computing device 105 can determine whether one or both of the targets 200a, 200b should be selected as OCTAP targets 200. The computing device 105 can use predetermined heading angle thresholds θχ, θ2 to determine a first angle range 180 ± θ± and a second angle range ([180 + 01( 180 + 02], [180 — 01( 180 — 02]) · The first and second angle ranges can be used to determine whether the targets 200a, 200b could potentially collide with the host vehicle 101. The computing device 105 can also determine a longitudinal distance xt for each of the targets 200a, 200b and compare the longitudinal distance xt to a first distance threshold xr. Example values include = 30°, θ2 = 60°, x± = 15 meters.
[0048] The computing device 105 can define three types of OCTAP targets 200. A type I OCTAP target 200 is a target 200 with a heading angle Θ in the first angle range and the longitudinal distance xt greater than the first distance threshold A type II OCTAP target 200 is a target 200 with a heading angle Θ within the second angle range, the longitudinal distance xt is greater than the first distance threshold xl5 and the target 200 was previously determined to have a confidence level of 3 or more, as described below. A type III OCTAP target 200 is a target 200 having a previously determined confidence level of 3 and a longitudinal distance xt less than the first distance threshold xx.
[0049] Figure 6 illustrates an example SCP scenario. The example of Figure 6 includes the host vehicle 101 and two laterally moving targets 200a, 200b. The computing device 105 can determine whether one or both of the targets 200a, 200b should be selected as SCP targets 200. The computing device 105 can use predetermined heading angle thresholds 03,04 to determine a third angle range [90 ± θ3, 270 ± 03] and a fourth angle range ([90 + 03,9O + 04], [90 — 03,9O — 04], [270 + 03,27O + 04], [270 — 03,27O — 04]) . Because the laterally moving targets 200a, 200b can be moving in opposite directions in the lateral direction, the third and fourth angle ranges include offsets of both 90 and 270 degrees. The third and fourth angle ranges can be used to determine whether the targets 200a, 200b could potentially collide with the host vehicle 101. The computing device 105 can also determine a longitudinal distance xt for each of the targets 200a, 200b and compare the longitudinal distance xt to a second distance threshold x2. Example values include 03 = 30°, 04 = 60°, x2 = 15 meters.
[0050] The computing device 105 can define three types of SCP targets 200. A type I SCP target 200 is a target 200 with a heading angle Θ in the third angle range and the longitudinal distance xt greater than the second distance threshold x2. A type II SCP target 200 is a target 200 with a heading angle Θ within the fourth angle range, the longitudinal distance xt is greater than the first distance threshold x2, and the target 200 was previously determined to have a confidence level of 3 or more, as described below. A type III SCP target 200 is a target 200 having a previously determined confidence level of 3 and a longitudinal distance xt less than the second distance threshold x2.
[0051] The computing device 105 can determine that the target 200 is no longer an SCP target 200 based on the heading angle Θ. When the target 200 is approaching the host vehicle
101, the heading angle Θ is typically either about 90° or 270° depending on whether the target 200 is moving to the left or to the right in the longitudinal direction. When the target 200 crosses the path of the host vehicle 101, the heading angle Θ shifts by 180 degrees, such that a target 200 that had a heading angle Θ of 90 degrees prior to crossing the path of the host vehicle 101 will have a heading angle Θ of 270 degrees after crossing the path of the host vehicle 101. Similarly, if the target 200 has a heading angle Θ of 270 prior to crossing the path of the host vehicle 101, the target 200 will have a heading angle Θ of 450 degrees, which is equivalent to a heading angle of 90 degrees. Thus, when the host vehicle 101 determines that the heading angle Θ of the target 200 has shifted by 180 degrees, i.e., the target 200 has crossed the path of the host vehicle 101, the target 200 has a much lower probability of colliding with the host vehicle 101 and the target 200 can be identified as not being an SCP target 200 and/or not requiring a threat assessment.
[0052] The computing device 105 can select OCTAP and SCP targets 200 up to a maximum number N. By filtering the selection of targets 200 to the maximum number N, the computing device 105 can reduce the total number of threat assessments calculated. The targets 200 selected are the OCTAP and SCP targets 200 that are closest to the host vehicle 101, i.e., the targets 200 with a longitudinal distance xt smaller than other targets 200.
[0053] The computing device 105 can determine a confidence level for each of the targets 200. The confidence level is based on the heading angle Θ of the target 200 and the distance xt of the target 200 from the host vehicle 101. The computing device 105 can use the confidence level to determine whether to perform a threat assessment on the target 200. The confidence level may be a value between 0 and 4, where 0 indicates a low likelihood of a collision and 4 indicates a high likelihood of a collision. The computing device 105 can determine the confidence level for the target 200 in succession more than one time, and based on previous determinations of the confidence level, the computing device 105 can change the current confidence level from a previously determined confidence level. That is, the computing device 105 can repeat the process (such as the process 1100 described below) to determine the confidence level to produce another value for the confidence level for the target 200. Each repeat of the process is one “time” repeating the process and the computing device 105 determines another value of the confidence level each “time” the process repeats. For example, the computing device 105 can determine the confidence level for different numbers of times ni,n2,n3.
[0054] The numbers can be predetermined, e.g., by a server 130, and based on a predicted number of times that the computing device 105 can determine the confidence level before reaching the target 200. For example, the number of times can relate to a convergence of a sensing tracking motion prediction algorithm. One of the sensors 110, e.g., a radar, a camera, etc., can directly measure a current position, speed, and acceleration of the target 200. The computing device 105 can then use the motion prediction algorithm to estimate where the target 200 will be the next time the process is performed and the next measurement of the target 200 position, speed, and acceleration. The three numbers n1,n2,n3 can be used by the computing device 105 to determine the confidence level between 0 and 4, as described below. By determining the confidence level a plurality of times, e.g., times, the computing device 105 can more precisely determine the likelihood of a collision between the target 200 and the host vehicle 101. The numbers n1( n2n3 can be, e.g., integer values between 3 and 10. [0055] For example, the computing device 105 can assign the confidence level for the target 200 to a value of 0, 1, 2, 3, or 4. A confidence level of 0 can be assigned when the computing device 105 determines that the target 200 is not an OCTAP or SCP target 200 or is a type II OCTAP or SCP target 200 at least n3 consecutive times. A confidence level of 1 can be assigned when the computing device 105 determines that the target 200 is a type I OCTAP or SCP target 200 between 1 and — 1 consecutive times. A confidence level of 2 can be assigned when the computing device 105 determines that the target 200 is a type I OCTAP or SCP target 200 between rt^ and n2 — 1 consecutive times. A confidence level of 3 can be assigned when the computing device 105 determines that the target 200 is a type I OCTAP or SCP target 200 more than n2 consecutive times or the target 200 is a type III OCTAP or SCP target 200. A confidence level of 4 can be assigned when the computing device 105 determines that the target 200 is a type II OCTAP or SCP target 200 between 1 and n3 — 1 consecutive times.
[0056] The computing device 105 can perform the threat assessment on the selected targets 200 and generate a threat number for each of the targets 200. A threat number is a prediction of whether a specific target 200 will intersect or collide with the host vehicle 101. Specifically, the computing device 105 may determine the acceleration threat number ATN, the brake threat number BTN, and the steering threat number STN for the host vehicle 101 and the target 200, and based on the threat numbers ATN, BTN, STN, which may be combined into a single threat number TN, actuate components 120.
[0057] The BTN is a measure of a change in longitudinal acceleration to allow one of the host vehicle 101 to stop or the target 200 to pass the host vehicle 101. The STN is a measure of a change in lateral acceleration to allow one of the host vehicle 101 and the target 200 to clear a crossing zone and/or to steer the host vehicle 101 around a front end or a rear end of the target 200. The ATN is a measure of a specific longitudinal acceleration to allow one of the host vehicle 101 and the target 200 to pass the other of the host vehicle 101 and the target 200. That is, the BTN is a measure of longitudinal acceleration of the host vehicle 101, and may be determined with data 115 from the sensors 110. The STN is a measure of lateral, longitudinal, and/or rotational acceleration of the host vehicle 101. For example, the STN can be based on a steering path curvature, a yaw rate, and/or a steering wheel angle of the host vehicle 101. The ATN is a measure of throttle changes. The computing device 105 may determine the STN, BTN, and/or ATN to for each of the targets 200 to produce the threat number.
[0058] The computing device 105 can actuate one or more vehicle components 120 based on the threat number. For example, if the threat number is above 0.7, the computing device 105 can actuate a brake 120 to decelerate the host vehicle 101, e.g., to -6.5 meters per second squared (m/s2). In another example, if the threat number is above 0.4 but less than or equal to 0.7, the computing device 105 can pre-charge the brake 120 to enable the brake 120 to operate more quickly if the threat number rises above 0.7. For example, if the brake 120 is a hydraulic brake 120, the computing device 105 can increase a hydraulic pressure in the hydraulic brake 120. In another example, if the threat number is greater than 0.2 but less than or equal to 0.4, the computing device 105 can display a visual warning on a vehicle 101 HMI and/or play an audio warning over a speaker.
[0059] Figure 7 is a block diagram of an example process 700 for mitigating a collision. The process 700 starts in a block 705, in which the computing device 105 identifies a plurality of potential targets 200. The computing device 105 can actuate sensors 110 to collect data 115 about targets 200 that have a potential to collide with the host vehicle 101.
[0060] Next, in a block 710, the computing device 105 identifies the targets 200, if any, that are in an OCTAP scenario. As described above, targets 200 that are moving toward the host vehicle 101 in the longitudinal direction, i.e., oncoming targets 200, can be identified as OCTAP targets 200.
[0061] Next, in a block 715, the computing device 105 identifies the targets 200, if any, that are in a SCP scenario. As described above, laterally moving targets 200 can be identified as SCP targets 200.
[0062] Next, in a block 720, the computing device 105 filters the targets 200 to the predetermined maximum number N. As described above, performing a threat assessment on each identified target 200 can be computationally costly, so the computing device 105 can select a predetermined maximum number N of targets 200 on which to perform the threat assessment. The computing device 105 filters the total number of target 200 to the maximum number N.
[0063] Next, in a block 725, the computing device 105 determines a confidence level for each of the selected targets 200. As described above, the confidence level can be used to determine the likelihood of a collision between the host vehicle 101 and the target 200.
[0064] Next, in a block 730, the computing device 105 performs a threat assessment for each of the selected targets 200. As described above, the threat assessment can result in a threat number indicating a likelihood of a collision.
[0065] Next, in a block 735, the computing device 105 actuates a host vehicle component 120 based on the threat assessment. Tor example, if the threat number is between 0.2 and 1, the computing device 105 can actuate a warning, e.g., an audio alert, a visual alert, a message to a user portable device, etc. If the threat number is between 0.2 and 0.7, the computing device 105 can pre-charge a brake 120, as described above. The computing device 105 can further actuate an Emergency Brake Assist (EBA) that actuates an antilock brake system (ABS) prior to full actuation of the brake 120 by the user. The computing device 105 can further actuate a dynamic brake 120 support, which increases a brake 120 power based on the threat number. Furthermore, if the host vehicle 101 is in an autonomous or semi-autonomous mode, the computing device 105 can actuate the brake 120 without input from the user. Following the block 735, the process 700 ends.
[0066] Next, in a block 740, the computing device 105 determines whether to continue the process 700. The computing device 105 can determine to continue the process 700 if the host vehicle 101 is still driving along the roadway. If the computing device 105 determines to continue the process 700, the process 700 returns to the block 705 to identify more targets 200. [0067] Figure 8 illustrates an example process 800 for classifying a target 200 in an OCTAP scenario. The process 800 begins in a block 805, in which the computing device 105 identifies an oncoming target 200. As described above, an oncoming target 200 is a target 200 moving toward the host vehicle 101 in the longitudinal direction.
[0068] Next, in a block 810, the computing device 105 determines the distance xt and the heading angle Θ for the target 200. The computing device 105 can use data 115 from the sensors 110 to determine the distance xt and the heading angle 0, as described above.
[0069] Next, in a block 815, the computing device 105 determines whether the distance xt is above a first threshold If the distance xt is above the first threshold, the process 800 continues in a block 835. Otherwise, the process 800 proceeds to the block 820.
[0070] In the block 820, the computing device 105 determines whether the target 200 was previously determined to have a confidence level above a threshold. For example, the threshold can be 3. As described above, the computing device 105 can determine the confidence level for the target 200 a plurality of times, and the computing device 105 examines whether the most recent determination of the confidence level is above the threshold. If the most recent determination of the confidence level for the target 200 was above the threshold, the process 800 continues in a block 830. Otherwise, the process 800 continues in a block 825.
[0071] In the block 825, the computing device 105 determines that the target 200 is not an OCTAP target 200. The process 800 then continues in a block 855.
[0072] In the block 830, the computing device 105 determines that the target 200 is an OCTAP Type III target 200. The process 800 then continues in the block 855.
[0073] In the block 835, the computing device 105 determines whether the heading angle Θ is within a first angle range. The first angle range, as described above, can be used to determine the type of OCTAP target 200. If the heading angle Θ is within the first angle range, the process 800 continues in a block 840. Otherwise, the process 800 continues in a block 845. [0074] In the block 840, the computing device 105 determines that the target 200 is an OCTAP Type I target 200. The process 800 continues in the block 855.
[0075] In the block 845, the computing device 105 determines whether the heading angle Θ is within a second angle range and the most recently determined confidence level for the target 200 is 3 or more. If the heading angle Θ is within the second angle range, the process 800 continues in a block 850. Otherwise, the process 800 continues in the block 825.
[0076] In the block 850, the computing device 105 determines that the target 200 is an OCTAP Type II target 200. The process 800 continues in the block 855.
[0077] In the block 855, the computing device 105 determines whether to continue the process 800. Based on continued determinations of the confidence level and the distance xt of the target 200, the type of OCTAP target 200 can change as the host vehicle 101 moves toward the target 200. If the computing device 105 determines to continue, the process 800 returns to the block 805 to identify another oncoming target 200. Otherwise, the process 800 ends. [0078] Figure 9 illustrates an example process 900 for classifying a target 200 in an SCP scenario. The process 900 begins in a block 905, in which the computing device 105 identifies a laterally moving target 200. As described above, a laterally moving target 200 is a target 200 moving toward the host vehicle 101 in the lateral direction.
[0079] Next, in a block 910, the computing device 105 determines the distance xt and the heading angle Θ for the target 200. The computing device 105 can use data 115 from the sensors 110 to determine the distance xt and the heading angle 0, as described above.
[0080] Next, in a block 915, the computing device 105 determines whether the distance is above a second threshold x2. If the distance xt is above the second threshold, the process 900 continues in a block 935. Otherwise, the process 900 proceeds to the block 920.
[0081] In the block 920, the computing device 105 determines whether the target 200 was previously determined to have a confidence level above a threshold. For example, the threshold can be 3. As described above, the computing device 105 can determine the confidence level for the target 200 a plurality of times, and the computing device 105 examines whether the most recent determination of the confidence level is above the threshold. If the most recent determination of the confidence level for the target 200 was above the threshold, the process 900 continues in a block 930. Otherwise, the process 900 continues in a block 925.
[0082] In the block 925, the computing device 105 determines that the target 200 is not an SCP target 200. The process 900 then continues in a block 955.
[0083] In the block 930, the computing device 105 determines that the target 200 is an SCP Type III target 200. The process 900 then continues in the block 955.
[0084] In the block 935, the computing device 105 determines whether the heading angle Θ is within a third angle range, as described above. The third angle range, as described above, can be used to determine the type of SCP target 200. If the heading angle Θ is within the third angle range, the process 900 continues in a block 940. Otherwise, the process 900 continues in a block 945.
[0085] In the block 940, the computing device 105 determines that the target 200 is an SCP Type I target 200. The process 900 continues in the block 955.
[0086] In the block 945, the computing device 105 determines whether the heading angle Θ is within a fourth angle range, as described above, and the most recently determined confidence level for the target 200 is 3 or more. If the heading angle Θ is within the fourth angle range and the most recently determined confidence level for the target 200 is 3 or more, the process 900 continues in a block 950. Otherwise, the process 900 continues in the block 925. [0087] In the block 950, the computing device 105 determines that the target 200 is an SCP Type II target 200. The process 900 continues in the block 955.
[0088] In the block 955, the computing device 105 determines whether to continue the process 900. Based on continued determinations of the confidence level and the distance xt of the target 200, the type of SCP target 200 can change as the host vehicle 101 moves toward the target 200. If the computing device 105 determines to continue, the process 900 returns to the block 905 to identify another laterally moving target 200. Otherwise, the process 900 ends. [0089] Figure 10 is a block diagram of an example process 1000 for filtering the targets 200. The process 1000 begins in a block 1005, in which the computing device 105 identifies one of the targets 200.
[0090] Next, in a block 1010, the computing device 105 determines whether the total number of targets 200 selected exceeds the maximum number N of targets 200. The computing device 105 can perform the threat assessment for a limited number of targets 200, and the computing device 105 may have already selected N targets to perform the threat assessment. If the total number of targets 200 selected exceeds the maximum number N, the process 1000 continues in a block 1015. Otherwise, the process 1000 continues in a block 1030.
[0091] In the block 1015, the computing device 105 determines whether the target 200 is closer to the host vehicle 101 than one of the previously selected targets 200. That is, the computing device 105 compares the distance xt of the current target 200 to the distances xt for each of the previously selected targets 200, if any. If the distance xt of the current target 200 is smaller than the distance xt of one of the other selected targets 200, the current target 200 is closer to the host vehicle 101 than that one selected target 200. If the target 200 is closer to the host vehicle 101 than one of the selected targets 200, the process 1000 continues in a block 1025. Otherwise, the process 1000 continues in a block 1020.
[0092] In the block 1020, the computing device 105 determines not to select the target 200. That is, the target 200 is not chosen for selection and future threat assessment. The process 1000 continues in a block 1035.
[0093] In the block 1025, the computing device 105 deletes the OCTAP or SCP target 200 that is farthest from the host vehicle 101. The computing device 105 compares the distances xt for all selected targets 200 and removes the target 200 having the highest distance xt. Thus, the computing device 105 filters from all of the targets 200 to a smaller subset of targets 200.
[0094] In the block 1030, the computing device 105 adds the target 200 to the list of selected targets 200. The computing device 105 can use the list to determine which targets 200 to perform the threat assessment.
[0095] In the block 1035, the computing device 105 determines whether to continue the process 1000. The computing device 105 can determine to continue the process based on, e.g., detecting more targets 200 that may be added to the list. If the computing device 105 determines to continue, the process 1000 returns to the block 1005 to identify another target 200. Otherwise, the process 1000 ends.
[0096] Figure 11 is a block diagram of an example process 1100 for determining the confidence level for a target 200. The process 1100 begins in a block 1105, in which the computing device 105 identifies the target 200.
[0097] Next, in a block 1110, the computing device 105 determines whether the target 200 is one of an OCTAP target 200 or a SCP target 200. The computing device 105 can determine whether the target 200, based on the processes such as the example processes 800 and 900 above, is selected as an OCTAP target 200 or a SCP target 200. If the target 200 is an OCTAP target 200 or a SCP target 200, the process 1100 continues in a block 1140. Otherwise, the process 1100 continues in a block 1115.
[0098] In the block 1115, the computing device 105 increases a confidence counter value by 1. The confidence counter value can be used to determine the confidence level of the target 200.
[0099] Next, in a block 1120, the computing device 105 determines whether the confidence counter value is below a first threshold. The confidence counter is a measure of a number of times that the computing device 105 has determined a confidence threshold for the target 200. The first threshold can be a predetermined number, such as described above. If the confidence counter value is below the first threshold, the process 1100 continues in a block 1130. Otherwise, the process 1100 continues in a block 1125.
[0100] In the block 1125, the computing device 105 determines whether the confidence counter value is between the first threshold, e.g., nl5 and a second threshold. The second threshold can be a predetermined number, such as n2 described above. If the confidence counter value is between the first threshold and the second threshold, the process 1100 continues in a block 1135. Otherwise, the process 1100 continues in a block 1170.
[0101] In the block 1130, the computing device 105 assigns the target 200 with a confidence level of 1, and the process 1100 ends.
[0102] In the block 1135, the computing device 105 assigns the target 200 with a confidence level of 2, and the process 1100 ends.
[0103] In the block 1140, the computing device 105 determines whether the target 200 is one of a Type I OCTAP target 200 and a Type I SCP target 200. If the target 200 is a Type I OCTAP target 200 or a Type I SCP target 200, the process 1100 continues in the block 1115. Otherwise, the process 1100 continues in a block 1145.
[0104] In the block 1145, the computing device 105 determines whether the target 200 is one of a Type II OCTAP target 200 and a Type II SCP target 200. If the target 200 is a Type II OCTAP target 200 or a Type II SCP target 200, the process 1100 continues in a block 1150. Otherwise, the process 1100 continues in the block 1170.
[0105] In the block 1150, the computing device 105 increases a holding counter value by
1. The holding counter is a measure of the number of times that the computing device 105 has determined the confidence value for the target 200, and can be used to determine the confidence level of the target 200.
[0106] Next, in a block 1155, the computing device 105 determines whether the holding counter value is below a holding counter value threshold. The holding counter value threshold can be a predetermined number, such as n3 as described above. If the holding counter value is below the holding counter value threshold, the process 1100 continues in a block 1165. Otherwise, the process 1100 continues in a block 1160.
[0107] In the block 1160, the computing device 105 assigns the target 200 with a confidence level of 0, and the process 1100 ends.
[0108] In the block 1165, the computing device 105 assigns the target 200 with a confidence level of 4 and resets the confidence counter value to the second level n2. Following the process 1170, the process 1100 ends.
[0109] In the block 1170, the computing device 105 assigns the target 200 with a confidence value of 3, resets the confidence countervalue to the second level n2, and resets the holding counter value to 0. Following the block 1170, the process 1100 ends.
[0110] 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, data collector measurements, computations, processing time, communications time, etc.
[0111] 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.
[0112] 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.
[0113] 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 700, one or more of the steps could be omitted, or the steps could be executed in a different order than shown in Figure 7. 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.
[0114] 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.
[0115] The article “a” modifying a noun should be understood as meaning one or more unless stated otherwise, or context requires otherwise. The phrase “based on” encompasses being partly or entirely based on.
Claims (15)
1. A method, comprising:
determining a respective confidence level of a potential collision for each of a plurality of targets based on each target’s heading angle and distance from a host vehicle;
determining a threat number for each target when its respective confidence level is above a threshold; and actuating a vehicle component based on the threat number.
2. The method of claim 1, further comprising determining whether each of the targets is one of a laterally moving target and a longitudinally oncoming target.
3. The method of claim 1, further comprising determining whether the target heading angle is within a first heading angle range.
4. The method of claim 1, further comprising determining, for one of the targets, whether the target heading angle is within a second heading angle range and the target was previously determined to have a confidence level above the threshold.
5. The method of claim 1, further comprising determining whether the distance is below a distance threshold.
6. The method of claim 1, further comprising selecting a predetermined maximum number of targets based on the distance.
7. The method of claim 6, further comprising removing a farthest target from the selected targets upon identifying a closer target.
8. The method of claim 6, further comprising increasing a confidence counter for one of the targets when the target was previously one of the selected targets.
9.
The method of claim 8, further comprising increasing the confidence level for one of the targets based on the confidence counter of the target.
10. The method of claim 1, further comprising determining the confidence level based on a previously determined confidence level.
11. The method of any of claims 3-10, further comprising determining whether each of the targets is one of a laterally moving target and a longitudinally oncoming target.
12. The method of any of claims 2-5 and 10, further comprising selecting a predetermined maximum number of targets based on the distance.
13. A computer programmed to perform the method of any of claims 1-10.
14. A vehicle comprising the computer of claim 13.
15. A computer program product comprising a computer-readable medium storing instructions executable by a computer processor to execute the method of any of claims 1-10.
Intellectual
Property
Office
Application No: Claims searched:
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201762446153P | 2017-01-13 | 2017-01-13 | |
US15/498,078 US10351129B2 (en) | 2017-01-13 | 2017-04-26 | Collision mitigation and avoidance |
Publications (2)
Publication Number | Publication Date |
---|---|
GB201800316D0 GB201800316D0 (en) | 2018-02-21 |
GB2560096A true GB2560096A (en) | 2018-08-29 |
Family
ID=61190374
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
GB1800316.0A Withdrawn GB2560096A (en) | 2017-01-13 | 2018-01-09 | Collision mitigation and avoidance |
Country Status (2)
Country | Link |
---|---|
DE (1) | DE102018100583A1 (en) |
GB (1) | GB2560096A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022042853A1 (en) * | 2020-08-28 | 2022-03-03 | Siemens Industry Software Netherlands B.V. | Critical scenario identification for verification and validation of vehicles |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112440986B (en) * | 2020-11-30 | 2022-08-09 | 重庆长安汽车股份有限公司 | Driving control method, pedestrian AEB system, intelligent driving automobile, controller and computer readable storage medium |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090045928A1 (en) * | 2007-08-16 | 2009-02-19 | Rao Manoharprasad K | System and method for combined blind spot detection and rear crossing path collision warning |
US20090192710A1 (en) * | 2008-01-29 | 2009-07-30 | Ford Global Technologies, Llc | Method and system for collision course prediction and collision avoidance and mitigation |
JP2012014257A (en) * | 2010-06-29 | 2012-01-19 | Toyota Motor Corp | Alarm device |
US20140297171A1 (en) * | 2013-03-29 | 2014-10-02 | Nippon Soken, Inc. | Vehicle-installation intersection judgment apparatus and program |
US20160052515A1 (en) * | 2014-08-21 | 2016-02-25 | Hyundai Motor Company | Method and apparatus of predicting collision for omnidirectional application within emergency brake system |
US20160109571A1 (en) * | 2013-05-23 | 2016-04-21 | GM Global Technology Operations LLC | System and method for providing target threat assessment in a collision avoidance system on a vehicle |
EP3249630A2 (en) * | 2016-05-25 | 2017-11-29 | Panasonic Intellectual Property Management Co., Ltd. | Object detection apparatus, and storage medium |
-
2018
- 2018-01-09 GB GB1800316.0A patent/GB2560096A/en not_active Withdrawn
- 2018-01-11 DE DE102018100583.0A patent/DE102018100583A1/en active Pending
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090045928A1 (en) * | 2007-08-16 | 2009-02-19 | Rao Manoharprasad K | System and method for combined blind spot detection and rear crossing path collision warning |
US20090192710A1 (en) * | 2008-01-29 | 2009-07-30 | Ford Global Technologies, Llc | Method and system for collision course prediction and collision avoidance and mitigation |
JP2012014257A (en) * | 2010-06-29 | 2012-01-19 | Toyota Motor Corp | Alarm device |
US20140297171A1 (en) * | 2013-03-29 | 2014-10-02 | Nippon Soken, Inc. | Vehicle-installation intersection judgment apparatus and program |
US20160109571A1 (en) * | 2013-05-23 | 2016-04-21 | GM Global Technology Operations LLC | System and method for providing target threat assessment in a collision avoidance system on a vehicle |
US20160052515A1 (en) * | 2014-08-21 | 2016-02-25 | Hyundai Motor Company | Method and apparatus of predicting collision for omnidirectional application within emergency brake system |
EP3249630A2 (en) * | 2016-05-25 | 2017-11-29 | Panasonic Intellectual Property Management Co., Ltd. | Object detection apparatus, and storage medium |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022042853A1 (en) * | 2020-08-28 | 2022-03-03 | Siemens Industry Software Netherlands B.V. | Critical scenario identification for verification and validation of vehicles |
Also Published As
Publication number | Publication date |
---|---|
GB201800316D0 (en) | 2018-02-21 |
DE102018100583A1 (en) | 2018-07-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10403145B2 (en) | Collison mitigation and avoidance | |
US10232849B2 (en) | Collision mitigation and avoidance | |
US10351129B2 (en) | Collision mitigation and avoidance | |
US10266175B2 (en) | Vehicle collision avoidance | |
US10446033B2 (en) | Vehicle detection and avoidance | |
US11400927B2 (en) | Collision avoidance and mitigation | |
US11518381B2 (en) | Enhanced threat selection | |
US10967853B2 (en) | Enhanced collision mitigation | |
US10160459B2 (en) | Vehicle lane direction detection | |
US11285942B2 (en) | Collision mitigation and avoidance | |
US11884252B2 (en) | Enhanced threat assessment | |
US11383705B2 (en) | Enhanced collision avoidance | |
US20210256321A1 (en) | Enhanced object detection with clustering | |
US11273806B2 (en) | Enhanced collision mitigation | |
GB2560096A (en) | Collision mitigation and avoidance | |
US11148663B2 (en) | Enhanced collision mitigation | |
US11267465B1 (en) | Enhanced threat assessment | |
US20220396246A1 (en) | Enhanced vehicle operation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |