Adaptive user-specific automated driver assistance system warning

Abstract

An ADAS and method of providing user-specific ADAS warnings, each involving: determining an identity of a driver of a vehicle; accessing a memory configured to store a set of user profiles, each user profile defining a set of ADAS warnings; identifying a target user profile based on whether the driver identity corresponds to any of the set of user profiles, including accessing any of the set of stored user profiles or creating and storing a new user profile; and during a period of time after identifying the target user profile, updating the set of ADAS warnings defined by the target user profile based on operation of the vehicle, and providing ADAS warnings based on the set of ADAS warnings defined by the target user profile.

Description

Technical Field

[0001] This disclosure generally relates to automated driver assistance systems (ADAS) for vehicles, and more specifically to adaptive user-specific ADAS warnings. Background Technology

[0002] Automated Driver Assistance Systems (“ADAS”) are electronic systems configured to assist a driver in operating a vehicle (driving, parking, etc.). Examples of ADAS functions include, but are not limited to, adaptive cruise control (ACC), collision avoidance, lane departure and blind spot monitoring, and lane keeping or lane centering. One aspect of ADAS functions may include warnings to the vehicle’s driver, such as visual displays, audible sounds, tactile feedback, or some combination thereof. It will be understood that different drivers may react differently to different warnings. However, conventional ADAS system warnings are often default or pre-set settings. However, such user-general warnings may not be the most appropriate way to draw the attention of a vehicle-specific driver. Therefore, there are opportunities for improvement in this area.

[0003] The background description provided herein is for the purpose of generally presenting the context of this disclosure. The inventors’ work currently mentioned to the extent described in this background section, and aspects described at the time of filing as prior art, are neither expressly nor implicitly acknowledged as prior art to this disclosure. Summary of the Invention

[0004] According to one aspect of this disclosure, an Automated Driver Assistance System (ADAS) for a vehicle is presented. In one exemplary implementation, the ADAS includes: one or more systems configured to determine a set of parameters indicating the identity of a driver of the vehicle; and a controller configured to: determine the driver identity based on the set of parameters; access a memory configured to store a set of user profiles, each user profile defining a set of ADAS warnings; and identify a target user profile based on whether the driver identity corresponds to any user profile in the set of user profiles, including: when the driver identity does not correspond to any user profile in the set of user profiles, creating a target user profile and setting the target user profile as the target user profile in the set of user profiles. A user profile in the profile is stored in memory, wherein a set of ADAS warnings defined by the target user profile includes default or predetermined ADAS warnings, and when the driver identity corresponds to a user profile in the set of user profiles, the user profile is accessed as the target user profile, wherein the set of ADAS warnings defined by the target user profile includes user-specific ADAS warnings for the driver of the vehicle; and during the period following the identification of the target user profile: updating the set of ADAS warnings defined by the target user profile based on the operation of the vehicle, and providing ADAS warnings based on the set of ADAS warnings defined by the target user profile.

[0005] In some implementations, the controller is configured to update a specific ADAS warning from a set of ADAS warnings based on the driver's response rate to that specific ADAS warning and a calibrable response rate threshold. In other implementations, the controller is configured to update that specific ADAS warning from a set of ADAS warnings based on the number of instances of driver failure to respond to that specific ADAS warning and a calibrable threshold for instances of failure to respond.

[0006] In some implementations, the controller is configured to update a set of ADAS warnings based on other driver-specific factors monitored by a driver monitoring system, including at least one of the following: (i) the driver's gaze relative to the road, (ii) the driver's level of drowsiness, and (iii) the driver's health status. In some implementations, the controller is configured to update a set of ADAS warnings based on other non-driver-specific factors, including at least one of the following: (i) the current road traffic volume level and (ii) the current road construction level.

[0007] In some implementations, the controller is configured to update a specific ADAS warning from the set of ADAS warnings by changing the output type of the ADAS warning. In some implementations, the output type of the ADAS warning is one of visual output, audible output, and haptic output. In some implementations, one or more systems include a driver monitoring system configured to monitor the driver of the vehicle.

[0008] According to another aspect of this disclosure, a method for determining and providing adaptive user-specific ADAS warnings for vehicles is proposed. In one exemplary implementation, the method includes: determining the driver identity of the vehicle by a vehicle controller; accessing a memory configured to store a set of user profiles, each user profile defining a set of ADAS warnings; identifying a target user profile by the controller based on whether the driver identity corresponds to any user profile in the set of user profiles, including: creating a target user profile and storing the target user profile as one of the user profiles in the memory when the driver identity does not correspond to any user profile in the set of user profiles, wherein the set of ADAS warnings defined by the target user profile includes default or predetermined ADAS warnings; and accessing the user profile as the target user profile when the driver identity corresponds to one of the user profiles in the set of user profiles, wherein the set of ADAS warnings defined by the target user profile includes user-specific ADAS warnings for the vehicle's driver; and during a period following the identification of the target user profile: updating the set of ADAS warnings defined by the target user profile by the controller based on vehicle operation, and providing ADAS warnings by the controller based on the set of ADAS warnings defined by the target user profile.

[0009] In some implementations, updating a specific ADAS warning within a set of ADAS warnings is based on the driver's response rate to that specific ADAS warning and a calibrable response rate threshold. In other implementations, updating a specific ADAS warning within a set of ADAS warnings is based on the number of instances where the driver fails to respond to that specific ADAS warning and a calibrable threshold for instances of failed responses.

[0010] In some implementations, a set of ADAS warnings is updated based on other driver-specific factors monitored by a driver monitoring system, including at least one of the following: (i) the driver's gaze relative to the road, (ii) the driver's level of drowsiness, and (iii) the driver's health status. In some implementations, a set of ADAS warnings is updated based on other non-driver-specific factors, including at least one of the following: (i) the current road traffic volume level and (ii) the current road construction level.

[0011] In some implementations, updating a specific ADAS warning within a set of ADAS warnings involves changing the output type of the ADAS warning. In some implementations, the output type of the ADAS warning is one of visual, audible, and haptic output. In some implementations, determining the vehicle's driver identity is performed using a driver monitoring system configured to monitor the vehicle's driver.

[0012] According to another aspect of this disclosure, an ADAS for a vehicle is presented. In one exemplary implementation, the ADAS includes: an identity determination device for determining a driver's identity; a user profile storage device for accessing and storing a set of user profiles, each user profile defining a set of ADAS warnings; and a target user profile identification device for identifying a target user profile based on whether the driver's identity corresponds to any user profile in the set of user profiles, including: when the driver's identity does not correspond to any user profile in the set of user profiles, creating a target user profile and storing the target user profile as one of the user profiles in the set of user profiles in the user profile storage device, wherein the target user profile defines... The set of ADAS warnings defined includes default or predetermined ADAS warnings, and access to a user profile as a target user profile when the driver's identity corresponds to a user profile in a set of user profiles, wherein the set of ADAS warnings defined by the target user profile includes user-specific ADAS warnings for the driver of the vehicle; an ADAS warning updating device for updating the set of ADAS warnings defined by the target user profile based on the vehicle's operation during a period of time after the target user profile is identified; and an ADAS warning providing device for providing ADAS warnings based on the set of ADAS warnings defined by the target user profile.

[0013] In some implementations, the ADAS warning updating device updates a specific ADAS warning in a set of ADAS warnings based on the driver's response rate to a specific ADAS warning and a calibrable response rate threshold. In some implementations, the ADAS warning updating device updates a specific ADAS warning in a set of ADAS warnings based on the number of instances of driver failure to respond to a specific ADAS warning and a calibrable failure instance threshold. In some implementations, the ADAS warning updating device updates a specific ADAS warning in a set of ADAS warnings by changing the output type of the ADAS warning, wherein the output type of the ADAS warning is one of visual output, audible output, and tactile output.

[0014] Further applicability of this disclosure will become apparent from the detailed description provided below. It should be understood that the specific embodiments and examples are intended for illustrative purposes only and are not intended to limit the scope of this disclosure. Attached Figure Description

[0015] This disclosure will be more fully understood through detailed description and the accompanying drawings, in which:

[0016] Figure 1 This is a functional block diagram of a vehicle having an example Automated Driver Assistance System (ADAS) according to the principles of this disclosure; and

[0017] Figure 2 This is a flowchart of an example method for determining and providing adaptive user-specific ADAS warnings for a vehicle based on the principles of this disclosure. Detailed Implementation

[0018] As discussed above, there are opportunities for improvement in the field of Advanced Driver Assistance Systems (ADAS) for vehicles. Therefore, this paper proposes improved vehicle ADAS and corresponding methods. These techniques provide adaptive, user-specific ADAS warnings, which can improve the driver experience and, consequently, safety due to improved driver attention or responsiveness. For example, some drivers may be less responsive to certain default or pre-defined ADAS warnings, potentially leading to unresponsiveness when their attention is required (such as taking over vehicle control during specific situations). Therefore, the ADAS and corresponding methods in this paper match the driver's identity with a stored profile (or, if no stored profile exists, create a new one). This profile is then used to provide user-specific ADAS warnings and is periodically updated over time based on the driver's responsiveness to them. Non-limiting examples of ADAS functions that can utilize these adaptive driver-specific ADAS warnings include: adaptive cruise control (ACC), collision avoidance, lane departure and blind spot monitoring, and lane keeping or lane centering, but it will be understood that these techniques can be applied to any suitable vehicle ADAS function or similar function (e.g., driver takeover, or DTO function).

[0019] Now for reference Figure 1The figure illustrates a functional block diagram of an example vehicle 100 having an ADAS according to the principles of this disclosure. Vehicle 100 includes a powertrain 104 (engine, electric motor, combinations thereof, etc.) that generates drive torque and transmits the drive torque (e.g., via a transmission) to the drivetrain 108 of vehicle 100 for propulsion. Controller 112 controls the operation of vehicle 100, including controlling powertrain 104 to generate the desired amount of drive torque (e.g., based on driver torque requests (such as driver torque requests received via the accelerator pedal)). Controller 112 is also configured to perform at least a portion of the ADAS technology of this disclosure. Controller 112 locally stores a driver ADAS profile at internal or external memory (MEM) 116 (e.g., non-volatile memory), or stores and retrieves driver ADAS or "user profiles" from remote storage (e.g., a remote server) via network 120. Controller 112 utilizes a driver monitoring system 124 to determine the identity of the driver of vehicle 100. The driver monitoring system 124 includes a system of sensors (multiple infrared sensors, multiple cameras, etc.) that are typically operated to monitor the driver’s attention.

[0020] For the purposes of this disclosure, driver monitoring system 124 is configured to determine a set of characteristics of the driver and subsequently match these characteristics against a user profile. A non-limiting example of this set of characteristics is facial recognition features (interocular distance, facial shape, etc.). While this document specifically describes a driver monitoring system as monitoring the driver of a vehicle for the purpose of identifying the driver, it will be appreciated that additional or other systems may be used to determine the driver's identity. These other systems may include, for example, but not limited to, voice identification, fingerprint identification, telephone identification, etc. For example, only one mobile phone may be detected when the vehicle is started, and the identity connected to that mobile phone (e.g., a user profile) may be determined to be the driver's identity.

[0021] As will be understood, drivers may have to selectively join to allow their identity to be monitored and matched as described herein. When a driver's identity matches a stored user profile, that user profile ("target user profile") is retrieved for subsequent use. However, when a driver's identity does not match any stored user profile, a new driver user profile is created and subsequently used (i.e., used as the target user profile). The target user profile defines a set of ADAS warnings. For existing user profiles retrieved, these ADAS warnings are likely already tuned or calibrated for that particular driver. For newly created user profiles, the ADAS warnings will be default or pre-defined ADAS warnings (e.g., for a general user), and these warnings can then be adjusted over time to be tuned or calibrated for that particular driver. Controller 112 will use the ADAS warnings specified by the target user profile to output ADAS warnings to the driver during operation of vehicle 100.

[0022] As previously discussed and described in more detail below, non-limiting examples of these types of ADAS warnings include visual, audible, and tactile outputs to the driver via driver interface 128. Non-limiting examples of components of driver interface 128 include visual actuators (such as touch displays and lights (e.g., lights or dashboard)), audible actuators (such as speakers), and tactile actuators (e.g., vibration devices). Controller 112, memory 116 or network 120, driver monitoring system 124, and driver interface 128 may be collectively referred to as ADAS system 132 of vehicle 100, but it will be understood that ADAS system 132 may include other components (e.g., other sensors, steering actuators, acceleration / braking actuators, etc.). Over time, controller 112 may update these ADAS warnings in the target user profile based on the driver's reaction to the ADAS warnings during operation of vehicle 100. For example, some ADAS warnings may not attract the driver's attention, and therefore, the severity of ADAS warnings in the target profile may be increased or changed (e.g., from visual warnings to audible or tactile warnings).

[0023] Now for reference Figure 2 The figure illustrates a flowchart of an example method 200 for determining and providing user-specific ADAS warnings for a vehicle, based on the principles of this disclosure. Although referenced... Figure 1Method 200 is described for vehicle 100, but it will be understood that method 200 can be applied to any suitable vehicle. As previously discussed, a key safety aspect of autonomous driving is the driver's timely response when driver attention is required. For various reasons (inattention to the road, inclement weather, sensor unavailability, diagnostic errors, etc.), the driver is frequently asked to take over control of vehicle 100, a process known as a driver takeover (DTO) request. There are also other normal warnings (such as forward collision warnings, lane departure warnings, etc.) designed to instruct the driver to exercise the control he or she already possesses. These ADAS alerts or warnings are typically set to occur at specific times and are identical to each driver (type, intensity, etc.). This is also referred to herein as a default or pre-set ADAS warning, which can be configured based on aggregated data instructing a general driver. However, driver-specific ADAS warnings would be more desirable because they are more effective across a wide range of drivers due to their personalization to each specific driver.

[0024] Method 200 begins at 204, where driver identity information is collected or aggregated by controller 112 using driver monitoring system (DMS) 124. As previously discussed, this information may be a set of features (e.g., facial recognition features) indicating the driver's identity. At 208, controller 112 then attempts to match the driver's identity with one of a set of stored user profiles (e.g., stored in memory 116 or via network 120). When a match is found, method 200 proceeds to 212. Otherwise, method 200 proceeds to 220. At 212, controller 112 accesses / retrieves the matched user profile (target user profile), and controller 112 loads a set of ADAS warnings for the target user profile, which may have been customized, at least to some extent, for that particular driver (e.g., based on previous driving history). At 216, controller 112 monitors the driver's responsiveness to the set of ADAS warnings for the target user profile during operation of vehicle 100. This monitoring can occur, for example, within a predetermined time period or mileage (e.g., 50 miles) of a worthwhile driving activity. Then, method 200 proceeds to 228.

[0025] When the driver's identity does not match any of the stored user profiles, method 200 proceeds to 220, where controller 112 creates and stores a new user profile (target user profile) with default or predetermined ADAS warnings (e.g., for a general driver) loaded for use. At 224, controller 112 monitors the driver's responsiveness to a set of ADAS warnings from the target user profile during operation of vehicle 100. Method 200 then proceeds to 228. At 228, controller 112 determines whether any warning in the set of ADAS warnings needs to be adjusted. This can be determined in various ways. For example, controller 112 may adjust a particular ADAS warning if the driver is unresponsive to it for longer than a calibrable response rate or time threshold. Alternatively, for example, controller 112 may adjust a particular ADAS warning if the number of instances of the driver being unresponsive to it exceeds the number of calibrable response failures. Whether the predetermined time period or predetermined mileage for monitoring has occurred can also be a factor in determining whether further adjustments are needed (i.e., adjustments may not have been performed if the monitoring duration / data is insufficient). When adjustments are needed, controller 112 performs the adjustment at 232, and method 200 ends or returns to 204. When adjustments are not needed, method 200 ends or returns to 204.

[0026] The term "driver responsiveness" as used herein can refer to whether a driver takes timely and appropriate action to mitigate a warning or alert. Such adjustments at 232 can include increasing the intensity or severity of a specific ADAS warning and / or changing its output type (visual → auditory, auditory → tactile, etc.). Other factors that may affect driver responsiveness can also be considered, such as gaze relative to the road, level of drowsiness, driver health, and current traffic volume and / or construction level. For example, when other factors (such as high traffic volume / construction level) may affect driver responsiveness, no changes or less extreme changes to the ADAS warning may be made. Different types and intensities of ADAS warnings can also be tested to determine the most effective means of alerting a particular driver (voice ADAS warnings, displayed text ADAS warnings, light ADAS warnings, audible ADAS warnings, etc.). For Human-Machine Interface (HMI) warnings, they can be adapted so that subsequent alerts or warnings are changed to learn how the driver will react. It will be understood that other factors can further influence how ADAS warnings are adjusted. For example, a driver might set the vehicle's audio system to a relatively high volume, which could result in louder ADAS warnings or different types of ADAS warnings (e.g., light-based ADAS warnings). Weather conditions (snow / ice, rain, etc.) can also influence how a driver is expected to respond to a particular ADAS warning.

[0027] While the foregoing describes changing the type of ADAS warning and / or increasing the severity or intensity of an ADAS warning, it will also be appreciated that ADAS warnings can be adjusted to be less severe or less intense based on the driver's responsiveness to a particular ADAS warning. For example, a driver may be highly responsive to a particular audible ADAS warning, and therefore the controller 112 may potentially reduce the severity or intensity (e.g., volume) of that particular ADAS warning. Such a determination can be made, for example, when a particular ADAS warning is more severe or more intense than the corresponding default or predetermined ADAS warning (e.g., for a typical driver). While a single type of ADAS warning has been described, it will also be appreciated that a particular ADAS warning may include multiple types of output (e.g., audible and visual output) to increase the likelihood of a driver response. For example, by providing multiple types of output simultaneously, the likelihood of a driver responding may be higher.

[0028] Example embodiments are provided so that this disclosure will be thorough and will fully convey the scope of protection to those skilled in the art. Numerous specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of embodiments of this disclosure. It will be apparent to those skilled in the art that the example embodiments may be embodied in many different forms without requiring the specific details, and should not be construed as limiting the scope of this disclosure. In some example embodiments, well-known processes, well-known device structures, and well-known techniques are not described in detail.

[0029] The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the” may also be intended to include the plural forms unless the context clearly indicates otherwise. The terms “and / or” include any and all combinations of one or more of the associated listed items. The terms “comprises,” “comprising,” “including,” and “having” are inclusive and therefore specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. Unless expressly identified as an order of execution, the method steps, processes, and operations described herein should not be construed as requiring them to be performed in the specific order discussed or shown. It should also be understood that additional or alternative steps may be employed.

[0030] While the terms first, second, third, etc., may be used herein to describe various elements, components, regions, layers, and / or portions, these elements, components, regions, layers, and / or portions should not be limited by these terms. These terms may be used only to distinguish one element, component, region, layer, or portion from another. Unless the context clearly indicates otherwise, terms such as “first,” “second,” and other numerical terms used herein do not imply order or sequence. Therefore, the first element, component, region, layer, or portion discussed below may be referred to as a second element, component, region, layer, or portion without departing from the teachings of the exemplary embodiments.

[0031] As used herein, the term "module" may refer to, be part of, or include: application-specific integrated circuits (ASICs); electronic circuits; combinational logic circuits; field-programmable gate arrays (FPGAs); storage of executable code or processes in a processor or a distributed network of processors (shared, dedicated, or grouped) and a networked cluster or data center; other suitable components that provide the described functionality; or a combination of some or all of the foregoing, such as in a system-on-a-chip. The term "module" may also include memory (shared, dedicated, or grouped) storing code executed by one or more processors.

[0032] As used above, the term "code" can include software, firmware, bytecode, and / or microcode, and can refer to programs, routines, functions, classes, and / or objects. As used above, the term "shared" means that some or all of the code from multiple modules can be executed using a single (shared) processor. Additionally, some or all of the code from multiple modules can be stored in a single (shared) memory. As used above, the term "grouped" means that some or all of the code from a single module can be executed using a group of processors. Additionally, a set of memory can be used to store some or all of the code from a single module.

[0033] The techniques described herein can be implemented by one or more computer programs executed by one or more processors. The computer program includes computer-executable instructions stored on a non-transient tangible computer-readable medium. The computer program may also include stored data. Non-limiting examples of non-transient tangible computer-readable media are non-volatile memory, magnetic storage, and optical storage.

[0034] Certain parts of the above description present the techniques described herein based on the algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are means by which those skilled in the art of data processing effectively communicate the substance of their work to others skilled in the art. Although these operations are described functionally or logically, they should be understood as being implemented by computer programs. Furthermore, it has repeatedly proven convenient, without loss of generality, to arrange these operations as modules or to name them by function.

[0035] Unless otherwise specified, as is apparent from the foregoing discussion, it should be understood that the discussion throughout the specification using terms such as “processing,” “calculating,” “calculating,” “determining,” and “displaying” refers to the actions and processes of a computer system or similar electronic computing device that manipulate and transform data represented as physical (e.g., electronic) quantities within computer system memory and registers or other such information storage, transmission, or display devices.

[0036] Certain aspects of the described technology include processing steps and instructions described herein in algorithmic form. It should be noted that the described processing steps and instructions may be embodied in software, firmware, or hardware, and when embodied in software, may be downloaded to reside on and be operated from different platforms used by a real-time network operating system.

[0037] This disclosure also relates to means for performing the operations described herein. Such means may be specifically configured for a desired purpose, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored on a computer-readable medium accessible to the computer. Such computer programs may be stored in tangible computer-readable storage media, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic cards or optical cards, application-specific integrated circuits (ASICs), or any type of medium suitable for storing electronic instructions, each coupled to a computer system bus. Furthermore, a computer referred to herein may include a single processor or may be an architecture employing multiple processors to enhance computing power.

[0038] The algorithms and operations presented herein are not inherently related to any particular computer or other device. Various general-purpose systems may also be used with programs based on the teachings herein, or it may prove convenient to construct more specialized devices to perform the required method steps. The necessary structures for various such systems, as well as equivalent variations, will be apparent to those skilled in the art. Furthermore, this disclosure does not refer to any particular programming language. It should be understood that the teachings of this disclosure as described herein can be implemented using various programming languages, and any references to a particular language are provided for the purpose of disclosing implementations and best practices of the invention.

[0039] The foregoing description of embodiments has been provided for purposes of illustration and description. This description is not intended to be exhaustive or limiting of this disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but are interchangeable and may be used in selected embodiments where applicable, even if not specifically shown or described. The same parts may also be varied in various ways. Such variations are not considered to depart from this disclosure, and all such modifications are intended to be included within the scope of the invention.

Claims

1. An Advanced Driver Assistance System (ADAS) for a vehicle, the ADAS comprising: One or more systems configured to determine a set of parameters indicating the identity of the driver of a vehicle; as well as Controller, the controller being configured to: The driver's identity is determined based on the set of parameters; Access is configured to store a set of user profiles, each user profile defining a set of ADAS warnings; Identifying a target user profile based on whether the driver's identity corresponds to any of the user profiles in the set includes: When the driver identity does not correspond to any of the user profiles in the set of user profiles, a target user profile is created and stored in the memory as one of the user profiles in the set of user profiles, wherein the set of ADAS warnings defined by the target user profile includes a set of default or predetermined ADAS warnings, and When the driver identity corresponds to one of the user profiles in the set of user profiles, the user profile is accessed as the target user profile, wherein the set of ADAS warnings defined by the target user profile includes a set of user-specific ADAS warnings for the driver of the vehicle. as well as During the period following the identification of the target user profile: Update the set of ADAS warnings defined by the target user profile based on the vehicle's operation, and ADAS warnings are provided based on the set of ADAS warnings defined by the target user profile.

2. The ADAS as described in claim 1, characterized in that, The controller is configured to update a specific ADAS warning in a set of ADAS warnings in response to the driver's response rate to a specific ADAS warning exceeding a calibrable response rate threshold.

3. The ADAS as described in claim 1, characterized in that, In response to providing a threshold number of times a specific ADAS warning in the set of ADAS warnings is reached, the controller is configured to update the specific ADAS warning in the set of ADAS warnings based on the number of instances of the driver's failed response to the specific ADAS warning and a calibrable threshold for failed response instances.

4. The ADAS as described in claim 1, characterized in that, The one or more systems include a driver monitoring system configured to monitor the driver of the vehicle, and wherein the controller is configured to update the set of ADAS warnings based on other driver-specific factors monitored by the driver monitoring system, the other driver-specific factors including at least one of the following: (i) the driver's gaze relative to the road, (ii) the driver's level of drowsiness, and (iii) the driver's health status.

5. The ADAS as described in claim 1, characterized in that, The controller is configured to update the set of ADAS warnings based on other non-driver-specific factors, including at least one of the following: (i) current road traffic level and (ii) current road construction level.

6. The ADAS as described in claim 1, characterized in that, The controller is configured to update a specific ADAS warning in the set of ADAS warnings by changing the output type of the ADAS warning.

7. The ADAS as described in claim 6, characterized in that, The output type of the ADAS warning is one of visual output, audible output, and tactile output.

8. The ADAS as described in claim 1, characterized in that, At least some of the warnings in the set of user-specific ADAS warnings have a different degree or severity compared to the corresponding warnings in the set of default or pre-defined ADAS warnings.

9. The ADAS as described in claim 8, characterized in that, The set of user-specific ADAS warnings is uniquely tuned for a specific driver of the vehicle, so that the specific driver responds to the set of user-specific ADAS warnings as much as possible.

10. A method for determining and providing an adaptive user-specific automated driver assistance system (ADAS) warning for a vehicle, the method comprising: The driver's identity is determined by the vehicle's controller; The controller accesses a memory configured to store a set of user profiles, each user profile defining a set of ADAS warnings; The controller identifies the target user profile based on whether the driver's identity corresponds to any of the user profiles in the set of user profiles, including: When the driver identity does not correspond to any of the user profiles in the set of user profiles, a target user profile is created and stored in the memory as one of the user profiles in the set of user profiles, wherein the set of ADAS warnings defined by the target user profile includes a set of default or predetermined ADAS warnings, and When the driver identity corresponds to one of the user profiles in the set of user profiles, the user profile is accessed as the target user profile, wherein the set of ADAS warnings defined by the target user profile includes a set of user-specific ADAS warnings for the driver of the vehicle. as well as During the period following the identification of the target user profile: The controller updates the set of ADAS warnings defined by the target user profile based on the vehicle's operation. The controller provides ADAS warnings based on the set of ADAS warnings defined by the target user profile.

11. The method as described in claim 10, characterized in that, Updating a specific ADAS warning in the set of ADAS warnings is performed in response to the driver's response rate to the specific ADAS warning exceeding a calibrable response rate threshold.

12. The method as described in claim 10, characterized in that, Updating a specific ADAS warning in the set of ADAS warnings is performed in response to providing the specific ADAS warning a threshold number of times it is reached, and is based on the number of instances of the driver's response to the specific ADAS warning failing and a threshold for calibrated response failure instances.

13. The method as described in claim 10, characterized in that, The identification of the driver of the vehicle is performed using a driver monitoring system configured to monitor the driver of the vehicle, wherein the set of ADAS warnings is updated based on other driver-specific factors monitored by the driver monitoring system, the other driver-specific factors including at least one of the following: (i) the driver's gaze relative to the road, (ii) the driver's level of drowsiness, and (iii) the driver's health status.

14. The method as described in claim 10, characterized in that, The ADAS warning set is updated based on other non-driver-specific factors, including at least one of the following: (i) current road traffic level and (ii) current road construction level.

15. The method as described in claim 10, characterized in that, Updating a specific ADAS warning within the set of ADAS warnings includes changing the output type of the ADAS warning.

16. The method as described in claim 15, characterized in that, The output type of the ADAS warning is one of visual output, audible output, and tactile output.

17. An Advanced Driver Assistance System (ADAS) for a vehicle, the ADAS comprising: An identity verification device is used to determine the identity of the driver of the vehicle; User profile storage device for accessing and storing a set of user profiles, each user profile defining a set of ADAS warnings; A target user profile identification device, used to identify a target user profile based on whether the driver's identity corresponds to any user profile in the set of user profiles, including: When the driver identity does not correspond to any of the user profiles in the set of user profiles, a target user profile is created and stored as one of the user profiles in the user profile storage device, wherein the set of ADAS warnings defined by the target user profile includes a set of default or predetermined ADAS warnings, and When the driver identity corresponds to one of the user profiles in the set of user profiles, the user profile is accessed as the target user profile, wherein the set of ADAS warnings defined by the target user profile includes a set of user-specific ADAS warnings for the driver of the vehicle. ADAS warning update device, used to update the set of ADAS warnings defined by the target user profile based on the vehicle's operation during a period following the identification of the target user profile; and An ADAS warning providing device for providing ADAS warnings based on a set of ADAS warnings defined by the target user profile.

18. The ADAS as described in claim 17, characterized in that, The ADAS warning update device updates the specific ADAS warning in the set of ADAS warnings in response to the driver's response rate to a specific ADAS warning exceeding a calibrable response rate threshold.

19. The ADAS as described in claim 17, characterized in that, In response to providing a threshold number of times a specific ADAS warning in the set of ADAS warnings is reached, the ADAS warning updating device updates the specific ADAS warning in the set of ADAS warnings based on the number of instances of the driver's failed response to the specific ADAS warning and a calibrable threshold for failed response instances.

20. The ADAS as described in claim 17, characterized in that, The ADAS warning update device updates a specific ADAS warning in the set of ADAS warnings by changing the output type of the ADAS warning, wherein the output type of the ADAS warning is one of visual output, audible output, and tactile output.

Images