User interface for controlling safety-critical functions of a vehicle

Abstract

A user interface (100) for controlling a function of a vehicle is provided. The user interface comprises: a manual input device (105, 107a-c, 109a-c) for generating a user input signal when manually actuated by a user; and one or more proximity sensors (103a-f) arranged near the manual input device (105, 107a-c, 109a-c), wherein each proximity sensor (103a-f) is configured to generate a proximity sensor signal when a hand is present near the proximity sensor (103a-f). In addition, the user interface (100) comprises a processing circuit (101) for controlling the function of the vehicle based on the user input signal and the one or more proximity sensor signals.

Description

Technical Field

[0001] The present invention relates generally to automotive safety. More particularly, the present invention relates to a user interface for controlling safety-critical functions of a vehicle and a vehicle including such a user interface. Background Art

[0002] When a vehicle is driving on the road, especially at high speeds, if the driver performs complex operations on the in-vehicle infotainment (IVI) system and the center console in the cockpit, distracting them from monitoring the road, this can lead to high safety risks. To restrict certain types of IVI and cockpit operations at high speeds, traditional solutions typically simply prohibit these operations and prevent them from being executed.

[0003] For example, changes to certain vehicle settings can be prohibited when a speed threshold is exceeded, forcing the driver to monitor road conditions with full concentration without distraction. Another example is prohibiting the execution of certain applications, such as communication tools or video players, while the car is moving. Prohibited operations can include operations performed directly on the in-vehicle infotainment system (IVI), instrument cluster (IC), or cockpit console devices with manual control elements (such as touch screens, buttons, or knobs), as well as operations performed on steering wheel buttons.

[0004] However, this conventional approach suffers from a drawback: it doesn't distinguish between actions performed by the driver and another passenger. For example, if a co-pilot's actions don't pose a safety threat, they should be permitted for entertainment and convenience purposes. For example, entering a new destination address for navigation at high speeds can be life-threatening due to driver distraction. However, if a co-pilot could perform this task for the driver, it would be significantly more effective in instantly updating the navigation destination and quickly guiding the driver on a new route.

[0005] In view of the foregoing, there is a need for improved user interfaces for controlling safety-critical functions of a vehicle. Summary of the Invention

[0006] It is an object of the present invention to provide an improved user interface for controlling safety-critical functions of a vehicle.

[0007] The above and other objects are achieved by the subject matter claimed in the independent claims. Other implementations are apparent from the dependent claims, the description and the drawings.

[0008] In general, the embodiments disclosed herein achieve driving safety by preventing the driver from operating the vehicle's console user interface while the vehicle is moving to avoid distraction. On the other hand, the operating actions can still be performed by other passengers of the vehicle, especially the co-pilot. In this regard, the embodiments disclosed herein distinguish whether the operations on the vehicle's in-vehicle infotainment system (IVI) and the cockpit are performed by the driver or the co-pilot of the vehicle. The co-pilot can perform these operations and they can take effect, while the driver's operations may be rejected and a safety alert message will be generated for the driver. This can maintain the convenience of the co-pilot's operations while avoiding life-threatening operations by the driver.

[0009] Thus, an improved user interface is provided that can control functions such as the use of the vehicle's electronic systems in a safe manner. This achieves driving safety by preventing the driver from operating the vehicle's console interface while the vehicle is in motion, but enabling the co-driver to operate the console interface.

[0010] More specifically, according to a first aspect, a user interface for controlling functions of a vehicle is provided. The functions of the vehicle may include safety-critical functions and safety-non-critical functions of the vehicle.

[0011] The user interface includes a manual input device configured to generate a user input signal when manually actuated by a user. Furthermore, the user interface includes one or more proximity sensors disposed proximate to the manual input device, each proximity sensor configured to generate a proximity sensor signal when a user's hand is present proximate to the proximity sensor. Furthermore, the user interface includes processing circuitry configured to control the function of the vehicle based on the user input signal and the one or more proximity sensor signals.

[0012] In another possible implementation of the first aspect, the processing circuit is configured to control the function of the vehicle in the following manner:

[0013] generating a user identification signal (e.g., a user identification flag) based on the one or more proximity sensor signals, wherein the user identification signal indicates whether the user is likely to be a driver of the vehicle;

[0014] The function of the vehicle is controlled based on the user identification signal.

[0015] In another possible implementation of the first aspect, generating the user identification signal includes:

[0016] initiating a time frame when the one or more proximity sensor signals indicate that the hand is located on the driver's side of the vehicle;

[0017] During the time frame, the user identification signal is generated to indicate that the user is the driver of the vehicle.

[0018] In another possible implementation of the first aspect, the processing circuit is used to terminate or block the function of the vehicle when the user identification signal indicates that the user is the driver of the vehicle, and the function is a safety-critical function, that is, a function whose manual operation may cause safety risks.

[0019] In another possible implementation of the first aspect, the processing circuit is further configured to generate an alert for the user when the user identification signal indicates that the user is the driver of the vehicle, and the function is a safety-critical function, i.e., a function whose manual operation may cause a safety risk. The alert may include an audible signal, a visible signal, or both.

[0020] In another possible implementation of the first aspect, the manual input device is located in a center console or a front console of the vehicle.

[0021] In another possible implementation manner of the first aspect, at least one of the one or more proximity sensors is arranged on a driver's side of the vehicle.

[0022] In another possible implementation manner of the first aspect, at least one of the one or more proximity sensors is arranged on a passenger side of the vehicle.

[0023] In another possible implementation manner of the first aspect, the processing circuit is integrated into the manual input device.

[0024] In another possible implementation of the first aspect, the manual input device includes one or more of the following input elements: a touch screen, a rotary knob, a button, a slider, a trackball, and a stick.

[0025] In another possible implementation of the first aspect, the processing circuit is used to control the function of the vehicle according to the user input signal, the one or more proximity sensor signals and the driving state of the vehicle.

[0026] In another possible implementation of the first aspect, the user interface is used to control a selected function among multiple functions of the vehicle, wherein each function has a function type, such as a safety-critical function and a safety-non-critical function, and the processing circuit is used to control the selected function of the vehicle based on the user input signal, the one or more proximity sensor signals and the function type of the selected function.

[0027] According to a second aspect, a vehicle, in particular a car, is provided, comprising the user interface according to the first aspect.

[0028] In another possible implementation of the second aspect, the manual input device of the user interface according to the first aspect is placed in the center console or front console of the vehicle according to the second aspect.

[0029] In another possible implementation of the second aspect, at least one of the one or more proximity sensors of the user interface according to the first aspect is arranged on a driver's side of the vehicle according to the second aspect.

[0030] In another possible implementation of the second aspect, at least one of the one or more proximity sensors of the user interface according to the first aspect is arranged on a passenger side of the vehicle according to the second aspect.

[0031] The following drawings and description set forth in detail one or more embodiments. Other features, objects, and advantages are apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The embodiments of the present invention will be described in more detail below with reference to the accompanying drawings and schematic diagrams, in which:

[0033] Figure 1 is a schematic diagram of a user interface for controlling vehicle functions provided by an embodiment;

[0034] Figure 2 is a schematic diagram of a user interface for controlling vehicle functions provided by another embodiment;

[0035] Figure 3 A flowchart of a process for controlling vehicle functions implemented by a user interface is provided in one embodiment.

[0036] In the following, identical reference numerals refer to identical or at least functionally equivalent features. DETAILED DESCRIPTION

[0037] In the following description, reference is made to the accompanying drawings that form a part hereof and that illustrate, by way of illustration, specific aspects of embodiments of the invention or in which embodiments of the invention may be used. It should be understood that embodiments of the invention may be used in other aspects and may include structural or logical variations not depicted in the accompanying drawings. Therefore, the following detailed description should not be taken in a limiting sense, and the scope of the invention is defined by the appended claims.

[0038] For example, it should be understood that the disclosure related to describing a method may also apply to a corresponding device or system for performing the method, and vice versa. For example, if one or more specific method steps are described, the corresponding device may include one or more units (e.g., functional units) to perform the one or more method steps described (e.g., one unit performs one or more steps, or multiple units perform one or more of the multiple steps respectively), even if the one or more units are not explicitly described or illustrated in the drawings. On the other hand, for example, if a specific device is described in terms of one or more units (e.g., functional units), the corresponding method may include a step to implement the function of the one or more units (e.g., one step to implement the function of one or more units, or multiple steps to implement the function of one or more of the multiple units respectively), even if the one or more steps are not explicitly described or illustrated in the drawings. In addition, it should be understood that unless otherwise expressly stated, the features of the various exemplary embodiments and / or aspects described herein may be combined with each other.

[0039] Figure 1 is a schematic diagram of a user interface 100 for controlling (ie, operating) functions of a vehicle, particularly a car. Figure 2 Another embodiment of a user interface 100 for controlling (ie, operating) functions of a vehicle, particularly a car, is shown.

[0040] exist Figure 1 and Figure 2 In the illustrated embodiment, user interface 100 includes multiple manual input devices, including a touch screen 105, rotatable control knobs 107a-c, and depressible control buttons 109a-c. Each manual input device is configured to generate a user input signal when manually actuated by a user. For example, touch screen 105 may generate a user input signal when a user's finger presses or slides. In one embodiment, the multiple manual input devices, including touch screen 105, rotatable control knobs 107a-c, and depressible control buttons 109a-c, may be located in a center console or front console of a vehicle.

[0041] like Figure 1 and Figure 2 As shown, the user interface 100 further includes proximity sensors 103a-f disposed near a plurality of manual input devices (i.e., the touch screen 105, the rotatable control knobs 107a, b, and the depressible control buttons 109a-c). Each proximity sensor 103a-f is configured to generate a corresponding proximity sensor signal when a user's hand is present near the proximity sensor 103a-f. As an example, in Figure 1 In the illustrated embodiment, the user interface 100 includes two proximity sensors 103a, 103b arranged near a plurality of manual input devices. Figure 2In the illustrated embodiment, the user interface 100 includes six proximity sensors 103a-f arranged near a plurality of manual input devices. It will be appreciated that the more proximity sensors 103a-f the user interface 100 includes, the better the user interface 100 will be able to detect the presence of an object, such as the presence of a user's hand operating a manual input device of the user interface 100.

[0042] In one embodiment, the user interface 100 may be arranged in the center console of a car, wherein the steering wheel and the driver's seat are located on the left side of the center console. In one embodiment, the user interface 100 may be arranged in the center console of a car, wherein the steering wheel and the driver's seat are located on the right side of the center console. Figure 1 and Figure 2 As shown, one or more of the proximity sensors 103a-f may be positioned on the driver's side of the vehicle, while other proximity sensors 103a-f may be positioned on the passenger side of the vehicle.

[0043] like Figure 1 and Figure 2 As shown, the user interface 100 also includes processing circuitry 101, which is used to control vehicle functions based on one or more user input signals provided by one or more manual input devices 105, 170a-c, 109a-c and proximity sensor signals provided by proximity sensors 103a-f. The processing circuitry 101 may include hardware and software. The hardware may include analog circuitry or digital circuitry, or both. The digital circuitry may include components such as an application-specific integrated circuit (ASIC), a field-programmable array (FPGA), a digital signal processor (DSP), or a general-purpose processor. In particular, the filters described herein may be implemented in hardware or software, or a combination of hardware and software. In one embodiment, the processing circuitry 101 includes one or more processors and non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code that, when executed by the one or more processors, causes the device user interface 100 to perform the operations or methods described herein.

[0044] In one embodiment, the function of the vehicle controlled by the processing circuit 101 of the user interface 100 based on one or more user input signals provided by one or more manual input devices 105, 170a-c, 109a-c and proximity sensor signals provided by proximity sensors 103a-f can be a software application, i.e., an APP executed by the processing circuit 101 of the user device 100 or by another electronic system of the vehicle.

[0045] In one embodiment, the processing circuitry 101 of the user interface 100 is configured to control a vehicle function by generating a user identification signal based on proximity sensor signals provided by a plurality of proximity sensors 103a-f, wherein the user identification signal indicates whether the user operating one or more manual input devices 105, 107a-c, 109a-c of the user interface 101 is the driver of the vehicle. In one embodiment, the user identification signal may be a flag or bit set by the processing circuitry 101. Furthermore, the processing circuitry 101 is configured to control the vehicle function based on the user identification signal. In one embodiment, the processing circuitry 101 is configured to terminate or block the vehicle function if the user identification signal indicates that the user is the driver of the vehicle. As used herein, a vehicle function is a function whose operation could potentially distract the driver of the vehicle. Furthermore, the processing circuitry 101 of the user interface 100 may be configured to generate an alert to the user if the function is a safety-critical function of the vehicle if the user identification signal indicates that the user is the driver of the vehicle.

[0046] In one embodiment, to generate the user identification signal, the processing circuit 101 of the user interface 100 is configured to initiate a time frame when one or more proximity sensor signals indicate that the hand operating the manual input device 105, 107a-c, 109a-c is located on the driver's side of the vehicle. During the time frame, the processing circuit 101 of the user interface 100 is configured to generate the user identification signal to indicate that the user is the driver of the vehicle.

[0047] In one embodiment, the processing circuitry 101 of the user interface may be integrated with the processing circuitry of one or more manual input devices 105, 107a-c, 109a-c for generating one or more user input signals.

[0048] The above embodiment improves driving safety by preventing the driver from operating the user interface 100 of the car while driving a vehicle (e.g., a car). On the other hand, the operation can still be performed by the co-driver using the user interface 100 of the car to control the functions of the car.

[0049] While the vehicle is moving, especially at high speeds, certain types of complex functions and / or operations (i.e., safety-critical functions of the vehicle) are considered distracting to the driver and pose a risk to road safety. Some examples of such distracting complex operations include: typing a destination address into a navigation application; attempting to understand vehicle settings and changing settings or preferences in the vehicle's human-machine interface (HMI); using certain types of software applications (also known as "apps") for specific purposes, such as chatting in text form with a messaging tool, watching videos in a video player, or playing computer games; and reading relatively long texts, such as user agreements and confirming consent.

[0050] On the other hand, simple functions and operations typically require very short operation time or require little distraction from the user's attention. Such functions and operations are not considered distracting and risky (referred to herein as non-safety-critical functions). Therefore, the driver can perform these operations while the vehicle is moving. For example, according to one embodiment, the allowed functions and operations, i.e., non-safety-critical functions of the vehicle, may include: opening or closing windows; turning on / off the air conditioning to adjust the vehicle's interior temperature; playing an audio file, or similar operations such as pausing, skipping, or selecting a track; and answering or making a Bluetooth hands-free call.

[0051] The main difference between complex functions and operations (i.e., safety-critical functions and operations) and simple functions and operations (i.e., safety-uncritical functions and operations) is that simple functions generally require only limited human-machine operation and quick operation of physical buttons or knobs. The driver is hardly distracted during operation. However, complex functions and operations require reading / understanding relatively complex content or entering a large amount of text into the user interface 100. The driver's attention can easily be diverted from road conditions to human-machine interaction for a relatively long time, thus distracting the driver. The embodiments disclosed herein can avoid driver distraction by prohibiting complex functions and operations, i.e., safety-critical functions, and warning the driver through audible or visible safety alarms.

[0052] Embodiments of the user interface 100 can implement a two-stage approach. In one embodiment, the user interface 100 can be configured to first distinguish whether a manual input operation was performed by the driver or the passenger of the vehicle based on one or more proximity sensor signals provided by one or more proximity sensors 103a-e. Furthermore, the processing circuitry 101 of the user interface 100 can be configured to combine this assessment with other traffic / vehicle information to identify whether the operation of the manual input device was used to operate a safety-critical function and to issue a safety alert to the driver. Thus, in one embodiment, the user interface 100 is configured to control a selected function from a plurality of vehicle functions, each of which is either a safety-critical function or a safety-non-critical function of the vehicle, wherein the processing circuitry 101 of the user interface 100 is configured to control the selected function of the vehicle based on a user input signal, one or more proximity sensor signals, and the function type of the selected function, i.e., whether the selected function is a safety-critical function or a safety-non-critical function. In another embodiment, the processing circuitry 101 of the user interface is configured to control the vehicle function based on the user input signal, one or more proximity sensor signals, and the vehicle's driving state (e.g., whether the vehicle is moving at a speed greater than or less than a speed threshold).

[0053] As described above, according to an embodiment, the user interface 100 is used to distinguish whether the operation of the user interface 100 (eg, the in-vehicle infotainment (IVI) system 100) is performed by the driver or the co-driver of the vehicle. Figure 1 In the illustrated embodiment, assuming a left-turn vehicle, if the driver extends their right arm and uses their right hand to operate within the control area of user interface 100, left proximity sensor 103a will detect the approach of their arm / hand, while right proximity sensor 103b will not. On the other hand, if the passenger attempts to operate within the control area of user interface 100, right proximity sensor 103b will be triggered, generating a proximity sensor signal, while left proximity sensor 103a will not be triggered. The triggering patterns of the left and right edge proximity sensors 103a-f can be used to identify whether the operation is originating from the left or right side, i.e., the driver's side or the passenger's side. A common operating pattern is when only one hand / arm is operating within the operating area at a time, meaning only one or more of the left or right proximity sensors 103a-d are triggered.

[0054] When proximity sensors 103a-f on both sides of user interface 100 are triggered, various possibilities exist. For example, according to one embodiment, a hand falls into the operating area while the arm is extended, without taking any action on manual input devices 105, 107a-c, or 109a-c. In another embodiment, the right or left hand of each person in the driver's seat and the passenger seat respectively extends into the operating area and simultaneously operates within it. In this case, regardless of whether the safety-threatening actions were actually performed by the driver, they may be deemed to have been performed by the driver and therefore prohibited for safety reasons.

[0055] In another embodiment, the processing circuit 101 of the user device 100 can be used to control vehicle functions based on other data (in addition to the one or more proximity sensor signals provided by the proximity sensors 103a-f and the one or more user input signals provided by the manual input devices 105, 107a-c, 109a-c), such as data provided by a gesture recognition mechanism implemented in the vehicle.

[0056] Figure 3 FIG. 3 is a flow chart of a process 300 for controlling vehicle functions implemented by the user interface 100 according to an embodiment. The process 300 includes the following steps.

[0057] First, the process 300 begins with a safety-critical operation / function of the vehicle, such as attempting to type a message into a chat window displayed on the touch screen 105 or enter a destination address into the vehicle's navigation system while the vehicle is moving at a high rate of speed. Figure 3 301).

[0058] The next step is to check whether the vehicle or road conditions are safe enough for such safety-critical functions / operations, assuming that the operation is performed by a driver who should be maximally focused on driving ( Figure 3 Block 303): In one embodiment, the processing circuit 101 of the user device 100 may use whether the vehicle speed exceeds a speed threshold as a metric, and the speed threshold may vary according to the corresponding application requirements. When the vehicle speed is very low or stationary, the operations may be considered risk-free and may be performed immediately. Otherwise, if the vehicle speed is above the threshold, the operation may be considered to have too high a safety risk, and it is necessary to determine who the operator is. Other road information that affects the driving state of the vehicle may also be collected to identify operational risks that distract the driver, such as dangerous and accident-prone sections specially marked in the navigation map, or overtaking vehicles in the next fast lane that are too crowded or too close, etc. The purpose of this step is to identify safety risks under the assumption that the driver is performing an operation and is distracted while driving.

[0059] After identifying the safety risk, the next step is to confirm whether the function / operation is performed by the driver or the co-pilot who initiates the operation ( Figure 3 If the function / operation is performed by the co-pilot, it is safe and the operation can be freely performed at any time ( Figure 3 Otherwise, it is determined that the driver's operation is unsafe and should be prohibited, and a visible or audible warning message is issued ( Figure 3 Finally, the process is completed ( Figure 3 311).

[0060] Those skilled in the art will understand that the "boxes" ("units") of the various figures (methods and devices) represent or describe the functions of an embodiment of the present invention (and not necessarily separate "units" in hardware or software), and therefore equally describe the functions or features of the device embodiments and the method embodiments (units are equivalent steps).

[0061] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described are merely exemplary. For example, unit division is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components can be merged or integrated into another system, or some features can be ignored or not performed. In addition, the mutual coupling or direct coupling or communication connection shown or described can be implemented through some interfaces. The direct coupling or communication connection between devices or units can be implemented through electronic, mechanical or other forms.

[0062] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one location, or may be distributed across multiple network units. Some or all of the units may be selected as needed to achieve the purpose of the embodiment.

[0063] In addition, the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

Claims

1. A user interface (100) for controlling functions of a vehicle, characterized in that The user interface (100) is used to control a selected function among a plurality of functions of the vehicle, wherein each function has a function type, and the function type is a safety-critical function type or a safety-non-critical function type, and the safety-critical function type includes a function whose manual operation may cause a safety risk; the user interface (100) includes: a manual input device (105, 107a-c, 109a-c) for generating a user input signal when manually actuated by a user; One or more proximity sensors (103a-f) arranged near the manual input device (105, 107a-c, 109a-c), each proximity sensor (103a-f) for generating a proximity sensor signal when a hand is present near the proximity sensor (103a-f); The processing circuit (101) is configured to generate a user identification signal based on the one or more proximity sensor signals, wherein the user identification signal indicates whether the user is a driver of the vehicle; The processing circuit (101) is further configured to terminate or block the function of the vehicle if the user identification signal indicates that the user is the driver of the vehicle, the function type of the selected function is a safety-critical function type, and the vehicle is moving at a speed greater than a preset speed threshold; If the user identification signal indicates that the user is the driver of the vehicle, the function type of the selected function is a safety-critical function type, the vehicle is moving at a speed less than a preset speed threshold, and information about the road the vehicle is currently traveling on includes road information that affects the safe driving state of the vehicle, then terminating or blocking the function of the vehicle; If the user identification signal indicates that the user is the driver of the vehicle, the function type of the selected function is a safety-critical function type, the vehicle is moving at a speed less than a preset speed threshold, and the information of the road the vehicle is currently traveling on does not include road information that affects the safe driving state of the vehicle, then executing the vehicle function; If the user identification signal indicates that the user is the driver of the vehicle, and the function type of the selected function is a safety non-critical function type, executing the vehicle function; Generating a user identification signal comprises: initiating a time frame when the one or more proximity sensor signals indicate that the hand is located on the driver's side of the vehicle; During the time frame, the user identification signal is generated to indicate that the user is the driver of the vehicle.

2. The user interface (100) according to claim 1, characterized in that The processing circuit (101) is further configured to generate an alert for the user when the user identification signal indicates that the user is the driver of the vehicle.

3. The user interface (100) according to any one of the preceding claims, characterized in that The manual input device (105, 107a-c, 109a-c) is located in the center console or the front console of the vehicle.

4. The user interface (100) according to claim 1, characterized in that At least one of the one or more proximity sensors (103a-f) is arranged on a driver's side of the vehicle.

5. The user interface (100) according to claim 4, characterized in that At least one of the one or more proximity sensors (103a-f) is arranged on a passenger side of the vehicle.

6. The user interface (100) according to claim 1, characterized in that The processing circuit (101) is integrated into the manual input device (105, 107a-c, 109a-c).

7. The user interface (100) according to claim 1, characterized in that The manual input device (105, 107a-c, 109a-c) includes one or more of the following input elements: a touch screen (105), a rotary knob (107a-c), a button (109a-c), a slider, a trackball, and a stick.

8. A vehicle, characterized in that: The method comprises a user interface (100) according to any one of claims 1 to 7.

Images