Patent Publication Number: US-8970358-B2

Title: Alert systems and methods for a vehicle

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application claims the benefit of U.S. Provisional Application No. 61/663,516, filed Jun. 22, 2012 which is incorporated herein by reference in its entirety. 
    
    
     TECHNICAL FIELD 
     The technical field generally relates to driver alert systems and methods, and more particularly relates to control methods and systems for driver alert systems of a vehicle. 
     BACKGROUND 
     Collision avoidance systems warn drivers of potential collision threats that may be in the line-of-sight of the driver (e.g., detected by on-board vehicle sensors) or out of the line-of-sight of the driver (e.g., determined from wireless vehicle-to-vehicle communications and/or vehicle-to-infrastructure communications). Collision avoidance systems may generate visual, auditory, or haptic alerts to warn a vehicle driver of the potential collision threats. Typically, the collision avoidance systems are implemented as separate systems. Thus, alerts may be generated by some collision avoidance systems without regard to alerts that are generated by other collision avoidance systems. If more than one alert is generated to the vehicle driver at any one time, the multiple alerts might have the potential to distract the driver from avoiding the collision. 
     Accordingly, it is desirable to provide methods and systems for coordinating the alerting of the driver of the vehicle using any combination of the auditory, visual, and haptic alerts. Furthermore, other desirable features and characteristics of the present invention will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the foregoing technical field and background. 
     SUMMARY 
     A method of alerting a driver of a vehicle is provided. In one embodiment, the method includes: receiving conditions data from one or more collision avoidance systems; determining an alert mode based on the conditions data; receiving a fault status indicating a fault of at least one of a haptic alert device, a visual alert device, and an auditory alert device; resetting the alert mode to an override mode based on the fault status; and selectively generating an alert pattern for at least one of a haptic alert device, a visual alert device, and an auditory alert device that does not have a fault based on the override mode of the alert mode. 
     A control system is provided for alerting a driver of a vehicle. In one embodiment, the system includes a first module that receives conditions data from one or more collision avoidance systems, that determines an alert mode based on the conditions data, that receives a fault status indicating a fault of at least one of a haptic alert device, a visual alert device, and an auditory alert device, and that resets the alert mode to an override mode based on the fault status. A second module selectively generates an alert pattern for at least one of a haptic alert device, a visual alert device, and an auditory alert device that does not have a fault based on the override mode of the alert mode. 
    
    
     
       DESCRIPTION OF THE DRAWINGS 
       The exemplary embodiments will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and wherein: 
         FIG. 1  is a functional block diagram illustrating a vehicle that includes a driver alert system in accordance with exemplary embodiments; 
         FIG. 2  is a dataflow diagram illustrating an alert control system of the driver alert system in accordance with exemplary embodiments; and 
         FIGS. 3-8  are flowcharts illustrating alert methods that may be performed by the alert systems in accordance with exemplary embodiments. 
     
    
    
     DETAILED DESCRIPTION 
     The following detailed description is merely exemplary in nature and is not intended to limit the application and uses. 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. It should be understood that throughout the drawings, corresponding reference numerals indicate like or corresponding parts and features. As used herein, the term module refers to an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and memory that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality. 
     Referring now to  FIG. 1 , a vehicle  10  is shown having a driver alert system  12  in accordance with various embodiments. The driver alert system  12  is associated with one or more collision avoidance systems  14 ,  16  of the vehicle  10 . The driver alert system  12  generally alerts a driver of one or more conditions that are detected and indicated by the collision avoidance system(s)  14 ,  16  in accordance with various embodiments. Although the figures shown herein depict example arrangements of elements, additional intervening elements, devices, features, or components may be present in actual embodiments. It should also be understood that  FIG. 1  is merely illustrative and may not be drawn to scale. 
     As shown, the vehicle  10  includes one or more line-of-sight collision avoidance or mitigation systems  14 , and one or more non-line-of-sight collision avoidance or mitigation systems  16 . The line-of-sight collision avoidance systems  14  generally include one or more on-board vehicle sensors (not shown) (e.g., camera, radar, and/or lidar) communicatively coupled to a control module (not shown) that detect a potential for a collision based on the vehicle sensor signals. Exemplary line-of-sight collision avoidance systems  14  include, but are not limited to, lane departure warning or lanekeeping assist systems  18 , front park assist systems  20 , rear park assist systems  22 , front and rear automatic braking systems  24 , rear cross traffic alert systems  26 , adaptive cruise control (ACC) systems  28 , side blind zone (or spot) detection systems  30 , lane change alert systems  32 , driver attention (e.g., distraction- and/or drowsiness-monitoring) systems  34 , and front and rear pedestrian detection systems  36 . 
     The non-line-of-sight collision avoidance systems  16  generally include one or more communication systems or devices (not shown) that can determine or forecast a potential collision. Exemplary non-line-of-sight collision avoidance systems include, but are not limited to, vehicle communication systems that communicate between the vehicle  10  and other vehicles (not shown) (e.g., vehicle-to-vehicle communication systems  38 ), vehicle communication systems that communicate between the vehicle  10  and an infrastructure (not shown) (e.g., vehicle-to-infrastructure communication systems  40 ) and vehicle communication systems that communicate between the vehicle  10  and an pedestrians/cyclists (e.g., vehicle-to-pedestrian communication systems  41 ) to forecast potential collisions due to traffic. As can be appreciated, in various embodiments, any one of the line-of-sight collision avoidance systems  14  or the non-line-of sight collision avoidance systems  16  can include both vehicle sensors and communication systems to detect activity either inside the line-of-sight of the driver or outside of the line-of-sight of the driver. 
     A control module  42  receives signals  44 ,  46  from the various collision avoidance systems  14 ,  16  indicating one or more potential collision conditions. As can be appreciated, in various other embodiments, the control module  42  may be integrated with other control modules (not shown) of the vehicle  10 , and/or may be implemented separately for each collision avoidance system  14 ,  16 . The control module  42  may also be a plug-in device that is installed into an onboard diagnostics connector of the vehicle (OBD-II), a retrofit module that is collocated with an existing vehicle module (i.e., installed at the host module using an adaptation connector), or as a replacement part for an existing vehicle system (i.e., inside rear-view mirror assembly). The control module  42  may also be a wireless device that is communicatively couples to the vehicle  10  over a short range wireless connection such as Wi-Fi, Bluetooth, NFC or similar. 
     The control module  42  generates control signals  48  to alert devices and/or control devices  50  such that a driver can be alerted of the condition and/or such that vehicle functions can be performed to minimize or prevent the collision. In various embodiments, the alert devices can include, one or more haptic alert devices  50  (e.g., one or more haptic alert devices of a vehicle seat assembly described, one or more haptic alert devices of a steering wheel assembly, etc.), one or more auditory alert devices  52  (e.g., warning chimes or beeps, etc.), one or more visual alert devices  54  (e.g., warning lamps, an information center, a screen of an infotainment system, LED panel, head-up display, display reflected off windshield, etc.), and auditory, visual, and haptic devices of an infotainment system  56 . The control devices can include, but are not limited to, a vehicle system control device  58  that performs vehicle braking, vehicle system control device  58  that adjusts the torque or position of the vehicle steering, or other driving maneuvers. In various embodiments, the control module  42  coordinates the generation of the control signals  48  such that the alerts alert the driver in a way that does not distract the driver from avoiding the collision. 
     Referring now to  FIG. 2  and with continued reference to  FIG. 1 , a dataflow diagram illustrates various embodiments of an alert control system that may be embedded within the control module  42 . Various embodiments of alert control systems according to the present disclosure may include any number of sub-modules embedded within the control module  42 . As can be appreciated, the sub-modules shown in  FIG. 2  may be combined and/or further partitioned to similarly coordinate and provide driver alerts and/or request vehicle functions to be performed. 
     In various embodiments, inputs to the alert system may be sensed from the vehicle  10 , received from other control modules (not shown) within the vehicle  10  (e.g., through a vehicle communication bus or an intra-vehicle wireless communication), received from modules remote from the vehicle  10  (e.g., through inter-wireless communication or cellular communication), received from one or more sensors (not shown) of the vehicle  10 , and/or determined/modeled by other sub-modules (not shown) within the control module  42 . In various embodiments, the control module  42  includes an alert settings datastore  70 , a user configuration module  72 , a monitoring module  74 , a mode determination module  76 , and a pattern determination module  78 . In various embodiments, the alert settings datastore  70  may reside in a local vehicle module, in a plug-in vehicle accessory device, in user-removable storage (e.g., USB flash drive, Secure Digital SD, etc.), in the storage of a user accommodated device (e.g., consumer smartphone or key fob that is wirelessly paired to the vehicle  10 ), or in a cloud database. For exemplary purposes, the alert settings datastore  70  is described as being a part of the control module  42 . 
     The alert settings datastore  70  stores predefined alert settings and/or user configured alert settings, as will be discussed in more detail below. As can be appreciated, the alert settings datastore  70  can include volatile memory that temporarily stores the settings, non-volatile memory that stores the settings across key cycles, or a combination of volatile and non-volatile memory. 
     The user configuration module  72  manages the display of a configuration menu  80 , and manages user input  82  received from a user interacting with the configuration menu  80 . As can be appreciated, the configuration menu  80  can be displayed on a display device within the vehicle  10  (e.g., via an information center), can be displayed on a display device that is remote from the vehicle  10  (e.g., a computing device or personal handheld device), or can be displayed on a device connected to the vehicle  10  (e.g., a technician tool). 
     In various embodiments, the configuration menu  80  may be implemented as a main menu with one or more sub-menus. Each menu or sub-menu includes selectable options that, when selected, allow a user to configure various alert settings associated with the haptic alert devices  50 , the auditory alert devices  52 , the visual alert devices  54 , and/or the infotainment system  56 . The alert settings for the haptic alert devices  50  can include, but are not limited to, an occurrence of the vibration (e.g., whether or not to perform the vibration for a particular mode), a location of the vibration (e.g., at a particular location on seat or other haptic device), an intensity of the vibration, a duration of the vibration, a rate of the vibration, and/or a frequency of the pulses of the vibration. The alert settings for the auditory alert devices  52  can include, but are not limited to, an occurrence of the auditory alert (e.g., whether or not to perform the auditory alert), a sound level of the auditory alert, a sound type of the auditory alert (e.g., a particular narrow-band chime or broadband auditory warning signal), a duration of the auditory alert, a rate of the auditory alert, and/or a frequency of sounds of the auditory alert. The alert settings for the visual alert devices  54  can include, but are not limited to, an occurrence of the visual alert (e.g., whether or not to perform the visual alert), a location of the visual alert (e.g., whether on a heads up display, an LED panel, or other visual alert device), a visual type of the visual alert (e.g., a particular color or symbol), a duration of the visual alert, a rate of the visual alert, and/or a frequency of visuals of the visual alert. 
     The alert settings for the infotainment system  56  can include, but are not limited to, an occurrence of an auditory muting, haptic feedback, or pattern display (e.g., whether or not to perform the auditory muting, the haptic feedback, and/or pattern display for a particular mode), and a type of auditory muting, haptic feedback, or pattern display that should be applied. For example, a rapid pulsing pattern may be transmitted via the finger making contact with a touch screen when a collision may be imminent. In another example, the radio can be intelligently muted based on interior vehicle conditions indicating a volume level of the infotainment system  56 . 
     In various embodiments, the configuration menu  80  allows the alert settings to be configured for alert types such as individual alert conditions, certain types or groups of alert conditions, particular driving scenarios, and/or for particular vehicle conditions. The individual alert conditions can include, but are not limited to, conditions associated with the various collision avoidance systems. The particular driving scenarios can include, but are not limited to, vehicle occupancy type conditions (e.g., as determined based on seatbelt signals, or seat compression signals, number of consumer device pairings, number of consumer devices discovered, rear seat entertainment system usage, passenger door opening/closing inferences, etc.), ambient conditions (such as day or night, or weather conditions, which for example, can be derived from wiper usage and outside air temperature), driver self-rated attention, distraction, or drowsy state (e.g., high, medium, or low), and a type of road that the vehicle is traveling on based on a digital map information (e.g., unique settings may be configured for different types of road classes: residential, arterial, highway, limited access, etc.). As can be appreciated, other map attributes such as posted speed limits may also be used (e.g., specific settings may apply based on the current posted speed limit). The digital map database may reside inside an embedded vehicle module, on a customer device, or on a remote server (which may be accessed in real time or accessed as a downloaded datastore). The vehicle conditions can include, but are not limited to, when the vehicle is experiencing a severe system malfunction (e.g., a specific device trouble code has activated or the driver has engaged the vehicle hazard lights). 
     The type or groups of alert conditions may include a grouping or type of any of the alert conditions, driving scenarios, and vehicle conditions and can include, but are not limited to, parking type conditions versus driving type (non-parking) conditions, and various collision threat conditions (e.g., minor threats verses imminent threats, and various threat levels there between). In various embodiments, alert conditions may also be configured to be specific to an identity of the current driver (e.g., the identity can be determined based on a current keyfob or driver memory seat selection, or driver identity based on a prioritized paired device). 
     Based on the user input  82  received from the user interacting with the configuration menu  80  (e.g., via one or more user input devices), the user configuration module  72  stores the user configured alert settings  84  in the alert settings datastore  70 . For example, as shown in the exemplary flowcharts of  FIGS. 3 and 4  and with continued reference to  FIG. 2 , a driver selection menu is displayed requesting selection of a particular driver at  300 . If a driver selection is not received at  310 , it is determined with the user input  82  indicates to exit the driver selection menu at  305 . If the user input  82  indicates to exit the driver selection menu at  305 , the driver selection menu is exited and the method may end at  308 . 
     If, however, the user input does not indicate to exit the driver selection menu at  305 , the driver selection menu is displayed at  300 . Upon receipt of user input  82  indicating a driver selection at  310 , an alert type selection menu is displayed requesting selection of a particular alert type at  320 . For example, the alert type may be an alert condition type, a group of alert conditions type, a driving scenario type, or a vehicle condition type. 
     If the user input  82  indicates that an alert condition type is selected at  330 , an alert condition selection menu is displayed requesting selection of a particular alert condition at  340 . Upon receipt of user input  82  indicating a selection of a particular alert condition at  350 , the particular alert condition is temporarily stored at  360 . Thereafter, the method continues at  365 . 
     If, at  370 , the user input  82  indicates that a group of alert conditions type is selected, a group of alert conditions selection menu is displayed requesting selection of a particular group or type of alert conditions at  380 . Upon receipt of user input  82  indicating a selection of a particular group or type of alert conditions at  390 , the particular group or type of alert conditions is temporarily stored at  400 . Thereafter, the method continues at  365 . 
     If, at  410 , the user input  82  indicates that a driving scenario type is selected, a driving scenarios selection menu is displayed requesting selection of a particular driving scenario at  420 . Upon receipt of user input  82  indicating a selection of a particular driving scenario at  430 , the particular driving scenario is temporarily stored at  440 . Thereafter, the method continues at  365 . 
     If, at  450 , the user input  82  indicates that a vehicle conditions type is selected, a vehicle conditions selection menu is displayed requesting selection of a particular vehicle condition at  460 . Upon receipt of user input  82  indicating a selection of a particular vehicle condition at  470 , the particular vehicle condition is temporarily stored at  480 . Thereafter, the method continues at  365 . 
     If, at  490 , the user input  82  indicates to exit the alert type selection menu, the driver selection menu is displayed at  300 . Otherwise, the alert type selection menu is displayed at  320 . 
     After  365  (in  FIG. 4 ), an alert device selection menu is displayed requesting selection of a particular alert device (e.g., a haptic device, an auditory device, a visual device, an infotainment system, etc.) at  500 . Upon receipt of user input  82  indicating a selection of a particular alert device at  510 , an alert settings selection menu is displayed requesting selection of a particular alert setting at  520 . Upon receipt of user input  82  indicating a selection of a particular alert setting at  530 , the particular alert setting is associated with the temporarily stored alert type at  540 . 
     If, at  550 , the user input  82  indicates to exit the alert settings selection menu, the alert device selection menu is displayed at  500 . Otherwise, the alert settings selection menu is displayed at  520 . If at  510 , the user input  82  does not indicate an alert type and the user input  82  does not indicate to exit the alert device menu at  560 , the alert device selection menu is displayed at  500 . If, however, the user input  82  does not indicate an alert type at  510  rather, the user input indicates to exit the alert device selection menu at  560 , the method returns to  320  to display the alert type selection menu at  570 . As can be appreciated, the method may iterate until the user has completed configuration of the selected alert settings and has exited the driver selection menu. 
     With reference back to  FIG. 2 , the monitoring module  74  monitors input data  86  associated with the alert devices  50 - 56  to determine whether the alert devices  50 - 56  are operating properly. If the monitoring module  74  determines that one or more of the alert devices  50 - 56  is not operating properly (i.e., malfunctioning), the monitoring module  74  generates a warning message  88 , generates a warning signal  90 , and/or generates a fault condition status  92  that can be evaluated by the mode determination module  76 . The fault condition status  92  may indicate a type of fault and the particular faulty device. 
     In various embodiments, the warning message  88  may include a diagnostic code that indicates a fault of the alert device  50 - 56 . The warning message  88  may be communicated to an occupant of the vehicle  10  (e.g., via an information center of the vehicle  10 ), may be communicated to a remote location (e.g., via a telematics system of the vehicle  10 ), may be communicated to an accommodated or plug-in device, and/or may be retrieved by a technician (e.g., via a technician tool that communicatively couples to a communication bus of the vehicle  10 ). In various embodiments, the warning signal  90  is a control signal that activates an alert device  50 - 56  other than the device that contains the fault. For example, the warning signal  90  can be a visual alert device  54  of the vehicle  10 , can be a control signal that activates an auditory alert device  52  of the vehicle  10 , and/or can be a control signal that activates a haptic alert device  50 . 
     The mode determination module  76  determines a current alert mode  94  based on various vehicle conditions indicated by the signals  44 ,  46 . The vehicle conditions are conditions that may require an alert to the driver and can be received from the various line-of-sight collision avoidance systems  14  ( FIG. 1 ) as collision avoidance system conditions data  96 , can be received from the non-line-of-sight collision avoidance systems  16  as vehicle-to-vehicle conditions data  98 , and/or as vehicle-to-infrastructure conditions data  100  and/or vehicle-to-pedestrian conditions data  41 . Based on the conditions data  96 - 100 , the mode determination module  76  sets the alert mode  94  to indicate one or more alert conditions, one or more vehicle conditions, and/or one or more driving scenarios. In various embodiments, the mode determination module  76  may set the alert mode  94  (e.g., to an override mode) based on a determination of an imminent collision threat indicated by one of the systems  14 ,  16  ( FIG. 1 ). 
     In various embodiments, the mode determination module  76  may determine that the conditions data  96 - 100  present multiple alert modes  94 . In such a case, the mode determination module  76  generates the multiple alert modes or, alternatively, arbitrates between the alert modes based on a priority scheme to generate a single alert mode  94 , or alternatively, arbitrates between the alert modes to create a combined alert. In various embodiments, the mode determination module  76  monitors the fault condition status  92  of the alert devices.  50 - 56  ( FIG. 1 ). The mode determination module  76  sets the alert mode  94  based on the fault condition status  92 . For example, if the fault condition status  92  indicates a fault of the haptic device  50  ( FIG. 1 ), the mode determination module  76  may set the alert mode  94  to an override mode. 
     For example, as shown in the flowchart of  FIG. 5  and with continued reference to  FIG. 2 , the conditions data  96 - 100  is received at  600 . The conditions data  96 - 100  is evaluated at  610  and the alert mode  94  (or modes) is determined at  620 . Based on the evaluation, the alert mode  94  can indicate one or more alert conditions, one or more driving scenarios, and/or one or more vehicle conditions. 
     It is determined whether a fault condition status  92  has been received at  630 . If a fault condition status  92  has not been received at  630 , or the fault condition status  92  indicates that the fault is not a fault of an alert device  50 - 56  ( FIG. 1 ) that is associated with the alert mode  94 , the method may end at  660 . If, however, a fault condition status  92  is received at  630 , and the fault condition status  92  indicates a fault of an alert device  50 - 56  ( FIG. 1 ) associated with the alert mode  94  at  640 , the alert mode  94  is set to an override mode based on the faulty device at  650 . Thereafter, the method may end at  660 . 
     With reference back to  FIG. 2 , the pattern determination module  78  determines one or more alert patterns based on the alert mode  94 . The alert patterns include haptic alert patterns  104 , visual alert patterns  106 , and/or auditory alert patterns  108  that are used by the haptic alert devices  50  ( FIG. 1 ), the visual alert devices  54  ( FIG. 1 ), the auditory alert devices  52  ( FIG. 1 ), and/or the infotainment system  56  ( FIG. 1 ) to generate the alerts. Depending on the type of pattern (e.g., haptic, visual, and/or audio), the patterns may indicate a location or locations of the alert within the alert device  50 - 56  (e.g., a vibration at a particular location or locations on seat or other haptic device), an auditory type of the alert (e.g., a particular chime), a visual type of the alert (e.g., a particular color or symbol) an intensity of the alert, a duration of the alert, a rate of the alert and/or a frequency of vibration pulses, visuals, or sounds of the alert. 
     In various embodiments, the pattern determination module  78  determines the alert patterns  104 - 108  for a particular device by retrieving predefined alert settings  110 , and/or the user configured alert settings  84  from the alert settings datastore  70 . The alert settings  84 ,  110  are retrieved based on the alert mode  94 . For example, as shown in the flowchart of  FIG. 6  and with continued reference to  FIG. 2 , one or more alert modes  94  are received (for ease of the discussion the method will be discussed in the context of a single alert mode  94 ) at  700 . 
     If the alert mode  94  is an override mode at  710 , predefined alert settings  110  associated with the particular override mode are retrieved from the alert settings datastore  70  at  720  and one or more of the alert patterns  104 - 108  are set based on the predefined alert settings  110  at  730 . Thereafter, the method may end at  735 . 
     If, however, the alert mode  94  is not an override mode at  710 , and user configured alert settings  84  exist for all of the one or more alert conditions, vehicle conditions, or driving scenarios of the alert mode  94  at  740 , the user configured alert setting  84  are retrieved from the alert settings datastore  70  at  750 . One or more of the alert patterns  104 - 108  are set based on the user configured alert settings  84  at  760 . Thereafter, the method may end at  735 . 
     If the alert mode  94  is not an override mode at  710 , and user configured alert settings  84  do not exist for all of the one or more alert conditions, vehicle conditions or driving scenarios of the alert mode  94  at  740 , however user configured alert settings  84  exist for some (but not all) of the one or more alert conditions, vehicle conditions, or driving scenarios at  770 , the user configured alert settings  84  are retrieved for the alert conditions, vehicle conditions, or driving scenarios in which they exist at  780 , and the predefined alert settings  110  are retrieved for the remaining alert conditions, vehicle conditions, or driving scenarios at  790 . One or more alert patterns  104 - 108  are set based on the user configured alert settings  84  and the predefined alert settings  110  at  800 . Thereafter, the method may end at  735 . 
     If the alert mode  94  is not an override mode at  710 , and user configured alert settings  84  do not exist for all of the one or more alert conditions, vehicle conditions, or driving scenarios at  740 , and in fact they do not exist for any of the one or more alert conditions, vehicle conditions, or driving scenarios at  770 , the predefined alert settings  110  are retrieved for the alert conditions, vehicle conditions, or driving scenarios of the alert mode  94  at  810 , and one or more alert patterns  104 - 108  are set based on the predefined alert settings  110  at  820 . Thereafter, the method may end at  735 . 
     With reference back to  FIG. 2 , when the alert mode  94  indicates multiple alert conditions, vehicle conditions, and/or driving scenarios that are associated with multiple patterns, the pattern determination module  78  coordinates the alert patterns  104 - 108  before being generated. In various embodiments, the pattern determination module  78  coordinates the alert patterns  104 - 108  by synchronizing a timing of the patterns, arbitrating between patterns, and/or combining patterns into a single pattern. In various embodiments, the pattern determination module  78  coordinates the alert patterns  104 - 108  based on whether the alert patterns  104 - 108  are associated with the same alert device  50 - 56  ( FIG. 1 ) or with different alert devices  50 - 56  ( FIG. 1 ). 
     For example, as shown in  FIG. 7  and with continued reference to  FIG. 2 , the alert patterns  104 - 108  are evaluated at  900 . If multiple alert patterns do not exit at  910 , the method may end at  915 . If, however, multiple alert patterns  104 - 108  exist at  910 , it is determined whether any of the alert patterns  104 - 108  are associated with a same alert device  50 - 56  ( FIG. 1 ) at  920 . If alert patterns  104 - 108  are associated with a same alert device  50 - 56  ( FIG. 1 ) at  920 , the alert patterns  104 - 108  are arbitrated or combined for each same alert device  50 - 56  ( FIG. 1 ) at  930  before being generated. 
     For example, the alert patterns  104 - 108  can be arbitrated based on a predefined priority scheme to determine a preferred pattern. In another example, the alert patterns  104 - 108  can be combined or added to create unique, superimposed, and/or summative patterns without the need for arbitration. In various embodiments, the combined patterns may be combined for all or part of the alert depending on the timing of the alert. 
     If alert patterns  104 - 108  are only associated with a same alert device  50 - 56  ( FIG. 1 ) at  920 , and are not associated with different alert devices  50 - 56  ( FIG. 1 ) at  940 , the method may end at  915  (e.g., with only combining or arbitrating patterns between a same device). 
     If, in addition to alert patterns  104 - 108  being associated with a same alert device  50 - 56  ( FIG. 1 ), alert patterns  104 - 108  are associated with different alert devices  50 - 56  ( FIG. 1 ) at  940 , the alert patterns  104 - 108  between the alert devices  50 - 56  ( FIG. 1 ) are further synchronized or arbitrated at  950  before being generated. For example, the alert devices  50 - 56  ( FIG. 1 ) can be arbitrated based on a predefined priority scheme to determine a preferred alert device  50 - 56  ( FIG. 1 ) and the alert pattern  104 - 108  associated with that alert device  50 - 56  ( FIG. 1 ) is generated. In another example, visual, auditory, and or haptic alert patterns  104 - 108  can be synchronized to issue similar patterns (e.g., three visual alert flashes, three haptic seat pulses, and/or three beeps) without the need for arbitration. Thereafter, the method may end at  915  (e.g., with combining or arbitrating patterns of a same device and with synchronizing or arbitrating patterns between different devices). 
     If, however, alert patterns  104 - 108  are not associated with a same alert device  50 - 56  ( FIG. 1 ) at  920 , but the alert patterns  104 - 108  are associated with different alert devices  50 - 56  ( FIG. 1 ) at  940 , the alert patterns  104 - 108  between the different alert devices  50 - 56  ( FIG. 1 ) are synchronized or arbitrated at  950 , and the method may end at  915  (e.g., with only synchronizing or arbitrating patterns between different devices). 
     With reference back to  FIG. 2 , the pattern determination module  78  may further modify the alert patterns  104 - 108  from the patterns determined from the user configured alert settings  84  and/or the predefined alert settings  110  and/or modify an output of the infotainment system via infotainment signals  116  based on interior vehicle conditions  112  and/or exterior vehicle conditions  114 . The interior vehicle conditions  112  can include, but are not limited to, sensed or predicted acoustics of the interior of the vehicle  10  ( FIG. 1 ) that may impact a driver&#39;s ability to sense the alert. The exterior vehicle conditions can include, but are not limited to, sensed or predicted acoustics or vibrations of the exterior of the vehicle  10  ( FIG. 1 ) that may impact the driver&#39;s ability to sense the alert. 
     For example, as shown in the  FIG. 8  and with continued reference to  FIG. 2 , the vehicle conditions are received at  1000 . If the vehicle conditions are interior vehicle conditions  112  at  1010 , the alert patterns  104 - 108  are modified based on the interior vehicle conditions  112  at  1020 . For example, if the evaluation of the interior vehicle conditions  112  indicate the detection of a particular song or music being played on a radio of the infotainment system  56  ( FIG. 1 ), one or more of the haptic alert patterns  104  can be modified by increasing an intensity (e.g., a vibration intensity) based on the presence of low frequency content or radio volume. In another example, if the evaluation of the interior vehicle conditions  112  indicate the detection of a high volume setting of the infotainment system  56  ( FIG. 1 ), a low frequency auditory alert pattern may be superimposed into the auditory content of the infotainment system  56  ( FIG. 1 ) to reinforce the alert that is being communicated by a haptic alert device  50  ( FIG. 1 ). 
     If the vehicle conditions are interior vehicle conditions  112 , alternatively or additionally, the infotainment signals  116  are generated based on the interior vehicle conditions  112  at  1020 . For example, if the evaluation of the interior vehicle conditions  112  indicate the detection of a high volume setting of the infotainment system  56  ( FIG. 1 ), the infotainment volume level may be reduced via infotainment signals  116  to a level that is below the auditory alert sound level (e.g., 75 dBA), or the low frequency content (e.g., below 250 Hz) may be eliminated entirely or reduced to improve the driver&#39;s ability to perceive a haptic alert via infotainment signals  116 . 
     As can be appreciated, other interior conditions  112  may include, but are not limited to, an output of a driver distraction module, output of a driver workload estimation module (e.g., identifying that the driver is engaged in complex driving maneuvers, identifying if the driver is receiving an incoming call, is in an active call or is receiving urgent maneuver indications from the navigation system), a drowsy driver module, or an enabled state of semi-autonomous driving systems (e.g., cruise control, adaptive cruise control, lane keeping or lane centering system). For example, if the output of the driver distraction module suggest a driver is in a high, prolonged state of distraction, or prolonged state of severe drowsiness, alert patterns can be changed to provide a higher intensity alert (e.g., stronger vibration, louder alert, or brighter visual display) or an earlier alert. Similarly, if the driver is detected to be pressing a touch screen panel with their finger on an infotainment screen (which may indicate the driver&#39;s eyes are looking away from the outside traffic scene as they guide their finger to the desired area of the touch screen panel), alert patterns can be changed to provide a higher intensity alert (e.g., stronger vibration, louder alert, or brighter visual display) or even earlier alert. 
     If, in addition to the vehicle conditions being interior vehicle conditions  112  at  1010 , the vehicle conditions are not exterior vehicle conditions  114  at  1030 , the method may end at  1050  (e.g., with modifying patterns  104 - 108  and/or generating infotainment signals  116  only based on interior vehicle conditions  112 ). 
     If, in addition to the vehicle conditions being interior vehicle conditions  112  at  1010 , the vehicle conditions are exterior vehicle conditions  114  at  1030 , the alert patterns  104 - 108  are further modified based on the exterior vehicle conditions  114  at  1040 . For example, if the evaluation of the exterior vehicle conditions  114  indicates the detection of vehicle vibration as indicated by a vehicle suspension system (not shown), the alert patterns  104 - 108  are modified during rough road conditions. In this example, the patterns  104 - 108  may be adjusted based on the nature or magnitude of the vibration from the suspension system. For example, if an average magnitude over a predetermined time is determined to exceed some threshold, the alert pattern  104 - 108  can be adjusted to increase the vibration intensity (e.g., by a discrete value, or a value that is determined based on the magnitude). Thereafter, the method may end at  1050  (e.g., with modifying patterns  104 - 108  and/or generating infotainment signals  116  based on interior vehicle conditions  112  and with modifying patterns  104 - 108  based exterior vehicle conditions  114 ). 
     If, at  1010  the vehicle conditions are not interior vehicle conditions  112 , however, the vehicle conditions are exterior vehicle conditions  114  at  1030 , the alert patterns  104 - 108  are modified based on the exterior vehicle conditions  114  at  1040 . Thereafter, the method may end at  1050  (e.g., with modifying patterns  104 - 108  only based exterior vehicle conditions  114 ). 
     As can be appreciated in light of the disclosure, the order of operation within the methods shown in the flowcharts is not limited to the sequential execution as illustrated in the figures, but may be performed in one or more varying orders as applicable and in accordance with the present disclosure. As can further be appreciated, one or more steps of the methods may be added or removed without altering the method. In various embodiments, the methods can be scheduled to run based on predetermined events, and/or can run continually during operation of the vehicle. 
     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 exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the disclosure in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the exemplary embodiment or exemplary embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope of the disclosure as set forth in the appended claims and the legal equivalents thereof.