Parking management architecture for parking autonomous vehicles
Through V2X link and sensor data verification, autonomous vehicles find and occupy available parking space in the parking lot, solving the challenge of parking in the parking lot of L4 autonomous vehicles and achieving a safe and efficient parking process.
Patent Information
- Application Number
- CN201911270218.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-04-22
- Filing Date
- 2019-12-11
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2039-12-11
AI Technical Summary
The lack of effective ways to manage and implement the parking process of L4 autonomous vehicles, especially how to find and occupy parking space safely and effectively in parking lots is a challenge.
Access the remote server through the vehicle to all (V2X) link, obtain a list of available parking spaces in the parking lot, generate routes based on the parking lot map, navigate to available parking spaces, and use sensor data to verify the availability of parking spaces, plan parking paths to Vehicles are parked.
The safe and effective parking process of autonomous vehicles in the parking lot is realized, the human-computer interaction is reduced, parking efficiency and safety is improved, and available parking spaces can be found through the perception process without a list of available parking spaces.
Smart Images

Figure CN111857119B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure generally relate to operating an autonomous vehicle. More specifically, embodiments of the present disclosure relate to a parking system architecture for parking an autonomous vehicle. Background Art
[0002] A vehicle operating in an automated driving mode (e.g., without human control) can relieve occupants, particularly the driver, from some driving-related responsibilities. When operating in an automated driving 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] Autonomous driving has been defined at multiple levels. In Level 4 (L4) autonomous driving, the vehicle is designed to perform all safety-critical driving functions and monitor road conditions throughout the journey. Motion planning and control are key operations in autonomous driving, especially for automated parking situations.
[0004] Vehicle parking is an important part of autonomous driving scenarios. How to effectively and safely manage parking for L4 autonomous driving is an important topic to be explored. There is a lack of effective methods for L4 autonomous parking. Summary of the invention
[0005] One aspect of the present application provides a computer-implemented method for operating an autonomous vehicle. The method may include: in response to a request to park an autonomous vehicle (ADV) in a parking lot, accessing a remote server via a vehicle-to-everything (V2X) link to obtain a list of one or more parking spaces displayed as available in the parking lot; generating a route based on a parking lot map associated with the parking lot to navigate through the list of parking spaces; driving the ADV according to the route to locate one of the parking spaces that is available at a point in time; and in response to locating an available parking space, planning a parking path to park the ADV in the available parking space.
[0006] Another aspect of the present application provides a non-transitory machine-readable medium storing instructions, which when executed by a processor causes the processor to perform operations. The operations may include: in response to a request to park an autonomous vehicle (ADV) in a parking lot, accessing a remote server via a vehicle-to-everything (V2X) link to obtain a list of one or more parking spaces displayed as available in the parking lot; generating a route based on a parking lot map associated with the parking lot to navigate through the list of parking spaces; driving the ADV according to the route to locate one of the parking spaces that is available at a point in time; and in response to locating an available parking space, planning a parking path to park the ADV in the available parking space.
[0007] Another aspect of the present application provides a data processing system. The data processing system may include a processor and a memory, the memory being connected to the processor to store instructions. The instructions, when executed by the processor, cause the processor to perform operations. The operations may include: in response to a request to park an autonomous vehicle (ADV) in a parking lot, accessing a remote server through a vehicle-to-all (V2X) link to obtain a list of one or more parking spaces displayed as available in the parking lot; generating a route based on a parking lot map associated with the parking lot to navigate through the list of parking spaces; driving the ADV according to the route to locate one of the parking spaces that is available at a point in time; and in response to locating an available parking space, planning a parking path to park the ADV in the available parking space. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Embodiments of the present disclosure are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like reference numerals indicate similar elements.
[0009] Figure 1 is a block diagram illustrating a networked system according to one embodiment.
[0010] Figure 2 is a block diagram illustrating an example of an autonomous driving vehicle according to one embodiment.
[0011] FIG. 3A to FIG. 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 process diagram illustrating a process of automatic parking according to one embodiment.
[0013] Figure 5 is a block diagram illustrating a process of automatic parking according to one embodiment.
[0014] Figure 6 is a flow chart illustrating a process of automatic parking according to one embodiment.
[0015] Figure 7 is a flowchart illustrating a process of automatic parking according to another embodiment.
[0016] Figure 8 is a block diagram illustrating a data processing system according to one embodiment. DETAILED DESCRIPTION
[0017] Various embodiments and aspects of the present disclosure will be described with reference to the details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative of the present disclosure and should not be construed as limiting the present disclosure. Many specific details are described to provide a comprehensive understanding of various embodiments of the present disclosure. However, in some cases, well-known or conventional details are not described to provide a concise discussion of embodiments of the present disclosure.
[0018] References in this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment of the present disclosure. The appearances of the phrase "in one embodiment" in various places in this specification are not necessarily all referring to the same embodiment.
[0019] According to some embodiments, a parking management architecture or system is provided to centrally manage parking spaces (also referred to as parking spots or parking areas) of various parking lots (also referred to as parking structures) using high-definition (HD) maps. In such a configuration, each participating parking lot managed by a central system is equipped with one or more sensors configured to sense and detect which parking spaces of the parking lot are available. Signals representing available parking spaces may be periodically transmitted to a centralized server via a network. The centralized server compiles a list of parking spaces that appear to be available at different points in time, which list may be maintained in a database and accessible via an application programming interface (API) on a network. The centralized server may be communicatively coupled to multiple parking lots to manage their parking spaces.
[0020] When an autonomous vehicle (ADV) decides to park in a particular parking lot, the ADV accesses a centralized server over a network, e.g., via a vehicle-to-everything (V2X) link, to obtain a list of parking spaces within the parking lot that appear to be available at that point in time. Based on the list of apparently available parking spaces, the ADV generates a route to, for example, sequentially navigate through the available parking spaces within the parking lot. When the ADV arrives at an available parking space indicated in the list, the ADV may perform a perception process to verify whether the parking space is indeed available based on sensor data obtained from one or more sensors mounted on the vehicle. If available, the ADV plans a parking path using one or more sets of parking rules to park the ADV in the parking space.
[0021] According to one embodiment, in response to a request to park the ADV in a parking lot, a remote server is accessed over a network (e.g., a VX2 link) to obtain a list of parking spaces displayed as available in the parking lot. Based on the list of available parking spaces and a map associated with the parking lot, a route is generated to navigate through at least the available parking spaces in the parking lot. The ADV is driven according to the route to locate at least one of the available parking spaces, and the ADV is parked in the located available parking space. The centralized server is configured to periodically receive signals from the plurality of parking spaces indicating which parking spaces in the parking lot are apparently available.
[0022] In one embodiment, the route may be designed to navigate through all apparently available parking spaces in the shortest distance. When an apparently available parking space is located, the ADV verifies whether the parking space is indeed available based on a perception process that is performed based on sensor data obtained from various sensors mounted on the vehicle. If, in response to verifying that no parking space is available, the ADV continues to travel according to the route to locate the next parking space indicated in the list until a parking space is located and verified or all parking spaces in the list have been processed.
[0023] According to another embodiment, if no available parking spaces are indicated in the list, or the list cannot be obtained from the centralized server due to network problems, the ADV can still drive through all parking spaces in the parking lot using a perception process based on sensor data obtained from one or more sensors of the ADV to locate possible available parking spaces. Alternatively, the method relying on perception and the method using the centralized server method can be utilized in parallel to find the first parking space available in the parking lot.
[0024] Figure 1 is a block diagram showing a network configuration of an autonomous driving vehicle according to one embodiment of the present disclosure. Figure 1, the network configuration 100 includes an autonomous vehicle 101 that can be communicatively connected to one or more servers 103 to 104 via a network 102. Although one autonomous vehicle is shown, multiple autonomous vehicles can be connected to each other and / or to servers 103 to 104 via the network 102. The network 102 can be any type of network, for example, a wired or wireless local area network (LAN), a wide area network (WAN) such as the Internet, a cellular network, a satellite network, or a combination thereof. Servers 103 to 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 to 104 can be data analysis servers, content servers, traffic information servers, maps and points of interest (MPOI) servers, or location servers, etc.
[0025] 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 related to the environment in which the vehicle operates. The vehicle and its associated controller use the detected information to navigate through the environment. The autonomous vehicle 101 may operate in a manual mode, in a fully autonomous mode, or in a partially autonomous mode.
[0026] In one embodiment, the autonomous vehicle 101 includes, but is not limited to, a perception and planning system 110, a vehicle control system 111, a wireless communication system 112, a user interface system 113, an infotainment system 114, and a sensor system 115. The autonomous vehicle 101 may also include certain common components included in an ordinary vehicle, such as an engine, wheels, a steering wheel, a transmission, etc., which may be controlled by the vehicle control system 111 and / or the perception and planning system 110 using a variety of communication signals and / or commands, such as acceleration signals or commands, deceleration signals or commands, steering signals or commands, braking signals or commands, etc.
[0027] Components 110 to 115 may be communicatively coupled to each other via an interconnect, a bus, a network, or a combination thereof. For example, components 110 to 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. It is a message-based protocol originally designed for multiplexed electrical wiring within an automobile, but is also used in many other environments.
[0028] Reference now Figure 2In 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 ranging (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 of the autonomous vehicle. The LIDAR unit 215 may include, among other system components, one or more laser sources, a laser scanner, and one or more detectors. The camera 211 may include one or more devices for capturing images of the environment surrounding the autonomous vehicle. The camera 211 may be a still 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.
[0029] The sensor system 115 may also include other sensors, such as: a sonar sensor, an infrared sensor, a steering sensor, a throttle sensor, a brake sensor, and an audio sensor (e.g., a microphone). The audio sensor may be configured to collect sound 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.
[0030] 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 decelerate the wheels or tires of the vehicle. It should be noted that, as Figure 2 The components shown may be implemented in hardware, software or a combination thereof.
[0031] Back to Figure 1, the wireless communication system 112 allows communication between the autonomous driving vehicle 101 and external systems such as devices, sensors, other vehicles, etc. For example, the wireless communication system 112 can communicate directly with one or more devices wirelessly, or communicate wirelessly via a communication network, such as communicating with servers 103 to 104 through the network 102. The wireless communication system 112 can use any cellular communication network or wireless local area network (WLAN), for example, using WiFi, to communicate with another component or system. The wireless communication system 112 can communicate directly with a device (e.g., a passenger's mobile device, a display device, a speaker in the vehicle 101) using, for example, an infrared link, Bluetooth, etc. The user interface system 113 can be part of a peripheral device implemented in the vehicle 101, including, for example, a keyboard, a touch screen display device, a microphone, and a speaker.
[0032] Some or all of the functions of the autonomous vehicle 101 may be controlled or managed by the perception and planning system 110, particularly when operating in an autonomous mode. The perception and planning system 110 includes the necessary hardware (e.g., processor, memory, storage device) and software (e.g., operating system, planning and routing program) to receive information from the sensor system 115, the control system 111, the wireless communication system 112, and / or the user interface system 113, process the received information, plan a route or path from a starting point to a destination point, and then drive the vehicle 101 based on the planning and control information. Alternatively, the perception and planning system 110 may be integrated with the vehicle control system 111.
[0033] For example, a user as a passenger may specify a starting location and a destination of 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 to 104. The location server provides location services, and the MPOI server provides map services and POIs of certain locations. Alternatively, such location and MPOI information may be locally cached in a permanent storage device of the perception and planning system 110.
[0034] 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). It should be noted that the servers 103 to 104 may be operated by a third-party entity. Alternatively, the functionality of the servers 103 to 104 may be integrated with the perception and planning system 110. Based on 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.
[0035] 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, which may be 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.
[0036] Based on the driving statistics 123, the machine learning engine 122 generates or trains a rule set, an algorithm, and / or a prediction model 124 for various purposes. In one embodiment, the algorithm 124 may include a parking rule for searching for a parking space in a parking lot and parking the ADV in the parking space in the parking lot, and a communication rule for communicating with a centralized server that manages multiple parking lots to obtain a list of available parking spaces in the parking lot. The algorithm 124 may then be uploaded to the ADV for real-time use during autonomous driving.
[0037] Figure 3A and Figure 3B 300 is a block diagram illustrating an example of a perception and planning system for use with an autonomous vehicle according to one embodiment of the present disclosure. Figure 1 A portion of an autonomous vehicle 101 includes, but is not limited to, a perception and planning system 110, a control system 111, and a sensor system 115. FIG. 3A to FIG. 3BThe 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 , a route planning module 307 and a parking module 308 .
[0038] Some or all of the modules 301 to 308 may be implemented in software, hardware, or a combination thereof. For example, these modules may be installed in permanent storage 352, loaded into memory 351, and executed by one or more processors (not shown). It should be noted that some or all of these modules may be communicatively coupled to Figure 2 Some or all modules of the vehicle control system 111 of the present invention may be integrated with them. Some of the modules 301 to 308 may be integrated together as an integrated module. For example, the functions of the parking module 308 may be implemented in at least some of the perception module 302, the planning module 305, and the route making module 307.
[0039] 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 referred to as the map and route module) manages any data related to the user's trip or route. The user can log in, for example, via a user interface and specify the starting location and destination of the trip. The positioning module 301 communicates with other components of the autonomous vehicle 300, such as map and route information 311, to obtain trip-related data. 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 at certain locations, which can be cached as part of the map and route information 311. As 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.
[0040] Based on the sensor data provided by the sensor system 115 and the positioning information obtained by the positioning module 301, the perception module 302 determines the perception of the surrounding environment. The perception information can represent what an average driver would perceive around the vehicle that the driver is driving. The perception can include, for example, lane configuration in the form of objects, traffic light signals, the relative position of another vehicle, pedestrians, buildings, crosswalks or other traffic-related signs (e.g., stop signs, yield signs), etc. The lane configuration includes information describing one or more lanes, such as the shape of the lane (e.g., straight or curved), the width of the lane, how many lanes there are in a road, one-way or two-way lanes, merging or diverging lanes, exit lanes, etc.
[0041] The perception module 302 may include a computer vision system or the functionality of a computer vision system to process and analyze images captured by one or more cameras to identify objects and / or features in the autonomous vehicle environment. The objects may include traffic signals, road 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.
[0042] For each object, the prediction module 303 predicts what the object will behave in the situation. The prediction is performed based on the perception data of the perceived driving environment at that point in time, 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 make a turn. If the perception data indicates that there is no traffic light at the intersection, the prediction module 303 may predict that the vehicle may need to come to a complete stop before entering the intersection. If the perception data indicates that the vehicle is currently in a left-turn-only lane or a right-turn-only lane, the prediction module 303 may predict that the vehicle will be more likely to turn left or right, respectively.
[0043] 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 a crossing path) and metadata describing the object (e.g., speed, direction, turn angle), the decision module 304 decides how to encounter the object (e.g., overtake, yield, stop, pass). The decision module 304 can make such decisions based on a rule set such as traffic rules or driving rules 312, which can be stored in the persistent storage device 352.
[0044] The route making 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 location to the destination location (e.g., received from a user), the route making module 307 obtains route and map information 311 and determines all possible routes or paths from the starting location to the destination location. The route making module 307 can generate a reference line for each of the routes from the starting location to the destination location determined by it in the form of a topographic map. The reference line refers to an ideal route or path without any interference from other things 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. The topographic map is then provided to the decision module 304 and / or the planning module 305. Based on 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 traffic conditions predicted by the prediction module 303), the decision module 304 and / or the planning module 305 examine all possible routes to select and modify one of the optimal routes. The actual path or route used to control the ADV may differ substantially from the reference line provided by the route planning module 307 , depending on the particular driving circumstances at that point in time.
[0045] Based on the decision for each of the perceived objects, 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 lines provided by the route making module 307 as a basis. In other words, 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 overtake the object, and the planning module 305 may determine whether to overtake on the left or right side of the object. Planning and control data are generated by the planning module 305 and 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 25 mph.
[0046] Based on the planning and control data, the control module 306 controls and drives the autonomous vehicle according to the route or path defined by the planning and control data by sending appropriate commands or signals to the vehicle control system 111. 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, and steering commands) at different points in time along the route or path.
[0047] In one embodiment, the planning phase is performed in multiple planning cycles (also referred to as driving cycles) (such as, for example, in each 100 millisecond (ms) time interval). For each of the planning cycles or driving cycles, one or more control commands will be issued based on the planning data and the control data. That is, for each 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 of the current cycle (e.g., the next 5 seconds) based on the target location planned in the previous cycle. Then, the control module 306 generates one or more control commands (e.g., throttle command, brake command, steering control command) based on the planning data and control data of the current cycle.
[0048] It should be noted that the decision module 304 and the planning module 305 can be integrated into an integrated module. The decision module 304 / planning module 305 can 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 can determine a series of speeds and directions for enabling the autonomous vehicle to move along a path that substantially avoids perceived obstacles while allowing the autonomous vehicle to move along a roadway-based path to a final destination. The destination can be set based on user input via the user interface system 113. The navigation system can dynamically update the driving path while the autonomous vehicle is running. The navigation system can combine data from a GPS system and one or more maps to determine a driving path for the autonomous vehicle.
[0049] In one embodiment, reference is now made to Figure 4, the parking module 308 is communicatively connected to the modules 301 to 307 and is responsible for identifying a parking space in the parking lot and parking the vehicle in the parking space using a set of parking rules or algorithms 313. The parking module 308 is also communicatively connected to a parking management system represented by a parking management server 410 through a network to dynamically obtain parking availability information for a specific parking lot at a point in time. The parking management server 410 can be a centralized server. The parking management architecture or system is configured to centrally manage the parking spaces (also referred to as parking spaces or parking areas) of each parking lot 412 using a high-definition (HD) map. In such a configuration, each participating parking lot 412 managed by the parking management server 410 is equipped with one or more sensors (e.g., infrared sensors, ultrasonic sensors, pressure sensors, etc., not shown), which are configured to sense and detect which parking space of the parking lot is available. A signal representing an available parking space can be periodically transmitted from the parking lot 412 to the parking management server 410 through the network. The parking management server 410 compiles a parking space list 411 that is displayed as available at that point in time, which can be maintained in a database and can be accessed through an API over a network. A centralized server can be communicatively coupled to multiple parking lots to manage their parking spaces.
[0050] When the ADV 300 decides to park in a specific parking lot (parking lot 412 in this example), the V2X interface module 401 of the parking module 308 accesses the parking management server 410 through a network (e.g., through a vehicle-to-everything (V2X) link) to obtain a list 411 of parking spaces in the parking lot 412 that are displayed as available at that point in time. Based on the apparent list of available parking spaces, the parking route generator 402 of the parking module 308 generates or calls the route formulation module 307 to generate a route to, for example, navigate through the available parking spaces in the parking lot one by one in sequence. When the ADV 300 arrives at an available parking space indicated in the list, the parking space verifier 403 of the parking module 308 may execute or call the perception module 302 to perform a perception process to verify whether the parking space is indeed available based on sensor data obtained from one or more sensors installed on the vehicle. If available, the planning module 305 uses one or more parking rule sets to plan a parking path for parking the ADV in the parking space. Note that modules 401 to 403 may be integrated into fewer modules as part of parking module 308 .
[0051] According to one embodiment, reference is now made to Figure 4 and Figure 5As an example, in response to a request to park the ADV 300 in the parking lot 412, the V2X interface module 401 of the parking module 308 of the ADV 300 accesses the parking management server 410 through a network (e.g., through a VX2 link 501) to obtain a list 411 of parking spaces displayed as available in the parking lot 412. Based on the list 411 of available parking spaces and a map associated with the parking lot 412, the parking route generator 402 generates or calls the route formulation module 307 to generate a route 502 to at least navigate through the available parking spaces indicated in the list 411.
[0052] In this example, for illustrative purposes, parking spaces 511 to 513 are displayed as available as shown in list 411. Therefore, route 502 will be designed to navigate at least through parking spaces 511 to 513 displayed as available. Then, ADV 300 drives according to route 502 to locate at least one of the available parking spaces, and parks the ADV in the located available parking space. Note that parking management server 410 is configured to periodically receive signals from multiple parking lots indicating which parking space in the parking lot is displayed as available.
[0053] In one embodiment, the route 502 may be designed to navigate through all parking spaces 511 displayed as available to the parking space 513 in the shortest distance. When a parking space displayed as available is located, the parking space validator 403 of the parking module 308 verifies or calls the perception module 302 based on the perception process to verify whether the parking space is indeed available. The verification process is performed based on sensor data obtained from various sensors installed on the vehicle (e.g., LIDAR, camera, RADAR, etc.). If the parking space is unavailable in response to the verification, the ADV 300 continues to drive according to the route to locate the next parking space indicated in the list until a parking space is located and verified or all parking spaces in the list have been processed.
[0054] For example, available parking space list 411 indicates that parking space 511 is displayed as available. However, when ADV 300 arrives at parking space 511, parking space 511 may happen to be occupied by another vehicle. In this case, ADV 300 will continue driving according to route 502 to locate the next parking space displayed as available, which in this example is parking space 512, and so on. Note that a parking space that is displayed as available when the sensor detects a signal indicating availability and sends the signal to parking management server 410 may no longer be available when the vehicle arrives at the parking space because another vehicle may already be parked in the parking space.
[0055] According to another embodiment, if there are no available parking spaces indicated in the list 411, or the list 411 cannot be obtained from the parking management server 410 due to network problems, the ADV 300 can generate a route 502 using a perception process based on sensor data obtained from the sensors of the ADV 300 to drive through all parking spaces in the parking lot to locate a potentially available parking spot. Figure 5 In the example shown, although parking space 514 is not listed in list 411 or list 411 is unavailable, ADV 300 can drive according to route 502 using a perception process to locate and identify parking space 514. Without list 411, ADV 300 may take longer to locate and identify available parking spaces. However, this approach can be used as a backup option when list 411 is not available. Alternatively, the method relying on perception and the method using a centralized server method can be utilized in parallel to find the first parking space available in the parking lot.
[0056] Note that the parking route 502 is generated based on a map (also referred to as a parking lot map 405) associated with the parking lot 412. Such a parking lot map is an HD map that contains detailed information indicating the location and / or layout of parking spaces within the parking lot 412. Parking lot maps of different parking lots may have been generated, for example, as Figure 3A A portion of the map and route information 311 of the ADV 300 is pre-loaded and stored in the ADV 300. Alternatively, when the vehicle approaches the corresponding parking lot, the map of the specific parking lot can be dynamically obtained from the parking management server 410. When the parking lot has multiple parking levels, the map can include multiple parts, each corresponding to one of the parking levels. The perception module 302 of the ADV 300 can determine which parking level the ADV 300 is currently located in and load the appropriate map part for the current parking level.
[0057] It should be noted that some or all of the components shown and described above can be implemented in software, hardware, or a combination thereof. For example, such components can be implemented as software installed and stored in a permanent storage device, which can be loaded in a memory by a processor (not shown) and executed in the memory to implement the process or operation described throughout the present application. Alternatively, such components can be implemented as executable code programmed or embedded in dedicated hardware (such as an integrated circuit (e.g., an application-specific integrated circuit or ASIC), a digital signal processor (DSP), or a field programmable gate array (FPGA)), which can be accessed via a corresponding driver and / or operating system from an application. In addition, such components can be implemented as specific hardware logic in a processor or processor core as part of an instruction set that can be accessed by a software component through one or more specific instructions.
[0058] Figure 6 600 is a flow chart illustrating a process of automatic parking according to one embodiment. Process 600 may be performed by processing logic that may include software, hardware, or a combination thereof. For example, process 600 may be performed by parking module 308. Figure 6 In operation 601, in response to a request to park the ADV in a parking lot, the processing logic accesses a remote server (e.g., a centralized parking management server) via a V2X link to obtain a list of parking spaces displayed as available in the parking lot. In operation 602, the processing logic generates a parking route to navigate at least through the parking spaces displayed as available in the parking lot. In one embodiment, the route is designed to pass through all the parking spaces displayed as available in the shortest route. In operation 603, the ADV drives according to the parking route to locate one of the available parking spaces in the parking lot. In response to locating the available parking space, in operation 604, the processing logic plans the parking route to park the vehicle in the parking space.
[0059] Figure 7 700 is a flow chart illustrating a process of automatic parking according to another embodiment. Process 700 may be performed by processing logic that may include software, hardware, or a combination thereof. For example, process 700 may be performed by parking module 308. Figure 7 In operation 701, processing logic receives a request to park a vehicle in a parking space of a parking lot. In response to the request in operation 702, processing logic accesses a centralized parking management system through a network to obtain a list of available parking spaces of the parking lot. In operation 703, processing logic generates a first parking route based on an HD map associated with the parking lot to navigate through at least the available parking spaces. In operation 704, the vehicle drives according to the first parking route to locate one of the available parking spaces. If the located parking space is verified, in operation 705, a parking path is planned to automatically park the vehicle in the parking space.
[0060] On the other hand, in parallel or alternatively, in response to the parking request, in operation 706, the processing logic generates a second parking route based on a map of the parking lot to navigate through at least a portion of the parking spaces in the parking lot. In operation 707, the vehicle drives according to the second parking route. In operation 708, the processing logic uses a perception process to identify and detect an available parking space based on sensor data obtained from one or more sensors of the vehicle. Note that operations 702 to 704 and operations 706 to 708 may be performed in parallel. Alternatively, operations 706 to 708 may be performed when a list of available parking spaces cannot be obtained or operations 702 to 704 fail to locate an available parking space.
[0061] Figure 8is a block diagram illustrating an example of a data processing system that can be used with one embodiment of the present disclosure. For example, system 1500 can represent any data processing system described above that performs any of the above processes or methods, such as Figure 1 The system 1500 may include many different components. These components may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices, or other modules suitable for circuit boards (such as motherboards or plug-in cards of computer systems) or as components otherwise incorporated into the chassis of a computer system.
[0062] It should also be noted that system 1500 is intended to illustrate a high-level view of many components of a computer system. However, it should be understood that additional components may be provided in some embodiments, and in addition, different arrangements of the components shown may be provided in other embodiments. System 1500 may represent a desktop computer, a laptop computer, a tablet computer, a server, a mobile phone, a media player, a personal digital assistant (PDA), a smart watch, a personal communicator, a gaming device, a network router or hub, a wireless access point (AP) or a repeater, a set-top box, or a combination thereof. In addition, although only a single machine or system is shown, the term "machine" or "system" should also be understood to include any set of machines or systems that individually or collectively execute one (or more) instruction sets to execute any one or more methods discussed herein.
[0063] In one embodiment, system 1500 includes a processor 1501, a memory 1503, and devices 1505 to 1508 connected by a bus or interconnect 1510. Processor 1501 may represent a single processor or multiple processors including a single processor core or multiple processor cores. Processor 1501 may represent one or more general-purpose processors, such as a microprocessor, a central processing unit (CPU), etc. More specifically, processor 1501 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets, or a processor implementing a combination of instruction sets. Processor 1501 may also be one or more special-purpose processors, such as an application-specific integrated circuit (ASIC), a cellular or baseband processor, a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, a graphics processor, a communication processor, an encryption processor, a coprocessor, an embedded processor, or any other type of logic capable of processing instructions.
[0064] Processor 1501 (which may be a low-power multi-core processor socket, such as an ultra-low voltage processor) may serve as a main processing unit and central hub for communicating with various components of the system. Such a processor may be implemented as a system on a chip (SoC). Processor 1501 is configured to execute instructions for performing the operations and steps discussed herein. System 1500 may also include a graphics interface that communicates with an optional graphics subsystem 1504, which may include a display controller, a graphics processor, and / or a display device.
[0065] The processor 1501 may communicate with the memory 1503, which in one embodiment may be implemented via a plurality of memory devices to provide a certain amount of system storage. The memory 1503 may include one or more volatile storage (or memory) devices, such as random access memory (RAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), static RAM (SRAM), or other types of storage devices. The memory 1503 may store information including sequences of instructions to be executed by the processor 1501 or any other device. For example, executable code and / or data of various operating systems, device drivers, firmware (e.g., input-output basic system or BIOS), and / or applications may be loaded into the memory 1503 and executed by the processor 1501. The operating system may be any type of operating system, such as the Robot Operating System (ROS), a Company Operating system, Mac from Apple From Company LINUX, UNIX, or other real-time or embedded operating systems.
[0066] System 1500 may also include IO devices, such as devices 1505 to 1508, including a network interface device 1505, an optional input device 1506, and other optional IO devices 1507. The network interface device 1505 may include a wireless transceiver and / or a network interface card (NIC). The wireless transceiver may be a WiFi transceiver, an infrared transceiver, a Bluetooth transceiver, a WiMax transceiver, a wireless cellular phone transceiver, a satellite transceiver (e.g., a global positioning system (GPS) transceiver) or other radio frequency (RF) transceivers or combinations thereof. The NIC may be an Ethernet card.
[0067] Input device 1506 may include a mouse, a touchpad, a touch-sensitive screen (which may be integrated with display device 1504), a pointer device (such as a stylus), and / or a keyboard (e.g., a physical keyboard or a virtual keyboard displayed as part of a touch-sensitive screen). For example, input device 1506 may include a touch screen controller coupled to a touch screen. The touch screen and touch screen controller may, for example, use any of a variety of touch-sensitive technologies (including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies), as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen to detect contact and movement or discontinuity thereof.
[0068] IO devices 1507 may include audio devices. The audio devices may include speakers and / or microphones to facilitate voice-enabled functions such as voice recognition, voice replication, digital recording, and / or telephone functions. Other IO devices 1507 may also include universal serial bus (USB) ports, parallel ports, serial ports, printers, network interfaces, bus bridges (e.g., PCI-PCI bridges), sensors (e.g., such as accelerometer motion sensors, gyroscopes, magnetometers, light sensors, compasses, proximity sensors, etc.), or combinations thereof. Device 1507 may also include an imaging processing subsystem (e.g., a camera), which may include an optical sensor such as a charge-coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) optical sensor for facilitating camera functions (e.g., recording photos and video clips). Certain sensors may be connected to interconnect 1510 via a sensor hub (not shown), while other devices such as a keyboard or thermal sensor may be controlled by an embedded controller (not shown) according to the specific configuration or design of system 1500.
[0069] In order to provide permanent storage of information such as data, applications, one or more operating systems, etc., a mass storage device (not shown) may also be connected to the processor 1501. In various embodiments, in order to achieve a thinner and lighter system design and improve system responsiveness, such a mass storage device may be implemented via a solid-state device (SSD). However, in other embodiments, the mass storage device may be implemented primarily using a hard disk drive (HDD), wherein a smaller amount of SSD storage devices act as SSD caches to achieve non-volatile storage of context states and other such information during power-off events, thereby enabling fast power-on when system activities are restarted. In addition, a flash memory device may be connected to the processor 1501, for example, via a serial peripheral interface (SPI). Such a flash memory device may provide non-volatile storage of system software, including the BIOS and other firmware of the system.
[0070] The storage device 1508 may include a computer-accessible storage medium 1509 (also referred to as a machine-readable storage medium or computer-readable medium) on which is stored one or more instruction sets or software (e.g., modules, units, and / or logic 1528) embodying any one or more of the methods or functions described herein. The processing module / unit / logic 1528 may represent any of the above-mentioned components, such as, for example, the planning module 305, the control module 306, and / or the parking module 308. The processing module / unit / logic 1528 may also reside completely or at least partially in the memory 1503 and / or in the processor 1501 during its execution by the data processing system 1500, the memory 1503, and the processor 1501, which also constitute a machine-accessible storage medium. The processing module / unit / logic 1528 may also be transmitted or received via the network interface device 1505 via the network.
[0071] Computer-readable storage medium 1509 may also be used to permanently store some of the software functions described above. Although computer-readable storage medium 1509 is shown as a single medium in an exemplary embodiment, the term "computer-readable storage medium" should be considered to include a single medium or multiple media (e.g., a centralized or distributed database and / or associated caches and servers) storing the one or more instruction sets. The term "computer-readable storage medium" should also be considered to include any medium capable of storing or encoding an instruction set that is used to be executed by a machine and causes the machine to perform any one or more methods of the present disclosure. Therefore, the term "computer-readable storage medium" should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, or any other non-temporary machine-readable medium.
[0072] The processing modules / units / logic 1528, components, and other features described herein may be implemented as discrete hardware components or integrated into the functionality of hardware components (such as ASICS, FPGAs, DSPs, or similar devices). In addition, the processing modules / units / logic 1528 may be implemented as firmware or functional circuits within a hardware device. In addition, the processing modules / units / logic 1528 may be implemented in any combination of hardware devices and software components.
[0073] It should be noted that although system 1500 is shown as having various components of a data processing system, it is not intended to represent any particular architecture or manner of interconnecting the components; as such details are not germane to the embodiments of the present disclosure. It should also be appreciated that network computers, handheld computers, mobile phones, servers, and / or other data processing systems having fewer or possibly more components may also be used with embodiments of the present disclosure.
[0074] 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 generally considered herein to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulation of physical quantities.
[0075] It should be borne in mind, however, that all of these and similar terms are intended to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise expressly indicated in the above discussion, it should be understood that throughout the specification, discussions utilizing 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 data represented as physical (electronic) quantities within the computer system's registers and memories and transforms the data 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.
[0076] Embodiments of the present disclosure also relate to devices 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).
[0077] The processes or methods depicted in the foregoing figures may be performed by processing logic including hardware (e.g., circuits, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer-readable medium), or a combination of both. Although the processes or methods are described above in terms of some sequential operations, it should be understood that some of the operations may be performed in a different order. In addition, some operations may be performed in parallel rather than sequentially.
[0078] 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.
[0079] In the above description, embodiments of the present invention have been described with reference to specific exemplary embodiments of the present disclosure. It will be apparent that various modifications may be made to the present disclosure without departing from the broader spirit and scope of the present invention as set forth in the appended claims. Therefore, the present description and the accompanying drawings should be understood in an illustrative sense rather than a restrictive sense.
Claims
1. A computer-implemented method for operating an autonomous vehicle, the method include: In response to a request to park the autonomous vehicle in a parking lot, accessing a remote server via the vehicle-to-all link to obtain a list of a plurality of parking spaces displayed as available in the parking lot; generating a route for navigating through the list of parking spaces based on a parking lot map associated with the parking lot, wherein the route is designed to navigate through the list of all of the plurality of parking spaces in a shortest distance; driving the automated driving vehicle according to the route to locate one of the parking spaces that is available at a point in time; and In response to locating an available parking space, a parking path is planned to park the autonomous vehicle in the available parking space.
2. The method according to claim 1, in, The remote server periodically receives signals from a plurality of sensors disposed within the parking lot, the signals indicating which parking spaces are available.
3. The method according to claim 1, further comprising: include: In response to locating a first parking space indicated in the list, determining whether the located first parking space is indeed available based on sensor data obtained from one or more sensors installed on the autonomous vehicle, wherein, if the first parking space is indeed available based on the sensor data, planning the parking path to park the autonomous vehicle in the first parking space.
4. The method according to claim 3, further comprising: include: In response to determining that the first parking space is not available based on the sensor data, continuing to drive the autonomous vehicle along the route to locate a next parking space indicated in the list.
5. The method according to claim 4, in, Continuing to drive the autonomous vehicle along the route is performed until an available parking space is located or all parking spaces in the list have been processed.
6. The method according to claim 3, in, The one or more sensors include a lidar device.
7. The method according to claim 1, in, If the list does not contain any parking spaces indicated as available from the remote server, the method further comprises: generating a second route based on the parking lot map to navigate through at least a portion of a parking space in the parking lot; driving the autonomous driving vehicle according to the second route; and Based on sensor data obtained from one or more sensors of the autonomous vehicle, an available parking space is identified.
8. A non-transitory machine-readable medium storing instructions, which, when executed by a processor, cause the processor to perform operations, the operations include: In response to a request to park the autonomous vehicle in a parking lot, accessing a remote server via the vehicle-to-all link to obtain a list of a plurality of parking spaces displayed as available in the parking lot; generating a route for navigating through the list of parking spaces based on a parking lot map associated with the parking lot, wherein the route is designed to navigate through the list of all of the plurality of parking spaces in a shortest distance; driving the automated driving vehicle according to the route to locate one of the parking spaces that is available at a point in time; and In response to locating an available parking space, a parking path is planned to park the autonomous driving vehicle in the available parking space.
9. The machine-readable medium of claim 8, in, The remote server periodically receives signals from a plurality of sensors disposed within the parking lot, the signals indicating which parking spaces are available.
10. The machine-readable medium of claim 8, in, The operation also includes: in response to locating a first parking space indicated in the list, determining whether the located first parking space is indeed available based on sensor data obtained from one or more sensors installed on the autonomous driving vehicle, wherein, if the first parking space is indeed available based on the sensor data, planning the parking path to park the autonomous driving vehicle in the first parking space.
11. The machine-readable medium of claim 10, in, The operations also include, in response to determining based on the sensor data that the first parking space is not available, continuing to drive the autonomous vehicle along the route to locate a next parking space indicated in the list.
12. The machine-readable medium of claim 11, in, Continuing to drive the autonomous vehicle along the route is performed until an available parking space is located or all parking spaces in the list have been processed.
13. The machine-readable medium of claim 10, in, The one or more sensors include a lidar device.
14. The machine-readable medium of claim 8, in, If the list does not include any parking spaces indicated as available from the remote server, the machine-readable medium further comprises: generating a second route based on the parking lot map to navigate through at least a portion of a parking space in the parking lot; driving the autonomous driving vehicle according to the second route; and Based on sensor data obtained from one or more sensors of the autonomous vehicle, an available parking space is identified.
15. A data processing system, include: processor; as well as a memory coupled to the processor to store instructions that, when executed by the processor, cause the processor to perform operations comprising: In response to a request to park the autonomous vehicle in a parking lot, accessing a remote server through the vehicle-to-all link to obtain a list of a plurality of parking spaces displayed as available in the parking lot, generating a route for navigating through the list of parking spaces based on a parking lot map associated with the parking lot, wherein the route is designed to navigate through the list of all of the plurality of parking spaces in a shortest distance, driving the autonomous vehicle according to the route to locate one of the parking spaces that is available at a point in time, and In response to locating an available parking space, a parking path is planned to park the autonomous driving vehicle in the available parking space.
16. The system according to claim 15, in, The remote server periodically receives signals from a plurality of sensors disposed within the parking lot, the signals indicating which parking spaces are available.
17. The system according to claim 15, in, The operation also includes: in response to locating a first parking space indicated in the list, determining whether the located first parking space is indeed available based on sensor data obtained from one or more sensors installed on the autonomous driving vehicle, wherein, if the first parking space is indeed available based on the sensor data, planning the parking path to park the autonomous driving vehicle in the first parking space.
