US20200117925A1

US20200117925A1 - Parking spot identification for vehicle park-assist

Info

Publication number: US20200117925A1
Application number: US16/159,300
Authority: US
Inventors: Markus Krekel; Cinderella Matuk; Ahmed Benmimoun; Lars KUHNERT
Original assignee: Ford Global Technologies LLC
Current assignee: Ford Global Technologies LLC
Priority date: 2018-10-12
Filing date: 2018-10-12
Publication date: 2020-04-16
Anticipated expiration: 2038-10-12
Also published as: DE102019127367A1; CN111047900A; US10628687B1

Abstract

Method and apparatus are disclosed for parking spot identification for vehicle park-assist. An example vehicle includes range-detection sensors, an acceleration sensor, an autonomy unit to perform park-assist, and a controller. The controller is configured to determine, via the acceleration sensor, whether the vehicle is accelerating. The controller also is to, responsive to determining that the vehicle is not accelerating, identify potential parking spots for the park-assist via the range-detection sensors. The controller also is to, responsive to detecting that the vehicle is accelerating, suppress identification of the potential parking spots.

Description

TECHNICAL FIELD

The present disclosure generally relates to park-assist and, more specifically, to parking spot identification for vehicle park-assist.

BACKGROUND

Oftentimes, vehicles include autonomous or semi-autonomous driving systems that enable the vehicles to be driven with reduced driver input. Typically, a vehicle with an autonomous or semi-autonomous driving system includes sensors that collect information of a surrounding environment of the vehicle. In such instances, the autonomous or semi-autonomous driving system performs motive functions (e.g., steering, accelerating, braking, etc.) based on the collected information. Some driving systems utilize information collected from sensors to autonomously or semi-autonomously park a vehicle into an identified parking spot (e.g., a parallel parking spot, a perpendicular parking spot, an angled parking spot).
SUMMARY
The appended claims define this application. The present disclosure summarizes aspects of the embodiments and should not be used to limit the claims. Other implementations are contemplated in accordance with the techniques described herein, as will be apparent to one having ordinary skill in the art upon examination of the following drawings and detailed description, and these implementations are intended to be within the scope of this application.
Example embodiments are shown for parking spot identification for vehicle park-assist. An example disclosed vehicle includes range-detection sensors, an acceleration sensor, an autonomy unit to perform park-assist, and a controller. The controller is configured to determine, via the acceleration sensor, whether the vehicle is accelerating. The controller also is to, responsive to determining that the vehicle is not accelerating, identify potential parking spots for the park-assist via the range-detection sensors. The controller also is to, responsive to detecting that the vehicle is accelerating, suppress identification of the potential parking spots.
In some examples, the acceleration sensor includes a vehicle speed sensor. In some examples, the acceleration sensor includes an accelerator pedal position sensor.
Some examples further include a display to present a representation of a parking spot identified by the controller. In some such examples, the autonomy unit is to perform the park-assist to park the vehicle in the parking spot identified by the controller.
In some examples, the controller is to suppress the identification of the potential parking spots responsive to determining, via the range-detection sensors, that the vehicle is passing or being passed by another vehicle.
In some examples, when the vehicle is in one of a plurality of lanes designated for a same direction-of-travel, the controller is to suppress the identification of potential parallel parking spots along a side of the vehicle while detecting one or more of the plurality of lanes on the side of the vehicle.
Some examples further include a GPS receiver to identify a vehicle location. In such examples, the controller is to determine whether to suppress the identification of the potential parking spots based on the vehicle location. Some such examples further include a communication module to retrieve parking information for the vehicle location. In such examples, the controller is to determine whether to suppress the identification of the potential parking spots for the vehicle location based on the parking information.
In some examples, the controller is to suppress the identification of a potential perpendicular parking spot in front of the vehicle responsive to detecting that the vehicle is located on a road. In some such examples, the controller is to suppress the identification of the potential perpendicular parking spot for remote park-assist.
Some examples further include a steering angle sensor. In such examples, the controller is to suppress the identification of a potential perpendicular parking spot in front of the vehicle upon determining, via the steering angle sensor and the range-detection sensors, that the vehicle is turning away from the potential perpendicular parking spot. In some such examples, the controller is to suppress the identification of the potential perpendicular parking spot based on the steering wheel angle sensor in response to detecting that the vehicle is at least one of within a parking lot and approaching a bend in a road.
In some examples, the controller is to override suppressing the identification of the potential parking spots responsive to determining that a current driving pattern of the vehicle corresponds with a parking lot.
An example disclosed method includes determining whether a vehicle is accelerating via an acceleration sensor. The example disclosed method also includes identifying, via a processor and range-detection sensors, potential parking spots for a park-assist system of the vehicle responsive to determining that the vehicle is not accelerating. The examples disclosed method also includes suppressing, via the processor, identification of the potential parking spots responsive to detecting that the vehicle is accelerating.
An example disclosed vehicle includes range-detection sensors, a human-machine interface (HMI) unit including a display, and a controller. The controller is configured to identify a potential parking spot via the range- detection sensors. The controller also is configured to present, via the display, an interface depicting the potential parking spot and receive, via the HMI unit, a confirmation or a correction from an operator. The example disclosed vehicle also includes an autonomy unit to perform park-assist into the potential parking spot responsive to the controller receiving the confirmation.
In some examples, responsive to receiving the correction, the controller is to determine whether the correction corresponds with another potential parking spot. In some such examples, responsive to the controller determining that the correction corresponds with the other potential parking spot, the autonomy unit is to perform the park-assist into the other potential parking spot. Further, in some such examples, the controller is to store identification of the potential parking spot or the other potential parking spot in a parking map. Moreover, some such examples further include a communication module that is configured to transmit the parking map to a remote server.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the invention, reference may be made to embodiments shown in the following drawings. The components in the drawings are not necessarily to scale and related elements may be omitted, or in some instances proportions may have been exaggerated, so as to emphasize and clearly illustrate the novel features described herein. In addition, system components can be variously arranged, as known in the art. Further, in the drawings, like reference numerals designate corresponding parts throughout the several views.

FIG. 1 illustrates an example vehicle in accordance with the teachings herein.

FIG. 2 is a block diagram of electronic components of the vehicle of FIG. 1.

FIG. 3 depicts an example scenario for a park-assist system of the vehicle of FIG. 1.

FIG. 4 depicts another example scenario for a park-assist system of the vehicle of FIG. 1.

FIG. 5 depicts another example scenario for a park-assist system of the vehicle of FIG. 1.

FIG. 6 depicts another example scenario for a park-assist system of the vehicle of FIG. 1.

FIGS. 7A-7B depict another example scenario for a park-assist system of the vehicle of FIG. 1.

FIG. 8 is a flowchart for identifying parking spots for vehicle park-assist in accordance with the teachings herein.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

While the invention may be embodied in various forms, there are shown in the drawings, and will hereinafter be described, some exemplary and non-limiting embodiments, with the understanding that the present disclosure is to be considered an exemplification of the invention and is not intended to limit the invention to the specific embodiments illustrated.
Oftentimes, vehicles include autonomous or semi-autonomous driving systems that enable the vehicles to be driven with reduced driver input. Typically, a vehicle with an autonomous or semi-autonomous driving system includes sensors that collect information of a surrounding environment of the vehicle. In such instances, the autonomous or semi-autonomous driving system performs motive functions (e.g., steering, accelerating, braking, etc.) based on the collected information. Some driving systems utilize information collected from sensors to autonomously or semi-autonomously park a vehicle into an identified parking spot (e.g., a parallel parking spot, a perpendicular parking spot, an angled parking spot).
Some autonomous parking systems of vehicles identify parking spots without prompting by operators (e.g., drivers) of the vehicles. In some such instances, an autonomous parking system potentially may identify an available parking spot where no parking spot is, in fact, present. In other words, some autonomous parking systems potentially may identify false positives for parking spots. For instance, some false positives potentially may be a result of vehicle sensors (e.g., ultrasonic sensors, radar sensors, lidar sensors, cameras) detecting a constant gap over time between two or more moving objects. Additionally or alternatively, an autonomous parking system potentially may fail to identify an available parking spot where a parking spot is, in fact, present. In other words, some autonomous parking systems potentially may identify false negatives for parking spots.
Example methods and apparatus disclosed herein include a vehicle park-assist system that deters false negatives and false positives when identifying potential available parking spots. Examples disclosed herein include a park-assist system that determines whether to search for available parking spots based on characteristics of a vehicle and/or characteristics of a surrounding environment of the vehicle. If the characteristics correspond with a parking event of the vehicle, the park-assist system enables identification of the potential available parking spots. If the characteristics do not correspond with a parking event of the vehicle, the park-assist system suppresses identification of the potential available parking spots to prevent false positives from being identified. In some examples, the park-assist system simultaneously (1) enables identification of the potential available parking spots in one direction (e.g., to the left) of the vehicle and (2) suppresses identification of the potential available parking spots in another direction (e.g., to the right) of the vehicle. Also, examples disclosed herein include an interface that enables an operator (e.g., a driver) of the vehicle to correct a parking spot identified by a park-assist system, thereby reducing the number of false negatives and false positives for available parking spots.
As used herein, “vehicle park-assist” and “park-assist” refer to a system in which a vehicle controls its motive functions without direct steering or velocity input from a driver to autonomously park within a parking spot. As used herein, “vehicle remote park-assist,” “remote park-assist,” “RePA,” and “remote parking” refer to a system in which a vehicle controls its motive functions without direct steering or velocity input from a driver to autonomously park within a parking spot while the driver is located outside of the vehicle. For example, an autonomy unit of a remote park-assist system controls the motive functions of the vehicle upon receiving a remote initiation signal from a driver.
Turning to the figures, FIG. 1 illustrates an example vehicle 100 in accordance with the teachings herein. The vehicle 100 may be a standard gasoline powered vehicle, a hybrid vehicle, an electric vehicle, a fuel cell vehicle, and/or any other mobility implement type of vehicle. The vehicle 100 includes parts related to mobility, such as a powertrain with an engine, a transmission, a suspension, a driveshaft, and/or wheels, etc. The vehicle 100 may be semi-autonomous (e.g., some routine motive functions controlled by the vehicle 100) or autonomous (e.g., motive functions are controlled by the vehicle 100 without direct driver input).
In the illustrated example, the vehicle 100 includes a steering wheel 102 and an acceleration pedal 104. The steering wheel 102 enables an operator (e.g., a driver) to steer the vehicle 100 for non-autonomous and/or semi-autonomous motive functions. Further, the acceleration pedal 104 enables the vehicle 100 to accelerate the vehicle 100 for non-autonomous and/or semi-autonomous motive functions.
Further, the vehicle 100 of the illustrated example includes a steering wheel angle sensor 106, an acceleration pedal sensor 108, and a vehicle speed sensor 110. The steering wheel angle sensor 106 is configured to detect an angle of the steering wheel 102. For example, the steering wheel angle sensor 106 monitors the steering wheel 102 to detect whether, in which direction, and/or to what degree the operator is turning the steering wheel 102. The acceleration pedal sensor 108 is configured to detect a position and/or angle of the acceleration pedal 104. For example, the acceleration pedal sensor 108 monitors the acceleration pedal 104 to detect (i) whether the operator is engaging the acceleration pedal 104, (ii) to what degree the operator has actuated the acceleration pedal 104, and/or an (iii) acceleration of the vehicle 100 that corresponds with actuation of the acceleration pedal 104. Further, the vehicle speed sensor 110 detects a speed at which the vehicle 100 is travelling along a surface. In some examples, the vehicle speed sensor 110 is configured to detect an acceleration of the vehicle 100 by monitoring a speed of the vehicle 100 over a period of time. That is, the vehicle 100 includes one or more acceleration sensors, such as the acceleration pedal sensor 108 and/or the vehicle speed sensor 110, that are configured to monitor an acceleration of the vehicle 100.
In the illustrated example, the vehicle 100 also includes range-detection sensors. For example, the range-detection sensors enable the vehicle 100 to perform autonomous and/or semi-autonomous driving maneuvers. As used herein, a “range-detection sensor” refers to an electronic device that is configured to collect information to detect a presence of and distance to nearby object(s). In the illustrated example, the range-detection sensors of the vehicle 100 include proximity sensors 112 and cameras 114. The proximity sensors 112 are configured to detect the presence, proximity, and/or location of object(s) near the vehicle 100. For example, the proximity sensors 112 include radar sensor(s), lidar sensor(s), ultrasonic sensor(s), and/or any other sensor configured to detect the presence, proximity, and/or location of nearby object(s). A radar sensor detects and locates an object via radio waves, a lidar sensor detects and locates the object via lasers, and an ultrasonic sensor detects and locates the object via ultrasound waves. Further, the cameras 114 capture image(s) and/or video of a surrounding area of the vehicle 100 to enable nearby object(s) to be identified and located. In the illustrated example, the range-detection sensors (e.g., the proximity sensors 112, the cameras 114) are located on each side of the vehicle 100 (e.g., front, rear, left, right) to enable the range-detection sensors in monitoring each portion of the surrounding area of the vehicle 100. In some examples, the measurements collected by the range-detection sensors over time are utilized to determine a velocity and/or an acceleration of the vehicle 100.
Further, the vehicle 100 of FIG. 1 includes a global positioning system (GPS) receiver 116 and a display 118. The GPS receiver 116 is configured to receive a signal from a global positioning system to identify a location of the vehicle 100. The display 118 is configured to present interface(s) and/or other output information to an occupant of the vehicle 100. For example, the display 118 is a center console display (e.g., a liquid crystal display (LCD), an organic light emitting diode (OLED) display, a flat panel display, a solid state display, etc.) and/or a heads-up display. In some examples, the display 118 is a touchscreen that is configured to collect input information from an occupant.
The vehicle 100 of the illustrated example also includes a communication module 120 that includes wired or wireless network interfaces to enable communication with other devices and/or external networks. The communication module 120 also includes hardware (e.g., processors, memory, storage, antenna, etc.) and software to control the wired or wireless network interfaces. For example, the communication module 120 includes one or more communication controllers for cellular networks, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Code Division Multiple Access (CDMA). In the illustrated example, the communication module 120 includes a wireless personal area network (WPAN) module that is configured to wirelessly communicate with a mobile device (e.g., a key fob, a smart phone, a wearable, a smart watch, a tablet, etc.) of an operator and/or other occupant of the vehicle 100 via short-range wireless communication protocol(s). In some examples, the communication module 120 implements the Bluetooth® and/or Bluetooth® Low Energy (BLE) protocols. The Bluetooth® and BLE protocols are set forth in Volume 6 of the Bluetooth® Specification 4.0 (and subsequent revisions) maintained by the Bluetooth® Special Interest Group. Additionally or alternatively, the communication module 120 is configured to wirelessly communicate via Wi-Fi®, Near Field Communication (NFC), ultra-wide band (UWB) communication, ultra-high frequency (UHF) communication, low frequency (LF) communication, and/or any other communication protocol that enables the communication module 120 to communicatively couple to a mobile device.
In the illustrated example, the vehicle 100 includes an autonomy unit 122. For example, the autonomy unit 122 is an electronic control unit (e.g., one of a plurality of electronic control units 208 of FIG. 2). The autonomy unit 122 is configured to control performance of autonomous and/or semi-autonomous driving maneuvers of the vehicle 100 based upon, at least in part, data collected by the proximity sensors 112, the cameras 114, and/or other range-detection sensors of the vehicle 100. For example, the autonomy unit 122 performs autonomous and/or semi-autonomous driving maneuvers of the vehicle 100 for park-assist.
The vehicle 100 of FIG. 1 also includes a park-assist controller 124 that is configured to control operation of a park-assist system of the vehicle 100. For example, the park-assist controller 124 is configured to collect vehicle data of the vehicle 100. In some examples, the vehicle data includes a speed (e.g., collected via the vehicle speed sensor 110), an acceleration (e.g., collected via an acceleration sensor), a location (e.g., collected via the GPS receiver 116), a direction-of-travel (e.g., determined via the GPS receiver 116), a turn angle (e.g., collected via the steering wheel angle sensor 106), a driving pattern, etc. Further, the park-assist controller 124 is configured to collect data of a surrounding environment of the vehicle 100. In some examples, the environment data include proximity data (e.g., collected via the range-detection sensors) of nearby object(s) and/or location-classification information (e.g., collected via the range-detection sensors, a remote server, etc.). In some examples, the location-classification information identifies (i) a road along which the vehicle 100 is travelling, (ii) how many lanes the road includes, (iii) in which lane of the road the vehicle 100 is travelling, (iv) a width of the lane, (v) whether the road is bending (vi) whether the vehicle 100 is in a construction zone, (vii) whether the vehicle 100 is in a parking lot, (viii) whether the vehicle 100 is in a settlement area, etc.
Based on the collected vehicle data and/or data of the surrounding area, the park-assist controller 124 is configured to determine whether to suppress identification of potential parking spot(s). If the park-assist controller 124 determines to suppress identification of potential parking spot(s), the vehicle 100 does not monitor for potential parking spot(s) and/or present potential parking spot(s) to the operator. If the park-assist controller 124 determines to not suppress identification of potential parking spot(s), the vehicle 100 monitors for potential parking spot(s) based on data collected by the range-detection sensors. For example, if the park-assist controller 124 identifies a potential parking spot, the park-assist controller 124 presents, via the display 118, a representation of the potential parking spot. That is, the display 118 presents an interface depicting the potential parking spot to the operator. Additionally or alternatively, the park-assist controller 124 is configured to instruct the autonomy unit 122 to perform the park-assist motive functions to autonomously and/or semi-autonomously park the vehicle 100 in the parking spot identified by the park-assist controller 124.
FIG. 2 is a block diagram of electronic components 200 of the vehicle 100. As illustrated in FIG. 2, the electronic components 200 include an on-board computing platform 202, a human-machine interface (HMI) unit 204, the communication module 120, the GPS receiver 116, sensors 206, electronic control units (ECUs) 208, and a vehicle data bus 210.
The on-board computing platform 202 includes a processor 212 (also referred to as a microcontroller unit and a controller) and memory 214. In the illustrated example, the processor 212 of the on-board computing platform 202 is structured to include the park-assist controller 124. In other examples, the park-assist controller 124 is incorporated into one of the ECUs 208 with its own processor and memory. The processor 212 may be any suitable processing device or set of processing devices such as, but not limited to, a microprocessor, a microcontroller-based platform, an integrated circuit, one or more field programmable gate arrays (FPGAs), and/or one or more application-specific integrated circuits (ASICs). The memory 214 may be volatile memory (e.g., RAM including non-volatile RAM, magnetic RAM, ferroelectric RAM, etc.), non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, EEPROMs, memristor-based non-volatile solid-state memory, etc.), unalterable memory (e.g., EPROMs), read-only memory, and/or high-capacity storage devices (e.g., hard drives, solid state drives, etc.). In some examples, the memory 214 includes multiple kinds of memory, particularly volatile memory and non-volatile memory.
The memory 214 is computer readable media on which one or more sets of instructions, such as the software for operating the methods of the present disclosure, can be embedded. The instructions may embody one or more of the methods or logic as described herein. For example, the instructions reside completely, or at least partially, within any one or more of the memory 214, the computer readable medium, and/or within the processor 212 during execution of the instructions.
The terms “non-transitory computer-readable medium” and “computer-readable medium” include a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. Further, the terms “non-transitory computer-readable medium” and “computer-readable medium” include any tangible medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a system to perform any one or more of the methods or operations disclosed herein. As used herein, the term “computer readable medium” is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals.
The HMI unit 204 provides an interface between the vehicle 100 and a user. The HMI unit 204 includes digital and/or analog interfaces (e.g., input devices and output devices) to receive input from and display information for the user(s). The input devices include, for example, a cabin microphone 216, other audio input device(s), a control knob, an instrument panel, a digital camera for image capture and/or visual command recognition, a touchscreen (e.g. the display 118), button(s), a touchpad, etc.. The output devices may include the display 118, instrument cluster outputs (e.g., dials, lighting devices), actuators, speakers, etc. In the illustrated example, the HMI unit 204 includes hardware (e.g., a processor or controller, memory, storage, etc.) and software (e.g., an operating system, etc.) for an infotainment system (such as SYNC® and MyFord Touch® by Ford®). Additionally, the HMI unit 204 displays the infotainment system on, for example, the display 118.
The communication module 120 of the illustrated example is configured to communicate with a remote server 218 of an external network 220. For example, the external network 220 is a public network, such as the Internet; a private network, such as an intranet; or combinations thereof. Further, in some examples, the external network 220 utilizes a variety of networking protocols now available or later developed including, but not limited to, TCP/IP-based networking protocols.
The sensors 206 are arranged in and/or around the vehicle 100 to monitor properties of the vehicle 100 and/or an environment in which the vehicle 100 is located. One or more of the sensors 206 may be mounted to measure properties around an exterior of the vehicle 100. Additionally or alternatively, one or more of the sensors 206 may be mounted inside a cabin of the vehicle 100 or in a body of the vehicle 100 (e.g., an engine compartment, wheel wells, etc.) to measure properties in an interior of the vehicle 100. For example, the sensors 206 include accelerometers, odometers, tachometers, pitch and yaw sensors, wheel speed sensors, tire pressure sensors, biometric sensors and/or sensors of any other suitable type. In the illustrated example, the sensors 206 include the acceleration pedal sensor 108, the steering wheel angle sensor 106, the vehicle speed sensor 110, the proximity sensors 112, and the cameras 114.
The ECUs 208 monitor and control the subsystems of the vehicle 100. For example, the ECUs 208 are discrete sets of electronics that include their own circuit(s) (e.g., integrated circuits, microprocessors, memory, storage, etc.) and firmware, sensors, actuators, and/or mounting hardware. The ECUs 208 communicate and exchange information via a vehicle data bus (e.g., the vehicle data bus 210). Additionally, the ECUs 208 may communicate properties (e.g., status of the ECUs 208, sensor readings, control state, error and diagnostic codes, etc.) to and/or receive requests from each other. For example, the vehicle 100 may have dozens of the ECUs 208 that are positioned in various locations around the vehicle 100 and are communicatively coupled by the vehicle data bus 210.
In the illustrated example, the ECUs 208 include the autonomy unit 122, a speed control unit 222, a camera module 224, and a steering angle sensor module 226. For example, the autonomy unit 122 is configured to control performance of autonomous and/or semi-autonomous driving maneuvers of the vehicle 100. The speed control unit 222 is configured to monitor and/or control a speed at which the vehicle 100 travels. The camera module 224 controls one or more cameras 114 to collect image(s) and/or video, for example, that are presented to occupant(s) of the vehicle 100 via the display 118 and/or analyzed to control performance of autonomous and/or semi-autonomous driving maneuvers of the vehicle 100. Further, the steering angle sensor module 226 includes and/or is communicatively coupled to the steering wheel angle sensor 106 to monitor a steering angle of the steering wheel 102.
The vehicle data bus 210 communicatively couples the GPS receiver 116, the communication module 120, the on-board computing platform 202, the HMI unit 204, the sensors 206, and the ECUs 208. In some examples, the vehicle data bus 210 includes one or more data buses. The vehicle data bus 210 may be implemented in accordance with a controller area network (CAN) bus protocol as defined by International Standards Organization (ISO) 11898-1, a Media Oriented Systems Transport (MOST) bus protocol, a CAN flexible data (CAN-FD) bus protocol (ISO 11898-7) and/a K-line bus protocol (ISO 9141 and ISO 14230-1), and/or an Ethernet™ bus protocol IEEE 802.3 (2002 onwards), etc.
FIG. 3 depicts an example scenario for a park-assist system of the vehicle 100. In the illustrated example, the vehicle 100 is travelling along a road 300. The road 300 is a multi-lane road that includes a plurality of lanes designated for a same direction-of-travel. For example, the road 300 includes a lane 302 (e.g., an outer lane), a lane 304 (e.g., an inner lane), and a lane 306 (e.g., an outer lane) that are each designated for the same direction-of-travel. As illustrated in FIG. 3, the road 300 includes (1) outer lines 308 (e.g., solid lines) that define the outer limits of the road and (2) inner lines 310 (e.g., dashed lines) that separate the lanes 302, 304, 306 from each other.
In FIG. 3, the vehicle 100 is approaching a sign 312 located along the side of the road 300. For example, the sign 312 identifies that the vehicle 100 is within and/or is approaching a construction zone. Further, the vehicle 100 is proximate to a plurality of other vehicles 314 positioned on and/or along the road 300. For example, a vehicle 314 a, a vehicle 314 b, and a vehicle 316 c are parked (e.g., parallel parked) along a side of the road 300 adjacent to the vehicle 100. The vehicle 100 is travelling within the lane 302 of the road 300. A vehicle 314 d, a vehicle 314 e, and a vehicle 314 f are travelling within the lane 304 adjacent to the vehicle 100. Further, the vehicle 314 g is travelling within the lane 306 of the road 300.
The park-assist controller 124 of the vehicle 100 determines whether to suppress identification of potential parking spot(s) based on collected vehicle data and/or environmental data. In the illustrated example, the park-assist controller 124 of the vehicle 100 determines whether to suppress identification of a potential spot 316 (e.g., a potential parallel spot to the left of the vehicle 100), a potential spot 318 (e.g., a potential perpendicular spot in front of the vehicle 100), and/or a potential spot 320 (e.g., a potential perpendicular spot to the right of the vehicle 100).
In the illustrated example, the park-assist controller 124 is configured to determine whether to suppress identification of potential parking spot(s) based on an acceleration of the vehicle 100. For example, the park-assist controller 124 determines whether the vehicle 100 is accelerating via an acceleration sensor, such as the acceleration pedal sensor 108, the vehicle speed sensor 110, the proximity sensors 112, and/or the cameras 114. In response to the park-assist controller 124 determining that the vehicle 100 is accelerating, the park-assist controller 124 suppresses identification of potential parking spot(s) near the vehicle 100. In some examples, in response to the park-assist controller 124 determining that the vehicle 100 is not accelerating (e.g., is decelerating or is travelling at a constant speed), the park-assist controller 124 enables identification potential parking spot(s) (e.g., the potential spot 316). For example, the park-assist controller 124 enables identification of potential parking spot(s) 100 via the range-detection sensors (e.g., the proximity sensors 112, the cameras 114) of the vehicle 100.
Further, the park-assist controller 124 of the vehicle 100 is configured to determine whether to suppress identification of potential parking spot(s) based on an acceleration of the vehicle 100 relative to one or more of the other vehicles 314 that are travelling on the road 300 with the vehicle 100. In the illustrated example, the park-assist controller 124 suppresses identification of potential parking spot(s) near the vehicle 100 in response to detecting that the vehicle 100 is passing or being passed by one or more of the other vehicles 314 on the road 300. For example, the park-assist controller 124 determines, via the range-detection sensors, whether the vehicle 100 is passing and/or is being passed by one or more of the other vehicles 314 on the road 300. In some examples, in response to detecting that the that the vehicle 100 is passing or being passed by one or more of the other vehicles 314 on the road 300, the park-assist controller 124 enables identification of potential parking spot(s) via the range-detection sensors.
In some examples, the park-assist controller 124 of the vehicle 100 is configured to determine whether to suppress identification of potential parking spot(s) based on a vehicle location. For example, the park-assist controller 124 suppresses identification of potential parking spot(s) when the vehicle 100 is at a location at which no parking spots are available. The park-assist controller 124 is configured to suppress identification of potential parking spot(s) upon determining that the vehicle 100 is in a construction zone, a settlement area, and/or any other location at which parking spots are unavailable. In some examples, the park-assist controller 124 determines that the vehicle 100 is in an area in which parking spots are unavailable based on the range-detection sensors. For example, the park-assist controller 124 utilizes image-recognition software to detect that the vehicle 100 is within and/or approaching a construction zone based on image(s) and/or video of the sign 312 that are captured by one or more of the cameras 114. Further, in some examples, the park-assist controller 124 is configured to determine the vehicle 100 is in an area in which parking spots are unavailable based on parking information for the location of the vehicle 100. For example, the park-assist controller 124 is configured to (1) identify the vehicle location via the GPS receiver 116 and (2) retrieve parking information for the vehicle location from a remote server (e.g., the remote server 218) via the communication module 120.
Further, the park-assist controller 124 of the vehicle 100 of the illustrated example is configured to override suppression of the identification of the potential parking spots based on a vehicle location. For example, the park-assist controller 124 overrides suppressing the identification of the potential parking spots in response to determining that the current vehicle location corresponds with a parking lot (e.g., a permanent parking lot such as a parking structure, a temporary parking lot such as a field). In some examples, the park-assist controller 124 is configured to determine that the vehicle 100 is located in a parking lot based on information collected via the range-detection sensors and/or the GPS receiver 116. Further, the park-assist controller 124 is configured to determine that the vehicle 100 is located in a parking lot by monitoring a current driving pattern of the vehicle 100. For example, the park-assist controller 124 determines that the vehicle 100 is in a parking lot upon detecting a series of driving maneuvers (e.g., quick turns, short forward motions) associated with a vehicle driving through a parking lot.
Additionally or alternatively, the park-assist controller 124 of the vehicle 100 is configured to determine whether to suppress identification of potential parking spot(s) based on a location of the vehicle 100 within the road 300. For example, the park-assist controller 124 is configured to suppress identification of a potential parking spot in front of the vehicle 100, such as the potential spot 318, in response to detecting that the vehicle 100 is travelling in a lane (e.g., the lane 302) of the road 300. When the vehicle 100 is travelling in one of a plurality of lanes of a road designated for a same direction-of-travel, the park-assist controller 124 suppresses identification of parallel parking spots along a side of the vehicle 100 while detecting (e.g., via the range-detection sensors) that one or more other lanes of the road is on that side of the vehicle 100. For example, when the vehicle 100 is travelling in the lane 302 of the road 300, the park-assist controller 124 suppresses identification of parallel parking spots to the right of the vehicle 100 such as the potential spot 320. In some examples, park-assist controller 124 enables identification of parallel parking spots along a side of the vehicle 100 while detecting (e.g., via the range-detection sensors) that no other lane of the road is on that side of the vehicle 100. For example, when the vehicle 100 is travelling in the lane 302 of the road 300, the park-assist controller 124 enables identification of parallel parking spots to the left of the vehicle 100 such as the potential spot 316. That is, in some examples, the park-assist controller 124 enables identification of potential parking spots in some direction(s) (e.g., to the left) and suppresses identification of potential parking spots in other direction(s) (e.g., to the right, in the front).
Further, in some examples, the park-assist controller 124 (1) suppresses identification of potential parking spot(s) when one or more of a plurality of conditions is not met and (2) enables identification of potential parking spot(s) when each of the plurality of conditions is met. For example, the park-assist controller 124 is configured to suppress identification when the vehicle 100 is (1) accelerating, (2) passing another vehicle, (3) being passed by another vehicle, (4) in a construction zone, (5) in a settlement area, and/or (6) in a middle lane. In such examples the park-assist controller 124 is configured to enable identification when the vehicle 100 is not (1) accelerating, (2) passing another vehicle, (3) being passed by another vehicle, (4) in a construction zone, (5) in a settlement area, and (6) in a middle lane.
FIG. 4 depicts another example scenario for the park-assist system of the vehicle 100. In the illustrated example, the vehicle 100 is travelling along a road 400. As illustrated in FIG. 4, the road 400 is a single-lane road that includes lines 402 (e.g., solid lines) to define the outer limits of the road 400. Further, in the illustrated example, the vehicle 100 is proximate to a plurality of other vehicles 404 parked along sides of the road 400. For example, a vehicle 404 a is parked along a left side of the road 400, and a vehicle 404 b and a vehicle 404 c are parked along a right side of the road 400.
In the illustrated example, the park-assist controller 124 of the vehicle 100 is configured to determine whether to suppress identification of potential parking spot(s) based on a location of the vehicle 100 relative to the road 400. For example, upon detecting (e.g., via the range-detection sensors and/or the GPS receiver 116) that the vehicle 100 is located on the road 400, the park-assist controller suppresses identification of a potential spot 406 in front of the vehicle 100. That is, the park-assist controller 124 is configured to suppress identification of potential parking spot(s) that are located on the road 400. Additionally or alternatively, to prevent identification of potential parking spot(s) located on the road 400, the park-assist controller 124 is configured to suppress identification of potential perpendicular parking spot(s) (e.g., the potential spot 406) for remote park-assist that is in front of the vehicle 100 and/or when the vehicle 100 is located in the road. Further, in the illustrated example, the park-assist controller 124 enables identification of a potential spot 408 that is located along a side of the road 400 (e.g., to the left of the vehicle 100).
FIG. 5 depicts another example scenario for the park-assist system of the vehicle 100. In the illustrated example, the vehicle 100 is travelling along a road 500. The road 500 is a multi-lane road that includes a plurality of lanes designated for a same direction-of-travel. For example, the road 500 includes a lane 502 (e.g., an outer lane), a lane 504 (e.g., an inner lane), and a lane 506 (e.g., an outer lane) that are each designated for the same direction-of-travel. As illustrated in FIG. 5, the road 500 is approaching an intersection with a traffic light 508. Further, the vehicle 100 is proximate to a plurality of other vehicles 510 positioned on the road 500. For example, a vehicle 510 a and a vehicle 510 b are located within the lane 502, a vehicle 510 c is located within the lane 504, and a vehicle 510 d and a vehicle 510 e are located within the lane 506. The other vehicles 510 are stopped at the intersection based on a status of the traffic light 508 (e.g., a red light is illuminated). The vehicle 100 is approaching the other vehicles 510 that are in the road 500 and stopped at the intersection.
In the illustrated example, the park-assist controller 124 of the vehicle 100 is configured to determine whether to suppress identification of potential parking spot(s) based on a location of the vehicle 100 relative to the road 500 and/or the other vehicles 510. For example, upon detecting (e.g., via the range-detection sensors and/or the GPS receiver 116) that the vehicle 100 is located in the lane 504 of the road 500, the park-assist controller suppresses identification of a potential spot 512 that is in front of the vehicle 100 and between the other vehicles 510. That is, the park-assist controller 124 is configured to suppress identification of potential parking spot(s) located on the road 500.
FIG. 6 depicts another example scenario for the park-assist system of the vehicle 100. In the illustrated example, the vehicle 100 is travelling along a road 600. Further, the vehicle 100 is approaching a turn or bend 602 in the road 600. Objects 604 (e.g., trees, bushes, rocks, road barriers, signs, support posts, etc.) are located to a side of the bend 602 of the road 600 such that the objects 604 are in front of the vehicle 100 as the vehicle 100 approaches the bend. In the illustrated example, an object 604 a and an object 604 b are positioned such that there is a gap between the object 604 a and the object 604 b that corresponds with a size of a potential spot 606 (e.g., a potential perpendicular parking spot). Further, the object 604 a and the object 604 b are located relative to the bend 602 in the road 600 such that the potential spot 606 is in front of the vehicle 100 as the vehicle 100 approaches the bend 602.
The park-assist controller 124 of the vehicle 100 of the illustrated example is configured to determine whether to suppress identification of a potential perpendicular parking spot (e.g., the potential spot 606) in front of the vehicle 100 based on a steering path of the vehicle 100. For example, the park-assist controller 124 of the vehicle 100 is configured to determine whether to suppress identification of a potential perpendicular parking spot in front of the vehicle 100 based on an angle of the steering wheel 102 that is detected via the steering wheel angle sensor 106. In the illustrated example, the park-assist controller 124 of the vehicle 100 suppresses identification of the potential spot 606 in response to determining, via the steering wheel angle sensor 106 and/or the range-detection sensors, that the vehicle 100 is turning away from the potential spot 606.
In the illustrated example, the park-assist controller 124 of the vehicle 100 determines whether to suppress identification of a potential perpendicular parking spot (e.g., the potential spot 606) based on the steering wheel angle sensor 106 upon detecting (e.g., via the range-detection sensors and/or the GPS receiver 116) that the vehicle 100 is approaching a bend in a road (e.g., the bend 602 in the road 600). Additionally or alternatively, the park-assist controller 124 determines whether to suppress identification of a potential perpendicular parking spot based on the steering wheel angle sensor 106 upon detecting other characteristics of the surrounding area. For example, the park-assist controller 124 determines whether to suppress identification of a potential perpendicular parking spot based on the steering wheel angle sensor 106 upon detecting that the vehicle 100 is in a parking lot.
FIGS. 7A-7B depict another example scenario for the park-assist system of the vehicle 100. More specifically, FIG. 7A depicts when the park-assist controller 124 of the vehicle 100 has incorrectly identified a potential parking spot, and FIG. 7B depicts when the park-assist controller 124 of the vehicle 100 has correctly identified potential parking spots.
In the illustrated example, the vehicle 100 is travelling along a road 700. Parking spots 702 (e.g., perpendicular parking spots) are located along a side of the road 700. Other vehicles 704 are located in some of the parking spots 702. Others of the parking spots 702 are unoccupied. For example, a parking spot 702 a and a parking spot 702 b are unoccupied. Further, the parking spot 702 a and the parking spot 702 b are located next to each other between a vehicle 704 a and a vehicle 704 b. As illustrated in FIGS. 7A-7B, the vehicle 100 is located near the parking spot 702 a and the parking spot 702 b that are unoccupied.
In operation, the park-assist controller 124 of the vehicle 100 is configured to identify a potential parking spot via the range-detection sensors (e.g., the proximity sensors 112, the cameras 114) of the vehicle 100. For example, in FIG. 7A, the park-assist controller 124 identifies a potential parking spot 706, via the range-detection sensors, based on a distance between the vehicle 704 a and the vehicle 704 b. Further, the park-assist controller 124 presents an interface to an operator (e.g., a driver) of the vehicle 100 that depicts the potential parking spot 706. For example, the park-assist controller 124 presents an interface to the operator via the display 118 of the vehicle 100. The interface presented to the operator includes a representation of the potential parking spot 706 relative to the location of the vehicle 100 and/or other nearby objects such as the vehicles 704 a, 704 b.
Further, the park-assist controller 124 of the vehicle 100 of the illustrated example is configured to receive a confirmation or a correction of the potential parking spot 706 from the operator. For example, the operator is to review the interface presented via the display 118 to determine whether the park-assist controller 124 has correctly identified a potential parking spot. That is, the operator reviews the interface presented via the display 118 to determine whether the potential parking spot 706 corresponds with one of the parking spot 702. After determining whether the potential parking spot 706 is correct or incorrect, the operator is to provide feedback to the park-assist controller 124. That is, the park-assist controller 124 is configured to receive a confirmation and/or a correction of the potential parking spot 706 from the operator via the HMI unit 204. A correction identifies that a potential parking spot does not correspond with an actual parking spot. In some examples, the correction provided by the operator includes a repositioning and/or reorientation of a potential parking spot such that potential parking spot corresponds with an actual parking spot. Further, in some examples, a touchscreen (e.g., the display 118) of the HMI unit 204 is configured to receive a tactile selection from the operator and/or the cabin microphone 216 of the HMI unit 204 is configured to receive an audio selection from the operator.
In FIG. 7A, the potential parking spot 706 identified by the park-assist controller 124 is incorrect. In response to receiving a correction from the operator of the vehicle 100, the park-assist controller 124 is configured to determine whether the correction corresponds with another potential parking spot. For example, if the correction includes a repositioning and/or reorientation of the potential parking spot 706, the park-assist controller 124 determines whether the adjustment of the potential parking spot 706 provided by the operator in the correction corresponds with another potential parking spot.
FIG. 7B illustrates the example park-assist scenario after the park-assist controller 124 has received the correction from the operator. As illustrated in FIG. 7B, the park-assist controller 124 has identified a potential parking spot 708 and a potential parking spot 710 based on the correction provided by the operator. Upon identifying the potential parking spots 708, 710, the park-assist controller 124 presents an interface to the operator that depicts the potential parking spots 708, 710. For example, the park-assist controller 124 presents an interface to the operator via the display 118 of the vehicle 100. The interface presented to the operator includes a representation of the potential parking spots 708, 710 relative to the location of the vehicle 100 and/or other nearby objects such as the vehicles 704 a, 704 b. Further, the park-assist controller 124 of the vehicle 100 is configured to receive a confirmation or a correction of the potential parking spot 708 and/or the potential parking spot 710 from the operator.
In FIG. 7B, the potential parking spot 708 matches, aligns with, and/or otherwise corresponds with the parking spot 702 a. Further, the potential parking spot 710 matches, aligns with, and/or otherwise corresponds with the parking spot 702 b. Upon receiving a confirmation from the operator, the park-assist controller 124 is configured to instruct the autonomy unit 122 to perform park-assist motive function(s) into one of the potential parking spots 708, 710 that align with a respective one of the parking spots 702 a, 702 b. That is, the autonomy unit 122 is configured to perform park-assist into a potential parking spot responsive to the park-assist controller 124 receiving a confirmation from the operator. Additionally or alternatively, the autonomy unit 122 is configured to perform park-assist into a potential parking spot responsive to the park-assist controller 124 determining that a correction received from the operator corresponds with another potential parking spot (e.g., the potential parking spot 708, the potential parking spot 710).
In the illustrated example, the park-assist controller 124 is configured to store identification of potential parking spot(s) (e.g., the potential parking spot 706, the potential parking spot 708, the potential parking spot 710) and/or their corresponding classification (e.g., correct, incorrect) in parking map to facilitate identification of potential parking spot(s) in the future. In some examples, the park-assist controller 124 stores the parking map onboard the vehicle 100 in the memory 214. Additionally or alternatively, the park-assist controller 124 stores the information remotely (e.g., at the remote server 218). For example, the park-assist controller 124 transmits the parking map to the remote server 218 via the communication module 120. In some examples, the park-assist controller 124 stores the parking map remotely to enable other vehicles to access the parking map to facilitate those vehicles in identifying potential parking spot(s) in the future.
FIG. 8 is a flowchart of an example method 800 to identify parking spots for vehicle park-assist. The flowchart of FIG. 8 is representative of machine readable instructions that are stored in memory (such as the memory 214 of FIG. 2) and include one or more programs which, when executed by a processor (such as the processor 212 of FIG. 2), cause the vehicle 100 to implement the example park-assist controller 124 of FIGS. 1 and 2. While the example program is described with reference to the flowchart illustrated in FIG. 8, many other methods of implementing the example park-assist controller 124 may alternatively be used. For example, the order of execution of the blocks may be rearranged, changed, eliminated, and/or combined to perform the method 800. Further, because the method 800 is disclosed in connection with the components of FIGS. 1-2, some functions of those components will not be described in detail below.
Initially, at block 802, the park-assist controller 124 collects vehicle data of the vehicle 100. For example, the park-assist controller 124 collects a speed (e.g., via the vehicle speed sensor 110), an acceleration (e.g., via the vehicle speed sensor 110, the acceleration pedal sensor 108), a location (e.g., via the GPS receiver 116), a direction-of-travel (e.g., via the GPS receiver 116), a turn angle (e.g., via the steering wheel angle sensor 106), a driving pattern, etc. of the vehicle 100. At block 804, the park-assist controller 124 collects data of a surrounding area of the vehicle 100. For example, the park-assist controller 124 collects proximity data (e.g., via the range-detection sensors) of nearby object(s) and/or location-classification information (e.g., via the range-detection sensors, the remote server 218). For example, the location-classification information identifies (i) on which road the vehicle 100 is travelling, (ii) how many lanes the road includes, (iii) in which lane of the road the vehicle 100 is travelling, (iv) a width of the lane, (v) whether the road is bending, (vi) whether the vehicle 100 is in a construction zone, (vii) whether the vehicle 100 is in a parking lot, (viii) whether the vehicle 100 is in a settlement area, etc.
At block 806, the park-assist controller 124 determines whether to suppress identification of potential parking spot(s) along the left side of the vehicle 100, for example, based on the collected vehicle data and/or data of the surrounding area. In response to the park-assist controller 124 determining to suppress the identification of potential parking spot(s) to the left of the vehicle 100, the method 800 proceeds to block 810. Otherwise, in response to the park-assist controller 124 determining not to suppress the identification of potential parking spot(s) to the left of the vehicle 100, the method 800 proceeds to block 808 at which the park-assist controller 124 monitors for potential parking spot(s) (e.g., parallel spots, perpendicular spots, angled spots) along the left side of the vehicle 100 (e.g., via the range-detection sensors).
At block 810, the park-assist controller 124 determines whether to suppress identification of potential parking spot(s) along the right side of the vehicle 100, for example, based on the collected vehicle data and/or data of the surrounding area. In response to the park-assist controller 124 determining to suppress the identification of potential parking spot(s) to the right of the vehicle 100, the method 800 proceeds to block 814. Otherwise, in response to the park-assist controller 124 determining not to suppress the identification of potential parking spot(s) to the right of the vehicle 100, the method 800 proceeds to block 812 at which the park-assist controller 124 monitors for potential parking spot(s) (e.g., parallel spots, perpendicular spots, angled spots) along the right side of the vehicle 100 (e.g., via the range-detection sensors).
At block 814, the park-assist controller 124 determines whether to suppress identification of potential parking spot(s) in front of and/or behind the vehicle 100, for example, based on the collected vehicle data and/or data of the surrounding area. In response to the park-assist controller 124 determining to suppress the identification of potential parking spot(s) in front of and/or behind the vehicle 100, the method 800 proceeds to block 818. Otherwise, in response to the park-assist controller 124 determining not to suppress the identification of potential parking spot(s) in front of and/or behind the vehicle 100, the method 800 proceeds to block 816 at which the park-assist controller 124 monitors for potential parking spot(s) (e.g., perpendicular spots, angled spots) in front of and/or behind the vehicle 100 (e.g., via the range-detection sensors).
At block 818, the park-assist controller 124 determines whether it has identified any potential parking spot(s) at blocks 808, 812, 816. In response to the park-assist controller 124 not identifying a potential parking spot, the method 800 returns to block 802. Otherwise, in response to the park-assist controller identifying potential parking spot(s), the method 800 proceeds to block 820.
At block 820, the park-assist controller 124 presents a representation of one or more of the potential parking spot(s) to an operator via the display 118 of the vehicle 100. At block 822, the HMI unit 204 of the vehicle 100 receives a selection from the operator of one of the potential parking spot(s). For example, the HMI unit 204 collects the selection from the operator as a tactile input (e.g., via a button, a dial, a touchscreen such as the display 118, etc.) and/or an audio input (e.g., via the cabin microphone 216, etc.).
At block 822, the park-assist controller 124 determines whether the potential parking spot has been confirmed or corrected by the operator. For example, the HMI unit 204 receives a confirmation input from the operator upon the operator confirming that the potential parking spot, as represented via the display 118, matches an actual parking spot viewed by the operator. The HMI unit 204 receives a correction input from the operator to inform the park-assist controller 124 that the potential parking spot, as represented via the display 118, does not match an actual parking spot viewed by the operator. In some examples, the correction input includes a readjustment of the potential parking spot such that the potential parking spot, as represented via the display 118, now matches an actual parking spot viewed by the operator.
In response to the park-assist controller 124 determining that the potential parking has been confirmed by the operator, the method 800 proceeds to block 826 at which the autonomy unit 122 performs park-assist motive functions to park the vehicle 100 in the identified parking spot. Otherwise, in response to the park-assist controller 124 determining that the potential parking has been corrected by the operator, the method 800 proceeds to block 828 at which the park-assist controller 124 determines whether it identifies another parking spot based on the correction. In response to the park-assist controller 124 not identifying another parking spot based on the correction, the method 800 returns to block 802. Otherwise, in response to the park-assist controller 124 identifying another parking spot based on the correction, the method 800 proceeds to block 826 at which the autonomy unit 122 parks the vehicle 100 in the identified parking spot. At block 830, the park-assist controller stores information of the identified parking spot in a parking map (e.g., in the memory 214 onboard the vehicle 100, in the remote server 218, etc.).
In this application, the use of the disjunctive is intended to include the conjunctive. The use of definite or indefinite articles is not intended to indicate cardinality. In particular, a reference to “the” object or “a” and “an” object is intended to denote also one of a possible plurality of such objects. Further, the conjunction “or” may be used to convey features that are simultaneously present instead of mutually exclusive alternatives. In other words, the conjunction “or” should be understood to include “and/or”. The terms “includes,” “including,” and “include” are inclusive and have the same scope as “comprises,” “comprising,” and “comprise” respectively. Additionally, as used herein, the terms “module” and “unit” refer to hardware with circuitry to provide communication, control and/or monitoring capabilities. A “module” and a “unit” may also include firmware that executes on the circuitry.
The above-described embodiments, and particularly any “preferred” embodiments, are possible examples of implementations and merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) without substantially departing from the spirit and principles of the techniques described herein. All modifications are intended to be included herein within the scope of this disclosure and protected by the following claims.

Claims

1. A vehicle comprising:

range-detection sensors;

an acceleration sensor;

an autonomy unit to perform park-assist; and

a controller configured to:

determine, via the acceleration sensor, whether the vehicle is accelerating;

responsive to determining that the vehicle is not accelerating, identify potential parking spots for the park-assist via the range-detection sensors; and

responsive to detecting that the vehicle is accelerating, suppress identification of the potential parking spots,

wherein, when the vehicle is in one of a plurality of lanes designated for a same direction-of-travel, the controller is configured to suppress the identification of potential parallel parking spots along a side of the vehicle while detecting one or more of the plurality of lanes on the side of the vehicle.

2. The vehicle of claim 1, wherein the acceleration sensor includes a vehicle speed sensor.

3. The vehicle of claim 1, wherein the acceleration sensor includes an accelerator pedal position sensor.

4. The vehicle of claim 1, further including a display to present a representation of a parking spot identified by the controller.

5. The vehicle of claim 4, wherein the autonomy unit is to perform the park-assist to park the vehicle in the parking spot identified by the controller.

6. The vehicle of claim 1, wherein the controller is configured to suppress the identification of the potential parking spots responsive to determining, via the range-detection sensors, that the vehicle is passing or being passed by another vehicle.

7. (canceled)

8. The vehicle of claim 1, further including a GPS receiver to identify a vehicle location, wherein the controller is configured to determine whether to suppress the identification of the potential parking spots based on the vehicle location.

9. The vehicle of claim 8, further including a communication module to retrieve parking information for the vehicle location, wherein the controller is configured to determine whether to suppress the identification of the potential parking spots for the vehicle location based on the parking information.

10. The vehicle of claim 1, wherein the controller is configured to suppress the identification of a potential perpendicular parking spot in front of the vehicle responsive to detecting that the vehicle is located on a road.

11. The vehicle of claim 10, wherein the controller is configured to suppress the identification of the potential perpendicular parking spot for remote park-assist.

12. The vehicle of claim 1, further including a steering wheel angle sensor, wherein the controller is configured to suppress the identification of a potential perpendicular parking spot in front of the vehicle upon determining, via the steering wheel angle sensor and the range-detection sensors, that the vehicle is turning away from the potential perpendicular parking spot.

13. The vehicle of claim 12, wherein the controller is configured to suppress the identification of the potential perpendicular parking spot based on the steering wheel angle sensor in response to detecting that the vehicle is at least one of within a parking lot and approaching a bend in a road.

14. The vehicle of claim 1, wherein the controller is configured to override suppressing the identification of the potential parking spots responsive to determining that a current driving pattern of the vehicle corresponds with a parking lot.

15-20. (Canceled)

21. A vehicle comprising:

range-detection sensors;

an acceleration sensor;

an autonomy unit to perform park-assist; and

a controller configured to:

determine, via the acceleration sensor, whether the vehicle is accelerating;

responsive to determining that the vehicle is not accelerating, identify potential parking spots for the park-assist via the range-detection sensors;

responsive to detecting that the vehicle is accelerating, suppress identification of the potential parking spots; and

responsive to detecting that the vehicle is located on a road, suppress the identification of a potential perpendicular parking spot in front of the vehicle.

22. A vehicle comprising:

range-detection sensors;

an acceleration sensor;

an autonomy unit to perform park-assist;

a steering wheel angle sensor; and

a controller configured to:

determine, via the acceleration sensor, whether the vehicle is accelerating;

suppress the identification of a potential perpendicular parking spot in front of the vehicle upon determining, via the steering wheel angle sensor and the range-detection sensors, that the vehicle is turning away from the potential perpendicular parking spot.

23. A vehicle comprising:

range-detection sensors;

an acceleration sensor;

an autonomy unit to perform park-assist; and

a controller configured to:

determine, via the acceleration sensor, whether the vehicle is accelerating;

responsive to determining that a current driving pattern of the vehicle corresponds with a parking lot, override suppressing the identification of the potential parking spots.