Speed ​​planning using speed planning criteria for idling of autonomous vehicles

Through the perception and planning system, the idle curve and speed criteria are generated and the speed planning is optimized, and the control complexity of autonomous driving vehicles in the idle state is solved, achieving a more accurate idle movement and a natural driving experience.

CN112947405BActive Publication Date: 2024-11-29BAIDU USA LLC
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
CN202011458213.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-10
Publication Date
2024-11-29
Estimated Expiration
2040-12-10

AI Technical Summary

Technical Problem

It is difficult to accurately control autonomous vehicles at idle speed, especially in gasoline-powered vehicles, which requires continuous pressing of the brakes, resulting in complex and unnatural operation of the control stage.

Method used

By sensing the driving environment based on multiple sensor data, an idle curve is generated, and speed criterion is generated according to the current speed, the cost function is optimized to perform speed planning, and a control command is generated to achieve the expected idle movement.

Benefits of technology

It realizes more precise idle movement of autonomous vehicles along the planned trajectory, imitates artificial driving behavior, and simplifies the idle autonomous driving process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112947405B_ABST
    Figure CN112947405B_ABST
Patent Text Reader

Abstract

The present application discloses speed planning using speed planning criteria for idling of an autonomously driven vehicle. In one embodiment, a driving environment is sensed based on sensor data obtained from various sensors, including determining a current speed of an ADV. In response to a request to drive at idle speed, a speed criterion is generated based on an idle speed curve and according to the current speed of the ADV. A speed planning operation is performed by optimizing a cost function based on the speed criterion to determine the speed of a trajectory point at different time points along a trajectory planned for driving the ADV. One or more control commands are then generated to control the ADV at a planned speed along the planned trajectory so that the ADV moves according to an expected idle speed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention generally relate to operating an autonomous vehicle. More particularly, embodiments of the present invention relate to speed planning for idling of an autonomously driven vehicle. Background Art

[0002] A vehicle operating in an autonomous mode (e.g., without human control) can relieve occupants, particularly the driver, of some driving-related responsibilities. When operating in an autonomous mode, the vehicle can navigate to various locations using onboard sensors, allowing the vehicle to travel with minimal human interaction or in some cases without any passengers.

[0003] During conventional manual driving, one can simply do nothing, i.e., drive the vehicle without any throttle or brake action. The vehicle will move with its idle speed. However, for autonomous driving, it is not easy for an autonomous vehicle (ADV) to plan autonomous driving at idle speed. Typical autonomous driving is divided into a planning phase and a control phase. The control phase will precisely follow the trajectory planned by the planning phase, which makes "releasing the gas and braking" unnatural and difficult to implement. In addition, driving at vehicle idle speed is very difficult (especially for gasoline-powered vehicles) because it requires constantly pressing the brakes and causes many troubles to the control phase operation. Summary of the invention

[0004] A first aspect of the present invention provides a computer-implemented method for operating an autonomous driving vehicle ADV. The method includes sensing the driving environment around the ADV based on sensor data obtained from a plurality of sensors, including determining the current speed of the ADV. The method also includes generating a speed criterion based on an idle curve and according to the current speed of the ADV in response to a request to drive at idle speed. The method also includes performing a speed planning operation by optimizing a cost function based on the speed criterion to determine the speed of a plurality of trajectory points along a trajectory planned for driving the ADV. The method also includes generating a plurality of control commands to control the ADV at a planned speed along the trajectory so that the ADV moves according to an expected idle speed.

[0005] A second aspect of the present invention provides a non-transitory machine-readable medium having instructions stored therein, which, when executed by a processor, causes the processor to perform the method provided by the first aspect of the present invention.

[0006] The third aspect of the present invention provides a data processing system, comprising a processor and a memory. The memory is coupled to the processor and stores instructions, and when the instructions are executed by the processor, the processor executes the method provided by the first aspect of the present invention.

[0007] By using the method of the present invention, the autonomous driving vehicle can be more accurately controlled to move along the planned trajectory according to the expected idle speed. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Embodiments of the invention are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

[0009] Figure 1 is a block diagram illustrating a networking system according to one embodiment.

[0010] Figure 2 is a block diagram illustrating an example of an autonomous vehicle according to one embodiment.

[0011] Figure 3A-3B is a block diagram illustrating an example of a perception and planning system for use with an autonomous vehicle, according to one embodiment.

[0012] Figure 4 is a diagram illustrating an example of a process performed by a planning and control system according to one embodiment.

[0013] Figure 5 is a diagram illustrating an example of path and speed planning using a point-to-lateral graph according to one embodiment.

[0014] Fig. 6A and Figure 6B is a diagram illustrating an example of path and speed planning using a measurement point-time graph according to one embodiment.

[0015] Figure 7 is a block diagram illustrating an example of an idle planning module according to one embodiment.

[0016] Figure 8 is a graph showing an example of an idle speed curve according to one embodiment.

[0017] Fig. 9 is a flow chart illustrating an example of a process for idle planning according to one embodiment. DETAILED DESCRIPTION

[0018] Various embodiments and aspects of the present invention will be described with reference to the details discussed below, and the accompanying drawings will illustrate various embodiments. The following description and the accompanying drawings are illustrations of the present disclosure and should not be construed as limiting the present invention. Many specific details are described to provide a comprehensive understanding of various embodiments of the present disclosure. However, in some cases, in order to provide a brief discussion of embodiments of the present disclosure, known or conventional details are not described.

[0019] References in the specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present disclosure. The phrase "in one embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment.

[0020] According to some embodiments, a collection of speed profiles is created, each speed profile corresponding to a particular type of vehicle. The speed profile contains data describing the idle driving behavior of the vehicle. Idle speed refers to the relative speed at which the vehicle moves without pressing the accelerator pedal or the brake pedal. For example, when the vehicle is started and the accelerator or brake pedal is not pressed, the vehicle will move and its speed will increase. The speed of the vehicle eventually reaches a relatively constant speed after a period of time. This relatively constant speed is called the idle speed for the vehicle. The speed profile can be created based on a large amount of driving statistics collected from a variety of vehicles.

[0021] The speed profile can then be uploaded to the ADV for real-time speed planning during autonomous driving. During autonomous driving, during speed planning, the speed profile can be used as a speed reference line, also known as a speed guideline, to determine the optimized speed for the vehicle. Since the speed guideline is generated based on a large number of driving statistics, the idle autonomous driving will closely mimic the driving behavior of a person during idle autonomous driving.

[0022] According to one embodiment, a driving environment is sensed based on sensor data obtained from various sensors, including determining a current speed of the ADV. In response to a request to drive at an idle speed, a speed criterion is generated based on an idle speed curve and according to the current speed of the ADV. A speed planning operation is performed by optimizing a cost function based on the speed criterion to determine the speed of a trajectory point at different time points along a trajectory planned for driving the ADV. One or more control commands are then generated to control the ADV at a planned speed along the planned trajectory so that the ADV moves according to the expected idle speed.

[0023] In one embodiment, an idle speed curve has been generated based on driving statistics collected from a large number of vehicles similar to the ADV while the vehicle is driving at an idle speed. The speed curve represents the speed change of the vehicle from zero to a relatively constant speed without applying a throttle command or a brake command. When generating a speed criterion, a portion of the speed curve from the current speed of the ADV to the target idle speed represented by the speed curve is extracted from the speed curve, wherein the extracted portion of the speed curve is used for a speed planning operation. During the speed planning operation, the extracted portion of the speed curve is used as a speed reference line to generate a speed cost using a speed cost function.

[0024] In one embodiment, an idle planning operation is performed in response to determining that the current speed of the ADV is below a predetermined speed threshold. The speed profile is one of many speed profiles generated based on driving statistics collected from a variety of vehicles. Each of the speed profiles is associated with one of the different types of vehicles.

[0025] Figure 1 is a block diagram showing an autonomous vehicle network configuration according to one embodiment of the present disclosure. Figure 1 , network configuration 100 includes an autonomous vehicle 101, which can be communicatively coupled to one or more servers 103-104 via a network 102. Although one autonomous vehicle is shown, multiple autonomous vehicles can be coupled to each other and / or to servers 103-104 via network 102. Network 102 can be any type of network, such as a local area network (LAN), a wide area network (WAN) such as the Internet, a cellular network, a satellite network, or a combination thereof, either wired or wireless. (One or more) servers 103-104 can be any type of server or server cluster, such as a web or cloud server, an application server, a back-end server, or a combination thereof. Servers 103-104 can be data analysis servers, content servers, traffic information servers, maps and points of interest (MPOI) servers, or location servers, etc.

[0026] An autonomous vehicle refers to a vehicle that can be configured to be in an autonomous mode, in which the vehicle navigates through an environment with little or no input from a driver. Such an autonomous vehicle may include a sensor system having one or more sensors configured to detect information about the environment in which the vehicle operates. The vehicle and its associated controller use the detected information to navigate through the environment. Autonomous vehicle 101 may operate in a manual mode, a fully autonomous mode, or a partially autonomous mode.

[0027] In one embodiment, autonomous vehicle 101 includes, but is not limited to, perception and planning system 110, vehicle control system 111, wireless communication system 112, user interface system 113, infotainment system 114, and sensor system 115. Autonomous vehicle 101 may also include certain common components included in ordinary vehicles, such as an engine, wheels, a steering wheel, a transmission, etc., which can be controlled by vehicle control system 111 and / or perception and planning system 110 using various communication signals and / or commands (e.g., acceleration signals or commands, deceleration signals or commands, steering signals or commands, braking signals or commands, etc.).

[0028] The components 110-115 may be communicatively coupled to each other via an interconnect, a bus, a network, or a combination thereof. For example, the components 110-115 may be communicatively coupled to each other via a controller area network (CAN) bus. The CAN bus is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other in applications without a host computer. It is a message-based protocol that was originally designed for multi-way electrical wiring within automobiles, but is also used in many other environments.

[0029] Reference now Figure 2 In one embodiment, the sensor system 115 includes, but is not limited to, one or more cameras 211, a global positioning system (GPS) unit 212, an inertial measurement unit (IMU) 213, a radar unit 214, and a light detection and range (LIDAR) unit 215. The GPS system 212 may include a transceiver operable to provide information about the location of the autonomous vehicle. The IMU unit 213 may sense the position and orientation changes of the autonomous vehicle based on inertial acceleration. The radar unit 214 may represent a system that uses radio signals to sense objects within the local environment of the autonomous vehicle. In some embodiments, in addition to sensing objects, the radar unit 214 may additionally sense the speed and / or heading of the object. The LIDAR unit 215 may use lasers to sense objects in the environment in which the autonomous vehicle is located. The LIDAR unit 215 may include one or more laser sources, a laser scanner, and one or more detectors, among other system components. The camera 211 may include one or more devices to capture images of the environment surrounding the autonomous vehicle. The camera 211 may be a static camera and / or a video camera. The camera may be mechanically movable, for example by mounting the camera on a rotating and / or tilting platform.

[0030] The sensor system 115 may also include other sensors, such as sonar sensors, infrared sensors, steering sensors, throttle sensors, brake sensors, and audio sensors (e.g., microphones). The audio sensor may be configured to capture sounds from the environment surrounding the autonomous vehicle. The steering sensor may be configured to sense the steering angle of the steering wheel, the wheels of the vehicle, or a combination thereof. The throttle sensor and the brake sensor sense the throttle position and the brake position of the vehicle, respectively. In some cases, the throttle sensor and the brake sensor may be integrated into an integrated throttle / brake sensor.

[0031] In one embodiment, the vehicle control system 111 includes, but is not limited to, a steering unit 201, a throttle unit 202 (also referred to as an acceleration unit), and a brake unit 203. The steering unit 201 is used to adjust the direction or forward direction of the vehicle. The throttle unit 202 is used to control the speed of the motor or engine, which in turn controls the speed and acceleration of the vehicle. The brake unit 203 decelerates the vehicle by providing friction to slow down the wheels or tires of the vehicle. Note that Figure 2 The components shown may be implemented in hardware, software or a combination thereof.

[0032] Return to reference Figure 1 , the wireless communication system 112 allows communication between the autonomous vehicle 101 and external systems, such as devices, sensors, other vehicles, etc. For example, the wireless communication system 112 can wirelessly communicate with one or more devices (such as servers 103-104 through the network 102) directly or via a communication network. The wireless communication system 112 can use any cellular communication network or wireless local area network (WLAN), such as using WiFi to communicate with another component or system. The wireless communication system 112 can communicate directly with devices (e.g., a passenger's mobile device, a display device within the vehicle 101, a speaker) using, for example, an infrared link, Bluetooth, etc. The user interface system 113 can be part of a peripheral device implemented within the vehicle 101, including, for example, a keyboard, a touch screen display device, a microphone, and a speaker, etc.

[0033] Some or all of the functions of autonomous vehicle 101 may be controlled or managed by perception and planning system 110, particularly when operating in an autonomous driving mode. Perception and planning system 110 includes the necessary hardware (e.g., processor(s), memory, storage devices) and software (e.g., operating system, planning and routing programs) to receive information from sensor system 115, control system 111, wireless communication system 112, and / or user interface system 113, process the received information, plan a route or path from an origin to a destination point, and then drive vehicle 101 based on the planning and control information. Alternatively, perception and planning system 110 may be integrated with vehicle control system 111.

[0034] For example, a user as a passenger may specify a starting location and a destination for a trip, for example, via a user interface. The perception and planning system 110 obtains trip-related data. For example, the perception and planning system 110 may obtain location and route information from an MPOI server, which may be part of the servers 103-104. The location server provides location services, and the MPOI server provides map services and POIs for certain locations. Alternatively, such location and MPOI information may be cached locally in a permanent storage device of the perception and planning system 110.

[0035] As the autonomous vehicle 101 moves along the route, the perception and planning system 110 may also obtain real-time traffic information from a traffic information system or server (TIS). Note that the servers 103-104 may be operated by a third-party entity. Alternatively, the functionality of the servers 103-104 may be integrated with the perception and planning system 110. Based on the real-time traffic information, MPOI information, and location information, as well as real-time local environmental data (e.g., obstacles, objects, nearby vehicles) detected or sensed by the sensor system 115, the perception and planning system 110 may plan an optimal route, and drive the vehicle 101 according to the planned route, for example via the control system 111, to safely and efficiently reach a designated destination.

[0036] The server 103 may be a data analysis system for performing data analysis services for various clients. In one embodiment, the data analysis system 103 includes a data collector 121 and a machine learning engine 122. The data collector 121 collects driving statistics 123 from various vehicles (autonomous vehicles or conventional vehicles driven by human drivers). The driving statistics 123 include information indicating driving commands issued (e.g., throttle, brake, steering commands) and responses of the vehicle captured by the vehicle's sensors at different points in time (e.g., speed, acceleration, deceleration, direction). The driving statistics 123 may also include information describing the driving environment at different points in time, such as routes (including starting and destination locations), MPOI, road conditions, weather conditions, etc.

[0037] Based on the driving statistics 123, the machine learning engine 122 generates or trains a set of rules, algorithms, and / or predictive models 124 for various purposes. In one embodiment, the algorithms 124 may include speed profiles associated with various types of vehicles that represent the idle behavior of the vehicle. The algorithms 124 may then be uploaded to the ADV to be used in real time during autonomous driving.

[0038] Figure 3A and 3B is a block diagram illustrating an example of a perception and planning system for use with an autonomous vehicle according to one embodiment. System 300 may be implemented as Figure 1 Portions of autonomous vehicle 101 include, but are not limited to, perception and planning system 110, control system 111, and sensor system 115. Figure 3A-3B The perception and planning system 110 includes but is not limited to a positioning module 301 , a perception module 302 , a prediction module 303 , a decision module 304 , a planning module 305 , a control module 306 and a routing module 307 .

[0039] Some or all of the modules 301-307 may be implemented in software, hardware, or a combination thereof. For example, these modules may be installed in permanent storage device 352, loaded into memory 351, and executed by one or more processors (not shown). Note that some or all of these modules may be communicatively coupled to Figure 2 Some or all modules of the vehicle control system 111 or Figure 2 Some or all modules of the vehicle control system 111 are integrated. Some of the modules 301-308 can be integrated together as integrated modules.

[0040] The positioning module 301 determines the current location of the autonomous vehicle 300 (e.g., using the GPS unit 212) and manages any data related to the user's trip or route. The positioning module 301 (also known as the map and route module) manages any data related to the user's trip or route. The user can log in and specify the starting location and destination of the trip, for example, via a user interface. The positioning module 301 communicates with other components of the autonomous vehicle 300, such as map and route information 311, to obtain data related to the trip. For example, the positioning module 301 can obtain location and route information from a location server and a map and POI (MPOI) server. The location server provides location services, and the MPOI server provides map services and POIs of certain locations, which can be cached as part of the map and route information 311. When the autonomous vehicle 300 moves along the route, the positioning module 301 can also obtain real-time traffic information from a traffic information system or server.

[0041] Based on the sensor data provided by the sensor system 115 and the positioning information obtained by the positioning module 301, the perception of the surrounding environment is determined by the perception module 302. The perception information can represent the situation around the vehicle that the driver is driving as perceived by an ordinary driver. The perception can include lane configuration, traffic light signals, relative positions of another vehicle, pedestrians, buildings, crosswalks or other traffic-related signs (e.g., stop signs, give way signs), etc., such as in the form of objects. The lane configuration includes information describing one or more lanes, such as, for example, the shape of the lane (e.g., straight or curved), the width of the lane, the number of lanes in the road, one-way or two-way lanes, merging or splitting lanes, exit lanes, etc.

[0042] The perception module 302 may include a computer vision system or functionality of a computer vision system to process and analyze images captured by one or more cameras in order to identify objects and / or features in the environment of the autonomous vehicle. Objects may include traffic signals, roadway boundaries, other vehicles, pedestrians, and / or obstacles, etc. The computer vision system may use object recognition algorithms, video tracking, and other computer vision techniques. In some embodiments, the computer vision system may map the environment, track objects, and estimate the speed of objects, etc. The perception module 302 may also detect objects based on other sensor data provided by other sensors such as radar and / or LIDAR.

[0043] For each object, the prediction module 303 predicts how the object will behave in the environment. The prediction is performed based on the perception data of the driving environment at the time point according to a set of map / route information 311 and traffic rules 312. For example, if the object is a vehicle in the opposite direction and the current driving environment includes an intersection, the prediction module 303 will predict whether the vehicle will likely move straight ahead or turn. If the perception data indicates that there is no traffic light at the intersection, the prediction module 303 can predict that the vehicle may have to be completely stopped before entering the intersection. If the perception data indicates that the vehicle is currently in a lane that can only turn left or a lane that can only turn right, the prediction module 303 can predict that the vehicle will be more likely to make a left turn or a right turn, respectively.

[0044] For each object, the decision module 304 makes a decision about how to handle the object. For example, for a particular object (e.g., another vehicle in an intersecting path) and metadata describing the object (e.g., speed, direction, turn angle), the decision module 304 determines how to encounter the object (e.g., pass, yield, stop, pass). The decision module 304 can make these decisions based on a set of rules (such as traffic rules or driving rules 312), which can be stored in the persistent storage device 352.

[0045] The routing module 307 is configured to provide one or more routes or paths from the starting point to the destination point. For a given trip from the starting position to the destination position, for example, received from a user, the routing module 307 obtains the route and map information 311 and determines all possible routes or paths from the starting position to the destination position. The routing module 307 can generate a reference line in the form of a topographic map for each route determined by it from the starting position to the destination position. The reference line refers to an ideal route or path without any interference from other factors such as other vehicles, obstacles or traffic conditions. That is, if there are no other vehicles, pedestrians or obstacles on the road, the ADV should follow the reference line accurately or closely. Then, the topographic map is provided to the decision module 304 and / or the planning module 305. The decision module 304 and / or the planning module 305 check all possible routes to select and modify one of the optimal routes according to other data provided by other modules (such as traffic conditions from the positioning module 301, the driving environment perceived by the perception module 302, and the traffic conditions predicted by the prediction module 303). Depending on the particular driving circumstances at a point in time, the actual path or route used to control the ADV may be close to or different than the reference line provided by the routing module 307 .

[0046] Based on the decision for each object perceived, the planning module 305 plans a path or route for the autonomous vehicle and driving parameters (e.g., distance, speed, and / or turning angle) using the reference line provided by the routing module 307 as a basis. That is, for a given object, the decision module 304 decides what to do with the object, and the planning module 305 determines how to do it. For example, for a given object, the decision module 304 may decide to pass through the object, and the planning module 305 may determine whether to pass on the left or right side of the object. Planning and control data are generated by the planning module 305, and the planning and control data include information describing how the vehicle 300 will move in the next movement cycle (e.g., the next route / path segment). For example, the planning and control data may indicate that the vehicle 300 moves at a speed of 30 miles per hour (mph) for 10 meters and then changes to the right lane at a speed of 25mph.

[0047] Based on the planning and control data, the control module 306 controls and drives the autonomous vehicle by sending appropriate commands or signals to the vehicle control system 111 according to the route or path defined by the planning and control data. The planning and control data includes sufficient information to drive the vehicle from a first point on the route or path to a second point using appropriate vehicle settings or driving parameters (e.g., throttle, brake, steering commands) at different points in time along the route or path.

[0048] In one embodiment, the planning phase is performed in multiple planning cycles (also referred to as driving cycles, such as in each time interval of 100 milliseconds (ms)). For each of the planning cycles or driving cycles, one or more control commands will be issued based on the planning and control data. That is, for every 100ms, the planning module 305 plans the next route segment or path segment, for example, including the target location and the time required for the ADV to reach the target location. Alternatively, the planning module 305 can also specify a specific speed, direction and / or steering angle, etc. In one embodiment, the planning module 305 plans the route segment or path segment for the next predetermined time period (such as 5 seconds). For each planning cycle, the planning module 305 plans the target location for the current cycle (e.g., the next 5 seconds) based on the target location planned in the previous cycle. The control module 306 then generates one or more control commands (e.g., throttle, brake, steering control commands) based on the planning and control data of the current cycle.

[0049] Note that decision module 304 and planning module 305 can be integrated into an integrated module. Decision module 304 / planning module 305 may include a navigation system or the functionality of a navigation system to determine a driving path for an autonomous vehicle. For example, the navigation system may determine a series of speeds and directions of travel to affect the movement of the autonomous vehicle along a path that substantially avoids perceived obstacles while generally advancing the autonomous vehicle along a roadway-based path to a final destination. The destination may be set based on user input via user interface system 113. The navigation system may dynamically update the driving path while the autonomous vehicle is operating. The navigation system may incorporate data from a GPS system and one or more maps to determine a driving path for the autonomous vehicle.

[0050] Figure 4 is a block diagram illustrating an example of a decision and planning system according to one embodiment. System 400 may be implemented as Figure 3A-3B The autonomous driving system 300 includes a portion of the autonomous driving system 300, such as, for example, a planning module 305 and / or a control module 306, to perform path planning and speed planning operations. Figure 4 , the decision and planning system 400 (also referred to as a planning and control or PnC system or module) includes a routing module 307, positioning / sensing data 401, a path decision module 403, a speed decision module 405, a path planning module 407, a speed planning module 409, an aggregator 411 and a trajectory calculator 413, among others.

[0051] The path decision module 403 and the speed decision module 405 can be implemented as part of the decision module 304. In one embodiment, the path decision module 403 may include a path state machine, one or more path traffic rules, and a station-lateral map generator. The path decision module 403 can use dynamic programming to generate a rough path curve as an initial constraint for the path / speed planning modules 407 and 409.

[0052] In one embodiment, the path state machine includes at least three states: cruising state, lane changing state and / or idle state. The path state machine provides previous planning results and important information, such as whether the ADV is cruising or changing lanes. The path traffic rules can be Figure 3A As part of the driving / traffic rules 312 of the ADV, the path traffic rules include traffic rules that can affect the results of the path decision module. For example, the path traffic rules may include traffic information, such as construction traffic signs near the ADV, and lanes with such construction signs may be avoided. Based on the state, traffic rules, reference lines provided by the route selection module 307, and obstacles perceived by the perception module 302 of the ADV, the path decision module 403 can decide how to deal with the perceived obstacles (i.e., ignore, exceed, give way, stop, pass) as part of the rough path curve.

[0053] For example, in one embodiment, a rough path curve is generated by a cost function consisting of costs based on the curvature of the path and the distance from the reference line and / or reference point to the obstacle. Points on the reference line are selected and moved to the left or right of the reference line as candidate moves representing path candidates. Each of the candidate moves has an associated cost. Dynamic programming can be used to solve the associated costs of the candidate moves for one or more points on the reference line to sequentially obtain the optimal cost one point at a time.

[0054] In one embodiment, a point-to-lateral (SL) map generator (not shown) generates a SL map as part of the rough path curve. The SL map is a two-dimensional geometric map (similar to an xy coordinate plane) that includes obstacle information perceived by the ADV. Based on the SL map, the path decision module 403 can arrange an ADV path that follows the obstacle decision. Dynamic programming (also known as dynamic optimization) is a mathematical optimization method that decomposes the problem to be solved into a series of value functions, solves each of these value functions only once, and stores their solutions. The next time the same value function appears, simply look up the previously calculated solution, saving computing time, instead of recalculating its solution.

[0055] The speed decision module 405 or speed decision module includes a speed state machine, speed traffic rules, and a station-time graph generator (not shown). The speed decision process 405 or speed decision module can use dynamic programming to generate a rough speed profile as an initial constraint for the path / speed planning modules 407 and 409. In one embodiment, the speed state machine includes at least two states: an acceleration state and / or a deceleration state. The speed traffic rules can be Figure 3A As part of the driving / traffic rules 312 of the speed state machine, the speed traffic rules include traffic rules that can affect the results of the speed decision module. For example, the speed traffic rules may include traffic information such as red / green traffic lights, another vehicle in a crossing route, etc. Based on the state of the speed state machine, the speed traffic rules, the rough path curve / SL map generated by the decision module 403, and the perceived obstacles, the speed decision module 405 can generate a rough speed curve to control when to accelerate and / or decelerate the ADV. The SL map generator can generate a measurement point-time (ST) map as part of the rough speed curve.

[0056] In one embodiment, the path planning module 407 includes one or more SL maps, geometric smoothers, and path cost modules (not shown). The SL map may include a point-to-point map generated by the SL map generator of the path decision module 403. The path planning module 407 can use a rough path curve (e.g., a point-to-point map) as an initial constraint to recalculate the optimal reference line using quadratic programming. Quadratic programming (QP) involves minimizing or maximizing an objective function (e.g., a quadratic function with several variables) subject to bounds, linear equality, and inequality constraints.

[0057] One difference between dynamic programming and quadratic programming is that quadratic programming optimizes all candidate moves for all points on a reference line at once. A geometric smoother may apply a smoothing algorithm (such as B-splines or regression) to the output point-to-point traverse map. The path cost module may recalculate the reference line using a path cost function to optimize the total cost for candidate moves of the reference points, for example using a QP optimization performed by a QP module (not shown). For example, in one embodiment, a total path cost function may be defined as follows:

[0058] path cost = ∑ points (heading) 2 +∑ points (curvature) 2 +∑ points (distance) 2 ,

[0059] Wherein, path cost is summed over all points on the reference line, heading represents the difference in radial angles (e.g., direction) between the points relative to the reference line, curvature represents the difference in curvature of the curve formed by the points relative to the reference line at the point, and distance represents the lateral (perpendicular to the reference line) distance from the point to the reference line. In some embodiments, distance represents the distance from the point to the destination location or the midpoint of the reference line. In another embodiment, the curvature cost is the change between the curvature values ​​of the curve formed at adjacent points. Note that points on the reference line can be selected as points that have equal distances from adjacent points. Based on the path cost, the path cost module can recalculate the reference line by minimizing the path cost using quadratic programming optimization, such as by a QP module.

[0060] The speed planning module 409 includes a point-time graph, a sequence smoother, and a speed cost module. The point-time graph may include an ST graph generated by the ST graph generator of the speed decision module 405. The speed planning module 409 may use a rough speed profile (e.g., a point-time graph) and the results from the path planning module 407 as initial constraints to calculate the optimal point-time curve. The sequence smoother may apply a smoothing algorithm (such as B-spline or regression) to the time series of points. The speed cost module may recalculate the ST graph using a speed cost function that is used to optimize the total cost for moving candidates (e.g., acceleration / deceleration) at different time points.

[0061] For example, in one embodiment, the total speed cost function may be:

[0062] speed cost = ∑ points (speed′) 2 +∑ points (speed″) 2 +(distance) 2 ,

[0063] Wherein, speed cost is summed over all time process points, speed' represents the acceleration value or the cost of changing the speed between two adjacent points, speed" represents the jerk value, or the derivative of the acceleration value or the cost of changing the speed between two adjacent points, and distance represents the distance from the ST point to the destination location. Here, the speed cost module calculates the measurement point-time graph by minimizing the speed cost using quadratic programming optimization, such as through the QP module.

[0064] Aggregator 411 performs the function of aggregating path and speed planning results. For example, in one embodiment, aggregator 411 can combine a two-dimensional ST map and a SL map into a three-dimensional SLT map. In another embodiment, aggregator 411 can interpolate (or fill in additional points) based on two consecutive points on an SL reference line or ST curve. In another embodiment, aggregator 411 can translate the reference point from (S, L) coordinates to (x, y) coordinates. Trajectory generator 413 can calculate the final trajectory to control ADV510. For example, based on the SLT map provided by aggregator 411, trajectory generator 413 calculates a list of (x, y, T) points that indicate when the ADC should pass through a particular (x, y) coordinate.

[0065] Therefore, the path decision module 403 and the speed decision module 405 are configured to generate a rough path curve and a rough speed curve considering obstacles and / or traffic conditions. Given all the path and speed decisions about obstacles, the path planning module 407 and the speed planning module 409 will use QP programming to optimize the rough path curve and the rough speed curve according to the obstacles to generate an optimal trajectory with minimum path cost and / or speed cost.

[0066] Figure 5 is a block diagram illustrating a point-to-horizontal map according to one embodiment. Figure 5 , the SL map 500 has an S horizontal axis or point, and an L vertical axis or side. As described above, the point-lateral coordinates are a relative geometric coordinate system that is referenced to a particular fixed point on a reference line and follows the reference line. For example, a (S, L) = (1, 0) coordinate may represent one meter in front of a fixed point (i.e., the reference point) on the reference line, and a lateral offset of zero meters. A (S, L) = (2, 1) reference point may represent two meters in front of the fixed reference point along the reference line, and a one meter perpendicular lateral offset from the reference line, e.g., a left offset.

[0067] refer to Figure 5, the SL map 500 includes a reference line 501 and obstacles 503-509 sensed by the ADV 510. In one embodiment, the RADAR or LIDAR unit of the ADV 510 can sense the obstacles 503-509 in a different coordinate system and translate them to the SL coordinate system. In another embodiment, the obstacles 503-509 can be artificially formed barriers as constraints, so the decision and planning modules will not search in the constrained geometric space. In this example, the path decision module can generate decisions for each of the obstacles 503-509, such as avoiding obstacles 503-508 and nudging (very close to) obstacles 509 (i.e., these obstacles can be other cars, buildings and / or structures). The path planning module can then use QP programming to recalculate or optimize the reference line 501 based on the path cost according to the obstacles 503-509, fine-tuning the reference line 501 with the minimum total cost as described above. In this example, the ADV nudged or approached the obstacle 509 very closely from the left side of the obstacle 509.

[0068] Fig. 6A and Figure 6B is a block diagram illustrating a measurement point-time diagram according to some embodiments. Fig. 6A , ST graph 600 has a vertical axis of measuring point (or S) and a horizontal axis of time (or T). ST graph 600 includes curve 601 and obstacles 603-607. As described above, curve 601 on the measuring point-time graph indicates at what time and how far the ADV is away from the measuring point. For example, (T, S) = (10000, 150) can mean that within 10000 milliseconds, the ADV will be 150 meters away from the fixed point (i.e., the reference point). In this example, obstacle 603 can be a building / structure to be avoided, and obstacle 607 can be an artificial barrier corresponding to the decision to overtake the moving vehicle.

[0069] refer to Figure 6B , in which case artificial barrier 605 is added to ST graph 610 as a constraint. An artificial barrier may be an example of a red light or a pedestrian in the path, which is about S2 away from the measured reference point, as perceived by the ADV. Barrier 705 corresponds to a decision to "stop" the ADV until the artificial barrier is later removed (i.e., the traffic light changes from red to green, or the pedestrian is no longer in the path).

[0070] One of the path planning and speed planning scenarios is planning an idle driving scenario. As described above, due to the nature of the idle scenario, it is difficult for the autonomous driving system to plan a path curve and a speed curve by issuing throttle commands and brake commands over a period of time to simulate the idle driving scenario. In the perceived idle situation, if the vehicle is driven by a person, no throttle or brake commands should be issued. However, during autonomous driving, for each driving cycle, the control module 306 will issue control commands based on the planning and control information provided by the planning module 305, which is difficult.

[0071] Return to reference Figure 3A According to one embodiment, the idle planning module 308 is configured to perform path planning and speed planning for idle driving scenarios. The idle planning module 308 can be implemented as part of the planning module 305 and / or the control module 306, or alternatively, Figure 4 The idle speed planning module 308 includes but is not limited to the following: Figure 7 A speed criterion generator 701 and an idle speed optimizer 702 are shown.

[0072] According to one embodiment, the driving environment is sensed by, for example, the perception module 302 and / or the positioning module 303 based on sensor data obtained from a variety of sensors (e.g., GPS, IMU), including determining the current speed of the ADV. In response to a request to drive at idle speed, the speed criterion generator 701 generates a speed criterion based on an idle curve and according to the current speed of the ADV. The idle optimizer 702 performs a speed planning operation, including optimizing a cost function based on the speed criterion to determine the speed of a track point at different time points along a track planned for driving the ADV. Then, one or more control commands are generated to control the ADV at a planned speed along the planned track so that the ADV moves according to the expected idle speed.

[0073] In one embodiment, for example, an idle speed curve is generated by a data analysis system such as server 103 based on driving statistics collected from a large number of vehicles similar to the ADV when the vehicles are driven at idle speed. The speed curve represents the speed change of the vehicle from zero to a relatively constant speed when no throttle command or brake command is applied. When generating the speed criterion, a portion of the speed curve from the current speed of the ADV to the target idle speed represented by the speed curve is extracted from the speed curve, wherein the extracted portion of the speed curve is used for the speed planning operation. During the speed planning operation, the extracted portion of the speed curve is used as a speed reference line to generate a speed cost using a speed cost function.

[0074] In one embodiment, an idle planning operation is performed in response to determining that the current speed of the ADV is below a predetermined speed threshold (e.g., a target idle speed associated with the ADV). The speed profile is one of many speed profiles generated based on driving statistics collected from a variety of vehicles. Each of the speed profiles is associated with one of a different type or model of vehicle.

[0075] Figure 8 An example of a speed curve representing the idle behavior of a vehicle according to one embodiment is shown. Speed ​​curve 800 represents the change or behavior of the vehicle speed in an idle driving scenario associated with a particular type or model of vehicle. Speed ​​curve 800 can be generated offline based on a large amount of driving statistics collected from a large number of vehicles of the same or similar type or model. According to one embodiment, in response to the current speed 801 of the ADV, a search operation is performed on the speed curve 800. In this example, based on the current speed 801, a portion 802 is identified and extracted from the speed curve 800. Portion 802 represents a speed curve from the current speed to the target speed 803. As described above, for idle driving scenarios, portion 802 can be used as an idle criterion or idle reference line for speed planning or speed optimization. For example, a speed cost function such as the speed cost function described above can be used to determine the speed cost based on the difference between the speed curve and the idle criterion 802. When the difference is large, the speed cost is high, and vice versa. Since the idle curve is generated based on the driving behavior of human drivers of a large number of vehicles, the speed planning for the idle driving scenario can be close to the human driving experience or a similar comfort level.

[0076] Fig. 9 900 is a flow chart illustrating an example of a process for idle planning according to one embodiment. Process 900 may be performed by processing logic, which may include software, hardware, or a combination thereof. For example, process 900 may be performed by Figure 3A-3B The autonomous driving system 300 performs. Fig. 9 At box 901, processing logic senses the driving environment around the ADV based on sensor data obtained from multiple sensors, including determining the current speed of the ADV. At box 902, in response to a request to drive at idle speed, the processing logic generates a speed criterion based on an idle curve and according to the current speed of the ADV. In one embodiment, an idle curve associated with the type or model of the ADV is retrieved, and a portion of the idle curve is extracted from the idle curve based on the current speed of the ADV. At box 903, the processing logic performs a speed planning operation by optimizing a cost function based on the speed criterion to determine the speed of multiple trajectory points along the trajectory planned for driving the ADV. At box 904, the processing logic generates multiple control commands to control the ADV at the planned speed along the trajectory so that the ADV moves according to the expected idle speed.

[0077] Note that some or all of the components shown and described above may be implemented in software, hardware, or a combination thereof. For example, these components may be implemented as software installed and stored in a permanent storage device, which may be loaded and executed in a memory by a processor (not shown) to perform the processes or operations described throughout the present application. Alternatively, these components may be implemented as executable code programmed or embedded in dedicated hardware, such as an integrated circuit (e.g., a dedicated IC or ASIC), a digital signal processor (DSP), or a field programmable gate array (FPGA), which may be accessed via a corresponding driver and / or operating system from an application. In addition, these components may be implemented as specific hardware logic in a processor or processor core as part of an instruction set accessible via one or more specific instruction software components.

[0078] Some portions of the foregoing detailed description have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities.

[0079] It should be remembered, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise stated, as will be apparent from the above discussion, it should be understood that throughout the specification, discussions using terms such as those set forth in the appended claims refer to the actions and processes of a computer system or similar electronic computing device that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system's memories or registers or other such information storage, transmission or display devices.

[0080] Embodiments of the present disclosure also relate to apparatus for performing the operations herein. Such a computer program is stored in a non-transitory computer-readable medium. A machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., computer) readable storage medium (e.g., a read-only memory ("ROM"), a random access memory ("RAM"), a magnetic disk storage medium, an optical storage medium, a flash memory device).

[0081] The processes or methods described in the foregoing figures may be performed by processing logic including hardware (e.g., circuits, dedicated logic, etc.), firmware, software (e.g., embodied on a non-transitory computer-readable medium), or a combination of both. Although the processes or methods are described above with respect to some sequential operations, it should be understood that some of the operations described may be performed in a different order. In addition, some operations may be performed in parallel rather than sequentially.

[0082] The embodiments of the present disclosure are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages ​​may be used to implement the teachings of the embodiments of the present disclosure as described herein.

[0083] In the foregoing description, embodiments of the present disclosure have been described with reference to specific exemplary embodiments of the present disclosure. Obviously, various modifications may be made thereto without departing from the broader spirit and scope of the present disclosure as set forth in the appended claims. Therefore, the description and the accompanying drawings should be considered illustrative rather than restrictive.

Claims

1. A computer-implemented method for operating an autonomous vehicle (ADV), the method comprising: sensing a driving environment around the ADV based on sensor data obtained from a plurality of sensors, including determining a current speed of the ADV; generating idle criteria for speed optimization based on an idle curve and in accordance with the current speed of the ADV in response to a request to drive the ADV at an idle speed, wherein the idle curve represents a speed change of a vehicle from zero to a relatively constant speed without application of a throttle command or a brake command; determining a speed cost based on a difference between a speed profile determined by a speed cost function and the idle criterion, optimizing the speed cost function using the speed cost, wherein the speed cost function is used to optimize a total cost for acceleration or deceleration at different time points; performing a speed planning operation to determine target speeds for a plurality of trajectory points along a trajectory planned for driving the ADV according to the optimized speed cost function; as well as A plurality of control commands are generated to control the ADV along the trajectory at the planned target speed so that the ADV moves according to the expected idle speed. 2 . The method of claim 1 , wherein the idle speed profile is generated based on driving statistics data collected from a plurality of vehicles similar to the ADV while the plurality of vehicles are driven at an idle speed.

3. The method of claim 1, wherein generating a speed criterion includes extracting a portion of the idle speed curve from the current speed of the ADV to a target idle speed represented by the idle speed curve, wherein the extracted portion is used for the speed planning operation.

4. The method of claim 1 further comprising determining whether the current speed of the ADV is below a predetermined speed threshold, wherein the speed criteria is generated if the current speed of the ADV is below the predetermined speed threshold. 5 . The method of claim 1 , wherein the idle speed profile is one of a plurality of speed profiles corresponding to a plurality of different types of vehicles, the plurality of speed profiles being generated based on driving statistics of a large number of vehicles of the different types.

6. A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor causes the processor to perform a computer-implemented method for operating an autonomous driving vehicle (ADV) as claimed in any one of claims 1 to 5.

7. A data processing system comprising: processor; as well as A memory coupled to the processor and storing instructions which, when executed by the processor, cause the processor to perform a computer-implemented method for operating an autonomous driving vehicle ADV as claimed in any one of claims 1 to 5.

8. A computer program product comprising a computer program which, when executed by a processor, implements a computer-implemented method for operating an autonomous driving vehicle ADV according to any one of claims 1 to 5.

Citation Information

Patent Citations

  • Navigation system with ecological route based destination guidance mechanism and method of operation thereof

    CN103270391A

  • Method and apparatus for fuel consumption prediction and cost estimation via crowd-sensing in vehicle navigation system

    CN106767874A

  • Driving control method and device for assisting transportation tool, equipment and medium

    CN110126815A

  • Method and control arrangement for vehicle route planning

    DE102018004671A1

  • Vehicle control device

    JP2012112754A