Vehicle control device
Patent Information
- Application Number
- CN202511892564.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-02-20
- Filing Date
- 2025-12-16
- Publication Date
- 2026-08-21
AI Technical Summary
[0018] Therefore, when a driver suggests a rest stop via the vehicle control system, they can avoid the hassle of operating a navigation system to search for rest facilities. In other words, the driver can reach the rest facility simply by guiding the vehicle along the path displayed on the display device.
Smart Images

Figure CN122607338A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a vehicle control device having the function of suggesting to the driver of a vehicle to stop driving and take a rest. Background Technology
[0002] A vehicle control device (see, for example, Patent Document 1 below) is proposed that has a function to suggest that the driver of the vehicle stop driving and take a rest (a rest suggestion function). This device (hereinafter referred to as the "conventional device") has a sensor that acquires the driver's biometric information. The conventional device acquires the driver's fatigue level based on the biometric information, and if the fatigue level exceeds a threshold, displays the location of nearby rest facilities on an image display device.
[0003] Patent Document 1: Japanese Patent Application Publication No. 2023-172749 Summary of the Invention
[0004] As described above, conventional devices use sensors to acquire the driver's biometric information. Here, the driver's biometric information is personal information. Therefore, sometimes the driver does not allow biometric information to be acquired through the sensor. In this case, the driver cannot utilize the rest suggestion function.
[0005] One of the objectives of this invention is to provide a vehicle control device that can suggest a rest to the driver when certain conditions are met, wherein the vehicle control device determines whether the conditions are met without using the driver's biometric information.
[0006] To achieve the above objectives, the vehicle control device (1) of the present invention includes: a processor (30, 10) configured to perform rest suggestion processing, which, when predetermined conditions are met, controls a predetermined notification device (20) to provide information prompting the driver of the vehicle to stop driving and rest, wherein,
[0007] The vehicle control device (1) includes a position sensor for sequentially acquiring the current position of the vehicle.
[0008] The processor, based on map data (MD) capable of identifying a first area (Ra) consisting of highways and a second area (Rb) excluding them, determines that the current location is contained within the first area, considers the driver to be driving, obtains the duration of this state as driving time (DT), and pre-stores this driving time as driving history (HST). When the driver starts driving, based on a first driving time (DT1) which is the duration of the previous driving, a rest time (RT1) which is the time the driver rested after the previous driving, and a second driving time (DT2) which is the total driving time of the driver from a predetermined time point (Tb) in the period (T) up to the current time point (T0), obtains a rest suggestion time (Tc) as the time when the next rest suggestion process should be executed. When the current time reaches the rest suggestion time, it is determined that the predetermined condition is met.
[0009] The vehicle control device of this invention determines the timing of the next rest suggestion based on driving time and rest time within a specified period. That is, according to this invention, the conditions for executing a rest suggestion are determined without using the driver's biometric information. Therefore, even drivers who prohibit the vehicle control device from accessing biometric information (personal information) can utilize the rest suggestion function. Furthermore, in situations involving repeated driving and resting, drivers may find it difficult to perceive the accumulation of fatigue or the easy increase in fatigue levels. The vehicle control device determines the timing of the rest suggestion not only based on the duration of the driver's previous driving session (i.e., the first driving time) and its immediately following rest time, but also based on the total driving time within the specified period (including the previous driving period). Thus, taking into account the potential for imperceptible increases in fatigue levels, rest suggestions are executed at appropriate timings.
[0010] In a vehicle control device according to one aspect of the present invention,
[0011] The processor performs the following processing: selecting the larger of the value obtained by subtracting the first driving time from the value obtained by multiplying the rest time by a predetermined first coefficient (k1) and the value obtained by dividing the second driving time by a predetermined second coefficient (k2); and obtaining the time point from the current time point after which the selected value has been subtracted from the predetermined standard time as the rest suggestion timing.
[0012] Thus, the processor can determine the timing of the next rest suggestion by performing relatively simple calculations.
[0013] In another aspect of the vehicle control device according to the invention,
[0014] The processor performs the following processing: when a destination is set, it obtains the path (R) from the current location to the destination; when the vehicle travels along the path from the current location, it infers the location the vehicle will arrive at at the rest suggestion time; when the distance to a first facility from which the vehicle can be parked exceeds a threshold, it searches for a second facility closer to the first facility by referring to the map data; and when the vehicle arrives at a specified location closer to the second facility, it executes the rest suggestion processing.
[0015] For example, when driving on a highway, if a rest stop is recommended immediately after passing a rest stop, and the next rest stop is relatively far away, this could potentially increase driving time. According to the present invention, this situation can be prevented.
[0016] In another aspect of the vehicle control device according to the invention,
[0017] The processor obtains the path (R) to the facility where the vehicle can be parked at the recommended rest time and displays the path on a designated display device.
[0018] Therefore, when a driver suggests a rest stop via the vehicle control system, they can avoid the hassle of operating a navigation system to search for rest facilities. In other words, the driver can reach the rest facility simply by guiding the vehicle along the path displayed on the display device. Attached Figure Description
[0019] Figure 1 This is a block diagram of a vehicle control device according to one embodiment of the present invention.
[0020] Figure 2 This is a conceptual diagram of driving history data, which serves as a record of driving and rest time.
[0021] Figure 3 This is a flowchart of the first program executed by the CPU to implement the rest suggestion function.
[0022] Figure 4 This is a flowchart of the second program executed by the CPU to implement the rest suggestion function.
[0023] Figure 5 This is a flowchart of the third program executed by the CPU to implement the rest suggestion function.
[0024] Figure 6 This is a block diagram of a vehicle control device according to a variation of the present invention. Detailed Implementation
[0025] (roughly)
[0026] The vehicle control device 1 according to one embodiment of the present invention is applicable to a vehicle V0 (hereinafter referred to as "the vehicle") equipped with an automatic driving function. The vehicle control device 1 has a rest suggestion function, which suggests to the driver to stop driving and rest when the automatic driving function of the vehicle is disabled and the driver is performing manual driving operations, under certain conditions.
[0027] (Specific structure)
[0028] Next, the structure of the vehicle control device 1 will be described in detail. For example... Figure 1 As shown, the vehicle control unit 1 includes an ECU 10 and a notification device 20, which are devices mounted on the vehicle. Furthermore, the vehicle control unit 1 includes a smartphone 30, which is a device carried by the driver.
[0029] ECU 10 includes a microcomputer (SOC) with a CPU 10a, ROM 10b, RAM 10c, timer 10d, etc. Furthermore, ECU 10 includes a communication device 10e. The communication device 10e follows a prescribed short-range wireless communication protocol (e.g., Bluetooth (registered trademark)) and is connected to the smartphone 30 described later via a wireless communication line.
[0030] The notification device 20 includes a display device and an audio device. The display device displays images according to display instructions obtained from the ECU 10. The audio device plays sounds according to sound playback instructions obtained from the ECU 10.
[0031] The smartphone 30 includes a microcomputer comprising a CPU, ROM, RAM, and a timer. The timer consists of multiple timer circuits (timers Tα, Tβ, and Tγ, described later) capable of simultaneously measuring multiple times. Furthermore, the smartphone 30 includes a communication device, an image display device, an audio device, and a touch panel. A pre-defined rest suggestion application is installed in the ROM of the smartphone 30.
[0032] (Rest suggestion function)
[0033] The driver activates a rest suggestion application on their smartphone 30 while riding in the vehicle, and the smartphone 30 is connected to the ECU 10 via a wireless communication line. In this state, the smartphone 30 acquires GPS signals from multiple GPS satellites and obtains its current location P (latitude and longitude) based on these GPS signals. The rest suggestion application includes map data MD. This map data MD includes information representing areas Ra and Rb, indicating the locations of roads and other areas (rest facilities where the vehicle can be parked). The smartphone 30 refers to the map data to determine the area (road / other) containing the current location P. When the current location P is within area Ra (road) while connected to the ECU 10 via the wireless communication line, the smartphone 30 considers the driver to be driving the vehicle. When the current location P is within area Rb (rest facility), the smartphone 30 considers the driver to have stopped driving and taken a rest. When the current location P moves from area Rb to area Ra while connected to the ECU 10 via the wireless communication line, the smartphone 30 determines that the driver has started driving. Furthermore, when the smartphone 30 is connected to the ECU 10 via a wireless communication line, it determines that the driver has stopped driving and begun to rest when the current position P moves from area Ra to area Rb. Conversely, when the smartphone 30 is not connected to the ECU 10 via a wireless communication line, it considers the driver to be in a state of getting out of the vehicle and resting. The smartphone 30 can also determine that the driver has begun to rest when the current position P remains stationary within area Rb for a period exceeding a threshold. Furthermore, the smartphone 30 can sequentially acquire position information from the ECU 10 within area Rb, and based on this information, determine that the driver has begun to rest when it detects that the vehicle's position information has changed to a parking position. The smartphone 30 uses a timer Tα to measure the duration of the driver's driving state (from the start of driving to the start of rest) and obtains this measurement result as the driving time DT (reference). Figure 2 Furthermore, the smartphone 30 uses a timer Tβ to measure the duration of the driver's rest period (the time from the start of the rest to the start of driving), and obtains this measurement result as the rest time RT. Each time the smartphone 30 obtains the driving time DT and the rest time RT, it stores them as driving history data HST.
[0034] However, the longer the driver's continuous driving time (driving time DT), the higher the driver's fatigue level. Therefore, it is preferable for the driver to stop driving and rest when the driving time DT has become longer to a certain extent. Even if the driver stops driving and rests, if the time is insufficient, the driver's fatigue may not be fully recovered. Furthermore, the longer the total driving time T from the past specified time point to the current time point, the more likely the driver's fatigue level is to increase; therefore, it is preferable to shorten the subsequent driving time DT (increase the frequency of rest).
[0035] Therefore, when the prescribed conditions related to the driver's continuous driving time (driving time DT) and the driver's continuous rest time (rest time RT) are met, the smartphone 30 performs rest suggestion processing to suggest interrupting driving and taking a rest. Specifically, the smartphone 30 determines the moment T0 when the driver starts driving (refer to...) Figure 2 The smartphone 30 uses driving history data HST to obtain the duration of the last drive as driving time DT1. Furthermore, the smartphone 30 uses driving history data HST to obtain the time from the point Ta when the last drive was interrupted and the rest period began until the current point T0 as rest time RT1. Additionally, the smartphone 30 obtains the total of all driving times DT from a predetermined past point Tb to the current point T0 as driving time DT2.
[0036] At time T0, smartphone 30 obtains time Tx by subtracting the value obtained by multiplying rest time RT1 by a predetermined coefficient k1 from driving time DT1. If the calculated time Tx is less than 0, smartphone 30 treats it as 0. Next, smartphone 30 obtains time Ty by dividing driving time DT2 by a predetermined coefficient k2. Then, smartphone 30 compares time Tx and time Ty. Next, smartphone 30 obtains the larger of time Tx and time Ty as time Tz (=Max[Tx,Ty]). Then, smartphone 30 obtains the value obtained by subtracting time Tz from standard time Tstd as the remaining time Δt (=Tstd-Max[Tx,Ty]) from the current time T0 (the time determined to be the start of driving) until the timing Tc for the next rest suggestion processing. That is, in principle, the smartphone 30 is configured to execute the next rest suggestion processing at the point when a predetermined standard time Tstd has elapsed from time point T0. However, if the rest time RT1 is insufficient relative to the driving time DT1, the timing Tc is only advanced by the time Tx corresponding to the insufficient amount. However, if the total driving time DT2 in the period T (the period from time point Tb to time point T0) is relatively large, the driver's fatigue level is likely to increase. Therefore, the smartphone 30 compares the time Ty and the time Tx corresponding to the driving time DT2. If the time Ty is greater than the time Tx, the timing Tc of the time Ty is only advanced.
[0037] At time T0, the smartphone 30 allocates the remaining time Δt to the output value tγ of the timer Tγ, and makes the timer Tγ work as a countdown timer. Then, at time Tc when the output value tγ of the timer Tγ becomes "0", the smartphone 30 performs rest suggestion processing. Specifically, the smartphone 30 sends a predetermined notification command to the ECU 10 via a wireless communication line. Upon receiving the notification command, the ECU 10 sends an image display command to the display device of the notification device 20 to display the predetermined rest suggestion image G, and sends an audio playback command to the audio device of the notification device 20 to play the predetermined rest suggestion sound S.
[0038] In this embodiment, the length of the period T from time point Tb to the current time point T0 is "12 (hours)". Furthermore, the standard time Tstd is "180 (minutes)". Also, the coefficient k1 is "6" and the coefficient k2 is "5".
[0039] (Concrete example 1)
[0040] For example, when driving time DT1 is "180 minutes" and rest time RT1 is "30 minutes", time Tx becomes "0 = 180 - 30 × 6 minutes". That is, in this case, rest time RT1 is considered sufficient relative to driving time DT1. Here, when driving time DT2 is the same as driving time DT1, "180 minutes", time Ty is "36 minutes". In this example, since time Tx is "0", time Ty is greater than time Tx. Therefore, the remaining time Δtrest at time point T0 is "144 = 180 - 36 minutes".
[0041] (Concrete example 2)
[0042] For example, if driving time DT1 is 180 minutes and rest time RT1 is 20 minutes, then time Tx becomes 60 minutes. In this case, rest time RT1 is considered insufficient relative to driving time DT1. Here, when driving time DT2 is the same as driving time DT1 (180 minutes), time Ty is 36 minutes. In this example, time Tx is 60 minutes, therefore time Tx is greater than time Ty. Therefore, the remaining time Δtrest at time point T0 is 120 = 180 - 60 minutes.
[0043] (Concrete example 3)
[0044] For example, when driving time DT1 is "120 minutes" and rest time RT1 is "60 minutes", time Tx becomes "0 minutes". In this case, rest time RT1 is considered sufficient relative to driving time DT1. Here, when driving time DT2 is "360 minutes", time Ty is "72 minutes". In this example, time Tx is "0 minutes", therefore time Ty is greater than time Tx. Therefore, the remaining time Δtrest at time point T0 is "108 = 180 - 72 minutes".
[0045] Next, refer to Figures 3 to 5The structure of the rest suggestion application is explained below. The rest suggestion application includes programs PR1 to PR3. When the smartphone 30 is powered on, the CPU (hereinafter referred to as "CPU") displays the icon of the rest suggestion application on the main screen. When the CPU detects that the icon has been clicked, it launches the rest suggestion application and executes programs PR1 to PR3 (in parallel processing) at predetermined intervals. In addition, the CPU executes other programs (not shown) to determine whether it can connect to the ECU 10 via a wireless communication line. Then, if it can connect to the ECU 10, the CPU performs a predetermined authentication process to establish the wireless communication connection. On the other hand, if it cannot connect to the ECU 10, the CPU determines that the driver is in a state of getting out of the vehicle V0 and resting.
[0046] (Program PR1)
[0047] The CPU starts executing program PR1 from step 100 and proceeds to step 101.
[0048] In step S101, the CPU determines whether the driver has started driving. If the CPU changes from a state where the smartphone 30 is connected to the ECU 10 and the current location P is outside the area Ra to a state where it is inside the area Ra (highway), it determines that driving has started. If the CPU determines that the driver has started driving (101: Yes), it proceeds to step S102. On the other hand, if the CPU does not determine that the driver has started driving (101: No), it returns to step S101.
[0049] In step S102, the CPU sets (initializes) the output value tα of timer Tα to "0". Then, the CPU proceeds to step 103.
[0050] In step S103, the CPU starts timer Tα as the up-timer. Then, the CPU proceeds to step 104.
[0051] In step S104, the CPU determines whether the driver has started to rest. If the CPU changes from a state where the current position P is contained in region Ra to a state where it is contained in region Rb, it determines that the driver has started to rest. If the CPU determines that the driver has started to rest (104: Yes), it proceeds to step S105. On the other hand, if the CPU does not determine that the driver has started to rest (104: No), it returns to step S103.
[0052] In step S105, the CPU appends the output value tα of timer Tα as the driving time DT to the driving history data HST. Then, the CPU proceeds to step 106.
[0053] In step 106, the CPU terminates the execution of program PR1.
[0054] (Program PR2)
[0055] The CPU starts executing program PR2 from step 200 and proceeds to step 201.
[0056] In step S201, the CPU determines whether the driver has started to rest. If the CPU determines that the driver has started to rest (201: Yes), it proceeds to step S202. On the other hand, if the CPU does not determine that the driver has started to rest (201: No), it returns to step S201.
[0057] In step S202, the CPU sets (initializes) the output value tβ of timer Tβ to "0". Then, the CPU proceeds to step 203.
[0058] In step S203, the CPU sets timer Tβ as an up timer. Then, the CPU proceeds to step 204.
[0059] In step S204, the CPU determines whether the driver has started driving. If the CPU determines that the driver has started driving (204: Yes), it proceeds to step S205. On the other hand, if the CPU does not determine that the driver has started driving (204: No), it returns to step S203.
[0060] In step S205, the CPU appends the output value tβ of timer Tβ as rest time RT to the driving history data HST. Then, the CPU proceeds to step 206.
[0061] In step 206, the CPU terminates the execution of program PR2.
[0062] (Program PR3)
[0063] The CPU starts executing program PR3 from step 300 and proceeds to step 301.
[0064] In step S301, the CPU determines whether the driver has started driving. If the CPU determines that the driver has started driving (301: Yes), it proceeds to step S302. On the other hand, if the CPU does not determine that the driver has started driving (301: No), it returns to step S301.
[0065] In step S302, the CPU refers to the driving history data HST to obtain the driving time DT1 (the latest driving time DT). Then, the CPU proceeds to step 303.
[0066] In step S303, the CPU refers to the driver's operation history data HST to obtain the rest time RT1 (the latest rest time RT). Then, the CPU proceeds to step 304.
[0067] In step S304, the CPU refers to the driving history data HST and calculates the driving time DT2 (the total driving time DT in period T).
[0068] In step S305, the CPU calculates the remaining time Δt (Δt = Tstd - Max[DT1 - RT1 × k1, DT2 / k2]). Then, the CPU proceeds to step 306.
[0069] In step S306, the CPU allocates the remaining time Δt to the output value tγ of timer Tγ. Then, the CPU proceeds to step 307.
[0070] In step S307, the CPU starts timer Tγ as a countdown timer. Then, the CPU proceeds to step 308.
[0071] In step S308, the CPU determines whether the output value tγ is "0". If the CPU determines that the output value tγ is "0" (308: Yes), it proceeds to step S309. On the other hand, if the CPU does not determine that the output value tγ is "0" (308: No), it returns to step S307.
[0072] In step S309, the CPU performs a rest suggestion process. That is, the CPU, via ECU10, causes the notification device 20 to display a specified image and play a specified sound. Then, the CPU proceeds to step 310.
[0073] In step 310, the CPU terminates the execution of program PR3.
[0074] (Effect)
[0075] The vehicle control device 1 of this embodiment determines the timing Tc of the next rest suggestion based on the driving time DT and rest time RT within a specified period. That is, according to this embodiment, the driver's biometric information is not used to determine whether the conditions for executing the rest suggestion are met. Therefore, even drivers who prohibit the vehicle control device 1 from obtaining biometric information (personal information) can use the rest suggestion function. Furthermore, in cases of repeated driving and resting, drivers may not be aware of the accumulation of fatigue or the easy increase in fatigue. The vehicle control device 1 determines the timing Tc of the rest suggestion not only based on the duration of the driver's last drive, i.e., driving time DT1, and its immediately following rest time RT1, but also based on the total driving time DT within the specified period (including the last driving period), i.e., driving time DT2. Thus, taking into account the increase in fatigue that the driver may not be able to perceive, the rest suggestion is executed at an appropriate timing Tc.
[0076] (Variation Example 1)
[0077] The values assigned to the standard time Tstd and coefficients k1 and k2 are not limited to the embodiments described above. These values can also be set (changed) by the driver. For example, if the driver tends to require a relatively long time to recover from fatigue, the driver can assign smaller values to the standard time Tstd and / or coefficient k1. This increases the frequency of rest recommendations. Furthermore, if the driver tends to experience increased fatigue after starting to drive, the driver can assign smaller values to the standard time Tstd and / or coefficient k2. This also increases the frequency of rest recommendations. Additionally, the smartphone 30 can learn the frequency of driver rest based on the driver's driving history data HST and automatically adjust the standard time Tstd and coefficients k1 and k2 based on this learning result.
[0078] (Variation Example 2)
[0079] like Figure 6 As shown, a vehicle navigation system 40 can be used, which has the same functions as the notification device 20 and smartphone 30 in the above embodiments.
[0080] (Variation Example 3)
[0081] The driver can also input (set) a destination in the map data. In this case, the smartphone 30 obtains the path R from the current location P to the destination, and while the vehicle is traveling along path R from the current location P, it estimates the location Pc that the vehicle has reached at a time Tc when the rest suggestion process begins. For example, the smartphone 30 assumes that the vehicle is traveling at a prescribed average speed and estimates the location Pc. If the distance Δd from location Pc to a facility A1 where the vehicle can stop (e.g., a service area when traveling on a highway) exceeds a threshold Δdth, the smartphone 30 advances the time Tc. For example, the smartphone 30 refers to the map data to search for a facility A2 that is closer than facility A1, and performs the rest suggestion process at a time slightly before the vehicle arrives at facility A2.
[0082] (Variation Example 4)
[0083] At the time Tc during which the smartphone 30 performs rest suggestion processing, it obtains the path R to the facility A1 where the vehicle can be parked and displays the path R on the display device of the notification device 20.
[0084] Symbol Explanation
[0085] 1-Vehicle control device, 10-ECU, 20-Notification device, 30-Smartphone, V0-Vehicle (this vehicle).
Claims
1. A vehicle control device comprising a processor configured to execute a rest suggestion process, wherein the rest suggestion process, upon the fulfillment of predetermined conditions, controls a predetermined notification device to provide information to the driver of the vehicle prompting him to interrupt driving and take a rest, characterized in that, The vehicle control device includes position sensors for sequentially acquiring the current position of the vehicle. The processor is configured to perform the following processing: obtain a rest suggestion timing based on map data, which is configured to identify a first area consisting of roads and a second area other than roads; if the current location is determined to be included in the first area, it is considered that the driver is driving, the duration of this state is obtained as driving time, and the driving time is stored as driving history; when the driver starts driving, a rest suggestion timing is obtained as the timing for executing the next rest suggestion processing based on a first driving time which is the duration of the previous driving, a rest time which is the time the driver rested after the previous driving, and a second driving time which is the total driving time of the driver from a predetermined time point in the past to the current time point. When the time point of the rest suggestion timing is reached at the current time, it is determined that the predetermined condition is met.
2. The vehicle control device according to claim 1, characterized in that, The processor is configured to perform the following processing: select the larger of the value obtained by subtracting the value obtained by multiplying the rest time by a predetermined first coefficient from the first driving time and the value obtained by dividing the second driving time by a predetermined second coefficient; and obtain the time point from the current time point after which the time obtained by subtracting the selected value from a predetermined standard time is elapsed as the rest suggestion timing.
3. The vehicle control device according to claim 1, characterized in that, The processor performs the following processing: when a destination is set, it obtains the path from the current location to the destination; when the vehicle travels along the path from the current location, it infers the location the vehicle will arrive at at the rest suggestion time; when the distance to a first facility from which the vehicle can be parked exceeds a threshold, it searches for a second facility closer than the first facility by referring to the map data; and when the vehicle arrives at a specified location closer than the second facility, it executes the rest suggestion processing.
4. The vehicle control device according to claim 1, characterized in that, The processor is configured to acquire the path to the facility where the vehicle can be parked at the recommended rest time and display the path on a designated display device.
Citation Information
Patent Citations
Operation management system
JP2023172749A