The present disclosure relates to methods and systems for blind spot monitoring in a vehicle and, more particularly, blind sport monitoring that utilizes an adaptive alert zone.
This section provides background information related to the present disclosure, which is not necessarily prior art.
Although systems exist to help a driver of a vehicle locate objects, such as other vehicles, in a blind spot of the vehicle, and to generally assist with collision avoidance, such systems are subject to improvement. The present teachings advantageously provide systems and methods for blind spot monitoring and informing a driver that an object, such as another vehicle, is in a blind spot of the vehicle. The present teachings provide for improved collision avoidance systems and methods as well.
This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features.
The present teachings include systems and methods with a blind spot monitoring system including a blind spot sensor that monitors a blind spot alert area of a subject vehicle and that generates an alert when a secondary vehicle is detected within the blind spot alert area of the subject vehicle. An object detection system detects an adjacent vehicle traveling in an adjacent lane to the subject vehicle. A controller determines whether the subject vehicle has passed the adjacent vehicle and that expands the blind spot alert area in response to determining that the subject vehicle has passed the adjacent vehicle.
Further areas of applicability will become apparent from the description provided herein. The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
The drawings described herein are for illustrative purposes only of select embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.
Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings.
Example embodiments will now be described more fully with reference to the accompanying drawings.
With reference to
The blind spot sensors 20 include one or more sensors configured to identify objects, such as other vehicles, in a blind spot alert area of the subject vehicle 10. The blind spot sensors 20 can include any suitable sensors, such as any suitable radar, camera, ultrasonic, or other suitable sensors for detecting objects in a blind spot alert area of the subject vehicle 10. The blind spot sensors 20 can be mounted at any suitable position on the vehicle 10, such as near the back corners of the subject vehicle 10 or along the sides of the subject vehicle 10.
With reference to
For example, with reference to
With reference to
In addition to, or as an alternative to, the TSR system 32, the system 12 can use the GPS 28 to determine an upcoming traffic merge. For example, the system 12 can analyze GPS map and traffic data and a current location and trajectory path of the subject vehicle 10 and determine that the current lane of the subject vehicle 10 is about to merge with another lane, such as a highway lane.
With reference to
In addition, with reference to
With reference to
Additionally, the driver alert system 22 can alert the driver of the subject vehicle 10 to a location of the secondary vehicle 48, relative to the subject vehicle 10. For example, the driver alert system 22 can alert the driver of the subject vehicle 10 that the secondary vehicle 48 is approaching from the rear side, the left side, or the right side of the subject vehicle 10. For example, with reference to
With reference to
The controller 26 can also receive GPS/traffic data from the GPS 28. For example, the controller 26 can receive GPS data, including a current location of the subject vehicle 10 and map data of the area surrounding the subject vehicle 10. As discussed above, based on the current location of the subject vehicle 10 and the map data, the controller 26 can determine the trajectory path of the subject vehicle 10 and whether the current lane of the subject vehicle 10 is about to merge with another lane, such as a highway lane.
The controller 26 can receive traffic sign data from a TSR system 32. As described above, the TSR system 32 can receive image data from the front-facing camera 30 and can monitor a scan area 40 for traffic signs 42. The TSR system 32 can then analyze the traffic sign 42 and determine whether the traffic sign indicates an upcoming traffic merge.
The controller 26 can receive surrounding object data from an object detection system 36. As described above, the object detection system 36 can receive image data from the front-facing camera 30 and can monitor a scan area 40 for long vehicles 50 alongside the subject vehicle 10. The system 12 can then monitor a location of the subject vehicle 10 relative to the long vehicle 50.
The controller 26 can also receive lane departure data from the LDW system 34. The LDW system 34 can receive image data from the front-facing camera 30, or from other cameras installed on the subject vehicle 10, and can monitor lane lines surrounding the subject vehicle 10 to determine when the subject vehicle 10 is crossing over one or more lane lines. As described in further detail below, the controller 26 can receive lane departure data from the LDW system 34 and can expand the blind spot alert area in response to the subject vehicle 10 crossing two lanes at once.
Based on the GPS/traffic data, the traffic sign data, the surrounding object data, and the lane departure data, the controller 26 can output an expanded blind spot alert area command to the blind spot monitoring system 24. The blind spot monitoring system 24 can then appropriately expand the blind spot alert area and monitor the expanded blind spot alert area 46, 52 for secondary vehicles 48. The blind spot monitoring system 24 can then generate blind spot alert data when a secondary vehicle 48 is detected in the expanded blind spot alert area 46, 52.
Additionally, based on the blind spot alert data, the controller 26 can output an activation command to the driver alert system 22 to alert the driver of the subject vehicle 10 to the presence of a secondary vehicle 48 in the blind spot alert area of the subject vehicle 10. The activation command may include location data indicating a location of the secondary vehicle 48 relative to the subject vehicle 10.
With reference to
At 704, the controller 26 receives GPS/traffic data from the GPS 28 and/or traffic sign data from the TSR system 32. For example, as discussed above, the TSR system 32 can monitor a scan area 40 for traffic signs 42 and, when a traffic sign 42 is detected, analyze the traffic sign 42 to determine whether the traffic sign 42 indicates an upcoming traffic merge. As further discussed above, in addition to or as an alternative to the TSR system 32, the GPS 28 can also be used to determine an upcoming traffic merge. For example, the controller 26 can analyze GPS map data and a current location and trajectory path of the subject vehicle 10 and determine whether the current lane of the subject vehicle 10 is about to merge with another lane, such as a highway lane.
At 706, the controller determines whether the subject vehicle 10 is merging or about to merge into another lane of traffic. At 706, when the subject vehicle 10 is not merging or about to merge into another lane of traffic, the controller 26 proceeds to 708 and uses the normal or initial blind spot alert area 44, shown in
At 712, the controller 26 determines whether a secondary vehicle 48 is located in the blind spot alert area of the subject vehicle 10, as previously set at steps 708 or 710. At 712, when a secondary vehicle 48 is not present in the blind spot alert area of the subject vehicle 10, the controller 26 loops back to 704 and repeats the method 700.
At 712, when the controller 26 determines that a secondary vehicle 48 is present in the blind spot alert area of the subject vehicle 10, the controller 26 alerts the driver that a secondary vehicle 48 is in the blind spot alert area of the subject vehicle 10 using the driver alert system 22. The controller 26 then loops back to 704 and repeats the method 700.
With reference to
At 804, the controller 26 receives surrounding object data from the object detection system 36. For example, as discussed above with reference to
At 806, the controller 26 determines whether a long vehicle 50, such as a truck or vehicle towing a trailer, is adjacent to the subject vehicle 10. For example, the object detection system 36 or the controller 26 can detect a length of a vehicle adjacent to the subject vehicle 10, and compare the detected length to a predetermined length threshold.
At 806, when a long vehicle is not adjacent to the subject vehicle 10, the controller 26 proceeds to 808 and uses the normal or initial blind spot alert area 44, shown in
At 806, when a long vehicle is adjacent to the subject vehicle 10, the controller 26 proceeds to 810. At 810, the controller 26 determines whether subject vehicle 10 has passed the long vehicle 50 based on surrounding object data received from the object detection system 36. When the subject vehicle 10 has not passed the long vehicle 50, the controller 26 loops back to 810 and continues to check whether the subject vehicle 10 has passed the long vehicle 50. At 810, when the subject vehicle 10 has passed the long vehicle 50, the controller 26 proceeds to 812 and uses the expanded blind spot alert area 52, shown in
At 814, the controller 26 determines whether a secondary vehicle 48 is located in the blind spot alert area of the subject vehicle 10, as previously set at steps 808 and 812. At 814, when a secondary vehicle 48 is not present in the blind spot alert area of the subject vehicle 10, the controller 26 loops back to 804 and repeats the method 800.
At 814, when the controller 26 determines that a secondary vehicle 48 is present in the blind spot alert area of the subject vehicle 10, the controller 26 alerts the driver that a secondary vehicle 48 is in the blind spot alert area of the subject vehicle 10 using the driver alert system 22. The controller 26 then loops back to 804 and repeats the method 800.
With reference to
At 904, the controller 26 receives lane departure data from the LDW system 34. As described above, the LDW system 34 can receive image data from the front-facing camera 30, or from other cameras installed on the subject vehicle 10, and can monitor lane lines surrounding the subject vehicle 10 to determine when the subject vehicle 10 is crossing over one or more lane lines.
At 906, the controller 26 determines whether a turn signal of the subject vehicle 10 is currently activated. At 906, when a turn signal is not currently activated, the controller 26 proceeds to 908 and uses the normal or initial blind spot alert area 44, shown in
At 906, when the controller 26 determines that a turn signal is currently activated, the controller 26 proceeds to 910.
At 910, the controller 26 determines whether the subject vehicle 10 has crossed a lane marker line yet based on lane departure data from the LDW system 34. At 910, when the subject vehicle 10 has not yet crossed a lane marker line yet, the controller 26 proceeds to 908 and uses the normal or initial blind spot alert area 44, shown in
At 910, when the controller determines that the subject vehicle 10 has crossed a lane marker line, the controller 26 proceeds to 912.
At 912, the controller 26 determines whether the subject vehicle 10 is attempting to cross two lanes at once, based on lane departure data from the LDW system 34. At 912, when the controller 26 determines that the subject vehicle 10 is not attempting to cross two lanes at once, the controller 26 proceeds to 908 and uses the normal or initial blind spot alert area 44, shown in
At 912, when the controller 26 determines that the subject vehicle 10 is attempting to cross two lanes at once, based on lane departure data from the LDW system 34, the controller 26 proceeds to 914 and uses the expanded blind spot alert area 46, shown in
At 916, the controller 26 determines whether a secondary vehicle 48 is located in the blind spot alert area of the subject vehicle 10, as previously set at steps 908 or 914. At 916, when a secondary vehicle 48 is not present in the blind spot alert area of the subject vehicle 10, the controller 26 loops back to 904 and repeats the method 900.
At 916, when the controller 26 determines that a secondary vehicle 48 is present in the blind spot alert area of the subject vehicle 10, the controller 26 alerts the driver that a secondary vehicle 48 is in the blind spot alert area of the subject vehicle 10 using the driver alert system 22. The controller 26 then loops back to 904 and repeats the method 900.
In this way, the present teachings provide a blind spot monitoring system 24 with adaptive blind spot alert areas to warn the driver of a subject vehicle 10 of approaching vehicles earlier than in previous systems.
Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those who are skilled in the art. Numerous specific details are set forth such as examples of specific components, devices, and methods, to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms, and that neither should be construed to limit the scope of the disclosure. In some example embodiments, well-known processes, well-known device structures, and well-known technologies are not described in detail.
The terminology used is for the purpose of describing particular example embodiments only and is not intended to be limiting. The singular forms “a,” “an,” and “the” may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “including,” and “having,” are inclusive and therefore specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.
When an element or layer is referred to as being “on,” “engaged to,” “connected to,” or “coupled to” another element or layer, it may be directly on, engaged, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on,” “directly engaged to,” “directly connected to,” or “directly coupled to” another element or layer, there may be no intervening elements or layers present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between” versus “directly between,” “adjacent” versus “directly adjacent,” etc.). The term “and/or” includes any and all combinations of one or more of the associated listed items.
Although the terms first, second, third, etc. may be used to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another region, layer or section. Terms such as “first,” “second,” and other numerical terms when used herein do not imply a sequence or order unless clearly indicated by the context. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments.
Spatially relative terms, such as “inner,” “outer,” “beneath,” “below,” “lower,” “above,” “upper,” and the like, may be used for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. Spatially relative terms may be intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as “below” or “beneath” other elements or features would then be oriented “above” the other elements or features. Thus, the example term “below” can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.
The foregoing description of the embodiments has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.
Number | Name | Date | Kind |
---|---|---|---|
5689264 | Ishikawa | Nov 1997 | A |
5781119 | Yamashita et al. | Jul 1998 | A |
5899953 | Urahashi | May 1999 | A |
6193380 | Jacobs | Feb 2001 | B1 |
6506969 | Baron | Jan 2003 | B1 |
6560529 | Janssen | May 2003 | B1 |
6561295 | Kuroda et al. | May 2003 | B1 |
6744396 | Stone et al. | Jun 2004 | B2 |
6853894 | Kolls | Feb 2005 | B1 |
7038577 | Pawlicki et al. | May 2006 | B2 |
7504986 | Brandt et al. | Mar 2009 | B2 |
7602276 | Madau | Oct 2009 | B2 |
7612658 | Stopczynski | Nov 2009 | B2 |
7650227 | Kirk et al. | Jan 2010 | B2 |
8224370 | Miucic | Jul 2012 | B2 |
8489284 | Emam et al. | Jul 2013 | B2 |
8669857 | Sun et al. | Mar 2014 | B2 |
8775031 | Bankhead | Jul 2014 | B1 |
8775073 | Denaro | Jul 2014 | B2 |
8791802 | Schwindt et al. | Jul 2014 | B2 |
20020057195 | Yamamura | May 2002 | A1 |
20020126002 | Patchell | Sep 2002 | A1 |
20030016158 | Stayton et al. | Jan 2003 | A1 |
20030109985 | Kotzin | Jun 2003 | A1 |
20040016870 | Pawlicki et al. | Jan 2004 | A1 |
20040119609 | Solomon | Jun 2004 | A1 |
20040229621 | Misra | Nov 2004 | A1 |
20050015203 | Nishira | Jan 2005 | A1 |
20050033497 | Stopczynski | Feb 2005 | A1 |
20050128061 | Yanai | Jun 2005 | A1 |
20060006988 | Harter et al. | Jan 2006 | A1 |
20060155444 | Lee et al. | Jul 2006 | A1 |
20070018801 | Novotny et al. | Jan 2007 | A1 |
20070159355 | Kelly et al. | Jul 2007 | A1 |
20080169938 | Madau | Jul 2008 | A1 |
20080252482 | Stopczynski | Oct 2008 | A1 |
20080300755 | Madau et al. | Dec 2008 | A1 |
20090045928 | Rao et al. | Feb 2009 | A1 |
20090079553 | Yanagi et al. | Mar 2009 | A1 |
20090243822 | Hinninger et al. | Oct 2009 | A1 |
20100045448 | Kakinami | Feb 2010 | A1 |
20100049393 | Emam et al. | Feb 2010 | A1 |
20100238009 | Cook et al. | Sep 2010 | A1 |
20110010041 | Wagner et al. | Jan 2011 | A1 |
20110084852 | Szczerba | Apr 2011 | A1 |
20110187863 | Glander et al. | Aug 2011 | A1 |
20120116659 | Yuasa | May 2012 | A1 |
20120218124 | Lee et al. | Aug 2012 | A1 |
20120245832 | Meis et al. | Sep 2012 | A1 |
20130018545 | Prakah-Asante et al. | Jan 2013 | A1 |
20130051042 | Nordbruch | Feb 2013 | A1 |
20130054086 | Lo et al. | Feb 2013 | A1 |
20130176145 | Yu | Jul 2013 | A1 |
20130181860 | Le | Jul 2013 | A1 |
20130253810 | Miyajima et al. | Sep 2013 | A1 |
20130253811 | Miyajima et al. | Sep 2013 | A1 |
20140191895 | Binzer et al. | Jul 2014 | A1 |
20150100216 | Rayes | Apr 2015 | A1 |
20150185319 | Matsuura et al. | Jul 2015 | A1 |
20150193885 | Akiva et al. | Jul 2015 | A1 |
20150195496 | Hayakawa et al. | Jul 2015 | A1 |
20150232021 | Downey | Aug 2015 | A1 |
20150232034 | Weller et al. | Aug 2015 | A1 |
20150301182 | Geiger et al. | Oct 2015 | A1 |
20150302586 | Fukata | Oct 2015 | A1 |
20150331098 | Luebbert | Nov 2015 | A1 |
20160090043 | Kim et al. | Mar 2016 | A1 |
20160101730 | Shehan et al. | Apr 2016 | A1 |
20160207466 | Lynam | Jul 2016 | A1 |
20160232790 | Massey | Aug 2016 | A1 |
20170154523 | Moritani et al. | Jun 2017 | A1 |
Number | Date | Country |
---|---|---|
2013-002987 | Jan 2013 | JP |
WO 2013081998 | Jun 2013 | WO |
WO 2014006919 | Jan 2014 | WO |
Entry |
---|
U.S. Appl. No. 15/096,400, filed Apr. 12, 2016, Ting-Yu Lai. |
U.S. Appl. No. 15/096,416, filed Apr. 12, 2016, Ting-Yu Lai. |
U.S. Appl. No. 15/096,430, filed Apr. 12, 2016, Ting-Yu Lai. |
Number | Date | Country | |
---|---|---|---|
20170291547 A1 | Oct 2017 | US |