Patent Grant
12060066
The present teaching generally relates to autonomous driving. More specifically, the present teaching relates to planning and control in autonomous driving.
With recent technological advancement in artificial intelligence (AI), there is a surge in applying AI in different application fields. This includes the field of autonomous driving, in which planning and control are essential. This is shown in
Motion planning may generally refer to the effort of planning the movement of a vehicle to achieve certain effect. For example, the movement of the vehicle may be planned in a way that complies with the traffic regulations or safety. Motion planning is then to determine what movement the vehicle needs to make to achieve that. Behavior planning generally refers to the effort to plan how the vehicle should behave in different situations, e.g., the vehicle behavior while crossing an intersection, the vehicle behavior in staying within or following a lane, or the vehicle behavior in making a turn. For instance, in terms of overtaking a slow moving front vehicle, certain vehicle behavior may be planned. Behavior planning and motion planning may be related. For example, the planned vehicle behavior may need to be translated into motion in order to implement the behavior.
Vehicle control 130 as shown in
Surrounding information 100 in
The planning module 120 may also perform motion planning, which is traditionally based on, e.g., rapidly exploring random trees (RRT) for state space or Markov Decision Process (MDP) for environmental modeling. The planning module 120 may generate, based on the planned route/motion, planning data to be fed to the vehicle control module 130 so that the vehicle control module 130 can proceed to control the vehicle in a way as planned. To make the vehicle to move to carry out the plan, the vehicle control module 130 may then generate control signals 140 which may be sent to different parts of the vehicle to implement the planned vehicle movement. Vehicle control is traditionally exercised based on generic vehicle kinematic models and/or different types of feedback controllers.
Each human driver generally operates or controls a vehicle differently with diverse preferences. Human drivers also operate vehicles adaptively based on real time situations, which may arise out of the present conditions of the vehicle itself, the extrinsic environment conditions that serve to limit the ability of the vehicle to operate, and/or the reaction or response to the current vehicle movement from passengers in the vehicle. For example, with children in the vehicle, a human driver may elect, for safety, to avoid (route planning) a route that is curvy on a snowy day. A human driver may drive in different manners when different passengers are riding in the vehicle to ensure comfort of the passenger. Although a human driver generally controls a vehicle by following a lane by staying roughly in the middle of the lane, the behavior may change when faced with a right turn. In this case, the same human driver may curve to the right side of the lane when the vehicle is approaching the point of the right turn. In addition, different human drivers may curve to the right in different ways. Furthermore, lane changing behavior may also differ with respect to different vehicles in different surrounding situations. The existing technologies do not address those issues, let alone providing solutions.
Therefore, there is a need to provide improved solutions for planning and control in autonomous driving.
The teachings disclosed herein relate to methods, systems, and programming for online services. More particularly, the present teaching relates to methods, systems, and programming for developing a virtual agent that can have a dialog with a user.
In one example, a method for lane planning in an autonomous vehicle is disclosed. Sensor data are received that capture ground images of a road the autonomous vehicle is on. Based on the sensor data, a current lane of the road that autonomous vehicle is currently occupying is detected. Lane control for the autonomous vehicle is planned based on the detected current lane and self-aware capability parameters in accordance with a driving lane control model. The self-aware capability parameters are used to predict operational capability of the autonomous vehicle with respect to a current location of the autonomous vehicle. The driving lane control model is generated based on recorded human driving data to achieve human-like lane control behavior in different scenarios.
In another example, a system for lane planning in an autonomous vehicle is disclosed. The system comprises a driving lane detector and a driving lane planning unit. The driving lane detector is configured for receiving sensor data capturing ground images of a road the autonomous vehicle is on and detecting, from the sensor data, a current lane of the road the autonomous vehicle is currently occupying. The driving lane planning unit is configured for planning lane control for the autonomous vehicle based on the detected current lane and self-aware capability parameters in accordance with a driving lane control model. The self-aware capability parameters are used to predict the operational capability of the autonomous vehicle with respect to a current location of the vehicle. The driving lane control model is generated based on recorded human driving data to achieve human-like lane control behavior in different scenarios.
Other concepts relate to software for implementing the present teaching on developing a virtual agent. A software product, in accord with this concept, includes at least one machine-readable non-transitory medium and information carried by the medium. The information carried by the medium may be executable program code data, parameters in association with the executable program code, and/or information related to a user, a request, content, or information related to a social group, etc.
In one example, machine readable non-transitory medium is disclosed, wherein the medium has information recorded theron for lane control in an autonomous vehicle, where the information, when read by the machine, causes the machine to perform various steps. Sensor data are received that capture ground images of a road the autonomous vehicle is on. Based on the sensor data, a current lane of the road that autonomous vehicle is currently occupying is detected. Lane control for the autonomous vehicle is planned based on the detected current lane and self-aware capability parameters in accordance with a driving lane control model. The self-aware capability parameters are used to predict operational capability of the autonomous vehicle with respect to a current location of the autonomous vehicle. The driving lane control model is generated based on recorded human driving data to achieve human-like lane control behavior in different scenarios.
Additional novel features will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following and the accompanying drawings or may be learned by production or operation of the examples. The novel features of the present teachings may be realized and attained by practice or use of various aspects of the methodologies, instrumentalities and combinations set forth in the detailed examples discussed below.
The methods, systems and/or programming described herein are further described in terms of exemplary embodiments. These exemplary embodiments are described in detail with reference to the drawings. These embodiments are non-limiting exemplary embodiments, in which like reference numerals represent similar structures throughout the several views of the drawings, and wherein:
In the following detailed description, numerous specific details are set forth by way of examples in order to provide a thorough understanding of the relevant teachings. However, it should be apparent to those skilled in the art that the present teachings may be practiced without such details. In other instances, well known methods, procedures, components, and/or circuitry have been described at a relatively high-level, without detail, in order to avoid unnecessarily obscuring aspects of the present teachings.
The present disclosure generally relates to systems, methods, medium, and other implementations for planning and control of route/vehicle behaviors in a self-capability aware, human-like, and personalized manner that is adaptive to real time situations.
Real time data 480 may include various types of information useful or relevant for planning and control of the vehicle.
Real time data related to time may generally include current date, time, or month. Passenger related data may include various characteristics related to the passenger of the vehicle such as passenger reaction cues, which may include visual, acoustic, or behavior cues observed from the passenger, or conditions of the passenger such as mental state, physical state, or functional state of the passenger. The conditions of the passenger may be inferred based on the cues observed from the passenger reaction cues. Weather related data may include the weather of the locale where the vehicle is currently situated. The road related data may include information about the physical condition of the nearby road(s), e.g., wetness, steepness, or curviness of the road, or the local traffic condition such as congestion along the road.
Each of the planning modules may be triggered via some triggering signal. For instance, the route planning module 550 may be activated via a route planning trigger signal; the motion planning module 560 may be activated upon receiving a motion planning trigger signal; while the lane planning module 570 may start to operate when a lane planning trigger signal is received. Such a trigger signal may be manually provided (by, e.g., a driver or a passenger) or automatically generated based on, e.g., certain configuration or certain event. A driver may manually activate the route planning module 550 or any other planning module for the route/motion/lane planning, much like what people do to manually start, e.g., cruise control in a car.
The planning activities may also be activated by a certain configuration or an event. For example, the vehicle may be configured to activate route planning whenever the vehicle accepts an input indicating the next destination. This may be regardless what the current location of the vehicle is. In some embodiments, the planning modules may be always triggered on whenever the vehicle is on and depending on the situation, they may become engaged in different planning activities as needed. In different situations, they may also interact with each other in a manner called for by the situation. For example, the lane planning module 570 may determine to change lane in certain circumstance. Such a planned lane control is output by the lane planning module 570 and may be fed to the motion planning module 560 so that a specific path trajectory (planned motion) appropriate for carrying out the planned lane changing may be further planned by the motion planning module 560.
Output of a planning module may be fed into another within the planning module 440 for either further planning or for providing an input for the future planning of another. For example, the output of the route planning module 550 (planned route 520) may be fed to the motion planning module 560 so that the route information may influence how the vehicle motion is planned. As discussed above, the output (planned lane control 540) of the lane planning module 570 may be fed to the motion planning module 560 so that the lane control behavior planned may be realized via planned motion control. Conversely, the output of the motion planning module 560 (the planned motion 530) may also be fed to the lane planning module 570 to influence the planning of the lane control behavior. For instance, in personalized motion planning, the motion planning module 560 may determine that the motion of the vehicle needs to be gentle due to the observation that the passenger of the vehicle prefers smooth motion. Such a determination is part of the motion planning and may be to be sent to the lane planning module 570 so that the lane control behavior of the vehicle may be carried out in a way that ensures smooth motion, e.g., change lane as little as possible.
To ensure that the vehicle behavior is planned and controlled in a self-capability aware manner, the route planning module 550, the motion planning module 560, and the lane planning module 570 also access the self-aware capability model 490 and use it to determine the planning strategy in a manner that takes into account of what the vehicle is actually capable of in the current scenario.
The self-aware capability model 490 in any situation may include various parameters, each of which is associated with some factors that may impact the actual ability of the vehicle so that the vehicle planning (route, motion, or lane) has to consider. In the following disclosure, self-aware capability model and self-aware capability parameters will be used interchangeably.
There are other conditions external to the vehicle that may affect various planning activities. This includes the light or atmosphere related conditions as well as the surrounding of the vehicle. For instance, if the vehicle is positioned in such a way that there is a sun glare so that sensors may not work well, this will impact the planning decisions. If the vehicle is in an area with a heavy fog condition, such information is also important to the planning module. If there is a high level of precipitation, such information may also be taken into account by the planning modules. The surrounding traffic may also be important in terms of planning. For instance, extrinsic parameters may provide information related to nearby vehicles or objects so that the planning modules may consider such information in their respective planning. The extrinsic parameters may include information about such nearby vehicles/objects, e.g., the nearby vehicle is a big truck or a bicycle, which may also impact how the planning decision is made. In addition, events occur along the road the vehicle is on may also impact the planning. For instance, whether the vehicle is currently on a road that is in a school zone or whether there is a construction going on along the road the vehicle is currently on may also be important information to the planning modules for obvious reasons.
The extrinsic capability parameters may be acquired and updated continuously in time to support the planning modules to adapt their decisions based on external situations in real time. In some situations, the extrinsic capability parameters may also be predicted. For example, if the vehicle is driving on a road to the west in the afternoon, it may be predicted that there will be sun glare. Although such predicted extrinsic capability parameter may not be the real time information, it nevertheless will assist the planning module (e.g., the route planning module) to make an appropriate decision. For instance, if the intended destination for a vehicle is in the north west direction and there are roads available at the time to both the west and the north, knowing that there will be sun glare if heading to the west in late afternoon, the route planning module 550 may accordingly decide to presently take the road heading to the north first and later take a road to head to the west after sun is down to avoid sun glare (safer). Such predicted extrinsic capability parameters may be determined based on other information such as the current location of the vehicle and the intended destination of the vehicle.
With capability parameters (including both intrinsic and extrinsic), the vehicle becomes self-aware of both intrinsic and extrinsic capability related limitations, which may be crucial in terms of planning.
To facilitate the self-aware capability parameter generator 740 to generate extrinsic capability parameters, the locale context determining unit 730 may retrieve information stored in a map configuration 750 and a road context configuration 760 based on the current location 720 and the destination information 710. The locale context information related to the roads may include the surrounding or contextual information of the road the vehicle is currently on and/or the roads that the vehicle will be on subsequently. For example, the map configuration 750 may provide information about the roads from the current location to the intended destination, while the road context configuration 760 may provide some known or static information about the characteristics associated with roads, such as altitude, steepness, curviness of each road, etc. Such gathered static information about the roads may then be used by the self-aware capability parameter generator 740.
The road conditions may change over time. For example, roads may become icy or slippery due to changes in weather conditions. Such dynamically changing context information about the roads may be acquired separately by, e.g., the self-aware capability parameter generator 740 on a continuous basis and used in generating extrinsic capability parameters that are reflective of the real time situations. As will be discussed below in reference to
To generate intrinsic vehicle capability information, information related to the vehicle may be accessed from a vehicle information storage 750. The vehicle information storage 750 may store vehicle parameters configured when the vehicle was manufactured such as whether the vehicle is equipped with cruise control or certain types of sensors. The storage 750 may also subsequently update information related to the parameters intrinsic to the vehicle. Such subsequent update may be generated due to, e.g., vehicle maintenance or repair or even update observed in real time. In discussion below in reference to
In some embodiments of the operation, upon receiving the locale context information from the locale context determining unit 730, the locale context information processor 810 processes the received information and, e.g., extracts information related to the current route the vehicle is on and sends such information to the self-aware capability parameter updater 830. Such information related to the current route may include steepness or curviness of the route or other types of static information such as the altitude and orientation of the route. The situation parameter determiner 820 receives the current location 720 and, e.g., separates location and time information and sends the information to the self-aware capability parameter identifier 830 so that it may use that information to identify capability parameters specific to the location and the precise time.
With the information about the location of the vehicle and the current time, the self-aware capability parameter updater 830 may access intrinsic capability models 840 and/or extrinsic capability models 850 to retrieve capability related parameter values specific to the current location and time. In some embodiments, the intrinsic capability models 840 may be configured to specify types of parameters relevant to the intrinsic capabilities of the vehicle and the current values thereof. Similarly, the extrinsic capability models 850 may be configured to specify types of parameters that have an impact on the ability of the vehicle to operate and their current values.
In operation, in order to keep the values of the parameters current, the intrinsic and extrinsic capability models (840 and 850) may regularly trigger the updaters (860-a, . . . , 860-f) to gather real time information and update the values of the corresponding parameters based on such gathered real time information. For example, the intrinsic capability models 840 may be configured to have a mechanism to activate the vehicle capability parameter updater 860-a to gather updated information related to the intrinsic capabilities of the vehicle. Such a mechanism may specify different modes of triggering. For instance, it may be on a regular schedule, e.g., daily or hourly. It may also specify to be triggered by some external event such as a signal received from a maintenance shop or a sensor in the vehicle that senses that some functional state of a component in the vehicle has been changed. In this case, the vehicle capability parameter updater 860-a may accept real time vehicle information from the sensor(s) and update the values/states of the relevant capability parameter in the intrinsic capability models to reflect that real time status of the vehicle. For instance, if during the operation of the vehicle, the headlight or a break may become non-functional. Such information sensed in real time may be gathered by the vehicle capability parameter updater 860-a and used to update the information stored in the intrinsic capability parameter storage 840. Such updated information relates to the vehicle may then be used by the self-aware capability parameters generator 740 to generate intrinsic capability parameters.
Similarly, the extrinsic capability models 850 may be configured to specify the update mechanism(s) for updating different types of extrinsic capability parameters. The update mechanism may specify regularly scheduled update or update to be triggered by some events. Different types of extrinsic capability parameters may be configured to be updated based on different triggering mechanisms. For example, for weather related extrinsic capability parameters or extrinsic capability parameters that may be keyed on weather, e.g., visibility in the vicinity of the vehicle, the update may be made regularly, e.g., every few minutes. Similarly, traffic sensitive parameters, e.g., the actual permissible speed which is usually direct result of the traffic condition, may also be updated regularly. Different types of parameters, although all regularly updated, may have different update schedule, which may range from every few seconds to every few minutes or every few hours.
On the other hand, some extrinsic capability related parameters may be made upon the occurrence of some events. For instance, for an orientation sensitive parameter, e.g., whether sun glare exists, the update may be triggered when the vehicle is heading in certain directions. If the direction of the vehicle is heading changes from north to north-west at some afternoon time, this may trigger the orientation sensitive parameter updater 860-d to gather information related to sun glare and update the situation with regard to sun glare. In some situations, the update may indicate that there is no sub glare, e.g., when it is a cloudy day. In some situations, the update may indicate that there is sun glare. In either situation, such orientation sensitive information is then used to update the value of the corresponding extrinsic capability parameter stored in the extrinsic capability parameter storage 850. Similarly, update of time sensitive parameters, such as visibility of the vehicle due to time of the day, may be triggered based on detected location, time zone of the location, and the specific time of the day at the moment. In some embodiments, the update of some of the capability parameters may also be triggered by event related to the detected updates of other capability parameter values. For example, the update of road sensitive parameters such as slippery road condition may be triggered when the update for the weather condition indicates that it started to rain or snow.
In the illustrated embodiments, the vehicle capability parameter updater 860-a receives the static vehicle information from storage 750 and dynamic vehicle information update from real time vehicle information feed which may be from multiple sources. Examples of such sources include dealers, vehicle maintenance places, sensors on the vehicle reporting the status change of components, or other sources. The weather sensitive parameter updater 860-b may receive both dynamic weather update and the updates of other weather sensitive capability parameters, e.g., precipitation, visibility, fog, or any other parameters that relate to weather and have the potential to impact the operation of the vehicle. Weather related information may be from multiple data sources that feed real time data.
The traffic sensitive parameter updater 860-c may receive both dynamic traffic reports and other information relating to the traffic that may influence the operation of the vehicle. Examples include the extent of the traffic jam (which may be used to determine whether the route of the vehicle needs to be re-planned) or the time of the accident that had caused the traffic (to estimate how long the delay will continue in order to determine whether to re-do the route planning). Traffic or traffic related information may be received from one or more sources for real time data feed. The orientation sensitive parameter updater 860-d may be configured to gather information along the road in the direction of the vehicle. Such orientation sensitive information may include sun glare in certain directions (e.g., east or west) or any potential situations in the direction of the road the vehicle is on (e.g., landslide situation ahead of the road). Similarly, the road sensitive parameter updater 860-e may, once triggered, gather information about various roads or road conditions with respect to the location of the vehicle, from one or more real time information feed sources. Such information may be related to the roads (e.g., open, close, detoured, school zone, etc.) or conditions thereof (e.g., slippery, icy, flooded, construction, etc.). The time sensitive parameter updater 860-f may be configured to collect from data source(s) real time data that depend on time. For example, the visibility of the road may depend on the time of day at the zone the vehicle is in.
The collected real time data may then be used to update the intrinsic capability models 840 and/or the extrinsic capability models 850. Such updated data may be time stamped. The self-aware capability parameter updater 830 may then access both the intrinsic and extrinsic capability models 840 and 850 to determine relevant capability parameters and the updated values thereof. The retrieved intrinsic/extrinsic capability parameters may then be output so that they can be used by various planning modules as shown in
Such dynamically gathered self-aware capability parameters are to be used in various vehicle behavior planning operations, including route planning, motion planning, and lane related vehicle behavior planning. For example, in human driving, choosing a route to a destination is often done with consideration of factors captured by the self-aware capability parameters. For example, a human driver may choose a route to a desired destination based on, e.g., what the vehicle is equipped with or capable of (intrinsic capability parameters). If the vehicle is in such a condition that it cannot handle steep road well, then such road needs to be avoided. In addition, a human driver may also consider other factors such as weather of the day, conditions of the roads considered, events known or scheduled at certain time of day (extrinsic capability parameters). For instance, it one road points to the west and the sun will be setting at that time, perhaps there will be too much glare so that it is better to take another alternative road. For both safety and reliability, autonomous vehicles ought to also consider such intrinsic and extrinsic capabilities with respect to route choices during route planning.
Traditional approaches to route planning often adopt some cost function so that the cost of a route selected is minimized. For instance, conventional route planning considers, e.g., optimization of distance traveled, minimization of time required to arrive the destination, or minimize the fuel used to get to the destination. In some instances, conventional approaches may also consider traffic conditions in optimizing the cost, e.g., high traffic route may decrease the speed leading to increased time and fuel to get to the destination. Such optimization functions often assume that all vehicles can handle all routes in the same manner and all routes can be handled equally well. Such assumptions are often not true so that when autonomous vehicles apply such planning schemes, they often find unable to proceed or even become unsafe in some situations. The present teaching aims to achieve safe, realistic, and reliable route planning that is adaptive to the changing intrinsic and extrinsic capability related parameters.
As shown in
In this illustrated embodiment, the route planning module 550 comprises a route selection preference determiner 1030 and a global route planner 1020. The route selection preference determiner 1030 is to determine the preferences to be considered in selecting a route. The global route planner 1020 is to select an appropriate route based on a variety of information, including the self-aware capability parameters 150. In some embodiments, the route planning activities may be triggered based on the route planning trigger signal as shown. Upon being activated, the global route planner 1020 may gather various types of dynamic information relevant to the present route planning operation. For example, the global route planner 1020 may rely on information related to the source/current location and the destination desired. The planning is performed with respect to the source/current location and the destination. The destination information may be determined in different ways. For example, it may optionally be received from a driver/passenger via an interface unit 1010.
The global route planner 1020 may also take real time data 480 as input and plans a route accordingly. As discussed with respect to
The global route planner 1020 may also consider preference(s) to be applied in route planning. Such preferences may be specified by a driver/passenger via the user interface unit 1010 (which may be forwarded to the global route planner 1020) or may be obtained via other means (see disclosure below with reference to
To determine an appropriate route, in addition to knowing the selection preferences, the global route planner 1020 may also need to know additional information about the roads, such as what routes available from the current location of the vehicle to the intended destination. In addition, for each route available, the map/road configuration 1060 may also store characteristic information about each of the available roads/routes. Such characteristic information of the roads/routes may include, but not limited to, geometric characteristics such as nature of the roads/routes (highway or not), dimension of the roads/routes, steepness/curviness, condition of the roads/routes, etc. During planning, the global route planner 1020 may first determine the roads/routes available between the current location of the vehicle to the desired destination. To select an appropriate route to the destination, for such available roads/routes, their characteristic information may also be accessed by the global route planner 1020 so that selections may be made based on such characteristic information.
With the information about the available roads/routes available as well as the characteristic information about those available roads/routes, the global route planner 1020 may then select an appropriate route to the destination by matching the route selection preferences, determined by the route selection preference determiner 1030, with the characteristic information of the available roads/routes. Details about the global route planner 1020 are provided with reference to
As discussed previously, the global route planner 1020 selects a planned route based on dynamic information from different sources, including real-time data 480 and self-aware capability parameters 510. In addition to that, as the vehicle may be on move or the destination may change over time, the current location of the vehicle and the destination may also change in time, just like the real-time data 480 and the self-aware capability parameters 510. When such information changes, it may impact the global route planned. For example, when the current location changes, the real-time data associated with the current location may also change, e.g., from good weather associated with the previous spot to the raining condition associated with the current location. This may in turn lead to a change in terms of route selection preferences and ultimately, the route selected. Thus, the global route planner 1020 may interact with the route selection preference determiner 1030 in a bi-directional manner and dynamic manner. Whenever there is a change that may warrant a re-determination of route selection preferences, the global route planner 1020 may then activate the route selection preference determiner 1030 to modify or re-generate the preferences to be used by the global route planner 1020 to determine an appropriate route given the situation.
Illustratively, the optional mechanism to determine personalized preferences comprises a passenger driving data analyzer 1245, a preference personalization module 1250, and a passenger preference determiner 1240. In operation, the passenger driving data analyzer 1245 receives recorded human driving data 430 as input and analyzes or learns from such data to understand route preferences relevant to specific drivers/passengers. For example, from the recorded human driving data 430, it may be learned that a specific driver prefers to drive on local roads instead of highway or historically chose to use highways at nights even though it involved much longer distance. It may also learn preferences of all drivers associated with the vehicle. For instance, multiple people (husband, wife, and a child of a household) may be associated with the vehicle, i.e., anyone of these people may operate the vehicle. The passenger driving data analyzer 1245 may learn from the recorded human driving data 430 various types of information associated with the driving behavior of such drivers, which may enable the preference personalization module 1250, upon receiving such driving behavior information, to establish personal preferences of each of such individuals.
Upon receiving the information related to each individual driver from the passenger driving data analyzer 1245, the preference personalization module 1250 may then generate personalized preferences in terms of route choices. Such route related preferences may reflect not only route choices but also represent preferences of route choices in different situations such as specific time frames of a day, seasons, locations, etc. Such established preferences for each individual driver may then be stored in storage 1265. At the time of route planning, the passenger preference determiner 1240 receives the real-time data 480 and based on various types of information in the real-time data 480 (e.g., month/day/time, passenger information, locale weather, etc.), the passenger preference determiner 1240 may access, from the route selection preference storage 1265, relevant preferences that can be applied in current route planning. For example, if the real-time data indicate that the driver is a specific person and the time is currently 7:45 pm in January, etc., the passenger preference determiner 1240 may identify personalized route preferences in 1265 related to the current specific driver which are associated with the specific time frame and season of the year (e.g., a driver may prefer driving on highway in winter season). The personalized route selection preferences so identified may then be sent to the route selection engine 1230 so that personalized preferences of the driver/passenger at the time of the route planning can be considered in determining what route is to be selected.
As shown in
In selecting route appropriate for the current situation, the route selection engine 1230 may also receiving self-aware capability parameters 510. In the illustrated embodiment, the self-aware capability parameter analyzer 1205 separates extrinsic capability parameters and intrinsic capability parameters and sends the extrinsic capability parameters to the route selection engine 1230 so that extrinsic conditions associated with the current situation the vehicle is in can be considered in selecting a route. For example, the extrinsic capability parameters may indicate that there is on-going construction on Route 7, the route selection engine 1230 may consider that and avoid Route 7. However, if the destination is currently set for a school on Route 7 and the driver's habit is to pick up children from the school each day at the present time (e.g., 3:30 pm), the route selection engine 1230 may elect to choose Route 7, given all things considered.
Similarly, intrinsic capability parameters may also be considered in selecting an appropriate route. In this illustrated embodiment, the intrinsic capability parameters are fed to the intrinsic capability based filter generator 1210, which may create different filters 1215 based on the intrinsic capability parameters so that such filters may be utilized by the route selection engine to filter out routes that are not appropriate given the intrinsic capability parameters. For example, if the intrinsic capability parameters indicate that the vehicle has no snow tire, any routes that are steep and/or curvy may not be appropriate on a snowy day.
The route selection engine 1230 selects a route based on both the current location of the vehicle, tracked by a current location updater 1235, and a destination, tracked by a destination updater 1225. Depending on the situation, changed current location and destination may trigger the route selection engine 1230 to activate the route selection preference determiner 1030 to re-evaluate the preferences in route selection given the changed circumstance.
The route planning according to the present teaching allows various types of information, such as real-time data and self-aware capability parameters, to be taken into account in route planning so that the planned routes are adaptive with respect to the vehicle condition at the time (via intrinsic capability parameters), the dynamic environment the vehicle is in at the time (via real-time data as well as extrinsic capability parameters), the passenger characteristics determined based on, e.g., dynamically updated real-time data (see
Human drivers control their vehicle motion in a manner that is comfortable. In most situations, human drivers also pay attention to the feedback or reaction of passengers who ride with them in the vehicle and respond to the vehicle motion. For example, some human drivers may prefer start and stop the vehicle smoothly. Some human drivers who usually start and stop the vehicle fairly abruptly may adjust their driving when they observe that passengers sitting in their vehicle respond in a certain way. Such human behavior may play an important role in autonomous vehicles. It is commonly recognized that driving behavior changes from person to person and how such behavior is to be adjusted in the presence of others in the same vehicle may also differ from person to person.
Traditionally, autonomous vehicles may adopt planning models that are trained to capture the characteristics of human driving behavior of the general population. Such generalized models do not customize the planning approach based on individual driver/passenger preferences or intents. The present teaching aims to provide personalized motion planning based on knowledge of the driver/passenger as well as the dynamic observations of driver/passenger response to vehicle motions.
A sub-category model for motion planning may be, as compared with the generic models, directed to a sub-category of vehicles or a sub-category of drivers/passengers. For example, a sub-category model may be directed to sports cars and another sub-category model may be provided for vans. In addition, a sub-category model may be directed to teenager drivers and another sub-category model may be directed to senior citizens. Each sub-category model is tuned or specialized so that the motion planning for a matching sub-category can be performed more accurately. According to the present teaching, motion planning models may also include personalized models which may include individual models, each of which may specify preferences of each individual in terms of vehicle motions. For example, a passenger's individual preference model may specify that the passenger prefers smooth vehicle motion and another passenger's individual preference model may specify some different preferences. Such generic, sub-category and individual models for motion planning may be derived based on recorded human driving data so that the motion planned based on such models are more human-like.
With reference back to
The motion planned by the generic motion planner 1450 (based on generic motion planning models and/or sub-category motion planning models) may be further adjusted or adapted according to personalized preferences. In the illustrated embodiment, this is achieved by the passenger motion adapter 1460. There may be different ways to adapt the motion planned to meet personalized preferences. In some embodiments, personalized preferences may be accessed from individual passenger models 1430. If the identity of the passenger is known, the associated individual passenger model for the passenger may be retrieved from 1430 and the specified preferences in vehicle motion may be used to determine how to achieve personalized motion planning. For instance, an individual model for a particular passenger may indicate that the passenger prefers a smooth ride without taking risks.
Another way to achieve personalized motion planning is adaptively adjusting motion planning based on dynamically observed information. As discussed previously with reference to
According to the present teaching, in addition to personalized motion planning (e.g., not only with respect to sub-categories but also with respect to individuals), motion planning may also be adaptive to the current situation characterized by, e.g., self-aware capability parameters and real-time situations such as weather, road conditions, etc. The passenger motion adapter 1460 receives the extrinsic capability parameters from 1410 and plans motion accordingly. For example, if extrinsic capability parameters indicate that there is sun glare or foggy, motion may be planned accordingly (e.g., slow down).
The passenger observation analyzer 1420 is provided to determine the reaction or feedback of the passenger to the current vehicle motion to determine whether the vehicle motion needs to be adjusted. For example, if passenger reaction indicates that the passenger is not happy about the current vehicle motion, an adjustment may be made in motion planning accordingly. The passenger reaction is to be estimated based on different cues, including visual, acoustic, text, or contextual scenarios.
In some embodiments, the sensor activator 1500 activates the in-situ sensors 1510 to detect the passenger reaction. The in-situ sensors 1510 comprise a plurality of sensors including visual sensors, acoustic sensors, infrared sensors, . . . , or communication sensors and the like that enable the detection of any expression of the passenger. For instance, the visual sensors included in the in-situ sensors 1510 may comprise a plurality of spatially distributed (within the vehicle) camera devices that are capable of capturing, processing and fusing images of a scene from a variety of viewpoints into some form more useful individual images/videos. For example, the visual sensors may capture a gesture or facial expression of the passenger, which may be used to estimate the reaction of the passenger. The in-situ sensors may be selectively activated. For instance, at night, in order to observe accurately the passenger's reaction, visual sensor may not work well and in this situation, infrared sensors may be activated instead.
As depicted in
Upon the detection of the passenger, the sensor data may be continuously fed to the passenger feature detector 1540 to detect various passenger behavior features, which may include both visual and acoustic. For instance, certain body language may be detected that may reveal that the passenger is doing certain things, such as sleeping (napping), reading, yawning, or frequently checking his/her watch. Such detected passenger features may also include acoustic features. For instance, the passenger feature detector 1540 may detect that the passenger is saying “slow down.” Visual and acoustic cues may be simultaneously detected that reveal consistent reaction cues. For example, the passenger may constantly check the watch and say “faster!”
The passenger features may be detected based on visual and acoustic feature detection models 1550. Such models may guide the passenger feature detector 1540 in terms of what feature to detect and provide, for each feature to be detected, a corresponding model that can be used to detect the feature. Those models may be personalized in the sense that what is to be detected may depend on the passenger. For instance, if the passenger is known to be mute, there is no reason to detect acoustic features associated with the passenger. Those feature detection models may be adaptive so that once they are trained and deployed on the vehicle, they may be configured to receive scheduled or dynamic update so that the models are adaptive to the changing situations.
The detected passenger visual features are then sent to the visual-based reaction cue estimator 1580, which may then estimate the passenger's reaction cues based on such visual cues. For example, if it is detected that the passenger is checking on the watch, the visual based reaction estimator 1580 may the reaction cue may be that the passenger is not happy with the speed of the vehicle and becomes impatient. Such an estimated cue may also be derived based on, e.g., a personalized visual feature model in 1550, which may be used to determine whether such a behavior (checking watch) is indicative of certain reaction cue associated with this particular passenger (may or may not be depending on the person).
Similarly, the detected passenger acoustic features are sent to the acoustic based reaction cue estimator 1590, which may then estimate the passenger's reaction cue based on such acoustic features. For example, if it is detected that the passenger is snoring, the acoustic based reaction cue estimator 1590 may estimate that the passenger is comfortable with or at least not unhappy with the current vehicle motion. Such an estimated cue may also be derived based on, e.g., a personalized acoustic feature model in 1550, which may be used to determine whether such a behavior is indicative of certain reaction cue of this particular passenger.
To estimate the reaction of the passenger, the visual based and acoustic based reaction cue estimators 1580 and 1590 may be engaged in estimating the emotional state of the passenger. For example, from the body language observed from the passenger (e.g., restless or seems to be vomiting), it may indicate that the passenger feels uneasy which may be a cue of his/her reaction to the vehicle motion. In addition, the tone of the voice used when the passenger says “faster” or “slow down” may also be used to estimate a level of anxiety of the passenger which is a clue as to how unhappy the passenger is. Such estimated emotional state may be used in evaluating the severity of the reaction that the passenger exhibits in response to the current vehicle motion and may be used to guide whether and/or how to adjust the motion planning.
In addition to the observed physical features, other parameters may also be used to estimate whether the current vehicle motion is acceptable. For instance, the source of observation may be an input directly entered by the passenger via some communication interface (e.g., a touch screen display) within the vehicle. The passenger may input via the display interface in the vehicle that he/she wants the vehicle motion to be smoother. This may be detected by the passenger expression detector 1560 via different communication sensors, which could be textual or acoustic.
As discussed previously, the scenarios that the passenger is currently in may also influence how the motion should be planned. The passenger scenario detector 1570 is configured to detect any scenario parameters that may be relevant to motion planning. For instance, if it is known that each afternoon between 3:30 pm and 4:30 pm (time of day), the vehicle is used to pick up children from school (task in hand), this may place a restriction on motion planning. That is, the motion planned may need to be based on safety. Once detected, such a restriction may be configured to trump the estimated desire (of the passenger) to be faster in order to ensure safety of the children. Other scenario related factors may also be observed, e.g., the health and age of the passenger. If it is observed (from a passenger model 1535) that the passenger is an elderly and suffers from dementia, such scenario parameters may be used to void some detected desire of the passenger. For instance, if the current vehicle motion is already pretty fast and the passenger keeps demanding to be even faster, given the age and known health condition of the passenger, the motion planning module may use such information to make an appropriate motion planning decision.
The various passenger reaction cues, detected by the visual/acoustic based reaction cue estimators 1580 and 1590, the passenger expression detector 1560, and the passenger scenario detector 1570, are then send to the user reaction generator 1595, where the detected different parameters are selected and integrated to generate estimated user reaction and sent to the passenger motion adapter 1460 so that the motion planned by the generic motion planner 1450 may be adapted in accordance with the observed dynamic user reaction to the current vehicle motion.
Visual/acoustic features of the passenger are detected at 1650 and are used to estimate, at 1670 and 1680 respectively, the visual and acoustic reaction cues, which are then sent also to the passenger reaction generator 1595. Different types of information so collected (from 1640, 1660, 1670, and 1680) are then all used by the passenger reaction generator 1595 to generate, at 1690, the estimated user reaction.
Going back to
To personalize the motion planning, the generically planned motion may then be adapted based on personalized information, which may include both known personal preferences and dynamically observed passenger reaction to the current vehicle motion. To achieve that, know passenger preferences are identified, at 1750, based on the individual passenger models 1430. In addition, dynamic passenger reaction/feedback is estimated, at 1760, based on information gathered from different sources/sensors. The personal preferences, either already known or estimated dynamically, are then used to personalize the motion planned, e.g., by adapting, at 1770, the motion planned based on generic information. Such personalized planned motion is then output, at 1780, as the planned motion 530.
As discussed with respect to
Recorded human driving data 430 are utilized to train models so that the models can capture characteristics related to motion planning that are more human-like. To train the generic motion planning models 1440, the received recorded human driving data are sent to the model training engine 1810 and the trained models are saved as the generic motion planning models 1440. To obtain sub-category motion planning models 1480, the recorded human driving data 430 are classified by the sub-category training data segmenter 1820 into training data sets for the sub-categories and then fed to the model training engine 1810 for training. For each sub-category model, appropriate sub-category training data set is applied to derive the corresponding sub-category model and such trained sub-category models are then saved in 1480. Similarly, for obtaining individual passenger models 1430 for motion planning, recorded human driving data may be processed to generate different training sets by the individual training data extractor 1830, each for an individual, and used by the model training engine 1810 to derive individual passenger models that characterize the preferences of the corresponding individuals.
In addition to the individual preferences, the individual passenger models 1430 may also include models that characterize impact of vehicle motions on individual passengers observed from the reaction or feedback of passengers. The observed reaction/feedback may be positive or negative and can be used to influence how the motion should be planned in the future for passengers.
To obtain impact based models for individuals, the real-time data 480, which capture the passenger characteristics in terms of their behavioral, visual, acoustic cues as well as their conditions (including mental, physical and functional states during vehicle movement), may be segmented based on individuals and such segmented data may then be used to derive models that characterize how certain motions impact passengers. In some embodiments, the mechanism 1800 includes an observation classifier 1850 that segments the real-time data 480 according to individual passengers and fed such segmented training data sets to the independent impact model training engine 1840 to derive individual impact models. Such derived individual impact models are then stored as part of the individual passenger models 1430.
Referring back to
On the other hand, lane changing may involve behavior of the vehicle when it moves from one lane to an adjacent lane while the vehicle is moving. Different passengers may exhibit different lane changing behaviors. From safety considerations, there may be desirable lane changing behaviors for different situations. Lane planning in terms of lane changing is to plan the vehicle movement with respect to the lanes in a manner that is safe, natural, human-like, and personalized.
In addition to the speed by which the vehicle is to move to the next lane, the lane changing behavior may also differ in terms of how the vehicle moves into the next lane. Also as shown in
Different drivers/passengers may exhibit different lane planning (include both lane following and lane changing) behaviors and in some situations, the same driver/passenger may behave differently under different circumstances. For instance, if there is no one on the street, a driver may decide to cut into the next lane quickly in lane change. When the street is crowded, the same driver may be more careful and decide to take time to gradually ease into the next lane. The lane planning module 570 is configured to learn different human behaviors in different circumstances and use such learned knowledge/models to achieve lane planning in autonomous driving.
Smooth and predictable lane following and lane changing behavior is a key aspect of offering human-like driving experience in autonomous vehicles. It may be especially challenging when significant environment noise is present in camera images and/or videos captured during the vehicle operation. Traditional approaches rely on computer vision to detect lanes by detecting drivable area on the fly. Some uses end to end image raw pixels for vehicle control signal prediction. Such conventional approaches fail to utilize the available manual driving data collected so that they usually produce rigid planning and control and are susceptible to environment variances, while ultimately limit the capability to operate the vehicle satisfactorily.
The present teaching utilizes lane detection models and lane planning models for lane planning and control. Both models are trained based on large amount of training data, some labeled and some are as collected. For lane detection, lane detection models are obtained using training data with labeled lanes to derive supervised models for lane detection. Such supervised models are to be trained using a large set of training data covering a wide range of environmental conditions to ensure the representativeness and robustness of the trained models.
For lane planning, to achieve human-like lane planning behavior, large volume of human driving data are collected and used to train lane control models that, when used for lane planning, are to exhibit human-like behavior in maneuvering the vehicles. Although the lane detection models and the lane planning models are trained separately, in operation, the two sets of models are used in a cascade manner for inference in order to produce robust behavior in diverse types of environment or conditions with human-like operational behavior. In some embodiments, when human driving data are classified according to individual drivers, the present teaching can be configured to further personalize to create personalized human-like lane planning models. With such personalized human-like lane planning models, an autonomous driving vehicle may be operated during lane planning/control in an adaptive manner, depending on who is the passenger in the vehicle.
In some embodiments, the lane detection models 2120 may correspond to a generic model, capturing the characteristics of lane detection in different situations. In some embodiments, the lane detection model 2120 may include different models, each of which may be for providing a model to detect lanes in a specific distinct situation. For example, some model(s) may be for detecting lanes in normal road conditions, some may be for detecting lanes when the road is wet, some may be for detecting lanes when the road has glare or reflection, some may even be for estimating lanes when the roads are covered with, e.g., snow or other types of visual obstructing objects. The lane detection models may also provide separate models for different types of vehicle. For example, some vehicles have higher gravity so that cameras capturing the ground image in front of the vehicle may be installed at higher positions relative to the ground. In this case, the lane detection models for such vehicles may be different from the lane detection models for vehicles with cameras installed at a level closer to the ground level. Each type of model may be trained using appropriate labeled training data that are related to the corresponding scenario.
To achieve human-like lane planning behavior in autonomous driving, the driving lane planning model training engine 2140 takes recorded human driving data 430 as input and learns human-like behavior in terms of lane planning. As discussed above, such human driving data may be collected from a wide range of drivers/situations/conditions in order for the driving lane planning model training engine 2140 to learn and capture the characteristics of a wide range of human driving behavior in lane planning/control. In some embodiments, the driving lane planning model training engine 2140 may optionally take some supervised training data with labeled lanes as input, e.g., as seeds or some small set of data to drive the learning towards convergence more quickly.
Based on the recorded human driving data 430, the driving lane planning model training engine 2140 may learn and/or train models for both lane following and lane changing. In some embodiments, for each of lane following and lane changing, a generic model in 2150 for generic human behavior may be derived. In some embodiments, the lane planning model training engine 2140 may also learn and/or train multiple models for lane planning, each of which may be for different known situations, e.g., lane following or lane changing for specific subgroups of the general population, or for particular different driving environment scenarios (wet road, dark light, crowded road). Such models for subgroups of the general population may also be stored in 2150.
The human-like lane control models 2150 may also be personalized and stored in 2150. When multiple models are to be derived via training, lane human driving data that meet the condition associated with each of different model may be extracted and used to train the models. For example, lane planning (including lane following and lane changing) models for lane related behavior exhibited when driving on crowded roads may be learned based on human driving data related to lane driving behavior on crowded roads. The models for lane planning may also be personalized. To achieve personalization, the driving lane planning model training engine 2140 may derive a model for each individual passenger (e.g., with respect to each of lane following and lane changing) based on the passenger's past driving data. Optionally, information from a personal profile associated with the passenger may also be used during learning in order to obtain a model that is more accurately reflect the preferences of the passenger.
Such obtained different types of lane planning/control models may then be stored in the driving lane control model storage 2150. In some embodiments, different models for different situations may be organized and indexed for easy identification and quick access in real time during the operation of the vehicle. In some embodiments, the driving lane detection model training engine 2110 and the driving lane planning model training engine 2140 may reside remotely from the vehicle and the learning may be performed in a centralized manner, i.e., they may be operating based on training data from different sources and the learning and update may be activated regularly. The trained models may be sent to distributed vehicles. In some embodiments, personalized models for lane planning may be updated locally in each vehicle based on data acquired locally.
The training via both 2110 and 2140 engines may be achieved via any learning mechanism including artificial neural networks, deep leaning networks, etc. Depending on the types and number of models to be obtained, each training engine may comprise a plurality of sub training engines, each for a specific (set of) models for some specific purposes and each may be configured and implemented differently in order to deriving the most effective models. Each training engine (2110 and 2140) may also include, in addition to learning, pre-processing mechanisms (not shown) for process the training data prior to being used by learning mechanism to derive trained models. For example, it may include data segmentation mechanism that segment the received training data into separate sets, each may be used for training a specific model directed for a particular situation, e.g., the driving lane planning model training engine 2140 may be configured to derive a generic model for the general population, a personalized model for the driver/passenger of the vehicle, a model for lane planning in day light condition, a model for lane planning in night light condition, a model for lane planning in wet road condition, and a model for lane planning for snowy day condition. In this case, the pre-processing mechanism may then first group the received recorded human driving data 430 into different groups, each of which for one model planned so that the training engine may then use the appropriate training data group to learn the appropriate model. The models may be continuously updated when the new training data arrive. The update of the models may be performed by re-learning based on all data received (batch mode) or by incremental mode.
Once the models, include the lane detection models 2120 and the driving lane control models 2150, are generated, they are used to plan lane related behavior for an autonomous driving vehicle in a human-like manner and in some instances personalized. As discussed previously, in operation, the obtained driving lane detection models 2120 and the driving lane control models 2150 are applied in a cascade manner. In the illustrated embodiments, when the vehicle is on the road, sensor(s) installed in the vehicle take pictures/videos of the road the vehicle is currently driving on and send such sensor data to the driving lane detector 2130. In addition to the sensor data, the driving lane detector 2130 may also receive the self-aware capability parameters 510. Via the self-aware capability parameters, the driving lane detector 2130 may determine various types of information, e.g., road condition, the vehicle's capabilities, etc., in order to determine how it may proceed in a way that is appropriate. For example, if it is night time of the day, which may be indicated in the extrinsic capability parameters, the driving lane detector 2130 may proceed to invoke a lane detection model that is trained for detecting lanes in dark light situation to achieve reliable performance.
Using the appropriately invoked lane detection model(s), the driving lane detector 2130 estimates segments of the lanes from the sensor data and optionally the estimated position of the vehicle. Such estimated lane segments and the vehicle position are then sent to the driving lane planning unit 2160, where appropriate driving lane planning model(s) may then be applied in a cascade manner for planning the lane control behavior of the vehicle.
As discussed previously, lane planning includes both lane following and lane changing. In operation, lane planning is directed to either controlling the vehicle behavior in lane following or the vehicle behavior in lane changing. When the vehicle is in motion, the operation context may provide some indication as to whether lane following or lane changing planning is needed. For instance, if the vehicle needs to exit, it may need first to get into an exit lane from a current lane that does not lead to the exit. In this case, lane changing is implied so that the task involved in lane planning is for lane changing. In some embodiments, the passenger in the vehicle may also provide an explicit lane control decision to indicate lane changing, e.g., by turning on the turn signal. In some embodiments, an indication of lane changing may also be from the vehicle itself, e.g., the engine may experience some problem so that the autonomous driving system may send a lane control decision signal to the driving lane planning unit 2160, instructing to prepare for lane changing so that the vehicle can move to the emergency lane. In normal situations, the vehicle may assume a default mode of lane following in absence of any indication of entering into a lane changing mode.
To perform lane planning, the driving lane planning unit 2160 receives, from different sources, various types of information (e.g., detected lanes, estimated vehicle position, lane planning decision, and self-aware capability parameters 510) and proceeds to lane planning accordingly. For example, if the lane control decision signal indicates that the current task is for lane following, models for lane following are to be retrieved and used for planning. If the current task is for lane changing, then models for lane changing are to be used.
Similar to the driving lane detector 2130, the driving lane planning unit 2160 may invoke the generic lane planning model from 2150 for the planning. It may also invoke different lane planning models that are appropriate for the situation in hand in order to enhance the performance. As discussed earlier, the self-aware capability parameters 510 provide both intrinsic and extrinsic capability parameters, which may indicate the weather condition, road condition, etc. which can be used by the driving lane planning unit 2160 to invoke appropriate lane planning models for the planning. For example, if the current task is for lane following with a right turn coming up, personalized human-like models for the passenger in the event of a right turn from the current lane may be retrieved from 2150 and used to plan the vehicle behavior as to how to ease into a position in the current right lane and then make a right turn.
On the other hand, if the current task is for lane changing, the lane control decision indicates that it is to change to the lane left to the current one, and the self-aware capability parameters indicate heavy rain and flooded roads, then the driving lane planning unit 2160 may appropriately access lane planning models trained for planning lane changing behavior on very wet roads. In some embodiments, such tasks may also be carried out using generic lane changing models. Based on selected models for the tasks in hand, the driving lane planning unit 2160 generates the planned lane control, which may then be sent to the vehicle control module 450 (
The driving lane planning unit 2160 may also perform personalized lane planning. In some embodiments, the passenger currently present in the vehicle may be known, e.g., either via driver/passenger information sent to the driving lane planning unit 2160 or via detection of the passenger (now shown) from the sensor data. Upon receiving such information about the passenger, the driving lane planning unit 2160 may appropriately invoke lane control models suitable for the passenger. Such invoked customized models may be a model for a subgroup that the passenger belongs to or may be a model that is personalized for the passenger. Such customized models may then be used to control how the lane planning is performed in a personalized manner.
During operation, when a vehicle is in motion, the sensors on the vehicle acquire sensor data including imagery of the road ahead of the vehicle with lanes present. Such sensor data are received at 2250 and are used to detect, at 2260, lanes in front of the vehicle based on the lane detection models. The relative position of the vehicle may also be optionally estimated. Such detected lanes and optionally estimated vehicle position may then be sent to the driving lane planning unit 2160. At the driving lane planning unit 2160, various types of information received at 2270, which include lane control decision, detected lanes, and self-aware capability parameters. Such information is used to determine the lane planning models to be used so that the lane planning can be achieved, at 2280, based on appropriated selected lane planning models.
By learning from human driving data, the learned lane planning models capture the characteristics of human behavior in lane planning so that when such models are used in autonomous driving, the vehicle can be controlled in a human-like manner. In addition, by further personalizing lane planning models based on relevant driving data of the passengers/drivers, the lane planning behavior of the vehicle can be controlled in a manner that is familiar and comfortable for the passenger/driver in the vehicle.
With reference to
When the motion and lane control planned to achieve human-like behavior, the vehicle control module 450 aims at delivering the planned action. According to the present teaching, the vehicle control module 450 also aims at learning how to control the vehicle according to the knowledge in terms of how the vehicle behaves or responds to different control signals in different situations so that the vehicle can be controlled to achieve the desired effect, including the planned vehicle behavior. Traditional approaches apply machine learning based control and derive vehicle dynamics models from classical mechanics, which often fail to model a variety of situations that occurred in real world. As a consequence, it often leads to poor performance and in some situations, may cause dangerous consequences. Although some conventional approaches is designed to learn the vehicle dynamics models from historic data via, e.g., neural networks, are able to learn the vehicle dynamics models in common scenarios, in some situations, such systems have made predictions that have substantial and unpredicted errors, which in real life can be fatal.
The present teaching discloses an approach that enables both achieving accurate simulation and safety of the vehicle performance. Instead of directly learn the vehicle dynamics model from the historic data, classical mechanics model is used as backbone model and learn how to adjust the predicted result from the historic data. In addition, limitation to the adjustment to be made is specified as a way to prevent a prediction result that significantly deviates from the normal situations.
With the HLVC model 2330 created, when the human-like vehicle control unit 2340 receives information related to a target motion and the current vehicle state, it generates a human-like vehicle control signal based on the HLVC model 2330 with respect to the real time situation associated with the vehicle (characterized by the real time data 480). When additional recorded human driving data 430 are made available, the HLVC model 2330 may be dynamically updated or re-trained so that it captures the characteristics of human vehicle control behavior in a variety of situations. The dynamic update of the HLVC model 2330 may be triggered via a model update signal as shown in
In some embodiments, the HLVC model 2330 may also be personalized. This is illustrated in
Details on the human-like vehicle control unit 2340 is disclosed below with reference to
Data to be used for deriving the HLVC model 2330 may also include environment data that characterize the surrounding condition under which the vehicle control data yielded the corresponding vehicle state. The environment data may include various types of information, e.g., road condition, whether condition, vehicle type and condition. In some embodiments, the environment data may also include information about the passenger in the vehicle as well as characteristics of the passenger, e.g., gender, age, health situation, preferences, etc. All these different types of information from the human driving data may present some variables that may impact the passenger's vehicle control behavior. For instance, when the road is wet or slippery, human drivers may exhibit different vehicle control behavior in terms of break the vehicle (e.g., apply pressure on the brake more slowly) than that when the road is not slippery.
When the HLVC model 2330 is generated, it can be used by the human-like vehicle control signal generator 2420 to generate a vehicle control signal, when it receives a desired target motion, to yield human-like vehicle control behavior in achieving the desired target motion. To generate a human-like vehicle control signal, the vehicle control signal generator 2420 obtains real time data 480 comprising information about the surrounding of the vehicle at the time of the desired target motion and use such information in invoking the HLVC model 2330 to generate a human-like vehicle control signal. As illustrated in the example above, a target motion may be to accelerate, in 5 seconds, the vehicle to 40 miles per hour starting from the current velocity of 30 miles per hour. The real time data for that moment may indicate that the road the vehicle is on has a deep slope and the road is slippery because it is currently raining. Such real time data is relevant and may be provided as environment data to the HLVC model 2330. The human-like vehicle control signal generator 2420 may invoke the HLVC model 2330 with such parameters in order to obtain an inferred human-like vehicle control signal that enables the autonomous vehicle to achieve the desired target motion in a manner similar to human driving.
The information obtained by the human-like vehicle control signal generator 2420 may then be applied to the HLVC model 2330 to generate, at 2570, the human-like vehicle control signal in accordance with the HLVC model 2330. In the event of personalization, one or more specific HLVC sub-models appropriate for the situation may be invoked and used to generate personalized human-like vehicle control signal. During the operation, the human-like vehicle control unit 2340 may check, at 2540, whether an update triggering signal is present. If an update signal is received, determined at 2540, the human-like vehicle control model generator 2410 proceeds to step 2510 to gather training data and re-train or adaptively adjust the HLVC model 2330 based on the dynamically collected human driving data.
The vehicle state data 2620-2 may include information characterizing the state of the vehicle, including, e.g., position of the vehicle, velocity of the vehicle, roll/pitch/yaw of the vehicle, and steering angle of the vehicle, etc. The vehicle control data 2620-3 may provide information characterizing the control applied to the vehicle, such as brake applied with a certain force, steering by turning the steering wheel by a certain angle, or throttle.
According to the present teaching, rather than training the HLVC model 2330 to generate the vehicle control signal directly, the present teaching combines or fuses the traditional kinematic model based prediction approach with learning model, created by learning from human driving data, as to how to adjust a vehicle control signal predicted using the traditional kinematic model so that the adjustment yields human-like vehicle control behavior. Such an integrated approach enables not only more accurate vehicle control but also human-like feel as to control of the vehicle.
In learning the HLVC model 2330, the vehicle state data 2620-2 and vehicle control data 2620-3 are provided to the VKM vehicle control prediction engine 2630 to predict the motion achieved because of the control exercised. The VKM vehicle control prediction engine 2630 performs the prediction based on based on the vehicle kinematic model 2310, e.g., via traditional mechanical dynamics approach to generate VKM based prediction signal, as shown in
As shown, the vehicle control model learning engine 2640 may be triggered by the model update signal. When it is activated, the vehicle control model learning engine 2640 invokes the training data processing unit 2610 and the VKM vehicle control prediction engine 2630 to initiate the training process. In some embodiment, any subsequent training based on additional human driving data may be performed in a derivative manner or in a batch mode, i.e., re-train the HLVC model 2330.
In operation, upon receiving a target motion, the human-like vehicle control signal, the VKM vehicle control signal inference engine 2810 obtains the current state of the vehicle and generates a VKM based vehicle control signal based on the vehicle kinematic model 2310. As discussed herein, the use of the traditional approach to generate an inferred vehicle control signal based merely on the vehicle kinematic model 2310 aims at providing initially an inferred vehicle control signal based on purely on mechanical dynamics. To achieve human-like behavior in vehicle control to achieve the target motion, the inferred VKM based vehicle control signal is to be further used as an input to the HLVC model based fusion unit 2830, where the VKM based vehicle control signal is used as the initial inferred result to be fused with the HLVC based approach so that the VKM based vehicle control signal may be adjusted in accordance with the learned HLVC model 2330.
The HLVC model based fusion unit 2830 may activate, upon receiving the target motion, the context data determiner 2820 to obtain any information related to the surrounding of the vehicle. The context data determiner 2820 receives the real time data 480 and extracts relevant information such as environment data or passenger data, etc. and sends to the HLVC model based fusion unit 2830. Based on the target motion, the current vehicle state, context information surrounding the vehicle, and the VKM based vehicle control signal inferred using the traditional vehicle kinematic model 2310, the HLVC model based fusion unit 2830 accesses the HLVC model 2330 based on such input data to obtain a fused human-like vehicle control signal.
As discussed herein, the HLVC model 2330 may be created by learning the discrepancies between VKM model based predictions and the observed information from the recorded human driving data 430. As such, what the HLVC model 2330 captures and learns may correspond to adjustments to be made to the VKM based vehicle control signals to achieve human-like behavior. As discussed previously, as learning process may create overfitting situation, especially when the training data include outliers, to minimize the risks in vehicle control due to adjustment to the VKM based vehicle control signal, the human-like vehicle control signal generator 2420 may also optionally include preventative measures by limiting the adjustments to VKM vehicle control signals based on some fusion constraints 2840, as shown in
In some embodiments, information about the passenger in the vehicle may also be extracted from real time data 480 and can be used to access personalized HLVC sub-model related to the passenger, which may be a HLVC sub-model for a group that the passenger belongs or a completely personalized HLVC sub-model for the passenger). Using such a personalized HLVC sub-model may allow the human-like vehicle control signal generator 2420 to generate personalized human-like vehicle control signal so that the vehicle control carried out based on it can be not only human-like but also to the personal liking of the passenger.
To implement various modules, units, and their functionalities described in the present disclosure, computer hardware platforms may be used as the hardware platform(s) for one or more of the elements described herein. The hardware elements, operating systems and programming languages of such computers are conventional in nature, and it is presumed that those skilled in the art are adequately familiar therewith to adapt those technologies to the present teachings as described herein. A computer with user interface elements may be used to implement a personal computer (PC) or other type of work station or terminal device, although a computer may also act as a server if appropriately programmed. It is believed that those skilled in the art are familiar with the structure, programming and general operation of such computer equipment and as a result the drawings should be self-explanatory.
The computer 3100, for example, includes COM ports 3150 connected to and from a network connected thereto to facilitate data communications. The computer 3100 also includes a central processing unit (CPU) 3120, in the form of one or more processors, for executing program instructions. The exemplary computer platform includes an internal communication bus 3110, program storage and data storage of different forms, e.g., disk 3170, read only memory (ROM) 3130, or random access memory (RAM) 3140, for various data files to be processed and/or communicated by the computer, as well as possibly program instructions to be executed by the CPU. The computer 2600 also includes an I/O component 3160, supporting input/output flows between the computer and other components therein such as interface elements 3180 in different media forms. An exemplary type of interface element may correspond to different types of sensors 3180-a deployed on the autonomous driving vehicle. Another type of interface element may correspond to a display or a projection 3180-b for visual based communication. There may be additional components for other multi-modal interface channels such as acoustic device 3180-c for audio based communications and/or component 2680-d for signaling based on communication, e.g., signal that causes vibration on a vehicle component such as a car seat. The computer 3100 may also receive programming and data via network communications.
Hence, aspects of the methods of the present teachings, as outlined above, may be embodied in programming. Program aspects of the technology may be thought of as “products” or “articles of manufacture” typically in the form of executable code and/or associated data that is carried on or embodied in a type of machine readable medium. Tangible non-transitory “storage” type media include any or all of the memory or other storage for the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, disk drives and the like, which may provide storage at any time for the software programming.
All or portions of the software may at times be communicated through a network such as the Internet or various other telecommunication networks. Such communications, for example, may enable loading of the software from one computer or processor into another, for example, from a management server or host computer of a search engine operator or other enhanced ad server into the hardware platform(s) of a computing environment or other system implementing a computing environment or similar functionalities in connection with the present teachings. Thus, another type of media that may bear the software elements includes optical, electrical and electromagnetic waves, such as used across physical interfaces between local devices, through wired and optical landline networks and over various air-links. The physical elements that carry such waves, such as wired or wireless links, optical links or the like, also may be considered as media bearing the software. As used herein, unless restricted to tangible “storage” media, terms such as computer or machine “readable medium” refer to any medium that participates in providing instructions to a processor for execution.
Hence, a machine-readable medium may take many forms, including but not limited to, a tangible storage medium, a carrier wave medium or physical transmission medium. Non-volatile storage media include, for example, optical or magnetic disks, such as any of the storage devices in any computer(s) or the like, which may be used to implement the system or any of its components as shown in the drawings. Volatile storage media include dynamic memory, such as a main memory of such a computer platform. Tangible transmission media include coaxial cables; copper wire and fiber optics, including the wires that form a bus within a computer system. Carrier-wave transmission media may take the form of electric or electromagnetic signals, or acoustic or light waves such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media therefore include for example: a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any other optical medium, punch cards paper tape, any other physical storage medium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave transporting data or instructions, cables or links transporting such a carrier wave, or any other medium from which a computer may read programming code and/or data. Many of these forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to a physical processor for execution.
Those skilled in the art will recognize that the present teachings are amenable to a variety of modifications and/or enhancements. For example, although the implementation of various components described above may be embodied in a hardware device, it may also be implemented as a software only solution—e.g., an installation on an existing server. In addition, the present teachings as disclosed herein may be implemented as a firmware, firmware/software combination, firmware/hardware combination, or a hardware/firmware/software combination.
While the foregoing has described what are considered to constitute the present teachings and/or other examples, it is understood that various modifications may be made thereto and that the subject matter disclosed herein may be implemented in various forms and examples, and that the teachings may be applied in numerous applications, only some of which have been described herein. It is intended by the following claims to claim any and all applications, modifications and variations that fall within the true scope of the present teachings.
This application is a Continuation of U.S. patent application Ser. No. 15/845,294, filed Dec. 18, 2017 and titled “METHOD AND SYSTEM FOR HUMAN-LIKE DRIVING LANE PLANNING IN AUTONOMOUS DRIVING VEHICLES,” the content of which is incorporated by reference herein in its entirety, and this application is also related to the following U.S. patent applications: a U.S. patent application Ser. No. 15/845,173, filed on Dec. 18, 2017 and titled METHOD AND SYSTEM FOR SELF CAPABILITY AWARE ROUTE PLANNING IN AUTONOMOUS DRIVING VEHICLES, a U.S. patent application Ser. No. 15/845,337, filed on Dec. 18, 2017 and titled METHOD AND SYSTEM FOR PERSONALIZED MOTION PLANNING IN AUTONOMOUS DRIVING VEHICLES and a U.S. patent application Ser. No. 15/845,423, filed on Dec. 18, 2017 and titled METHOD AND SYSTEM FOR ENSEMBLE VEHICLE CONTROL PREDICTION IN AUTONOMOUS DRIVING VEHICLES, all of which are incorporated herein by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5184303 | Link | Feb 1993 | A |
| 5483446 | Momose et al. | Jan 1996 | A |
| 5517412 | Unoura | May 1996 | A |
| 5559491 | Stadler | Sep 1996 | A |
| 5801763 | Suzuki | Sep 1998 | A |
| 5896129 | Murphy | Apr 1999 | A |
| 6487501 | Jeon | Nov 2002 | B1 |
| 6577334 | Kawai et al. | Jun 2003 | B1 |
| 6748301 | Ryu | Jun 2004 | B1 |
| 6859728 | Sakamoto et al. | Feb 2005 | B2 |
| 6980098 | Shinada et al. | Dec 2005 | B2 |
| 7155376 | Yang et al. | Dec 2006 | B2 |
| 7265657 | Nishida et al. | Sep 2007 | B2 |
| 7418372 | Nishira et al. | Aug 2008 | B2 |
| 7797108 | Grimm | Sep 2010 | B2 |
| 7930096 | Kubota et al. | Apr 2011 | B2 |
| 8190363 | Tomita et al. | May 2012 | B2 |
| 8465621 | Vaders | Jun 2013 | B2 |
| 8634980 | Urmson et al. | Jan 2014 | B1 |
| 8744744 | Takagi | Jun 2014 | B2 |
| 8780195 | Rubin | Jul 2014 | B1 |
| 8849494 | Herbach et al. | Sep 2014 | B1 |
| 8862299 | Ricci | Oct 2014 | B2 |
| 8874301 | Rao et al. | Oct 2014 | B1 |
| 8965621 | Urmson | Feb 2015 | B1 |
| 9008890 | Herbach et al. | Apr 2015 | B1 |
| 9090261 | Kitagishi et al. | Jul 2015 | B2 |
| 9103688 | Pivonka | Aug 2015 | B2 |
| 9146127 | Bank et al. | Sep 2015 | B2 |
| 9221396 | Zhu | Dec 2015 | B1 |
| 9274525 | Ferguson | Mar 2016 | B1 |
| 9315191 | Morimoto | Apr 2016 | B2 |
| 9371099 | Lagassey | Jun 2016 | B2 |
| 9429943 | Wilson et al. | Aug 2016 | B2 |
| 9430882 | Ho | Aug 2016 | B2 |
| 9443153 | Gupta et al. | Sep 2016 | B1 |
| 9493130 | Penilla | Nov 2016 | B2 |
| 9582004 | Rothoff et al. | Feb 2017 | B2 |
| 9594373 | Solyom et al. | Mar 2017 | B2 |
| 9672734 | Ratnasingam | Jun 2017 | B1 |
| 9721472 | Jain et al. | Aug 2017 | B2 |
| 9760806 | Ning | Sep 2017 | B1 |
| 9776644 | Chun et al. | Oct 2017 | B2 |
| 9816827 | Slusar | Nov 2017 | B1 |
| 9902401 | Stein et al. | Feb 2018 | B2 |
| 9933781 | Bando et al. | Apr 2018 | B1 |
| 9970780 | Bai et al. | May 2018 | B2 |
| 9989964 | Berntorp et al. | Jun 2018 | B2 |
| 10011281 | Kang et al. | Jul 2018 | B1 |
| 10031523 | Ricci et al. | Jul 2018 | B2 |
| 10059343 | Hoare et al. | Aug 2018 | B2 |
| 10073965 | Jantz et al. | Sep 2018 | B2 |
| 10077056 | Fields et al. | Sep 2018 | B1 |
| 10197631 | Barfield, Jr. | Feb 2019 | B2 |
| 10229229 | Matsumura | Mar 2019 | B2 |
| 10254759 | Faust et al. | Apr 2019 | B1 |
| 10259458 | Yoo et al. | Apr 2019 | B2 |
| 10275664 | Mullen | Apr 2019 | B2 |
| 10324463 | Konrardy et al. | Jun 2019 | B1 |
| 10324464 | Hatano | Jun 2019 | B2 |
| 10406978 | Zheng et al. | Sep 2019 | B2 |
| 10467488 | Sicconi et al. | Nov 2019 | B2 |
| 10503988 | Cordell et al. | Dec 2019 | B2 |
| 10507839 | Altmannshofer et al. | Dec 2019 | B2 |
| 10563993 | Ho et al. | Feb 2020 | B1 |
| 10572717 | Zhu et al. | Feb 2020 | B1 |
| 10579070 | Konrardy et al. | Mar 2020 | B1 |
| 10599144 | Zheng et al. | Mar 2020 | B2 |
| 10671076 | Kobilarov | Jun 2020 | B1 |
| 10675985 | Matsuo | Jun 2020 | B2 |
| 10687031 | Imomoto et al. | Jun 2020 | B2 |
| 10692371 | Nix | Jun 2020 | B1 |
| 10699580 | Gross | Jun 2020 | B1 |
| 10705525 | Smolyanskiy et al. | Jul 2020 | B2 |
| 10710590 | Zheng et al. | Jul 2020 | B2 |
| 10710610 | Hiramatsu et al. | Jul 2020 | B2 |
| 10733673 | Slusar | Aug 2020 | B1 |
| 10752244 | Buburuzan et al. | Aug 2020 | B2 |
| 10769525 | Redding et al. | Sep 2020 | B2 |
| 10860023 | Di Cairano et al. | Dec 2020 | B2 |
| 10867455 | Segal et al. | Dec 2020 | B2 |
| 10936886 | Ganguli et al. | Mar 2021 | B2 |
| 10957064 | Ganguli et al. | Mar 2021 | B2 |
| 10960838 | Sobhany | Mar 2021 | B2 |
| 10994741 | Zhou | May 2021 | B2 |
| 11042155 | Zheng et al. | Jun 2021 | B2 |
| 11091172 | Mori et al. | Aug 2021 | B2 |
| 11119483 | Kadin | Sep 2021 | B2 |
| 11130497 | Zhou et al. | Sep 2021 | B2 |
| 11243532 | Levihn | Feb 2022 | B1 |
| 11260852 | Rahimi et al. | Mar 2022 | B2 |
| 11273836 | Zheng et al. | Mar 2022 | B2 |
| 11279362 | Kuwahara | Mar 2022 | B2 |
| 11299166 | Zheng et al. | Apr 2022 | B2 |
| 11328210 | Mondello et al. | May 2022 | B2 |
| 11373466 | Golov | Jun 2022 | B2 |
| 11378956 | Zhang et al. | Jul 2022 | B2 |
| 11392796 | Curewitz et al. | Jul 2022 | B2 |
| 11404075 | Lakhani | Aug 2022 | B1 |
| 11410475 | Golov | Aug 2022 | B2 |
| 11449048 | Harihara Subramanian | Sep 2022 | B2 |
| 11458974 | McNew | Oct 2022 | B2 |
| 11468285 | Tang et al. | Oct 2022 | B1 |
| 11507093 | Kang | Nov 2022 | B2 |
| 11584379 | Misu et al. | Feb 2023 | B2 |
| 11643092 | Doemling et al. | May 2023 | B2 |
| 11648935 | Sierra Gonzalez et al. | May 2023 | B2 |
| 11798407 | Wang et al. | Oct 2023 | B1 |
| 11874808 | Kondal | Jan 2024 | B1 |
| 11945440 | Censi et al. | Apr 2024 | B2 |
| 11945445 | Maleitzke | Apr 2024 | B1 |
| 11948082 | Yan et al. | Apr 2024 | B2 |
| 20020062207 | Faghri | May 2002 | A1 |
| 20020116156 | Remboski et al. | Aug 2002 | A1 |
| 20020129353 | Williams | Sep 2002 | A1 |
| 20020135618 | Maes et al. | Sep 2002 | A1 |
| 20020188404 | Jeon | Dec 2002 | A1 |
| 20030001732 | Furusho | Jan 2003 | A1 |
| 20030048000 | Harter | Mar 2003 | A1 |
| 20030060949 | Letang | Mar 2003 | A1 |
| 20030072471 | Otsuka et al. | Apr 2003 | A1 |
| 20030103650 | Otsuka et al. | Jun 2003 | A1 |
| 20040107030 | Nishira et al. | Jun 2004 | A1 |
| 20040122639 | Qiu | Jun 2004 | A1 |
| 20050080565 | Olney et al. | Apr 2005 | A1 |
| 20050134117 | Ito | Jun 2005 | A1 |
| 20050240328 | Shirato et al. | Oct 2005 | A1 |
| 20060025966 | Kanamaru | Feb 2006 | A1 |
| 20060089765 | Pack et al. | Apr 2006 | A1 |
| 20070010938 | Kubota et al. | Jan 2007 | A1 |
| 20070142995 | Wotlermann | Jun 2007 | A1 |
| 20070276599 | Ogawa | Nov 2007 | A1 |
| 20080084283 | Kalik | Apr 2008 | A1 |
| 20080186154 | Haug | Aug 2008 | A1 |
| 20080195280 | Deng et al. | Aug 2008 | A1 |
| 20090005929 | Nakao et al. | Jan 2009 | A1 |
| 20090040037 | Schraga | Feb 2009 | A1 |
| 20090216399 | Ishikawa | Aug 2009 | A1 |
| 20090234552 | Takeda et al. | Sep 2009 | A1 |
| 20100014714 | Zhang et al. | Jan 2010 | A1 |
| 20100030466 | Rogers et al. | Feb 2010 | A1 |
| 20100052948 | Vian | Mar 2010 | A1 |
| 20100131148 | Camhi | May 2010 | A1 |
| 20100209892 | Lin et al. | Aug 2010 | A1 |
| 20100211270 | Chin et al. | Aug 2010 | A1 |
| 20100250001 | Hodgkins et al. | Sep 2010 | A1 |
| 20110205045 | Pilutti | Aug 2011 | A1 |
| 20110231063 | Kim | Sep 2011 | A1 |
| 20110320163 | Markkula et al. | Dec 2011 | A1 |
| 20120070804 | Pang et al. | Mar 2012 | A1 |
| 20120083964 | Montemerlo et al. | Apr 2012 | A1 |
| 20120105613 | Weng | May 2012 | A1 |
| 20120191343 | Haleem | Jul 2012 | A1 |
| 20120221341 | Rodemer | Aug 2012 | A1 |
| 20120268260 | Miller et al. | Oct 2012 | A1 |
| 20120271500 | Tsimhoni et al. | Oct 2012 | A1 |
| 20120316730 | Zhang et al. | Dec 2012 | A1 |
| 20130009761 | Horseman | Jan 2013 | A1 |
| 20130179023 | Schmidt | Jul 2013 | A1 |
| 20130206495 | Westbrook | Aug 2013 | A1 |
| 20130231824 | Wilson et al. | Sep 2013 | A1 |
| 20130302756 | Takeuchi et al. | Nov 2013 | A1 |
| 20130332165 | Beckley | Dec 2013 | A1 |
| 20140005923 | Bank et al. | Jan 2014 | A1 |
| 20140074480 | Gratke | Mar 2014 | A1 |
| 20140195213 | Kozloski et al. | Jul 2014 | A1 |
| 20140223384 | Graumann | Aug 2014 | A1 |
| 20140309913 | Ricci et al. | Oct 2014 | A1 |
| 20150049016 | Sinha | Feb 2015 | A1 |
| 20150050922 | Ramalingam | Feb 2015 | A1 |
| 20150062168 | Ng-Thow-Hing | Mar 2015 | A1 |
| 20150088374 | Yopp | Mar 2015 | A1 |
| 20150104757 | Moncrief et al. | Apr 2015 | A1 |
| 20150145664 | You et al. | May 2015 | A1 |
| 20150149017 | Attard | May 2015 | A1 |
| 20150158486 | Healey | Jun 2015 | A1 |
| 20150161454 | Han | Jun 2015 | A1 |
| 20150166069 | Engelman et al. | Jun 2015 | A1 |
| 20150175172 | Truong | Jun 2015 | A1 |
| 20150241231 | Abramson | Aug 2015 | A1 |
| 20150246673 | Tseng et al. | Sep 2015 | A1 |
| 20150254008 | Tal et al. | Sep 2015 | A1 |
| 20150266455 | Wilson | Sep 2015 | A1 |
| 20150284008 | Tan | Oct 2015 | A1 |
| 20150284010 | Beardsley et al. | Oct 2015 | A1 |
| 20150336587 | Inoue et al. | Nov 2015 | A1 |
| 20150336588 | Ebner | Nov 2015 | A1 |
| 20160001781 | Fung et al. | Jan 2016 | A1 |
| 20160026180 | Tsimhoni | Jan 2016 | A1 |
| 20160026182 | Boroditsky et al. | Jan 2016 | A1 |
| 20160039356 | Talwar | Feb 2016 | A1 |
| 20160063858 | Schmudderich et al. | Mar 2016 | A1 |
| 20160068103 | McNew et al. | Mar 2016 | A1 |
| 20160103499 | Yamamoto | Apr 2016 | A1 |
| 20160148059 | Kawano et al. | May 2016 | A1 |
| 20160167653 | Malone et al. | Jun 2016 | A1 |
| 20160171320 | Nagata | Jun 2016 | A1 |
| 20160231743 | Bendewald et al. | Aug 2016 | A1 |
| 20160264131 | Chan | Sep 2016 | A1 |
| 20160307056 | Schiek | Oct 2016 | A1 |
| 20160327949 | Wilson et al. | Nov 2016 | A1 |
| 20160358477 | Ansari | Dec 2016 | A1 |
| 20160363935 | Shuster et al. | Dec 2016 | A1 |
| 20160364990 | Khaghani et al. | Dec 2016 | A1 |
| 20160378112 | Ljubuncic et al. | Dec 2016 | A1 |
| 20170008521 | Braunstein et al. | Jan 2017 | A1 |
| 20170010618 | Shashua et al. | Jan 2017 | A1 |
| 20170015318 | Scofield | Jan 2017 | A1 |
| 20170031361 | Olson | Feb 2017 | A1 |
| 20170052034 | Magazinik et al. | Feb 2017 | A1 |
| 20170057507 | Gordon et al. | Mar 2017 | A1 |
| 20170057516 | Gordon et al. | Mar 2017 | A1 |
| 20170088143 | Goldman-Shenhar et al. | Mar 2017 | A1 |
| 20170096164 | Sun et al. | Apr 2017 | A1 |
| 20170109644 | Nariyambut et al. | Apr 2017 | A1 |
| 20170113627 | Ding | Apr 2017 | A1 |
| 20170113801 | Brunaux | Apr 2017 | A1 |
| 20170120448 | Lee et al. | May 2017 | A1 |
| 20170123419 | Levinson | May 2017 | A1 |
| 20170123423 | Sako et al. | May 2017 | A1 |
| 20170136842 | Anderson et al. | May 2017 | A1 |
| 20170146362 | Bai et al. | May 2017 | A1 |
| 20170158225 | Brown | Jun 2017 | A1 |
| 20170168689 | Goldman-Shenhar et al. | Jun 2017 | A1 |
| 20170169208 | Jantz et al. | Jun 2017 | A1 |
| 20170176195 | Rajagopalan et al. | Jun 2017 | A1 |
| 20170192437 | Bier et al. | Jul 2017 | A1 |
| 20170200061 | Julian et al. | Jul 2017 | A1 |
| 20170210379 | Obata et al. | Jul 2017 | A1 |
| 20170217428 | Tan et al. | Aug 2017 | A1 |
| 20170217446 | Halder | Aug 2017 | A1 |
| 20170225677 | Yoshida et al. | Aug 2017 | A1 |
| 20170234689 | Gibson et al. | Aug 2017 | A1 |
| 20170240096 | Ross et al. | Aug 2017 | A1 |
| 20170241794 | Koo et al. | Aug 2017 | A1 |
| 20170262790 | Khasis | Sep 2017 | A1 |
| 20170267177 | Nariyambut Murali | Sep 2017 | A1 |
| 20170267256 | Minster et al. | Sep 2017 | A1 |
| 20170284823 | McNew et al. | Oct 2017 | A1 |
| 20170286785 | Schaffer | Oct 2017 | A1 |
| 20170297564 | Xi | Oct 2017 | A1 |
| 20170297586 | Li | Oct 2017 | A1 |
| 20170297588 | Doshi | Oct 2017 | A1 |
| 20170305434 | Ratnasingam | Oct 2017 | A1 |
| 20170316625 | Stefan et al. | Nov 2017 | A1 |
| 20170320500 | Yoo et al. | Nov 2017 | A1 |
| 20170329330 | Hatano | Nov 2017 | A1 |
| 20170349099 | Kunze | Dec 2017 | A1 |
| 20170357257 | Yang et al. | Dec 2017 | A1 |
| 20170364070 | Oba | Dec 2017 | A1 |
| 20170364083 | Yang et al. | Dec 2017 | A1 |
| 20170369052 | Nagy | Dec 2017 | A1 |
| 20170369072 | Huber | Dec 2017 | A1 |
| 20170370744 | Miyajima | Dec 2017 | A1 |
| 20180009445 | Nishi | Jan 2018 | A1 |
| 20180011488 | Nishi | Jan 2018 | A1 |
| 20180022350 | McNew | Jan 2018 | A1 |
| 20180032082 | Shalev-Shwartz et al. | Feb 2018 | A1 |
| 20180035606 | Burdoucci | Feb 2018 | A1 |
| 20180043901 | Kim | Feb 2018 | A1 |
| 20180052000 | Larner et al. | Feb 2018 | A1 |
| 20180052458 | Tsuji et al. | Feb 2018 | A1 |
| 20180058875 | Wan et al. | Mar 2018 | A1 |
| 20180067488 | Pollach et al. | Mar 2018 | A1 |
| 20180074493 | Prokhorov et al. | Mar 2018 | A1 |
| 20180074497 | Tsuji | Mar 2018 | A1 |
| 20180075309 | Sathyanarayana | Mar 2018 | A1 |
| 20180089563 | Redding | Mar 2018 | A1 |
| 20180093676 | Emura et al. | Apr 2018 | A1 |
| 20180105185 | Watanabe et al. | Apr 2018 | A1 |
| 20180105186 | Motomura et al. | Apr 2018 | A1 |
| 20180113461 | Potnis et al. | Apr 2018 | A1 |
| 20180120843 | Berntorp et al. | May 2018 | A1 |
| 20180130347 | Ricci et al. | May 2018 | A1 |
| 20180135998 | Paramasivam | May 2018 | A1 |
| 20180141562 | Signhal et al. | May 2018 | A1 |
| 20180141568 | Singhal et al. | May 2018 | A1 |
| 20180148036 | Gaither | May 2018 | A1 |
| 20180154899 | Tiwari | Jun 2018 | A1 |
| 20180157957 | Ambeck-Madsen et al. | Jun 2018 | A1 |
| 20180162409 | Altmannshofer et al. | Jun 2018 | A1 |
| 20180164879 | Moffat | Jun 2018 | A1 |
| 20180170392 | Yang et al. | Jun 2018 | A1 |
| 20180186372 | Shimizu et al. | Jul 2018 | A1 |
| 20180194280 | Shibata et al. | Jul 2018 | A1 |
| 20180194354 | Takeda | Jul 2018 | A1 |
| 20180197440 | Ramachandra et al. | Jul 2018 | A1 |
| 20180201273 | Xiao | Jul 2018 | A1 |
| 20180257682 | Brooks | Sep 2018 | A1 |
| 20180259956 | Kawamoto | Sep 2018 | A1 |
| 20180267558 | Tiwari et al. | Sep 2018 | A1 |
| 20180281787 | Shiota et al. | Oct 2018 | A1 |
| 20180281807 | Minegishi et al. | Oct 2018 | A1 |
| 20180281812 | Tochioka | Oct 2018 | A1 |
| 20180284766 | Minegishi et al. | Oct 2018 | A1 |
| 20180284767 | Minegishi et al. | Oct 2018 | A1 |
| 20180284774 | Kawamoto | Oct 2018 | A1 |
| 20180292824 | Kazemi et al. | Oct 2018 | A1 |
| 20180292830 | Kazemi et al. | Oct 2018 | A1 |
| 20180300964 | Lakshamanan | Oct 2018 | A1 |
| 20180307902 | Arai | Oct 2018 | A1 |
| 20180312168 | Li | Nov 2018 | A1 |
| 20180316625 | Xu et al. | Nov 2018 | A1 |
| 20180357409 | Jantz et al. | Dec 2018 | A1 |
| 20180362049 | Avireddi et al. | Dec 2018 | A1 |
| 20190012909 | Mintz | Jan 2019 | A1 |
| 20190022347 | Wan et al. | Jan 2019 | A1 |
| 20190035275 | Nishi | Jan 2019 | A1 |
| 20190047578 | Swan | Feb 2019 | A1 |
| 20190047584 | Donnelly | Feb 2019 | A1 |
| 20190049967 | Lim et al. | Feb 2019 | A1 |
| 20190049981 | Fischer | Feb 2019 | A1 |
| 20190051172 | Stenneth et al. | Feb 2019 | A1 |
| 20190064801 | Frazzoli | Feb 2019 | A1 |
| 20190064804 | Frazzoli | Feb 2019 | A1 |
| 20190102656 | Kwant et al. | Apr 2019 | A1 |
| 20190102689 | Lassoued et al. | Apr 2019 | A1 |
| 20190113929 | Mukadam | Apr 2019 | A1 |
| 20190120640 | Ho | Apr 2019 | A1 |
| 20190129422 | Nojoumian | May 2019 | A1 |
| 20190135434 | Zhang | May 2019 | A1 |
| 20190138024 | Liang et al. | May 2019 | A1 |
| 20190138691 | Hu et al. | May 2019 | A1 |
| 20190143992 | Sohn et al. | May 2019 | A1 |
| 20190147254 | Bai et al. | May 2019 | A1 |
| 20190147255 | Homayounfar et al. | May 2019 | A1 |
| 20190155291 | Heit et al. | May 2019 | A1 |
| 20190164007 | Liu et al. | May 2019 | A1 |
| 20190168760 | Ryne et al. | Jun 2019 | A1 |
| 20190180502 | Englard | Jun 2019 | A1 |
| 20190180527 | Segal et al. | Jun 2019 | A1 |
| 20190184875 | Gomez | Jun 2019 | A1 |
| 20190184878 | Milner | Jun 2019 | A1 |
| 20190185010 | Ganguli et al. | Jun 2019 | A1 |
| 20190185011 | Zheng et al. | Jun 2019 | A1 |
| 20190185012 | Zheng et al. | Jun 2019 | A1 |
| 20190185013 | Zhou et al. | Jun 2019 | A1 |
| 20190187700 | Zheng | Jun 2019 | A1 |
| 20190187705 | Ganguli et al. | Jun 2019 | A1 |
| 20190187706 | Zhou et al. | Jun 2019 | A1 |
| 20190187707 | Zheng | Jun 2019 | A1 |
| 20190187708 | Zheng et al. | Jun 2019 | A1 |
| 20190188467 | Armeni et al. | Jun 2019 | A1 |
| 20190196487 | Akiyama et al. | Jun 2019 | A1 |
| 20190212749 | Chen | Jul 2019 | A1 |
| 20190213429 | Sicconi et al. | Jul 2019 | A1 |
| 20190220028 | Anderson | Jul 2019 | A1 |
| 20190228571 | Atsmon | Jul 2019 | A1 |
| 20190235497 | Glebov et al. | Aug 2019 | A1 |
| 20190241198 | Mori | Aug 2019 | A1 |
| 20190243459 | Imaizumi | Aug 2019 | A1 |
| 20190258251 | Ditty et al. | Aug 2019 | A1 |
| 20190265712 | Satzoda | Aug 2019 | A1 |
| 20190265713 | Zhou et al. | Aug 2019 | A1 |
| 20190266418 | Xu et al. | Aug 2019 | A1 |
| 20190266489 | Hu | Aug 2019 | A1 |
| 20190291728 | Shalev-Shwartz | Sep 2019 | A1 |
| 20190291745 | Sikorski | Sep 2019 | A1 |
| 20190294167 | Kutila et al. | Sep 2019 | A1 |
| 20190299978 | Balakrishnan | Oct 2019 | A1 |
| 20190302768 | Zhang et al. | Oct 2019 | A1 |
| 20190311715 | Pfeffinger | Oct 2019 | A1 |
| 20190318267 | Zhang et al. | Oct 2019 | A1 |
| 20190318740 | Takiguchi | Oct 2019 | A1 |
| 20190322287 | Escrig-Monferrer et al. | Oct 2019 | A1 |
| 20190324553 | Liu | Oct 2019 | A1 |
| 20190329763 | Sierra Gonzalez et al. | Oct 2019 | A1 |
| 20190332109 | Kolouri et al. | Oct 2019 | A1 |
| 20190333381 | Shalev-Shwartz | Oct 2019 | A1 |
| 20190344797 | Palanisamy | Nov 2019 | A1 |
| 20190346844 | Chen et al. | Nov 2019 | A1 |
| 20190361439 | Zeng | Nov 2019 | A1 |
| 20190369637 | Shalev-Shwartz | Dec 2019 | A1 |
| 20190370580 | Aoi | Dec 2019 | A1 |
| 20200005060 | Martin et al. | Jan 2020 | A1 |
| 20200019165 | Levandowski et al. | Jan 2020 | A1 |
| 20200026362 | Kim | Jan 2020 | A1 |
| 20200031361 | Soliman | Jan 2020 | A1 |
| 20200031371 | Soliman | Jan 2020 | A1 |
| 20200033868 | Palanisamy | Jan 2020 | A1 |
| 20200033869 | Palanisamy | Jan 2020 | A1 |
| 20200057487 | Sicconi | Feb 2020 | A1 |
| 20200064839 | Oyama | Feb 2020 | A1 |
| 20200065711 | Clément | Feb 2020 | A1 |
| 20200075006 | Chen | Mar 2020 | A1 |
| 20200079524 | Escobar | Mar 2020 | A1 |
| 20200081442 | Kizumi | Mar 2020 | A1 |
| 20200089245 | Yadmellat | Mar 2020 | A1 |
| 20200090074 | Isele | Mar 2020 | A1 |
| 20200094815 | Tan et al. | Mar 2020 | A1 |
| 20200097754 | Tawari | Mar 2020 | A1 |
| 20200101974 | Ha et al. | Apr 2020 | A1 |
| 20200116499 | Jung et al. | Apr 2020 | A1 |
| 20200139973 | Palanisamy | May 2020 | A1 |
| 20200139989 | Xu | May 2020 | A1 |
| 20200150773 | Son | May 2020 | A1 |
| 20200160069 | Sathyanarayana et al. | May 2020 | A1 |
| 20200160168 | Yang et al. | May 2020 | A1 |
| 20200174490 | Ogale et al. | Jun 2020 | A1 |
| 20200192307 | Wee et al. | Jun 2020 | A1 |
| 20200207353 | Chen et al. | Jul 2020 | A1 |
| 20200210717 | Hou et al. | Jul 2020 | A1 |
| 20200225676 | Telpaz | Jul 2020 | A1 |
| 20200242421 | Sobhany et al. | Jul 2020 | A1 |
| 20200244430 | Karabinis | Jul 2020 | A1 |
| 20200255014 | Meroux | Aug 2020 | A1 |
| 20200264900 | Cheriton | Aug 2020 | A1 |
| 20200278685 | Jang et al. | Sep 2020 | A1 |
| 20200317449 | Baijens | Oct 2020 | A1 |
| 20200339123 | Ozay et al. | Oct 2020 | A1 |
| 20200377082 | Nassouri et al. | Dec 2020 | A1 |
| 20210004017 | Colgate | Jan 2021 | A1 |
| 20210009115 | Ohmura et al. | Jan 2021 | A1 |
| 20210009133 | McNew | Jan 2021 | A1 |
| 20210056863 | Stefanescu | Feb 2021 | A1 |
| 20210061294 | Doemling et al. | Mar 2021 | A1 |
| 20210064033 | Telpaz et al. | Mar 2021 | A1 |
| 20210078611 | Hayes | Mar 2021 | A1 |
| 20210080950 | Tran | Mar 2021 | A1 |
| 20210097315 | Carruthers | Apr 2021 | A1 |
| 20210107494 | Silver | Apr 2021 | A1 |
| 20210114619 | Mimura | Apr 2021 | A1 |
| 20210165409 | Berntorp et al. | Jun 2021 | A1 |
| 20210166325 | Shalev-Shwartz | Jun 2021 | A1 |
| 20210173402 | Chang et al. | Jun 2021 | A1 |
| 20210188316 | Marchetti-Bowick et al. | Jun 2021 | A1 |
| 20210237776 | Hashimoto et al. | Aug 2021 | A1 |
| 20210245770 | Zhou et al. | Aug 2021 | A1 |
| 20210253128 | Nister | Aug 2021 | A1 |
| 20210256846 | McErlean | Aug 2021 | A1 |
| 20210271988 | Bouton et al. | Sep 2021 | A1 |
| 20210323570 | Yasui | Oct 2021 | A1 |
| 20210364307 | Kracun et al. | Nov 2021 | A1 |
| 20210380139 | Taveira | Dec 2021 | A1 |
| 20210403038 | Horigome et al. | Dec 2021 | A1 |
| 20220074758 | Sameer | Mar 2022 | A1 |
| 20220101726 | Fields | Mar 2022 | A1 |
| 20220109705 | Verbeke | Apr 2022 | A1 |
| 20220185295 | Zheng et al. | Jun 2022 | A1 |
| 20220187837 | Tebbens et al. | Jun 2022 | A1 |
| 20220244061 | Mellinger | Aug 2022 | A1 |
| 20220269290 | Dadkhah Tehrani et al. | Aug 2022 | A1 |
| 20220297719 | Mittal | Sep 2022 | A1 |
| 20220315000 | Wray | Oct 2022 | A1 |
| 20220324449 | Shi | Oct 2022 | A1 |
| 20220350336 | Gyllenhammar et al. | Nov 2022 | A1 |
| 20220364870 | Wang | Nov 2022 | A1 |
| 20230055066 | Asadi | Feb 2023 | A1 |
| 20230110730 | Chen et al. | Apr 2023 | A1 |
| 20230114577 | Sameer | Apr 2023 | A1 |
| 20230142461 | Hoel et al. | May 2023 | A1 |
| 20230143946 | Konrardy et al. | May 2023 | A1 |
| 20230144209 | Cai et al. | May 2023 | A1 |
| 20230159025 | Tummala et al. | May 2023 | A1 |
| 20230192095 | Liu | Jun 2023 | A1 |
| 20230202490 | Marzorati | Jun 2023 | A1 |
| 20230219564 | Baumann | Jul 2023 | A1 |
| 20230278582 | Zhang | Sep 2023 | A1 |
| 20230282210 | Bond | Sep 2023 | A1 |
| 20230294514 | Mohanty | Sep 2023 | A1 |
| 20230322234 | Wang et al. | Oct 2023 | A1 |
| 20230347940 | Longo et al. | Nov 2023 | A1 |
| 20230351228 | Hazard et al. | Nov 2023 | A1 |
| 20230382395 | Makita et al. | Nov 2023 | A1 |
| 20240119682 | Rudman | Apr 2024 | A1 |
| 20240132060 | Newman et al. | Apr 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2017100444 | May 2017 | AU |
| 101011967 | Aug 2007 | CN |
| 101165509 | Apr 2008 | CN |
| 101596903 | Dec 2009 | CN |
| 103646298 | Mar 2014 | CN |
| 103985250 | Aug 2014 | CN |
| 104331953 | Feb 2015 | CN |
| 104890595 | Sep 2015 | CN |
| 104973071 | Oct 2015 | CN |
| 105593640 | May 2016 | CN |
| 105974920 | Sep 2016 | CN |
| 106197449 | Dec 2016 | CN |
| 106649983 | May 2017 | CN |
| 106767874 | May 2017 | CN |
| 106915354 | Jul 2017 | CN |
| 106960600 | Jul 2017 | CN |
| 106989752 | Jul 2017 | CN |
| 106990714 | Jul 2017 | CN |
| 107200020 | Sep 2017 | CN |
| 107207013 | Sep 2017 | CN |
| 107223101 | Sep 2017 | CN |
| 107340772 | Nov 2017 | CN |
| 10 2015 215 079 | Feb 2017 | DE |
| 10 2016 122 402 | May 2017 | DE |
| 2 369 299 | Sep 2011 | EP |
| 2 916 190 | Sep 2015 | EP |
| 2915718 | Sep 2015 | EP |
| 3272611 | Jul 2019 | EP |
| 2546565 | Jul 2017 | GB |
| 2007176396 | Jul 2007 | JP |
| 2008275575 | Nov 2008 | JP |
| 101795250 | Nov 2017 | KR |
| 2016012867 | Jan 2016 | WO |
| 2016109637 | Jul 2016 | WO |
| 2016170785 | Oct 2016 | WO |
| 2017029096 | Feb 2017 | WO |
| 2017062106 | Apr 2017 | WO |
| 2017189203 | Nov 2017 | WO |
| 2017219319 | Dec 2017 | WO |
| Entry |
|---|
| Chinese Office Action dated Dec. 15, 2022 for Chinese Application No. 201780097496.0, with English translation, 21 pages. |
| Chinese Office Action dated Dec. 30, 2022 for Chinese Application No. 201780097485.2, with English translation, 18 pages. |
| Chinese Office Action dated Dec. 30, 2022 for Chinese Application No. 201780097497.5 with English translation, 18 pages. |
| Chinese Office Action dated Jan. 4, 2023 for Chinese Application No. 201780097486.7 with English translation, 18 pages. |
| Tang, Lei, et al., “Review of Vehicular Mobility Models for Vehicular Ad Hoc Network”, Journal of Chang'an University (Natural Science), vol. 36, No. 5, Sep. 15, 2016, 12 pages. |
| Wang, Xiaoyuan, et al., “Study on the Integrated Cognitive Topological Structure of Driver in the Multi-Resource Information Fusion”, Communications Standardization, vol. 4, Issue No. 164, Apr. 30, 2007 (Year: 2007), 6 pages. |
| Zhou, Huizi, et al., “Dynamic Path Planning for Autonomous Driving with Avoidance of Obstacles”, Journal of Computer Application, vol. 37, No. 3, Mar. 10, 2017, pp. 883-888. |
| Zou, Shuilong et al., “Method and System for Road Condition Real-Time Recognition and Danger Judgment Based on Composite Sensor”, Mobile Communications, vol. 15, Aug. 15, 2017 (Year: 2017), 6 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058086. |
| International Search Report and Written Opinion mailed Mar. 29, 2018 for International Application No. PCT/IB2017/058086, 7 pages. |
| Extended European Search Report dated Jul. 2, 2021 for European Application No. 17935322.2, 11 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058493. |
| International Search Report and Written Opinion Apr. 13, 2018 for International Application No. PCT/IB2017/058493, 13 pages. |
| Extended European Search Report dated Oct. 4, 2021 for European Application No. 17935810.6, 12 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058084. |
| International Search Report and Written Opinion mailed Apr. 25, 2018 for International Application No. PCT/IB2017/058084, 8 pages. |
| Extended European Search Report mailed Jun. 25, 2021 for European Application No. 17935461.8, 6 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058489. |
| International Search Report and Written Opinion mailed Apr. 12, 2018 for International Application No. PCT/IB2017/058489, 7 pages. |
| Extended European Search Report mailed Jun. 28, 2021 for European Application No. 17935508.6, 6 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058085. |
| International Search Report and Written Opinion mailed Mar. 29, 2018 for International Application No. PCT/IB2017/058085, 7 pages. |
| Extended European Search Report dated Jul. 2, 2021 for European Application No. 17935411.3, 8 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058490. |
| International Search Report and Written Opinion mailed Apr. 6, 2018 for International Application No. PCT/IB2017/058490, 8 pages. |
| Extended European Search Report dated Jul. 2, 2021 for European Application No. 17935151.5, 6 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058087. |
| International Search Report and Written Opinion mailed Mar. 30, 2018 for International Application No. PCT/IB2017/058087, 7 pages. |
| Extended European Search Report dated Jun. 29, 2021 for European Application No. 17935271.1, 5 pages. |
| International Preliminary Report on Patentability mailed Jul. 2, 2020 for International Application No. PCT/IB2017/058491. |
| International Search Report and Written Opinion mailed Apr. 23, 2018 for International Application No. PCT/IB2017/058491, 6 pages. |
| First Office Action dated Mar. 16, 2022 for Chinese Application No. 201780097481.4, with English translation, 17 pages. |
| Extended European Search Report dated Jul. 1, 2021 for European Application No. 17935809.8, 5 pages. |
| European Office Action dated Sep. 16, 2022 for European Application No. 17935322.2, 12 pages. |
| Al-Shihabi, T. & Mourant, R. R., “A Framework for Modeling Human-like Driving Behaviors For Autonomous Vehicles in Driving Simulators,” Agents '01: Proceedings of the Fifth International Conference on Autonomous Agent, May 2001, pp. 286-291. |
| First Office Action dated Feb. 4, 2023 for Chinese Application No. 201780097474.4, 9 pages. |
| First Office Action dated Feb. 4, 2023 for Chinese Application No. 201780097495.6, 8 pages. |
| First Office Action dated Feb. 21, 2023 for Chinese Application No. 201780097506.0, 15 pages. |
| Notice of Allowance dated Nov. 29, 2023 for Chinese Application No. 201780097497.5, 6 pages. |
| Notice of Allowance dated Dec. 16, 2023 for Chinese Application No. 201780097486.7, 6 pages. |
| Notice of Allowance dated May 29, 2024 for Chinese Application No. 201780097495.6, 4 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220185296 A1 | Jun 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15845294 | Dec 2017 | US |
| Child | 17688750 | US |
