EP3928300A1 - Phantom traffic jam detection and avoidance - Google Patents

Phantom traffic jam detection and avoidance

Info

Publication number
EP3928300A1
EP3928300A1 EP19736922.6A EP19736922A EP3928300A1 EP 3928300 A1 EP3928300 A1 EP 3928300A1 EP 19736922 A EP19736922 A EP 19736922A EP 3928300 A1 EP3928300 A1 EP 3928300A1
Authority
EP
European Patent Office
Prior art keywords
vehicle
traffic
road segment
speed
processors
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP19736922.6A
Other languages
German (de)
English (en)
French (fr)
Inventor
Neil DHILLON
Tanmay WADHWA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Google LLC
Original Assignee
Google LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Google LLC filed Critical Google LLC
Publication of EP3928300A1 publication Critical patent/EP3928300A1/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
    • G08G1/096725—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information generates an automatic action on the vehicle control
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K31/00—Vehicle fittings, acting on a single sub-unit only, for automatically controlling vehicle speed, i.e. preventing speed from exceeding an arbitrarily established velocity or maintaining speed at a particular velocity, as selected by the vehicle operator
    • B60K31/18—Vehicle fittings, acting on a single sub-unit only, for automatically controlling vehicle speed, i.e. preventing speed from exceeding an arbitrarily established velocity or maintaining speed at a particular velocity, as selected by the vehicle operator including a device to audibly, visibly, or otherwise signal the existence of unusual or unintended speed to the driver of the vehicle
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/10—Input arrangements, i.e. from user to vehicle, associated with vehicle functions or specially adapted therefor
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/20—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor
    • B60K35/21—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor using visual output, e.g. blinking lights or matrix displays
    • B60K35/22—Display screens
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/20—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor
    • B60K35/28—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor characterised by the type of the output information, e.g. video entertainment or vehicle dynamics information; characterised by the purpose of the output information, e.g. for attracting the attention of the driver
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/85—Arrangements for transferring vehicle- or driver-related data
    • 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/143—Speed control
    • 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
    • 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
    • B60W60/00—Drive control systems specially adapted for autonomous road vehicles
    • B60W60/001—Planning or execution of driving tasks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V20/00—Scenes; Scene-specific elements
    • G06V20/50—Context or environment of the image
    • G06V20/52—Surveillance or monitoring of activities, e.g. for recognising suspicious objects
    • G06V20/54—Surveillance or monitoring of activities, e.g. for recognising suspicious objects of traffic, e.g. cars on the road, trains or boats
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/0112—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from the vehicle, e.g. floating car data [FCD]
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/0116—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from roadside infrastructure, e.g. beacons
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0125—Traffic data processing
    • G08G1/0133—Traffic data processing for classifying traffic situation
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0137—Measuring and analyzing of parameters relative to traffic conditions for specific applications
    • G08G1/0145—Measuring and analyzing of parameters relative to traffic conditions for specific applications for active traffic flow control
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/017—Detecting movement of traffic to be counted or controlled identifying vehicles
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/052—Detecting movement of traffic to be counted or controlled with provision for determining speed or overspeed
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/056—Detecting movement of traffic to be counted or controlled with provision for distinguishing direction of travel
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/065—Traffic control systems for road vehicles by counting the vehicles in a section of the road or in a parking area, i.e. comparing incoming count with outgoing count
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
    • G08G1/096716—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096733—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place
    • G08G1/096758—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place where no selection takes place on the transmitted or the received information
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096766—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission
    • G08G1/096775—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission where the origin of the information is a central station
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2310/00—Arrangements, adaptations or methods for cruise controls
    • B60K2310/22—Displays for target speed
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2360/00—Indexing scheme associated with groups B60K35/00 or B60K37/00 relating to details of instruments or dashboards
    • B60K2360/16—Type of output information
    • B60K2360/167—Vehicle dynamics information
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2360/00—Indexing scheme associated with groups B60K35/00 or B60K37/00 relating to details of instruments or dashboards
    • B60K2360/18—Information management
    • B60K2360/188—Displaying information using colour changes
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/20—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor
    • B60K35/29—Instruments characterised by the way in which information is handled, e.g. showing information on plural displays or prioritising information according to driving conditions
    • 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
    • B60W2050/0001—Details of the control system
    • B60W2050/0002—Automatic control, details of type of controller or control system architecture
    • B60W2050/0004—In digital systems, e.g. discrete-time systems involving sampling
    • B60W2050/0005—Processor details or data handling, e.g. memory registers or chip architecture
    • 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
    • B60W2050/0001—Details of the control system
    • B60W2050/0002—Automatic control, details of type of controller or control system architecture
    • B60W2050/0008—Feedback, closed loop systems or details of feedback error signal
    • 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
    • B60W2050/0062—Adapting control system settings
    • B60W2050/0075—Automatic parameter input, automatic initialising or calibrating 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
    • B60W2554/00—Input parameters relating to objects
    • B60W2554/40—Dynamic objects, e.g. animals, windblown objects
    • B60W2554/406—Traffic density
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V2201/00—Indexing scheme relating to image or video recognition or understanding
    • G06V2201/08—Detecting or categorising vehicles

Definitions

  • the present disclosure relates to digital mapping data and, more particularly, to detecting and reducing the effects of traffic jams by providing instructions to users and vehicles entering a road segment to mitigate traffic on the road segment.
  • traffic jams may occur without an accident or lane closure.
  • a traffic reduction system first identifies a traffic jam on a road segment which may be a phantom traffic jam.
  • the traffic reduction system may identify the traffic jam on the road segment by receiving sensor data from vehicles on the road segment or infrastructure components on the road segment indicating that several vehicles are slowing down.
  • the traffic reduction system may receive sensor data from infrastructure components on the road segment, such as image or video data that does not include an accident, construction, traffic signal, or lane closure on the road segment.
  • the traffic reduction system may also receive additional information regarding the cause of the traffic from a traffic sever.
  • the traffic reduction system determines a target speed or speed range for vehicles approaching the road segment to travel at to reduce the amount of traffic on the road segment. More specifically, if each vehicle on the road segment maintains the same distance between the vehicle and the vehicle in front of the vehicle and the vehicle and the vehicle behind the vehicle, then the vehicles will not have to slow down. Accordingly, the traffic reduction system determines a following distance for each of the vehicles to maintain between the vehicle in front of and behind each respective vehicle and calculates a target speed corresponding to the following distance.
  • the traffic reduction system provides an indication of the target speed to each vehicle, or a computing device within the vehicle, approaching the road segment.
  • the indication is a numeric indication which is provided for display on a user’s client device or on the vehicle head unit.
  • the indication may also include a background color, such as a green background color indicating that the user needs to speed up to maintain the appropriate following distance, a yellow background color indicating that the user needs to slow down, a blue background color indicating that the user needs to stay at the same speed, an orange background color that the user needs to slow down rapidly, etc. In this manner, the user/driver may travel at the target speed to reduce traffic on the road segment.
  • the indication of the target speed is provided to a computing device within the vehicle that controls some operation of the vehicle, such as a computing device in an autonomous vehicle, a semi-autonomous vehicle, or any other vehicle having autonomous operation features.
  • the computing device may control the vehicle to adjust the speed and travel at the target speed.
  • an example embodiment of the techniques of the present disclosure is a method for use in controlling the speed of a vehicle.
  • the method includes identifying a road segment within a geographic area having more than a threshold amount of traffic, determining a target speed for a vehicle approaching the road segment to travel at to reduce an amount of traffic at the road segment, and providing, to a computing device associated with a vehicle approaching the road segment, an indication of the target speed for the vehicle.
  • the server device includes one or more processors and a non- transitory computer-readable medium storing instructions. When executed by the one or more processors, the instructions cause the server device to identify a road segment within a geographic area having more than a threshold amount of traffic, determine a target speed for a vehicle approaching the road segment to travel at to reduce an amount of traffic at the road segment, and provide, to a computing device associated with a vehicle approaching the road segment, an indication of the target speed for the vehicle.
  • Yet another embodiment of these techniques is a method for use in controlling the speed of a vehicle.
  • the method includes providing, to a server device, an indication of a location of the vehicle, receiving, from the server device, an indication of a target speed for the vehicle to travel at when the vehicle is approaching a road segment having more than a threshold amount of traffic, determining a current speed of the vehicle, and outputting a feedback signal indicative of a difference between the current speed and a target speed.
  • a further embodiment of these techniques includes a device for use in controlling the speed of a vehicle.
  • the device includes one or more processors and a non-transitory computer-readable medium storing instructions. When executed by the one or more processors, the instructions cause the device to: provide, to a server device, an indication of a location of the vehicle; receive from the server device, an indication of a target speed for the vehicle to travel at when the vehicle is approaching a road segment having more than a threshold amount of traffic; determine a current speed of the vehicle; and output a feedback signal indicative of a difference between the current speed and the target speed.
  • the present disclosure also provides a computer-readable medium comprising instructions that, when executed by a computing device, cause the computing device to perform any of the methods disclosed herein.
  • the present disclosure also provides a computer program comprising instructions that, when executed by a computing device, cause the computing device to perform any of the methods disclosed herein.
  • FIG. 1A illustrates an example scenario including vehicles on a roadway that create traffic by following too closely together
  • Fig. IB illustrates another example scenario including vehicles on a roadway that do not create traffic by maintaining the appropriate following distances
  • FIG. 2 illustrates an example vehicle in which the techniques of the present disclosure can be used to generate speed displays for reducing traffic jams
  • FIG. 3 is a block diagram of an example communication system in which techniques for reducing the effects of traffic jams can be implemented
  • Figs. 4A-4B are example speed displays indicating target speeds for a vehicle approaching a road segment with traffic to reduce the amount of traffic on the road segment;
  • Fig. 5 is a flow diagram of an example method for reducing effects of traffic jams, which may be implemented in a server device.
  • Fig. 6 is a flow diagram of an example method for presenting a speed display to reduce effects of traffic jams, which may be implemented in a client device.
  • the present disclosure provides methods for use in controlling the speed of a vehicle to reduce the effects of traffic jams.
  • a respective target speed for each of a plurality of vehicles approaching a traffic jam is determined, and an indication of the target speed is provided to each vehicle.
  • each vehicle adjusts its current speed to minimize the difference between its current speed and the target speed.
  • Driving at the target speed causes the distance between each vehicle to increase and/or optimizes the speed at which vehicles approach the traffic jam, which may be a phantom traffic jam. This, in turn, reduces the likelihood of sudden braking that might perpetuate the phantom traffic jam.
  • the speed of vehicles in this manner, the phantom traffic jam is able to dissipate.
  • phantom traffic jams may occur due to a chain reaction caused by one vehicle slowing down on a densely populated roadway. This causes the vehicle behind it to slow down even more and sets off a chain reaction of vehicles slowing down which acts like a traveling wave.
  • the minimum traffic density or number of vehicles per unit of distance in which a traffic jam can occur on a road may be determined using the following equation:
  • pi is the minimum traffic density or number of vehicles per unit of distance in which a traffic jam can occur on a road
  • p M is the maximum traffic density for the particular road (e.g., where there is no space between vehicles on the road),
  • [0025] b is a measure of road conditions which decreases in accordance with the curvature of the road and/or the weather conditions
  • u is the speed at which vehicles travel on the road when there is no traffic, such as the speed limit or slightly above the speed limit.
  • FIG. 1A depicts an example roadway 100 with vehicles 102-110 traveling on the roadway.
  • the roadway 100 does not include an intersection, traffic signal, accident, construction, lane closure, etc.
  • a traffic jam is created along the roadway due to a second vehicle 104 following a first vehicle 102 too closely.
  • the second vehicle 104 decelerates faster than the first vehicle 102 to avoid hitting the first vehicle 102.
  • the third vehicle 106 decelerates faster than the second vehicle 104 and the fourth vehicle 108 decelerates even faster than the third vehicle 106.
  • the fourth vehicle 108 then has to wait for the second vehicle 104 and the third vehicle 106 to speed up before the fourth vehicle 108 can accelerate once again.
  • the traffic flow behaves as a traveling wave amplifying in magnitude the further a vehicle is from the first vehicle that slows down.
  • the fifth vehicle 110 is also likely to follow the pattern of the first four vehicles.
  • the fifth vehicle 110 may follow closely behind the fourth vehicle 108 and accelerate and decelerate in the same manner as the fourth vehicle 108.
  • Fig. IB depicts an example roadway 150 with vehicles 152-158 traveling on the road.
  • the second vehicle 154 on the roadway 150 maintains the same distance between the second vehicle 154 and first vehicle 152 (di) as the distance between the second vehicle 154 and the third vehicle 156 (d2).
  • a fourth vehicle 158 approaches the third vehicle 156, the third vehicle 156 and the fourth vehicle 158 maintain the same distance as the distance between the third vehicle 156 and the second vehicle 154 (d2).
  • the traffic reduction system determines a target acceleration of a vehicle on the road segment or approaching the road segment at a particular point in time based on the speeds and positions of the vehicle, the vehicle in front of the vehicle, and the vehicle behind the vehicle. More specifically, the traffic reduction system may determine the target acceleration (a) of the vehicle as:
  • x n is the position of vehicle n
  • x n+i is the position of vehicle n + 1 in front of vehicle n
  • x n -i is the position of vehicle n - 1 behind vehicle n
  • v n is the velocity of vehicle n
  • v n+i is the velocity of vehicle n + 1 in front of vehicle n
  • P n ⁇ i is the velocity of vehicle n - 1 behind vehicle n
  • k d is the gain of positional feedback
  • k v is the gain of velocity feedback
  • the traffic reduction system may then determine a target speed for the vehicle to accelerate or decelerate to within a threshold time period (e.g., 10 seconds, 30 seconds, etc.) based on the vehicle’s current speed, the target acceleration, and the threshold time period.
  • a threshold time period e.g. 10 seconds, 30 seconds, etc.
  • the target speed may be presented on a user’s client device 10 numerically or as a
  • an example environment 1 in which the techniques outlined above can be implemented includes a client device 10 and a vehicle 12 with a head unit 14.
  • the client device 10 may be a smart phone or a tablet computer, for example.
  • the client device 10 communicates with the head unit 14 of the vehicle 12 via a communication link 16, which may be wired (e.g., Universal Serial Bus (USB)) or wireless (e.g., Bluetooth, Wi-Fi Direct).
  • the client device 10 also can communicate with various content providers, servers, etc. via a wireless communication network such as a fourth- or third-generation cellular network (4G or 3G, respectively).
  • 4G or 3G fourth- or third-generation cellular network
  • the head unit 14 can include a display 18 such as a digital map.
  • the display 18 in some implementations is a touchscreen and includes a software keyboard for entering text input, which may include the name or address of a destination, point of origin, etc.
  • Hardware input controls 20 and 22 on the head unit 14 and the steering wheel, respectively, can be used for entering alphanumeric characters or to perform other functions for requesting navigation directions.
  • the head unit 14 also can include audio input and output components such as a microphone 24 and speakers 26, for example.
  • an example communication system 100 in which a traffic reduction system can be implemented includes a client device 10 and several other client devices 82a-n, such as a computing device configured to execute a geographic application 84, which also can be referred to as“navigation application 84.”
  • the application 84 can display an interactive digital map, request and receive routing data to provide driving, walking, or other navigation directions, provide various geolocated content, etc.
  • Each of the client devices 82a-n may be operated by users displaying digital maps while navigating to various locations.
  • the example communication system 100 includes infrastructure components 306, such as traffic lights which are disposed on or around road segments and collect sensor data related to the road segments.
  • the infrastructure components 306 may include traffic signals, cameras, street lights, or any other suitable roadside equipment.
  • the infrastructure components 306 may include one or more sensors (not shown) such as a camera, a positioning sensor, etc., a processing component 308, and a vehicle-to-infrastmcture (V2I) communication interface for communicating with vehicles within a communication range of the infrastructure component 306 and/or communicating with server devices.
  • sensors such as a camera, a positioning sensor, etc.
  • processing component 308 and a vehicle-to-infrastmcture (V2I) communication interface for communicating with vehicles within a communication range of the infrastructure component 306 and/or communicating with server devices.
  • V2I vehicle-to-infrastmcture
  • the communication system 100 includes a server device 60 configured to provide a target speed to the client device 10.
  • the server device 60 can be communicatively coupled to a database 80 that stores, in an example implementation, sensor data received from the other client devices 82a-n and the infrastructure components 306 to determine whether there is a traffic jam at a particular road segment.
  • the server device 60 can communicate with one or several databases that store any type of suitable geospatial information or information that can be linked to a geographic context.
  • the communication system 100 also can include a navigation data server 34 that provides driving, walking, biking, or public transit directions, for example.
  • the communication system 100 can include a map data server 50 that provides map data to the server device 60 for generating a map display.
  • the communication system 100 can include a traffic server (not shown) that provides traffic data to the server device 60.
  • the devices operating in the communication system 100 can be interconnected via a communication network 30.
  • the client device 10 may include a memory 320, one or more processors (CPUs) 316, a graphics processing unit (GPU) 312, an I/O module 314, a user interface (UI) 332, and one or several sensors (not shown), such as a global positioning system (GPS) module, an accelerometer, a gyroscope, a magnetometer such as a compass, etc.
  • the memory 320 can be a non-transitory memory and can include one or several suitable memory modules, such as random access memory (RAM), read-only memory (ROM), flash memory, other types of persistent memory, etc.
  • the I/O module 14 may be a touch screen, for example.
  • the client device 10 can include fewer components than illustrated in Fig.
  • the client device 10 may be any suitable portable or non-portable computing device.
  • the client device 10 may be a laptop computer, a desktop computer, a wearable device such as a smart watch or smart glasses, etc.
  • the memory 320 stores an operating system (OS) 326, which can be any type of suitable mobile or general-purpose operating system.
  • OS operating system
  • the OS 326 can include application programming interface (API) functions that allow applications to retrieve sensor readings.
  • API application programming interface
  • a software application configured to execute on the client device 10 can include instructions that invoke an OS 326 API for retrieving a current location of the client device 10 at that instant.
  • the API can also return a quantitative indication of how certain the API is of the estimate (e.g., as a percentage).
  • the memory 320 also stores a speed display 322, which can be included as functionality within a geographic application, such as a navigation application.
  • the navigation application can display an interactive digital map, request and receive routing data to provide driving, walking, or other navigation directions, provide various geolocated content, etc.
  • the current location of the client device 10 is provided to the server device 60.
  • the server device 60 determines that the client device 10 is approaching a road segment with traffic (e.g., within a threshold distance of the road segment, such as 500 ft, half of a mile, one mile, etc., and/or when the vehicle 12 is travelling toward the road segment according to the direction of travel of the vehicle 12), particularly traffic that is not caused by an accident, lane closure, construction, traffic signal, etc., but by vehicles following each other too closely, the server device 60 provides an indication of a target speed for the vehicle 12 associated with the client device 10 to travel at to reduce the amount of traffic on the road segment.
  • a threshold distance of the road segment such as 500 ft, half of a mile, one mile, etc.
  • the speed display 322 is configured to present the indication of the target speed, for example as a numeric indication (e.g., 33 mph), as a directional arrow (e.g., where an arrow pointing up indicates that the user should speed up and an arrow pointing down indicates that the user should slow down), and/or as a background color selected from a set of background colors that each represent different changes in speed.
  • a numeric indication e.g., 33 mph
  • a directional arrow e.g., where an arrow pointing up indicates that the user should speed up and an arrow pointing down indicates that the user should slow down
  • a background color selected from a set of background colors that each represent different changes in speed e.g., a green background color may indicate that the user of the client device 10 needs to speed up
  • a blue background color may indicate that the user of the client device 10 needs to stay at the same speed
  • a yellow background color may indicate that the user of the client device 10 needs to slow down
  • the speed display 322 may be presented as a notification within the navigation application, and may be presented periodically overlaying the interactive digital map or continuously for the time period in which the client device 10 is approaching or is on the road segment with traffic.
  • the server device 60 may provide real-time updates of the target speed for the vehicle 12 to travel at based on the speeds of the other vehicles in front of the vehicle 12, behind the vehicle 12, and/or on the road segment.
  • each client device 82a-n may be operated by a user displaying map data.
  • Each of the client devices 82a-n may be a smartphone or a tablet computer and may have one or several sensors 19.
  • each client device 82a-n may include a memory that stores an operating system (OS) and a navigation application 84 which is configured to generate interactive digital maps and/or perform other geographic functions, as indicated above.
  • the navigation application 84 can receive map data in a raster (e.g., bitmap) or non-raster (e.g., vector graphics) format from the map data server 50 and present the map data via a map display 86.
  • a raster e.g., bitmap
  • non-raster e.g., vector graphics
  • the map data can be organized into layers, such as a basic layer depicting roads, streets, natural formations, etc., a traffic layer depicting current traffic conditions, a weather layer depicting current weather conditions, a navigation layer depicting a path to reach a destination, etc.
  • the navigation application 84 also can display driving, walking, or transit directions, and in general provide functions related to geography, geolocation, navigation, etc. via the map display 86.
  • the client devices 82a-n may provide map data and/or sensor data to the server device 60 for identifying traffic on various road segments. More specifically, when a user of the client device 82a-n agrees to share location and other sensor data, the client device 82a-n provides positioning data indicating the current location of the client device 82a-n to the server device 60 as well as acceleration data and/or speed data for the client device 82a-n. When the server device 60 obtains several instances of deceleration from client devices 82a-n within the same geographic area, or speeds below a threshold speed, the server device 60 may identify traffic on the roadway corresponding to the current locations of the client devices 82a-n. In other implementations, the server device 60 may communicate with a traffic server (not shown) to identify traffic on a road segment.
  • a traffic server not shown
  • Fig. 3 illustrates the navigation application 84 as a standalone application
  • the functionality of the navigation application 84 also can be provided in the form of an online service accessible via a web browser executing on the client devices 82a-n, as a plug-in or extension for another software application executing on the client devices 82a-n, etc.
  • the navigation application 84 generally can be provided in different versions for different respective operating systems.
  • the maker of the client devices 82a-n can provide a Software Development Kit (SDK) including the navigation application 84 for the AndroidTM platform, another SDK for the iOSTM platform, etc.
  • SDK Software Development Kit
  • the server device 60 includes one or more processors 62 and a memory 64.
  • the memory 64 may be tangible, non-transitory memory and may include any types of suitable memory modules, including random access memory (RAM), read-only memory (ROM), flash memory, other types of persistent memory, etc.
  • the memory 64 stores instructions executable on the processors 62 that make up a traffic reduction engine 68, which can identify traffic jams on roadways or portions of roadways, such as road segments.
  • the traffic reduction engine 68 may also receive a current location of a client device 10 approaching the roadway and determine a target speed for the vehicle 12 associated with the client device 10 to travel at to reduce the amount of traffic on the roadway. An indication of the target speed is displayed by the speed display 322 of the client device 10.
  • the traffic reduction engine 68 and the speed display 322 can operate as components of a traffic reduction system.
  • the traffic reduction system can include only server-side components and simply provide the speed display 322 with instructions to display an indication of the target speed.
  • traffic reduction techniques in these embodiments can be implemented transparently to the speed display 322.
  • the entire functionality of the traffic reduction engine 68 can be implemented in the speed display 322. While the speed display 322 is shown in Fig. 3 as operating in the client device 10, the speed display 322 may also operate within a vehicle head unit 14 or in any other computing device operating in a vehicle 12. For example, the speed display 322 may operate in a computing device that controls operation of the vehicle 12.
  • the server device 60 may provide indications of target speeds for the vehicle 12 to travel at to the speed display 322, and the computing device may control operation of the vehicle 12 to accelerate or decelerate to achieve the desired speeds.
  • Fig. 3 illustrates the server device 60 as only one instance of a server.
  • the server device 60 includes a group of one or more server devices, each equipped with one or more processors and capable of operating independently of the other server devices. Server devices operating in such a group can process requests from the client device 10 individually (e.g., based on availability), in a distributed manner where one operation associated with processing a request is performed on one server device while another operation associated with processing the same request is performed on another server device, or according to any other suitable technique.
  • the term“server device” may refer to an individual server device or to a group of two or more server devices.
  • the speed display 322 operating in the client device 10 receives and transmits data to the server device 60.
  • the client device 10 may transmit a communication to the traffic reduction engine 68 (implemented in the server device 60) indicating the current location of the client device 10.
  • the traffic reduction engine 68 may determine whether the vehicle 12 is approaching a road segment having more than a threshold amount of traffic based on the current location of the client device.
  • the threshold amount of traffic may be a traffic density for the road segment, such as 100 vehicles per mile, 200 vehicles per mile, etc. In other implementations, the threshold amount of traffic may be based on a threshold speed for vehicles on the road segment relative to the speed limit for the road segment.
  • the threshold amount of traffic may be based on a threshold deceleration for vehicles on the road segment.
  • the traffic reduction engine 68 may receive sensor data from client devices 82a-n traveling on the road segment indicating speed and acceleration/deceleration values for the vehicles.
  • the traffic reduction engine 68 may also receive sensor data from infrastructure components 306 on the road segment.
  • the traffic reduction engine 68 may receive traffic data from a traffic server indicating the amount of traffic on a road segment.
  • the traffic server may provide a traffic density for the road segment, a categorical description of the amount of traffic, such as light, medium, or heavy, or an indication of an expected amount of additional time for traversing the road segment due to the traffic.
  • the threshold amount of traffic may be a threshold traffic density (e.g., 100 vehicles per mile), a threshold traffic category (e.g., medium or above), or a threshold amount of additional time for traversing the road segment due to the traffic (e.g., 5 minutes).
  • the traffic reduction engine 68 may compare average speed and/or acceleration/deceleration values to a threshold speed or deceleration to determine whether the road segment has a threshold amount of traffic.
  • the threshold speed may be based on the speed limit for the road segment, such that the threshold speed for a road segment having a speed limit of 55 mph, for example, is higher than the threshold speed for a road segment having a speed limit of 35 mph.
  • the sensor data from the infrastructure components 306 may include image or video data from a camera on the road segment.
  • the traffic reduction engine 68 may analyze the image or video data to determine that there are no accidents, lane closures, traffic signals, construction, etc., on the road segment. This may indicate that the traffic is due to vehicles failing to maintain threshold following distances on the road segment.
  • the traffic reduction engine 68 may also receive additional information regarding the cause of the traffic from a traffic sever.
  • the traffic reduction engine 68 may receive a signal from a vehicle located within the road segment indicating that the traffic is not caused by an accident, a lane closure, construction, or a traffic signal.
  • the traffic reduction engine 68 may receive information from a navigation application 84 operating in a client device 82a-n within the vehicle indicating that the traffic is not caused by an accident, a lane closure,
  • the client device 82a-n may communicate with infrastructure components 306 on the road segment which indicate that the traffic is not caused by an accident, a lane closure, construction, or a traffic signal, and may forward the communication to the server device 60.
  • the traffic reduction engine 68 determines a target speed for the vehicle 12 when the vehicle 12 is approaching a road segment with more than the threshold amount of traffic.
  • the target speed may be determined based on the traffic density of the road segment and/or a threshold following distance for the road segment.
  • the traffic reduction engine 68 may determine a threshold following distance for the road segment based on the traffic density of the road segment where the threshold following distance decreases as the traffic density increases.
  • the threshold following distance may be based on the flow of traffic on the road segment, such that following distances may be higher as vehicles travel faster on the road segment. For example, the following distance may be higher when vehicles travel around 50 mph on the road segment than when vehicles travel around 30 mph on the road segment.
  • the traffic reduction engine 68 may then determine a target speed based on the following distance and the speed of the vehicles on the road segment.
  • the traffic reduction engine 68 determines a target speed for the vehicle 12 using bilateral control methods, where the target speed is determined to maintain a threshold distance between the vehicle 12 and the vehicles in front of and behind the vehicle 12.
  • the traffic reduction engine 68 determines a target acceleration for the vehicle 12 using the equation described above, where:
  • the traffic reduction engine 68 may include pre-stored values for k d , the gain of positional feedback, and k v , the gain of velocity feedback.
  • the traffic reduction engine 68 may also determine the positions and speeds of the vehicles in front of and behind the vehicle 12 based on the sensor data from the client devices 82a-n. In some implementations, the traffic reduction engine 68 estimates the positions and speeds of the vehicle in front of and behind the vehicle 12 based on average speeds and distances between vehicles according to the sensor data from client devices 82a-n on the road segment.
  • the traffic reduction engine 68 determines the target speed for the vehicle to accelerate or decelerate to within a threshold time period (e.g., 10 seconds, 30 seconds, etc.) based on the vehicle’s current speed, the target acceleration, and the threshold time period.
  • a threshold time period e.g. 10 seconds, 30 seconds, etc.
  • the traffic reduction engine 68 may identify the vehicle in front of the vehicle 12 and the vehicle behind the vehicle 12 based on the location data from the client devices 82a-n. For example, the traffic reduction engine 68 may identify the two vehicles closest to the vehicle 12 according to the location data from the client devices 82a-n as the vehicles in front of and behind the vehicle 12. The traffic reduction engine 68 may then determine the positions and speeds of the identified vehicles and the position and speed of the vehicle 12 to determine the target acceleration.
  • the traffic reduction engine 68 may identify a first set of vehicles in front of the vehicle 12 and a second set of vehicles behind the vehicle 12 based on the location data from the client devices 82a-n. For example, the traffic reduction engine 68 may identify vehicles within a threshold distance in front of the vehicle 12 (e.g., 100 ft, 200 ft, 500 ft, 1000 ft, etc.) according to the location data from the client devices 82a-n as the vehicles in front of the vehicle 12 and may identify vehicles within a threshold distance behind the vehicle 12 (e.g., 100 ft, 200 ft, 500 ft, 1000 ft, etc.) according to the location data from the client devices 82a-n as the vehicles behind the vehicle 12.
  • a threshold distance in front of the vehicle 12 e.g., 100 ft, 200 ft, 500 ft, 1000 ft, etc.
  • the traffic reduction engine 68 may then estimate the position and speed of the vehicle in front of the vehicle 12 based on the positions and speeds of the identified vehicles in front of the vehicle 12. For example, the traffic reduction engine 68 may estimate the position and speed of the vehicle in front of the vehicle 12 as the average of the positions and speeds of the identified vehicles in front of the vehicle 12. Furthermore, the traffic reduction engine 68 may estimate the position and speed of the vehicle behind the vehicle 12 based on the positions and speeds of the identified vehicles behind the vehicle 12. For example, the traffic reduction engine 68 may estimate the position and speed of the vehicle behind the vehicle 12 as the average of the positions and speeds of the identified vehicles behind the vehicle 12.
  • the traffic reduction engine 68 may identify the vehicle in front of the vehicle 12 and the vehicle behind the vehicle 12 based on image or video data from infrastructure components 306 on the road segment. More specifically, the traffic reduction engine 68 may determine the license plate number and/or the make and model of the vehicle in front of the vehicle 12 and the license plate number and/or the make and model of the vehicle behind the vehicle 12 by analyzing the image or video data, using optical character recognition (OCR), object recognition, or other computer vision techniques.
  • OCR optical character recognition
  • the infrastructure components 306 may also provide sensor data for the identified vehicles including the positions and speeds of the identified vehicles, and the traffic reduction engine 68 may determine the target acceleration based on the positions and speeds of the identified vehicles.
  • the client devices 82a-n may provide indications of the vehicles in which they are traveling, such as the make, model, and/or license plate number for the vehicles.
  • users of the client devices 82a-n may provide the indications of the vehicles via the navigation application 84 by for example, entering in the make, model, and/or license plate number of their respective vehicles.
  • the traffic reduction engine 68 may then determine the positions and speeds of the vehicles in front of and behind the vehicle 12 based on the sensor data from the client devices 82a-n which provide indications of vehicles matching the vehicles identified from the image or video data.
  • the vehicle head unit 14 may receive sensor data from sensors in the vehicle 12 which indicate the distance between the vehicle 12 and the vehicle in front of the vehicle and the distance between the vehicle 12 and the vehicle behind the vehicle.
  • the vehicle 12 may include front-facing and back-facing depth sensors, such as light detection and ranging (LiDAR) sensors, radio detection and ranging (RADAR) sensors, etc.
  • LiDAR light detection and ranging
  • RADAR radio detection and ranging
  • the depth data detected by the front-facing and back-facing depth sensors may be provided to the vehicle head unit 14 which may provide the depth data to the client device 10 via the communication link 16.
  • the client device 10 may then determine the position of the vehicle in front of the vehicle 12 based on the depth data and the position of the client device 10 from the GPS module. Similarly, the client device 10 may then determine the position of the vehicle behind the vehicle 12 based on the depth data and the position of the client device 10 from the GPS module. The client device 10 may also determine the speed of the vehicle in front of the vehicle 12 based on changes in the depth data.
  • the depth data may be provided to the client device 10 continuously or periodically (e.g., every second, every 5 seconds, every 10 seconds, etc.), and the client device 10 may determine the speed of the vehicle in front of the vehicle 12 based on the change in the depth data over a particular time period and the speed of the vehicle 12 during that time period from the GPS module and/or the accelerometer.
  • the client device 10 may also determine the speed of the vehicle behind the vehicle 12 in a similar. Then the client device 10 may determine the target acceleration based on the positions and speeds of the vehicles in front of and behind the vehicle 12 and the position and speed of the vehicle 12.
  • the client device 10 may provide the positions and speeds of the vehicles in front of and behind the vehicle 12 and the position and speed of the vehicle 12 to the server device 60, which in turn determines the target acceleration and provides an indication of the target speed to the client device 10.
  • the client device 10 provides the depth data to the server device 60 which determines the positions and speeds of the vehicles in front of and behind the vehicle 12. The server device 60 then determines the target acceleration based on the positions and speeds of the vehicles in front of and behind the vehicle 12 and the position and speed of the vehicle 12.
  • the traffic reduction engine 68 then provides an indication of the target speed to the speed display 322.
  • the indication of the target speed is a numeric indication or a background color from a set of background colors.
  • the indication of the target speed may be a feedback signal indicative of the difference between the target speed and the current speed.
  • the feedback signal may be provided to a computing device within the vehicle 12 that controls some operation of the vehicle 12 (e.g., a throttle control), such as a computing device in an autonomous vehicle, a semi-autonomous vehicle, or any other vehicle having autonomous operation features. In this manner, the computing device may control the vehicle 12 to adjust the speed and travel at the target speed.
  • Figs. 4A and 4B include example speed displays 400, 450 indicating target speeds for a vehicle 12 approaching a road segment with traffic.
  • the speed displays 400 may be presented on the user interface 332 of the client device 10 or on a vehicle head unit 14.
  • Each example speed display 400, 450 includes a numeric indication of the target speed 402, 452 for the vehicle 12, a background color or shading 404, 454 indicating that the vehicle 12 should speed up, slow down, stay at the same speed, rapidly decelerate, etc.
  • the speed displays 400, 450 may be presented with a first background color or shading indicating that the vehicle 12 should speed up, a second background color or shading indicating that the vehicle 12 should slow down, a third background color or shading indicating that the vehicle 12 should remain at the same speed, a fourth background color or shading indicating that the vehicle 12 should rapidly decelerate, etc.
  • Each example speed display 400, 450 also includes another indicator 406, 456 regarding whether the vehicle should speed up, slow down, stay at the same speed, etc., such as a directional arrow.
  • Fig. 5 illustrates an example method 500 for use in controlling the speed of a vehicle, which can be implemented at a network server (such as the server device 60), for example.
  • the method can be implemented in a set of instructions stored on a computer- readable memory and executable at one or more processors of the server device 60.
  • the method can be implemented by the traffic reduction engine 68.
  • sensor data is received from client devices 82a-n operating in vehicles on a road segment. Sensor data may also be received from infrastructure
  • the server device 60 may analyze the sensor data to determine whether there is a threshold amount of traffic on the road segment (block 504). In some implementations, the server device 60 may also analyze the sensor data to determine whether the traffic is caused by an intersection, traffic signal, accident, construction, lane closure, etc., or due to vehicles failing to maintain threshold following distances on the road segment.
  • the threshold amount of traffic may be a traffic density for the road segment, such as 100 vehicles per mile, 200 vehicles per mile, etc. In other implementations, the threshold amount of traffic may be based on a threshold speed for vehicles on the road segment relative to the speed limit for the road segment.
  • the threshold amount of traffic may be based on a threshold deceleration for vehicles on the road segment.
  • the server device 60 may receive traffic data from a traffic server indicating the amount of traffic on the road segment.
  • the traffic server may provide a traffic density for the road segment, a categorical description of the amount of traffic, such as light, medium, or heavy, or an indication of an expected amount of additional time for traversing the road segment due to the traffic.
  • the threshold amount of traffic may be a threshold traffic density (e.g., 100 vehicles per mile), a threshold traffic category (e.g., medium or above), or a threshold amount of additional time for traversing the road segment due to the traffic (e.g., 5 minutes).
  • the server device 60 may compare average speed and/or acceleration/deceleration values for vehicles on the road segment to a threshold speed or deceleration to determine whether the road segment has a threshold amount of traffic.
  • the threshold speed may be based on the speed limit for the road segment, such that the threshold speed for a road segment having a speed limit of 55 mph, for example, is higher than the threshold speed for a road segment having a speed limit of 35 mph.
  • the sensor data from the infrastructure components 306 may include image or video data from a camera on the road segment. The server device 60 may analyze the image or video data to determine that there are no accidents, lane closures, traffic signals, construction, etc., on the road segment.
  • the server device 60 may flag the road segment and store indications of road segments having more than the threshold amount of traffic at the particular time. Once the server device 60 determines that the road segment does not have the threshold amount of traffic, the server device 60 may remove the road segment from the list.
  • the server device 60 may compare the current location to the indications of road segments having more than the threshold amount of traffic to determine whether the vehicle 12 is on or approaching a road segment having more than the threshold amount of traffic.
  • the server device 60 may determine that the vehicle 12 is approaching the road segment when the vehicle 12 is within a threshold distance of the road segment (e.g., 500 ft, half of a mile, one mile, etc.), and/or when the vehicle 12 is travelling toward the road segment according to the direction of travel of the vehicle.
  • a threshold distance of the road segment e.g., 500 ft, half of a mile, one mile, etc.
  • a target speed for the vehicle 12 is determined to maintain a bilateral following distance between the vehicle 12 and the vehicles in front of and behind the vehicle 12 to reduce the traffic (block 508).
  • the server device 60 determines the target speed for a particular time period (e.g., 10 seconds, 30 seconds, etc.) by determining a target acceleration for the particular time period and a current speed of the vehicle 12. The server device 60 then identifies the target speed as the sum of the current speed and the product of the target acceleration and the particular time period. As described above, the server device 60 determines the target acceleration based on the position and speed of the vehicle 12 according to sensor data from the client device 10, and the positions and speeds of a vehicle or vehicles in front of and behind the vehicle 12 according to sensor data from the other client devices 82a-n.
  • a particular time period e.g. 10 seconds, 30 seconds, etc.
  • the positions and speeds of vehicles directly in front of the vehicle 12 may be estimated based on a combination of the positions and speeds of several vehicles within a threshold distance in front of the vehicle 12. Furthermore, the positions and speeds of vehicles directly behind the vehicle 12 may be estimated based on a combination of the positions and speeds of several vehicles within a threshold distance behind the vehicle 12.
  • the server device 60 provides an indication of the target speed for example, to the client device 10 or to a vehicle head unit 14.
  • the indication of the target speed is a numeric indication or a background color from a set of background colors.
  • the indication of the target speed may be a feedback signal indicative of the difference between the target speed and the current speed.
  • the feedback signal may be provided to a computing device within the vehicle 12 that controls some operation of the vehicle 12 (e.g., a throttle control), such as a computing device in an autonomous vehicle, a semi-autonomous vehicle, or any other vehicle having autonomous operation features to control the vehicle 12 to adjust the speed and travel at the target speed.
  • the client device 10 continuously or periodically provides sensor data to the server device 60 indicating the current location and/or speed of the vehicle 12.
  • the server device 60 may then generate updated target speeds, periodically (e.g., every 30 seconds, every minute, every 2 minutes, every 5 minutes, etc.) or continuously, based on the most recent location and speed of the vehicle 12 and most recent locations and speeds of vehicles in front of and behind the vehicle 12 which are on or approaching the road segment.
  • the server device 60 then provides indications of the updated target speeds for example, to the client device 10 or to the vehicle head unit 14. In this manner, a user may adjust the speed of the vehicle 12 accordingly.
  • Fig. 6 illustrates an example method 600 for use in controlling the speed of a vehicle, which can be implemented at a client device (such as the client device 10), for example.
  • the method can be implemented in a set of instructions stored on a computer- readable memory and executable at one or more processors of the client device 10.
  • the method can be implemented by the speed display 322.
  • the client device 10 operating in a vehicle 12, provides an indication of its current location to the server device 60.
  • the client device 10 may provide indications of its current location continuously to the server device 60, periodically, at predetermined time intervals, or in any other suitable manner.
  • the client device 10 receives an indication from the server device 60 of a target speed to travel at as the vehicle 12 approaches a road segment with more a threshold amount of traffic.
  • the client device 10 determines the current speed of the vehicle 12, for example based on sensor data from the GPS module and/or the accelerometer.
  • the client device 10 then generates a feedback signal indicative of the difference between the current speed and the target speed.
  • the feedback signal may be an indication of the target speed displayed on the user interface 332, such as the speed displays 400, 450 shown in Figs. 4A and 4B. More specifically, the user interface 332 may present a numeric indication of the target speed for the vehicle 12, a background color or shading indicating that the vehicle 12 should speed up, slow down, stay at the same speed, rapidly decelerate, etc., based on the current speed of the vehicle 12, a directional arrow indicating that the vehicle 12 should speed up, slow down, stay at the same speed, rapidly decelerate, etc., based on the current speed of the vehicle 12, or any other suitable indicator.
  • the feedback signal may be an indication of the target speed which is provided to a throttle control of the vehicle 12.
  • the client device 10 may provide the indication of the target speed to a computing device within the vehicle 12 that controls some operation of the vehicle 12, such as the vehicle head unit 14. The computing device may then control the vehicle 12 to travel at the target speed.
  • Modules may constitute either software modules (e.g., code stored on a machine-readable medium) or hardware modules.
  • a hardware module is tangible unit capable of performing certain operations and may be configured or arranged in a certain manner.
  • one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware modules of a computer system e.g., a processor or a group of processors
  • software e.g., an application or application portion
  • a hardware module may be implemented mechanically or electronically.
  • a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application- specific integrated circuit (ASIC)) to perform certain operations.
  • a hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
  • the term hardware should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein.
  • hardware modules are temporarily configured (e.g., programmed)
  • each of the hardware modules need not be configured or instantiated at any one instance in time.
  • the hardware modules comprise a general-purpose processor configured using software
  • the general-purpose processor may be configured as respective different hardware modules at different times.
  • Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
  • Hardware and software modules can provide information to, and receive information from, other hardware and/or software modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple of such hardware or software modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware or software modules. In embodiments in which multiple hardware modules or software are configured or instantiated at different times, communications between such hardware or software modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware or software modules have access. For example, one hardware or software module may perform an operation and store the output of that operation in a memory device to which it is
  • a further hardware or software module may then, at a later time, access the memory device to retrieve and process the stored output.
  • Hardware and software modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
  • processors may be temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions.
  • the modules referred to herein may, in some example embodiments, comprise processor-implemented modules.
  • the methods or routines described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or processors or processor-implemented hardware modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
  • the one or more processors may also operate to support performance of the relevant operations in a“cloud computing” environment or as an SaaS.
  • a“cloud computing” environment or as an SaaS.
  • at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs).
  • the performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines.
  • the one or more processors or processor- implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the one or more processors or processor-implemented modules may be distributed across a number of geographic locations.
  • any reference to“one embodiment” or“an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment.
  • the appearances of the phrase“in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
  • Coupled and “connected” along with their derivatives.
  • some embodiments may be described using the term“coupled” to indicate that two or more elements are in direct physical or electrical contact.
  • the term“coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.
  • the embodiments are not limited in this context.
  • the terms“comprises,”“comprising,”“includes,”“including,” “has,”“having” or any other variation thereof are intended to cover a non-exclusive inclusion.
  • a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Chemical & Material Sciences (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Combustion & Propulsion (AREA)
  • Analytical Chemistry (AREA)
  • Automation & Control Theory (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Atmospheric Sciences (AREA)
  • Human Computer Interaction (AREA)
  • Multimedia (AREA)
  • Theoretical Computer Science (AREA)
  • Traffic Control Systems (AREA)
EP19736922.6A 2019-06-24 2019-06-24 Phantom traffic jam detection and avoidance Pending EP3928300A1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2019/038664 WO2020263214A1 (en) 2019-06-24 2019-06-24 Phantom traffic jam detection and avoidance

Publications (1)

Publication Number Publication Date
EP3928300A1 true EP3928300A1 (en) 2021-12-29

Family

ID=67185771

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19736922.6A Pending EP3928300A1 (en) 2019-06-24 2019-06-24 Phantom traffic jam detection and avoidance

Country Status (6)

Country Link
US (1) US11928961B2 (ko)
EP (1) EP3928300A1 (ko)
JP (1) JP7418463B2 (ko)
KR (1) KR20220023993A (ko)
CN (1) CN113748447A (ko)
WO (1) WO2020263214A1 (ko)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4147107A4 (en) * 2020-05-04 2024-06-19 Magna Electronics Inc. INFRASTRUCTURE INTERACTION SYSTEM AND PROCEDURES
CN113335292B (zh) * 2021-06-22 2022-03-22 北京百度网讯科技有限公司 车辆控制方法、装置、设备和计算机存储介质
FR3133815A1 (fr) * 2022-03-23 2023-09-29 Hypervisoul Group Methode pour augmenter la capacite de transport d'une route pour vehicules connectes automatises
CN114495509B (zh) * 2022-04-08 2022-07-12 四川九通智路科技有限公司 基于深度神经网络监控隧道运行状态的方法
CN117641278A (zh) * 2022-08-12 2024-03-01 通用汽车环球科技运作有限责任公司 用于交通状况洞察的系统和方法
CN115384552B (zh) * 2022-09-29 2024-09-06 阿波罗智能技术(北京)有限公司 自动驾驶车辆的控制方法、装置和自动驾驶车辆
US20240157937A1 (en) * 2022-10-31 2024-05-16 Nissan North America, Inc. Vehicle on-board unit
WO2024177671A1 (en) * 2023-02-22 2024-08-29 Google Llc System and method for reducing rapid deceleration of vehicles
DE102023105055A1 (de) 2023-03-01 2024-09-05 Cariad Se Verfahren zum Leiten eines Kollektivs von Kraftfahrzeugen auf einer Fahrbahn, Fahrassistenzsystem für ein Kraftfahrzeug, Kraftfahrzeug und Verkehrsleitvorrichtung
CN117275236B (zh) * 2023-10-11 2024-04-05 宁波宁工交通工程设计咨询有限公司 基于多目标识别的交通拥堵管理方法及系统

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3394662B2 (ja) 1996-08-30 2003-04-07 沖電気工業株式会社 交通流計測方法および装置
US6615130B2 (en) 2000-03-17 2003-09-02 Makor Issues And Rights Ltd. Real time vehicle guidance and traffic forecasting system
DE10037827B4 (de) 2000-08-03 2008-01-10 Daimlerchrysler Ag Fahrzeugautonomes Verkehrsinformationssystem
JP3854881B2 (ja) 2002-03-18 2006-12-06 株式会社東芝 渋滞回避支援装置
JP2005112255A (ja) * 2003-10-10 2005-04-28 Sony Corp 車載装置及び車載装置の表示方法
JP2005186831A (ja) 2003-12-26 2005-07-14 Toyota Motor Corp 車両の統合制御システム
JP4622650B2 (ja) 2005-04-21 2011-02-02 アイシン・エィ・ダブリュ株式会社 渋滞案内方法及び車載装置
US7925426B2 (en) 2005-11-17 2011-04-12 Motility Systems Power management systems and devices
US7912628B2 (en) * 2006-03-03 2011-03-22 Inrix, Inc. Determining road traffic conditions using data from multiple data sources
US7739040B2 (en) 2006-06-30 2010-06-15 Microsoft Corporation Computation of travel routes, durations, and plans over multiple contexts
US20110037619A1 (en) * 2009-08-11 2011-02-17 On Time Systems, Inc. Traffic Routing Using Intelligent Traffic Signals, GPS and Mobile Data Devices
US8676466B2 (en) 2009-04-06 2014-03-18 GM Global Technology Operations LLC Fail-safe speed profiles for cooperative autonomous vehicles
US9688286B2 (en) 2009-09-29 2017-06-27 Omnitracs, Llc System and method for integrating smartphone technology into a safety management platform to improve driver safety
US8494759B2 (en) 2010-09-08 2013-07-23 Toyota Motor Engineering & Manufacturing North America, Inc. Vehicle speed indication using vehicle-infrastructure wireless communication
US8195313B1 (en) * 2010-11-19 2012-06-05 Nest Labs, Inc. Thermostat user interface
US9081651B2 (en) 2013-03-13 2015-07-14 Ford Global Technologies, Llc Route navigation with optimal speed profile
US9272711B1 (en) * 2014-12-31 2016-03-01 Volkswagen Ag Congestion-friendly adaptive cruise control
US9896096B2 (en) 2016-04-11 2018-02-20 David E. Newman Systems and methods for hazard mitigation
CN106023626A (zh) * 2016-06-17 2016-10-12 深圳市元征科技股份有限公司 一种交通拥堵提示方法、服务器及车载设备
CN106056910A (zh) * 2016-07-13 2016-10-26 乐视控股（北京）有限公司 一种交通状态检测方法和装置
US20180301026A1 (en) * 2017-04-12 2018-10-18 Dmitri Yudanov Method and apparatus for vehicle traffic congestion prevention
JP2018190315A (ja) 2017-05-11 2018-11-29 住友電気工業株式会社 コンピュータプログラム、交通管制装置および交通管制方法
US10358129B2 (en) * 2017-06-06 2019-07-23 Toyota Motor Engineering & Manufacturing North America, Inc. Systems and methods for dynamic vehicle control according to traffic
US10403133B1 (en) * 2017-07-27 2019-09-03 State Farm Mutual Automobile Insurance Company Vehicle roadway traffic density management systems for optimizing vehicle spacing
CN111819608A (zh) * 2018-03-07 2020-10-23 谷歌有限责任公司 用于有效地穿越交叉路口的驾驶员反馈
EP3791374A1 (en) * 2018-08-17 2021-03-17 Google LLC Reducing vehicular congestion at an intersection
US11232705B2 (en) * 2018-11-28 2022-01-25 Toyota Jidosha Kabushiki Kaisha Mitigation of traffic oscillation on roadway

Also Published As

Publication number Publication date
US20220108610A1 (en) 2022-04-07
JP7418463B2 (ja) 2024-01-19
CN113748447A (zh) 2021-12-03
KR20220023993A (ko) 2022-03-03
US11928961B2 (en) 2024-03-12
WO2020263214A1 (en) 2020-12-30
JP2022538710A (ja) 2022-09-06

Similar Documents

Publication Publication Date Title
US11928961B2 (en) Phantom traffic jam detection and avoidance
US20210108942A1 (en) Warning polygons for weather from vehicle sensor data
US10311728B2 (en) Method and apparatus for providing a confidence-based road event message
US10296795B2 (en) Method, apparatus, and system for estimating a quality of lane features of a roadway
US11263549B2 (en) Method, apparatus, and system for in-vehicle data selection for feature detection model creation and maintenance
EP3222973B1 (en) Map updates from a connected vehicle fleet
US11681294B2 (en) Method and system for prediction of roadwork zone
US10764713B2 (en) Map based feedback loop for vehicle observation
US9886857B2 (en) Organized intelligent merging
US11410074B2 (en) Method, apparatus, and system for providing a location-aware evaluation of a machine learning model
EP3051515B1 (en) Method and apparatus for providing aggregated notifications for dangerous curves
EP3227638B1 (en) Method and apparatus for providing point of interest information
US11263726B2 (en) Method, apparatus, and system for task driven approaches to super resolution
EP3290867A1 (en) Method, apparatus and computer program product for a navigation system user interface
EP3543907A1 (en) Method, apparatus, and system for dynamic adaptation of an in-vehicle feature detector
US11055862B2 (en) Method, apparatus, and system for generating feature correspondence between image views
JP7399891B2 (ja) ナビゲーション中に難しい操縦についての追加の命令を提供すること
US20150260532A1 (en) Systems and methods for updating map information using local driver input
US20200250864A1 (en) Hazard warning polygons constrained based on end-use device
US20220410881A1 (en) Apparatus and methods for predicting a state of visibility for a road object based on a light source associated with the road object
US12097881B2 (en) Method, apparatus, and system for determining an autonomous vehicle operational strategy when detecting wrong way driving
US20220207996A1 (en) Method, apparatus, and system for real-time traffic based location referencing with offsets for road incident reporting
WO2024177671A1 (en) System and method for reducing rapid deceleration of vehicles
US20240192018A1 (en) System and method for virtual lane generation
US20240192017A1 (en) System and a method for validation of sensor data

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210923

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20221207