Embodiments of the subject matter described herein relate generally to vehicle safety systems. More particularly, embodiments of the subject matter relate to a rear cross traffic alert system.
The prior art is replete with onboard vehicle systems that are intended to enhance safety and increase the situational awareness of the driver during various maneuvers. For example, many vehicles are now outfitted with rear vision display systems. A typical rear vision display system includes a dashboard or console mounted video display, which displays a video image feed taken from a camera located at the rear of the vehicle. The video image provides a rearward field of view to the driver that might otherwise be obscured, resulting in enhanced safety before and during back-up maneuvers.
As another example, many vehicles include rear parking assist systems. A typical rear parking assist system utilizes one or more obstacle-detecting sensors mounted at the rear of the vehicle. When the vehicle is in reverse gear, the rear parking assist system will generate alerts (e.g., beeping noises and/or lights) when the sensors detect an obstacle in the rearward path of the vehicle. The alerts can vary in frequency, volume, pattern, etc., in accordance with the detected distance between the rear of the vehicle and the obstacle. The alerts may notify the driver prior to a collision with the detected obstruction.
Some vehicles may also include a rear cross traffic alert (“RCTA”) system. An RCTA system enhances situational awareness by providing an alert when it detects oncoming cross traffic behind the vehicle, where such cross traffic represents a potential hazard when the vehicle is backing up. The RCTA system could also be used to assist the driver in other situations, such as parallel parking.
A method for displaying rear cross traffic alert information on a rear vision display element of a vehicle is provided. The method involves: obtaining sensor data from a rear cross traffic detection system; determining when the sensor data indicates a potential cross traffic collision between the vehicle and a detected object; and, in response to the determining step, displaying a cross traffic warning symbol on the rear vision display element. The cross traffic warning symbol visually indicates the presence of the detected object.
A rear cross traffic alert system for a vehicle is also provided. The system includes a sensing subsystem configured to monitor for cross traffic behind the vehicle. The system also includes a processor architecture that receives sensor data from the sensing subsystem and, when the sensor data indicates a warning condition caused by an object detected by the sensing subsystem, generates image rendering display commands associated with a cross traffic warning symbol. The system also includes a rear vision display element configured to receive the image rendering display commands and, in response thereto, render the cross traffic warning symbol in a manner that visually indicates presence of the object.
A rear vision display element for a vehicle is also provided. The rear vision display element is used to render a rear display having a real-time rearward image corresponding to a rearward view from the vehicle, and having a cross traffic warning symbol superimposed on the real-time rearward image. The cross traffic warning symbol visually indicates the presence of an object behind and to the side of the vehicle.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
A more complete understanding of the subject matter may be derived by referring to the detailed description and claims when considered in conjunction with the following figures, wherein like reference numbers refer to similar elements throughout the figures.
The following detailed description is merely illustrative in nature and is not intended to limit the embodiments of the subject matter or the application and uses of such embodiments. As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Any implementation described herein as exemplary is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description.
Techniques and technologies may be described herein in terms of functional and/or logical block components, and with reference to symbolic representations of operations, processing tasks, and functions that may be performed by various computing components or devices. It should be appreciated that the various block components shown in the figures may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.
For the sake of brevity, conventional techniques related to vehicle-based image capturing and image processing, object detection and sensing, graphics rendering, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in an embodiment of the subject matter.
The techniques and technology described herein relate to an onboard RCTA system for a vehicle. An RCTA system configured as described herein leverages a rear vision display element, and the RCTA system generates and renders graphical rear cross traffic alert symbols on the rear vision display element. In this manner, the RCTA system displays alert symbols in an intuitive and user-friendly location where the driver may already be looking while backing up. Leveraging the rear vision display element in this manner results in component reuse and reduces manufacturing and deployment costs associated with the RCTA system.
In operation, triggering of a rear cross traffic alert results in the presentation of a visual warning symbol on the same display element that is used for the rear vision system. The rear cross traffic alert symbol is rendered in an appropriate location on the rear vision display (e.g., to the left or right side) that indicates the position or approaching path of the detected object. The alert symbol might be chosen such that it graphically indicates a hazard, a vehicle, or a potential collision, and the alert symbol might visually indicate or otherwise be rendered in a manner that indicates the distance between the host vehicle and the approaching vehicle. The alert symbol may have distinctive, variable, or distinguishable visual characteristics that convey the nature of the threat—the visual characteristics may also be rendered with the goal of capturing the driver's attention. Moreover, if combined with a rear vision display having an expansive field of view, the location of the alert symbol on the rear vision display could track the approaching object or indicate the distance to the approaching object in real-time.
Integration of the rear cross traffic alert into a rear vision display image can increase situational awareness of the driver, and can reinforce that the potential threat is located to the rear of the vehicle. Placement of the rear cross traffic alert symbol within the rear vision image can provide directional and/or distance information in a readily absorbed and understood manner. Thus, the driver will be more likely to notice such an alert as it is presented on a display element where he or she may already be looking at the time of the maneuver (e.g., backing up).
Although the following description refers to “cross traffic” that can be detected, the RCTA system can of course sense and detect the presence of other objects, obstacles, or obstructions proximate the host vehicle. For example, the RCTA system could be configured and calibrated to detect the presence of pedestrians, animals, bicycles, and other objects in addition to vehicles, whether moving or stationary.
In addition, although the following description refers to rear cross traffic detection, the concepts, techniques, and technologies can be equivalently deployed in an onboard system that detects front cross traffic. Of course, a front cross traffic detection system would be suitably configured to detect approaching vehicles or objects that are in front of and to the side of the host vehicle (rather than vehicles or objects that are behind and to the side of the host vehicle). Those skilled in the art should understand how to modify the rear cross traffic detection system described herein for use as a front cross traffic detection system.
The RCTA system described here is preferably implemented as an onboard vehicle system. In this regard,
Processor architecture 208 can be implemented and realized using one or more processor components, which may be co-located or distributed throughout the host vehicle. A given processor component may be implemented or performed with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A processor may be realized as a microprocessor, a controller, a microcontroller, or a state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
Processor architecture 208 is suitably configured to receive and process data from various onboard sources, determine when a potential collision or warning condition exists, and generate appropriate image rendering display commands associated with cross traffic warning or alert symbols (as needed). The processor architecture 208 depicted in
Rear vision camera 202 is suitably configured to capture a real-time rearward image that corresponds to a rearward view from the host vehicle. In preferred embodiments, rear vision camera 202 can capture images in a continuous or virtually continuous manner such that RCTA system 200 can render a real-time video feed on rear vision display element 204. Rear vision camera 202 can be located at or near the rear of the host vehicle. For example, rear vision camera 202 may be mounted or integrated into the rear bumper, the rear window assembly, the rear roof structure, or the license plate area of the host vehicle. Image data from rear vision camera 202 can be provided to image processor 208a. In turn, image processor 208a prepares image rendering display commands that are associated with the real-time rearward images. Accordingly, rear vision display element 204 can render the rear vision images (along with superimposed rear cross traffic alert symbols when applicable) in response to the image rendering display commands.
Rear vision display element 204 may be used to display various images and data, in both a graphical and a textual format, and to supply visual feedback to the user. Rear vision display element 204 may be realized using any suitable display technology, such as, without limitation: LCD; OLED; TFT; HUD projection; or any known technology. The specific location, shape, and size of rear vision display element 204 may be selected to accommodate the structural configuration of the host vehicle, user preferences, ergonomic considerations, or the like. For example, rear vision display element 204 might be integrated into or located at: a rearview mirror of the vehicle, a side mirror of the vehicle, a video game unit of the vehicle, an audio/visual entertainment unit of the vehicle, a head-up display of the vehicle, a navigation unit of the vehicle, a dashboard display unit of the vehicle, a visor of the vehicle, a passenger cabin pillar of the vehicle, and/or other locations that are visible to the driver.
Rear cross traffic detection/sensing system 206 is suitably configured to monitor for the presence of cross traffic, obstructions, moving objects, people, etc., which might be located behind and to the sides of the host vehicle. In certain embodiments, rear cross traffic detection/sensing system 206 includes one or more sensors located at or near the rear of the host vehicle. In preferred embodiments, rear cross traffic detection/sensing system 206 includes at least two sensors—one located at or near the left and right rear corners of the host vehicle. These sensor locations allow RCTA system 200 to detect cross traffic approaching from either side of the host vehicle, and the sensors are preferably configured to provide a wide angle detection range. The sensors used by rear cross traffic detection/sensing system 206 may be realized using any appropriate sensor technology. For example, these sensors may be implemented with radar sensors, optical sensors, infrared sensors, sonar sensors, ultrasonic sensors, or the like. During operation, these sensors provide sensor data to rear cross traffic alert processor 208b, where such sensor data conveys or otherwise indicates the presence of an object, the relative direction of the object, and/or the distance to the object. In a basic embodiment, the sensor data may represent a trigger signal that indicates whether or not an object has been detected. In other embodiments, the sensor data could include real-time distance information along with angular information, relative velocity information, etc.
Rear cross traffic alert processor 208b processes the received sensor data (possibly with other data obtained from various onboard sources) to determine whether or not to issue a rear cross traffic warning. For the preferred embodiment described here, rear cross traffic alert processor 208b processes gear status data 214 and vehicle speed data 216 along with the sensor data received from rear cross traffic detection/sensing system 206. Certain embodiments may also be suitably configured to process steering wheel angle and/or yaw angle data to determine the host vehicle path and whether or not the host vehicle path might intersect the path of the approaching object. Gear status data 214 may be provided by an appropriate onboard control module or processing component, such as an engine control module or a transmission control module (not shown). Similarly, vehicle speed data 216 may be provided by an appropriate onboard control module or processing component, such as a brake controller or processor or a traction control module (not shown).
In the context of RCTA system 200, gear status data 214 conveys or indicates whether the host vehicle is currently in a gear that triggers the rear vision image and the rear cross traffic detection/sensing system 206. For example, the rear vision image and rear cross traffic detection/sensing system 206 might be triggered only when the host vehicle is in reverse. Alternatively, they might be triggered when the host vehicle is in reverse or neutral. In other embodiments, they might be triggered when the host vehicle is in any non-forward driving gear.
In the context of RCTA system 200, vehicle speed data 216 conveys or indicates the current speed of the host vehicle (in preferred embodiments, this will be the speed while the host vehicle is in reverse). Rear cross traffic alert processor 208b processes vehicle speed data 216 (in conjunction with the sensor data received from rear cross traffic detection/sensing system 206) to determine whether the current conditions represent an immediate collision risk or potential hazard. For example, if vehicle speed data 216 indicates that the host vehicle is not moving, then it may not be necessary for rear cross traffic alert processor 208b to issue a cross traffic warning. On the other hand, if vehicle speed data 216 indicates that the host vehicle is backing up at a relatively high velocity, then rear cross traffic alert processor 208b will issue a cross traffic warning if it predicts a collision with an oncoming vehicle.
Audio element 210 is suitably configured to generate an audible alert in some embodiments when the sensor data from rear cross traffic detection/sensing system 206 indicates a warning condition associated with detected rear cross traffic. In this regard, audio element 210 may be a speaker or other transducer that generates a distinguishable sound or noise (e.g., a beep or a beeping pattern) in response to the detection of rear cross traffic. Such audible feedback is preferably generated in concert with the display of an appropriate alert symbol on rear vision display element 204.
Haptic feedback element 212 is suitably configured to generate a haptic feedback alert when the sensor data from rear cross traffic detection/sensing system 206 indicates a warning condition associated with detected rear cross traffic. In this regard, haptic feedback element 212 may be a vibration or impact-generating component that is actuated in response to the detection of rear cross traffic. When actuated, haptic feedback element 212 transmits haptic feedback to the driver that indicates the presence of rear cross traffic and, in preferred embodiments, the approaching direction of the cross traffic. For example, if the host vehicle is outfitted with a haptic driver seat, then the left side or left rear corner of the seat will vibrate if RCTA system 200 detects rear cross traffic approaching from the driver side of the host vehicle, and the right side or right rear corner of the seat will vibrate if RCTA system 200 detects rear cross traffic approaching from the passenger side of the host vehicle. Notably, such haptic feedback is preferably generated in concert with the display of an appropriate alert symbol on rear vision display element 204.
Cross traffic warning symbol 304 may include any number of separate graphical elements. The version depicted in
It should be appreciated that the icons, graphical elements, shapes, and sizes used for the cross traffic warning symbols may vary to suit the preferences of the user and/or to suit the needs of the particular deployment. For example, a cross traffic warning symbol may include only one graphical icon, e.g., an arrow, a star, a depiction of a vehicle, or a warning triangle. In certain embodiments, such as that shown in
Rear vision display element 300 may be located in any desired position onboard the host vehicle (as described previously). In this regard,
During operation of the host vehicle, the RCTA system can react and respond to the sensor data obtained from its rear cross traffic detection/sensing system and generate appropriate cross traffic display alerts as needed. In practice, the rear vision display having the features and elements described herein can be generated and dynamically updated and refreshed in real-time (or substantially real-time) during operation of the host vehicle. In this regard,
As described above, preferred embodiments of an RCTA system leverage the functionality of a rear vision display. Accordingly, this embodiment of process 500 determines whether to activate the rear vision display of the host vehicle (query task 502). For query task 502, the RCTA system could monitor a mode indicator, vehicle status data (such as gear status data 214 depicted in
When the rear vision display is activated, process 500 will render a real-time rearward image on the rear vision display (task 504). This rearward image corresponds to a rearward view captured by the rear vision camera located at or near the rear of the host vehicle. In addition, process 500 obtains sensor data from the rear cross traffic detection/sensing system (task 506). The sensor data will be indicative of the presence or absence of an object (or objects) behind and to the side (or sides) of the host vehicle. In certain embodiments, the sensor data conveys or is otherwise indicative of the distance between the host vehicle and the detected object. The received sensor data can be processed and analyzed in an appropriate manner to determine whether or not the sensor data indicates a potential cross traffic collision (or other warning condition or state) between the host vehicle and a detected object (query task 508).
A practical implementation of an RCTA system could analyze and process the sensor data in any number of different ways to determine when a collision might be imminent. For example, query task 508 may trigger an alert whenever an object is detected by the rear cross traffic detection/sensing system. Alternatively, the RCTA system might be designed to process and analyze additional information and/or vehicle status data before triggering an alert. For example, the RCTA system may be suitably configured to determine and analyze any of the following information in connection with the decision made during query task 508: the speed of the approaching object; the speed of the host vehicle; an estimated time-to-collision between the host vehicle and the detected object; an estimated distance-to-collision between the host vehicle and the detected object; or the like. In other words, query task 508 need not automatically trigger a rear cross traffic alert based solely upon the detection of an object behind and on the side of the host vehicle. Rather, the RCTA system could be designed to predict whether or not an actual collision or hazard risk exists and respond accordingly.
If query task 508 detects a rear cross traffic collision risk, then process 500 can generate and display an appropriate cross traffic warning symbol on the rear vision display element of the host vehicle (task 510). As explained above, the cross traffic warning symbol includes one or more graphically rendered icons or elements that visually indicate the presence of the detected object. In preferred embodiments, the cross traffic warning symbol (or symbols) and the rear vision image are rendered together such that the cross traffic warning symbol is superimposed on the rear vision image. Moreover, as described above with reference to
An implementation of the RCTA system could utilize audible and/or haptic feedback in conjunction with the display of a rear cross traffic alert symbol. Accordingly, process 500 may perform an optional task 512 to generate an audible alert when the sensor data indicates a potential cross traffic collision. Additionally (or alternatively), process 500 may perform an optional task 514 to generate a haptic feedback alert when the sensor data indicates a potential cross traffic collision.
Although not required, the RCTA system could be designed to vary one or more visually distinguishable characteristics of the cross traffic warning symbol in a manner that conveys or indicates useful information to the driver. For example, a cross traffic warning symbol can be rendered using visually distinguishable characteristics associated with: a time-to-collision; a distance-to-collision; the potential collision severity; the speed of the approaching vehicle; or the like. The visually distinguishable characteristics can be specified such that the user can quickly and easily interpret the meaning of the displayed cross traffic warning symbol. In practice, the different visually distinguishable characteristics may correspond to any of the following characteristics, individually or in any combination thereof: different colors; different brightness; different transparency levels; different translucency levels; different line patterns; different line thickness; different shapes; different sizes; different display locations; different flicker patterns; different focus levels; different sharpness levels; duty cycle of displayed features; frequency of displayed features; duration of display; different clarity levels; etc.
The control of variable display characteristics may be influenced or dictated by the sensor data provided by the rear cross traffic detection/sensing system and/or other data available to the RCTA system. In this regard, process 500 may process the sensor data (and/or other data) to estimate, calculate, or determine at least one metric that is associated with the detected object, the approaching traffic, the potential collision, or the like (task 516). For example, the metric could be related to a time-to-collision between the vehicle and the detected object, such that task 516 obtains an estimated time. As another example, the metric could be related to a distance-to-collision between the vehicle and the detected object, such that task 516 obtains an estimated distance. As yet another example, the metric could be related to a potential collision severity between the vehicle and the detected object, such that task 516 obtains an estimated severity. These examples are not exhaustive, and the RCTA system could process and handle other metrics as appropriate to the particular embodiment.
This embodiment of process 500 continues by modulating, varying, adjusting, changing, or otherwise controlling at least one visually distinguishable characteristic of the rear cross traffic warning symbol in accordance with the estimated metric (task 518). The manner in which the displayed feature (or features) is modulated can vary from one embodiment to another. For example, the warning symbol could be displayed in a flashing manner when the approaching traffic is relatively far away from the host vehicle, and in a solid or continuous manner when the approaching traffic is relatively close to the host vehicle. As another example, the warning symbol could be rendered in a first color (e.g., yellow) if the estimated time-to-collision is relatively long, and in a second color (e.g., red) if the estimated time-to-collision is relatively short. Of course, any visually distinguishable characteristic of the warning symbol could be gradually or continuously varied to indicate an escalating (or diminishing) threat or warning level.
If it is time to refresh the display (query task 520), then process 500 may lead back to query task 502 to obtain the most current data and update the rear vision display. If not, then the current state of the rear vision display is maintained. The relatively high refresh rate of process 500 results in a relatively seamless and immediate updating of the rear vision display and rear cross traffic alert symbols (if needed).
While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or embodiments described herein are not intended to limit the scope, applicability, or configuration of the claimed subject matter in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the described embodiment or embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope defined by the claims, which includes known equivalents and foreseeable equivalents at the time of filing this patent application.