Vehicle and control method thereof

Abstract

A vehicle and a control method thereof are provided. A vehicle according to an exemplary embodiment of the present disclosure may include an input / output interface and a processor that, when a speed limiting function of the vehicle is activated, determines whether the activation of the speed limiting function is an error event, and, when it is determined that the activation of the speed limiting function is an error event, determines whether the activation of the speed limiting function is an error event. The processor outputs a notification through the input / output interface to deactivate the speed limiting function.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to Korean Patent Application No. 10-2024-0125799, filed on September 13, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Various embodiments of this disclosure relate to vehicles and control methods for detecting vehicle-related functions that may cause unexpected events. Background Technology

[0004] Recently, with the widespread use of driver assistance technologies and autonomous driving functions, vehicles have adopted acceleration functions (e.g., cruise control) to maintain the vehicle at a preset speed, and functions to limit the vehicle to a predetermined speed (e.g., speed limit).

[0005] However, as driver assistance features become increasingly diverse, drivers sometimes find it difficult to manipulate the interface to activate or deactivate (e.g., specific) driver assistance and autonomous driving features.

[0006] In an exemplary embodiment, a recently provided speed limit function (e.g., speed limiter) once activated is not (e.g., easily) deactivated by inputs that a driver typically attempts (such as the brake pedal or accelerator pedal). In an exemplary embodiment, the activated function is (e.g., only) released when a (e.g., specific) button on the steering wheel or the like is pressed.

[0007] When this speed limit function is activated due to the driver's unexpected behavior in road conditions such as highways (e.g., specific road conditions), the driver may become confused due to the (e.g., unfamiliar) controlled driving environment. Summary of the Invention

[0008] This disclosure relates to determining whether the activation of the speed limit function is an unintentional erroneous event by the driver when the speed limit function of the vehicle is activated, and providing a notification to deactivate the speed limit function when it is determined that the activation is an erroneous event.

[0009] The purpose of this disclosure is not limited to the purposes described herein, and other purposes not mentioned may be understood from the description herein.

[0010] Vehicles according to various embodiments of the present disclosure may include an input / output interface and a processor, wherein when the vehicle's speed limiting function is activated, the processor determines whether the activation of the speed limiting function is an error event, and when it is determined that the activation of the speed limiting function is an error event, the processor outputs a notification for disabling the speed limiting function through the input / output interface.

[0011] The processor can determine whether the activation of the speed limit function is an error event based on the first driving data and the second driving data. The first driving data is the driver's driving data before the speed limit function is activated, and the second driving data is the driver's driving data after the speed limit function is activated.

[0012] The processor can calculate an error score based on the first driving data and the second driving data to determine whether the activation of the speed limit function is an error event, and determine that the activation of the speed limit function is an error event when the error score is above a predetermined value.

[0013] The first driving data may include information about the number of times the driver used the vehicle's speed limit function within a first predetermined time period, and when calculating the error score, the processor may set the information about the number of times the driver used the vehicle's speed limit function as a weight.

[0014] The more often a driver uses the vehicle's speed limit function, the lower the processor can set its weight.

[0015] The first driving data and the second driving data may include at least one of the driver's acceleration input intensity and the duration of the driver's acceleration input.

[0016] The first driving data and the second driving data may include information about the number of times the driver alternates between acceleration and deceleration inputs within a second predetermined time period.

[0017] The processor can determine whether the activation of the speed limit function is an erroneous event by recognizing the driver's voice.

[0018] The notification for disabling the speed limit function can include content related to the input unit used to disable the speed limit function.

[0019] When the activation of the speed limiting function is determined to be an error event, the processor can (e.g., automatically) disable the speed limiting function.

[0020] A method for controlling a vehicle according to various exemplary embodiments of the present disclosure may include: when a speed limiting function of the vehicle is activated, determining whether the activation of the speed limiting function is an error event, and when it is determined that the activation of the speed limiting function is an error event, outputting a notification for disabling the speed limiting function.

[0021] Determining whether the activation of the speed limit function is an error event may include: determining whether the activation of the speed limit function is an error event based on first driving data and second driving data, where the first driving data is the driver's driving data before the speed limit function is activated and the second driving data is the driver's driving data after the speed limit function is activated.

[0022] Determining whether the activation of the speed limit function is an erroneous event may include: calculating an error score based on first driving data and second driving data to determine whether the activation of the speed limit function is an erroneous event, and determining that the activation of the speed limit function is an erroneous event when the error score is above a predetermined value.

[0023] The first driving data may include information about the number of times the driver used the vehicle's speed limit function within a first predetermined time period, and calculating the error score may include: setting the information about the number of times the driver used the vehicle's speed limit function as a weight when calculating the error score.

[0024] When calculating error scores, weighting information about the number of times a driver uses the speed limit function can include setting a lower weight as the number of times a driver uses the vehicle's speed limit function increases.

[0025] The first driving data and the second driving data may include at least one of the driver's acceleration input intensity and the duration of the driver's acceleration input.

[0026] The first driving data and the second driving data may include information about the number of times the driver alternates between acceleration and deceleration inputs within a second predetermined time period.

[0027] Determining whether the activation of the speed limit function is an erroneous event may include: determining whether the activation of the speed limit function is an erroneous event by recognizing the driver's voice.

[0028] The notification for disabling the speed limit function can include content related to the input unit used to disable the speed limit function.

[0029] The method may also include: disabling the speed limiting function when it is determined that the activation of the speed limiting function is an error event (e.g., automatically). Attached Figure Description

[0030] The above and other objects and features of this disclosure will become more apparent from the description of exemplary embodiments thereof with reference to the accompanying drawings, in which:

[0031] Figure 1 The configuration of a vehicle according to an exemplary embodiment is shown;

[0032] Figure 2 This is a flowchart of operations for determining an error event and providing a notification in a control device, according to an exemplary embodiment;

[0033] Figure 3 This is an exemplary view of the speed limit function button according to an exemplary implementation;

[0034] Figure 4 This is a flowchart of (e.g., specific) operations for determining an error event and providing a notification in a control device, according to an exemplary embodiment;

[0035] Figure 5 This is a flowchart of the operation of calculating an error score according to an exemplary implementation;

[0036] Figure 6 This is an exemplary view of content related to first driving data according to an exemplary implementation;

[0037] Figure 7 This is a flowchart of operations for determining an error event in a control device according to an exemplary embodiment; and

[0038] Figure 8 This is a flowchart of an operation for determining an error event and performing automatic control in a control device, according to an exemplary embodiment. Detailed Implementation

[0039] In the following, exemplary embodiments according to this disclosure will be described in detail with reference to the accompanying drawings.

[0040] However, this disclosure is not limited to the described embodiments, but can be implemented in various different forms, and one or more components in the embodiments may be used by (e.g., selectively) coupling or substitution without departing from this disclosure.

[0041] Furthermore, the terms used in the embodiments of this disclosure (including technical and scientific terms) may be interpreted as having meanings that can be understood relative to this disclosure, unless specifically or otherwise defined and described, and the meanings of common terms such as terms defined in dictionaries may be interpreted in light of the contextual meaning of the relevant art.

[0042] Furthermore, the terminology used in the embodiments of this disclosure is for describing the embodiments and is not intended to limit this disclosure.

[0043] In this disclosure, unless otherwise specified in the phrase, the singular form may include the plural form, and when described as “at least one (or one or more) of A, B and C”, it may include one or more of possible combinations of A, B and C.

[0044] Furthermore, terms such as first, second, A, B, (a) and (b) may be used to describe components of embodiments of this disclosure.

[0045] These terms are used to distinguish one component from another, and the properties, sequence, order, etc. of the corresponding components are not limited by these terms.

[0046] Furthermore, when the first component is described as being “connected,” “coupled,” or “joined” to the second component, it may include cases where the first component is (e.g., directly) connected, coupled, or joined to the second component, and also includes cases where the first component is “connected,” “coupled,” or “joined” to the second component through other components present between the first and second components.

[0047] Furthermore, when the first component is described as being formed or disposed "above" or "below" the second component, "above" or "below" can include situations where the two components are in contact with each other (e.g., directly) and / or where one or more third components are formed or disposed between the two components. Additionally, when described as "above" or "below," it can include meanings based on the upward and / or downward directions of a component.

[0048] In the various flowcharts of this disclosure, at least some operations may be omitted or their order may be changed, and at least some of the various embodiments of this disclosure may be performed at (e.g., specific) points in time within each operation of the flowchart. The various flowcharts herein may be executed by at least one of a control device 100, a processor 130, a control unit, or a computer program.

[0049] In the following description, embodiments will be described in detail with reference to the accompanying drawings, and the same reference numerals denote the same or corresponding parts, and repeated descriptions may be omitted.

[0050] Figure 1 A configuration diagram of vehicle 1 according to an exemplary embodiment is shown.

[0051] Vehicle 1 may include a control device 100, a communication unit 110, a storage unit 120, a processor 130, an input / output interface 140, and a sensor unit 150. Figure 1 Each component can be implemented inside the vehicle.

[0052] Control device 100 is a means or program for determining whether the speed limiting function of vehicle 1 is an unexpected error event of the driver when the speed limiting function of vehicle 1 is activated, and controlling the notification of vehicle 1 based on the determination result. Control device 100 may be integrally formed with internal components of the vehicle and may be implemented as a separate device and connected to the internal components of the vehicle via a separate connection unit. Control device 100 is shown to include communication unit 110, storage unit 120 and processor 130, but may be formed to include another component of vehicle 1 (e.g., input / output interface 140).

[0053] Communication unit 110 can communicate with a user terminal, another vehicle, or an external server. Communication unit 110 can perform short-range communication, GPS signal reception, vehicle-to-everything (V2X) communication, optical communication, broadcast transmission / reception, and / or Intelligent Transmission System (ITS) communication functions. Communication unit 110 can support short-range communication using at least one of Bluetooth, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra-Wideband (UWB), ZigBee, Near Field Communication (NFC), Wi-Fi, Wi-Fi Direct, and / or Wireless Universal Serial Bus (USB) technologies. Communication unit 110 may include a mobile communication module using a mobile communication network and a wireless internet module for wireless internet access.

[0054] Storage unit 120 may include instructions related to logic for determining whether an event in which the speed limit function is activated is an error event. Additionally, storage unit 120 may include driver driving data. Storage unit 120 may include memory. Storage unit 120 may be located within processor 130 or control device 100, or may be (e.g., a separate) memory. Storage unit 120 may be formed in combination of non-volatile memory such as hard disk drives, flash memory, electrically erasable programmable read-only memory (EEPROM), static RAM (SRAM), ferroelectric RAM (FRAM), phase-change RAM (PRAM), and magnetic RAM (MRAM) and / or volatile memory such as DRAM, synchronous DRAM (SDRAM), and double data rate SDRAM (DDR-SDRAM).

[0055] The processor 130 may be electrically or operatively connected to the communication unit 110, the storage unit 120, the input / output interface 140, the sensor unit 150, and various internal components of the vehicle 1, and may be a circuit for electrically controlling each component and executing software commands to perform the various data processing and calculations described herein.

[0056] The processor 130 can process signals transmitted between components of the vehicle 1 and perform overall control, enabling each component (e.g., typically) to perform its function. The processor 130 can be implemented in hardware, in software, or a combination of hardware and software. Furthermore, the control device 100 may include at least one processor 130.

[0057] The input / output interface 140 may include an input unit for receiving control commands from the user and an output unit for outputting the operating status, results, etc., of the control device 100. Here, the input unit may include physical keys (e.g., physical buttons) and soft keys implemented on a touch display screen.

[0058] The output unit may include a display screen, and also includes a voice output unit such as a speaker and a haptic module that generates vibrations. In an exemplary embodiment, when a touch sensor such as a touch film, touch sheet, or touchpad is provided on the display screen, the display screen operates as a touch screen, and the input and output units may be implemented in an integrated form.

[0059] The input / output interface 140 can be implemented as a physical button, a display screen, a head-up display (HUD), an instrument panel, an audio-visual navigation (AVN), a human-machine interface (HMI), a user settings menu (USM), etc. Furthermore, the display screen can be included in the rearview or side mirrors.

[0060] For example, a user can request operations related to the assessment of the driver's attention state and the control of autonomous driving-related functions (e.g., via the display screen) through physical buttons on the instrument panel, which serves as an input unit, or through the display screen of the AVN. Furthermore, vehicle 1 can receive input or output from the screen through the display screen of a console located in the second or third row of the vehicle, or through the display screen of an application implemented in the user terminal.

[0061] Sensor unit 150 may include at least one of radio detection and ranging (radar), light detection and ranging (LiDAR), fingerprint recognition sensor, retinal recognition sensor, iris recognition sensor, camera, steering wheel grip sensor, pressure sensor, position sensor (e.g., GPS), ultrasonic sensor, heart rate sensor, optical sensor, pressure relief sensor, motion sensor, seat sensor, or infrared sensor. The camera may include an external camera for monitoring the exterior of the vehicle and an internal camera for detecting objects inside the vehicle (such as the driver).

[0062] Sensor unit 150 may include sensors (e.g., pressure sensors) for measuring the pressure of the accelerator pedal and brake pedal to detect driver acceleration and deceleration inputs. Additionally, sensor unit 150 may include a timer function module for measuring the duration of pedal depressing.

[0063] Figure 2 This is a flowchart of operations for determining an error event and providing a notification in a control device, according to an exemplary embodiment. Figure 3 This is an exemplary view of the pattern-changing button according to an exemplary implementation.

[0064] The control device 100 can detect whether the speed limit function of the vehicle 1 is activated (S210).

[0065] For example, processor 130 can detect when the user presses a button. Figure 3 The input of the mode change button 11 is as follows. The mode change button 11 can be an input unit for activating or deactivating the speed limiting function. The input / output interface 140 can include the mode change button 11. The mode change button 11 can be implemented as a soft key (e.g., a touch item) that can be displayed on the screen, as well as a physical key.

[0066] By pressing the mode change button 11, another driving assistance function or an autonomous driving function of vehicle 1 can be selected. Therefore, when the user presses the mode change button 11, in addition to the speed limit function according to the embodiment of this disclosure, driving assistance functions such as cruise control can also be activated.

[0067] Even when cruise control is activated via mode change button 11, acceleration via the accelerator pedal is possible, and since cruise control is deactivated (e.g., automatically) when the brake pedal is pressed, there is no interference (e.g., problem) even if cruise control is unintentionally activated.

[0068] However, once activated, speed limiting functions (such as speed limit) cannot be deactivated by other inputs, but only (e.g., via mode change button 11). Therefore, it is useful to check whether the activation of the speed limiting function caused by mode change button 11 was an unintentional event by the driver.

[0069] The control device 100 can determine whether the activation of the speed limiting function is an error event (S230).

[0070] In an exemplary implementation, processor 130 may detect whether abnormal driver behavior occurs when the speed limit function is activated. For example, abnormal driver behavior may indicate that the driver's behavior is hindered by the unintentional activation of the speed limit function. For example, even if the speed limit function is activated, behaviors such as (e.g., continuously and forcefully pressing the accelerator pedal to drive faster than the current speed limit) or alternating pressing of the brake and accelerator pedals may be detected.

[0071] According to an exemplary embodiment, the control device 100 can determine whether the activation of the speed limit function is an error event based on the driver's accumulated driving data before and after the activation of the speed limit function. A description of this is provided herein.

[0072] Based on the determined result, the control device 100 can provide a guidance notification for disabling the speed limit function (S250).

[0073] According to an exemplary implementation, when it is determined that the activation of the speed limiting function is an error event, the processor 130 may include in the notification the contents of the input unit that can disable the speed limiting function and provide (e.g., above) the notification through the input / output interface 140.

[0074] For example, processor 130 can generate and display a steering wheel including mode change button 11 as such. Figure 3 The UI content shown can be displayed on a display screen of vehicle 1 (e.g., instrument panel, head-up display (HUD), or AVN display). In an exemplary embodiment, to make the mode change button 11 easily recognizable to the driver, the mode change button 11 can be displayed as content distinct from other areas of the steering wheel's UI content. Additionally, an indicator for the mode change button 11 can be displayed. Furthermore, at least one of a text message and a voice message can be output via input / output interface 140 instructing the driver to release the speed limit function by pressing the mode change button 11.

[0075] Figure 4 This is a flowchart of (e.g., specific) operations for determining an error event and providing a notification in a control device 100, according to an exemplary embodiment. Figure 5 This is a flowchart of the operation for calculating error scores according to an exemplary implementation. Figure 6 This is an exemplary view of first driving data according to an exemplary implementation. Figure 4 The content can omit the part related to... Figure 3 Duplicate content. Furthermore, in Figure 5 The content can omit the part related to... Figure 3 and Figure 4 Duplicate content.

[0076] The control device 100 can collect and analyze the first driving data (S410).

[0077] According to an exemplary embodiment, the first driving data may be the driver's driving data prior to activating the speed limit function. The first driving data may include driver driving data accumulated over a predetermined time period, and the first driving data may be stored in the storage unit 120 and updated based on driving activity. The first driving data can be used to determine and learn the driver's typical driving habits.

[0078] According to an exemplary embodiment, the first driving data may include information about the number of times the driver used the speed limit function of vehicle 1 within a predetermined time period. For example, the number of times the driver used the speed limit function may be information representing the frequency with which the driver used the speed limit function in the past. Therefore, it is feasible to check whether the corresponding driver is a user who can (e.g., effectively) use the speed limit function.

[0079] According to an exemplary implementation, information about the number of times the driver used the speed limit function can be set as a weight in the process of calculating the error score to determine the error event.

[0080] According to an exemplary embodiment, the first driving data may include at least one of the driver's acceleration input intensity and acceleration input duration over a predetermined time period. For example, acceleration input can be identified by information about the opening of the accelerator pedal, and deceleration input can be identified, for example, by information about the opening of the brake pedal.

[0081] According to an exemplary embodiment, the first driving data may include information about the number of times the driver alternates between acceleration and deceleration inputs within a predetermined time period.

[0082] Next, the control device 100 can determine whether the speed limiting function has been activated (S420). When the speed limiting function is not activated (No in S420), the control device 100 can control the vehicle 1 according to the current conditions (S460). For example, when the driver (e.g., directly) controls the driving, the processor 130 can control the driving of the vehicle 1 according to the driver's control input.

[0083] When the speed limit function is activated (in S420), the control device 100 can collect second driving data (S430).

[0084] According to an exemplary embodiment, the second driving data may be driving data of the driver after the speed limit function is activated. The second driving data may be stored in the storage unit 120, and the second driving data may be used together with the first driving data to determine an error event.

[0085] According to an exemplary embodiment, the second driving data may include at least one of the intensity of the driver's acceleration input and the duration of the driver's acceleration input after the speed limit function is activated. For example, acceleration input can be identified by information about the opening of the accelerator pedal, and deceleration input can be identified, for example, by information about the opening of the brake pedal.

[0086] According to an exemplary implementation, the second driving data may include information about the number of times the driver alternates between acceleration and deceleration inputs within a predetermined time period after the speed limit function is activated.

[0087] Subsequently, the control device 100 can determine whether the activation of the speed limit function is an error event (S440).

[0088] According to an exemplary implementation, the processor 130 can determine whether an event in which the speed limit function is activated is an error event based on at least one of the first driving data and the second driving data.

[0089] In an exemplary embodiment, processor 130 may calculate an error score based on first driving data and second driving data. When the calculated error score is above a predetermined value, processor 130 may determine that the activation event of the speed limit function is an error event.

[0090] When the calculated error score is less than a predetermined value, the activation event of the speed limit function is determined to be a normal event, and the processor 130 can control the operation of the vehicle 1 according to the current conditions (S460). For example, when the calculated error score is less than the predetermined value, the speed limit function is an intentional event of the driver, and therefore, the processor 130 can maintain the speed of the vehicle 1 below the predetermined speed according to the corresponding speed limit function.

[0091] When the activation event of the speed limit function is determined to be an error event due to an error score exceeding a predetermined value, the control device 100 may provide the driver with the notification described herein (S450).

[0092] refer to Figure 5 The process for calculating error scores was made public.

[0093] The control device 100 can check the first driving data stored in the storage unit 120 (S510) and derive the average value and weight of the driver's driving data elements (S530).

[0094] For example, processor 130 can identify the driver and check the stored first driving data of the corresponding driver. Based on the driver identification result, checking the first driving data of the corresponding driver can be performed via user selection input or (e.g., automatically) via driver authentication, etc. For example, a specific user can be identified and their first driving data can be used, such as through fingerprint recognition, a user terminal, etc.

[0095] In addition, the processor 130 can calculate the average value and weight of the driving data elements stored in the first driving data.

[0096] For example, the processor 130 may calculate at least one of the following: the average number of times the driver uses the speed limit function during a predetermined period of time before the activation event of the speed limit function; the average driver acceleration input intensity stored during the predetermined period of time before the activation event of the speed limit function; and the average acceleration input duration stored during the predetermined period of time before the activation event of the speed limit function.

[0097] For example, refer to Figure 6 As primary driving data, the average acceleration input intensity calculated for each speed segment of vehicle 1 is shown. The acceleration input intensity can be determined based on the opening of the accelerator and brake pedals, and the average value can be calculated for each speed segment of vehicle 1.

[0098] At the same time, the processor 130 can set the number of times the driver uses the speed limit function within a predetermined time period before the speed limit function activation event occurs as a weight.

[0099] For example, a low weight can be set when drivers use the speed limit function frequently, i.e., when users are familiar with the speed limit function. Conversely, a high weight can be set when drivers use the speed limit function infrequently, i.e., when users are unfamiliar with the speed limit function. The frequency of driver use of the speed limit function can be set based on (e.g., a specific) value, and can also be set by comparing the value for each user (e.g., relative).

[0100] Meanwhile, the calculated average and the set weights can be restored as the first driving data.

[0101] Next, the control unit 100 can check the second driving data (S550).

[0102] For example, processor 130 can examine second driving data, which is the driving data of the corresponding driver stored after the speed limit function is activated. Processor 130 can store previous driving data and subsequent driving data (e.g., separately) based on the event that the speed limit function is activated.

[0103] Next, the control device 100 can calculate an error score based on the first driving data and the second driving data (S570). The error score can be a value calculated to determine whether an event is an error event (e.g., a specific event).

[0104] According to an exemplary embodiment, when the accelerator pedal opening in the second driving data exceeds the average opening value in the first driving data corresponding to the current vehicle speed segment (hereinafter, "the first condition is met"), the processor 130 can calculate an error score. That is, the control device 100 can calculate an error score when it detects an input that increases the speed compared to the normal vehicle speed after the speed limit function is activated.

[0105] Conversely, when the accelerator pedal opening in the second driving data is below the average opening value in the first driving data corresponding to the current vehicle speed segment (e.g., the first condition is not met), the control device 100 will not calculate an error score.

[0106] According to an exemplary implementation, the processor 130 can calculate an error score when the duration of acceleration input in the second driving data lasts for a predetermined time (e.g., 5 seconds) or more (hereinafter referred to as "satisfying the second condition") while the first condition is met.

[0107] Conversely, when the duration of acceleration input in the second driving data is consistently less than a predetermined time (e.g., 5 seconds) (e.g., the second condition is not met), no error score is calculated.

[0108] According to an exemplary implementation, when both the first and second conditions are met, the processor 130 can calculate an error score.

[0109] As an exemplary implementation, the processor 130 can calculate an error score based on the weights set in the first driving data and the acceleration input duration confirmed in the second driving data. As an example of calculating the error score, Equation 1 is as follows:

[0110] [Equation 1]

[0111] Error score = weight * acceleration input duration (s)

[0112] For example, if a user with a weight of 3 based on first-hand driving data presses the accelerator pedal for 7 seconds, the error score could be 21.

[0113] According to an exemplary embodiment, the control device 100 can calculate an error score based on the average of the number of times acceleration and deceleration inputs were alternately input, calculated based on first driving data, and the number of times acceleration and deceleration inputs were alternately input, confirmed based on second driving data. In the exemplary embodiment, the weight based on the first driving data can be reflected when calculating the error score. As an example of calculating the error score, Equation 2 is as follows:

[0114] [Equation 2]

[0115] Error score = weight * (current frequency (Hz) - average frequency (Hz))

[0116] The average frequency is the frequency of the average number of alternating acceleration and deceleration inputs calculated based on the first driving data, and the current frequency can be (e.g., set to) the frequency of the number of acceleration and deceleration inputs detected from the time the speed limit function is activated to the time the error score is calculated. In an exemplary embodiment, the average frequency can be normalized to 1, and the current frequency can be a frequency that compares the magnitude of the average frequency (e.g., relative). Frequency information can be calculated based on the average time interval when the accelerator and brake pedals are alternately depressed.

[0117] When the calculated error score is above a predetermined value, the control device 100 can determine that the activation of the speed limiting function is an error event (S590). This predetermined value can be preset or changed. For example, when the predetermined value is set to 20, the value calculated using Equation 1 is 21, and therefore, in the exemplary embodiment, the control device 100 can determine that the activation event of the speed limiting function is an error event.

[0118] Figure 7 This is a flowchart illustrating operations for determining an error event in a control device according to an exemplary embodiment. Figure 7 The repeated content of the accompanying figures described in this article may be omitted.

[0119] When the activation of the speed limit function is detected (S710), the control device 100 can recognize the driver's voice (S730). The processor 130 can recognize the driver's voice through a microphone included in the input / output interface 140.

[0120] The control device 100 can determine an error event based on the result of voice recognition (S750). For example, when activation of the speed limit function is detected, and then an abnormal voice from the driver activating the speed limit function is recognized, the processor 130 can determine that the corresponding event is an error event. For example, the abnormal voice may include, but is not limited to, preset words or volumes that are not intended for use with the speed limit function.

[0121] Figure 8 This is a flowchart of an operation for determining an error event and performing automatic control in a control device, according to an exemplary embodiment.

[0122] When the activation of the speed limiting function is detected (S810), the control device 100 may determine whether the activation of the speed limiting function is an error event according to the embodiments herein (S830). When it is determined that the activation of the speed limiting function is an error event, the control device 100 may (e.g., automatically) release the speed limiting function without (e.g., separately) notification or with notification (S850).

[0123] As used herein, the term "~cell" can provide (e.g., mean) a software component or a hardware component such as a field-programmable gate array (FPGA) or an ASIC, and the "~cell" performs a specific function. However, a "cell" is not limited to software or hardware. A "cell" can be located in an addressable storage medium and configured to reproduce one or more processors. Thus, as an exemplary implementation, a "cell" is a component such as a software component, an object-oriented software component, a class component and a task component, a process, a function, an attribute, a program, a subroutine, a program code segment, a driver, firmware, microcode, a circuit, data, a database, a data structure, a table, an array, and / or a variable. The functionality provided in components and "~cells" can be combined into a smaller number of components and "cells" or separated into additional components and "cells". Furthermore, components and "~cells" can be implemented as one or more CPUs in a reproduction device or a secure multimedia card.

[0124] According to this disclosure, it is feasible to provide an environment in which the driver can (e.g., more easily) release the speed limit function when the activated speed limit function is detected as an unintentional error by the driver.

[0125] This disclosure is not limited to the effects described herein, and other effects can be understood based on the description herein.

[0126] Although this disclosure has been described herein with reference to exemplary embodiments, modifications and changes (e.g., various) may be made to this disclosure without departing from the disclosure as described in at least the appended claims.

Claims

1. A vehicle comprising: Input / output interfaces; as well as processor, When the vehicle's speed limiting function is activated, the processor determines whether the activation of the speed limiting function is an error event, and when it is determined that the activation of the speed limiting function is the error event, the processor outputs a notification to disable the speed limiting function through the input / output interface.

2. The vehicle according to claim 1, wherein, The processor determines whether the activation of the speed limit function is an error event based on first driving data and second driving data. The first driving data is the driver's driving data before the speed limit function is activated, and the second driving data is the driver's driving data after the speed limit function is activated.

3. The vehicle according to claim 2, wherein, The processor calculates an error score based on the first driving data and the second driving data to determine whether the activation of the speed limit function is an error event, and determines that the activation of the speed limit function is an error event when the error score is above a predetermined value.

4. The vehicle according to claim 3, wherein, The first driving data includes information about the number of times the driver used the vehicle's speed limit function within a first predetermined time period, and When calculating the error score, the processor sets the information about the number of times the driver used the vehicle's speed limit function as a weight.

5. The vehicle according to claim 4, wherein, The more frequently the driver uses the vehicle's speed limit function, the lower the weight the processor sets.

6. The vehicle according to claim 4, wherein, The first driving data and the second driving data each include at least one of the driver's acceleration input intensity and the driver's acceleration input duration.

7. The vehicle according to claim 4, wherein, The first driving data and the second driving data each include information about the number of times acceleration input and deceleration input are alternately input within a second predetermined time period.

8. The vehicle according to claim 1, wherein, The processor determines whether the activation of the speed limit function is an error event by recognizing the driver's voice.

9. The vehicle according to claim 1, wherein, The notification for disabling the speed limit function includes content related to the input unit for disabling the speed limit function.

10. The vehicle according to claim 1, wherein, When it is determined that the activation of the speed limiting function is an error event, the processor automatically disables the speed limiting function.

11. A method for controlling a vehicle, comprising: When the speed limit function of the vehicle is activated, determine whether the activation of the speed limit function is an error event; and When it is determined that the activation of the speed limiting function is an error event, a notification is output to disable the speed limiting function.

12. The method according to claim 11, wherein, Determining whether the activation of the speed limit function is an error event includes: determining whether the activation of the speed limit function is an error event based on first driving data and second driving data, wherein the first driving data is the driver's driving data before the speed limit function is activated, and the second driving data is the driver's driving data after the speed limit function is activated.

13. The method according to claim 12, wherein, The step of determining whether the activation of the speed limiting function is an error event includes: Based on the first driving data and the second driving data, an error score is calculated to determine whether the activation of the speed limit function is an error event; and When the error score is above a predetermined value, the activation of the speed limit function is determined to be the error event.

14. The method according to claim 13, wherein, The first driving data includes information about the number of times the driver used the vehicle's speed limit function within a first predetermined time period, and Calculating the error score includes: when calculating the error score, setting the information about the number of times the driver uses the speed limit function of the vehicle as a weight.

15. The method according to claim 14, wherein, When calculating the error score, setting the weights based on the information about the number of times the driver uses the speed limit function includes setting the weights lower as the number of times the driver uses the vehicle's speed limit function increases.

16. The method of claim 14, wherein, The first driving data and the second driving data each include at least one of the driver's acceleration input intensity and the driver's acceleration input duration.

17. The method of claim 14, wherein, The first driving data and the second driving data each include information about the number of times acceleration input and deceleration input are alternately input within a second predetermined time period.

18. The method according to claim 11, wherein, Determining whether the activation of the speed limit function is an error event includes: determining whether the activation of the speed limit function is an error event by recognizing the driver's voice.

19. The method according to claim 11, wherein, The notification for disabling the speed limit function includes content related to the input unit for disabling the speed limit function.

20. The method of claim 11, further comprising: When it is determined that the activation of the speed limiting function is an error event, the speed limiting function is automatically disabled.

Images