A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the disclosure herein and to the drawings that form a part of this document: Copyright 2016-2017, TuSimple, All Rights Reserved.
This patent document pertains generally to tools (systems, apparatuses, methodologies, computer program products, etc.) for autonomous driving simulation systems, trajectory planning, vehicle control systems, and autonomous driving systems, and more particularly, but not by way of limitation, to a system and method for real world autonomous vehicle trajectory simulation.
An autonomous vehicle is often configured to follow a trajectory based on a computed driving path. However, when variables such as obstacles are present on the driving path, the autonomous vehicle must perform control operations so that the vehicle may be safely driven by changing the driving path to avoid the obstacles. In the related art, autonomous vehicle control operations have been determined by representing spatial information (e.g., a coordinate, a heading angle, a curvature, etc.) of the driving path as a polynomial expression or mathematical function for a movement distance in order to avoid a stationary obstacle. However, when dynamic obstacles are present on the driving path, the autonomous vehicle according to the related art may not accurately predict whether or not the vehicle will collide with the dynamic obstacles. In particular, the related art does not consider the interaction between the autonomous vehicle and other dynamic vehicles. Therefore, conventional autonomous vehicle control systems cannot accurately predict the future positions of other proximate dynamic vehicles. Further, conventional simulation systems do not consider the typical responses and behaviors of human drivers, which is often different than the response or behavior generated by a computing system. As a result, the optimal behavior of the conventional autonomous vehicle cannot be achieved.
A system and method for real world autonomous vehicle trajectory simulation is disclosed herein. Specifically, the present disclosure describes a data-driven system and method to simulate trajectory patterns of vehicles driven by human drivers for the purpose of establishing a traffic simulation with high fidelity. To eliminate the gap between simulated trajectories and actual trajectories of vehicles driven by human drivers under a similar situation, the system and method of various example embodiments may include various sensors to collect vehicle sensor data corresponding to driving patterns of human drivers, which is considered when building models to simulate trajectories of vehicles driven by human drivers.
The various embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which:
In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It will be evident, however, to one of ordinary skill in the art that the various embodiments may be practiced without these specific details.
A system and method for real world autonomous vehicle trajectory simulation is disclosed herein. Specifically, the present disclosure describes a data-driven system and method to simulate trajectory patterns of vehicles driven by human drivers for the purpose of establishing a traffic simulation with high fidelity. To eliminate the gap between simulated trajectories and actual trajectories of vehicles driven by human drivers under a similar situation, the system and method of various example embodiments may include various sensors to collect vehicle sensor data corresponding to driving patterns of human drivers, which is considered when building models to simulate trajectories of vehicles driven by human drivers.
As described in various example embodiments, a system and method for real world autonomous vehicle trajectory simulation are described herein. Referring to
The data collection system 201 can include an array of perception information gathering devices or sensors that may include image generating devices (e.g., cameras), light amplification by stimulated emission of radiation (laser) devices, light detection and ranging (LIDAR) devices, global positioning system (GPS) devices, sound navigation and ranging (sonar) devices, radio detection and ranging (radar) devices, and the like. The perception information gathered by the information gathering devices at various traffic locations can include traffic or vehicle image data, roadway data, environmental data, distance data from LIDAR or radar devices, and other sensor information received from the information gathering devices of the data collection system 201 positioned adjacent to particular roadways (e.g., monitored locations). Additionally, the data collection system 201 can include information gathering devices installed in moving test vehicles being navigated through pre-defined routings in an environment or location of interest. The perception information can include data from which a position and velocity of neighboring vehicles in the vicinity of or proximate to the autonomous vehicle can be obtained or calculated. Corresponding ground truth data can also be gathered by the data collection system 201.
The real world data collection system 201 can collect actual trajectories of vehicles and corresponding ground truth data under different scenarios and different driver intentions. The different scenarios can correspond to different locations, different traffic patterns, different environmental conditions, and the like. The scenarios can be represented, for example, by an occupancy grid, a collection of vehicle states on a map, or a graphical representation, such as a top-down image of one or more areas of interest. The driver intentions can correspond to a driver's short term driving goals, such as merging to a ramp, making right turn at an intersection, making a U-turn, and the like. The driver intentions can also correspond to a set of driver or vehicle control actions to accomplish a particular short term driving goal.
The image data and other perception data and ground truth data collected by the data collection system 201 reflects truly realistic, real-world traffic information related to the locations or routings, the scenarios, and the driver intentions being monitored. Using the standard capabilities of well-known data collection devices, the gathered traffic and vehicle image data and other perception or sensor data can be wirelessly transferred (or otherwise transferred) to a data processor of a standard computing system, upon which the real world data collection system 201 can be executed. Alternatively, the gathered traffic and vehicle image data and other perception or sensor data can be stored in a memory device at the monitored location or in the test vehicle and transferred later to the data processor of the standard computing system. The traffic and vehicle image data and other perception or sensor data, the ground truth data and the driver intention data gathered or calculated by the real world data collection system 201 can be used to generate training data, which can be processed by the one or more trajectory prediction models 180 in a training phase. For example, as well-known, neural networks, or other machine learning systems, can be trained to produce configured output based on training data provided to the neural network or other machine learning system in a training phase. The training data provided by the real world data collection system 201 can be used to build and/or train the generative prediction model (trajectory prediction models 180 shown in
Referring to
In an example embodiment, the processing performed by the example embodiments can be divided into two stages: the offline training phase, and the operational or simulation phase. In the offline training phase, the processed data provided by the real world data collection system 201 can be used to generate and/or train the plurality of trajectory prediction models 180 (shown in
After the prediction models 180 are trained in the training phase as described above, the prediction models 180 can be deployed in an operational or simulation phase of the autonomous vehicle trajectory simulation system 202. In the operational or simulation phase, the autonomous vehicle trajectory simulation system 202 can generate vicinal scenarios for each of a plurality of simulated vehicles in a simulation system. The vicinal scenarios serve to predict the behaviors and trajectories of vehicles in simulation based on scenarios driven by a vicinal scene data generator 173 and vehicle intention data 174 described in more detail below.
As a result of the processing performed by the autonomous vehicle trajectory simulation system 202, data corresponding to predicted or simulated driver behaviors and predicted or simulated vehicle trajectories can be produced and fed back into the simulation system 202 to improve the accuracy of the predicted trajectories. Ultimately, the improved simulation system 202 can be used to provide highly accurate predicted traffic trajectory information to a user or for configuration of a control system of an autonomous vehicle. In particular, the predicted or simulated traffic trajectory information can be provided to a system component used to create a virtual world where a control system for an autonomous vehicle can be trained and improved. The virtual world is configured to be identical (as possible) to the real world where vehicles are operated by human drivers. In other words, the predicted or simulated traffic trajectory information generated by the autonomous vehicle trajectory simulation system 202 is indirectly useful for configuring the control systems for an autonomous vehicle. It will be apparent to those of ordinary skill in the art that the autonomous vehicle trajectory simulation system 202 and the predicted or simulated traffic trajectory information described and claimed herein can be implemented, configured, processed, and used in a variety of other applications and systems as well.
Referring again to
A data storage device or memory 172 is also provided in the autonomous vehicle trajectory simulation system 202 of an example embodiment. The memory 172 can be implemented with standard data storage devices (e.g., flash memory, DRAM, SIM cards, or the like) or as cloud storage in a networked server. In an example embodiment, the memory 172 can be used to store a set of vehicle intention data 174. The vehicle intention data 174 corresponds to a data representation of various types of simulated vehicle and/or driver intentions. The simulated vehicle and/or driver intentions can correspond to a driver's short term driving goals, such as merging to a ramp, making right turn at an intersection, making a U-turn, and the like. The simulated vehicle and/or driver intentions can also correspond to a set of driver or vehicle control actions to accomplish a particular short term driving goal. The simulated vehicle and/or driver intentions for a variety of different vehicle actions and behaviors can be stored in the memory 172 as vehicle intention data 174. In a particular embodiment, the vicinal scene data generator module 173 can select a particular set of the vehicle intention data 174 to be processed with a particular vicinal scenario dataset configured by the vicinal scene data generator module 173 for an iteration of the simulation. In another embodiment, the particular set of the vehicle intention data 174 can be pre-determined prior to the execution of the simulation. For each iteration of the simulation, the vehicle intention data 174 can be passed to one of the plurality of prediction models 180 as shown in
In the example embodiment shown in
In various example embodiments, the plurality of prediction models 180 can be configured or trained to simulate more than the typical driving behaviors. To simulate an environment that is identical to the real world as much as possible, the prediction models 180 can receive training related to typical driving behaviors, which represent average people. Additionally, the prediction models 180 can receive training related to atypical driving behaviors. In most cases, training data related to typical and atypical driver and vehicle behaviors is used by the data collection system 201 to train the prediction models 180. In other words, in reality, most human drivers drive vehicles in a pleasant and humble way, while other drivers drive aggressively and impatiently. Because the plurality of prediction models 180 of an example embodiment is trained using real world driving and traffic data from the data collection system 201, the plurality of prediction models 180 of the various example embodiments receives training related to the driving behaviors of polite and impolite drivers as well as patient and impatient drivers in the virtual world. In all, the trained prediction models 180 can be configured with data representing driving behaviors that are as varied as possible. In some implementations, the dynamics of how a human may respond to stimuli may be included in the logic implemented in the trained prediction models 180, which may include, for example, a metric of how aggressively the driver brakes, turns, and accelerates. In some implementations, an aggressive driver may be modeled as one who applies very high control inputs to achieve the desired vehicle speeds, while a conservative driver may use more gradual control inputs. In some implementations, this may be modeled using parameterized values, with the input being controlled to the desired value. In some implementations, by adjusting the parameterized values, the aggressiveness of the simulated driver may be increased or decreased.
As described above, the plurality of trained prediction models 180, for each iteration of the simulation in the simulation or operational phase, enable the generation of a distribution of vehicle trajectories with corresponding likelihood ratings or probability values for each of a plurality of simulated vehicles of the simulation based on a particular vicinal scenario dataset configured by the vicinal scene data generator module 173 and a corresponding vehicle intention dataset 174. For each iteration of the simulation and for each of the plurality of trained prediction models 180, one of the plurality of trajectory samplers 182 can select a particular trajectory from the distribution of vehicle trajectories generated for the particular iteration. The particular trajectory can be selected based on a variety of pre-defined criteria including a maximal or minimal likelihood rating or probability value, conformity with pre-defined safety parameters, conformity with pre-defined economy parameters, conformity with pre-defined timing or distance parameters, and the like. The particular trajectory selected by the one of the plurality of trajectory samplers 182 can be stored in the memory 172 as vehicle trajectory data 176. Once the particular trajectory is selected and the vehicle trajectory data 176 for the current iteration is stored, the state updater module 175 can update the states and predicted trajectories of all simulated vehicles in the simulation according to the selected trajectory. The predicted vehicle trajectories retained as vehicle trajectory data 176 can be saved and fed back into the state updated module 175 to improve the accuracy of the predicted trajectories. At this point, the current iteration of the simulation is complete and control is passed back to the vicinal scene data generator module 173 for the start of the next iteration of the simulation in the simulation or operational phase. As described above, the vicinal scene data generator module 173 generates a new vicinal scenario for each simulated vehicle in the simulation system for the next iteration. The new vicinal scenarios are passed to the plurality of trained prediction models 180. A new set of vehicle intention data 174 is also selected or generated and passed to the plurality of trained prediction models 180. The trained prediction models 180 use the new vicinal scenarios and the new set of vehicle intention data 174 to produce a new distribution of vehicle trajectories for each of a plurality of simulated vehicles with corresponding likelihood ratings or probability values for the next iteration as described above. As a result, the autonomous vehicle trajectory simulation system 202 of an example embodiment can produce an interactive, realistic traffic simulation.
Referring now to
The example computing system 700 can include a data processor 702 (e.g., a System-on-a-Chip (SoC), general processing core, graphics core, and optionally other processing logic) and a memory 704, which can communicate with each other via a bus or other data transfer system 706. The mobile computing and/or communication system 700 may further include various input/output (I/O) devices and/or interfaces 710, such as a touchscreen display, an audio jack, a voice interface, and optionally a network interface 712. In an example embodiment, the network interface 712 can include one or more radio transceivers configured for compatibility with any one or more standard wireless and/or cellular protocols or access technologies (e.g., 2nd (2G), 2.5, 3rd (3G), 4th (4G) generation, and future generation radio access for cellular systems, Global System for Mobile communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (WCDMA), LTE, CDMA2000, WLAN, Wireless Router (WR) mesh, and the like). Network interface 712 may also be configured for use with various other wired and/or wireless communication protocols, including TCP/IP, UDP, SIP, SMS, RTP, WAP, CDMA, TDMA, UMTS, UWB, WiFi, WiMax, Bluetooth™, IEEE 802.11x, and the like. In essence, network interface 712 may include or support virtually any wired and/or wireless communication and data processing mechanisms by which information/data may travel between a computing system 700 and another computing or communication system via network 714.
The memory 704 can represent a machine-readable medium on which is stored one or more sets of instructions, software, firmware, or other processing logic (e.g., logic 708) embodying any one or more of the methodologies or functions described and/or claimed herein. The logic 708, or a portion thereof, may also reside, completely or at least partially within the processor 702 during execution thereof by the mobile computing and/or communication system 700. As such, the memory 704 and the processor 702 may also constitute machine-readable media. The logic 708, or a portion thereof, may also be configured as processing logic or logic, at least a portion of which is partially implemented in hardware. The logic 708, or a portion thereof, may further be transmitted or received over a network 714 via the network interface 712. While the machine-readable medium of an example embodiment can be a single medium, the term “machine-readable medium” should be taken to include a single non-transitory medium or multiple non-transitory media (e.g., a centralized or distributed database, and/or associated caches and computing systems) that store the one or more sets of instructions. The term “machine-readable medium” can also be taken to include any non-transitory medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the various embodiments, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The term “machine-readable medium” can accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.
The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
This application is a continuation of U.S. patent application Ser. No. 15/796,765, filed Oct. 28, 2017, titled “System and Method for Real World Autonomous Vehicle Trajectory Simulation.”
Number | Name | Date | Kind |
---|---|---|---|
7689559 | Canright | Mar 2010 | B2 |
7844595 | Canright | Nov 2010 | B2 |
8041111 | Wilensky | Oct 2011 | B1 |
8064643 | Stein | Nov 2011 | B2 |
8082101 | Stein | Dec 2011 | B2 |
8126642 | Trepagnier | Feb 2012 | B2 |
8164628 | Stein | Apr 2012 | B2 |
8175376 | Marchesotti | May 2012 | B2 |
8271871 | Marchesotti | Sep 2012 | B2 |
8378851 | Stein | Feb 2013 | B2 |
8401292 | Park | Mar 2013 | B2 |
8437890 | Anderson | May 2013 | B2 |
8478072 | Aisaka | Jul 2013 | B2 |
8553088 | Stein | Oct 2013 | B2 |
8744648 | Anderson | Jun 2014 | B2 |
8805601 | Aso | Aug 2014 | B2 |
8908041 | Stein | Dec 2014 | B2 |
8917169 | Schofield | Dec 2014 | B2 |
8963913 | Baek | Feb 2015 | B2 |
8981966 | Stein | Mar 2015 | B2 |
8993951 | Schofield | Mar 2015 | B2 |
9008369 | Schofield | Apr 2015 | B2 |
9025880 | Perazzi | May 2015 | B2 |
9042648 | Wang | May 2015 | B2 |
9117133 | Barnes | Aug 2015 | B2 |
9118816 | Stein | Aug 2015 | B2 |
9120485 | Dolgov | Sep 2015 | B1 |
9122954 | Srebnik | Sep 2015 | B2 |
9145116 | Clarke | Sep 2015 | B2 |
9147255 | Zhang | Sep 2015 | B1 |
9147353 | Slusar | Sep 2015 | B1 |
9156473 | Clarke | Oct 2015 | B2 |
9176006 | Stein | Nov 2015 | B2 |
9179072 | Stein | Nov 2015 | B2 |
9183447 | Gdalyahu | Nov 2015 | B1 |
9185360 | Stein | Nov 2015 | B2 |
9191634 | Schofield | Nov 2015 | B2 |
9233659 | Rosenbaum | Jan 2016 | B2 |
9233688 | Clarke | Jan 2016 | B2 |
9248832 | Huberman | Feb 2016 | B2 |
9251708 | Rosenbaum | Feb 2016 | B2 |
9277132 | Berberian | Mar 2016 | B2 |
9280711 | Stein | Mar 2016 | B2 |
9286522 | Stein | Mar 2016 | B2 |
9297641 | Stein | Mar 2016 | B2 |
9299004 | Lin | Mar 2016 | B2 |
9317776 | Honda | Apr 2016 | B1 |
9330334 | Lin | May 2016 | B2 |
9355635 | Gao | May 2016 | B2 |
9365214 | Ben Shalom | Jun 2016 | B2 |
9428192 | Schofield | Aug 2016 | B2 |
9436880 | Bos | Sep 2016 | B2 |
9443163 | Springer | Sep 2016 | B2 |
9446765 | Ben Shalom | Sep 2016 | B2 |
9459515 | Stein | Oct 2016 | B2 |
9466006 | Duan | Oct 2016 | B2 |
9490064 | Hirosawa | Nov 2016 | B2 |
9531966 | Stein | Dec 2016 | B2 |
9555803 | Pawlicki | Jan 2017 | B2 |
9612123 | Levinson | Apr 2017 | B1 |
9720415 | Levinson | Aug 2017 | B2 |
9784592 | Gupta | Oct 2017 | B2 |
9873427 | Danzl | Jan 2018 | B2 |
9878710 | Schmiidderich | Jan 2018 | B2 |
9934688 | Olson | Apr 2018 | B2 |
9989964 | Berntorp | Jun 2018 | B2 |
10019011 | Green | Jul 2018 | B1 |
10055675 | Micks | Aug 2018 | B2 |
10102750 | Aso | Oct 2018 | B2 |
10343685 | Zhu | Jul 2019 | B2 |
10466716 | Su | Nov 2019 | B1 |
10466717 | Su | Nov 2019 | B1 |
10474790 | Sun | Nov 2019 | B2 |
10564643 | Lui | Feb 2020 | B2 |
10569773 | Zhao | Feb 2020 | B2 |
10649458 | Sun | May 2020 | B2 |
10710592 | Lin | Jul 2020 | B2 |
10739775 | Sun | Aug 2020 | B2 |
10782693 | Zhang | Sep 2020 | B2 |
10782694 | Zhang | Sep 2020 | B2 |
10830669 | Sun | Nov 2020 | B2 |
10953880 | Ma | Mar 2021 | B2 |
10953881 | Ma | Mar 2021 | B2 |
20070230792 | Shashua | Oct 2007 | A1 |
20090024357 | Aso | Jan 2009 | A1 |
20100106356 | Trepagnier | Apr 2010 | A1 |
20100226564 | Marchesotti | Sep 2010 | A1 |
20100281361 | Marchesotti | Nov 2010 | A1 |
20100292886 | Szczerba | Nov 2010 | A1 |
20110206282 | Aisaka | Aug 2011 | A1 |
20120083947 | Anderson | Apr 2012 | A1 |
20120105639 | Stein | May 2012 | A1 |
20120140076 | Rosenbaum | Jun 2012 | A1 |
20120274629 | Baek | Nov 2012 | A1 |
20140114556 | Pan | Apr 2014 | A1 |
20140145516 | Hirosawa | May 2014 | A1 |
20140198184 | Stein | Jul 2014 | A1 |
20150062304 | Stein | Mar 2015 | A1 |
20150321699 | Rebhan | Nov 2015 | A1 |
20160037064 | Stein | Feb 2016 | A1 |
20160059855 | Rebhan | Mar 2016 | A1 |
20160094774 | Li | Mar 2016 | A1 |
20160165157 | Stein | Jun 2016 | A1 |
20160200317 | Danzl | Jul 2016 | A1 |
20160210528 | Duan | Jul 2016 | A1 |
20160325743 | Schmudderich | Nov 2016 | A1 |
20170016734 | Gupta | Jan 2017 | A1 |
20170031361 | Olson | Feb 2017 | A1 |
20170039890 | Truong | Feb 2017 | A1 |
20170123428 | Levinson | May 2017 | A1 |
20170124781 | Douillard | May 2017 | A1 |
20170132334 | Levinson | May 2017 | A1 |
20170269561 | Wood | Sep 2017 | A1 |
20170364776 | Micks | Dec 2017 | A1 |
20180086344 | Zhu | Mar 2018 | A1 |
20180120843 | Berntorp | May 2018 | A1 |
20180164804 | Hou | Jun 2018 | A1 |
20180349547 | Sun | Dec 2018 | A1 |
20190025853 | Julian | Jan 2019 | A1 |
20190072966 | Zhang | Mar 2019 | A1 |
20190072973 | Sun | Mar 2019 | A1 |
20190107840 | Green | Apr 2019 | A1 |
20190129436 | Sun | May 2019 | A1 |
20190129831 | Goldberg | May 2019 | A1 |
20190163181 | Liu | May 2019 | A1 |
20190163182 | Li | May 2019 | A1 |
20190337525 | Sippl | Nov 2019 | A1 |
20190367020 | Yan | Dec 2019 | A1 |
20200047769 | Oguro | Feb 2020 | A1 |
20200082248 | Villegas | Mar 2020 | A1 |
Number | Date | Country |
---|---|---|
107452207 | Dec 2017 | CN |
1754179 | Feb 2007 | EP |
2448251 | May 2012 | EP |
2463 843 | Jun 2012 | EP |
2463 843 | Jul 2013 | EP |
2761249 | Aug 2014 | EP |
2463843 | Jul 2015 | EP |
2448251 | Oct 2015 | EP |
2946336 | Nov 2015 | EP |
2993654 | Mar 2016 | EP |
3081419 | Oct 2016 | EP |
WO2005098739 | Oct 2005 | WO |
WO2005098751 | Oct 2005 | WO |
WO2005098782 | Oct 2005 | WO |
WO2010109419 | Sep 2010 | WO |
WO2013045612 | Apr 2013 | WO |
WO2014111814 | Jul 2014 | WO |
WO2014111814 | Jul 2014 | WO |
WO2014201324 | Dec 2014 | WO |
WO2015083009 | Jun 2015 | WO |
WO2015103159 | Jul 2015 | WO |
WO2015125022 | Aug 2015 | WO |
WO2015186002 | Dec 2015 | WO |
WO2015186002 | Dec 2015 | WO |
WO2016135736 | Sep 2016 | WO |
WO2017013875 | Jan 2017 | WO |
Number | Date | Country | |
---|---|---|---|
20200348678 A1 | Nov 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15796765 | Oct 2017 | US |
Child | 16929954 | US |