US20180210463A1 - System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles - Google Patents
System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles Download PDFInfo
- Publication number
- US20180210463A1 US20180210463A1 US15/926,809 US201815926809A US2018210463A1 US 20180210463 A1 US20180210463 A1 US 20180210463A1 US 201815926809 A US201815926809 A US 201815926809A US 2018210463 A1 US2018210463 A1 US 2018210463A1
- Authority
- US
- United States
- Prior art keywords
- vehicle
- platoon
- controller
- braking
- control
- 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.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title abstract description 11
- 230000000116 mitigating effect Effects 0.000 title abstract description 11
- 230000019771 cognition Effects 0.000 title 1
- 230000009471 action Effects 0.000 claims abstract description 80
- 238000001514 detection method Methods 0.000 claims description 8
- 230000005540 biological transmission Effects 0.000 claims description 6
- 238000002360 preparation method Methods 0.000 claims description 5
- 230000001133 acceleration Effects 0.000 claims description 3
- 231100001261 hazardous Toxicity 0.000 claims description 3
- 238000012544 monitoring process Methods 0.000 claims description 3
- 238000003384 imaging method Methods 0.000 claims description 2
- 238000001556 precipitation Methods 0.000 claims description 2
- 230000000979 retarding effect Effects 0.000 claims description 2
- 230000000007 visual effect Effects 0.000 claims description 2
- 238000012802 pre-warming Methods 0.000 claims 1
- 238000004891 communication Methods 0.000 description 39
- 238000010586 diagram Methods 0.000 description 16
- 238000005259 measurement Methods 0.000 description 14
- 230000004044 response Effects 0.000 description 14
- 230000000977 initiatory effect Effects 0.000 description 8
- 230000008859 change Effects 0.000 description 7
- 239000000446 fuel Substances 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 238000013349 risk mitigation Methods 0.000 description 7
- 238000013459 approach Methods 0.000 description 6
- 230000001149 cognitive effect Effects 0.000 description 5
- 238000002485 combustion reaction Methods 0.000 description 5
- 230000036541 health Effects 0.000 description 5
- 238000010801 machine learning Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000009467 reduction Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000007704 transition Effects 0.000 description 3
- 230000003044 adaptive effect Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 230000003292 diminished effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000000246 remedial effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000009118 appropriate response Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012517 data analytics Methods 0.000 description 1
- 238000013496 data integrity verification Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000004090 dissolution Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013021 overheating Methods 0.000 description 1
- 238000003909 pattern recognition Methods 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000005086 pumping Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 238000002604 ultrasonography Methods 0.000 description 1
- 238000004804 winding Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/02—Control of position or course in two dimensions
- G05D1/021—Control of position or course in two dimensions specially adapted to land vehicles
- G05D1/0287—Control of position or course in two dimensions specially adapted to land vehicles involving a plurality of land vehicles, e.g. fleet or convoy travelling
- G05D1/0291—Fleet control
- G05D1/0293—Convoy travelling
-
- 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
- B60W10/00—Conjoint control of vehicle sub-units of different type or different function
- B60W10/04—Conjoint control of vehicle sub-units of different type or different function including control of propulsion units
-
- 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
- B60W10/00—Conjoint control of vehicle sub-units of different type or different function
- B60W10/18—Conjoint control of vehicle sub-units of different type or different function including control of braking systems
-
- 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
- B60W10/00—Conjoint control of vehicle sub-units of different type or different function
- B60W10/20—Conjoint control of vehicle sub-units of different type or different function including control of steering systems
-
- 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/14—Adaptive cruise control
- B60W30/16—Control of distance between vehicles, e.g. keeping a distance to preceding vehicle
- B60W30/165—Automatically following the path of a preceding lead vehicle, e.g. "electronic tow-bar"
-
- 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
- B60W50/00—Details 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/08—Interaction between the driver and the control system
- B60W50/14—Means for informing the driver, warning the driver or prompting a driver intervention
-
- 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
- B60W50/00—Details 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/08—Interaction between the driver and the control system
- B60W50/14—Means for informing the driver, warning the driver or prompting a driver intervention
- B60W50/16—Tactile feedback to the driver, e.g. vibration or force feedback to the driver on the steering wheel or the accelerator pedal
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
- B62D—MOTOR VEHICLES; TRAILERS
- B62D15/00—Steering not otherwise provided for
- B62D15/02—Steering position indicators ; Steering position determination; Steering aids
- B62D15/025—Active steering aids, e.g. helping the driver by actively influencing the steering system after environment evaluation
- B62D15/026—Active steering aids, e.g. helping the driver by actively influencing the steering system after environment evaluation combined with automatic distance control, i.e. electronic tow bar
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/0088—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots characterized by the autonomous decision making process, e.g. artificial intelligence, predefined behaviours
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/02—Control of position or course in two dimensions
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/02—Control of position or course in two dimensions
- G05D1/021—Control of position or course in two dimensions specially adapted to land vehicles
- G05D1/0212—Control of position or course in two dimensions specially adapted to land vehicles with means for defining a desired trajectory
- G05D1/0217—Control of position or course in two dimensions specially adapted to land vehicles with means for defining a desired trajectory in accordance with energy consumption, time reduction or distance reduction criteria
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/02—Control of position or course in two dimensions
- G05D1/021—Control of position or course in two dimensions specially adapted to land vehicles
- G05D1/0212—Control of position or course in two dimensions specially adapted to land vehicles with means for defining a desired trajectory
- G05D1/0223—Control of position or course in two dimensions specially adapted to land vehicles with means for defining a desired trajectory involving speed control of the vehicle
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/02—Control of position or course in two dimensions
- G05D1/021—Control of position or course in two dimensions specially adapted to land vehicles
- G05D1/0287—Control of position or course in two dimensions specially adapted to land vehicles involving a plurality of land vehicles, e.g. fleet or convoy travelling
- G05D1/0291—Fleet control
- G05D1/0295—Fleet control by at least one leading vehicle of the fleet
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/16—Anti-collision systems
- G08G1/161—Decentralised systems, e.g. inter-vehicle communication
- G08G1/163—Decentralised systems, e.g. inter-vehicle communication involving continuous checking
-
- 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/165—Anti-collision systems for passive traffic, e.g. including static obstacles, trees
-
- 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
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/22—Platooning, i.e. convoy of communicating vehicles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- 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
- B60W50/00—Details 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/08—Interaction between the driver and the control system
- B60W50/14—Means for informing the driver, warning the driver or prompting a driver intervention
- B60W2050/143—Alarm means
-
- 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
- B60W50/00—Details 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/08—Interaction between the driver and the control system
- B60W50/14—Means for informing the driver, warning the driver or prompting a driver intervention
- B60W2050/146—Display means
-
- 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
- B60W2300/00—Indexing codes relating to the type of vehicle
- B60W2300/14—Tractor-trailers, i.e. combinations of a towing vehicle and one or more towed vehicles, e.g. caravans; Road trains
- B60W2300/145—Semi-trailers
-
- 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
- B60W2420/00—Indexing codes relating to the type of sensors based on the principle of their operation
- B60W2420/40—Photo, light or radio wave sensitive means, e.g. infrared sensors
- B60W2420/403—Image sensing, e.g. optical camera
-
- 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
- B60W2420/00—Indexing codes relating to the type of sensors based on the principle of their operation
- B60W2420/40—Photo, light or radio wave sensitive means, e.g. infrared sensors
- B60W2420/408—Radar; Laser, e.g. lidar
-
- 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
- B60W2510/00—Input parameters relating to a particular sub-units
- B60W2510/06—Combustion engines, Gas turbines
- B60W2510/0638—Engine speed
-
- 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
- B60W2510/00—Input parameters relating to a particular sub-units
- B60W2510/06—Combustion engines, Gas turbines
- B60W2510/0657—Engine torque
-
- 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
- B60W2510/00—Input parameters relating to a particular sub-units
- B60W2510/06—Combustion engines, Gas turbines
- B60W2510/0671—Engine manifold pressure
-
- 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
- B60W2510/00—Input parameters relating to a particular sub-units
- B60W2510/18—Braking system
- B60W2510/182—Brake pressure, e.g. of fluid or between pad and disc
-
- 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
- B60W2520/00—Input parameters relating to overall vehicle dynamics
- B60W2520/28—Wheel speed
-
- 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
- B60W2540/00—Input parameters relating to occupants
- B60W2540/10—Accelerator pedal position
-
- 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
- B60W2540/00—Input parameters relating to occupants
- B60W2540/12—Brake pedal position
-
- B60W2550/308—
-
- 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/20—Static 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/40—Dynamic objects, e.g. animals, windblown objects
- B60W2554/402—Type
- B60W2554/4026—Cycles
-
- 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/40—Dynamic objects, e.g. animals, windblown objects
- B60W2554/402—Type
- B60W2554/4029—Pedestrians
-
- 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
-
- 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/802—Longitudinal distance
-
- 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/804—Relative longitudinal speed
-
- 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
- B60W2555/00—Input parameters relating to exterior conditions, not covered by groups B60W2552/00, B60W2554/00
- B60W2555/20—Ambient conditions, e.g. wind or rain
-
- 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
- B60W2556/00—Input parameters relating to data
- B60W2556/45—External transmission of data to or from the vehicle
- B60W2556/65—Data transmitted between vehicles
-
- 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
- B60W2710/00—Output or target parameters relating to a particular sub-units
- B60W2710/18—Braking system
-
- 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
- B60W2710/00—Output or target parameters relating to a particular sub-units
- B60W2710/20—Steering systems
-
- 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
- B60W2720/00—Output or target parameters relating to overall vehicle dynamics
- B60W2720/10—Longitudinal speed
-
- 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
- B60W2754/00—Output or target parameters relating to objects
- B60W2754/10—Spatial relation or speed relative to objects
- B60W2754/30—Longitudinal distance
-
- 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
- B60W2754/00—Output or target parameters relating to objects
- B60W2754/10—Spatial relation or speed relative to objects
- B60W2754/50—Relative longitudinal speed
-
- G05D2201/0213—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/005—Moving wireless networks
Definitions
- the present application relates generally to controllers, architectures, methods and systems for enabling vehicles to closely follow one another safely using automatic or partially automatic control, and more particularly, to a system and method for mitigating or avoiding risks due to hazards encountered by connected vehicles operating in a platoon.
- a system and method for mitigating or avoiding risks due to hazards encountered by platooning vehicles is therefore needed.
- a system and method for mitigating or avoiding risks due to hazards encountered by connected vehicles operating in a platoon involves operating a following vehicle in a platoon behind a lead vehicle, receiving data generated by one or more sensors arranged to interrogate a space radially extending from the lead vehicle as the lead vehicle travels over the road surface, ascertaining a hazard caused by an object in the space, and causing the following vehicle to take a preemptive action to avoid or mitigate the hazard caused by the object in the space, the preemptive action taken by the following vehicle prior to the lead vehicle taking any action in response to the hazard caused by the object.
- a plurality of tiered severity threat levels is defined, each level having one or more corresponding preemptive action(s) respectively.
- one of the tiered severity threat levels commensurate with the threat is selected.
- the corresponding one or more preemptive action(s) is/are then implemented by the following vehicle to mitigate or avoid the risks associated with the object.
- the tiered threat levels include low, moderate, high and emergency.
- one of the preemptive actions may involve increasing the gap between the two vehicles by decreasing the relative velocity of the following vehicle(s) prior to taking any preemptive action by the lead vehicle. By reducing the relative velocity of the following vehicle first, the gap between the vehicles will grow.
- the gap can be increase while either maintaining or dissolving the platoon. In either case, a normal operating gap may be reestablished once the perceived threat has passed.
- raw data collected by the one or more sensors, on the lead vehicle is transmitted by the lead vehicle to the following vehicle.
- the following vehicle is responsible for perceiving the environment within the space radially extending from the lead vehicle, ascertaining the hazard caused by the object in the space, and taking a preemptive action prior to and/or without waiting for the lead vehicle taking any preemptive action.
- the lead vehicle is responsible for perceiving the environment in the space, ascertaining the hazard level, and then transmitting one or more coded commands, each indicative or a preemptive action, to the following vehicle.
- the following vehicle interprets the commands and implements the preemptive action(s) prior to the lead vehicle taking any preemptive action.
- pre-cognitive braking is implemented with platooning vehicles.
- a notice is sent to the following vehicle by the lead vehicle in response to a braking event by the lead vehicle.
- the following vehicle initiates a braking before the lead vehicle, resulting in an increase of a gap maintained between the two vehicles.
- a system operating onboard a vehicle is configured to receive data from one or more sensors external to the vehicle that are arranged to sense a driving condition in the vicinity of the vehicle. In response, the system is arranged to make a decision or take an action at least in part based on the received data.
- FIG. 1 is a block diagram of a controller architecture suitable for use in an automated or partially automated vehicle control system that supports platooning.
- FIG. 2 is a block diagram of a representative platoon controller architecture suitable for use in the automated or partially automated vehicle control system of FIG. 1 .
- FIG. 3 is a block diagram of a gap controller in accordance with one embodiment.
- FIGS. 4A-4C are a series of diagrams illustrating different control states used by a gap regulator in accordance with one embodiment during different operational states.
- FIG. 5 is a state space diagram illustrating a sliding mode control scheme.
- FIG. 6 is a specific ASIL compliant controller hardware architecture suitable for use in an automated or partially automated vehicle control system that supports platooning.
- FIG. 7 illustrates components of a gateway in accordance with one embodiment.
- FIG. 8 is a diagram showing a lead vehicle and several following vehicle(s) encountering a hazard represented by an object while traveling across a road surface.
- FIGS. 9A-9C are a set of block diagrams illustrating a non-exclusive embodiment of a system for mitigating or avoiding risks due to hazards encountered by connected vehicles in accordance with the present invention.
- FIGS. 10A-10C are another set of block diagrams illustrating another non-exclusive embodiment of a system for mitigating or avoiding risks due to hazards encountered by connected vehicles in accordance with the present invention.
- FIG. 11 illustrates an illustrative plurality of tiered severity threat levels each having one or more corresponding preemptive action(s) in accordance with a non-exclusive embodiment of the present invention.
- FIG. 12 illustrates several categories of preemptive actions in accordance with a non-exclusive embodiment of the present invention.
- FIG. 13 illustrates a flow chart illustrating operational steps in accordance with a non-exclusive embodiment of the present invention.
- FIG. 14 illustrates two vehicles operating in a platoon in accordance with the present invention.
- FIG. 15 illustrates a plot showing a gap between two platooning vehicles during pre-cognitive braking in accordance with a non-exclusive embodiment of the invention.
- FIG. 16 illustrates a flow chart detailing steps for implementing pre-cognitive braking in accordance with the a non-exclusive embodiment of the invention.
- the Applicant has proposed various vehicle platooning systems in which a second, and potentially additional, vehicle(s) is/are automatically, or semi-automatically controlled to closely follow a lead vehicle in a safe manner
- U.S. application Ser. Nos. 15/605,456, 15/607,902; 13/542,622 and 13/542,627; U.S. Provisional Application Nos. 62/377,970 and 62/343,819; and PCT Application Nos. PCT/US2014/030770, PCT/US2016/049143 and PCT/US2016/060167 describe various vehicle platooning systems in which a trailing vehicle is at least partially automatically controlled to closely follow a designated lead vehicle.
- One of the goals of platooning is typically to maintain a desired longitudinal distance between the platooning vehicles, which is frequently referred to herein as the “desired gap”. That is, it is desirable for the trailing vehicle (e.g., a trailing truck) to maintain a designated gap relative to a specific vehicle (e.g., a lead truck).
- the vehicles involved in a platoon will typically have sophisticated control systems suitable for initiating a platoon, maintaining the gap under a wide variety of different driving conditions, and gracefully dissolving the platoon as appropriate.
- FIG. 1 diagrammatically illustrates a vehicle control architecture that is suitable for use with platooning tractor-trailer trucks.
- the specific controller illustrated is primarily designed for use in conjunction with a platooning system in which both vehicles include an active driver.
- the driver of the lead vehicle being fully responsible for control of the front vehicle.
- the a driver of the trailing vehicle is responsible for steering the trailing vehicle, but the platoon controller 110 is primarily responsible for controlling the engine torque and braking requests of the following vehicle during active platooning.
- generally similar control schemes can be used in systems which contemplate more automated control of one or both of the platoon partners.
- a platoon controller 110 receives inputs from a number of sensors 130 on the tractor and/or one or more trailers or other connected units, and a number of actuators and actuator controllers 150 arranged to control operation of the tractor's powertrain and other vehicle systems.
- An actuator interface 160 may be provided to facilitate communications between the platoon controller 110 and the actuator controllers 150 .
- the platoon controller 110 also interacts with an inter-vehicle communications controller 170 which orchestrates communications with the platoon partner and a Network Operations Center (NOC) communications controller 180 that orchestrates communications with a NOC.
- the vehicle also preferably has selected configuration files 190 that include known information about the vehicle.
- the functional components of the platoon controller 110 include gap controller 112 , a variety of estimators 114 , one or more partner vehicle trackers 116 and various monitors 118 . In many applications, the platoon controller 110 will include a variety of other components 119 as well. Exemplary embodiments of the platoon controller 110 and gap controller 112 are described in more detail below with reference to FIGS. 2 and 3 .
- Some of the sensors utilized by the platoon controller 110 may include GNSS (GPS) unit 131 , wheel speed sensors 132 , inertial measurement devices 134 , radar unit 137 , LIDAR unit 138 , cameras 139 , accelerator pedal position sensor 141 , steering wheel position sensor 142 , brake pedal position sensor 143 , and various accelerometers 144 .
- GPS global navigation satellite systems
- GPS is just one of the currently available global navigation satellite systems (GNSS). Therefore, it should be appreciated that data from any other GNSS system or from other suitable position sensing systems may be used in place of, or in addition to, the GPS system.
- sensors including wheel speed sensors, 132 , radar unit 137 , accelerator pedal position sensor 141 , steering wheel position sensor 142 , brake pedal position sensor 143 , and accelerometer 144 are relatively standard equipment on newer trucks (tractors) used to pull semi-trailers.
- others such as the GNSS unit 131 and LIDAR unit 138 (if used) are not currently standard equipment on such tractors or may not be present on a particular vehicle and may be installed as needed or desired to help support platooning.
- vehicle actuators controllers 150 that the platoon controller may direct at least in part include engine torque controller 152 (which is often part of the integrated functionality of an engine control unit (ECU) or powertrain control module (PCM)), transmission controller 154 , brake controller 156 , steering controller 157 (when automated steering is provided); and clutch controller 158 .
- ECU engine control unit
- PCM powertrain control module
- transmission controller 154 brake controller 156
- brake controller 156 brake controller
- steering controller 157 when automated steering is provided
- clutch controller 158 clutch controller 158 .
- the specific actuator controllers 150 directed or otherwise utilized by the platoon controller on any particular controlled vehicle may vary widely. Further, the capabilities of any particular actuator controller (e.g.
- an actuator interface 160 is preferably provided to translate requests, commands, messages and instructions from the platoon controller 110 into formats that are appropriate for the specific actuator controller hardware and software utilized on the controlled vehicle.
- the actuator interface 160 also provides a mechanism for communicating/translating messages, commands, instructions and requests received from the various actuator controllers back to the platoon controller 110 .
- an appropriate actuator interface would be provided to interact with each of the specific vehicle controllers utilized.
- this may include one or more of an engine torque interface 161 , a brake interface 162 , a transmission interface 164 , a retarder interface 165 (if a separate retarder controller is used), a steering interface 167 , and/or any other appropriate controller interface 169 .
- a separate retarder controller may be accessible to, and therefore directed by, platoon controller 110 through an appropriate retarder interface 165 .
- the platoon controller 110 may separately determine a retard command that it sends to the actuator interface 160 .
- the actuator interface will interpret the retard command and pass on appropriate retardation control commands to the ECU or other appropriate vehicle controller.
- the communications between vehicles may be directed over any suitable channel and may be coordinated by inter-vehicle communications controller 170 .
- DSRC Dedicated Short Range Communications
- IEEE 802.11p protocol IEEE 802.11p protocol
- other communications protocols and channels may be used in addition to or in place of a DSRC link.
- the inter vehicle communications may additionally or alternatively be transmitted over a cellular communications channel such as 4G LTE Direct, 5G, a Citizen's Band (CB) Radio channel, one or more General Mobile Radio Service (GMRS) bands, and one or more Family Radio Service (FRS) bands or any other now existing or later developed communications channels using any suitable communication protocol.
- a cellular communications channel such as 4G LTE Direct, 5G, a Citizen's Band (CB) Radio channel, one or more General Mobile Radio Service (GMRS) bands, and one or more Family Radio Service (FRS) bands or any other now existing or later developed communications channels using any suitable communication protocol.
- 4G LTE Direct 4G LTE Direct
- 5G Fifth Generation
- CB Citizen's Band
- GMRS General Mobile Radio Service
- FSS Family Radio Service
- the transmitted information may include the current commands generated by the platoon controller 110 such as requested/commanded engine torque 280 , requested/commanded braking deceleration 282 . They may also include steering commands, gear commands, etc. when those aspects are controlled by platoon controller 110 . Corresponding information is received from the partner vehicle, regardless of whether those commands are generated by a platoon controller or other suitable controller on the partner vehicle (e.g., an adaptive cruise control system (ACC) or a collision mitigation system (CMS)), or through other or more traditional mechanisms—as for example, in response to driver inputs (e.g., accelerator pedal position, brake position, steering wheel position, etc.).
- ACC adaptive cruise control system
- CMS collision mitigation system
- tractor sensor information provided to platoon controller 110 is also transmitted to the platoon partner and corresponding information is received from the platoon partner so that the platoon controllers 110 on each vehicle can develop an accurate model of what the partner vehicle is doing.
- any other relevant information that is provided to the platoon controller including any vehicle configuration information 190 that is relevant to the platoon controller.
- the specific information transmitted may vary widely based on the requirements of the platoon controllers 110 , the sensors and actuators available on the respective vehicles, and the specific knowledge that each vehicle may have about itself.
- the information transmitted between vehicles may also include information about intended future actions. For example, if the lead vehicle knows it approaching a hill, it may expect to increase its torque request (or decrease its torque request in the context of a downhill) in the near future and that information can be conveyed to a trailing vehicle for use as appropriate by the platoon controller 110 .
- the nature of the expected events themselves can be indicated (e.g., a hill, or curve or exit is approaching) together with the expected timing of such events.
- the intended future actions can be reported in the context of expected control commands such as the expected torques and/or other control parameters and the timing at which such changes are expected.
- expected control commands such as the expected torques and/or other control parameters and the timing at which such changes are expected.
- expected events there are a wide variety of different types of expected events that may be relevant to the platoon control.
- the communications between the vehicles and the NOC may be transmitted over a variety of different networks, such as the cellular network, various Wi-Fi networks, satellite communications networks and/or any of a variety of other networks as appropriate.
- the communications with the NOC may be coordinated by NOC communications controller 180 .
- the information transmitted to and/or received from the NOC may vary widely based on the overall system design.
- the NOC may provide specific control parameters such as a target gap tolerance. These control parameters or constraints may be based on factors known at the NOC such as speed limits, the nature of the road/terrain (e.g., hilly vs. flat, winding vs. straight, etc.) weather conditions, traffic or road conditions, etc.
- the NOC may provide information such information to the platoon controller.
- the NOC may also provide information about the partner vehicle including its configuration information and any known relevant information about its current operational state such as weight, trailer length, etc.
- the configuration file 190 may include a wide variety of information about the host vehicle that may be considered relevant to the controller.
- some of the information might include the vehicle's specification including such things as engine performance characteristics, available sensors, the nature of its braking system, the location of its GNSS antenna relative to the front of the cab, gear ratios, differential ratios etc.
- FIG. 2 illustrates a particular embodiment of a platoon controller 110 .
- the platoon controller 110 includes a gap controller 112 , a plurality of estimators 114 , one or more trackers 116 , any desired monitors 118 and potentially any of a variety of other components 119 .
- the gap controller 112 includes a target and state setter 200 , a gap regulator 210 and a gap estimator 240 .
- the target and state setter 200 is arranged to determine the intended operational mode (state) of the gap regulator 210 and the values of any variable control parameters that are appropriate for use in that operational mode.
- the gap regulator 210 is arranged to control the trailing platoon partner in the manner designated by the target and state setter 200 .
- the gap regulator 210 controls the vehicle in a manner that seeks to attain and maintain the desired gap in accordance with any designated control parameters specified by the state setter 200 .
- the gap regulator 210 controls the vehicle in a manner that seeks to attain the appropriate response for the selected operational mode.
- the gap estimator 240 is arranged to estimate/determine the current gap based on actual measurements and/or other information that is available to the platoon controller 110 . It should be apparent that an accurate understanding of the current gap is important to successful operation of the gap regulator. At the same time, it should be appreciated that any measurement system has inherent tolerances and can be subject to reporting errors and/or may become unavailable in some circumstances. Thus, the gap estimator 240 is configured to receive information from multiple position or relative position related sensors and to fuse such data into a reliable estimate of the current gap.
- the torque and braking requests generated by GAP regulator 210 are sent to the appropriate actuator interface (e.g., engine torque interface 161 and brake interface 162 respectively).
- the engine torque interface 161 then forwards an appropriate torque command to engine torque controller 152 which directs the delivery of the requested torque by directing various engine operating parameters such as fuel charge, valve timing, retarder state, etc. appropriately.
- the brake interface 162 generates an appropriate brake request that is sent to the brake controller 156 .
- gap controller 112 A particular embodiment of gap controller 112 is described in more detail below with reference to FIG. 3 .
- estimators 114 that are useful for the gap controller 112 .
- these may include one or more of a mass estimator 271 , a drag estimator 273 , a ground speed estimator 275 , a gyro bias estimator 277 and/or other estimators 279 .
- the mass estimator 271 is arranged to estimate the respective masses of the platoon partners. These mass estimations may be used by the gap controller 112 to help scale its torque and brake requests appropriately based on the respective weights (masses) of the platoon partners.
- the drag estimator 273 is arranged to estimate the respective drag resistances of the platoon partners. These drag resistance estimates may also be used by the gap controller to help adjust its torque and brake requests appropriately.
- the drag resistance of any particular truck or other vehicle can vary based on a variety of factors including: (a) its drag profile (which in the context of a truck may change based on the trailer being pulled—if any, or other characteristics of the load); (b) the vehicle's current speed, (c) wind speed and direction, (d) rolling resistance, (e) platoon state (e.g., whether a platoon is active, the position of the vehicle within the platoon, the gap), (f) bearing wear, etc.
- the ground speed estimator 275 is arranged to estimate the actual ground speed of the respective platoon partners.
- Many trucks and other vehicles have wheel speed sensors that can quite accurately measure the rotational speed of the associated wheels.
- the actual ground speed at which the vehicles are traveling will vary based on the respective diameters of the wheels and slip conditions of the tires.
- the precise diameter of the wheels can vary based on the tires used.
- the diameter of the wheels will vary over time with tire wear, changes in ambient temperature and other factors. The wheel diameter will even change over the course of a particular trip as the tires heat up (or otherwise change in temperature) during use. In practice, all of these variations in wheel diameter are potentially significant enough to impact the gap estimation and gap control.
- the ground speed estimator 275 is arranged to estimate the actual ground speed based on measured wheel speed and other available information such as GNSS information.
- the ground speed estimates are particularly useful in times when tracker based gap measurements (e.g., radar, cameras, LIDAR, etc.) aren't available—which may occur, for example, when the platoon partners are laterally offset due to a lane change, etc.
- the measurements utilized by the gap controller 112 are inertial measurements that are gyro based. These may include yaw measurements which indicate the rate at which the associated vehicle is turning, longitudinal acceleration measurements, etc. Gyros often have an inherent measurement error referred to as a gyro bias that can affect measurements.
- the gyro bias estimator 277 estimates such biases to allow the gap controller to compensate for such gyro based measurement errors.
- the platoon controller 110 can include any other estimators 279 that may be useful to any particular gap controller 112 as well.
- the platoon controller 110 may also include one or more trackers 116 .
- Each tracker 116 is arranged to measure or otherwise determine the gap.
- One type of tracker that is used in many implementations is a radar based radar tracker 283 .
- Newer commercially available trucks often come equipped with a radar unit as standard equipment and radar trackers are particularly well suited for use in such vehicles.
- one or more radar units may be installed on any vehicle that does not come pre-equipped with a radar unit to facilitate use of radar tracker 283 .
- some specific radar trackers are described in more detail in co-pending U.S. application Ser. Nos. 15/590,715 and 15/590,803, both filed May 9, 2017, both of which are incorporated herein by reference.
- LIDAR is another distance measuring technology that is well suited for measuring the gap between vehicles. LIDAR is quickly gaining popularity for use in automated and autonomous driving applications. LIDAR tracker 286 is well suited for use on vehicles that have or are provided with LIDAR units. Cameras and stereo cameras are also becoming more popular distance measuring tools for use in various automated and autonomous driving applications.
- a GPS tracker could be used that is based primarily on the respective reported GPS positions of the vehicles.
- the tracker(s) used in many embodiments are configured to fuse data from multiple sensors to help validate the measurements of the primary sensors used by the respective trackers.
- the aforementioned radar tracker application describes a variety of methods for fusing data to help validate measurements of a primary sensor in that manner
- the gap estimator 240 could replace or be replaced by one or more of the trackers, or could be thought of as a tracker itself since it determines/estimates the gap based on inputs from multiple sensors.
- the gap estimator 240 is shown separately as part of gap controller 112 since it fuses distance data from the tracker(s) and any other available sources such as GNSS sensors on each of the vehicles.
- the platoon controller 110 may also include one or more monitors 118 that are configured to monitor specific components that are relevant to gap control.
- one specific monitor that is particularly useful to the control of platooning trucks is brake health monitor 291 .
- the brake health monitor 291 is configured to monitor the brake system and to identify circumstances in which the brakes may not be able to deliver the level of braking normally expected for platoon control—as for example could occur if the foundation brakes include drum brakes that have been used while traveling downhill in the mountains to the extent that they are close to overheating. If the brake health monitor 291 identifies such a circumstance, it informs the platoon controller, which can take the appropriate remedial action.
- the appropriate remedial action will vary based on the specific circumstances identified by the brake health monitor, but may include, for example, actions such as dissolving the platoon, increasing the target gap to a level more appropriate for the brake conditions, etc.
- the brake health monitor can also configured to identify circumstances in which the condition of the brakes has improved (e.g., the brakes have cooled sufficiently) and inform the platoon controller of those circumstances as well so that the platoon controller can act accordingly. For example, improved braking status may allow the target gap to be reduced, a platoon to be reestablished or other appropriate actions.
- the platoon controller may include any of a variety of other monitors 299 that are configured to monitor the state or status of other components, systems, environmental conditions, road or traffic conditions, etc. that may be relevant to platoon control.
- a DSRC link monitor may be provided to monitor the status of a DSRC communication link between the platoon partners.
- the gap controller 112 includes a target and state setter 200 , a gap regulator 210 and a gap estimator 240 .
- the target and state setter 200 includes an operating state selector 203 , and a control parameter selector 206 that determines, selects, sets or otherwise indicates to the gap regulator the values of any variable control parameters that are appropriate for use in the selected operational mode.
- the operating state selector 203 is arranged to determine the intended operational mode (state) of the gap regulator 210 .
- the operational modes might include a “normal” or “gap control” operational mode in which the gap regulator is configured to control towards attaining an maintaining a designated gap between the vehicles.
- control parameter variables dictated by the control parameter selector might include the target gap itself (e.g. 10 m, 12 m, etc.)—which may vary somewhat based on driving conditions (e.g., weather, terrain, road conditions, traffic, etc.).
- Other control parameters during normal operation may include parameters that impact the draw-in speed, the tightness of the control, tolerances or variations between torque control and braking control, etc.
- “initiate platoon” and/or “draw-in” or “pull-in” may be one or more separate states that are used to establish a platoon and/or to bring the platoon partners together in a safe manner under at least partially automated control.
- dissolving a platoon includes increasing the gap between the vehicles in a controlled manner to/towards a point at which the platoon can be dissolved and vehicle control can be safely transferred to manual control by the driver or to control through the use of a different system such as adaptive cruise control.
- the dissolve mode may optionally be triggered by a wide variety of different circumstances, as for example, in response to one of the platoon partners or the NOC deciding to terminate the platoon; the detection of a car cutting-in between the platooning vehicles; the loss of communications between the vehicles for an extended period; the detection of an object in front of the lead vehicle that is too slow or too close to the platoon; etc.
- Velocity control, or relative velocity control may be preferable to trying to control to maintain a particular gap in a variety of specific circumstances—as for example when the trailing vehicle's radar (or other) tracking unit loses sight of the partner vehicle, as can occur when there is a lateral offset between the vehicles due to a lane change or other conditions.
- the gap regulator 210 is arranged to control the trailing platoon partner in the manner designated by the target and state setter 200 .
- the gap regulator 210 includes a scaler 212 and two separate controllers which are used in different combinations in different operating modes.
- the controllers include a sliding mode controller 215 (which performs gap control) and a velocity/relative velocity controller 218 . It should be appreciated that in other embodiments, a single controller, additional and/or different may be provided as appropriate for any particular implementation.
- the feed forward scaler 212 is configured to scale the torque and brake signals from the front vehicle before adding them to the outputs from the sliding mode and relative velocity controllers 215 , 218 to create the torque and brake request to the engine and brake controllers.
- Such scaling may be based on factors such as the respective weights (masses) of the platoon partners, the respective drags of the vehicles, the severity of a braking event (e.g., in high braking scenarios, the braking command may be increased a bit to provide a margin of safety to account for uncertainties in braking performance and reactions times), etc.
- such scaling functions can be integrated into the respective controllers themselves if desired.
- the sliding mode controller 215 is configured to control the trailing vehicle in a manner that seeks to attain and maintain the desired gap in accordance with the target gap and any other control parameters specified by the control parameter selector 206 .
- its primary function is gap control.
- the velocity controller 218 is configured to control the trailing vehicles in a manner that maintains a designated velocity relative to the lead vehicle, or in some circumstances, simply a designated velocity. In the illustrated embodiment, these two separate controllers are provided so that the gap regulator 210 can provide different types of control, as may be appropriate in different operational circumstances. A few specific examples are described with reference to FIGS. 4A-4C .
- both the controllers 215 and 218 are operated continuously during platooning and the selector/adder 250 is used to select the appropriate signals to output based on the current operating mode.
- An optional braking monitor 255 is a safety feature that may be utilized to help ensure that the brake commands outputted by selector/adder 250 don't overly aggressively brake the trailing vehicle except in where necessary from a safety/crash prevention standpoint. This is to reduce the risk of traffic behind the trailing platoon partner from being impacted by unexpected aggressive braking of the trailing platoon partner.
- the sliding mode controller 215 is arranged to control the trailing vehicle in a manner such that its relative velocity relative to the front vehicle varies as a function of the gap between the vehicles.
- This characteristic is illustrated in the state space diagrams of FIG. 5 which show a control scheme in accordance with one specific implementation. More specifically, FIG. 5 plots relative velocity between the vehicles (the Y-axis) vs. gap between the vehicles (the X-axis).
- FIG. 5 also show a torque request controller target control line 320 .
- the nominal desired gap is 12 meters—which is represented by line 310 .
- the target control point 311 is 12 meters with zero relative velocity, which is the point represented by the intersection of line 310 (12 meters gap) and line 312 (zero relative velocity).
- the torque request controller component 221 of gap regulator 210 is configured to generate a torque request that is appropriate to control the gap in accordance with target control line 320 .
- the torque request is then implemented by engine torque controller 152 .
- the rear truck is controlled to travel slightly faster than the front truck is traveling such that the relative velocity of the rear truck has a small positive value.
- the rear truck draws closer to the lead truck, its relative velocity is reduced in a smooth manner until the gap is reduced to the target control point 311 , at which point the relative velocity would be zero if perfect control were attained. If the rear truck gets closer than the desired gap, it is slowed so that it has a negative relative velocity relative to the lead truck to reestablish the desired gap.
- the sliding mode controller 215 utilizes a unified sliding mode control scheme during both the “pull-in” and gap maintenance stages of platooning. Configuring the sliding mode controller to control towards target control line 320 helps ensure that the relative speed vs. gap relationship stays within a region safe for platooning.
- the sliding mode controller 215 includes separate controllers (e.g. torque request controller 221 and brake request generator components 223 ) which are configured to control towards different gap control targets.
- the different control targets are illustrated in the state space diagrams of FIG. 5 which show a control scheme in accordance with one specific implementation. More specifically, FIG. 5 shows a brake request controller target control line 330 in addition to torque request controller target control line 320 . FIG. 5 additionally shows representative transition paths from various points in the state space to the torque request target control line 320 .
- modulating the torque request alone is sufficient to control the gap appropriately without requiring the use of the foundation brakes. This is in part because the torque request can be negative to a certain degree without needing to actuate the foundation brakes through the use of engine braking and/or the retarder (if available). As mentioned above, when fuel is cut-off there will be some pumping losses and some frictional losses in the powertrain, so some level of negative torque can be provided while using normal valve timing by simply reducing the fuel charge appropriately. When larger negative torque is needed, the engine torque controller 152 can create larger negative torques by actuating the retarder and/or by taking other appropriate measures.
- the brake request controller component 223 of gap regulator 210 is arranged to generate brake requests during normal operation that are generally arranged to maintain a different gap—specifically a smaller gap—than the torque request controller 221 targets.
- This difference in the gaps that the torque and brake request controllers control to is sometimes referred to herein as the gap tolerance 340 .
- brake requests 213 are not generated unless or until the gap is reduced at least the gap tolerance below the torque request target control line 320 . Since the brakes can only be used to slow the vehicle, the effect of this difference is that the trailing truck will be allowed to creep in a relatively small amount (2 meters in the example) before the foundation brakes are actuated when the gap regulator 210 cannot maintain the desired gap through control of the torque request alone.
- Normal gap control is illustrated in FIG. 4A .
- the sliding mode controller 215 is use to determine torque and brake requests that are appropriate to attain and maintain the target gap set by control parameter selector 206 .
- the torque and brake requests generated by the sliding mode controller 215 may be scaled appropriately by selector/adder 250 based on inputs from feed forward scaler 212 .
- the outputs of the relative velocity controller 218 are not used in the control of the trailing vehicle.
- the sliding mode controller 215 includes separate torque request and brake request controllers 221 , 223 as illustrated in FIG. 3 .
- the torque request and brake request controllers 221 , 223 are configured to control the engine and brakes respectively towards different gap targets which tends to provide a smoother, more comfortable ride and reduce the use of wheel brakes (e.g., the foundation brakes in tractor-trailer rigs) compared to control in which the engine and brakes are controlled to the same target gap.
- wheel brakes e.g., the foundation brakes in tractor-trailer rigs
- the sliding mode controller 215 works very well to control the gap, there will be operational circumstances in which different types of control may be appropriate. For example, a different type of control may be desirable when it is necessary to dissolve a platoon and return the trailing vehicle to manual or other automated control.
- the gap between vehicles during platooning will be smaller, often much smaller, than can safely be maintained by a driver under manual control. Therefore, in general, when a platoon is dissolved with the intent to restoring manual control of the trailing vehicle, it will be desirable to grow the gap to a distance that is appropriate for manual control before relinquishing control to the driver. This can be accomplished in a smooth manner by relative velocity controller 218 .
- operating state selector 203 determines that the platoon should be dissolved, it directs the GAP regulator 210 to transition to a dissolve mode as represented by FIG. 4B .
- primary control is provided by relative velocity controller 218 .
- the control parameter selector 206 may designate a desired (target) relative velocity for the trailing truck during the dissolve.
- the specific target relative velocity may vary based on the nature of the circumstances and/or the vehicles involved in the platoon. In general, it is desirable to select a relative velocity that will cause the vehicles to gradually, but expeditiously separate, without requiring the trailing vehicle to slow excessively (which could unduly hinder following traffic) and preferably without requiring the lead vehicle to alter its drive plan.
- relative velocities during dissolves on the order of 0.5 to 4 meters per second, as for example, 1-2 m/s, have been found to work well in the context of platooning trucks.
- the lead vehicle may take a variety of actions. For example, the lead truck may accelerate or increase its torque command aggressively. In such cases, it may not be desirable to try to accelerate the trailing truck in a similar manner thereby allowing the lead vehicle to pull away more than would otherwise occur under relative velocity control.
- One way to accomplish this in the context of platooning trucks is to ignore or otherwise disable positive torque commands from feed forward scaler 212 .
- the velocity controller 218 may be configured to permit a certain amount of gap shrinkage when the gap is relatively larger to thereby reduce the overall amount of braking required.
- the sliding mode controller is configured to ensure that the gap between the vehicles is always sufficient to give the trailing vehicle sufficient time to respond in a manner that prevents the trailing vehicle from running into the back of the lead vehicle regardless of the occurrence of (reasonable) unexpected events. Therefore, if the sliding mode controller is outputting a braking or negative torque signal that has a greater magnitude than the relative velocity controller, then that larger braking/negative torque command should be passed to the vehicle's engine and braking controllers.
- the selector/adder 250 is configured to only utilize negative commands (i.e., braking commands and negative torque commands) from the sliding mode controller 215 and to only use such commands when they are greater in magnitude than the commands from the relative velocity controller 218 .
- negative commands i.e., braking commands and negative torque commands
- the relative velocity controller 218 is well suited for use in this circumstance—although the preferred relative velocity control may be a bit different than occurs during a dissolve. Specifically, the goal is typically not to drop back as quickly or as far as would occur during a dissolve—thus a smaller relative velocity (e.g. 0.5 m/s vs. 2 m/s), may be appropriate.
- FIG. 4C One approach to such relative velocity control is illustrated in FIG. 4C .
- velocity controller 218 is used in conjunction with normal scaling from feed forward scaler 212 . This causes the trailing platoon partner to better follow lead vehicle accelerations and/or torque increases than occurs during the dissolve state illustrated in FIG. 4B .
- braking requests and negative torque request from the sliding mode controller 215 may be utilized as appropriate by selector/adder 250 in a manner similar to the approach described above with respect to FIG. 4B .
- platoon and gap controller architectures are illustrated in FIGS. 2 and 3 , it should be appreciated that the specific architectures utilized may vary widely to meet the needs of any particular platooning or other automated vehicle control scheme.
- controllers can be implemented algorithmically using software or firmware algorithms executing on one or more processors, using programmable logic, using digital or analog components or using any combination of the preceding.
- the controlled power plant is an internal combustion engine, as for example a diesel engine.
- the described control approach can be utilized regardless of the nature of the power plant used to provide torque to drive the host vehicle.
- the described controller design, functionalities and architectures may generally be applied to the control of vehicles that utilize electric motors, turbines, fuel cells, or other types of powerplants to provide power to a drivetrain or directly to one or more wheels, including hybrids which combine more than one type of powerplant (e.g., hybrids that incorporate both an electric motor and an internal combustion engine).
- any type of internal combustion engine may be used including gas powered engines, diesel powered engines, two-stroke engines, 4 -stroke engines, variable stroke engines, engines utilizing more than four-strokes, rotary engines, turbine engines, etc.
- FIG. 6 illustrates a platoon control system hardware architecture that is particularly well suited suitable for ASIL compliant platoon control.
- the illustrated embodiment includes three separate controller hardware units. These include platoon controller 410 , vehicle interface controller 460 and gateway processor 470 . Selected components of a representative gateway processor 470 are illustrated in FIG. 7 .
- the platoon controller 410 communicates with the vehicle interface controller 460 through an interface 420 and with gateway 470 through a direct link 478 .
- the link 478 is a dedicated direct wired connection and no other devices are coupled to that link.
- the wired connection may be provided by any suitable form of cabling or traces, as for example co-ax cable, twisted pair wirings, fiber optics or any other suitable physical connection medium.
- the platoon controller 410 incorporates all of the functionality of platoon controller 110 described above.
- the vehicle interface controller 460 (also sometimes referred to as a system manager) performs the functionality of actuator interface 160 and further includes a number of safety monitors.
- the safety monitors are arranged to execute ASIL compliant safety monitoring algorithms and the vehicle interface controller 460 is designed as an ASIL compliant device.
- the vehicle interface controller 460 includes a higher safety level processor and software (including the safety monitors) that independently verifies the commands transmitted by the platoon controller 110 before they are passed on to the vehicle actuators. These verifications use a subset of the available sensor inputs, together with verification algorithms that are independent and distinct from those used by the platoon controller.
- the gateway processor 470 is arranged to coordinate communications between a host vehicle and the platoon partner(s) and to coordinate communication between the host and the network operation center and/or any other entities that are external to the vehicle.
- the gateway processor 470 includes the inter-vehicle communications controller 170 and NOC communication controller 180 as best illustrated in FIG. 7 .
- the inter-vehicle communications controller utilizes a short-range, vehicle-to-vehicle wireless communications protocol, as for example the DSRC protocol.
- the NOC communication controller typically communicates with a networks operations center using cellular or satellite communications.
- connection (link 478 ) between the gateway processor 470 and the platoon controller 410 is a dedicated direct wired connection and no other devices are coupled to the link.
- an Ethernet or similar standardized wired communications protocol is used to pass information between the gateway processor and the platoon controller. This facilitates high speed, high reliability communications between the gateway processor and the platoon controller.
- a 100BASE or higher (e.g. 1000BASE, 10GBASE, etc.) Ethernet physical layer may be used, although it should be appreciated that a variety of other physical layers may be used in other embodiments.
- the gateway processor 470 is also arranged to communicate with a forward facing camera 477 mounted on the vehicle and a dashboard display 475 .
- the gateway processor transmits a video feed received from the forward facing camera 477 to the trailing vehicle(s) so that the driver of the trailing vehicle has a view of what is in front of the lead vehicle.
- the gateway processor 470 receives such a video feed from the gateway processor on the lead vehicle and transmits the feed to the dashboard display 475 where it is displayed to give the driver of the host vehicle a view of what is in front of the lead vehicle.
- Displaying a view of what is in front of the lead vehicle to drivers of a trailing vehicle is desirable to provide the driver of the trailing vehicle with improved situational awareness and the ability to independently react to situations that occur in front of the platoon. This can be particularly important because in many platoons (e.g. platoons that involve tractor trailer trucks) the trailing vehicle will be very close to the lead vehicle (much closer than normal manual driving) and the lead vehicle will effectively block the view of the trailing vehicle which can be an uncomfortable experience for drivers and/or passengers in a trailing platoon partner—especially when they do not have access to a view of what is going on in front of the platoon.
- platoons e.g. platoons that involve tractor trailer trucks
- the trailing vehicle will be very close to the lead vehicle (much closer than normal manual driving) and the lead vehicle will effectively block the view of the trailing vehicle which can be an uncomfortable experience for drivers and/or passengers in a trailing platoon partner—especially when they do not have access to a view
- the video streams passed through the gateway may be managed by a video manager 474 . Since the gateway 470 communicates directly with the camera 477 and/or dashboard display 475 , the platoon controller 410 is not in any way burdened by the need to manage that data flow.
- the gateway 470 also includes a message logger 473 that logs various messages and other information passed there through in order to provide a record for diagnostic purposes and the like.
- the functionality of the message logger 473 will be described in more detail below.
- the platoon controller 410 is configured as a listener on any appropriate vehicle communications buses where it can directly obtain information about the vehicle's operational state—such as the vehicle's current wheel speed, any brake or accelerator pedal inputs, steering wheel position (as appropriate), transmission gear, etc. It is also coupled to sensor units such as GPS unit 131 to receive positional information about the location of the vehicle, and to forward looking radar unit 137 to receive information about the position of objects outside the vehicle (e.g., radar scenes). Similar information may be obtained from other sensors as well, such as LIDAR 138 , camera(s) 139 etc.
- the platoon controller 410 Since the platoon controller 410 is configured strictly as a listener on the vehicle's communication bus(es) and does not itself transmit information over such bus(es), it does not need to be ASIL compliant, as long as the control commands it outputs to the vehicle interface controller are verified to ASIL standards by the vehicle interface controller 460 .
- the vehicle interface controller 460 (also sometimes referred to as the system manager 460 ), which is ASIL compliant, is arranged to send commands to, and otherwise communicate with, the vehicle's engine controller (EECU), the brake controller (BECU), and/or any other appropriate controllers either directly or via one or more communications buses, such as the vehicle's CAN bus(es).
- EECU vehicle's engine controller
- BECU brake controller
- any other appropriate controllers either directly or via one or more communications buses, such as the vehicle's CAN bus(es).
- the interface 420 between platoon controller 410 and vehicle interface controller 460 (also sometimes referred to as the system manager 460 ) is fairly narrowly defined. It includes the substantive commands generated by the platoon controller—which in the illustrated embodiment include torque request 422 , brake request 424 , and optionally a retarder request 426 . When the platoon controller also controls the steering or other aspects of the host vehicle steering and/or other appropriate control commands (not shown) may be included as well.
- the interface 420 also includes a platooning state indicator 428 that is a signal from the platoon controller indicating whether or not it believes that its output should be directing operation of the vehicle.
- the platooning state indicator 428 may take many forms, as for example a simple flag that when high indicates that the platoon controller 410 believes that platooning is/should be active and that its torque, braking and retard commands 422 , 424 , 426 should be followed. In such an arrangement, a low flag state indicates that the platoon controller believes that it is not controlling the vehicle.
- the vehicle interface controller 460 does not forward any torque, braking, retard or other control commands at any time that the platooning state indicator 428 indicates that platoon control is not active.
- the vehicle interface controller/system manager 460 initiates a termination of the platoon.
- the interface 420 also facilitates the transmission of certain state information—which is preferably ASIL validated state information—about both the host vehicle and the partner truck that is useful to the safety monitors.
- the host vehicle state information 441 includes state information about the host vehicle that has been validated (e.g., ASIL-C validated) by the system manager 460 and is useful to one or more safety monitors on the partner vehicle.
- the partner vehicle state information 444 includes state information about the partner vehicle that has been validated by the partner vehicle's system manager and is useful for one or more safety monitors 465 on the host vehicle.
- Host vehicle state information 441 is transmitted to the platoon controller 410 , which forwards such information without modification to the gateway 470 , which in turn forwards the host vehicle state information to the gateway on the partner vehicle.
- Partner vehicle state information 444 received by gateway 470 from the partner vehicle's gateway is forwarded without modification to the platoon controller 410 and from there to system manager 460 (again without modification).
- the host state information 441 is transmitted with a checksum or other suitable data integrity verification mechanism that allows the receiving system manager to verify that the data it receives is uncorrupted. Any corrupted information can then be ignored.
- the ASIL validated state information is passed without modification from one ASIL compliant device (system manager 460 on a first platoon partner) to another (system manager 460 on a second platoon partner) and therefore is suitable for use in ASIL compliant safety checking algorithms—even when intermediate transmitting devices (e.g., platoon controller 410 , gateway 470 ) are not themselves ASIL compliant.
- the host and partner vehicle state information may include any ASIL validated state information that is used by any of the safety monitors. This may include, for example, vehicle wheel speeds, brake requests, torque requests and/or delivered torque, brake air supply pressure, steering position, accelerometer readings and/or any other information about the partner vehicle used by the system manager 460 as part of a safety monitor.
- the platoon controller 410 utilizes partner state information originated by an ASIL validated device beyond the state information used by the system manager 460 , that information can optionally be included in the vehicle state information 441 , 444 as well—although such inclusion is not necessary and usually not desirable since such information can typically be obtained and sent by the partner vehicle's platoon controller, which reduces the bandwidth that needs to be allocated to the interface 420 .
- the platoon controller 410 is preferably an authorized listener on any appropriate vehicle control bus(es), the platoon controller does not need to wait to receive such information from the system manager. Rather, it obtains any relevant host vehicle sensor information directly from the appropriate sensor over any suitable connection such as an appropriate CAN bus.
- any sensor information relevant to the system manager on the partner vehicle is read by the system manager (regardless of whether it is also read by the platoon controller) and included in host vehicle state information 441 so that the partner vehicle's system manager is ensured that such information is ASIL verified.
- any host vehicle sensor information that is not directly accessible by the platoon controller can be received via the system manager 460 acting as an intermediary.
- the host vehicle sensor information used by the host vehicle platoon controller 410 and the host vehicle system manager 460 will often vary and may further vary from the partner vehicle sensor information of interest.
- the host platoon controller utilizes GNSS position data in the determination of the torque and braking requests, however the GNSS position information may not be utilized by the System Manager since it is not ASIL compliant.
- Some of the sensor information that is used by the safety monitor on the host vehicle may not be needed by the safety monitor on the partner vehicle. This may include information such as the radar scenes, the accelerator pedal position, inputs from a host vehicle driver interface device 469 , etc. To the extent that such sensor information is not used by the partner vehicle, there is no need for such information to be included in the vehicle state information 441 , 444 .
- a host vehicle's sensor information that is used by the platoon controller on the partner vehicle may not be ASIL compliant and therefore may not be used in the safety monitors on the partner vehicle.
- sensor information that is not relevant to the safety monitors on the partner vehicle does not need to be included as part of vehicle state information 441 , 444 . Rather, such data may be obtained by the platoon controller 410 and sent to the corresponding platoon controller on the partner vehicle (by way of communication controllers 470 ).
- the driver interface device 469 may be a button or other suitable mechanism positioned at a convenient location on the host vehicle dashboard or elsewhere in the host vehicle cabin.
- the driver interface device 469 is a mechanism that the driver may press as appropriate to indicate that the driver is ready to platoon during initiation of a platoon, or to initiate the dissolution of a platoon when platooning is no longer desired.
- the use of the driver interface device 469 is described in more detail in U.S. patent application Ser. No. 15/607,902 which is incorporated herein by reference.
- commands from the driver interface device 469 (which are preferably ASIL compliant) are sent to the vehicle interface controller 460 and passed from there to the platoon controller 410 .
- requests to the driver interface device pass from the platoon controller to the vehicle interface controller 460 and from the vehicle interface controller 460 to the driver interface device 469 .
- This architecture simplifies the work that must be done to make the driver interface device 469 ASIL compliant.
- the platoon controller 410 may also be a direct listener to commands from the driver interface device.
- interface 420 includes driver platoon related requests and commands 427 which represent the request sent to and commands received from the driver interface device 469 .
- the vehicle interface controller 460 is implemented as a single dedicated integrated circuit chip and the platoon controller 410 and gateway processor 470 are each implemented as separate system on modules (SOMs).
- SOMs system on modules
- the platoon control system hardware architecture illustrated in FIG. 6 is particularly well suited for efficiently handling platooning control related tasks in an ASIL compliant manner using information available from a variety of sources including sources that are not themselves ASIL. With the described arrangement, the powertrain control commands ultimately issued by the control system may be ASIL rated.
- the hardware architecture of FIG. 6 also has several advantages from a security standpoint.
- the gateway processor 470 is not connected to any of the vehicle's control related communications buses (e.g., the CAN bus(es)). Therefore, the gateway processor 470 , which is potentially the least secure of the three hardware components, is not able to transmit any information directly onto any of the more secure vehicle communications buses or receive any information directly from such buses—which is advantageous from a security standpoint since a nefarious entity cannot gain control the vehicle in any way by somehow hacking into the gateway processor 470 . Furthermore, with this arrangement, the gateway processor 470 does not need to be ASIL compliant which greatly simplifies its certification.
- a road obstacle or other hazard may cause a lead vehicle in a platoon to react and take action to avoid risks associated with the hazard.
- the lead vehicle reacting before the following vehicle often increases risks. For example, if the lead vehicle brakes before the following vehicle, in a worst case scenario, it is conceivable that the following vehicle may collide with the leading vehicle.
- Such problems caused by road obstacles or hazards are avoided or mitigated by (1) receiving data generated by one or more sensors arranged to interrogate a space radially extending from the lead vehicle as the lead vehicle travels over the road surface, (2) ascertaining a hazard caused by an object in the space from the data indicative of the perceived environment and (3) causing the following vehicle, while operating in the platoon, to take a preemptive action to avoid or mitigate risks resulting from the hazard caused by the object in the space, the preemptive action taken by the following vehicle prior to and/or without waiting for the lead vehicle taking any action in response to the object in the space. For example, by slowing the following vehicle before the lead vehicle, it has been the incidence of collision between the platooning vehicles is significantly reduced.
- present invention is directed to a boarder concept.
- present application is should be construed as addressing the general concept of using sensor data collected or generated by one vehicle in a platoon to control the operation of another vehicle in the platoon.
- the data is used by the receiving vehicle to avoid hazardous conditions or other risks.
- this is by no means a requirement.
- the data can be used by the receiving vehicle for just about any purpose.
- FIG. 8 a diagram 800 showing a platoon including a lead vehicle 802 and several following vehicle(s) 804 encountering a hazard, represented by an object 806 , while traveling across a road surface is illustrated.
- a gap 808 is provided and controlled between any pair of leading and following trucks as described in detail above.
- the lead vehicle 802 includes one or more sensors (not illustrated in FIG. 8 ) that are used to interrogate a space, designated by reference numeral 810 .
- the space 810 extends radially outward from the front of the vehicle 802 , encompassing the road ahead. It should be understood, however, that the particular direction and shape of the space 810 as depicted is by no means limiting. On the contrary, the space 810 in various embodiments can radiate outward from the front, side(s) rear, 360 degrees or any fraction thereof, around the lead vehicle 802 . Thus, the space 810 , which is interrogated by the aforementioned sensor(s), should be widely construed to cover any applicable shape or direction.
- the sensor(s) on the lead vehicle 802 generate data indicative of the perceived environment within the space 810 .
- a hazard caused by the presence of an obstacle such as object 806
- the object 806 represents a wide variety of potential obstacles, such as other vehicles (e.g., cars, trucks, motorcycles), pedestrians, a cyclist, road debris, traffic signs or posts along the side of the road, or just about any other possible obstruction that may be encountered while driving.
- the Applicant has found that with platooning vehicles in non-emergency situations, risks associated with hazards, such as created by an obstacle 806 , are often mitigated or altogether avoided by directing the following vehicle 804 to take a preemptive action prior and/or without waiting for the lead vehicle 802 to react to the obstacle. For example, if the platoon crests a hill on a highway and suddenly encounters stopped cars (e.g., objects 806 that represents a hazard) ahead on the highway, then the following vehicle 804 preferably brakes or takes some other preemptive action to slow down before the lead vehicle 802 slows down. By braking earlier, the rate at which following vehicle loses velocity is greater than the lead vehicle. As a result, the gap 808 between the two vehicles increases, potentially dissolving the platoon. The likelihood that the following vehicle 804 colliding with the leading vehicle 802 is therefore significantly reduced.
- stopped cars e.g., objects 806 that represents a hazard
- the processing of the data generated by the sensor(s) on the lead vehicle, indicative of the perceived environment within the space 810 may be performed either on the following vehicle 804 or the lead vehicle 802 . Two such embodiments are described below.
- FIGS. 9A-9C a set of block diagrams illustrating a first embodiment of a risk mitigation or avoidance system 900 is illustrated.
- the processing of the sensor data collected on the lead vehicle 802 is mostly performed by the following vehicle 804 .
- the lead vehicle 802 generates and collects the data from the sensor(s) and then transmits or relays the data in raw or generally non-processed form to the following vehicle 804 .
- the following vehicle 804 perceives from the data the environment in the space 810 ahead of the lead vehicle 802 , including the presence of an obstacle 806 that may represent a hazard. If a hazard is detected, one of a plurality of tiered severity threat levels is selected, depending on the severity of the hazard created by the obstacle 806 .
- the following vehicle then implements one or more preemptive actions, as dictated by the selected severity threat level, to avoid or mitigate the risks created by the object.
- FIG. 9B a block diagram of the modules provided in the lead vehicle 802 for generating, collecting and relaying the data to the following vehicle 804 is illustrated.
- the lead vehicle 802 includes one or more sensor(s) 902 , a platoon controller, such as the controllers 110 and/or 410 as described above, and the gateway 470 for transmitting or relaying the data to the following vehicle 804 .
- the sensor(s) 902 interrogate the space 810 , detecting any object(s) 806 .
- the data from the sensor(s) 902 which can be used to perceive the environment within the space 810 , is then transmitted to the following vehicle 804 via the gateway 470 .
- the senor(s) 902 may include one or more of a radar detection system, a Lidar or laser detection system, a camera or imaging system, a radio system, an automated braking system, an automated collision avoidance system, a GPS system, a cruise control system, or any other type of passive sensor (e.g., a sensor that does not transmit signals but rather is required to perform a measurement, such as a camera) or active sensors such similar radar, Lidar and/or ultrasound, or any combination thereof.
- the sensor(s) 902 also includes “sensors” that require some type of hardware on the senses object, such as ultra-wideband, where an antenna is needed on the sensed vehicle. As each of these types of sensor(s) and their use on vehicles is well known, a further description is not provided herein for the sake of brevity.
- the sensors 902 do not necessarily have to be physically provided on the lead vehicle 802 .
- the sensors 902 can also be various types of road-side sensors, such as but not limited to a camera, a traffic speed monitor or camera, a precipitation monitor, a temperature monitor, a wind sensor, a humidity sensor, a traffic monitoring sensor, or an in-ground sensor.
- road-side sensors such as but not limited to a camera, a traffic speed monitor or camera, a precipitation monitor, a temperature monitor, a wind sensor, a humidity sensor, a traffic monitoring sensor, or an in-ground sensor.
- the term “sensor” as used herein should be broadly construed and is intended to mean both sensors on-board a vehicle, road-side sensors, or possibly a combination of both.
- the following vehicle 804 includes a gateway 470 for receiving the data transmitted by lead vehicle 802 , a threat level determination module 904 , an action implementation module 906 , platoon controller 110 and/or 410 , and optionally a machine learning module 908 .
- the platoon controller 110 and/or 410 on the following vehicle 804 operates to maintain the gap 808 with the lead vehicle.
- the module 904 processes the data received over the gateway 470 . From the data, the module 904 can perceive the environment in the space 810 ahead of the lead truck 802 and ascertain any possible hazards created by one or more objects 806 that may be detected.
- the module 904 may select one of a plurality of tiered severity threat level thresholds or thresholds, each defining one or more corresponding preemptive action(s) respectively. In other words, the module 904 selects an appropriate one of the tiered threat levels commensurate with the severity of the threat represented by a perceived object 806 .
- the action implementation module 906 operates in cooperation with the threat level determination module 904 .
- the module 906 is responsible for implementing specific preemptive action(s) that correspond to the selected severity threat level, as determined by the module 904 , to mitigate or avoid the risks resulting from the object 806 in the space 810 .
- Such preemptive action(s) may include, but are not limited to, broad categories such warnings and/or alerts, certain precautionary preparations in anticipation of a possible collision, and other specific actions.
- machine learning module 908 operates in cooperation with the threat level determination module 904 to identify objects 806 and ascertain the threat level they may represent.
- Machine learning module 908 provides the ability to predict, learn and identify particular object(s) 806 that may be perceived in the field 810 .
- module 908 may rely on image or pattern recognition and computational learning, artificial intelligence, along with data analytics and algorithms, to distinguish different types of objects (e.g., cars, buses, trucks, pedestrians, etc., and the particulars regarding each).
- learning module 908 may be able to differentiate one type of vehicle versus another, whether or not a vehicle is moving or stationary (e.g., stalled on the road or moving), the direction a vehicle is travelling from the color of detected lights (e.g., white light from headlights indicates the vehicle is traveling in the oncoming direction, whereas red or brake lights indicates the vehicle is traveling in the same direction), road debris, pedestrians, etc.
- the level determination module 904 can make a more accurate assessment of the perceived threat. If the object ahead is identified as a pedestrian, then the selected threat level is likely to be at an emergency level, meaning immediate preemptive action is required to avoiding running over the person.
- the selected threat level will likely be pre-warning or a non-emergency (i.e., a low threat), and the preemptive action will likely be a mere warning.
- FIGS. 10A-10C a set of block diagrams illustrating a second embodiment of a risk mitigation or avoidance system 1000 is illustrated.
- the processing of the sensor data collected on the lead vehicle 802 is mostly performed by the following vehicle 804 .
- the lead vehicle 802 is responsible for (1) generating the data from the one or more sensor(s) 902 , (2) perceiving if the environment in space 810 ahead of lead vehicle 802 includes any object(s) 806 , (3) ascertaining any threat created by the object(s) 806 and (4) selecting an appropriate tiered threat level threshold that is commensurate with the severity of the threat represented by an object(s) 806 .
- the lead vehicle 802 generates and sends coded commands to the following vehicle 804 that are indicative of the preemptive actions to be taken as dictated by the selected severity level.
- FIG. 10B illustrates the modules for generating and processing the data from the sensor(s) 902 on the leading vehicle 802 .
- the lead vehicle 802 includes sensor(s) 902 , threat level detection module 904 , platoon controller 110 and/or 410 , optionally machine learning module 908 , and gateway 470 .
- the leading vehicle 802 includes an encoder module 910 , which is responsible for encoding any preemptive action(s) defined by the module 904 .
- the gateway 470 then transmits the encoded command signal(s) to the following vehicle 804 .
- FIG. 10C illustrates the modules for receiving and processing the command(s) on the following vehicle 804 .
- the modules include gateway 407 for receiving the command(s), a platoon controller 110 and/or 410 , a decoder 912 , and action implementation module 906 .
- the received command(s) are decoded by module 912 and provided to the module 906 .
- module 906 implements the defined preemptive action.
- the threat level detection module 904 is responsible for selecting one of a plurality of tiered threat levels or thresholds depending on the severity of the perceive threat.
- a non-exclusive embodiment with four tiers is described below.
- the number of tiers may significantly vary from a few too many As such, the specific tiers and the corresponding preemptive actions as discussed below are exemplary and should not be construed as limiting in any regard.
- the four severity levels include:
- the table also includes three columns, each defining a category of preemptive actions.
- the three categories in this example include:
- corresponding preemptive actions for each of the three categories are listed.
- the corresponding preemptive actions for each category include:
- Warning(s)/Alert(s) flashing or operating warning lights on the following vehicle, operating a horn on the following vehicle, operating visual warnings on the following vehicle, operating haptic actuators on the following vehicle and/or manipulating a radio on the following vehicle.
- Safety Preparations for braking (e.g., pre-pressurizing pneumatic brakes), and/or pre-tensioning seat belt(s).
- the checkmarks indicate which category of preemptive action is available for each severity level threshold in accordance with this embodiment. Specifically:
- Warnings/Alerts and Safety Preparations are available.
- the threat level determination module 904 may select any one or combination of preemptive actions available in a given category once a threat severity level is defined. Typically, all of the preemptive actions in a given category will not be selected. However, in certain circumstances, they all may be selected. It suffices to say that the module 904 has the ability to pick and chose the preemptive actions in a given category on a case-by-case basis, depending on the totality of the circumstances represented by a given threat.
- a flow chart 1300 illustrating operational steps of a non-exclusive embodiment of the risk mitigation or avoidance system 900 / 1000 is illustrated.
- the preemptive action(s) taken by the following vehicle for each tier include:
- the platoon controller 110 / 410 of two (or more) vehicles coordinate to establish a platoon as described herein.
- step 1304 the one or more sensor(s) 902 on the lead vehicle interrogate the space 810 .
- step 1304 the environment in space 810 , as perceived by processing the data generated by the sensor(s) 902 , is analyzed.
- the data can be processed by either the following vehicle 804 , the lead 802 vehicle or even possibly by a combination of both (or more vehicles) in the platoon.
- decision 1308 a determination is made if there is a perceived hazard or not.
- steps 1302 through 1306 are continually repeated so long as the platoon is maintained.
- the threat level determination module 904 selects the appropriate tiered severity threat level commensurate with the perceived threat.
- the severity levels include low ( 1310 ), moderate ( 1312 ), high ( 1314 ) and emergency ( 1316 ).
- module 904 defines the appropriate warnings and/or alerts in step 1318 and the action implementation module 906 implements those warnings and/or alerts in step 1320 in the lead vehicle 802 and/or the following vehicle 804 .
- the modules 904 and 906 cooperate to control the velocity of the platooning vehicles (i.e., reduce the velocity of the following vehicle(s)) relative to the lead vehicle for the purpose of increasing the gap as provided in steps 1322 and 1324 respectively.
- the modules 904 and 906 cooperate to dissolve the platoon in a controlled manner as provided in step 1326 .
- the relative velocity of the following vehicle is reduced, allowing the gap 808 to grow until the platoon is dissolved.
- the modules 904 and 906 cooperate to first hard brake the following vehicle(s) in step 1328 and then dissolve the platoon in step 1330 . If multiple following vehicles 804 are involved, it is preferred that the timing of the hard braking occur in sequence, starting from the last vehicle to the lead vehicle.
- control is returned to decision 1308 . If the perceived hazard remains, then one of the security levels 1310 - 1316 , and their subsequent actions, is performed until the threat is no longer present and/or the platoon is dissolved. If the threat is no longer present, then control is returned to step 1302 , and normal platooning proceeds. If the platoon was dissolved as a result of a preemptive action, then the vehicles may decide to re-engage as described above once the threat has passed.
- the sensor(s) 902 on the lead vehicle are radar detectors capable of detecting or ascertaining the size and relative velocity of object(s) 806 in space 810 .
- the threat level determination module optionally along with machine learning module 908 , can identify object(s) 806 and the threat they may represent.
- the present invention is not limited to using radar sensors.
- radar can be used in cooperation with cameras. The radar can be used to identify the size and relative velocity of object(s) 806 with respect to the lead vehicle, whereas images of the object(s) 806 can be used by learning module 908 to precisely identify the objects.
- Scenario One In this example, a car enters onto a freeway via an on ramp 50 meters ahead of a platoon of vehicles. Both the entering car and the platoon are traveling at approximately the same highway speed. Since 50 meters is generally considered a safe distance, and all involved vehicles are traveling at approximately the same speed, any perceived threat will be low. As a result, simply warning and/or alerting the platoon drivers and any other surrounding drivers, is an adequate response commensurate with the relatively low threat. As a result, the warnings alerts, such flashing warning lights, vibrating the seats of the platooning drivers, setting off an audio warning, are typically sufficient preemptive actions.
- Scenario Two In this scenario, the same car enters the freeway 50 meters ahead of the platoon. However, rather than traveling at highway speed, the car is traveling only at 45 mph, or approximately 20 mph slower than the platoon. As a result, the severity level is moderate, meaning a collision is not imminent, but the lead vehicle of the platoon should react (e.g., switch lanes and/or brake) action to avoid a possible collision. In this situation, the gap is increased without dissolving the platoon. For example, the gap can be increased from a normal operating condition of 12 meters to 24 meters by reducing the velocity of the following vehicle(s). As the relative velocity of the following vehicle is reduced and the gap grows, the lead vehicle can then take precautionary action to avoid the car ahead.
- the gap can be increased from a normal operating condition of 12 meters to 24 meters by reducing the velocity of the following vehicle(s). As the relative velocity of the following vehicle is reduced and the gap grows, the lead vehicle can then take precautionary action to avoid the car ahead.
- platoon controllers 110 / 410 on the following vehicle can increase relative speed to reduce the gap to a normal operating distance (e.g., 12 meters).
- Scenario Three A car abruptly cuts off the platoon entering space 810 immediately ahead of the lead vehicle.
- the platoon is now dangerously tail-gating the car ahead, which represents a high security threat if the car ahead suddenly brakes.
- the system acts to dissolve the platoon, again by first braking or otherwise reducing the velocity of the following vehicle(s) versus the lead vehicle. Once the velocity of the following vehicle(s) is reduced, then the lead vehicle can brake or otherwise reduce its velocity. Since the following vehicle started reducing its velocity sooner, it will slow down quicker relative to the lead vehicle. As a result, the gap will widen until the platoon is dissolved.
- Scenario Four A platoon crests a hill on a freeway and immediately sees stalled cars ahead and quick braking is required to avoid a collision.
- the following vehicle immediately initiates hard braking (e.g., a Brake Now command), reducing its relative velocity with respect to the lead vehicle and growing the gap and dissolving the platoon.
- hard braking e.g., a Brake Now command
- the lead vehicle can brake and take other preemptive steps to reduce its velocity.
- the gap will increase as the two vehicles reduce their velocity.
- the relative velocity between the two vehicles can also be precisely controlled when either widening or dissolving the gap.
- the rate of velocity reduction of the following vehicle may range from ( ⁇ 0.1 to ⁇ 2.0) meters per second relative to the lead vehicle.
- the velocity reduction per vehicle can be successively incremented depending on vehicle position in the platoon.
- the velocity rate reduction for the second, third and fourth vehicles can be incremented ( ⁇ 0.2, ⁇ 0.4 and ⁇ 0.6) meters per second respectively.
- any number of severity threat levels or thresholds may be used and the number, type and/or specific preemptive actions per category may widely vary.
- the vehicles involved platooning and/or and risk mitigation or avoidance can be autonomous, semi-autonomous, or driven by a driver, or any combination thereof.
- Pre-cognitive braking is one particular pre-emptive action that can be used to mitigate or avoid risks due to hazards encountered by platooning vehicles.
- pre-cognitive braking when a lead vehicle 802 issues a brake command, the following vehicle(s) 804 is/are immediately informed, so that the following vehicle(s) 804 can take preemptive action, preferably before a change in speed of the front vehicle 802 occurs.
- a pair of vehicles 802 , 804 operating in a platoon with a gap 808 is illustrated.
- the lead vehicle 802 initiates a braking command
- the braking action can be implemented or may result in a number of ways, such as but not limited to, the driver braking (i.e., pushing the brake pedal), an active cruise control system (ACC) initiating a braking action, or some other automated driving unit initiating the braking action.
- ACC active cruise control system
- a braking notice 1402 of the braking command is transmitted by the lead vehicle 802 to the following vehicle 804 .
- the following vehicle 804 aware of the braking event, the braking action of the two vehicles can be coordinated, avoiding or mitigating risks.
- the notice information associated with the braking event 1402 sent from the lead vehicle 802 to the following vehicle 804 may widely vary.
- the relayed information may include a simple brake command to more detailed information, such as brake application pressure, brake air supply reservoir pressure, engine torque, engine speed or RPMs, compression (Jake) brake application, accelerator pedal position, engine manifold air pressure (MAP), computed delivery torque, vehicle speed, system faults, battery voltage, radar or lidar data, or any combination thereof.
- brake application pressure brake air supply reservoir pressure
- engine torque engine speed or RPMs
- compression (Jake) brake application compression (Jake) brake application
- accelerator pedal position accelerator pedal position
- engine manifold air pressure (MAP) engine manifold air pressure
- computed delivery torque vehicle speed, system faults, battery voltage, radar or lidar data, or any combination thereof.
- braking information is prioritized over types of non-critical information.
- the information pertaining to the braking event 1402 as relayed via a data link established by the gateways 470 of the lead vehicle 802 and the following vehicle 804 .
- the data link may be implemented using WiFi, one or more designated radio channels, Zigbee or any industry or agreed upon standard radio.
- WiFi Wireless Fidelity
- Zigbee any industry or agreed upon standard radio.
- Any reliable, low latency data link may be used, having for instance, a latency of 10 milliseconds or less.
- Pre-cognitive braking involves, as referred to above, the coordinated braking action between the lead vehicle 802 and the following vehicle 804 .
- the coordinated action involves initiating the braking of the following vehicle 804 before the lead vehicle. In this way, the gap between the two vehicles grows and the two (or more vehicles) may each brake in a controlled, safe manner
- FIG. 15 a diagram 1500 that plots the distance “D” of the gap 808 between the two vehicles over time while platooning is illustrated.
- the gap distance D Prior to a braking event by the lead vehicle 802 , designated by 1502 in the plot, the gap distance D remains fairly constant, fluctuating only slightly as corrective action is taken by the vehicles to maintain the desired gap.
- the braking action 1502 occurs, the following vehicle 804 is immediately notified via the data link.
- the braking of the two vehicles is coordinated such that the following vehicle 804 brakes (i.e., slows down) first before the lead vehicle 802 .
- the gap grows as illustrated by the rise in the plot 808 after braking is initiated.
- the braking behavior of the two vehicles can be controlled in a variety of ways. For instance, the two vehicles can begin braking at substantially the same time, but with the following vehicle braking harder than the lead vehicle. As a result, the rate at which the gap grows over time is increased as the following vehicle reduces its speed at a quicker rate. This is just one possible alternative. Many other braking strategies, as discussed in more detail below, may be used.
- FIG. 16 a flow chart 1600 illustrating the steps of pre-cognitive braking are illustrated.
- a braking event is monitored at the lead vehicle 802 to determine if a braking event has occurred.
- a braking event may be detected in a number of ways and is not necessarily limited to the driver pushing the brake pedal.
- the braking event can be triggered by an active cruise control system (ACC) or some other automated driving unit initiating the braking action.
- ACC active cruise control system
- a notice of the detected braking event is communicated to the following vehicle 804 .
- the communication may take place over the communication link established between the gateways 407 of the two vehicles.
- the communication includes a brake command along with possibly other information, such as brake application pressure, brake air supply reservoir pressure, engine torque, engine speed or RPMs, compression (Jake) brake application, accelerator pedal position, engine manifold air pressure (MAP), computed delivery torque, vehicle speed, system faults, battery voltage, radar or lidar data, or any combination thereof.
- the following vehicle may implement a number of braking strategies. For instance, the braking at following vehicle may be timed to occur a few moments before the braking action of the lead vehicle. Alternatively, or in addition, the following vehicle may be controlled to reduce vehicle speed at a controlled rate that is more significant than the lead vehicle. As a result, the gap will widen as the two vehicles reduce their speed.
- Heavy vehicles such as trucks or busses, typically rely on pneumatic or air brakes.
- These types of brakes use compressed air in a chamber, pressing on a piston, to apply pressure on to a brake pad that is used to brake or stop the vehicle.
- the driver When braking while driving, the driver typically pushes the brake pedal, which forces air under pressure into the chamber, causing the piston to apply pressure to the brake, slowing the vehicle.
- pneumatic brakes the braking action may be delayed until there is adequate air pressure in the chamber.
- the following vehicle 804 may in response to a received braking notice 1402 begin to immediately pressurize its brake chamber(s) ahead of and/or more aggressively than the lead vehicle 802 . As a result, the brakes may be applied by the following vehicle 804 before the lead vehicle 802 .
- one or any combination of the above-listed parameters may be used to formulate a braking strategy for the following vehicle 804 .
- the rate of braking of the following vehicle 804 can be calculated relative to the lead vehicle 802 .
- the velocity reduction of the following vehicle 804 may be controlled to be ( ⁇ 0.1 to ⁇ 2.0) meters per second relative to the lead vehicle 802 .
- step 1608 the braking, including the use of any particular braking strategy, occurs with the following vehicle.
- step 1610 the braking, including the use of any particular braking strategy, occurs with the lead vehicle after braking is initiated with the following vehicle in the previous step.
- the type of vehicles that may be used for platooning and/or risk mitigation or avoidance may widely vary and are not limited to exclusively trucks.
- the present invention contemplates that any vehicle class or type may be used, regardless if powered by a combustion engine, electric motor, fuel cells, or any other possible self-propulsion mechanism, including cars, trucks, buses, motorcycles, or any other self-propelled vehicle that is currently or may be developed in the future.
Landscapes
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Mechanical Engineering (AREA)
- Transportation (AREA)
- Combustion & Propulsion (AREA)
- Chemical & Material Sciences (AREA)
- Radar, Positioning & Navigation (AREA)
- Aviation & Aerospace Engineering (AREA)
- Remote Sensing (AREA)
- Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Human Computer Interaction (AREA)
- Control Of Driving Devices And Active Controlling Of Vehicle (AREA)
- Traffic Control Systems (AREA)
- Business, Economics & Management (AREA)
- Artificial Intelligence (AREA)
- Evolutionary Computation (AREA)
- Game Theory and Decision Science (AREA)
- Control Of Position, Course, Altitude, Or Attitude Of Moving Bodies (AREA)
Abstract
Description
- This application claims priority of U.S. Provisional Application No. 62/638,794, filed on Mar. 5, 2018. This Application is also a Continuation-in-Part of U.S. application Ser. No. 15/589,124, filed on May 8, 2017, which is a Continuation of U.S. application Ser. No. 14/855,044, filed Sep. 15, 2015 (now U.S. Pat. No. 9,645,579, issued May 9, 2017), which is a 371 of International Application No. PCT/US2014/030770, filed on Mar. 17, 2014, which claims priority of U.S. Provisional Application No. 61/792,304, filed Mar. 15, 2013. This application is also a Continuation-in-Part of U.S. application Ser. No. 15/607,902, filed on May 30, 2017 which claims priority of U.S. Provisional Application Nos.: 62/343,819, filed May 31, 2016; 62/363,192, filed Jul. 15, 2016; and 62/377,970, filed on Aug. 22, 2016. All of the aforementioned priority applications are incorporated herein by reference in their entirety for all purposes.
- The present application relates generally to controllers, architectures, methods and systems for enabling vehicles to closely follow one another safely using automatic or partially automatic control, and more particularly, to a system and method for mitigating or avoiding risks due to hazards encountered by connected vehicles operating in a platoon.
- In recent years significant strides have been made in the field of automated vehicle control. One segment of vehicle automation relates to vehicular convoying systems that enable vehicles to follow closely together in a safe, efficient and convenient manner Following closely behind another vehicle has the potential for significant fuel savings benefits, but is generally unsafe when done manually by the driver. Known vehicle convoying systems, often interchangeable referred to as “platooning” or “connected vehicles”, calls for one or more following vehicle(s) closely following a lead vehicle in an automatic or semi-automatically controlled manner.
- The fuel efficiency advantages of platooning connected vehicles is particularly noticeable in fields such as the trucking industry in which long distances tend to be traveled at highway speeds. One of the on-going challenges of vehicle platooning and convoying systems is creating controller systems architectures that effectively maintain a gap between vehicles while meeting stringent safety standards as required for integration of connected vehicles into mainstream road vehicles.
- Maintaining road safety and avoiding collisions due to hazards encountered on the road is also very important with platooning. Although the platooning of connected vehicles has a very good safety record, there is always a need for improvement.
- A system and method for mitigating or avoiding risks due to hazards encountered by platooning vehicles is therefore needed.
- A system and method for mitigating or avoiding risks due to hazards encountered by connected vehicles operating in a platoon is described. The system and method involve operating a following vehicle in a platoon behind a lead vehicle, receiving data generated by one or more sensors arranged to interrogate a space radially extending from the lead vehicle as the lead vehicle travels over the road surface, ascertaining a hazard caused by an object in the space, and causing the following vehicle to take a preemptive action to avoid or mitigate the hazard caused by the object in the space, the preemptive action taken by the following vehicle prior to the lead vehicle taking any action in response to the hazard caused by the object.
- In one non-exclusive embodiment, a plurality of tiered severity threat levels is defined, each level having one or more corresponding preemptive action(s) respectively. When a threat is perceived, one of the tiered severity threat levels commensurate with the threat is selected. The corresponding one or more preemptive action(s) is/are then implemented by the following vehicle to mitigate or avoid the risks associated with the object. In one particular non-exclusive embodiment, the tiered threat levels include low, moderate, high and emergency.
- In yet another non-exclusive embodiment, one of the preemptive actions may involve increasing the gap between the two vehicles by decreasing the relative velocity of the following vehicle(s) prior to taking any preemptive action by the lead vehicle. By reducing the relative velocity of the following vehicle first, the gap between the vehicles will grow.
- In yet other alternative embodiments, the gap can be increase while either maintaining or dissolving the platoon. In either case, a normal operating gap may be reestablished once the perceived threat has passed.
- In yet another embodiment, raw data collected by the one or more sensors, on the lead vehicle, is transmitted by the lead vehicle to the following vehicle. In response, the following vehicle is responsible for perceiving the environment within the space radially extending from the lead vehicle, ascertaining the hazard caused by the object in the space, and taking a preemptive action prior to and/or without waiting for the lead vehicle taking any preemptive action.
- In an alternative to the above embodiment, the lead vehicle is responsible for perceiving the environment in the space, ascertaining the hazard level, and then transmitting one or more coded commands, each indicative or a preemptive action, to the following vehicle. In response, the following vehicle interprets the commands and implements the preemptive action(s) prior to the lead vehicle taking any preemptive action.
- In yet other embodiments, pre-cognitive braking is implemented with platooning vehicles. A notice is sent to the following vehicle by the lead vehicle in response to a braking event by the lead vehicle. In response to the notice, the following vehicle initiates a braking before the lead vehicle, resulting in an increase of a gap maintained between the two vehicles.
- In yet other embodiments, a system operating onboard a vehicle is configured to receive data from one or more sensors external to the vehicle that are arranged to sense a driving condition in the vicinity of the vehicle. In response, the system is arranged to make a decision or take an action at least in part based on the received data.
- The invention and the advantages thereof, may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:
-
FIG. 1 is a block diagram of a controller architecture suitable for use in an automated or partially automated vehicle control system that supports platooning. -
FIG. 2 is a block diagram of a representative platoon controller architecture suitable for use in the automated or partially automated vehicle control system ofFIG. 1 . -
FIG. 3 is a block diagram of a gap controller in accordance with one embodiment. -
FIGS. 4A-4C are a series of diagrams illustrating different control states used by a gap regulator in accordance with one embodiment during different operational states. -
FIG. 5 is a state space diagram illustrating a sliding mode control scheme. -
FIG. 6 is a specific ASIL compliant controller hardware architecture suitable for use in an automated or partially automated vehicle control system that supports platooning. -
FIG. 7 illustrates components of a gateway in accordance with one embodiment. -
FIG. 8 is a diagram showing a lead vehicle and several following vehicle(s) encountering a hazard represented by an object while traveling across a road surface. -
FIGS. 9A-9C are a set of block diagrams illustrating a non-exclusive embodiment of a system for mitigating or avoiding risks due to hazards encountered by connected vehicles in accordance with the present invention. -
FIGS. 10A-10C are another set of block diagrams illustrating another non-exclusive embodiment of a system for mitigating or avoiding risks due to hazards encountered by connected vehicles in accordance with the present invention. -
FIG. 11 illustrates an illustrative plurality of tiered severity threat levels each having one or more corresponding preemptive action(s) in accordance with a non-exclusive embodiment of the present invention. -
FIG. 12 illustrates several categories of preemptive actions in accordance with a non-exclusive embodiment of the present invention. -
FIG. 13 illustrates a flow chart illustrating operational steps in accordance with a non-exclusive embodiment of the present invention. -
FIG. 14 illustrates two vehicles operating in a platoon in accordance with the present invention. -
FIG. 15 illustrates a plot showing a gap between two platooning vehicles during pre-cognitive braking in accordance with a non-exclusive embodiment of the invention. -
FIG. 16 illustrates a flow chart detailing steps for implementing pre-cognitive braking in accordance with the a non-exclusive embodiment of the invention. - The present invention will now be described in detail with reference to several embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention, including the description of a plurality of different aspects of the invention, including, in some case, one or more alternatives. It will be apparent to those skilled in the art that the invention can be practice without implementing all of the features disclosed herein.
- The Applicant has proposed various vehicle platooning systems in which a second, and potentially additional, vehicle(s) is/are automatically, or semi-automatically controlled to closely follow a lead vehicle in a safe manner By way of example, U.S. application Ser. Nos. 15/605,456, 15/607,902; 13/542,622 and 13/542,627; U.S. Provisional Application Nos. 62/377,970 and 62/343,819; and PCT Application Nos. PCT/US2014/030770, PCT/US2016/049143 and PCT/US2016/060167 describe various vehicle platooning systems in which a trailing vehicle is at least partially automatically controlled to closely follow a designated lead vehicle. Each of these earlier applications is incorporated herein by reference.
- One of the goals of platooning is typically to maintain a desired longitudinal distance between the platooning vehicles, which is frequently referred to herein as the “desired gap”. That is, it is desirable for the trailing vehicle (e.g., a trailing truck) to maintain a designated gap relative to a specific vehicle (e.g., a lead truck). The vehicles involved in a platoon will typically have sophisticated control systems suitable for initiating a platoon, maintaining the gap under a wide variety of different driving conditions, and gracefully dissolving the platoon as appropriate.
- The architecture and design of control systems suitable for implementing vehicle platooning may vary widely. The specific controller design can vary based on the level of automation contemplated for the controller, as well as the nature of and equipment available on the host vehicles participating in the platoon. By way of example,
FIG. 1 diagrammatically illustrates a vehicle control architecture that is suitable for use with platooning tractor-trailer trucks. The specific controller illustrated is primarily designed for use in conjunction with a platooning system in which both vehicles include an active driver. The driver of the lead vehicle being fully responsible for control of the front vehicle. The a driver of the trailing vehicle is responsible for steering the trailing vehicle, but theplatoon controller 110 is primarily responsible for controlling the engine torque and braking requests of the following vehicle during active platooning. However, it should be appreciated that generally similar control schemes can be used in systems which contemplate more automated control of one or both of the platoon partners. - In the illustrated embodiment illustrated in
FIG. 1 , aplatoon controller 110, receives inputs from a number ofsensors 130 on the tractor and/or one or more trailers or other connected units, and a number of actuators andactuator controllers 150 arranged to control operation of the tractor's powertrain and other vehicle systems. Anactuator interface 160 may be provided to facilitate communications between theplatoon controller 110 and theactuator controllers 150. - The
platoon controller 110 also interacts with aninter-vehicle communications controller 170 which orchestrates communications with the platoon partner and a Network Operations Center (NOC)communications controller 180 that orchestrates communications with a NOC. The vehicle also preferably has selectedconfiguration files 190 that include known information about the vehicle. - Some of the functional components of the
platoon controller 110 includegap controller 112, a variety ofestimators 114, one or morepartner vehicle trackers 116 andvarious monitors 118. In many applications, theplatoon controller 110 will include a variety ofother components 119 as well. Exemplary embodiments of theplatoon controller 110 andgap controller 112 are described in more detail below with reference toFIGS. 2 and 3 . - Some of the sensors utilized by the
platoon controller 110 may include GNSS (GPS)unit 131,wheel speed sensors 132,inertial measurement devices 134,radar unit 137,LIDAR unit 138,cameras 139, acceleratorpedal position sensor 141, steeringwheel position sensor 142, brakepedal position sensor 143, andvarious accelerometers 144. Of course, not all of these sensors will be available on all vehicles involved in a platoon and not all of these sensors are required in any particular embodiment. A variety of other sensor 149 (now existing or later developed or commercially deployed) may be additionally or alternatively be utilized by the platoon controller in other embodiments. In the primary embodiments described herein, GPS position data is used. However, GPS is just one of the currently available global navigation satellite systems (GNSS). Therefore, it should be appreciated that data from any other GNSS system or from other suitable position sensing systems may be used in place of, or in addition to, the GPS system. - Many (but not all) of the described sensors, including wheel speed sensors, 132,
radar unit 137, acceleratorpedal position sensor 141, steeringwheel position sensor 142, brakepedal position sensor 143, andaccelerometer 144 are relatively standard equipment on newer trucks (tractors) used to pull semi-trailers. However, others, such as theGNSS unit 131 and LIDAR unit 138 (if used) are not currently standard equipment on such tractors or may not be present on a particular vehicle and may be installed as needed or desired to help support platooning. - Some of the
vehicle actuators controllers 150 that the platoon controller may direct at least in part include engine torque controller 152 (which is often part of the integrated functionality of an engine control unit (ECU) or powertrain control module (PCM)),transmission controller 154,brake controller 156, steering controller 157 (when automated steering is provided); andclutch controller 158. Of course, not all of these actuator controllers will be available or are required in any particular embodiment and it may be desirable to interface with a variety of othervehicle actuator controllers 159 that may be available on the controlled vehicle as well. Therefore, it should be appreciated that thespecific actuator controllers 150 directed or otherwise utilized by the platoon controller on any particular controlled vehicle may vary widely. Further, the capabilities of any particular actuator controller (e.g. engine torque controller 152), as well as its interface (e.g., the nature and format of the commands, instructions, requests and messages it can handle or generate) will often vary with the make and model of that particular actuator controller. Therefore, anactuator interface 160 is preferably provided to translate requests, commands, messages and instructions from theplatoon controller 110 into formats that are appropriate for the specific actuator controller hardware and software utilized on the controlled vehicle. Theactuator interface 160 also provides a mechanism for communicating/translating messages, commands, instructions and requests received from the various actuator controllers back to theplatoon controller 110. Typically an appropriate actuator interface would be provided to interact with each of the specific vehicle controllers utilized. In various embodiments, this may include one or more of anengine torque interface 161, abrake interface 162, atransmission interface 164, a retarder interface 165 (if a separate retarder controller is used), asteering interface 167, and/or any otherappropriate controller interface 169. - Large trucks and other heavy vehicles frequently have multiple systems for “braking” the truck. These include the traditional brake system assemblies mounted in the wheels of the vehicle—which are often referred to in the industry as the “foundation brakes.” Most large trucks/heavy vehicles also have a mechanism referred to as a “retarder” that is used to augment the foundation brakes and serve as an alternative mechanism for slowing the vehicle or to help prevent the vehicle from accelerating down a hill. Often, the retarder will be controlled by the
engine torque controller 152 and in such embodiments, the retarder can be controlled by sending appropriate torque commands (which may be negative) to theengine torque controller 152. In other embodiments a separate retarder controller (not shown) may be accessible to, and therefore directed by,platoon controller 110 through anappropriate retarder interface 165. In still other embodiments, theplatoon controller 110 may separately determine a retard command that it sends to theactuator interface 160. In such embodiments the actuator interface will interpret the retard command and pass on appropriate retardation control commands to the ECU or other appropriate vehicle controller. - The communications between vehicles may be directed over any suitable channel and may be coordinated by
inter-vehicle communications controller 170. By way of example, the Dedicated Short Range Communications (DSRC) protocol (e.g. the IEEE 802.11p protocol), which is a two-way short to medium range wireless communications technology that has been developed for vehicle to vehicle communications, works well. Of course other communications protocols and channels may be used in addition to or in place of a DSRC link. For example, the inter vehicle communications may additionally or alternatively be transmitted over a cellular communications channel such as 4G LTE Direct, 5G, a Citizen's Band (CB) Radio channel, one or more General Mobile Radio Service (GMRS) bands, and one or more Family Radio Service (FRS) bands or any other now existing or later developed communications channels using any suitable communication protocol. - In various embodiments, the transmitted information may include the current commands generated by the
platoon controller 110 such as requested/commanded engine torque 280, requested/commanded braking deceleration 282. They may also include steering commands, gear commands, etc. when those aspects are controlled byplatoon controller 110. Corresponding information is received from the partner vehicle, regardless of whether those commands are generated by a platoon controller or other suitable controller on the partner vehicle (e.g., an adaptive cruise control system (ACC) or a collision mitigation system (CMS)), or through other or more traditional mechanisms—as for example, in response to driver inputs (e.g., accelerator pedal position, brake position, steering wheel position, etc.). - In many embodiments, much or all of the tractor sensor information provided to
platoon controller 110 is also transmitted to the platoon partner and corresponding information is received from the platoon partner so that theplatoon controllers 110 on each vehicle can develop an accurate model of what the partner vehicle is doing. The same is true for any other relevant information that is provided to the platoon controller, including anyvehicle configuration information 190 that is relevant to the platoon controller. It should be appreciated that the specific information transmitted may vary widely based on the requirements of theplatoon controllers 110, the sensors and actuators available on the respective vehicles, and the specific knowledge that each vehicle may have about itself. - The information transmitted between vehicles may also include information about intended future actions. For example, if the lead vehicle knows it approaching a hill, it may expect to increase its torque request (or decrease its torque request in the context of a downhill) in the near future and that information can be conveyed to a trailing vehicle for use as appropriate by the
platoon controller 110. Of course, there is a wide variety of other information that can be used to foresee future torque or braking requests and that information can be conveyed in a variety of different forms. In some embodiments, the nature of the expected events themselves can be indicated (e.g., a hill, or curve or exit is approaching) together with the expected timing of such events. In other embodiments, the intended future actions can be reported in the context of expected control commands such as the expected torques and/or other control parameters and the timing at which such changes are expected. Of course, there are a wide variety of different types of expected events that may be relevant to the platoon control. - The communications between the vehicles and the NOC may be transmitted over a variety of different networks, such as the cellular network, various Wi-Fi networks, satellite communications networks and/or any of a variety of other networks as appropriate. The communications with the NOC may be coordinated by
NOC communications controller 180. The information transmitted to and/or received from the NOC may vary widely based on the overall system design. In some circumstances, the NOC may provide specific control parameters such as a target gap tolerance. These control parameters or constraints may be based on factors known at the NOC such as speed limits, the nature of the road/terrain (e.g., hilly vs. flat, winding vs. straight, etc.) weather conditions, traffic or road conditions, etc. In other circumstances the NOC may provide information such information to the platoon controller. The NOC may also provide information about the partner vehicle including its configuration information and any known relevant information about its current operational state such as weight, trailer length, etc. - The
configuration file 190 may include a wide variety of information about the host vehicle that may be considered relevant to the controller. By way of example, some of the information might include the vehicle's specification including such things as engine performance characteristics, available sensors, the nature of its braking system, the location of its GNSS antenna relative to the front of the cab, gear ratios, differential ratios etc. -
FIG. 2 illustrates a particular embodiment of aplatoon controller 110. In the illustrated embodiment, theplatoon controller 110 includes agap controller 112, a plurality ofestimators 114, one ormore trackers 116, any desiredmonitors 118 and potentially any of a variety ofother components 119. - In the illustrated embodiment, the
gap controller 112 includes a target andstate setter 200, agap regulator 210 and agap estimator 240. In general, the target andstate setter 200 is arranged to determine the intended operational mode (state) of thegap regulator 210 and the values of any variable control parameters that are appropriate for use in that operational mode. - The
gap regulator 210 is arranged to control the trailing platoon partner in the manner designated by the target andstate setter 200. In the gap control operational mode, thegap regulator 210 controls the vehicle in a manner that seeks to attain and maintain the desired gap in accordance with any designated control parameters specified by thestate setter 200. In other modes, thegap regulator 210 controls the vehicle in a manner that seeks to attain the appropriate response for the selected operational mode. - The
gap estimator 240 is arranged to estimate/determine the current gap based on actual measurements and/or other information that is available to theplatoon controller 110. It should be apparent that an accurate understanding of the current gap is important to successful operation of the gap regulator. At the same time, it should be appreciated that any measurement system has inherent tolerances and can be subject to reporting errors and/or may become unavailable in some circumstances. Thus, thegap estimator 240 is configured to receive information from multiple position or relative position related sensors and to fuse such data into a reliable estimate of the current gap. - The torque and braking requests generated by
GAP regulator 210 are sent to the appropriate actuator interface (e.g.,engine torque interface 161 andbrake interface 162 respectively). Theengine torque interface 161 then forwards an appropriate torque command toengine torque controller 152 which directs the delivery of the requested torque by directing various engine operating parameters such as fuel charge, valve timing, retarder state, etc. appropriately. Thebrake interface 162 generates an appropriate brake request that is sent to thebrake controller 156. - A particular embodiment of
gap controller 112 is described in more detail below with reference toFIG. 3 . - Returning to
FIG. 2 , there are a variety ofestimators 114 that are useful for thegap controller 112. In various embodiments these may include one or more of amass estimator 271, adrag estimator 273, aground speed estimator 275, agyro bias estimator 277 and/orother estimators 279. - The
mass estimator 271 is arranged to estimate the respective masses of the platoon partners. These mass estimations may be used by thegap controller 112 to help scale its torque and brake requests appropriately based on the respective weights (masses) of the platoon partners. - The
drag estimator 273 is arranged to estimate the respective drag resistances of the platoon partners. These drag resistance estimates may also be used by the gap controller to help adjust its torque and brake requests appropriately. In general, the drag resistance of any particular truck or other vehicle can vary based on a variety of factors including: (a) its drag profile (which in the context of a truck may change based on the trailer being pulled—if any, or other characteristics of the load); (b) the vehicle's current speed, (c) wind speed and direction, (d) rolling resistance, (e) platoon state (e.g., whether a platoon is active, the position of the vehicle within the platoon, the gap), (f) bearing wear, etc. - The
ground speed estimator 275 is arranged to estimate the actual ground speed of the respective platoon partners. Many trucks and other vehicles have wheel speed sensors that can quite accurately measure the rotational speed of the associated wheels. The actual ground speed at which the vehicles are traveling will vary based on the respective diameters of the wheels and slip conditions of the tires. The precise diameter of the wheels can vary based on the tires used. Furthermore, the diameter of the wheels will vary over time with tire wear, changes in ambient temperature and other factors. The wheel diameter will even change over the course of a particular trip as the tires heat up (or otherwise change in temperature) during use. In practice, all of these variations in wheel diameter are potentially significant enough to impact the gap estimation and gap control. Therefore, theground speed estimator 275 is arranged to estimate the actual ground speed based on measured wheel speed and other available information such as GNSS information. The ground speed estimates are particularly useful in times when tracker based gap measurements (e.g., radar, cameras, LIDAR, etc.) aren't available—which may occur, for example, when the platoon partners are laterally offset due to a lane change, etc. - Several of the measurements utilized by the
gap controller 112 are inertial measurements that are gyro based. These may include yaw measurements which indicate the rate at which the associated vehicle is turning, longitudinal acceleration measurements, etc. Gyros often have an inherent measurement error referred to as a gyro bias that can affect measurements. Thegyro bias estimator 277 estimates such biases to allow the gap controller to compensate for such gyro based measurement errors. - The
platoon controller 110 can include anyother estimators 279 that may be useful to anyparticular gap controller 112 as well. - The
platoon controller 110 may also include one ormore trackers 116. Eachtracker 116 is arranged to measure or otherwise determine the gap. One type of tracker that is used in many implementations is a radar basedradar tracker 283. Newer commercially available trucks often come equipped with a radar unit as standard equipment and radar trackers are particularly well suited for use in such vehicles. Of course, one or more radar units may be installed on any vehicle that does not come pre-equipped with a radar unit to facilitate use ofradar tracker 283. By way of example, some specific radar trackers are described in more detail in co-pending U.S. application Ser. Nos. 15/590,715 and 15/590,803, both filed May 9, 2017, both of which are incorporated herein by reference. - LIDAR is another distance measuring technology that is well suited for measuring the gap between vehicles. LIDAR is quickly gaining popularity for use in automated and autonomous driving applications.
LIDAR tracker 286 is well suited for use on vehicles that have or are provided with LIDAR units. Cameras and stereo cameras are also becoming more popular distance measuring tools for use in various automated and autonomous driving applications. - Of course, other distance measuring technologies can be used to measure or estimate the gap between vehicles as represented by
other trackers 289. By way of example, a GPS tracker could be used that is based primarily on the respective reported GPS positions of the vehicles. - The tracker(s) used in many embodiments are configured to fuse data from multiple sensors to help validate the measurements of the primary sensors used by the respective trackers. The aforementioned radar tracker application describes a variety of methods for fusing data to help validate measurements of a primary sensor in that manner
- In various embodiments, the
gap estimator 240 could replace or be replaced by one or more of the trackers, or could be thought of as a tracker itself since it determines/estimates the gap based on inputs from multiple sensors. In the illustrated embodiment, thegap estimator 240 is shown separately as part ofgap controller 112 since it fuses distance data from the tracker(s) and any other available sources such as GNSS sensors on each of the vehicles. - The
platoon controller 110 may also include one ormore monitors 118 that are configured to monitor specific components that are relevant to gap control. By way of example, one specific monitor that is particularly useful to the control of platooning trucks isbrake health monitor 291. Thebrake health monitor 291 is configured to monitor the brake system and to identify circumstances in which the brakes may not be able to deliver the level of braking normally expected for platoon control—as for example could occur if the foundation brakes include drum brakes that have been used while traveling downhill in the mountains to the extent that they are close to overheating. If thebrake health monitor 291 identifies such a circumstance, it informs the platoon controller, which can take the appropriate remedial action. The appropriate remedial action will vary based on the specific circumstances identified by the brake health monitor, but may include, for example, actions such as dissolving the platoon, increasing the target gap to a level more appropriate for the brake conditions, etc. Of course, the brake health monitor can also configured to identify circumstances in which the condition of the brakes has improved (e.g., the brakes have cooled sufficiently) and inform the platoon controller of those circumstances as well so that the platoon controller can act accordingly. For example, improved braking status may allow the target gap to be reduced, a platoon to be reestablished or other appropriate actions. - The platoon controller may include any of a variety of
other monitors 299 that are configured to monitor the state or status of other components, systems, environmental conditions, road or traffic conditions, etc. that may be relevant to platoon control. For example, a DSRC link monitor may be provided to monitor the status of a DSRC communication link between the platoon partners. - Referring next to
FIG. 3 , another embodiment ofgap controller 112 will be described in more detail. Similarly to the embodiment illustrated inFIG. 2 , thegap controller 112 includes a target andstate setter 200, agap regulator 210 and agap estimator 240. In the embodiment ofFIG. 3 , the target andstate setter 200 includes an operatingstate selector 203, and acontrol parameter selector 206 that determines, selects, sets or otherwise indicates to the gap regulator the values of any variable control parameters that are appropriate for use in the selected operational mode. - The operating
state selector 203 is arranged to determine the intended operational mode (state) of thegap regulator 210. In some specific embodiments, the operational modes might include a “normal” or “gap control” operational mode in which the gap regulator is configured to control towards attaining an maintaining a designated gap between the vehicles. In the gap control operational mode control parameter variables dictated by the control parameter selector might include the target gap itself (e.g. 10 m, 12 m, etc.)—which may vary somewhat based on driving conditions (e.g., weather, terrain, road conditions, traffic, etc.). Other control parameters during normal operation may include parameters that impact the draw-in speed, the tightness of the control, tolerances or variations between torque control and braking control, etc. In other embodiments, “initiate platoon” and/or “draw-in” or “pull-in” may be one or more separate states that are used to establish a platoon and/or to bring the platoon partners together in a safe manner under at least partially automated control. - Another potential operational mode is a “dissolve” mode in which the platoon controller transitions the trailing vehicle toward/to a position at which the driver of the trailing vehicle (or an automatic cruise control system) can safely take over control of the vehicle. Generally, dissolving a platoon includes increasing the gap between the vehicles in a controlled manner to/towards a point at which the platoon can be dissolved and vehicle control can be safely transferred to manual control by the driver or to control through the use of a different system such as adaptive cruise control. The dissolve mode may optionally be triggered by a wide variety of different circumstances, as for example, in response to one of the platoon partners or the NOC deciding to terminate the platoon; the detection of a car cutting-in between the platooning vehicles; the loss of communications between the vehicles for an extended period; the detection of an object in front of the lead vehicle that is too slow or too close to the platoon; etc.
- Another potential operational mode may be a velocity control or relative velocity control mode. Velocity control, or relative velocity control may be preferable to trying to control to maintain a particular gap in a variety of specific circumstances—as for example when the trailing vehicle's radar (or other) tracking unit loses sight of the partner vehicle, as can occur when there is a lateral offset between the vehicles due to a lane change or other conditions.
- Of course, there can be a variety of other operational modes as well.
- The
gap regulator 210 is arranged to control the trailing platoon partner in the manner designated by the target andstate setter 200. In the embodiment illustrated inFIG. 3 , thegap regulator 210 includes ascaler 212 and two separate controllers which are used in different combinations in different operating modes. In the illustrated embodiment, the controllers include a sliding mode controller 215 (which performs gap control) and a velocity/relative velocity controller 218. It should be appreciated that in other embodiments, a single controller, additional and/or different may be provided as appropriate for any particular implementation. - In the illustrated embodiment, the
feed forward scaler 212 is configured to scale the torque and brake signals from the front vehicle before adding them to the outputs from the sliding mode andrelative velocity controllers - The sliding
mode controller 215 is configured to control the trailing vehicle in a manner that seeks to attain and maintain the desired gap in accordance with the target gap and any other control parameters specified by thecontrol parameter selector 206. Thus, its primary function is gap control. Thevelocity controller 218 is configured to control the trailing vehicles in a manner that maintains a designated velocity relative to the lead vehicle, or in some circumstances, simply a designated velocity. In the illustrated embodiment, these two separate controllers are provided so that thegap regulator 210 can provide different types of control, as may be appropriate in different operational circumstances. A few specific examples are described with reference toFIGS. 4A-4C . In the described embodiments, both thecontrollers adder 250 is used to select the appropriate signals to output based on the current operating mode. Anoptional braking monitor 255 is a safety feature that may be utilized to help ensure that the brake commands outputted by selector/adder 250 don't overly aggressively brake the trailing vehicle except in where necessary from a safety/crash prevention standpoint. This is to reduce the risk of traffic behind the trailing platoon partner from being impacted by unexpected aggressive braking of the trailing platoon partner. - The sliding
mode controller 215 is arranged to control the trailing vehicle in a manner such that its relative velocity relative to the front vehicle varies as a function of the gap between the vehicles. This characteristic is illustrated in the state space diagrams ofFIG. 5 which show a control scheme in accordance with one specific implementation. More specifically,FIG. 5 plots relative velocity between the vehicles (the Y-axis) vs. gap between the vehicles (the X-axis).FIG. 5 also show a torque request controllertarget control line 320. In the illustrated embodiment, the nominal desired gap is 12 meters—which is represented byline 310. Thus, thetarget control point 311 is 12 meters with zero relative velocity, which is the point represented by the intersection of line 310 (12 meters gap) and line 312 (zero relative velocity). - The torque
request controller component 221 ofgap regulator 210 is configured to generate a torque request that is appropriate to control the gap in accordance withtarget control line 320. The torque request is then implemented byengine torque controller 152. As can be seen inFIG. 5 , when the gap is larger than the desired gap, the rear truck is controlled to travel slightly faster than the front truck is traveling such that the relative velocity of the rear truck has a small positive value. As the rear truck draws closer to the lead truck, its relative velocity is reduced in a smooth manner until the gap is reduced to thetarget control point 311, at which point the relative velocity would be zero if perfect control were attained. If the rear truck gets closer than the desired gap, it is slowed so that it has a negative relative velocity relative to the lead truck to reestablish the desired gap. - The sliding
mode controller 215 utilizes a unified sliding mode control scheme during both the “pull-in” and gap maintenance stages of platooning. Configuring the sliding mode controller to control towardstarget control line 320 helps ensure that the relative speed vs. gap relationship stays within a region safe for platooning. - In the embodiment illustrated in
FIG. 3 , the slidingmode controller 215 includes separate controllers (e.g.torque request controller 221 and brake request generator components 223) which are configured to control towards different gap control targets. The different control targets are illustrated in the state space diagrams ofFIG. 5 which show a control scheme in accordance with one specific implementation. More specifically,FIG. 5 shows a brake request controllertarget control line 330 in addition to torque request controllertarget control line 320.FIG. 5 additionally shows representative transition paths from various points in the state space to the torque requesttarget control line 320. - For most open highway driving conditions, modulating the torque request alone is sufficient to control the gap appropriately without requiring the use of the foundation brakes. This is in part because the torque request can be negative to a certain degree without needing to actuate the foundation brakes through the use of engine braking and/or the retarder (if available). As mentioned above, when fuel is cut-off there will be some pumping losses and some frictional losses in the powertrain, so some level of negative torque can be provided while using normal valve timing by simply reducing the fuel charge appropriately. When larger negative torque is needed, the
engine torque controller 152 can create larger negative torques by actuating the retarder and/or by taking other appropriate measures. - Separately, the brake
request controller component 223 ofgap regulator 210 is arranged to generate brake requests during normal operation that are generally arranged to maintain a different gap—specifically a smaller gap—than thetorque request controller 221 targets. This difference in the gaps that the torque and brake request controllers control to is sometimes referred to herein as thegap tolerance 340. In general, brake requests 213 are not generated unless or until the gap is reduced at least the gap tolerance below the torque requesttarget control line 320. Since the brakes can only be used to slow the vehicle, the effect of this difference is that the trailing truck will be allowed to creep in a relatively small amount (2 meters in the example) before the foundation brakes are actuated when thegap regulator 210 cannot maintain the desired gap through control of the torque request alone. When the desired gap can be restored by modulating the torque requests alone without crossing targetbrake control line 330, then the foundation brakes do not need to be used at all. This has the effect of safely maintaining a gap while reducing the probability that the foundation brakes will be deployed unnecessarily. - Normal gap control is illustrated in
FIG. 4A . During normal gap control, the slidingmode controller 215 is use to determine torque and brake requests that are appropriate to attain and maintain the target gap set bycontrol parameter selector 206. When appropriate, the torque and brake requests generated by the slidingmode controller 215 may be scaled appropriately by selector/adder 250 based on inputs from feed forwardscaler 212. In this normal gap control mode, the outputs of therelative velocity controller 218 are not used in the control of the trailing vehicle. - In some embodiments, the sliding
mode controller 215 includes separate torque request andbrake request controllers FIG. 3 . The torque request andbrake request controllers - Although the sliding
mode controller 215 works very well to control the gap, there will be operational circumstances in which different types of control may be appropriate. For example, a different type of control may be desirable when it is necessary to dissolve a platoon and return the trailing vehicle to manual or other automated control. Typically, the gap between vehicles during platooning will be smaller, often much smaller, than can safely be maintained by a driver under manual control. Therefore, in general, when a platoon is dissolved with the intent to restoring manual control of the trailing vehicle, it will be desirable to grow the gap to a distance that is appropriate for manual control before relinquishing control to the driver. This can be accomplished in a smooth manner byrelative velocity controller 218. - When operating
state selector 203 determines that the platoon should be dissolved, it directs theGAP regulator 210 to transition to a dissolve mode as represented byFIG. 4B . In the dissolve mode, primary control is provided byrelative velocity controller 218. Thecontrol parameter selector 206 may designate a desired (target) relative velocity for the trailing truck during the dissolve. The specific target relative velocity may vary based on the nature of the circumstances and/or the vehicles involved in the platoon. In general, it is desirable to select a relative velocity that will cause the vehicles to gradually, but expeditiously separate, without requiring the trailing vehicle to slow excessively (which could unduly hinder following traffic) and preferably without requiring the lead vehicle to alter its drive plan. By way of example, relative velocities during dissolves on the order of 0.5 to 4 meters per second, as for example, 1-2 m/s, have been found to work well in the context of platooning trucks. - During a dissolve, the lead vehicle may take a variety of actions. For example, the lead truck may accelerate or increase its torque command aggressively. In such cases, it may not be desirable to try to accelerate the trailing truck in a similar manner thereby allowing the lead vehicle to pull away more than would otherwise occur under relative velocity control. One way to accomplish this in the context of platooning trucks is to ignore or otherwise disable positive torque commands from feed forward
scaler 212. - Another potential scenario is that the lead truck brakes or slows significantly while under velocity control. In some circumstances, the
velocity controller 218 may be configured to permit a certain amount of gap shrinkage when the gap is relatively larger to thereby reduce the overall amount of braking required. In the illustrated embodiment, the sliding mode controller is configured to ensure that the gap between the vehicles is always sufficient to give the trailing vehicle sufficient time to respond in a manner that prevents the trailing vehicle from running into the back of the lead vehicle regardless of the occurrence of (reasonable) unexpected events. Therefore, if the sliding mode controller is outputting a braking or negative torque signal that has a greater magnitude than the relative velocity controller, then that larger braking/negative torque command should be passed to the vehicle's engine and braking controllers. Therefore, during a dissolve, the selector/adder 250 is configured to only utilize negative commands (i.e., braking commands and negative torque commands) from the slidingmode controller 215 and to only use such commands when they are greater in magnitude than the commands from therelative velocity controller 218. - There may also be operational circumstances outside of dissolves in which relative velocity control or simply velocity control is desired. For example, there may be circumstances in which the back of the lead vehicle moves out of view of the trailing vehicle's tracker(s) 116 or the tracker(s) 116 otherwise loses sight of the back of the platoon partner. This can occur, for example, as a result of a lane change by one of the platoon partners. In such a circumstance the gap regulator may not have an accurate measure of the longitudinal gap between the vehicles—and may have to rely on less accurate approaches for determining the gap such as the vehicle's respective GNSS positions. In such circumstances, it may be desirable to control the trailing vehicle to slowly drop back until the back of the lead vehicle comes within the tracker's view. Again, the
relative velocity controller 218 is well suited for use in this circumstance—although the preferred relative velocity control may be a bit different than occurs during a dissolve. Specifically, the goal is typically not to drop back as quickly or as far as would occur during a dissolve—thus a smaller relative velocity (e.g. 0.5 m/s vs. 2 m/s), may be appropriate. - One approach to such relative velocity control is illustrated in
FIG. 4C . In the velocity control scheme ofFIG. 4C velocity controller 218 is used in conjunction with normal scaling from feed forwardscaler 212. This causes the trailing platoon partner to better follow lead vehicle accelerations and/or torque increases than occurs during the dissolve state illustrated inFIG. 4B . At the same time, for safety purposes, braking requests and negative torque request from the slidingmode controller 215 may be utilized as appropriate by selector/adder 250 in a manner similar to the approach described above with respect toFIG. 4B . - Although particular platoon and gap controller architectures are illustrated in
FIGS. 2 and 3 , it should be appreciated that the specific architectures utilized may vary widely to meet the needs of any particular platooning or other automated vehicle control scheme. - As will be apparent to those familiar with the art, the described controllers can be implemented algorithmically using software or firmware algorithms executing on one or more processors, using programmable logic, using digital or analog components or using any combination of the preceding.
- In the detailed description above, it is assumed that the controlled power plant is an internal combustion engine, as for example a diesel engine. However, it should be appreciated that the described control approach can be utilized regardless of the nature of the power plant used to provide torque to drive the host vehicle. Thus, the described controller design, functionalities and architectures may generally be applied to the control of vehicles that utilize electric motors, turbines, fuel cells, or other types of powerplants to provide power to a drivetrain or directly to one or more wheels, including hybrids which combine more than one type of powerplant (e.g., hybrids that incorporate both an electric motor and an internal combustion engine). When the power plant is or includes an internal combustion engine, any type of internal combustion engine may be used including gas powered engines, diesel powered engines, two-stroke engines, 4-stroke engines, variable stroke engines, engines utilizing more than four-strokes, rotary engines, turbine engines, etc.
- The description above has focused primarily on tractor-trailer truck platooning applications, however, it should be appreciated that the described control approach are well suited for use in a wide variety of connected vehicle applications, regardless of whether one or more of the vehicles involved have 2, 3, 4, 18 or any other number of wheels, and regardless of nature of the powerplants used in such vehicle.
-
FIG. 6 illustrates a platoon control system hardware architecture that is particularly well suited suitable for ASIL compliant platoon control. The illustrated embodiment includes three separate controller hardware units. These includeplatoon controller 410,vehicle interface controller 460 andgateway processor 470. Selected components of arepresentative gateway processor 470 are illustrated inFIG. 7 . As best seen inFIG. 6 , theplatoon controller 410 communicates with thevehicle interface controller 460 through aninterface 420 and withgateway 470 through adirect link 478. In some embodiments, thelink 478 is a dedicated direct wired connection and no other devices are coupled to that link. The wired connection may be provided by any suitable form of cabling or traces, as for example co-ax cable, twisted pair wirings, fiber optics or any other suitable physical connection medium. - In the illustrated embodiment, the
platoon controller 410 incorporates all of the functionality ofplatoon controller 110 described above. The vehicle interface controller 460 (also sometimes referred to as a system manager) performs the functionality ofactuator interface 160 and further includes a number of safety monitors. In some embodiments, the safety monitors are arranged to execute ASIL compliant safety monitoring algorithms and thevehicle interface controller 460 is designed as an ASIL compliant device. - In general, the
vehicle interface controller 460 includes a higher safety level processor and software (including the safety monitors) that independently verifies the commands transmitted by theplatoon controller 110 before they are passed on to the vehicle actuators. These verifications use a subset of the available sensor inputs, together with verification algorithms that are independent and distinct from those used by the platoon controller. - The
gateway processor 470 is arranged to coordinate communications between a host vehicle and the platoon partner(s) and to coordinate communication between the host and the network operation center and/or any other entities that are external to the vehicle. As such, in a specific implementation of the system illustrated inFIG. 1 thegateway processor 470 includes theinter-vehicle communications controller 170 andNOC communication controller 180 as best illustrated inFIG. 7 . Typically the inter-vehicle communications controller utilizes a short-range, vehicle-to-vehicle wireless communications protocol, as for example the DSRC protocol. The NOC communication controller typically communicates with a networks operations center using cellular or satellite communications. - In some embodiments, the connection (link 478) between the
gateway processor 470 and theplatoon controller 410 is a dedicated direct wired connection and no other devices are coupled to the link. In some implementations an Ethernet or similar standardized wired communications protocol is used to pass information between the gateway processor and the platoon controller. This facilitates high speed, high reliability communications between the gateway processor and the platoon controller. In a specific example, a 100BASE or higher (e.g. 1000BASE, 10GBASE, etc.) Ethernet physical layer may be used, although it should be appreciated that a variety of other physical layers may be used in other embodiments. - In some embodiments, the
gateway processor 470 is also arranged to communicate with aforward facing camera 477 mounted on the vehicle and adashboard display 475. When the host vehicle is the lead vehicle in a platoon, the gateway processor transmits a video feed received from theforward facing camera 477 to the trailing vehicle(s) so that the driver of the trailing vehicle has a view of what is in front of the lead vehicle. When the host vehicle is a trailing vehicle in the platoon, thegateway processor 470 receives such a video feed from the gateway processor on the lead vehicle and transmits the feed to thedashboard display 475 where it is displayed to give the driver of the host vehicle a view of what is in front of the lead vehicle. Displaying a view of what is in front of the lead vehicle to drivers of a trailing vehicle is desirable to provide the driver of the trailing vehicle with improved situational awareness and the ability to independently react to situations that occur in front of the platoon. This can be particularly important because in many platoons (e.g. platoons that involve tractor trailer trucks) the trailing vehicle will be very close to the lead vehicle (much closer than normal manual driving) and the lead vehicle will effectively block the view of the trailing vehicle which can be an uncomfortable experience for drivers and/or passengers in a trailing platoon partner—especially when they do not have access to a view of what is going on in front of the platoon. - The video streams passed through the gateway may be managed by a
video manager 474. Since thegateway 470 communicates directly with thecamera 477 and/ordashboard display 475, theplatoon controller 410 is not in any way burdened by the need to manage that data flow. - In some embodiments the
gateway 470 also includes amessage logger 473 that logs various messages and other information passed there through in order to provide a record for diagnostic purposes and the like. The functionality of themessage logger 473 will be described in more detail below. - The
platoon controller 410 is configured as a listener on any appropriate vehicle communications buses where it can directly obtain information about the vehicle's operational state—such as the vehicle's current wheel speed, any brake or accelerator pedal inputs, steering wheel position (as appropriate), transmission gear, etc. It is also coupled to sensor units such asGPS unit 131 to receive positional information about the location of the vehicle, and to forward lookingradar unit 137 to receive information about the position of objects outside the vehicle (e.g., radar scenes). Similar information may be obtained from other sensors as well, such asLIDAR 138, camera(s) 139 etc. Since theplatoon controller 410 is configured strictly as a listener on the vehicle's communication bus(es) and does not itself transmit information over such bus(es), it does not need to be ASIL compliant, as long as the control commands it outputs to the vehicle interface controller are verified to ASIL standards by thevehicle interface controller 460. - The vehicle interface controller 460 (also sometimes referred to as the system manager 460), which is ASIL compliant, is arranged to send commands to, and otherwise communicate with, the vehicle's engine controller (EECU), the brake controller (BECU), and/or any other appropriate controllers either directly or via one or more communications buses, such as the vehicle's CAN bus(es).
- In the illustrated embodiment, the
interface 420 betweenplatoon controller 410 and vehicle interface controller 460 (also sometimes referred to as the system manager 460) is fairly narrowly defined. It includes the substantive commands generated by the platoon controller—which in the illustrated embodiment includetorque request 422,brake request 424, and optionally aretarder request 426. When the platoon controller also controls the steering or other aspects of the host vehicle steering and/or other appropriate control commands (not shown) may be included as well. - The
interface 420 also includes a platooningstate indicator 428 that is a signal from the platoon controller indicating whether or not it believes that its output should be directing operation of the vehicle. The platooningstate indicator 428 may take many forms, as for example a simple flag that when high indicates that theplatoon controller 410 believes that platooning is/should be active and that its torque, braking and retard commands 422, 424, 426 should be followed. In such an arrangement, a low flag state indicates that the platoon controller believes that it is not controlling the vehicle. Thevehicle interface controller 460 does not forward any torque, braking, retard or other control commands at any time that the platooningstate indicator 428 indicates that platoon control is not active. In the event (generally unlikely) that one of the safety monitors 465 indicates that platooning is not appropriate when theplatoon controller 410 believes that platooning is valid (as indicated by platooning state indicator 428), the vehicle interface controller/system manager 460 initiates a termination of the platoon. - The
interface 420 also facilitates the transmission of certain state information—which is preferably ASIL validated state information—about both the host vehicle and the partner truck that is useful to the safety monitors. Specifically, the hostvehicle state information 441 includes state information about the host vehicle that has been validated (e.g., ASIL-C validated) by thesystem manager 460 and is useful to one or more safety monitors on the partner vehicle. The partnervehicle state information 444 includes state information about the partner vehicle that has been validated by the partner vehicle's system manager and is useful for one or more safety monitors 465 on the host vehicle. Hostvehicle state information 441 is transmitted to theplatoon controller 410, which forwards such information without modification to thegateway 470, which in turn forwards the host vehicle state information to the gateway on the partner vehicle. Partnervehicle state information 444 received bygateway 470 from the partner vehicle's gateway is forwarded without modification to theplatoon controller 410 and from there to system manager 460 (again without modification). Preferably thehost state information 441 is transmitted with a checksum or other suitable data integrity verification mechanism that allows the receiving system manager to verify that the data it receives is uncorrupted. Any corrupted information can then be ignored. With this approach the ASIL validated state information is passed without modification from one ASIL compliant device (system manager 460 on a first platoon partner) to another (system manager 460 on a second platoon partner) and therefore is suitable for use in ASIL compliant safety checking algorithms—even when intermediate transmitting devices (e.g.,platoon controller 410, gateway 470) are not themselves ASIL compliant. - The host and partner vehicle state information may include any ASIL validated state information that is used by any of the safety monitors. This may include, for example, vehicle wheel speeds, brake requests, torque requests and/or delivered torque, brake air supply pressure, steering position, accelerometer readings and/or any other information about the partner vehicle used by the
system manager 460 as part of a safety monitor. To the extent that theplatoon controller 410 utilizes partner state information originated by an ASIL validated device beyond the state information used by thesystem manager 460, that information can optionally be included in thevehicle state information interface 420. - It is noted that some of the host vehicle's sensor information (e.g., wheel speed, brake pedal position, radar scenes, etc) is used by both the
platoon controller 410 and thesystem manager 460. Since theplatoon controller 410 is preferably an authorized listener on any appropriate vehicle control bus(es), the platoon controller does not need to wait to receive such information from the system manager. Rather, it obtains any relevant host vehicle sensor information directly from the appropriate sensor over any suitable connection such as an appropriate CAN bus. However any sensor information relevant to the system manager on the partner vehicle is read by the system manager (regardless of whether it is also read by the platoon controller) and included in hostvehicle state information 441 so that the partner vehicle's system manager is ensured that such information is ASIL verified. In other embodiments any host vehicle sensor information that is not directly accessible by the platoon controller can be received via thesystem manager 460 acting as an intermediary. - Although there will be some overlap in the sensor information used, it should be appreciated that the host vehicle sensor information used by the host
vehicle platoon controller 410 and the hostvehicle system manager 460 will often vary and may further vary from the partner vehicle sensor information of interest. For example, the host platoon controller utilizes GNSS position data in the determination of the torque and braking requests, however the GNSS position information may not be utilized by the System Manager since it is not ASIL compliant. - Some of the sensor information that is used by the safety monitor on the host vehicle may not be needed by the safety monitor on the partner vehicle. This may include information such as the radar scenes, the accelerator pedal position, inputs from a host vehicle
driver interface device 469, etc. To the extent that such sensor information is not used by the partner vehicle, there is no need for such information to be included in thevehicle state information - Some of a host vehicle's sensor information that is used by the platoon controller on the partner vehicle may not be ASIL compliant and therefore may not be used in the safety monitors on the partner vehicle. Such, sensor information that is not relevant to the safety monitors on the partner vehicle does not need to be included as part of
vehicle state information platoon controller 410 and sent to the corresponding platoon controller on the partner vehicle (by way of communication controllers 470). For example, it is extremely difficult to ASIL validate GPS or other GNSS position data. Therefore, GNSS position data is preferably not included in thevehicle state information gateways 470. - The
driver interface device 469 may be a button or other suitable mechanism positioned at a convenient location on the host vehicle dashboard or elsewhere in the host vehicle cabin. Thedriver interface device 469 is a mechanism that the driver may press as appropriate to indicate that the driver is ready to platoon during initiation of a platoon, or to initiate the dissolution of a platoon when platooning is no longer desired. The use of thedriver interface device 469 is described in more detail in U.S. patent application Ser. No. 15/607,902 which is incorporated herein by reference. In the illustrated embodiment, commands from the driver interface device 469 (which are preferably ASIL compliant) are sent to thevehicle interface controller 460 and passed from there to theplatoon controller 410. Similarly, requests to the driver interface device pass from the platoon controller to thevehicle interface controller 460 and from thevehicle interface controller 460 to thedriver interface device 469. This architecture simplifies the work that must be done to make thedriver interface device 469 ASIL compliant. It should be appreciated, however, that in other embodiments, theplatoon controller 410 may also be a direct listener to commands from the driver interface device. In the embodiment illustrated inFIG. 6 ,interface 420 includes driver platoon related requests and commands 427 which represent the request sent to and commands received from thedriver interface device 469. - In some specific embodiments, the
vehicle interface controller 460 is implemented as a single dedicated integrated circuit chip and theplatoon controller 410 andgateway processor 470 are each implemented as separate system on modules (SOMs). - The platoon control system hardware architecture illustrated in
FIG. 6 is particularly well suited for efficiently handling platooning control related tasks in an ASIL compliant manner using information available from a variety of sources including sources that are not themselves ASIL. With the described arrangement, the powertrain control commands ultimately issued by the control system may be ASIL rated. - The hardware architecture of
FIG. 6 also has several advantages from a security standpoint. In the illustrated embodiment, thegateway processor 470 is not connected to any of the vehicle's control related communications buses (e.g., the CAN bus(es)). Therefore, thegateway processor 470, which is potentially the least secure of the three hardware components, is not able to transmit any information directly onto any of the more secure vehicle communications buses or receive any information directly from such buses—which is advantageous from a security standpoint since a nefarious entity cannot gain control the vehicle in any way by somehow hacking into thegateway processor 470. Furthermore, with this arrangement, thegateway processor 470 does not need to be ASIL compliant which greatly simplifies its certification. - During the course of driving, a road obstacle or other hazard may cause a lead vehicle in a platoon to react and take action to avoid risks associated with the hazard. Under such circumstances, the lead vehicle reacting before the following vehicle often increases risks. For example, if the lead vehicle brakes before the following vehicle, in a worst case scenario, it is conceivable that the following vehicle may collide with the leading vehicle.
- Such problems caused by road obstacles or hazards are avoided or mitigated by (1) receiving data generated by one or more sensors arranged to interrogate a space radially extending from the lead vehicle as the lead vehicle travels over the road surface, (2) ascertaining a hazard caused by an object in the space from the data indicative of the perceived environment and (3) causing the following vehicle, while operating in the platoon, to take a preemptive action to avoid or mitigate risks resulting from the hazard caused by the object in the space, the preemptive action taken by the following vehicle prior to and/or without waiting for the lead vehicle taking any action in response to the object in the space. For example, by slowing the following vehicle before the lead vehicle, it has been the incidence of collision between the platooning vehicles is significantly reduced.
- While scenario above describes a situation of hazard avoidance, it should be understood that present invention is directed to a boarder concept. For instance, the present application is should be construed as addressing the general concept of using sensor data collected or generated by one vehicle in a platoon to control the operation of another vehicle in the platoon. Typically, the data is used by the receiving vehicle to avoid hazardous conditions or other risks. However, this is by no means a requirement. On the contrary, the data can be used by the receiving vehicle for just about any purpose.
- Referring to
FIG. 8 , a diagram 800 showing a platoon including alead vehicle 802 and several following vehicle(s) 804 encountering a hazard, represented by anobject 806, while traveling across a road surface is illustrated. As the vehicles are operating in a platoon, agap 808 is provided and controlled between any pair of leading and following trucks as described in detail above. - The
lead vehicle 802 includes one or more sensors (not illustrated inFIG. 8 ) that are used to interrogate a space, designated byreference numeral 810. In this particular embodiment shown, thespace 810 extends radially outward from the front of thevehicle 802, encompassing the road ahead. It should be understood, however, that the particular direction and shape of thespace 810 as depicted is by no means limiting. On the contrary, thespace 810 in various embodiments can radiate outward from the front, side(s) rear, 360 degrees or any fraction thereof, around thelead vehicle 802. Thus, thespace 810, which is interrogated by the aforementioned sensor(s), should be widely construed to cover any applicable shape or direction. - As the platoon travels down the road surface, the sensor(s) on the
lead vehicle 802 generate data indicative of the perceived environment within thespace 810. As a result, a hazard caused by the presence of an obstacle, such asobject 806, may be ascertained. In various embodiments, theobject 806 represents a wide variety of potential obstacles, such as other vehicles (e.g., cars, trucks, motorcycles), pedestrians, a cyclist, road debris, traffic signs or posts along the side of the road, or just about any other possible obstruction that may be encountered while driving. - The Applicant has found that with platooning vehicles in non-emergency situations, risks associated with hazards, such as created by an
obstacle 806, are often mitigated or altogether avoided by directing the followingvehicle 804 to take a preemptive action prior and/or without waiting for thelead vehicle 802 to react to the obstacle. For example, if the platoon crests a hill on a highway and suddenly encounters stopped cars (e.g., objects 806 that represents a hazard) ahead on the highway, then the followingvehicle 804 preferably brakes or takes some other preemptive action to slow down before thelead vehicle 802 slows down. By braking earlier, the rate at which following vehicle loses velocity is greater than the lead vehicle. As a result, thegap 808 between the two vehicles increases, potentially dissolving the platoon. The likelihood that the followingvehicle 804 colliding with the leadingvehicle 802 is therefore significantly reduced. - In various implementations, the processing of the data generated by the sensor(s) on the lead vehicle, indicative of the perceived environment within the
space 810, may be performed either on the followingvehicle 804 or thelead vehicle 802. Two such embodiments are described below. - Referring to
FIGS. 9A-9C , a set of block diagrams illustrating a first embodiment of a risk mitigation oravoidance system 900 is illustrated. In this embodiment, the processing of the sensor data collected on thelead vehicle 802 is mostly performed by the followingvehicle 804. - As illustrated in
FIG. 9A , thelead vehicle 802 generates and collects the data from the sensor(s) and then transmits or relays the data in raw or generally non-processed form to the followingvehicle 804. In response, the followingvehicle 804 perceives from the data the environment in thespace 810 ahead of thelead vehicle 802, including the presence of anobstacle 806 that may represent a hazard. If a hazard is detected, one of a plurality of tiered severity threat levels is selected, depending on the severity of the hazard created by theobstacle 806. The following vehicle then implements one or more preemptive actions, as dictated by the selected severity threat level, to avoid or mitigate the risks created by the object. - In
FIG. 9B , a block diagram of the modules provided in thelead vehicle 802 for generating, collecting and relaying the data to the followingvehicle 804 is illustrated. In particular, thelead vehicle 802 includes one or more sensor(s) 902, a platoon controller, such as thecontrollers 110 and/or 410 as described above, and thegateway 470 for transmitting or relaying the data to the followingvehicle 804. - As the
lead vehicle 802 travels down the road surface, the sensor(s) 902 interrogate thespace 810, detecting any object(s) 806. The data from the sensor(s) 902, which can be used to perceive the environment within thespace 810, is then transmitted to the followingvehicle 804 via thegateway 470. - In various embodiments, the sensor(s) 902 may include one or more of a radar detection system, a Lidar or laser detection system, a camera or imaging system, a radio system, an automated braking system, an automated collision avoidance system, a GPS system, a cruise control system, or any other type of passive sensor (e.g., a sensor that does not transmit signals but rather is required to perform a measurement, such as a camera) or active sensors such similar radar, Lidar and/or ultrasound, or any combination thereof. In addition, the sensor(s) 902 also includes “sensors” that require some type of hardware on the senses object, such as ultra-wideband, where an antenna is needed on the sensed vehicle. As each of these types of sensor(s) and their use on vehicles is well known, a further description is not provided herein for the sake of brevity.
- The
sensors 902 do not necessarily have to be physically provided on thelead vehicle 802. In alternative embodiments, thesensors 902 can also be various types of road-side sensors, such as but not limited to a camera, a traffic speed monitor or camera, a precipitation monitor, a temperature monitor, a wind sensor, a humidity sensor, a traffic monitoring sensor, or an in-ground sensor. As such, the term “sensor” as used herein should be broadly construed and is intended to mean both sensors on-board a vehicle, road-side sensors, or possibly a combination of both. - Referring to
FIG. 9C , a diagram illustrating the modules for receiving, processing and implementing preemptive action(s) on the followingvehicle 804 are illustrated. The followingvehicle 804 includes agateway 470 for receiving the data transmitted bylead vehicle 802, a threatlevel determination module 904, anaction implementation module 906,platoon controller 110 and/or 410, and optionally amachine learning module 908. - As described above, the
platoon controller 110 and/or 410 on the followingvehicle 804 operates to maintain thegap 808 with the lead vehicle. As the platoon travels down the road surface, themodule 904 processes the data received over thegateway 470. From the data, themodule 904 can perceive the environment in thespace 810 ahead of thelead truck 802 and ascertain any possible hazards created by one ormore objects 806 that may be detected. - In the event any detected object(s) 806 represent a threat, then in accordance with a non-exclusive embodiment, the
module 904 may select one of a plurality of tiered severity threat level thresholds or thresholds, each defining one or more corresponding preemptive action(s) respectively. In other words, themodule 904 selects an appropriate one of the tiered threat levels commensurate with the severity of the threat represented by a perceivedobject 806. - The
action implementation module 906 operates in cooperation with the threatlevel determination module 904. Themodule 906 is responsible for implementing specific preemptive action(s) that correspond to the selected severity threat level, as determined by themodule 904, to mitigate or avoid the risks resulting from theobject 806 in thespace 810. Such preemptive action(s) may include, but are not limited to, broad categories such warnings and/or alerts, certain precautionary preparations in anticipation of a possible collision, and other specific actions. - In optional embodiments,
machine learning module 908 operates in cooperation with the threatlevel determination module 904 to identifyobjects 806 and ascertain the threat level they may represent.Machine learning module 908 provides the ability to predict, learn and identify particular object(s) 806 that may be perceived in thefield 810. For instance,module 908 may rely on image or pattern recognition and computational learning, artificial intelligence, along with data analytics and algorithms, to distinguish different types of objects (e.g., cars, buses, trucks, pedestrians, etc., and the particulars regarding each). Using image recognition,learning module 908 may be able to differentiate one type of vehicle versus another, whether or not a vehicle is moving or stationary (e.g., stalled on the road or moving), the direction a vehicle is travelling from the color of detected lights (e.g., white light from headlights indicates the vehicle is traveling in the oncoming direction, whereas red or brake lights indicates the vehicle is traveling in the same direction), road debris, pedestrians, etc. By recognizing or defining anobject 806, thelevel determination module 904 can make a more accurate assessment of the perceived threat. If the object ahead is identified as a pedestrian, then the selected threat level is likely to be at an emergency level, meaning immediate preemptive action is required to avoiding running over the person. On the other hand if theobject 806 is identified as road debris, such as a tire tread, then the selected threat level will likely be pre-warning or a non-emergency (i.e., a low threat), and the preemptive action will likely be a mere warning. - Referring to
FIGS. 10A-10C , a set of block diagrams illustrating a second embodiment of a risk mitigation oravoidance system 1000 is illustrated. In this embodiment, the processing of the sensor data collected on thelead vehicle 802 is mostly performed by the followingvehicle 804. - As illustrated in
FIG. 10A , thelead vehicle 802 is responsible for (1) generating the data from the one or more sensor(s) 902, (2) perceiving if the environment inspace 810 ahead oflead vehicle 802 includes any object(s) 806, (3) ascertaining any threat created by the object(s) 806 and (4) selecting an appropriate tiered threat level threshold that is commensurate with the severity of the threat represented by an object(s) 806. In addition, thelead vehicle 802 generates and sends coded commands to the followingvehicle 804 that are indicative of the preemptive actions to be taken as dictated by the selected severity level. -
FIG. 10B illustrates the modules for generating and processing the data from the sensor(s) 902 on the leadingvehicle 802. Specifically, thelead vehicle 802 includes sensor(s) 902, threatlevel detection module 904,platoon controller 110 and/or 410, optionallymachine learning module 908, andgateway 470. As each of these modules has been previously discussed, another description is not repeated herein for the sake of brevity. In addition, the leadingvehicle 802 includes anencoder module 910, which is responsible for encoding any preemptive action(s) defined by themodule 904. Thegateway 470 then transmits the encoded command signal(s) to the followingvehicle 804. -
FIG. 10C illustrates the modules for receiving and processing the command(s) on the followingvehicle 804. The modules include gateway 407 for receiving the command(s), aplatoon controller 110 and/or 410, adecoder 912, andaction implementation module 906. During use, the received command(s) are decoded bymodule 912 and provided to themodule 906. In response to the command(s),module 906 implements the defined preemptive action. - In either of the above embodiments, the threat
level detection module 904 is responsible for selecting one of a plurality of tiered threat levels or thresholds depending on the severity of the perceive threat. By way of example, a non-exclusive embodiment with four tiers is described below. In alternative embodiments, the number of tiers may significantly vary from a few too many As such, the specific tiers and the corresponding preemptive actions as discussed below are exemplary and should not be construed as limiting in any regard. - Referring to
FIG. 11 , a table including four severity threat levels is illustrated in accordance with a non-exclusive embodiment of the invention. In this particular embodiment, the four severity levels include: -
- (1) Pre-warning threat,
- (2) Moderate security threat,
- (3) High security threat, and
- (4) Emergency security threat.
- The table also includes three columns, each defining a category of preemptive actions. The three categories in this example include:
-
- (1) Warning(s) and/or Alerts,
- (2) Safety precautions in anticipation of a collision, and
- (3) Specific actions.
- Referring to
FIG. 12 , corresponding preemptive actions for each of the three categories are listed. The corresponding preemptive actions for each category include: - Warning(s)/Alert(s): flashing or operating warning lights on the following vehicle, operating a horn on the following vehicle, operating visual warnings on the following vehicle, operating haptic actuators on the following vehicle and/or manipulating a radio on the following vehicle.
- Safety Preparations: for braking (e.g., pre-pressurizing pneumatic brakes), and/or pre-tensioning seat belt(s).
- Specific Actions: braking, steering, engine braking or retarding, transmission gear shifts, adjusting throttle or torque requests, spoiler adjustments, and/or differential steering.
- Referring again to the table of
FIG. 11 , the checkmarks indicate which category of preemptive action is available for each severity level threshold in accordance with this embodiment. Specifically: - Pre-warning or low security threat level: Warnings/Alerts and Safety Preparations are available.
- Moderate security level: Specific Actions.
- High security: Safety Preparations and Specific Actions.
- Emergency level: all three categories are available.
- It should be understood that in any given circumstance, the threat
level determination module 904 may select any one or combination of preemptive actions available in a given category once a threat severity level is defined. Typically, all of the preemptive actions in a given category will not be selected. However, in certain circumstances, they all may be selected. It suffices to say that themodule 904 has the ability to pick and chose the preemptive actions in a given category on a case-by-case basis, depending on the totality of the circumstances represented by a given threat. - Referring to
FIG. 13 , aflow chart 1300 illustrating operational steps of a non-exclusive embodiment of the risk mitigation oravoidance system 900/1000 is illustrated. With this particular embodiment, the preemptive action(s) taken by the following vehicle for each tier include: -
- (1) Pre-warning level: Warning and/or alert preemptive actions are taken, but the platoon remains intact,
- (2) Moderate level: The
gap 808 is increased, but the platoon remains intact; - (3) High security level: The platoon is dissolved; and
- (4) Emergency level: Hard braking by following vehicle(s) 804 and the platoon is dissolved.
- In the
initial step 1302, theplatoon controller 110/410 of two (or more) vehicles coordinate to establish a platoon as described herein. - In
step 1304, the one or more sensor(s) 902 on the lead vehicle interrogate thespace 810. - In
step 1304, the environment inspace 810, as perceived by processing the data generated by the sensor(s) 902, is analyzed. As previously discussed, the data can be processed by either the followingvehicle 804, thelead 802 vehicle or even possibly by a combination of both (or more vehicles) in the platoon. - In
decision 1308, a determination is made if there is a perceived hazard or not. - If not, then steps 1302 through 1306 are continually repeated so long as the platoon is maintained.
- On the other hand, if a threat is perceived, for example because a
threatening object 806 is identified in thespace 810, then the threat level determination module 904 (either in the lead or following vehicle) selects the appropriate tiered severity threat level commensurate with the perceived threat. In this example, the severity levels include low (1310), moderate (1312), high (1314) and emergency (1316). - If the
low security threat 1310 is selected, thenmodule 904 defines the appropriate warnings and/or alerts instep 1318 and theaction implementation module 906 implements those warnings and/or alerts instep 1320 in thelead vehicle 802 and/or the followingvehicle 804. - If the
moderate security level 1312 is selected, then themodules steps - If the
high security threat 1314 is selected, then themodules step 1326. For example, the relative velocity of the following vehicle is reduced, allowing thegap 808 to grow until the platoon is dissolved. - If the
emergency security threat 1316 is selected, then themodules step 1328 and then dissolve the platoon instep 1330. If multiple followingvehicles 804 are involved, it is preferred that the timing of the hard braking occur in sequence, starting from the last vehicle to the lead vehicle. - Regardless of the tiered security level selected, control is returned to
decision 1308. If the perceived hazard remains, then one of the security levels 1310-1316, and their subsequent actions, is performed until the threat is no longer present and/or the platoon is dissolved. If the threat is no longer present, then control is returned tostep 1302, and normal platooning proceeds. If the platoon was dissolved as a result of a preemptive action, then the vehicles may decide to re-engage as described above once the threat has passed. - To better explain the operation of the
systems 900/1000 for mitigating or avoiding risks encountered by platooning vehicles, several real world examples are provided and discussed below. In this example, the sensor(s) 902 on the lead vehicle are radar detectors capable of detecting or ascertaining the size and relative velocity of object(s) 806 inspace 810. Based on the size and relative velocity, the threat level determination module, optionally along withmachine learning module 908, can identify object(s) 806 and the threat they may represent. Again, the present invention is not limited to using radar sensors. As noted above, a number of different types of sensors can be used, either alone or in combination. For example, radar can be used in cooperation with cameras. The radar can be used to identify the size and relative velocity of object(s) 806 with respect to the lead vehicle, whereas images of the object(s) 806 can be used by learningmodule 908 to precisely identify the objects. - Scenario One: In this example, a car enters onto a freeway via an on ramp 50 meters ahead of a platoon of vehicles. Both the entering car and the platoon are traveling at approximately the same highway speed. Since 50 meters is generally considered a safe distance, and all involved vehicles are traveling at approximately the same speed, any perceived threat will be low. As a result, simply warning and/or alerting the platoon drivers and any other surrounding drivers, is an adequate response commensurate with the relatively low threat. As a result, the warnings alerts, such flashing warning lights, vibrating the seats of the platooning drivers, setting off an audio warning, are typically sufficient preemptive actions.
- Scenario Two: In this scenario, the same car enters the freeway 50 meters ahead of the platoon. However, rather than traveling at highway speed, the car is traveling only at 45 mph, or approximately 20 mph slower than the platoon. As a result, the severity level is moderate, meaning a collision is not imminent, but the lead vehicle of the platoon should react (e.g., switch lanes and/or brake) action to avoid a possible collision. In this situation, the gap is increased without dissolving the platoon. For example, the gap can be increased from a normal operating condition of 12 meters to 24 meters by reducing the velocity of the following vehicle(s). As the relative velocity of the following vehicle is reduced and the gap grows, the lead vehicle can then take precautionary action to avoid the car ahead. If braking is needed, the likelihood of the following
vehicle 804 colliding with thelead vehicle 802 is greatly diminished with a larger gap. When the car ahead speeds up, and the perceived threat is diminished, thenplatoon controllers 110/410 on the following vehicle can increase relative speed to reduce the gap to a normal operating distance (e.g., 12 meters). - Scenario Three: A car abruptly cuts off the
platoon entering space 810 immediately ahead of the lead vehicle. In this scenario, the platoon is now dangerously tail-gating the car ahead, which represents a high security threat if the car ahead suddenly brakes. In response, the system acts to dissolve the platoon, again by first braking or otherwise reducing the velocity of the following vehicle(s) versus the lead vehicle. Once the velocity of the following vehicle(s) is reduced, then the lead vehicle can brake or otherwise reduce its velocity. Since the following vehicle started reducing its velocity sooner, it will slow down quicker relative to the lead vehicle. As a result, the gap will widen until the platoon is dissolved. - Scenario Four: A platoon crests a hill on a freeway and immediately sees stalled cars ahead and quick braking is required to avoid a collision. In this emergency scenario, the following vehicle immediately initiates hard braking (e.g., a Brake Now command), reducing its relative velocity with respect to the lead vehicle and growing the gap and dissolving the platoon. Once the following vehicle reduces its velocity, then the lead vehicle can brake and take other preemptive steps to reduce its velocity. Again, since following vehicle started slowing down first, the gap will increase as the two vehicles reduce their velocity.
- In the various scenarios above, there are a number of situations where the following vehicle is required to reduce velocity prior to the lead vehicle doing the same. The Applicant has found that by initiating reduced velocity of the following vehicle just a split second (e.g., a half second or less) ahead of the lead vehicle results in the size of the gap growing larger as both vehicles decelerate.
- In various embodiments, the relative velocity between the two vehicles can also be precisely controlled when either widening or dissolving the gap. For example, the rate of velocity reduction of the following vehicle may range from (−0.1 to −2.0) meters per second relative to the lead vehicle. In situations where there are multiple following vehicles in a platoon, the velocity reduction per vehicle can be successively incremented depending on vehicle position in the platoon. For instance, the velocity rate reduction for the second, third and fourth vehicles can be incremented (−0.2, −0.4 and −0.6) meters per second respectively. By sequentially controlling the timing (i.e., initiating braking from the back to the front vehicle) and increasing the negative rate of velocity from the back vehicle to the forward vehicle, the gap between each vehicle can be widened or dissolved in a controlled manner
- It should also be understood that the above embodiments of the risk mitigation and
avoidance system 900/1000 are merely illustrative and should by no means be construed as limiting. - For example, any number of severity threat levels or thresholds may be used and the number, type and/or specific preemptive actions per category may widely vary. The above examples of four threat severity levels, and the specific preemptive actions listed for each of the three categories, should therefore not be construed as limiting in any manner. Any number of severity levels, categories and preemptive actions may be used.
- In addition, it should be understood that while much of the discussion above was provided in the context of a platoon including only two vehicles, again this should not be construed as a limitation of any kind. On the contrary, the gap control and risk mitigation or avoidance, as described herein, is applicable to platooning involving any number of vehicles, regardless of vehicle type.
- In yet other embodiments, the vehicles involved platooning and/or and risk mitigation or avoidance can be autonomous, semi-autonomous, or driven by a driver, or any combination thereof.
- Pre-cognitive braking is one particular pre-emptive action that can be used to mitigate or avoid risks due to hazards encountered by platooning vehicles. With pre-cognitive braking, when a
lead vehicle 802 issues a brake command, the following vehicle(s) 804 is/are immediately informed, so that the following vehicle(s) 804 can take preemptive action, preferably before a change in speed of thefront vehicle 802 occurs. - Referring to
FIG. 14 , a pair ofvehicles gap 808 is illustrated. In this example, thelead vehicle 802 initiates a braking command In various embodiments, the braking action can be implemented or may result in a number of ways, such as but not limited to, the driver braking (i.e., pushing the brake pedal), an active cruise control system (ACC) initiating a braking action, or some other automated driving unit initiating the braking action. Regardless of the origin, abraking notice 1402 of the braking command is transmitted by thelead vehicle 802 to the followingvehicle 804. With the followingvehicle 804 aware of the braking event, the braking action of the two vehicles can be coordinated, avoiding or mitigating risks. - The notice information associated with the
braking event 1402 sent from thelead vehicle 802 to the followingvehicle 804 may widely vary. In different embodiments, the relayed information may include a simple brake command to more detailed information, such as brake application pressure, brake air supply reservoir pressure, engine torque, engine speed or RPMs, compression (Jake) brake application, accelerator pedal position, engine manifold air pressure (MAP), computed delivery torque, vehicle speed, system faults, battery voltage, radar or lidar data, or any combination thereof. Also, it should be understood that other information besides braking commands may be sent between thevehicles - The information pertaining to the
braking event 1402, as relayed via a data link established by thegateways 470 of thelead vehicle 802 and the followingvehicle 804. In various embodiments, the data link may be implemented using WiFi, one or more designated radio channels, Zigbee or any industry or agreed upon standard radio. The above list is merely exemplary. Any reliable, low latency data link may be used, having for instance, a latency of 10 milliseconds or less. - Pre-cognitive braking involves, as referred to above, the coordinated braking action between the
lead vehicle 802 and the followingvehicle 804. In some embodiments, the coordinated action involves initiating the braking of the followingvehicle 804 before the lead vehicle. In this way, the gap between the two vehicles grows and the two (or more vehicles) may each brake in a controlled, safe manner - Referring to
FIG. 15 , a diagram 1500 that plots the distance “D” of thegap 808 between the two vehicles over time while platooning is illustrated. Prior to a braking event by thelead vehicle 802, designated by 1502 in the plot, the gap distance D remains fairly constant, fluctuating only slightly as corrective action is taken by the vehicles to maintain the desired gap. When thebraking action 1502 occurs, the followingvehicle 804 is immediately notified via the data link. In this particular embodiment, the braking of the two vehicles is coordinated such that the followingvehicle 804 brakes (i.e., slows down) first before thelead vehicle 802. As a result, the gap grows as illustrated by the rise in theplot 808 after braking is initiated. - It should be understood that the aforementioned embodiment illustrated above is merely illustrative and should be in no way construed as limiting. In various alternative implementations, the braking behavior of the two vehicles can be controlled in a variety of ways. For instance, the two vehicles can begin braking at substantially the same time, but with the following vehicle braking harder than the lead vehicle. As a result, the rate at which the gap grows over time is increased as the following vehicle reduces its speed at a quicker rate. This is just one possible alternative. Many other braking strategies, as discussed in more detail below, may be used.
- Referring to
FIG. 16 , a flow chart 1600 illustrating the steps of pre-cognitive braking are illustrated. - In the initial step 1602, events are monitored at the
lead vehicle 802 to determine if a braking event has occurred. Again, as discussed above, a braking event may be detected in a number of ways and is not necessarily limited to the driver pushing the brake pedal. For instance, the braking event can be triggered by an active cruise control system (ACC) or some other automated driving unit initiating the braking action. - In step 1604, a notice of the detected braking event is communicated to the following
vehicle 804. The communication may take place over the communication link established between the gateways 407 of the two vehicles. In various embodiments, the communication includes a brake command along with possibly other information, such as brake application pressure, brake air supply reservoir pressure, engine torque, engine speed or RPMs, compression (Jake) brake application, accelerator pedal position, engine manifold air pressure (MAP), computed delivery torque, vehicle speed, system faults, battery voltage, radar or lidar data, or any combination thereof. - In optional step 1606, the following vehicle may implement a number of braking strategies. For instance, the braking at following vehicle may be timed to occur a few moments before the braking action of the lead vehicle. Alternatively, or in addition, the following vehicle may be controlled to reduce vehicle speed at a controlled rate that is more significant than the lead vehicle. As a result, the gap will widen as the two vehicles reduce their speed.
- Heavy vehicles, such as trucks or busses, typically rely on pneumatic or air brakes. These types of brakes use compressed air in a chamber, pressing on a piston, to apply pressure on to a brake pad that is used to brake or stop the vehicle. When braking while driving, the driver typically pushes the brake pedal, which forces air under pressure into the chamber, causing the piston to apply pressure to the brake, slowing the vehicle. With pneumatic brakes, the braking action may be delayed until there is adequate air pressure in the chamber.
- In one non-exclusive braking strategy, the following
vehicle 804 may in response to a receivedbraking notice 1402 begin to immediately pressurize its brake chamber(s) ahead of and/or more aggressively than thelead vehicle 802. As a result, the brakes may be applied by the followingvehicle 804 before thelead vehicle 802. - In yet other alternative embodiments, one or any combination of the above-listed parameters may be used to formulate a braking strategy for the following
vehicle 804. With this information, the rate of braking of the followingvehicle 804 can be calculated relative to thelead vehicle 802. For example, the velocity reduction of the followingvehicle 804 may be controlled to be (−0.1 to −2.0) meters per second relative to thelead vehicle 802. - In step 1608, the braking, including the use of any particular braking strategy, occurs with the following vehicle.
- In step 1610, the braking, including the use of any particular braking strategy, occurs with the lead vehicle after braking is initiated with the following vehicle in the previous step.
- Finally, the type of vehicles that may be used for platooning and/or risk mitigation or avoidance may widely vary and are not limited to exclusively trucks. On the contrary, the present invention contemplates that any vehicle class or type may be used, regardless if powered by a combustion engine, electric motor, fuel cells, or any other possible self-propulsion mechanism, including cars, trucks, buses, motorcycles, or any other self-propelled vehicle that is currently or may be developed in the future.
- Therefore, the present embodiments should be considered illustrative and not restrictive and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims (30)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/926,809 US20180210463A1 (en) | 2013-03-15 | 2018-03-20 | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
Applications Claiming Priority (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361792304P | 2013-03-15 | 2013-03-15 | |
PCT/US2014/030770 WO2014145918A1 (en) | 2013-03-15 | 2014-03-17 | Vehicle platooning systems and methods |
US201514855044A | 2015-09-15 | 2015-09-15 | |
US201662343819P | 2016-05-31 | 2016-05-31 | |
US201662363192P | 2016-07-15 | 2016-07-15 | |
US201662377970P | 2016-08-22 | 2016-08-22 | |
US15/589,124 US10481614B2 (en) | 2011-07-06 | 2017-05-08 | Vehicle platooning systems and methods |
US15/607,902 US10254764B2 (en) | 2016-05-31 | 2017-05-30 | Platoon controller state machine |
US201862638794P | 2018-03-05 | 2018-03-05 | |
US15/926,809 US20180210463A1 (en) | 2013-03-15 | 2018-03-20 | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/589,124 Continuation-In-Part US10481614B2 (en) | 2011-07-06 | 2017-05-08 | Vehicle platooning systems and methods |
Publications (1)
Publication Number | Publication Date |
---|---|
US20180210463A1 true US20180210463A1 (en) | 2018-07-26 |
Family
ID=64105711
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/926,813 Expired - Fee Related US10474166B2 (en) | 2011-07-06 | 2018-03-20 | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
US15/926,809 Abandoned US20180210463A1 (en) | 2013-03-15 | 2018-03-20 | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/926,813 Expired - Fee Related US10474166B2 (en) | 2011-07-06 | 2018-03-20 | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
Country Status (2)
Country | Link |
---|---|
US (2) | US10474166B2 (en) |
WO (1) | WO2018208372A2 (en) |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180186381A1 (en) * | 2016-08-22 | 2018-07-05 | Peloton Technology, Inc. | Applications for using mass estimations for vehicles |
US20190084537A1 (en) * | 2017-09-15 | 2019-03-21 | Bendix Commercial Vehicle Systems Llc | Braking controller and method using verification of reported trailer capabilities |
US10520952B1 (en) | 2011-07-06 | 2019-12-31 | Peloton Technology, Inc. | Devices, systems, and methods for transmitting vehicle data |
US10549739B2 (en) | 2017-09-15 | 2020-02-04 | Bendix Commercial Vehicle Systems Llc | Towing vehicle controller using trailer braking strategy and trailer braking control method |
US10549732B2 (en) | 2017-09-15 | 2020-02-04 | Bendix Commercial Vehicle Systems Llc | Towing vehicle controller using trailer braking strategy and trailer braking control method |
US20200160723A1 (en) * | 2018-11-21 | 2020-05-21 | Peloton Technology, Inc. | Systems and methods for managing tractor trailers |
US10732645B2 (en) | 2011-07-06 | 2020-08-04 | Peloton Technology, Inc. | Methods and systems for semi-autonomous vehicular convoys |
US10762791B2 (en) | 2018-10-29 | 2020-09-01 | Peloton Technology, Inc. | Systems and methods for managing communications between vehicles |
US10814844B2 (en) | 2017-09-15 | 2020-10-27 | Bendix Commercial Vehicle Systems Llc | Braking controller and method using verification of reported trailer capabilities |
US10899323B2 (en) | 2018-07-08 | 2021-01-26 | Peloton Technology, Inc. | Devices, systems, and methods for vehicle braking |
US11163317B2 (en) * | 2018-07-31 | 2021-11-02 | Honda Motor Co., Ltd. | System and method for shared autonomy through cooperative sensing |
US11161487B2 (en) * | 2019-08-15 | 2021-11-02 | Bendix Commercial Vehicle Systems Llc | System and method for controlling wheel brakes in a vehicle platooning with another vehicle |
US11173933B2 (en) * | 2019-11-15 | 2021-11-16 | Nxp B.V. | System and method for monitoring a moving vehicle |
US11181929B2 (en) | 2018-07-31 | 2021-11-23 | Honda Motor Co., Ltd. | System and method for shared autonomy through cooperative sensing |
US11290856B2 (en) | 2020-03-31 | 2022-03-29 | Toyota Motor North America, Inc. | Establishing connections in transports |
US11294396B2 (en) * | 2013-03-15 | 2022-04-05 | Peloton Technology, Inc. | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
US11328608B2 (en) * | 2017-03-28 | 2022-05-10 | Volvo Truck Corporation | Method for controlling the braking of a following vehicle of a string comprising a plurality of platooning vehicles |
US11334092B2 (en) | 2011-07-06 | 2022-05-17 | Peloton Technology, Inc. | Devices, systems, and methods for transmitting vehicle data |
US11360485B2 (en) | 2011-07-06 | 2022-06-14 | Peloton Technology, Inc. | Gap measurement for vehicle convoying |
US11427196B2 (en) | 2019-04-15 | 2022-08-30 | Peloton Technology, Inc. | Systems and methods for managing tractor-trailers |
SE545354C2 (en) * | 2018-09-04 | 2023-07-18 | Bosch Gmbh Robert | Vehicle control units, motor vehicles and method of operation of vehicle control units for time-synchronized braking |
US11735048B2 (en) | 2020-02-27 | 2023-08-22 | Toyota Motor North America, Inc. | Minimizing traffic signal delays with transports |
US11873000B2 (en) | 2020-02-18 | 2024-01-16 | Toyota Motor North America, Inc. | Gesture detection for transport control |
US12033502B2 (en) | 2020-03-31 | 2024-07-09 | Toyota Motor North America, Inc. | Traffic manager transports |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180211546A1 (en) * | 2015-08-26 | 2018-07-26 | Peloton Technology, Inc. | Devices, systems, and methods for authorization of vehicle platooning |
US10407035B1 (en) * | 2016-08-03 | 2019-09-10 | Apple Inc. | Integrated chassis control |
DE102017219665A1 (en) * | 2017-11-06 | 2019-05-09 | Robert Bosch Gmbh | Method for forming and coordinating at least one vehicle group |
US10647329B2 (en) * | 2017-12-12 | 2020-05-12 | Uatc, Llc | Disengaging autonomous control of vehicle |
US10698408B2 (en) * | 2018-08-30 | 2020-06-30 | Pony Ai Inc. | Distributed sensing for vehicle navigation |
US10971018B2 (en) * | 2018-11-30 | 2021-04-06 | Ford Global Technologies, Llc | Vehicular platoon subscription and management system |
CN109597414B (en) * | 2018-12-06 | 2022-03-18 | 英华达(上海)科技有限公司 | Driving system and method for average energy consumption of self-driving vehicle fleet |
KR20200083683A (en) * | 2018-12-14 | 2020-07-09 | 현대자동차주식회사 | Vehicle, Server communicating with the vehicle and method for controlling the same |
DE102019101443B4 (en) * | 2019-01-21 | 2023-07-20 | Knorr-Bremse Systeme für Nutzfahrzeuge GmbH | Method for controlling a convoy of vehicles during emergency braking |
EP3924948A4 (en) * | 2019-02-15 | 2022-08-17 | Lenovo (Beijing) Limited | Method and apparatus for managing a vehicle platoon |
US11367361B2 (en) * | 2019-02-22 | 2022-06-21 | Kyndryl, Inc. | Emulating unmanned aerial vehicle (UAV) |
US11320838B2 (en) * | 2019-10-09 | 2022-05-03 | Logan A. Lopez | Concerted autonomous vehicle collision avoidance |
JP2021082076A (en) * | 2019-11-20 | 2021-05-27 | ロベルト・ボッシュ・ゲゼルシャフト・ミト・ベシュレンクテル・ハフツングRobert Bosch Gmbh | Control system, control device, and control method |
CN114787010A (en) * | 2019-12-27 | 2022-07-22 | 英特尔公司 | Driving safety system |
US11973790B2 (en) * | 2020-11-10 | 2024-04-30 | Accenture Global Solutions Limited | Cyber digital twin simulator for automotive security assessment based on attack graphs |
KR20220082182A (en) * | 2020-12-09 | 2022-06-17 | 현대자동차주식회사 | Apparatus and method for avoiding rear collision in platooning of trailer vehicle |
JP2022099973A (en) * | 2020-12-23 | 2022-07-05 | ロベルト・ボッシュ・ゲゼルシャフト・ミト・ベシュレンクテル・ハフツング | Control device and control method of rider support system |
US20220410901A1 (en) * | 2021-06-28 | 2022-12-29 | GM Global Technology Operations LLC | Initializing early automatic lane change |
Citations (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5777451A (en) * | 1996-03-08 | 1998-07-07 | Nissan Diesel Motor Co., Ltd. | Vehicle longitudinal spacing controller |
US5781119A (en) * | 1995-03-14 | 1998-07-14 | Toyota Jidosha Kabushiki Kaisha | Vehicle guiding system |
US6032097A (en) * | 1996-11-27 | 2000-02-29 | Honda Giken Kogyo Kabushiki Kaisha | Vehicle platoon control system |
US6397149B1 (en) * | 1999-05-07 | 2002-05-28 | Honda Giken Kogyo Kabushiki Kaisha | Processional travel control apparatus |
US20020135507A1 (en) * | 2000-04-08 | 2002-09-26 | Hermann Winner | Method and device for controlling the distance from a vehicle to a preceding vehicle |
US6765495B1 (en) * | 2000-06-07 | 2004-07-20 | Hrl Laboratories, Llc | Inter vehicle communication system |
US20060195250A1 (en) * | 2005-02-28 | 2006-08-31 | Junichiro Kawaguchi | Method and a device for stabilization control of a vehicle traffic volume |
US20070032245A1 (en) * | 2005-08-05 | 2007-02-08 | Alapuranen Pertti O | Intelligent transportation system and method |
US20090079839A1 (en) * | 2006-06-19 | 2009-03-26 | Oshkosh Corporation | Vehicle diagnostics based on information communicated between vehicles |
US20100044998A1 (en) * | 2006-05-17 | 2010-02-25 | Eurolum | Wheeled vehicle, hitching method, unhitching method, method for managing said vehicles and resulting train of vehicles |
US20100191449A1 (en) * | 2007-07-30 | 2010-07-29 | Shouzou Iwamoto | Packet traffic control system |
US20100256852A1 (en) * | 2009-04-06 | 2010-10-07 | Gm Global Technology Operations, Inc. | Platoon vehicle management |
US20110093177A1 (en) * | 2009-10-21 | 2011-04-21 | Horn Berthold K P | Method and Apparatus for Reducing Motor Vehicle Traffic Flow Instabilities and Increasing Vehicle Throughput |
US20120323474A1 (en) * | 1998-10-22 | 2012-12-20 | Intelligent Technologies International, Inc. | Intra-Vehicle Information Conveyance System and Method |
US20130018766A1 (en) * | 2011-07-12 | 2013-01-17 | Edwin Roy Christman | Minimalist approach to roadway electrification |
US20130030606A1 (en) * | 2011-07-25 | 2013-01-31 | GM Global Technology Operations LLC | Autonomous convoying technique for vehicles |
US20130041567A1 (en) * | 2011-08-10 | 2013-02-14 | Denso Corporation | Travel support apparatus and travel support system |
US20130041576A1 (en) * | 2011-07-06 | 2013-02-14 | Joshua P. Switkes | Systems and Methods for Semi-Autonomous Convoying of Vehicles |
US20130211624A1 (en) * | 2010-05-31 | 2013-08-15 | Volvo Car Corporation | Control system for travel in a platoon |
US20140005906A1 (en) * | 2012-06-28 | 2014-01-02 | Toyota Motor Engineering & Manufacturing | Preceding vehicle state prediction |
US20140136044A1 (en) * | 2012-11-15 | 2014-05-15 | GM Global Technology Operations LLC | Active safety system and method for operating the same |
US20140172265A1 (en) * | 2012-12-19 | 2014-06-19 | Denso Corporation | Vehicle to vehicle communication device and convoy travel control device |
US20140210645A1 (en) * | 2013-01-30 | 2014-07-31 | Wavetronix Llc | Traffic flow through an intersection by reducing platoon interference |
US20140316671A1 (en) * | 2013-04-17 | 2014-10-23 | Denso Corporation | Platoon travel system |
US20150154871A1 (en) * | 2013-12-04 | 2015-06-04 | Volvo Car Corporation | Method and control system for controlling movement of a group of road vehicles |
US20150274161A1 (en) * | 2012-09-14 | 2015-10-01 | Robert Bosch Gmbh | Method for operating a driver assistance system of a vehicle |
US20160039412A1 (en) * | 2013-04-19 | 2016-02-11 | Continental Teves Ag & Co. Ohg | Method and system for preventing a following vehicle from driving up on a vehicle driving directly in front and use of the system |
US20160297447A1 (en) * | 2013-10-11 | 2016-10-13 | Nissan Motor Co., Ltd. | Travel Control Device and Travel Control Method |
US9511764B2 (en) * | 2014-02-28 | 2016-12-06 | Ford Global Technologies, Llc | Semi-autonomous mode control |
US20170168503A1 (en) * | 2015-12-11 | 2017-06-15 | Avishtech, Llc | Autonomous vehicle towing system and method |
US20170227972A1 (en) * | 2014-10-21 | 2017-08-10 | Road Trains Llc | Platooning control via accurate synchronization |
US20180032072A1 (en) * | 2016-07-28 | 2018-02-01 | Lytx, Inc. | Determining driver engagement with autonomous vehicle |
US20180137763A1 (en) * | 2015-02-26 | 2018-05-17 | Volvo Truck Corporation | Method of controlling inter-vehicle gap(s) in a platoon |
US20190171226A1 (en) * | 2017-12-01 | 2019-06-06 | Hyundai Motor Company | Platooning control apparatus and method therefor |
US20190220037A1 (en) * | 2018-01-12 | 2019-07-18 | Toyota Motor Engineering & Manufacturing North America, Inc. | Responsibilities and agreement acceptance for vehicle platooning |
Family Cites Families (295)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3725921A (en) | 1970-11-04 | 1973-04-03 | Bendix Corp | Traffic responsive speed control system |
JPS5141849A (en) | 1974-10-04 | 1976-04-08 | Matsushita Electric Ind Co Ltd | DENGENSOCHI |
US4370718A (en) | 1979-02-06 | 1983-01-25 | Chasek Norman E | Responsive traffic light control system and method based on conservation of aggregate momentum |
US5295551A (en) | 1986-03-06 | 1994-03-22 | Josef Sukonick | System for the cooperative driving of two or more vehicles |
KR940001633B1 (en) | 1990-01-17 | 1994-02-28 | 미쯔비시 덴끼 가부시끼가이샤 | Following control apparatus for an automotive vehicle |
JP2995970B2 (en) | 1991-12-18 | 1999-12-27 | トヨタ自動車株式会社 | Travel control device for vehicles |
US5331561A (en) | 1992-04-23 | 1994-07-19 | Alliant Techsystems Inc. | Active cross path position correlation device |
WO1995027964A1 (en) | 1994-04-12 | 1995-10-19 | Qualcomm Incorporated | Method and apparatus for freight transportation using a satellite navigation system |
US5572449A (en) | 1994-05-19 | 1996-11-05 | Vi&T Group, Inc. | Automatic vehicle following system |
JPH08314540A (en) | 1995-03-14 | 1996-11-29 | Toyota Motor Corp | Vehicle travel guide system |
US6720920B2 (en) * | 1997-10-22 | 2004-04-13 | Intelligent Technologies International Inc. | Method and arrangement for communicating between vehicles |
US7629899B2 (en) * | 1997-10-22 | 2009-12-08 | Intelligent Technologies International, Inc. | Vehicular communication arrangement and method |
US7418346B2 (en) * | 1997-10-22 | 2008-08-26 | Intelligent Technologies International, Inc. | Collision avoidance methods and systems |
US6370475B1 (en) * | 1997-10-22 | 2002-04-09 | Intelligent Technologies International Inc. | Accident avoidance system |
US5633456A (en) | 1995-08-04 | 1997-05-27 | Chrysler Corporation | Engine misfire detection with digital filtering |
JP3358403B2 (en) | 1995-09-11 | 2002-12-16 | トヨタ自動車株式会社 | Platoon running control device |
US6125321A (en) | 1996-06-07 | 2000-09-26 | Toyota Jidosha Kabushiki Kaisha | Motor vehicle drive system controller and automatic drive controller |
US20080154629A1 (en) * | 1997-10-22 | 2008-06-26 | Intelligent Technologies International, Inc. | Vehicle Speed Control Method and Arrangement |
US20080147253A1 (en) * | 1997-10-22 | 2008-06-19 | Intelligent Technologies International, Inc. | Vehicular Anticipatory Sensor System |
DE19849583B4 (en) | 1997-10-27 | 2009-06-18 | Nissan Motor Co., Ltd., Yokohama-shi | System and method for controlling a distance between vehicles |
US6167357A (en) | 1998-04-23 | 2000-12-26 | Cummins Engine Company, Inc. | Recursive vehicle mass estimation |
JP2000085407A (en) | 1998-07-17 | 2000-03-28 | Denso Corp | Vehicle-to-vehicle control device and recording medium |
US6418370B1 (en) | 1998-08-04 | 2002-07-09 | Denso Corporation | Apparatus and method for controlling a target distance and a warning distance between traveling vehicles and a recording medium for storing the control method |
DE19837380A1 (en) | 1998-08-18 | 2000-02-24 | Zahnradfabrik Friedrichshafen | Method to determine mass of vehicle; involves obtaining measurements to determine traction force variable and movement variable |
EP0982173A2 (en) | 1998-08-27 | 2000-03-01 | Eaton Corporation | Method for determination of an optimum vehicle cruise separation distance |
JP2000113400A (en) | 1998-09-30 | 2000-04-21 | Honda Motor Co Ltd | Automatic tracking travel system |
DE10017279A1 (en) | 1999-04-09 | 2000-10-12 | Bosch Gmbh Robert | Automatic guidance system for vehicle in traffic congestion performs left-right steering and distance maintenance, while giving driver priority to override automatic functions |
JP2000311291A (en) | 1999-04-27 | 2000-11-07 | Honda Motor Co Ltd | Convoy travel controller |
DE10024739A1 (en) | 1999-05-21 | 2000-12-07 | Honda Motor Co Ltd | Vehicle convoy travel mode control device transmits request to join existing convoy or break away from convoy to convoy lead vehicle and switches between manual and automatic control modes upon request recognition |
JP4082831B2 (en) | 1999-10-26 | 2008-04-30 | 株式会社小松製作所 | Vehicle control device |
US6604038B1 (en) | 1999-11-09 | 2003-08-05 | Power Talk, Inc. | Apparatus, method, and computer program product for establishing a remote data link with a vehicle with minimal data transmission delay |
US6510381B2 (en) | 2000-02-11 | 2003-01-21 | Thomas L. Grounds | Vehicle mounted device and a method for transmitting vehicle position data to a network-based server |
US7835864B1 (en) | 2000-02-20 | 2010-11-16 | Dale F. Oexmann | Vehicle proximity detection and control systems |
US6345603B1 (en) | 2000-04-11 | 2002-02-12 | Visteon Global Technologies, Inc. | Throttle control for vehicle using redundant throttle signals |
WO2002044957A1 (en) | 2000-11-30 | 2002-06-06 | Pirelli Pneumatici S.P.A. | System and method for monitoring tyres |
JP2002190091A (en) | 2000-12-20 | 2002-07-05 | Pioneer Electronic Corp | Traveling time setting method and device, method and device for calculating route using it |
US6898585B2 (en) | 2001-02-02 | 2005-05-24 | University Of Illinois | Fuzzy logic method for adaptively evaluating the validity of sensor data |
JP3838048B2 (en) | 2001-04-16 | 2006-10-25 | 日産自動車株式会社 | Vehicle travel control device |
JP4703917B2 (en) | 2001-09-10 | 2011-06-15 | コマツレンタル株式会社 | Rental system and rental business support method |
US6680548B2 (en) | 2001-11-20 | 2004-01-20 | Luxon Energy Devices Corporation | Electronic timers using supercapacitors |
US20130317676A1 (en) | 2012-05-23 | 2013-11-28 | Jared Klineman Cooper | System and method for inspecting a route during movement of a vehicle system over the route |
US9917773B2 (en) | 2008-08-04 | 2018-03-13 | General Electric Company | Data communication system and method |
US6963795B2 (en) | 2002-07-16 | 2005-11-08 | Honeywell Interntaional Inc. | Vehicle position keeping system |
JP4076071B2 (en) | 2002-08-19 | 2008-04-16 | アルパイン株式会社 | Communication method and vehicle communication apparatus between moving bodies |
US7104617B2 (en) | 2002-09-06 | 2006-09-12 | Ford Motor Company | Independent braking and controllability control method and system for a vehicle with regenerative braking |
US6882923B2 (en) | 2002-10-17 | 2005-04-19 | Ford Global Technologies, Llc | Adaptive cruise control system using shared vehicle network data |
EP1555511A4 (en) | 2002-10-22 | 2011-12-21 | Hitachi Ltd | Map data delivering method for communication-type navigation system |
JP2004217175A (en) | 2003-01-17 | 2004-08-05 | Toyota Motor Corp | Vehicle-to-vehicle distance control device |
WO2004077378A1 (en) | 2003-02-25 | 2004-09-10 | Philips Intellectual Property & Standards Gmbh | Method and system for leading a plurality of vehicles |
US6975246B1 (en) | 2003-05-13 | 2005-12-13 | Itt Manufacturing Enterprises, Inc. | Collision avoidance using limited range gated video |
JP2004348430A (en) | 2003-05-22 | 2004-12-09 | Pioneer Electronic Corp | Urgent braking alarm in vehicle, transmission device for urgent braking information, server device, and urgent braking alarm system and method |
US7660436B2 (en) | 2003-06-13 | 2010-02-09 | Sarnoff Corporation | Stereo-vision based imminent collision detection |
DE10350276A1 (en) * | 2003-10-28 | 2005-06-02 | Robert Bosch Gmbh | Device for fatigue warning in motor vehicles with distance warning system |
US7299130B2 (en) | 2003-12-12 | 2007-11-20 | Advanced Ceramic Research, Inc. | Unmanned vehicle |
EP1734339B1 (en) | 2004-03-29 | 2012-12-19 | Hitachi, Ltd. | Navigation system and course guiding method |
WO2006018944A1 (en) | 2004-08-18 | 2006-02-23 | Nissan Diesel Motor Co., Ltd. | Fuel consumption evaluation system |
KR101111099B1 (en) | 2004-09-09 | 2012-02-17 | 아바야 테크놀러지 코퍼레이션 | Methods of and systems for network traffic security |
US8903617B2 (en) | 2004-10-05 | 2014-12-02 | Vision Works Ip Corporation | Absolute acceleration sensor for use within moving vehicles |
JP2006131055A (en) | 2004-11-04 | 2006-05-25 | Denso Corp | Vehicle traveling controlling device |
DE602005001841T2 (en) | 2005-01-14 | 2008-04-17 | Alcatel Lucent | navigation service |
WO2007084147A2 (en) | 2005-02-02 | 2007-07-26 | Raytheon Company | System for situational awareness |
US7593811B2 (en) | 2005-03-31 | 2009-09-22 | Deere & Company | Method and system for following a lead vehicle |
US8442735B2 (en) | 2005-06-15 | 2013-05-14 | Ford Global Technologies, Llc | Traction control system and method |
US7894982B2 (en) | 2005-08-01 | 2011-02-22 | General Motors Llc | Method and system for linked vehicle navigation |
US7729857B2 (en) | 2005-08-18 | 2010-06-01 | Gm Global Technology Operations, Inc. | System for and method of detecting a collision and predicting a vehicle path |
US20070233337A1 (en) | 2005-09-14 | 2007-10-04 | Plishner Paul J | Semi-autonomous guidance system for a vehicle |
US7460951B2 (en) | 2005-09-26 | 2008-12-02 | Gm Global Technology Operations, Inc. | System and method of target tracking using sensor fusion |
FI120191B (en) | 2005-10-03 | 2009-07-31 | Sandvik Tamrock Oy | A method for driving mining vehicles in a mine and a transportation system |
US20070083318A1 (en) | 2005-10-07 | 2007-04-12 | Parikh Jayendra S | Adaptive cruise control using vehicle-to-vehicle wireless communication |
JP4720457B2 (en) | 2005-11-22 | 2011-07-13 | アイシン・エィ・ダブリュ株式会社 | Vehicle driving support method and driving support device |
US8000874B2 (en) | 2006-03-10 | 2011-08-16 | Nissan Motor Co., Ltd. | Vehicle headway maintenance assist system and method |
US7876258B2 (en) | 2006-03-13 | 2011-01-25 | The Boeing Company | Aircraft collision sense and avoidance system and method |
US7425903B2 (en) | 2006-04-28 | 2008-09-16 | International Business Machines Corporation | Dynamic vehicle grid infrastructure to allow vehicles to sense and respond to traffic conditions |
US20080258890A1 (en) | 2006-05-22 | 2008-10-23 | Todd Follmer | System and Method for Remotely Deactivating a Vehicle |
US9067565B2 (en) | 2006-05-22 | 2015-06-30 | Inthinc Technology Solutions, Inc. | System and method for evaluating driver behavior |
JP4579191B2 (en) | 2006-06-05 | 2010-11-10 | 本田技研工業株式会社 | Collision avoidance system, program and method for moving object |
WO2007143756A2 (en) | 2006-06-09 | 2007-12-13 | Carnegie Mellon University | System and method for autonomously convoying vehicles |
US8139109B2 (en) | 2006-06-19 | 2012-03-20 | Oshkosh Corporation | Vision system for an autonomous vehicle |
JP5507243B2 (en) | 2006-06-30 | 2014-05-28 | コンチネンタル・テベス・アーゲー・ウント・コンパニー・オーハーゲー | Method, apparatus, computer program, and computer program product for transmitting vehicle related information in and from a vehicle |
US7554435B2 (en) | 2006-09-07 | 2009-06-30 | Nissan Technical Center North America, Inc. | Vehicle on-board unit |
EP2086809A1 (en) | 2006-10-13 | 2009-08-12 | Continental Teves AG & CO. OHG | System for reducing the braking distance of a vehicle |
US9037388B2 (en) | 2006-11-17 | 2015-05-19 | Mccrary Personal Transport System, Llc | Intelligent public transit system using dual-mode vehicles |
US8532862B2 (en) | 2006-11-29 | 2013-09-10 | Ryan A. Neff | Driverless vehicle |
JP5130079B2 (en) | 2007-02-28 | 2013-01-30 | 株式会社デンソーアイティーラボラトリ | Electronic scanning radar apparatus and receiving array antenna |
ATE426878T1 (en) | 2007-03-26 | 2009-04-15 | Bay Zoltan Alkalmazott Kutatas | SYSTEM AND METHOD FOR DISTRIBUTING TRAFFIC DATA FROM VEHICLE TO VEHICLE USING RADIO WAVES |
US20080249667A1 (en) | 2007-04-09 | 2008-10-09 | Microsoft Corporation | Learning and reasoning to enhance energy efficiency in transportation systems |
US8326473B2 (en) | 2007-07-06 | 2012-12-04 | University of Pittsburgh—of the Commonwealth System of Higher Education | Powered vehicle convoying systems and methods of convoying powered vehicles |
DE102007040165A1 (en) | 2007-08-21 | 2009-02-26 | Siemens Ag | Method for operating a vehicle association, communication equipment, traction vehicle, vehicle and vehicle association |
US20090051510A1 (en) | 2007-08-21 | 2009-02-26 | Todd Follmer | System and Method for Detecting and Reporting Vehicle Damage |
US20100194638A1 (en) | 2007-08-27 | 2010-08-05 | Qualcomm Incorporated | Gnss receiver with wireless interface |
US20090062974A1 (en) | 2007-09-03 | 2009-03-05 | Junichi Tamamoto | Autonomous Mobile Robot System |
DE102007046763A1 (en) | 2007-09-28 | 2009-04-09 | Robert Bosch Gmbh | Control procedure and system |
DE102007058192A1 (en) | 2007-12-04 | 2009-06-10 | Continental Teves Ag & Co. Ohg | Central control unit for several assistance systems and motor vehicles provided in a motor vehicle (because of unrecognized priority) |
US20090157461A1 (en) | 2007-12-12 | 2009-06-18 | Honeywell International Inc. | Vehicle deployment planning system |
US8090517B2 (en) | 2007-12-19 | 2012-01-03 | Nissan Motor Co., Ltd. | Inter-vehicle distance maintenance supporting system and method |
GB0802212D0 (en) | 2008-02-06 | 2008-03-12 | Meritor Heavy Vehicle Braking | A brake system and method |
US8285456B2 (en) | 2008-02-29 | 2012-10-09 | Caterpillar Inc. | System for controlling a multimachine caravan |
US8078376B2 (en) | 2008-04-28 | 2011-12-13 | General Electric Company | System and method for verifying the availability of a level of a braking system in a powered system |
DE102008001841A1 (en) | 2008-05-19 | 2009-11-26 | Zf Friedrichshafen Ag | A method for driving a lock-up clutch in a hydrodynamic torque transmission device |
KR101463250B1 (en) | 2008-05-26 | 2014-11-18 | 주식회사 포스코 | Method for platooning of vehicles in an automated vehicle system |
FR2931984B1 (en) | 2008-06-02 | 2014-12-12 | Airbus France | METHOD AND APPARATUS FOR GENERATING A CONTROLLED SPEED FOR AN AIRCRAFT RUNNING ON THE GROUND WITHIN AN AIRCRAFT CONVOY. |
US20090326799A1 (en) | 2008-06-25 | 2009-12-31 | Expresspass Systems, Inc. | Distributed Route Segment Maintenance and Hierarchical Routing Based on Physical Vehicle Criteria |
EP2306423B1 (en) | 2008-07-10 | 2013-04-10 | Mitsubishi Electric Corporation | Train-of-vehicle travel support device |
JP2010030525A (en) | 2008-07-30 | 2010-02-12 | Toyota Motor Corp | Travel support device |
AU2008229680B2 (en) | 2008-08-20 | 2014-05-29 | Autonomous Solutions, Inc. | Follower vehicle control system and method for forward and reverse convoy movement |
EP2159779B1 (en) | 2008-08-27 | 2013-01-16 | Saab Ab | Using image sensor and tracking filter time-to-go to avoid mid-air collisions |
US8195358B2 (en) | 2008-09-11 | 2012-06-05 | Deere & Company | Multi-vehicle high integrity perception |
US20100082179A1 (en) | 2008-09-29 | 2010-04-01 | David Kronenberg | Methods for Linking Motor Vehicles to Reduce Aerodynamic Drag and Improve Fuel Economy |
US8126642B2 (en) | 2008-10-24 | 2012-02-28 | Gray & Company, Inc. | Control and systems for autonomously driven vehicles |
FR2939113B1 (en) | 2008-12-01 | 2012-07-06 | Thomas Petalas | SYSTEM FOR AUTOMATICALLY PLACING LOADS |
EP2390857B1 (en) | 2009-01-20 | 2013-07-03 | Toyota Jidosha Kabushiki Kaisha | Row-running control system and vehicle |
WO2010097943A1 (en) | 2009-02-27 | 2010-09-02 | トヨタ自動車株式会社 | Vehicle relative position estimation apparatus and vehicle relative position estimation method |
WO2010101749A1 (en) | 2009-03-05 | 2010-09-10 | Massachusetts Institute Of Technology | Predictive semi-autonomous vehicle navigation system |
US8224551B2 (en) | 2009-03-24 | 2012-07-17 | Bendix Commercial Vehicle Systems Llc | ACC extended mode operation |
US8380362B2 (en) | 2009-07-10 | 2013-02-19 | The Boeing Company | Systems and methods for remotely collaborative vehicles |
US8397063B2 (en) | 2009-10-07 | 2013-03-12 | Telcordia Technologies, Inc. | Method for a public-key infrastructure for vehicular networks with limited number of infrastructure servers |
US9457810B2 (en) | 2009-10-21 | 2016-10-04 | Berthold K. P. Horn | Method and apparatus for reducing motor vehicle traffic flow instabilities and increasing vehicle throughput |
US8738238B2 (en) | 2009-11-12 | 2014-05-27 | Deere & Company | Coordination of vehicle movement in a field |
WO2011082948A2 (en) | 2009-12-14 | 2011-07-14 | Continental Automotive Gmbh | Method for communicating between a first motor vehicle and at least one second motor vehicle |
JP5503961B2 (en) | 2009-12-25 | 2014-05-28 | 株式会社デンソーアイティーラボラトリ | Observation signal processor |
US8618922B2 (en) | 2010-03-30 | 2013-12-31 | GM Global Technology Operations LLC | Method and system for ensuring operation of limited-ability autonomous driving vehicles |
US9145137B2 (en) | 2010-04-07 | 2015-09-29 | Toyota Jidosha Kabushiki Kaisha | Vehicle driving-support apparatus |
JP5585177B2 (en) | 2010-04-12 | 2014-09-10 | トヨタ自動車株式会社 | Leading vehicle position determination device |
AT11551U3 (en) | 2010-07-12 | 2011-05-15 | Avl List Gmbh | Method for testing a vehicle and a test vehicle with an active secondary vehicle |
JP5494332B2 (en) | 2010-07-27 | 2014-05-14 | トヨタ自動車株式会社 | Vehicle control system |
JP5573461B2 (en) | 2010-07-27 | 2014-08-20 | トヨタ自動車株式会社 | Vehicle control system |
US9129523B2 (en) | 2013-05-22 | 2015-09-08 | Jaybridge Robotics, Inc. | Method and system for obstacle detection for vehicles using planar sensor data |
DE102010042048B4 (en) | 2010-10-06 | 2020-11-12 | Robert Bosch Gmbh | Device and method for assisting a driver of a motor vehicle in a driving maneuver |
US20160194014A1 (en) | 2010-11-17 | 2016-07-07 | General Electric Company | Vehicular data communication systems |
CN102803979A (en) | 2010-12-06 | 2012-11-28 | 科达汽车公司 | Electrochemical cell monitoring and balancing circuit with self-diagnostic feature |
US8510012B2 (en) | 2010-12-22 | 2013-08-13 | Bendix Commercial Vehicle Systems Llc | Anti-tailgating system and method |
US8624764B2 (en) | 2011-02-11 | 2014-01-07 | Analog Devices, Inc. | Test circuits and methods for redundant electronic systems |
FR2972066B1 (en) | 2011-02-28 | 2022-06-17 | Eurocopter France | METHOD FOR OPTIMIZING THE LOADING OF CARRIAGES INTO A VEHICLE |
WO2012117057A1 (en) | 2011-03-01 | 2012-09-07 | Continental Teves Ag & Co. Ohg | Safety device for motor vehicle and method for operating a motor vehicle |
US8887022B2 (en) | 2011-03-04 | 2014-11-11 | Infineon Technologies Austria Ag | Reliable data transmission with reduced bit error rate |
DE102011002275B4 (en) | 2011-04-27 | 2023-08-31 | Dr. Ing. H.C. F. Porsche Aktiengesellschaft | Method for predicting the driving behavior of a vehicle driving ahead |
WO2013006826A2 (en) | 2011-07-06 | 2013-01-10 | Peloton Technology Inc. | Systems and methods for semi-autonomous vehicular convoying |
US10520581B2 (en) | 2011-07-06 | 2019-12-31 | Peloton Technology, Inc. | Sensor fusion for autonomous or partially autonomous vehicle control |
US9645579B2 (en) | 2011-07-06 | 2017-05-09 | Peloton Technology, Inc. | Vehicle platooning systems and methods |
WO2018039134A1 (en) | 2016-08-22 | 2018-03-01 | Peloton Technology, Inc. | Automated connected vehicle control system architecture |
JP5565385B2 (en) | 2011-07-16 | 2014-08-06 | 株式会社デンソー | VEHICLE WIRELESS COMMUNICATION DEVICE AND COMMUNICATION SYSTEM |
JP5533810B2 (en) | 2011-07-23 | 2014-06-25 | 株式会社デンソー | Follow-up control device |
US9014915B2 (en) | 2011-07-25 | 2015-04-21 | GM Global Technology Operations LLC | Active safety control for vehicles |
US8554468B1 (en) | 2011-08-12 | 2013-10-08 | Brian Lee Bullock | Systems and methods for driver performance assessment and improvement |
JP5786941B2 (en) | 2011-08-25 | 2015-09-30 | 日産自動車株式会社 | Autonomous driving control system for vehicles |
JP5440579B2 (en) | 2011-09-27 | 2014-03-12 | 株式会社デンソー | Convoy travel device |
JP5472248B2 (en) | 2011-09-27 | 2014-04-16 | 株式会社デンソー | Convoy travel device |
JP2013073360A (en) | 2011-09-27 | 2013-04-22 | Denso Corp | Platoon driving device |
US8510029B2 (en) | 2011-10-07 | 2013-08-13 | Southwest Research Institute | Waypoint splining for autonomous vehicle following |
WO2013076136A1 (en) | 2011-11-21 | 2013-05-30 | Continental Teves Ag & Co. Ohg | Method and device for the position determination of objects by means of communication signals, and use of the device |
US9771070B2 (en) | 2011-12-09 | 2017-09-26 | GM Global Technology Operations LLC | Method and system for controlling a host vehicle |
US9187118B2 (en) | 2011-12-30 | 2015-11-17 | C & P Technologies, Inc. | Method and apparatus for automobile accident reduction using localized dynamic swarming |
WO2013109656A1 (en) | 2012-01-16 | 2013-07-25 | Maxim Integrated Products, Inc. | Method and apparatus for differential communications |
DE102012002695B4 (en) | 2012-02-14 | 2024-08-01 | Zf Cv Systems Hannover Gmbh | Procedure for determining an emergency braking situation of a vehicle |
US8620517B2 (en) | 2012-02-21 | 2013-12-31 | Toyota Mototr Engineering & Manufacturing North America, Inc. | Vehicular platooning using distributed receding horizon control |
EP2637072B1 (en) | 2012-03-05 | 2017-10-11 | Volvo Car Corporation | Path following of a target vehicle |
US20140310610A1 (en) | 2013-04-15 | 2014-10-16 | Flextronics Ap, Llc | Vehicle occupant impairment assisted vehicle |
US8457827B1 (en) | 2012-03-15 | 2013-06-04 | Google Inc. | Modifying behavior of autonomous vehicle based on predicted behavior of other vehicles |
US8880272B1 (en) | 2012-03-16 | 2014-11-04 | Google Inc. | Approach for estimating the geometry of roads and lanes by using vehicle trajectories |
SE537447C2 (en) | 2012-03-27 | 2015-05-05 | Scania Cv Ab | Device and method for streamlining fuel utilization during the speed of a vehicle |
SE1250443A1 (en) | 2012-05-03 | 2013-11-04 | Scania Cv Ab | Support system and method for forming vehicle trains |
US9669828B2 (en) | 2012-06-01 | 2017-06-06 | Toyota Motor Engineering & Manufacturing North America, Inc. | Cooperative driving and collision avoidance by distributed receding horizon control |
GB201210059D0 (en) | 2012-06-07 | 2012-07-25 | Jaguar Cars | Powertrain control system and method |
SE536549C2 (en) | 2012-06-14 | 2014-02-11 | Scania Cv Ab | System and method for assisting a vehicle in overtaking a vehicle train |
EP2685338B1 (en) | 2012-07-12 | 2018-04-11 | Volvo Car Corporation | Apparatus and method for lateral control of a host vehicle during travel in a vehicle platoon |
US10737665B2 (en) * | 2012-08-28 | 2020-08-11 | Ford Global Technologies, Llc | Vehicle braking based on external object communications |
SE537958C2 (en) | 2012-09-24 | 2015-12-08 | Scania Cv Ab | Procedure, measuring device and control unit for adapting vehicle train control |
US9221396B1 (en) | 2012-09-27 | 2015-12-29 | Google Inc. | Cross-validating sensors of an autonomous vehicle |
JP5668741B2 (en) | 2012-10-04 | 2015-02-12 | 株式会社デンソー | Convoy travel device |
JP6015329B2 (en) | 2012-10-11 | 2016-10-26 | 株式会社デンソー | Convoy travel system and convoy travel device |
SE1251163A1 (en) | 2012-10-15 | 2014-04-16 | Scania Cv Ab | System and method in connection with the occurrence of vehicle trains |
WO2014060117A1 (en) | 2012-10-17 | 2014-04-24 | Toll Collect Gmbh | Method and devices for collecting a traffic-related toll fee |
US20140129075A1 (en) | 2012-11-05 | 2014-05-08 | Dennis M. Carleton | Vehicle Control Using Modeled Swarming Behavior |
US8983714B2 (en) | 2012-11-16 | 2015-03-17 | Robert Bosch Gmbh | Failsafe communication system and method |
US9776587B2 (en) | 2012-11-29 | 2017-10-03 | Here Global B.V. | Method and apparatus for causing a change in an action of a vehicle for safety |
US9026282B2 (en) | 2012-11-30 | 2015-05-05 | Electro-Motive Diesel, Inc. | Two-tiered hierarchically distributed locomotive control system |
SE1251407A1 (en) | 2012-12-12 | 2014-06-13 | Scania Cv Ab | Device and method for evaluation of forward speed including vehicle train formation |
EP2934938B1 (en) | 2012-12-19 | 2022-09-07 | Volvo Truck Corporation | Method and arrangement for determining the speed behaviour of a leading vehicle |
US9659492B2 (en) | 2013-01-11 | 2017-05-23 | Here Global B.V. | Real-time vehicle spacing control |
US9367065B2 (en) | 2013-01-25 | 2016-06-14 | Google Inc. | Modifying behavior of autonomous vehicles based on sensor blind spots and limitations |
US9102406B2 (en) | 2013-02-15 | 2015-08-11 | Disney Enterprises, Inc. | Controlling unmanned aerial vehicles as a flock to synchronize flight in aerial displays |
KR101500060B1 (en) | 2013-02-26 | 2015-03-06 | 현대자동차주식회사 | Vehicle apparatus and system for controlling group driving, and method for selecting preceding vehicle using the same |
WO2014133425A1 (en) | 2013-02-27 | 2014-09-04 | Volvo Truck Corporation | System and method for determining an aerodynamically favorable position between ground traveling vehicles |
SE537259C2 (en) | 2013-03-06 | 2015-03-17 | Scania Cv Ab | Device and procedure for increased road safety in vehicle trains |
SE537446C2 (en) | 2013-03-06 | 2015-05-05 | Scania Cv Ab | Device and method of communication of vehicle trains |
US9740178B2 (en) | 2013-03-14 | 2017-08-22 | GM Global Technology Operations LLC | Primary controller designation in fault tolerant systems |
WO2014172322A1 (en) | 2013-04-15 | 2014-10-23 | Flextronics Ap, Llc | Vehicle intruder alert detection and indication |
US20140309836A1 (en) | 2013-04-16 | 2014-10-16 | Neya Systems, Llc | Position Estimation and Vehicle Control in Autonomous Multi-Vehicle Convoys |
JP5737316B2 (en) | 2013-04-17 | 2015-06-17 | 株式会社デンソー | Convoy travel system |
EP2799902A1 (en) | 2013-04-30 | 2014-11-05 | Baselabs GmbH | Method and apparatus for the tracking of multiple objects |
US9254846B2 (en) | 2013-05-03 | 2016-02-09 | Google Inc. | Predictive reasoning for controlling speed of a vehicle |
US9233697B2 (en) | 2013-05-24 | 2016-01-12 | General Electric Company | Method and system for controlling a vehicle system factoring mass attributable to weather |
US9043056B2 (en) | 2013-07-08 | 2015-05-26 | Disney Enterprises, Inc. | Method and system for using dynamic boundaries to manage the progression of ride vehicles that have rider control inputs |
US20150025917A1 (en) | 2013-07-15 | 2015-01-22 | Advanced Insurance Products & Services, Inc. | System and method for determining an underwriting risk, risk score, or price of insurance using cognitive information |
US9454150B2 (en) | 2013-07-17 | 2016-09-27 | Toyota Motor Engineering & Manufacturing North America, Inc. | Interactive automated driving system |
US9371002B2 (en) | 2013-08-28 | 2016-06-21 | Vision Works Ip Corporation | Absolute acceleration sensor for use within moving vehicles |
CN105579823B (en) | 2013-09-05 | 2018-09-18 | 克朗设备公司 | Dynamic operation person's behavior analyzer |
SE537985C2 (en) | 2013-09-30 | 2016-01-12 | Scania Cv Ab | System and method for regulating vehicle trains with a joint position-based driving strategy |
SE537482C2 (en) | 2013-09-30 | 2015-05-12 | Scania Cv Ab | Method and system for common driving strategy for vehicle trains |
SE537618C2 (en) | 2013-09-30 | 2015-08-04 | Scania Cv Ab | Method and system for common driving strategy for vehicle trains |
SE537469C2 (en) | 2013-09-30 | 2015-05-12 | Scania Cv Ab | A system and method for correcting map data and vehicle train position data |
SE537466C2 (en) | 2013-09-30 | 2015-05-12 | Scania Cv Ab | System and method for regulating a vehicle train with two different driving strategies |
SE537598C2 (en) | 2013-09-30 | 2015-07-14 | Scania Cv Ab | Method and system for organizing vehicle trains |
SE537603C2 (en) | 2013-09-30 | 2015-07-21 | Scania Cv Ab | Method and system for handling obstacles for vehicle trains |
SE537578C2 (en) | 2013-09-30 | 2015-06-30 | Scania Cv Ab | Control unit and method for controlling a vehicle in a vehicle train |
KR101909917B1 (en) | 2013-10-07 | 2018-10-19 | 한국전자통신연구원 | Apparatus and method for controlling autonomous vehicle platooning |
US9141112B1 (en) | 2013-10-16 | 2015-09-22 | Allstate Insurance Company | Caravan management |
US9174672B2 (en) | 2013-10-28 | 2015-11-03 | GM Global Technology Operations LLC | Path planning for evasive steering maneuver in presence of target vehicle and surrounding objects |
WO2015068501A1 (en) | 2013-11-08 | 2015-05-14 | 本田技研工業株式会社 | Convoy travel control device |
US9146561B2 (en) | 2013-12-03 | 2015-09-29 | King Fahd University Of Petroleum And Minerals | Robotic leader-follower navigation and fleet management control method |
JP6042794B2 (en) | 2013-12-03 | 2016-12-14 | 本田技研工業株式会社 | Vehicle control method |
US20150161894A1 (en) | 2013-12-05 | 2015-06-11 | Elwha Llc | Systems and methods for reporting characteristics of automatic-driving software |
US9406177B2 (en) | 2013-12-20 | 2016-08-02 | Ford Global Technologies, Llc | Fault handling in an autonomous vehicle |
US9355423B1 (en) | 2014-01-24 | 2016-05-31 | Allstate Insurance Company | Reward system related to a vehicle-to-vehicle communication system |
US9079587B1 (en) | 2014-02-14 | 2015-07-14 | Ford Global Technologies, Llc | Autonomous control in a dense vehicle environment |
SE538458C2 (en) | 2014-04-08 | 2016-07-12 | Scania Cv Ab | Method, apparatus and system comprising the apparatus for supporting the creation of vehicle trains |
US20150334371A1 (en) | 2014-05-19 | 2015-11-19 | Rockwell Automation Technologies, Inc. | Optical safety monitoring with selective pixel array analysis |
US20210133871A1 (en) | 2014-05-20 | 2021-05-06 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature usage recommendations |
WO2015179705A1 (en) | 2014-05-21 | 2015-11-26 | Quantum Fuel Systems Technologies Worldwide, Inc. | Enhanced compliance verification system |
CA2950136A1 (en) | 2014-05-23 | 2015-12-23 | Rochester Institute Of Technology | Method for optimizing asset value based on driver acceleration and braking behavior |
US9744970B2 (en) | 2014-07-14 | 2017-08-29 | Ford Global Technologies, Llc | Estimating a trailer road grade |
US9182764B1 (en) | 2014-08-04 | 2015-11-10 | Cummins, Inc. | Apparatus and method for grouping vehicles for cooperative driving |
FR3029662A1 (en) | 2014-12-03 | 2016-06-10 | Inst Nat Des Sciences Appliquees (Insa) | SIMULATION SYSTEM, DEVICES, METHODS AND PROGRAMS THEREFOR. |
CN107004346A (en) | 2014-12-05 | 2017-08-01 | 奥迪股份公司 | The method that the movement of the vehicle of fleet is formed for coordination |
US11107031B2 (en) | 2015-02-18 | 2021-08-31 | Ryder Integrated Logistics, Inc. | Vehicle fleet control systems and methods |
CN104717071B (en) | 2015-02-28 | 2018-01-05 | 深圳先进技术研究院 | Road train data authentication method for authenticating and car-mounted terminal |
US20170083844A1 (en) | 2015-04-01 | 2017-03-23 | Earthwave Technologies, Inc. | Systems, methods, and apparatus for efficient vehicle fleet tracking, deployment, and management |
EP3294599A4 (en) | 2015-05-11 | 2019-01-23 | Scania CV AB | Device, system and method for a platooning operation |
WO2016189495A1 (en) | 2015-05-27 | 2016-12-01 | Van Dyke, Marc | Alerting predicted accidents between driverless cars |
US9884631B2 (en) | 2015-06-04 | 2018-02-06 | Toyota Motor Engineering & Manufacturing North America, Inc. | Transitioning between operational modes of an autonomous vehicle |
DE102015211451A1 (en) | 2015-06-22 | 2017-01-05 | Volkswagen Aktiengesellschaft | Method for manipulation protection of user data packets to be transmitted via a bus system between system components |
US9944134B2 (en) | 2015-06-24 | 2018-04-17 | GM Global Technology Operations LLC | Integrated sensing unit and method for determining vehicle wheel speed and tire pressure |
US9449258B1 (en) | 2015-07-02 | 2016-09-20 | Agt International Gmbh | Multi-camera vehicle identification system |
US10115314B2 (en) | 2015-07-08 | 2018-10-30 | Magna Electronics Inc. | Lane change system for platoon of vehicles |
WO2017019595A1 (en) | 2015-07-27 | 2017-02-02 | Genghiscomm Holdings, LLC | Airborne relays in cooperative-mimo systems |
US9915051B2 (en) | 2015-09-01 | 2018-03-13 | Bahman Niroumand | Mandrel for forming an aggregate pier, and aggregate pier compacting system and method |
EP3353615A4 (en) | 2015-09-15 | 2019-04-10 | Peloton Technology Inc. | Vehicle identification and location using senor fusion and inter-vehicle communication |
WO2017048165A1 (en) | 2015-09-17 | 2017-03-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Communication device, first radio node, second radio node, and methods therein, for determining whether to allow a first vehicle to overtake a vehicle platoon |
US9823166B2 (en) | 2015-11-04 | 2017-11-21 | Ford Global Technologies, Llc | Coordinated testing in vehicle platoons |
US20170132299A1 (en) | 2015-11-10 | 2017-05-11 | Caterpillar Inc. | System and method for managing data associated with worksite |
US10204519B2 (en) | 2015-12-25 | 2019-02-12 | Ozyegin Universitesi | Communication between vehicles of a platoon |
US20170197615A1 (en) | 2016-01-11 | 2017-07-13 | Ford Global Technologies, Llc | System and method for reverse perpendicular parking a vehicle |
US9632507B1 (en) * | 2016-01-29 | 2017-04-25 | Meritor Wabco Vehicle Control Systems | System and method for adjusting vehicle platoon distances based on predicted external perturbations |
CN105835882A (en) | 2016-03-01 | 2016-08-10 | 乐视云计算有限公司 | Automatic vehicle traveling method and device |
SE539788C2 (en) | 2016-03-22 | 2017-11-28 | Scania Cv Ab | A method and a system for controlling platooning operation when a vehicle is to leave the platoon |
US10542464B2 (en) | 2016-04-01 | 2020-01-21 | Futurewei Technologies, Inc. | Methods for data communication to a platoon of connected vehicles |
US10353387B2 (en) | 2016-04-12 | 2019-07-16 | Here Global B.V. | Method, apparatus and computer program product for grouping vehicles into a platoon |
DE112016006737T5 (en) | 2016-04-15 | 2019-01-10 | Honda Motor Co., Ltd. | VEHICLE CONTROL SYSTEM, VEHICLE CONTROL PROCEDURE AND VEHICLE CONTROL PROGRAM |
SE540620C2 (en) | 2016-04-22 | 2018-10-02 | Scania Cv Ab | Method and system for determining risks for vehicles about leaving a platoon |
US20170309187A1 (en) | 2016-04-22 | 2017-10-26 | Hsin-Nan Lin | Vehicle platoon system and method thereof |
SE540619C2 (en) | 2016-04-22 | 2018-10-02 | Scania Cv Ab | Method and system for adapting platooning operation according to the behavior of other road users |
WO2017192726A1 (en) | 2016-05-03 | 2017-11-09 | Azuga, Inc. | Method and apparatus for evaluating driver performance and determining driver rewards |
NL2016753B1 (en) | 2016-05-10 | 2017-11-16 | Daf Trucks Nv | Platooning method for application in heavy trucks |
US9927816B2 (en) | 2016-05-13 | 2018-03-27 | Macau University Of Science And Technology | System and method for operating a follower vehicle in a vehicle platoon |
WO2017200433A1 (en) | 2016-05-17 | 2017-11-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, platoon controller and vehicle controller, for enabling a decision to join a vehicle platoon |
SE539923C2 (en) | 2016-05-23 | 2018-01-16 | Scania Cv Ab | Methods and communicators for transferring a soft identity reference from a first vehicle to a second vehicle in a platoon |
JP6565793B2 (en) | 2016-05-30 | 2019-08-28 | 株式会社デンソー | Convoy travel system |
EP3465371A4 (en) | 2016-05-31 | 2019-12-18 | Peloton Technology Inc. | Platoon controller state machine |
WO2017209666A1 (en) | 2016-05-31 | 2017-12-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and platoon manager for enabling a wireless device in a vehicle to communicate over a cellular network |
GB2540039A (en) | 2016-06-03 | 2017-01-04 | Daimler Ag | Method for operating a vehicle as a following vehicle in a platoon |
US10017179B2 (en) | 2016-06-06 | 2018-07-10 | GM Global Technology Operations LLC | Method for optimizing inter-vehicle distance and equitably sharing fuel benefits in a vehicle platoon |
US20170349058A1 (en) | 2016-06-07 | 2017-12-07 | Briggs & Stratton Corporation | Fleet management system for outdoor power equipment |
US9878657B2 (en) | 2016-06-15 | 2018-01-30 | Denso International America, Inc. | Projected laser lines/graphics onto the road for indicating truck platooning/warning to other drivers of presence of truck platoon |
US10332403B2 (en) | 2017-01-04 | 2019-06-25 | Honda Motor Co., Ltd. | System and method for vehicle congestion estimation |
US10027024B2 (en) | 2016-06-29 | 2018-07-17 | Denso International America, Inc. | Antenna for vehicle platooning |
WO2018000386A1 (en) | 2016-06-30 | 2018-01-04 | 华为技术有限公司 | Method for controlling vehicle platoon driving, centralized control device, and vehicle |
US11107018B2 (en) | 2016-07-15 | 2021-08-31 | Cummins Inc. | Method and apparatus for platooning of vehicles |
US10068485B2 (en) | 2016-08-15 | 2018-09-04 | Ford Global Technologies, Llc | Platooning autonomous vehicle navigation sensory exchange |
WO2018035145A1 (en) | 2016-08-19 | 2018-02-22 | Pcms Holdings, Inc. | Method for changing the lead vehicle of a vehicle platoon |
US10369998B2 (en) | 2016-08-22 | 2019-08-06 | Peloton Technology, Inc. | Dynamic gap control for automated driving |
JP6953412B2 (en) | 2016-08-30 | 2021-10-27 | ナブテスコオートモーティブ株式会社 | Vehicles and platooning vehicles |
JP7036730B2 (en) | 2016-08-31 | 2022-03-15 | ナブテスコオートモーティブ株式会社 | Brake system, vehicle and platooning vehicle group |
WO2018043753A1 (en) | 2016-09-05 | 2018-03-08 | ナブテスコオートモーティブ 株式会社 | Platooning management system |
US10849081B2 (en) | 2016-09-16 | 2020-11-24 | Qualcomm Incorporated | Synchronized radio transmission for vehicle platooning |
US9928746B1 (en) | 2016-09-16 | 2018-03-27 | Ford Global Technologies, Llc | Vehicle-to-vehicle cooperation to marshal traffic |
DE102016011325A1 (en) | 2016-09-21 | 2018-03-22 | Wabco Gmbh | A method for determining a dynamic vehicle distance between a follower vehicle and a front vehicle of a platoon |
US10089882B2 (en) | 2016-09-21 | 2018-10-02 | Wabco Europe Bvba | Method for controlling an own vehicle to participate in a platoon |
US9940840B1 (en) | 2016-10-06 | 2018-04-10 | X Development Llc | Smart platooning of vehicles |
US10040390B2 (en) | 2016-10-11 | 2018-08-07 | Ford Global Technologies, Llc | Vehicle light diagnostic |
US20180113448A1 (en) | 2016-10-24 | 2018-04-26 | Ford Global Technologies, Llc | Vehicle energy reduction |
US10399564B2 (en) | 2016-10-25 | 2019-09-03 | Ford Global Technologies, Llc | Vehicle roundabout management |
DE102016012868A1 (en) | 2016-10-28 | 2018-05-03 | Man Truck & Bus Ag | Technology for the longitudinal control of a commercial vehicle in a vehicle association |
EP3316062B1 (en) | 2016-10-31 | 2019-09-04 | Nxp B.V. | Platoon control |
US9616743B1 (en) | 2016-11-30 | 2017-04-11 | Borgwarner Inc. | Cooling air flow system |
EP3552071B1 (en) | 2016-12-08 | 2020-10-21 | PCMS Holdings, Inc. | System and method for routing and reorganization of a vehicle platoon in a smart city |
SE541478C2 (en) | 2016-12-16 | 2019-10-15 | Scania Cv Ab | Method and control unit for adjusting an inter vehicular distance between vehicles in a platoon |
US10482767B2 (en) | 2016-12-30 | 2019-11-19 | Bendix Commercial Vehicle Systems Llc | Detection of extra-platoon vehicle intermediate or adjacent to platoon member vehicles |
US10073464B2 (en) | 2016-12-30 | 2018-09-11 | Bendix Commercial Vehicle Systems Llc | Varying the distance between vehicles in a platoon |
US10372123B2 (en) | 2016-12-30 | 2019-08-06 | Bendix Commercial Vehicle Systems Llc | “V” shaped and wide platoon formations |
US10503176B2 (en) | 2016-12-30 | 2019-12-10 | Bendix Commercial Vehicle Systems Llc | Self-ordering of fleet vehicles in a platoon |
JPWO2018135630A1 (en) | 2017-01-20 | 2019-11-07 | ナブテスコオートモーティブ株式会社 | Convoy travel vehicle group and convoy travel method |
US10281926B2 (en) | 2017-01-23 | 2019-05-07 | Bendix Commercial Vehicle Systems Llc | Apparatus and method for controlling vehicles in a platoon |
US20210132630A1 (en) | 2017-01-24 | 2021-05-06 | Volvo Truck Corporation | A method for at least one string of platooning vehicles |
GB2551248A (en) | 2017-04-12 | 2017-12-13 | Daimler Ag | Method for operating a vehicle in a platoon |
US10017039B1 (en) | 2017-07-20 | 2018-07-10 | Bendix Commercial Vehicle Systems Llc | Vehicle platooning with a hybrid electric vehicle system |
-
2018
- 2018-03-20 US US15/926,813 patent/US10474166B2/en not_active Expired - Fee Related
- 2018-03-20 US US15/926,809 patent/US20180210463A1/en not_active Abandoned
- 2018-03-22 WO PCT/US2018/023723 patent/WO2018208372A2/en active Application Filing
Patent Citations (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5781119A (en) * | 1995-03-14 | 1998-07-14 | Toyota Jidosha Kabushiki Kaisha | Vehicle guiding system |
US5777451A (en) * | 1996-03-08 | 1998-07-07 | Nissan Diesel Motor Co., Ltd. | Vehicle longitudinal spacing controller |
US6032097A (en) * | 1996-11-27 | 2000-02-29 | Honda Giken Kogyo Kabushiki Kaisha | Vehicle platoon control system |
US20120323474A1 (en) * | 1998-10-22 | 2012-12-20 | Intelligent Technologies International, Inc. | Intra-Vehicle Information Conveyance System and Method |
US6397149B1 (en) * | 1999-05-07 | 2002-05-28 | Honda Giken Kogyo Kabushiki Kaisha | Processional travel control apparatus |
US20020135507A1 (en) * | 2000-04-08 | 2002-09-26 | Hermann Winner | Method and device for controlling the distance from a vehicle to a preceding vehicle |
US6765495B1 (en) * | 2000-06-07 | 2004-07-20 | Hrl Laboratories, Llc | Inter vehicle communication system |
US20060195250A1 (en) * | 2005-02-28 | 2006-08-31 | Junichiro Kawaguchi | Method and a device for stabilization control of a vehicle traffic volume |
US20070032245A1 (en) * | 2005-08-05 | 2007-02-08 | Alapuranen Pertti O | Intelligent transportation system and method |
US20100044998A1 (en) * | 2006-05-17 | 2010-02-25 | Eurolum | Wheeled vehicle, hitching method, unhitching method, method for managing said vehicles and resulting train of vehicles |
US20090079839A1 (en) * | 2006-06-19 | 2009-03-26 | Oshkosh Corporation | Vehicle diagnostics based on information communicated between vehicles |
US20100191449A1 (en) * | 2007-07-30 | 2010-07-29 | Shouzou Iwamoto | Packet traffic control system |
US20100256852A1 (en) * | 2009-04-06 | 2010-10-07 | Gm Global Technology Operations, Inc. | Platoon vehicle management |
US20110093177A1 (en) * | 2009-10-21 | 2011-04-21 | Horn Berthold K P | Method and Apparatus for Reducing Motor Vehicle Traffic Flow Instabilities and Increasing Vehicle Throughput |
US20130211624A1 (en) * | 2010-05-31 | 2013-08-15 | Volvo Car Corporation | Control system for travel in a platoon |
US20130041576A1 (en) * | 2011-07-06 | 2013-02-14 | Joshua P. Switkes | Systems and Methods for Semi-Autonomous Convoying of Vehicles |
US20130018766A1 (en) * | 2011-07-12 | 2013-01-17 | Edwin Roy Christman | Minimalist approach to roadway electrification |
US20130030606A1 (en) * | 2011-07-25 | 2013-01-31 | GM Global Technology Operations LLC | Autonomous convoying technique for vehicles |
US20130041567A1 (en) * | 2011-08-10 | 2013-02-14 | Denso Corporation | Travel support apparatus and travel support system |
US8948995B2 (en) * | 2012-06-28 | 2015-02-03 | Toyota Motor Engineering & Manufacturing North America, Inc. | Preceding vehicle state prediction |
US20140005906A1 (en) * | 2012-06-28 | 2014-01-02 | Toyota Motor Engineering & Manufacturing | Preceding vehicle state prediction |
US20150274161A1 (en) * | 2012-09-14 | 2015-10-01 | Robert Bosch Gmbh | Method for operating a driver assistance system of a vehicle |
US20140136044A1 (en) * | 2012-11-15 | 2014-05-15 | GM Global Technology Operations LLC | Active safety system and method for operating the same |
US20140172265A1 (en) * | 2012-12-19 | 2014-06-19 | Denso Corporation | Vehicle to vehicle communication device and convoy travel control device |
US20140210645A1 (en) * | 2013-01-30 | 2014-07-31 | Wavetronix Llc | Traffic flow through an intersection by reducing platoon interference |
US9412271B2 (en) * | 2013-01-30 | 2016-08-09 | Wavetronix Llc | Traffic flow through an intersection by reducing platoon interference |
US20140316671A1 (en) * | 2013-04-17 | 2014-10-23 | Denso Corporation | Platoon travel system |
US20160039412A1 (en) * | 2013-04-19 | 2016-02-11 | Continental Teves Ag & Co. Ohg | Method and system for preventing a following vehicle from driving up on a vehicle driving directly in front and use of the system |
US20160297447A1 (en) * | 2013-10-11 | 2016-10-13 | Nissan Motor Co., Ltd. | Travel Control Device and Travel Control Method |
US20150154871A1 (en) * | 2013-12-04 | 2015-06-04 | Volvo Car Corporation | Method and control system for controlling movement of a group of road vehicles |
US9511764B2 (en) * | 2014-02-28 | 2016-12-06 | Ford Global Technologies, Llc | Semi-autonomous mode control |
US20170227972A1 (en) * | 2014-10-21 | 2017-08-10 | Road Trains Llc | Platooning control via accurate synchronization |
US20180137763A1 (en) * | 2015-02-26 | 2018-05-17 | Volvo Truck Corporation | Method of controlling inter-vehicle gap(s) in a platoon |
US20170168503A1 (en) * | 2015-12-11 | 2017-06-15 | Avishtech, Llc | Autonomous vehicle towing system and method |
US20180032072A1 (en) * | 2016-07-28 | 2018-02-01 | Lytx, Inc. | Determining driver engagement with autonomous vehicle |
US20190171226A1 (en) * | 2017-12-01 | 2019-06-06 | Hyundai Motor Company | Platooning control apparatus and method therefor |
US20190220037A1 (en) * | 2018-01-12 | 2019-07-18 | Toyota Motor Engineering & Manufacturing North America, Inc. | Responsibilities and agreement acceptance for vehicle platooning |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10732645B2 (en) | 2011-07-06 | 2020-08-04 | Peloton Technology, Inc. | Methods and systems for semi-autonomous vehicular convoys |
US11360485B2 (en) | 2011-07-06 | 2022-06-14 | Peloton Technology, Inc. | Gap measurement for vehicle convoying |
US10520952B1 (en) | 2011-07-06 | 2019-12-31 | Peloton Technology, Inc. | Devices, systems, and methods for transmitting vehicle data |
US11334092B2 (en) | 2011-07-06 | 2022-05-17 | Peloton Technology, Inc. | Devices, systems, and methods for transmitting vehicle data |
US11294396B2 (en) * | 2013-03-15 | 2022-04-05 | Peloton Technology, Inc. | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles |
US20180186381A1 (en) * | 2016-08-22 | 2018-07-05 | Peloton Technology, Inc. | Applications for using mass estimations for vehicles |
US11328608B2 (en) * | 2017-03-28 | 2022-05-10 | Volvo Truck Corporation | Method for controlling the braking of a following vehicle of a string comprising a plurality of platooning vehicles |
US10525950B2 (en) * | 2017-09-15 | 2020-01-07 | Bendix Commercial Vehicle Systems Llc | Braking controller and method using verification of reported trailer capabilities |
US10549732B2 (en) | 2017-09-15 | 2020-02-04 | Bendix Commercial Vehicle Systems Llc | Towing vehicle controller using trailer braking strategy and trailer braking control method |
US10814844B2 (en) | 2017-09-15 | 2020-10-27 | Bendix Commercial Vehicle Systems Llc | Braking controller and method using verification of reported trailer capabilities |
US10549739B2 (en) | 2017-09-15 | 2020-02-04 | Bendix Commercial Vehicle Systems Llc | Towing vehicle controller using trailer braking strategy and trailer braking control method |
US20190084537A1 (en) * | 2017-09-15 | 2019-03-21 | Bendix Commercial Vehicle Systems Llc | Braking controller and method using verification of reported trailer capabilities |
US10899323B2 (en) | 2018-07-08 | 2021-01-26 | Peloton Technology, Inc. | Devices, systems, and methods for vehicle braking |
US11163317B2 (en) * | 2018-07-31 | 2021-11-02 | Honda Motor Co., Ltd. | System and method for shared autonomy through cooperative sensing |
US11181929B2 (en) | 2018-07-31 | 2021-11-23 | Honda Motor Co., Ltd. | System and method for shared autonomy through cooperative sensing |
SE545354C2 (en) * | 2018-09-04 | 2023-07-18 | Bosch Gmbh Robert | Vehicle control units, motor vehicles and method of operation of vehicle control units for time-synchronized braking |
US11341856B2 (en) | 2018-10-29 | 2022-05-24 | Peloton Technology, Inc. | Systems and methods for managing communications between vehicles |
US10762791B2 (en) | 2018-10-29 | 2020-09-01 | Peloton Technology, Inc. | Systems and methods for managing communications between vehicles |
US20200160723A1 (en) * | 2018-11-21 | 2020-05-21 | Peloton Technology, Inc. | Systems and methods for managing tractor trailers |
US11427196B2 (en) | 2019-04-15 | 2022-08-30 | Peloton Technology, Inc. | Systems and methods for managing tractor-trailers |
US11161487B2 (en) * | 2019-08-15 | 2021-11-02 | Bendix Commercial Vehicle Systems Llc | System and method for controlling wheel brakes in a vehicle platooning with another vehicle |
US11173933B2 (en) * | 2019-11-15 | 2021-11-16 | Nxp B.V. | System and method for monitoring a moving vehicle |
US11873000B2 (en) | 2020-02-18 | 2024-01-16 | Toyota Motor North America, Inc. | Gesture detection for transport control |
US11735048B2 (en) | 2020-02-27 | 2023-08-22 | Toyota Motor North America, Inc. | Minimizing traffic signal delays with transports |
US11290856B2 (en) | 2020-03-31 | 2022-03-29 | Toyota Motor North America, Inc. | Establishing connections in transports |
US11797949B2 (en) | 2020-03-31 | 2023-10-24 | Toyota Motor North America, Inc. | Establishing connections in transports |
US12033502B2 (en) | 2020-03-31 | 2024-07-09 | Toyota Motor North America, Inc. | Traffic manager transports |
Also Published As
Publication number | Publication date |
---|---|
WO2018208372A2 (en) | 2018-11-15 |
US20180210464A1 (en) | 2018-07-26 |
WO2018208372A3 (en) | 2019-02-07 |
US10474166B2 (en) | 2019-11-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10474166B2 (en) | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles | |
US11294396B2 (en) | System and method for implementing pre-cognition braking and/or avoiding or mitigation risks among platooning vehicles | |
US10921822B2 (en) | Automated vehicle control system architecture | |
US10906544B2 (en) | Dynamic gap control for automated driving | |
US10077050B2 (en) | Automated driving system for evaluating lane cut-out and method of using the same | |
US20190346863A1 (en) | Vehicle platooning systems and methods | |
JP5573461B2 (en) | Vehicle control system | |
US11614752B2 (en) | Vehicle platooning systems and methods | |
US11835965B2 (en) | Applications for using mass estimations for vehicles | |
US12050474B2 (en) | System and method for implementing precognition braking and/or avoiding or mitigation risks among platooning vehicles | |
US20230054037A1 (en) | System and method for implementing precognition braking and/or avoiding or mitigation risks among platooning vehicles | |
JP2012043199A (en) | Vehicle control system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PELOTON TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SWITKES, JOSHUA P.;ERLIEN, STEPHEN M.;LAUBINGER, LORENZ;SIGNING DATES FROM 20180323 TO 20180329;REEL/FRAME:045483/0363 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |