Patent Grant
12054209
This description relates to electric power steering torque compensation.
An electric power steering (EPS) system is a system that applies a torque on a steering column of a vehicle to turn the vehicle one way or another. The EPS (sometimes called electric power-assisted steering) system is mounted on either the steering column or steering gear and applies torque to the steering column which turns the steering wheel. In an autonomous vehicle, an EPS system can apply a torque to the steering column, thereby controlling the operation of the vehicle.
Techniques are provided for a method implemented by a computer, e.g., a computer onboard an autonomous vehicle. A planning circuit onboard the vehicle and connected to an EPS system of the vehicle determines a compensatory torque signal to modify an actual steering angle of a steering wheel of the vehicle to match an expected steering angle of the steering wheel. The planning circuit transmits the compensatory torque signal to a control circuit that controls the steering angle of the steering wheel. The EPS system modifies the actual steering angle based on the compensatory torque signal resulting in a modified steering angle. The control circuit operates the vehicle based on the modified steering angle.
These and other aspects, features, and implementations can be expressed as methods, apparatus, systems, components, program products, means or steps for performing a function, and in other ways.
These and other aspects, features, and implementations will become apparent from the following descriptions, including the claims.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.
In the drawings, specific arrangements or orderings of schematic elements, such as those representing devices, modules, instruction blocks and data elements, are shown for ease of description. However, it should be understood by those skilled in the art that the specific ordering or arrangement of the schematic elements in the drawings is not meant to imply that a particular order or sequence of processing, or separation of processes, is required. Further, the inclusion of a schematic element in a drawing is not meant to imply that such element is required in all embodiments or that the features represented by such element may not be included in or combined with other elements in some embodiments.
Further, in the drawings, where connecting elements, such as solid or dashed lines or arrows, are used to illustrate a connection, relationship, or association between or among two or more other schematic elements, the absence of any such connecting elements is not meant to imply that no connection, relationship, or association can exist. In other words, some connections, relationships, or associations between elements are not shown in the drawings so as not to obscure the disclosure. In addition, for ease of illustration, a single connecting element is used to represent multiple connections, relationships or associations between elements. For example, where a connecting element represents a communication of signals, data, or instructions, it should be understood by those skilled in the art that such element represents one or multiple signal paths (e.g., a bus), as may be needed, to affect the communication.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
Several features are described hereafter that can each be used independently of one another or with any combination of other features. However, any individual feature may not address any of the problems discussed above or might only address one of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Although headings are provided, information related to a particular heading, but not found in the section having that heading, may also be found elsewhere in this description. Embodiments are described herein according to the following outline:
This disclosure describes an autonomous vehicle with a planning circuit (described below) onboard the vehicle that is connected to an EPS system of the vehicle. The EPS system is controlled by a control circuit that applies a base torque to a steering column of the vehicle to turn the steering wheel to a desired steering angle. In some embodiments, the control circuit determines a base torque that will result in the desired steering angle, determines a base torque signal (for example, a voltage signal) of a magnitude that corresponds to a magnitude of the base torque, and transmits the base torque signal to the EPS. In response, the EPS applies the base torque represented by the base torque signal to the steering column. In this manner, the base torque signal is expected to turn the steering wheel by the desired steering angle. In some instances, for example, at certain vehicle speeds, an actual steering angle by which the steering wheel turns in response to the base torque signal deviates from the desired (or expected) steering angle. In some embodiments, the actual steering angle is provided to the control circuit as a feedback signal and the base torque is compensated by a compensatory torque that further modifies the actual steering angle to substantially match the expected steering angle.
This disclosure describes applying a compensatory torque to the steering column as a feedforward signal, rather than as a feedback signal, based on knowing an expected deviation of the actual steering angle from the expected steering angle ahead of time, that is, before the base torque signal is applied to the EPS. The feedforward signal represents the amount of compensatory torque by which the base torque is to be adjusted (for example, increased or decreased) so that the actual steering angle substantially matches the expected steering angle. In other words, based on vehicle driving conditions, the planning circuit expects a deviation between an actual steering angle and an expected steering angle. As a proactive response, the planning circuit determines a compensatory torque signal to modify the actual steering angle of the steering wheel to match the expected steering angle, and transmits the compensatory torque signal to the control circuit. The control circuit modifies the base torque signal according to the compensatory torque signal and applies the modified torque signal to the EPS system. Embodiments of the disclosure are described with reference to torque applied to a steering column to turn a steering wheel connected to the steering column. The techniques described here are applicable to vehicles without a steering wheel in which the steering column operates other features of the vehicle to turn the vehicle.
System Overview
As used herein, the term “autonomous capability” refers to a function, feature, or facility that enables a vehicle to be partially or fully operated without real-time human intervention, including without limitation fully autonomous vehicles, highly autonomous vehicles, and conditionally autonomous vehicles.
As used herein, an autonomous vehicle (AV) is a vehicle that possesses autonomous capability.
As used herein, “vehicle” includes means of transportation of goods or people. For example, cars, buses, trains, airplanes, drones, trucks, boats, ships, submersibles, dirigibles, etc. A driverless car is an example of a vehicle.
As used herein, “trajectory” refers to a path or route to navigate an AV from a first spatiotemporal location to second spatiotemporal location. In an embodiment, the first spatiotemporal location is referred to as the initial or starting location and the second spatiotemporal location is referred to as the destination, final location, goal, goal position, or goal location. In some examples, a trajectory is made up of one or more segments (e.g., sections of road) and each segment is made up of one or more blocks (e.g., portions of a lane or intersection). In an embodiment, the spatiotemporal locations correspond to real world locations. For example, the spatiotemporal locations are pick up or drop-off locations to pick up or drop-off persons or goods.
As used herein, “sensor(s)” includes one or more hardware components that detect information about the environment surrounding the sensor. Some of the hardware components can include sensing components (e.g., image sensors, biometric sensors), transmitting and/or receiving components (e.g., laser or radio frequency wave transmitters and receivers), electronic components such as analog-to-digital converters, a data storage device (such as a RAM and/or a nonvolatile storage), software or firmware components and data processing components such as an ASIC (application-specific integrated circuit), a microprocessor and/or a microcontroller.
As used herein, a “scene description” is a data structure (e.g., list) or data stream that includes one or more classified or labeled objects detected by one or more sensors on the AV vehicle or provided by a source external to the AV.
As used herein, a “road” is a physical area that can be traversed by a vehicle, and may correspond to a named thoroughfare (e.g., city street, interstate freeway, etc.) or may correspond to an unnamed thoroughfare (e.g., a driveway in a house or office building, a section of a parking lot, a section of a vacant lot, a dirt path in a rural area, etc.). Because some vehicles (e.g., 4-wheel-drive pickup trucks, sport utility vehicles, etc.) are capable of traversing a variety of physical areas not specifically adapted for vehicle travel, a “road” may be a physical area not formally defined as a thoroughfare by any municipality or other governmental or administrative body.
As used herein, a “lane” is a portion of a road that can be traversed by a vehicle. A lane is sometimes identified based on lane markings. For example, a lane may correspond to most or all of the space between lane markings, or may correspond to only some (e.g., less than 50%) of the space between lane markings. For example, a road having lane markings spaced far apart might accommodate two or more vehicles between the markings, such that one vehicle can pass the other without traversing the lane markings, and thus could be interpreted as having a lane narrower than the space between the lane markings, or having two lanes between the lane markings. A lane could also be interpreted in the absence of lane markings. For example, a lane may be defined based on physical features of an environment, e.g., rocks and trees along a thoroughfare in a rural area or, e.g., natural obstructions to be avoided in an undeveloped area. A lane could also be interpreted independent of lane markings or physical features. For example, a lane could be interpreted based on an arbitrary path free of obstructions in an area that otherwise lacks features that would be interpreted as lane boundaries. In an example scenario, an AV could interpret a lane through an obstruction-free portion of a field or empty lot. In another example scenario, an AV could interpret a lane through a wide (e.g., wide enough for two or more lanes) road that does not have lane markings. In this scenario, the AV could communicate information about the lane to other AVs so that the other AVs can use the same lane information to coordinate path planning among themselves.
The term “over-the-air (OTA) client” includes any AV, or any electronic device (e.g., computer, controller, IoT device, electronic control unit (ECU)) that is embedded in, coupled to, or in communication with an AV.
The term “over-the-air (OTA) update” means any update, change, deletion or addition to software, firmware, data or configuration settings, or any combination thereof, that is delivered to an OTA client using proprietary and/or standardized wireless communications technology, including but not limited to: cellular mobile communications (e.g., 2G, 3G, 4G, 5G), radio wireless area networks (e.g., WiFi) and/or satellite Internet.
The term “edge node” means one or more edge devices coupled to a network that provide a portal for communication with AVs and can communicate with other edge nodes and a cloud based computing platform, for scheduling and delivering OTA updates to OTA clients.
The term “edge device” means a device that implements an edge node and provides a physical wireless access point (AP) into enterprise or service provider (e.g., VERIZON, AT&T) core networks. Examples of edge devices include but are not limited to: computers, controllers, transmitters, routers, routing switches, integrated access devices (IADs), multiplexers, metropolitan area network (MAN) and wide area network (WAN) access devices.
“One or more” includes a function being performed by one element, a function being performed by more than one element, e.g., in a distributed fashion, several functions being performed by one element, several functions being performed by several elements, or any combination of the above.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this description, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
As used herein, an AV system refers to the AV along with the array of hardware, software, stored data, and data generated in real-time that supports the operation of the AV. In an embodiment, the AV system is incorporated within the AV. In an embodiment, the AV system is spread across several locations. For example, some of the software of the AV system is implemented on a cloud computing environment similar to cloud computing environment 300 described below with respect to
In general, this document describes technologies applicable to any vehicles that have one or more autonomous capabilities including fully autonomous vehicles, highly autonomous vehicles, and conditionally autonomous vehicles, such as so-called Level 5, Level 4 and Level 3 vehicles, respectively (see SAE International's standard J3016: Taxonomy and Definitions for Terms Related to On-Road Motor Vehicle Automated Driving Systems, which is incorporated by reference in its entirety, for more details on the classification of levels of autonomy in vehicles). The technologies described in this document are also applicable to partially autonomous vehicles and driver assisted vehicles, such as so-called Level 2 and Level 1 vehicles (see SAE International's standard J3016: Taxonomy and Definitions for Terms Related to On-Road Motor Vehicle Automated Driving Systems). In an embodiment, one or more of the Level 1, 2, 3, 4 and 5 vehicle systems may automate certain vehicle operations (e.g., steering, braking, and using maps) under certain operating conditions based on processing of sensor inputs. The technologies described in this document can benefit vehicles in any levels, ranging from fully autonomous vehicles to human-operated vehicles.
Autonomous vehicles have advantages over vehicles that require a human driver. One advantage is safety. For example, in 2016, the United States experienced 6 million automobile accidents, 2.4 million injuries, 40,000 fatalities, and 13 million vehicles in crashes, estimated at a societal cost of $910+billion. U.S. traffic fatalities per 100 million miles traveled have been reduced from about six to about one from 1965 to 2015, in part due to additional safety measures deployed in vehicles. For example, an additional half second of warning that a crash is about to occur is believed to mitigate 60% of front-to-rear crashes. However, passive safety features (e.g., seat belts, airbags) have likely reached their limit in improving this number. Thus, active safety measures, such as automated control of a vehicle, are the likely next step in improving these statistics. Because human drivers are believed to be responsible for a critical pre-crash event in 95% of crashes, automated driving systems are likely to achieve better safety outcomes, e.g., by reliably recognizing and avoiding critical situations better than humans; making better decisions, obeying traffic laws, and predicting future events better than humans; and reliably controlling a vehicle better than a human.
Referring to
In an embodiment, the AV system 120 includes devices 101 that are instrumented to receive and act on operational commands from the computer processors 146. In an embodiment, computing processors 146 are similar to the processor 304 described below in reference to
In an embodiment, the AV system 120 includes sensors 121 for measuring or inferring properties of state or condition of the AV 100, such as the AV's position, linear and angular velocity and acceleration, and heading (e.g., an orientation of the leading end of AV 100). Example of sensors 121 are GPS, inertial measurement units (IMU) that measure both vehicle linear accelerations and angular rates, wheel speed sensors for measuring or estimating wheel slip ratios, wheel brake pressure or braking torque sensors, engine torque or wheel torque sensors, and steering angle and angular rate sensors.
In an embodiment, the sensors 121 also include sensors for sensing or measuring properties of the AV's environment. For example, monocular or stereo video cameras 122 in the visible light, infrared or thermal (or both) spectra, LiDAR 123, RADAR, ultrasonic sensors, time-of-flight (TOF) depth sensors, speed sensors, temperature sensors, humidity sensors, and precipitation sensors.
In an embodiment, the AV system 120 includes a data storage unit 142 and memory 144 for storing machine instructions associated with computer processors 146 or data collected by sensors 121. In an embodiment, the data storage unit 142 is similar to the ROM 308 or storage device 310 described below in relation to
In an embodiment, the AV system 120 includes communications devices 140 for communicating measured or inferred properties of other vehicles' states and conditions, such as positions, linear and angular velocities, linear and angular accelerations, and linear and angular headings to the AV 100. These devices include Vehicle-to-Vehicle (V2V) and Vehicle-to-Infrastructure (V2I) communication devices and devices for wireless communications over point-to-point or ad hoc networks or both. In an embodiment, the communications devices 140 communicate across the electromagnetic spectrum (including radio and optical communications) or other media (e.g., air and acoustic media). A combination of Vehicle-to-Vehicle (V2V) Vehicle-to-Infrastructure (V2I) communication (and, in some embodiments, one or more other types of communication) is sometimes referred to as Vehicle-to-Everything (V2X) communication. V2X communication typically conforms to one or more communications standards for communication with, between, and among autonomous vehicles.
In an embodiment, the communication devices 140 include communication interfaces. For example, wired, wireless, WiMAX, Wi-Fi, Bluetooth, satellite, cellular, optical, near field, infrared, or radio interfaces. The communication interfaces transmit data from a remotely located database 134 to AV system 120. In an embodiment, the remotely located database 134 is embedded in a cloud computing environment 200 as described in
In an embodiment, the remotely located database 134 also stores and transmits digital data (e.g., storing data such as road and street locations). Such data is stored on the memory 144 on the AV 100, or transmitted to the AV 100 via a communications channel from the remotely located database 134.
In an embodiment, the remotely located database 134 stores and transmits historical information about driving properties (e.g., speed and acceleration profiles) of vehicles that have previously traveled along trajectory 198 at similar times of day. In one implementation, such data may be stored on the memory 144 on the AV 100, or transmitted to the AV 100 via a communications channel from the remotely located database 134.
Computing devices 146 located on the AV 100 algorithmically generate control actions based on both real-time sensor data and prior information, allowing the AV system 120 to execute its autonomous driving capabilities.
In an embodiment, the AV system 120 includes computer peripherals 132 coupled to computing devices 146 for providing information and alerts to, and receiving input from, a user (e.g., an occupant or a remote user) of the AV 100. In an embodiment, peripherals 132 are similar to the display 312, input device 314, and cursor controller 316 discussed below in reference to
The cloud computing environment 200 includes one or more cloud data centers. In general, a cloud data center, for example the cloud data center 204a shown in
The cloud 202 includes cloud data centers 204a, 204b, and 204c along with the network and networking resources (for example, networking equipment, nodes, routers, switches, and networking cables) that interconnect the cloud data centers 204a, 204b, and 204c and help facilitate the computing systems' 206a-f access to cloud computing services. In an embodiment, the network represents any combination of one or more local networks, wide area networks, or internetworks coupled using wired or wireless links deployed using terrestrial or satellite connections. Data exchanged over the network, is transferred using any number of network layer protocols, such as Internet Protocol (IP), Multiprotocol Label Switching (MPLS), Asynchronous Transfer Mode (ATM), Frame Relay, etc. Furthermore, in embodiments where the network represents a combination of multiple sub-networks, different network layer protocols are used at each of the underlying sub-networks. In some embodiments, the network represents one or more interconnected internetworks, such as the public Internet.
The computing systems 206a-f or cloud computing services consumers are connected to the cloud 202 through network links and network adapters. In an embodiment, the computing systems 206a-f are implemented as various computing devices, for example servers, desktops, laptops, tablet, smartphones, Internet of Things (IoT) devices, autonomous vehicles (including, cars, drones, shuttles, trains, buses, etc.) and consumer electronics. In an embodiment, the computing systems 206a-f are implemented in or as a part of other systems.
In an embodiment, the computer system 300 includes a bus 302 or other communication mechanism for communicating information, and a hardware processor 304 coupled with a bus 302 for processing information. The hardware processor 304 is, for example, a general-purpose microprocessor. The computer system 300 also includes a main memory 306, such as a random-access memory (RAM) or other dynamic storage device, coupled to the bus 302 for storing information and instructions to be executed by processor 304. In one implementation, the main memory 306 is used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 304. Such instructions, when stored in non-transitory storage media accessible to the processor 304, render the computer system 300 into a special-purpose machine that is customized to perform the operations specified in the instructions.
In an embodiment, the computer system 300 further includes a read only memory (ROM) 308 or other static storage device coupled to the bus 302 for storing static information and instructions for the processor 304. A storage device 310, such as a magnetic disk, optical disk, solid-state drive, or three-dimensional cross point memory is provided and coupled to the bus 302 for storing information and instructions.
In an embodiment, the computer system 300 is coupled via the bus 302 to a display 312, such as a cathode ray tube (CRT), a liquid crystal display (LCD), plasma display, light emitting diode (LED) display, or an organic light emitting diode (OLED) display for displaying information to a computer user. An input device 314, including alphanumeric and other keys, is coupled to bus 302 for communicating information and command selections to the processor 304. Another type of user input device is a cursor controller 316, such as a mouse, a trackball, a touch-enabled display, or cursor direction keys for communicating direction information and command selections to the processor 304 and for controlling cursor movement on the display 312. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x-axis) and a second axis (e.g., y-axis), that allows the device to specify positions in a plane.
According to one embodiment, the techniques herein are performed by the computer system 300 in response to the processor 304 executing one or more sequences of one or more instructions contained in the main memory 306. Such instructions are read into the main memory 306 from another storage medium, such as the storage device 310. Execution of the sequences of instructions contained in the main memory 306 causes the processor 304 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry is used in place of or in combination with software instructions.
The term “storage media” as used herein refers to any non-transitory media that store data and/or instructions that cause a machine to operate in a specific fashion. Such storage media includes non-volatile media and/or volatile media. Non-volatile media includes, for example, optical disks, magnetic disks, solid-state drives, or three-dimensional cross point memory, such as the storage device 310. Volatile media includes dynamic memory, such as the main memory 306. Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid-state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NV-RAM, or any other memory chip or cartridge.
Storage media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise the bus 302. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infrared data communications.
In an embodiment, various forms of media are involved in carrying one or more sequences of one or more instructions to the processor 304 for execution. For example, the instructions are initially carried on a magnetic disk or solid-state drive of a remote computer. The remote computer loads the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to the computer system 300 receives the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector receives the data carried in the infrared signal and appropriate circuitry places the data on the bus 302. The bus 302 carries the data to the main memory 306, from which processor 304 retrieves and executes the instructions. The instructions received by the main memory 306 may optionally be stored on the storage device 310 either before or after execution by processor 304.
The computer system 300 also includes a communication interface 318 coupled to the bus 302. The communication interface 318 provides a two-way data communication coupling to a network link 320 that is connected to a local network 322. For example, the communication interface 318 is an integrated service digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface 318 is a local area network (LAN) card to provide a data communication connection to a compatible LAN. In some implementations, wireless links are also implemented. In any such implementation, the communication interface 318 sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.
The network link 320 typically provides data communication through one or more networks to other data devices. For example, the network link 320 provides a connection through the local network 322 to a host computer 324 or to a cloud data center or equipment operated by an Internet Service Provider (ISP) 326. The ISP 326 in turn provides data communication services through the world-wide packet data communication network now commonly referred to as the “Internet” 328. The local network 322 and Internet 328 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on the network link 320 and through the communication interface 318, which carry the digital data to and from the computer system 300, are example forms of transmission media. In an embodiment, the network 320 contains the cloud 202 or a part of the cloud 202 described above.
The computer system 300 sends messages and receives data, including program code, through the network(s), the network link 320, and the communication interface 318. In an embodiment, the computer system 300 receives code for processing. The received code is executed by the processor 304 as it is received, and/or stored in storage device 310, or other non-volatile storage for later execution.
Autonomous Vehicle Architecture
In use, the planning module 404 receives data representing a destination 412 and determines data representing a trajectory 414 (sometimes referred to as a route) that can be traveled by the AV 100 to reach (e.g., arrive at) the destination 412. In order for the planning module 404 to determine the data representing the trajectory 414, the planning module 404 receives data from the perception module 402, the localization module 408, and the database module 410.
The perception module 402 identifies nearby physical objects using one or more sensors 121, e.g., as also shown in
The planning module 404 also receives data representing the AV position 418 from the localization module 408. The localization module 408 determines the AV position by using data from the sensors 121 and data from the database module 410 (e.g., a geographic data) to calculate a position. For example, the localization module 408 uses data from a GNSS (Global Navigation Satellite System) sensor and geographic data to calculate a longitude and latitude of the AV. In an embodiment, data used by the localization module 408 includes high-precision maps of the roadway geometric properties, maps describing road network connectivity properties, maps describing roadway physical properties (such as traffic speed, traffic volume, the number of vehicular and cyclist traffic lanes, lane width, lane traffic directions, or lane marker types and locations, or combinations of them), and maps describing the spatial locations of road features such as crosswalks, traffic signs or other travel signals of various types. In an embodiment, the high-precision maps are constructed by adding data through automatic or manual annotation to low-precision maps.
The control module 406 receives the data representing the trajectory 414 and the data representing the AV position 418 and operates the control functions 420a-c (e.g., steering, throttling, braking, ignition) of the AV in a manner that will cause the AV 100 to travel the trajectory 414 to the destination 412. For example, if the trajectory 414 includes a left turn, the control module 406 will operate the control functions 420a-c in a manner such that the steering angle of the steering function will cause the AV 100 to turn left and the throttling and braking will cause the AV 100 to pause and wait for passing pedestrians or vehicles before the turn is made.
Autonomous Vehicle Inputs
Another input 502b is a RADAR system. RADAR is a technology that uses radio waves to obtain data about nearby physical objects. RADARs can obtain data about objects not within the line of sight of a LiDAR system. A RADAR system 502b produces RADAR data as output 504b. For example, RADAR data are one or more radio frequency electromagnetic signals that are used to construct a representation of the environment 190.
Another input 502c is a camera system. A camera system uses one or more cameras (e.g., digital cameras using a light sensor such as a charge-coupled device [CCD]) to obtain information about nearby physical objects. A camera system produces camera data as output 504c. Camera data often takes the form of image data (e.g., data in an image data format such as RAW, JPEG, PNG, etc.). In some examples, the camera system has multiple independent cameras, e.g., for the purpose of stereopsis (stereo vision), which enables the camera system to perceive depth. Although the objects perceived by the camera system are described here as “nearby,” this is relative to the AV. In use, the camera system may be configured to “see” objects far, e.g., up to a kilometer or more ahead of the AV. Accordingly, the camera system may have features such as sensors and lenses that are optimized for perceiving objects that are far away.
Another input 502d is a traffic light detection (TLD) system. A TLD system uses one or more cameras to obtain information about traffic lights, street signs, and other physical objects that provide visual navigation information. A TLD system produces TLD data as output 504d. TLD data often takes the form of image data (e.g., data in an image data format such as RAW, JPEG, PNG, etc.). A TLD system differs from a system incorporating a camera in that a TLD system uses a camera with a wide field of view (e.g., using a wide-angle lens or a fish-eye lens) in order to obtain information about as many physical objects providing visual navigation information as possible, so that the AV 100 has access to all relevant navigation information provided by these objects. For example, the viewing angle of the TLD system may be about 120 degrees or more.
In some embodiments, outputs 504a-d are combined using a sensor fusion technique. Thus, either the individual outputs 504a-d are provided to other systems of the AV 100 (e.g., provided to a planning module 404 as shown in
Path Planning
In addition to the route 902, a planning module also outputs lane-level route planning data 908. The lane-level route planning data 908 is used to traverse segments of the route 902 based on conditions of the segment at a particular time. For example, if the route 902 includes a multi-lane highway, the lane-level route planning data 908 includes trajectory planning data 910 that the AV 100 can use to choose a lane among the multiple lanes, e.g., based on whether an exit is approaching, whether one or more of the lanes have other vehicles, or other factors that vary over the course of a few minutes or less. Similarly, in some implementations, the lane-level route planning data 908 includes speed constraints 912 specific to a segment of the route 902. For example, if the segment includes pedestrians or un-expected traffic, the speed constraints 912 may limit the AV 100 to a travel speed slower than an expected speed, e.g., a speed based on speed limit data for the segment.
In an embodiment, the inputs to the planning module 404 includes database data 914 (e.g., from the database module 410 shown in
In an embodiment, the directed graph 1000 has nodes 1006a-d representing different locations between the start point 1002 and the end point 1004 that could be occupied by an AV 100. In some examples, e.g., when the start point 1002 and end point 1004 represent different metropolitan areas, the nodes 1006a-d represent segments of roads. In some examples, e.g., when the start point 1002 and the end point 1004 represent different locations on the same road, the nodes 1006a-d represent different positions on that road. In this way, the directed graph 1000 includes information at varying levels of granularity. In an embodiment, a directed graph having high granularity is also a subgraph of another directed graph having a larger scale. For example, a directed graph in which the start point 1002 and the end point 1004 are far away (e.g., many miles apart) has most of its information at a low granularity and is based on stored data, but also includes some high granularity information for the portion of the graph that represents physical locations in the field of view of the AV 100.
The nodes 1006a-d are distinct from objects 1008a-b which cannot overlap with a node. In an embodiment, when granularity is low, the objects 1008a-b represent regions that cannot be traversed by automobile, e.g., areas that have no streets or roads. When granularity is high, the objects 1008a-b represent physical objects in the field of view of the AV 100, e.g., other automobiles, pedestrians, or other entities with which the AV 100 cannot share physical space. In an embodiment, some or all of the objects 1008a-b are a static objects (e.g., an object that does not change position such as a street lamp or utility pole) or dynamic objects (e.g., an object that is capable of changing position such as a pedestrian or other car).
The nodes 1006a-d are connected by edges 1010a-c. If two nodes 1006a-b are connected by an edge 1010a, it is possible for an AV 100 to travel between one node 1006a and the other node 1006b, e.g., without having to travel to an intermediate node before arriving at the other node 1006b. (When we refer to an AV 100 traveling between nodes, we mean that the AV 100 travels between the two physical positions represented by the respective nodes.) The edges 1010a-c are often bidirectional, in the sense that an AV 100 travels from a first node to a second node, or from the second node to the first node. In an embodiment, edges 1010a-c are unidirectional, in the sense that an AV 100 can travel from a first node to a second node, however the AV 100 cannot travel from the second node to the first node. Edges 1010a-c are unidirectional when they represent, for example, one-way streets, individual lanes of a street, road, or highway, or other features that can only be traversed in one direction due to legal or physical constraints.
In an embodiment, the planning module 404 uses the directed graph 1000 to identify a path 1012 made up of nodes and edges between the start point 1002 and end point 1004.
An edge 1010a-c has an associated cost 1014a-b. The cost 1014a-b is a value that represents the resources that will be expended if the AV 100 chooses that edge. A typical resource is time. For example, if one edge 1010a represents a physical distance that is twice that as another edge 1010b, then the associated cost 1014a of the first edge 1010a may be twice the associated cost 1014b of the second edge 1010b. Other factors that affect time include expected traffic, number of intersections, speed limit, etc. Another typical resource is fuel economy. Two edges 1010a-b may represent the same physical distance, but one edge 1010a may require more fuel than another edge 1010b, e.g., because of road conditions, expected weather, etc.
When the planning module 404 identifies a path 1012 between the start point 1002 and end point 1004, the planning module 404 typically chooses a path optimized for cost, e.g., the path that has the least total cost when the individual costs of the edges are added together.
Autonomous Vehicle Control
In an embodiment, the controller 1102 receives data representing a desired output 1104. The desired output 1104 typically includes a velocity, e.g., a speed and a heading. The desired output 1104 can be based on, for example, data received from a planning module 404 (e.g., as shown in
In an embodiment, the controller 1102 receives feedback that is used in adjusting the inputs provided to the throttle and steering. For example, if the AV 100 encounters a disturbance 1110, such as a hill, the measured speed 1112 of the AV 100 is lowered below the desired output speed. In an embodiment, any measured output 1114 is provided to the controller 1102 so that the necessary adjustments are performed, e.g., based on the differential 1113 between the measured speed and desired output. The measured output 1114 includes measured position 1116, measured velocity 1118, (including speed and heading), measured acceleration 1120, and other outputs measurable by sensors of the AV 100.
In an embodiment, information about the disturbance 1110 is detected in advance, e.g., by a sensor such as a camera or LiDAR sensor, and provided to a predictive feedback module 1122. The predictive feedback module 1122 then provides information to the controller 1102 that the controller 1102 can use to adjust accordingly. For example, if the sensors of the AV 100 detect (“see”) a hill, this information can be used by the controller 1102 to prepare to engage the throttle at the appropriate time to avoid significant deceleration.
The controller 1102 also has a lateral tracking controller 1208 which affects the operation of a steering controller 1210. For example, the lateral tracking controller 1208 instructs the steering controller 1210 to adjust the position of the steering angle actuator 1212 depending on, e.g., feedback received by the controller 1102 and processed by the lateral tracking controller 1208.
The controller 1102 receives several inputs used to determine how to control the throttle/brake 1206 and steering angle actuator 1212. A planning module 404 provides information used by the controller 1102, for example, to choose a heading when the AV 100 begins operation and to determine which road segment to traverse when the AV 100 reaches an intersection. A localization module 408 provides information to the controller 1102 describing the current location of the AV 100, for example, so that the controller 1102 can determine if the AV 100 is at a location expected based on the manner in which the throttle/brake 1206 and steering angle actuator 1212 are being controlled. In an embodiment, the controller 1102 receives information from other inputs 1214, e.g., information received from databases, computer networks, etc.
Steering Angle Control Using Feedforward Signal
In some implementations, the torque signals can be voltage signals.
Ideally, the base torque applied to the steering column will turn the steering wheel by the expected steering angle determined by the planning module 404. However, at certain vehicle conditions (for example, vehicle speed, vehicle load, travel conditions, or similar vehicle conditions), an actual steering angle by which the steering wheel turns deviates from the expected steering angle. Such deviation can be observed, for example, at speeds ranging between 7 m/s and 11 m/s. In some embodiments, the controller 1102 can implement a control loop, for example, a proportional-integral-derivative (PID) control loop, to modify the torque signal based on the actual steering angle.
In some embodiments, the planning module 404 determines, based, for example, on vehicle conditions, that a base torque applied to the steering column will result in an actual steering angle that deviates from an expected steering angle determined for that base torque. Accordingly, the planning module 404 compensates for the deviation by applying a compensatory torque as a feedforward signal to the control loop, as described below.
The “Reference Trajectory” represents a signal from the planning module 404 according to which the controller 1102 controls the steering wheel. Based on the “Reference Trajectory,” the voltage module 1606 generates a voltage representing a torque signal and transmits the torque signal to the EPS system 1602. The EPS system 1602 applies the torque The actual steering angle of the steering wheel is provided as a feedback by the EPS system 1602 to the controller 1102 or the planning module 404. Based on the feedback, the planning module 404 or the controller 1102 can operate the voltage module 1606 to adjust the voltage (for example, increase or decrease the voltage) such that the actual steering angle matches the expected steering angle.
In some embodiments, the planning module 404 or the controller 1102 can operate the feedforward function module 1608 to apply a feedforward signal to the voltage module 1606 even without the feedback from the EPS system 1602. Returning to
To apply a compensatory torque to a base torque as a feedforward signal, the planning module 404 or the controller 1102 generates and stores, ahead of time, multiple compensatory torque signals, each representing a compensatory torque to be applied based on vehicle conditions. The vehicle conditions can include, for example, different speeds of the vehicle, weather conditions in which the vehicle is operating, conditions of the roads on which the vehicle is operating, loads on the vehicle or combinations of them. Loads on the vehicle can include passenger profiles, that is, descriptions of passengers known to ride the vehicle.
At 1414, the multiple compensatory torque signals are generated. To do so, in some embodiments, the following process steps can be implemented. In some embodiments, the planning module 404 can assign a quantitative value to each vehicle condition and operate the vehicle at that vehicle condition. The planning module 404 can determine a compensatory torque signal for each vehicle condition. At 1416, an expected steering angle for a respective torque signal is determined. For example, the planning module 404 can determine an expected steering angle for the base torque signal. In some embodiments, the planning module 404 determines the expected steering angle by curve fitting a 2nd order polynomial surface that relates vehicle conditions (for example, speed) and steering angle to a feedforward torque.
At 1418, the torque signal can be applied to the steering column. For example, the planning module 404 can apply a base torque signal to the controller 1102 as described earlier. At 1420, the vehicle can be operated at pre-determined vehicle conditions. For example, the planning module 404 can operate the vehicle at each vehicle condition, as described earlier. At 1422, an actual steering angle is measured. For example, the EPS system 1602 can measure an actual steering angle by which the steering wheel has turned in response to the base torque signal received from the planning module 404. At 1424, a compensatory torque signal needed to modify the actual steering angle is determined. For example, the planning module 404 can determine a compensatory torque signal to be applied to the base torque signal to eliminate a deviation between the expected steering angle and the actual steering angle. At 1426, the compensatory torque signal, the actual steering angle and the pre-determined vehicle conditions can be stored. For example, the planning module 404 can generate a data set that includes the compensatory torque signal, the base torque signal, and the quantitative value assigned to the vehicle condition.
The planning module 404 can implement the process steps 1416-1426 multiple times at different vehicle conditions and generate multiple data sets. A data set can include one vehicle condition (for example, a vehicle speed) or multiple vehicle conditions (for example, vehicle speeds on a rainy day, vehicle speeds on unpaved roads, etc.). In this manner, the planning module 404 can implement experimental techniques to generate and store compensatory torque signals to be applied as feedforward signals. During vehicle operation, the planning module 404 can detect vehicle operating conditions and, from among the stored data sets, identify the data set that substantially matches the vehicle operating conditions. From that data set, the planning module 404 can identify the compensatory torque signal and transmit the compensatory torque signal as the feedforward signal. In some embodiments, the planning module 404 can apply the compensatory torque signal in real-time. By real-time, it is meant that a time between the planning module 404 determining to apply the feedforward signal and identifying and transmitting the feedforward signal can be negligible (for example, of the order of nanoseconds, microseconds or milliseconds).
For example, the planning module 404 can apply the compensatory torque signal based on weather conditions in which the vehicle is operated. The weather condition can include, for example, rain, snow, high winds, other weather conditions or combinations of them. The planning module 404 can determine the weather conditions based on information sensed by sensors mounted on the AV 100, based on the geographic location in and the time at which the AV 100 is driving, from a remote location, or combinations of them. As the velocity of the AV 100 increases when the AV 100 is being driven under such extreme weather conditions, the deviation between an estimated steering angle and an actual steering angle can be greater than when the AV 100 is being driven under normal weather conditions. In some embodiments, the planning module 404 can determine a change in the weather condition and responsively (for example, in real-time), apply the feedforward compensatory torque signal to decrease or eliminate the deviation between the estimated steering angle and the actual steering angle.
In another example, the planning module 404 can apply the compensatory torque signal based on road conditions on which the vehicle is driven. The road condition can include, for example, wet roads, slippery roads, dirt roads, damaged roads or other road conditions. The planning module 404 can determine the road conditions based on information sensed by sensors mounted on the AV 100, based on the geographic location in which the AV 100 is driving, from a remote location, or combinations of them. As the velocity of the AV 100 increases when the AV 100 is being driven under such extreme road conditions, the deviation between an estimated steering angle and an actual steering angle can be greater than when the AV 100 is being driven under normal road conditions. In some embodiments, the planning module 404 can determine a change in the road condition and responsively (for example, in real-time), apply the feedforward compensatory torque signal to decrease or eliminate the deviation between the estimated steering angle and the actual steering angle.
In a further example, the planning module 404 can apply the compensatory torque signal based on load on the vehicle. The load can be greater than a normal load, for example, due to increased occupancy or a heavy item being transported in the vehicle. The planning module 404 can determine the load based on information sensed by sensors mounted on the AV 100, from a remote location, or combinations of them. As the velocity of the AV 100 increases when the AV 100 is being driven under high load, the deviation between an estimated steering angle and an actual steering angle can be greater than when the AV 100 is being driven under normal load. In some embodiments, the planning module 404 can determine a change in the load and responsively (for example, in real-time), apply the feedforward compensatory torque signal to decrease or eliminate the deviation between the estimated steering angle and the actual steering angle.
In another example, the planning module 404 can apply the compensatory torque signal based on a passenger profile of one or more passengers of the AV 100. The planning module 404 can store generic driving preferences applicable to any passenger of the AV 100. The generic driving preferences can specify a passenger's driving preferences, such as, taking the shortest route to the destination, avoiding freeways or tolls, to name a few. Based on the generic driving preferences, the planning module 404 can determine a set of vehicle driving conditions to be applied to satisfy the generic driving preferences. Also, the planning module 404 can determine a compensatory torque signal to be applied to the steering column for the set of vehicle driving conditions. Over time, the planning module 404 can modify the generic driving preferences based on each passenger that uses the AV 100. Subsequently, the planning module 404 can identify the passenger that has boarded the vehicle, identify the passenger profile for that passenger, and determine the compensatory torque signal to be applied to the steering column for a set of vehicle driving conditions that will satisfy that passenger's driving preferences. The planning module 404 can apply the determined compensatory torque signal in real-time.
In an embodiment, a quantity of the compensatory torque signal to be applied to the steering column can be determined by utilizing trained models for the AV 100. The trained models may be generated by applying machine learning techniques to historical traversal data based on which previous compensatory torque signals were generated and applied. The trained model may also take into account time of day, traffic conditions, pedestrian density based on audiovisual or other data, and weather, among other factors. For example, the vehicle driving conditions and the compensatory torque signals applied for the vehicle driving conditions can be generated and stored. The techniques described here to determine the quantity of the compensatory torque signal can be applied to the historical traversal data. Machine learning techniques can be implemented to train the planning module 404 to determine the quantity of the compensatory torque signal for any combination of vehicle conditions from the historical traversal data. The quantities determined by machine learning can be improved with the quantities determined in real-time. In addition, the historical traversal data can be updated to improve the machine learning techniques.
In some embodiments, the process steps 1416-1426 can be implemented by a computer system remote to the vehicle or can be implemented by the planning module 404 and the data sets transmitted to the computer system remote to the vehicle. In such instances, the compensatory torque to be applied to the EPS system 1602 can be received by the planning module 404 from the remote computer system.
In some embodiments, the planning module 404 can compensate for the deviation between the expected steering angle and the actual steering angle up to a pre-determined steering angle threshold, for example, 10° or some other angle. A deviation beyond the pre-determined threshold indicates a mechanical issue with the vehicle requiring attention in a repair shop. In such instances, that is, upon determining that the deviation exceeds the pre-determined threshold, the planning module 404 can operate the vehicle to a target location, for example, a repair shop or other target location. In some embodiments, the planning module 404 can implement operations in addition to operating the vehicle to the target location. The additional operations can include, for example, transmitting alerts to be displayed to a passenger in the vehicle, to the target location, to a different location, restricting instructions that can be sent to the EPS system 1602 or combinations of them.
In the foregoing description, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. The description and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The sole and exclusive indicator of the scope of the invention, and what is intended by the applicants to be the scope of the invention, is the literal and equivalent scope of the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any definitions expressly set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. In addition, when we use the term “further comprising,” in the foregoing description or following claims, what follows this phrase can be an additional step or entity, or a sub-step/sub-entity of a previously-recited step or entity.
| Number | Date | Country | Kind |
|---|---|---|---|
| PA201970163 | Mar 2019 | DK | national |
This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/776,422, filed Jan. 29, 2020, which claims priority to U.S. Provisional Patent Application No. 62/798,419, filed Jan. 29, 2019, and Danish Patent Application No. PA201970163, filed Mar. 14, 2019, the entire contents of each of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5907277 | Tokunaga et al. | May 1999 | A |
| 6625530 | Bolourchi | Sep 2003 | B1 |
| 10829149 | Garimella | Nov 2020 | B1 |
| 11014606 | Wu et al. | May 2021 | B2 |
| 20040256171 | Sugitani | Dec 2004 | A1 |
| 20060129293 | Bemnzen et al. | Jun 2006 | A1 |
| 20080047775 | Yamazaki | Feb 2008 | A1 |
| 20110057510 | Yamashita et al. | Mar 2011 | A1 |
| 20150057889 | Tamaizumi | Feb 2015 | A1 |
| 20150344065 | Lee et al. | Dec 2015 | A1 |
| 20160121923 | Maeda et al. | May 2016 | A1 |
| 20160251030 | Okada | Sep 2016 | A1 |
| 20170137023 | Anderson et al. | May 2017 | A1 |
| 20170247048 | Namikawa | Aug 2017 | A1 |
| 20170282972 | Moretti | Oct 2017 | A1 |
| 20180111642 | Endo | Apr 2018 | A1 |
| 20180186406 | Itou et al. | Jul 2018 | A1 |
| 20180297631 | Miyatani | Oct 2018 | A1 |
| 20180346021 | Wang | Dec 2018 | A1 |
| 20190023319 | Tyrrell et al. | Jan 2019 | A1 |
| 20190225260 | Tsubaki et al. | Jul 2019 | A1 |
| 20190256133 | Tsubaki et al. | Aug 2019 | A1 |
| 20190291775 | Taki | Sep 2019 | A1 |
| 20190359247 | Tsubaki | Nov 2019 | A1 |
| 20190359250 | Isshiki | Nov 2019 | A1 |
| 20190362570 | Kikuta | Nov 2019 | A1 |
| 20200005553 | Eyerman et al. | Jan 2020 | A1 |
| 20200039576 | Shoji | Feb 2020 | A1 |
| 20200156698 | Tsubaki et al. | May 2020 | A1 |
| 20200180692 | Hara | Jun 2020 | A1 |
| 20200239067 | Wu et al. | Jul 2020 | A1 |
| 20200254996 | Kashiwamura | Aug 2020 | A1 |
| 20200290668 | Moreillon | Sep 2020 | A1 |
| 20200298904 | Kitazume et al. | Sep 2020 | A1 |
| 20210061344 | Kitazume | Mar 2021 | A1 |
| 20210179142 | Horibe | Jun 2021 | A1 |
| 20210253161 | Yoshida | Aug 2021 | A1 |
| 20220063710 | Tsubaki | Mar 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 101134471 | Mar 2008 | CN |
| 102264593 | Nov 2011 | CN |
| 103674365 | Mar 2014 | CN |
| 106494497 | Mar 2017 | CN |
| 2987701 | Feb 2016 | EP |
| 3382656 | Oct 2018 | EP |
| 2496299 | May 2013 | GB |
| 08026129 | Jan 1996 | JP |
| 2005225421 | Aug 2005 | JP |
| 2007326499 | Dec 2007 | JP |
| 2012101677 | May 2012 | JP |
| 2013193490 | Sep 2013 | JP |
| 2017052353 | Mar 2017 | JP |
| 2018081002 | May 2018 | JP |
| 1020110051944 | May 2011 | KR |
| 1020130026937 | Mar 2013 | KR |
| 1020170093493 | Aug 2017 | KR |
| WO 2018038108 | Mar 2018 | WO |
| WO 2018084190 | May 2018 | WO |
| Entry |
|---|
| [No Author Listed], “J3016: Taxonomy and Definitions for Terms Related to On-Road Motor Vehicle Automated Driving Systems” SAE International, Sep. 2016, 30 pages. |
| DK 1rst Technical Examination in Danish Appln. No. PA 201970163, dated Jun. 19, 2019, 9 pages. |
| DK 2nd Technical Examination in Danish Appln. No. PA 201970163, dated Jan. 21, 2020, 5 pages. |
| DK 3rd Technical Examination in Danish Appln. PA 201970163, dated Sep. 16, 2020, 2 pages. |
| PCT International Search Report and Written Opinion in International Appln. No. PCT/IB2020/050714, dated May 8, 2020, 13 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210347408 A1 | Nov 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62798419 | Jan 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16776422 | Jan 2020 | US |
| Child | 17328905 | US |
