Vehicle control device

The vehicle control device manages mode transitions using predefined APIs and driver intent recognition to prevent immobility in autonomous vehicles by ensuring controlled shifts and mode adherence.

JP2024162003AActive Publication Date: 2024-11-21TOYOTA JIDOSHA KK
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023077120
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-09
Publication Date
2024-11-21
Estimated Expiration
2043-05-09

AI Technical Summary

Technical Problem

Existing autonomous vehicles may become immobile when transitioning from manual to automatic driving modes due to uncontrolled shifts and failure to recognize driver intent, leading to operational failures.

Method used

A vehicle control device with predefined APIs and a processor that manages transitions between manual, automatic, and standby modes, ensuring proper mode changes based on driver input and system commands, preventing immobility by allowing controlled shifts and recognizing driver intentions.

Benefits of technology

Ensures smooth transitions between driving modes, preventing vehicles from becoming immobile by allowing manual operation when necessary and adhering to shift range requirements, thus maintaining operational integrity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024162003000001_ABST
    Figure 2024162003000001_ABST
Patent Text Reader

Abstract

To avoid, when automatic operation is started, a vehicle to be at a standstill.SOLUTION: A vehicle control device is connected between an automatic operation system and a vehicle platform that performs automatic operation according to an instruction from the automatic operation system comprises: a memory where a program is stored; and a processor which performs interface between the automatic operation system and the vehicle platform through executing the program. The processor is transited, when receiving a start command through manual operation in an unknown state, to a pure manual state, transited, when receiving a start command from the automatic operation system in an unknown state, to pre-standby state, transited, when satisfying a transition condition to a standby mode in the pre-standby state, to the standby mode, and transited, when detecting driving intention of an operator in the pre-standby state, to the pure manual state.SELECTED DRAWING: Figure 6
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a vehicle control device, and more particularly to a vehicle control device connected between an autonomous driving system and a vehicle platform that performs autonomous driving in accordance with commands from the autonomous driving system. [Background technology]

[0002] In recent years, development of autonomous driving technology for vehicles has been progressing. For example, in a vehicle control system disclosed in JP 2019-177807 A (Patent Document 1), a vehicle and an information processing device cooperate to perform autonomous driving. The information processing device automatically generates control information using autonomous driving control software and transmits it to the vehicle. The vehicle performs autonomous driving based on the received control information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-177807 A Summary of the Invention [Problem to be solved by the invention]

[0004] It is conceivable that the autonomous driving system may be attached externally to the vehicle body (the vehicle platform described below). Autonomous driving is achieved by the vehicle platform controlling the vehicle according to commands from the autonomous driving system. The vehicle platform has three vehicle modes: a manual driving mode under the control of the driver, an autonomous driving mode under the control of the autonomous driving system, and a standby mode in which the driver cannot basically control the vehicle and the vehicle waits for the autonomous driving system to start control.

[0005] When this vehicle is used for a service of transporting passengers, it is usually considered to be operated by automatic driving. After the vehicle platform is started by the automatic driving system, if the manual driving mode does not transition to the standby mode for some reason, the operator of the vehicle may assume that the vehicle is in the manual driving mode because automatic driving has not started, and may start manual driving. After starting manual driving, when the transition condition to the standby mode is met and the vehicle transitions to the standby mode, if the shift range is not the parking range, the vehicle will not transition to the automatic driving mode even if a command to transition to the automatic driving mode is sent from the automatic driving system. In this situation, when the shift range is switched to the parking range, the operator's operation to switch to another shift range cannot be accepted because the vehicle is in the standby mode, and further, since the vehicle has not transitioned to the automatic driving mode, instructions from the automatic driving system cannot be accepted, so the vehicle may become immobile.

[0006] This disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a vehicle control device that can prevent the vehicle from becoming immobile when autonomous driving begins. [Means for solving the problem]

[0007] The vehicle control device according to the present disclosure is a vehicle control device connected between an autonomous driving system and a vehicle platform that performs autonomous driving according to a command from the autonomous driving system, and includes a memory in which a program including a predetermined API defined for each signal is stored, and a processor that interfaces between the autonomous driving system and the vehicle platform by executing the program. The vehicle control device has a manual driving mode, an autonomous driving mode, and a standby mode as vehicle modes. The manual driving mode includes an unknown state, a pure manual state, and a pre-standby state. The vehicle platform can accept manual driving operations in the manual driving mode, can accept an operation of the shift range to the parking range among the manual driving operations in the standby mode, and can accept a driving command from the autonomous driving system in the autonomous driving mode. The processor transitions to a pure manual state when a manual start command is received in the unknown state, transitions to a pre-standby state when a start command is received from the autonomous driving system in the unknown state, transitions to standby mode when a condition for transitioning to standby mode is met in the pre-standby state, and transitions to the pure manual state when the driver's intention to drive is detected in the pre-standby state.

[0008] According to this configuration, the vehicle is transitioned to the pre-standby state on the condition that a start command is received from the automatic driving system in the unknown state, and is transitioned to the pure manual state on the condition that the driver's intention to drive is detected in the pre-standby state. Therefore, if the intention to drive is detected before transitioning to the standby mode, the vehicle is not transitioned to the standby mode. As a result, it is possible to provide a vehicle control device that can prevent the vehicle from becoming immobile when automatic driving is started.

[0009] The processor may transition to the autonomous driving mode when it receives an autonomous driving transition command from the autonomous driving system in the standby mode and the shift range is the parking range, and may transition to an error state when it receives an autonomous driving transition command from the autonomous driving system in the standby mode and the shift range is not the parking range.

[0010] With this configuration, it is possible to avoid an undesirable situation in which automatic driving is started while the shift range is not in the parking range in the standby mode.

[0011] The processor may transition to the autonomous driving mode on condition that it receives an autonomous driving transition command in the pure manual state.

[0012] With this configuration, it is possible to transition from a state in which manual driving is possible to a state in which automatic driving is possible.

[0013] The processor may transition to the pure manual state on condition that a standby mode stop command is received from the autonomous driving system while in the standby mode.

[0014] With this configuration, even if the vehicle has transitioned to standby mode, if a stop command is received from the autonomous driving system, the vehicle can be made capable of manual driving.

[0015] The processor may transition to the pure manual state on condition that it receives an automatic driving stop command from the automatic driving system while in the automatic driving mode.

[0016] With this configuration, even if the vehicle has transitioned to the autonomous driving mode, if a stop command is received from the autonomous driving system, the vehicle can be made capable of manual driving. [Brief description of the drawings]

[0017] [Figure 1] 1 is a diagram showing an overview of a vehicle according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram showing the configurations of the ADK, VCIB, and VP in more detail. [Diagram 3] FIG. 4 is a state transition diagram for explaining vehicle modes in this embodiment. [Figure 4] 11 is a time chart for explaining a transition from an unknown state to a pre-standby state in a manual driving mode. [Diagram 5] 5 is a time chart for explaining a transition from a pre-standby state to a standby mode in a manual driving mode. [Figure 6] 11 is a time chart for explaining a transition from an unknown state in the manual mode to a pre-standby state and then to a pure manual state. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] 1 is a diagram showing an overview of a vehicle according to an embodiment of the present disclosure. Vehicle 1 is configured to be capable of highly automated driving (e.g., automated driving classified as so-called automated driving level 4 or 5) in which the driving entity is a system. In this example, a situation is assumed in which vehicle 1 is used for an automated driving-related mobility service such as a passenger transport service.

[0019] The vehicle 1 includes an autonomous driving kit (ADK) 10, a vehicle control interface box (VCIB) 20, and a vehicle platform (VP) 30. The ADK 10 can be attached to a VP 30 (such as the rooftop of the VP 30) or detached from the VP 30. The ADK 10 and the VP 30 are connected to each other so as to be able to communicate with each other via the VCIB 20 in accordance with a communication standard such as a controller area network (CAN).

[0020] The ADK10 includes an autonomous driving system (ADS) 11 for autonomously driving the vehicle 1. The ADK10 (ADS11) creates a driving plan for the vehicle 1. The ADK10 outputs various commands (control requests) for driving the vehicle 1 according to the driving plan to the VP30 according to an API (Application Program Interface) defined for each control request. The ADK10 also receives various signals indicating the vehicle state (state of the VP30) from the VP30 according to an API defined for each signal. Then, the ADK10 reflects the vehicle state in the driving plan.

[0021] The VCIB 20 executes a predetermined API defined for each signal to receive various control requests from the ADK 10 and output vehicle status to the ADK 10. When the VCIB 20 receives a control request from the ADK 10, it outputs a control command corresponding to the control request to a system corresponding to the control command via the integrated control manager 41. The VCIB 20 also acquires various pieces of information about the VP 30 from various systems via the integrated control manager 41, and outputs the various pieces of information about the VP 30 to the ADK 10 as vehicle status.

[0022] When the ADK10 is attached, the VP30 can execute automatic driving control in the automatic driving mode in accordance with a control request from the ADK10. When the ADK10 is removed, the VP30 executes driving control in the manual driving mode.

[0023] The VP 30 includes a base vehicle 40. The base vehicle 40 executes various vehicle controls in accordance with control requests from the ADK 10. The base vehicle 40 includes, for example, an integrated control manager 41, a brake system 42, a steering system 43, a powertrain system 44, an active safety system 45, other systems 46 (see FIG. 2), wheel speed sensors 51 and 52, a pinion angle sensor 53, a camera 54, radar sensors 55 and 56, and a power switch 60.

[0024] The integrated control manager 41 includes a processor and a memory, and controls the above-mentioned systems related to the operation of the vehicle 1 in an integrated manner.

[0025] The brake system 42 controls the braking devices provided on each wheel of the base vehicle 40. Wheel speed sensors 51, 52 are connected to the brake system 42. The wheel speed sensors 51, 52 detect the rotation speeds of the front and rear wheels of the base vehicle 40, respectively, and output the detected rotation speeds to the brake system 42. The brake system 42 outputs the rotation speeds of each wheel to the VCIB 20 as one piece of information included in the vehicle state. The integrated control manager 41 calculates the speed (vehicle speed) of the vehicle 1 based on the rotation speeds of each wheel. The brake system 42 also generates a braking command for the braking device according to a predetermined control request output from the ADK 10 via the VCIB 20 and the integrated control manager 41. The brake system 42 controls the braking device using the generated braking command.

[0026] The steering system 43 controls the steering angle of the steering wheels of the vehicle 1 using a steering device. A pinion angle sensor 53 is connected to the steering system 43. The pinion angle sensor 53 detects a rotation angle (pinion angle) of a pinion gear connected to a rotating shaft of an actuator, and outputs the rotation angle to the steering system 43. The steering system 43 outputs the pinion angle to the VCIB 20 as one piece of information included in the vehicle state. The steering system 43 also generates a steering command for the steering device according to a predetermined control request output from the ADK 10 via the VCIB 20 and the integrated control manager 41. The steering system 43 controls the steering device using the generated steering command.

[0027] The powertrain system 44 controls an electric parking brake (EPB) system 441 provided on at least one of the multiple wheels, a parking lock (P-Lock) system 442 provided on the transmission of the vehicle 1, and a propulsion system 443 including a shift device configured to select a shift position.

[0028] The active safety system 45 detects obstacles (pedestrians, bicycles, parked vehicles, utility poles, etc.) in front or behind the vehicle 1 using the camera 54 / radar sensors 55, 56. The active safety system 45 determines whether there is a possibility that the vehicle 1 will collide with the obstacle based on the distance between the vehicle 1 and the obstacle and the moving direction of the vehicle 1. If the active safety system 45 determines that there is a possibility of a collision, it outputs a braking command to the brake system 42 via the integrated control manager 41 so as to increase the braking force.

[0029] The power switch 60 accepts a user's operation to select a power position of the vehicle 1. The power positions include an ignition-off (IG-OFF) position, an accessory (ACC) position, an ignition-on (IG-ON) position, a start position, and a ReadyON position.

[0030] The IG-OFF position corresponds to a power-off state for the vehicle 1. In the IG-OFF position, the power supply to each device installed in the vehicle 1 is cut off. In the ACC position, power is supplied to accessory devices such as the air conditioning system and audio equipment. In the IG-ON position, power is supplied to the accessory devices as well as the systems necessary for driving the vehicle 1. When the start position is selected, the VP30 is started so that the vehicle 1 is ready to be driven. After starting up the VP30, an initial diagnosis (initial check) is performed on the VP30. The initial diagnosis is a diagnosis to confirm that each system within the VP30 is normal. If the initial diagnosis confirms that the VP30 is normal, the VP30 transitions from the start position to the ReadyON position.

[0031] Fig. 2 is a diagram showing in more detail the configurations of the ADK 10, the VCIB 20, and the VP 30. As shown in Fig. 2, the ADK 10 (ADS 11) includes a computer 111, an HMI (Human Machine Interface) 112, a recognition sensor 113, a posture sensor 114, and a sensor cleaner 115.

[0032] During autonomous driving of the vehicle 1, the computer 111 acquires the environment of the vehicle 1, as well as the attitude, behavior, and position of the vehicle 1 using various sensors, acquires the vehicle state from the VP 30 via the VCIB 20, and sets the next operation (acceleration, deceleration, turning, etc.) of the vehicle 1. Then, the computer 111 outputs various commands to the VCIB 20 to realize the next operation. The computer 111 includes communication modules 111A and 111B.

[0033] The HMI 112 presents information to the user and accepts user operations during autonomous driving, during driving that requires user operation, and during transition between autonomous driving and manual driving.

[0034] The recognition sensor 113 is a sensor for recognizing the environment of the vehicle 1. The recognition sensor 113 includes, for example, at least one of a LIDAR (Laser Imaging Detection and Ranging), a millimeter wave radar, and a camera.

[0035] The attitude sensor 114 is a sensor for detecting the attitude, behavior, and position of the vehicle 1. The attitude sensor 114 includes, for example, an IMU (Inertial Measurement Unit) and a GPS (Global Positioning System). The sensor cleaner 115 is configured to remove dirt adhering to the above-mentioned various sensors (camera lenses, laser light irradiation parts, etc.) while the vehicle 1 is traveling, using a cleaning liquid, a wiper, etc.

[0036] The VCIB20 includes a main VCIB21 and a sub VCIB22. The VCIB21 includes a processor 211 and a memory 212. The VCIB22 includes a processor 221 and a memory 222. Each of the memories 212 and 222 includes a ROM (Read Only Memory) and a RAM (Random Access Memory) and stores a program including a predetermined API defined for each signal. Each of the processors 221 and 221 includes a CPU (Central Processing Unit) and executes the above programs to provide an interface between the ADK10 and the VP30.

[0037] The VCIB21 and the communication module 111A are connected to be able to communicate with each other. The VCIB22 and the communication module 111B are connected to be able to communicate with each other. Furthermore, the VCIB21 and the VCIB22 are connected to be able to communicate with each other. Each of the VCIB21 and 22 relays a control request and vehicle information between the ADK10 and the VP30. Specifically, the VCIB21 uses an API to generate a control command from a control request from the ADK10. Then, the VCIB21 outputs the generated control command to a corresponding system among the multiple systems included in the VP30. Furthermore, the VCIB21 uses an API to generate information indicating a vehicle state from vehicle information from each system of the VP30. The VCIB21 outputs the generated information indicating a vehicle state to the ADK10. The same applies to the VCIB22.

[0038] The EPB system 441 controls the EPB in accordance with a control request output from the ADK 10 via the VCIB 21. The EPB is provided separately from a braking device (such as a disc brake system), and locks the wheels by operating an actuator. The P-Lock system 442 controls the P-Lock device in accordance with a control request output from the ADK 10 via the VCIB 21. The P-Lock system 442 activates the P-Lock device when the control request includes a control request to set the shift position to the parking position (P range), and releases the operation of the P-Lock device when the control request includes a control request to set the shift position to a position other than the parking position. The P-Lock device fixes the rotation of the output shaft of the transmission and locks the wheels.

[0039] The propulsion system 443 switches the shift position of a shift device (not shown) and controls the driving force from a driving source (such as a motor generator or an engine) in accordance with a control request output from the ADK 10 via the VCIB 21. The shift positions include, in addition to the parking position, for example, a neutral position (N range), a forward driving position (D range), a reverse driving position (R range), and a brake position (B range).

[0040] The active safety system 45 is connected to the brake system 421 so as to be able to communicate with it. As described above, the active safety system 45 detects an obstacle ahead using the camera 54 and / or the radar sensor 55, and outputs a braking command to the brake system 421 to increase the braking force when it determines that there is a possibility of a collision. The other systems 46 include a body system, an air conditioner, audio equipment, etc. The body system controls parts such as a turn signal, a horn, and wipers according to a control request from the ADK 10.

[0041] In the vehicle 1, the autonomous driving is executed when the autonomous driving mode is selected by the user's operation on the HMI 112. As described above, the ADK 10 first creates a driving plan during the autonomous driving. Examples of the driving plan include a plan to continue driving straight, a plan to turn left / right at a predetermined intersection on a predetermined driving route, and a plan to change the driving lane. The ADK 10 calculates control physical quantities (acceleration, deceleration, tire turning angle, etc.) required for the vehicle 1 to operate according to the created driving plan. The ADK 10 divides the physical quantities for each execution cycle of the API. The ADK 10 outputs a control request representing the divided physical quantities to the VCIB 20 using the API. Furthermore, the ADK 10 acquires the vehicle state (the actual moving direction of the vehicle 1, the state of immobilization of the vehicle, etc.) from the VP 30, and recreates a driving plan that reflects the acquired vehicle state. In this way, the ADK 10 enables the autonomous driving of the vehicle 1.

[0042] 3 is a state transition diagram for explaining the vehicle modes in this embodiment. The VCIB 20 has a standby mode in addition to the manual driving mode and the automatic driving mode. The manual driving mode includes an unknown state, a pure manual state, and a pre-standby state.

[0043] On condition that a ReadyON command is received manually by the user in the unknown state, the VCIB 20 transitions to the pure manual state (see E1). In the pure manual state, the integrated control manager 41 (or another ECU) performs an initial diagnosis.

[0044] After the initial diagnosis is performed, the VCIB 20 transitions to the automatic operation mode (autonomous state) on the condition that it receives an automatic operation transition command from the ADK 10 in the pure manual state (see E3). In the automatic operation mode, the integrated control manager 41 controls the VP 30 according to a request from the ADK 10, thereby realizing automatic operation.

[0045] In the automatic operation mode, upon receiving an automatic operation stop command from the ADK 10, the VCIB 20 transitions to the pure manual state (see E6).

[0046] On the other hand, on condition that the VCIB 20 receives a ReadyON command from the ADK 10 in the unknown state, the VCIB 20 transitions to the pre-standby state (see E2). In the pre-standby state, the integrated control manager 41 (or another ECU) also performs an initial diagnosis. On condition that a transition condition to the standby mode (including, for example, a condition that an initial diagnosis has been performed / is being performed) is satisfied, the VCIB 20 further transitions from the manual driving mode (pre-standby state) to the standby mode (standby state) (see E4). On condition that a manual operation other than the manual operation of changing the shift position to the P range (for example, a predetermined operation for moving the vehicle 1, specifically, an operation of changing to the D, R, B range) is received in the pre-standby state, the VCIB 20 transitions to the pure manual state (see E10).

[0047] In this embodiment, the driver's intention to drive is detected by receiving a manual operation other than the manual operation of changing the shift position to the P range. However, without being limited to this, the driver's intention to drive may be detected by receiving an operation of an operating unit for manual driving (for example, an accelerator pedal, a brake pedal, a steering wheel, a parking brake), or may be detected by detecting that the vehicle speed has become other than 0.

[0048] In this embodiment, the state is changed to the pure manual state when the driving intention is detected. However, the condition for changing to the pure manual state may be, for example, that the state has not changed to the standby mode even after a predetermined period (e.g., 8 seconds) has elapsed since the state changed to the pre-standby state, or may be an AND condition of this condition and the state that the driving intention is detected.

[0049] In the standby mode, manual operations accepted by the VP 30 are suppressed. More specifically, the integrated control manager 41 (which may be an ECU in the propulsion system 443) does not accept a shift operation (a switching operation to a shift position other than the P range) for the shift device of the propulsion system 443. The integrated control manager 41 also does not accept an accelerator operation (depressing the accelerator pedal). Furthermore, the integrated control manager 41 (which may be an ECU in the EPB system 441) does not accept an EPB release operation of the EPB system 441.

[0050] In the standby mode, the VCIB 20 transitions to the automatic driving mode (autonomous state) on condition that an automatic driving transition command is received from the ADK 10 and the shift range is in the P range (see E5). In the standby mode, the VCIB 20 transitions to the error state on condition that an automatic driving transition command is received from the ADK 10 and the shift range is not in the P range.

[0051] When the VCIB20 receives a command to stop standby mode from the ADK10 in the automatic operation mode, the VCIB20 transitions to the manual operation mode (pure manual state) (see E8).

[0052] In the pure manual state, if an IG-OFF operation (typically, an operation to turn off the power switch 60) is performed, the VCIB 20 transitions to the unknown state (see E7).

[0053] FIG. 4 is a time chart for explaining the transition from the unknown state to the pre-standby state in the manual driving mode (see E2). From the top, FIG. 4 shows the power position of VP30, the power mode of VCIB20, the internal state, the power ON request from ADK10, the power mode command from ADK10, the vehicle power processing in VCIB20, the ReadyON processing in VP30 (vehicle 1), and the vehicle mode. The power modes include a wake mode and a driving mode. The wake mode is a mode in which the VCIB20 is activated by power supply from the auxiliary battery of VP30. The driving mode is a mode equivalent to the ReadyON state, in which the VCIB20 and all ECUs are activated, and power is supplied to each system from the high-voltage battery.

[0054] In the unknown state, the ADK10 outputs a command to transition the power mode to the driving mode. Then, in the VCIB20, the power ON request from the ADK10 is set to the ON state, vehicle power processing is executed, and the ReadyON processing is executed in the VP30. As a result, the power position of the VP30 transitions to the ReadyON position. Furthermore, the power mode of the VCIB20 transitions from the wake mode to the driving mode, the internal state transitions from the unknown state to the pre-standby state, and the power ON request from the ADK10 is set to the OFF state.

[0055] Fig. 5 is a time chart for explaining the transition from the pre-standby state of the manual driving mode to the standby mode (see E4). In addition to the items explained in Fig. 4, Fig. 5 shows the vehicle mode command from the ADK 10, standby mode preparation, automatic driving mode preparation, vehicle speed, and shift position.

[0056] When the initial diagnosis is completed in the pre-standby state of the manual driving mode, the internal state transitions from the pre-standby state to the standby state on the condition that the standby mode preparation is completed (for example, vehicle speed = 0). Accordingly, the vehicle mode also transitions from the manual driving mode to the standby mode.

[0057] Fig. 6 is a time chart for explaining the transition to the pure manual state after transition from the unknown state in the manual mode to the pre-standby state (see E10). After the transition to the pre-standby state described in Fig. 4, if the shift position is switched to a position other than the P range, for example, to the R, D, or B range, before transition to the standby mode, the internal state transitions from the pre-standby state to the pure manual state.

[0058] The above-mentioned conditions for the mode and state transition may include other conditions than those described above. The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the disclosure is indicated by the claims rather than the description of the above-mentioned embodiments, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0059] 1 vehicle, 10 ADK, 11 ADS, 111 computer, 111A, 111B communication module, 113 recognition sensor, 114 attitude sensor, 115 sensor cleaner, 20-22 VCIB, 211, 221 processor, 212, 222 memory, 30 VP, 40 base vehicle, 41 integrated control manager, 42, 421, 422 brake system, 43, 431, 432 steering system, 44 power train system, 441 EPB system, 442 P-Lock system, 443 propulsion system, 45 active safety system, 46 body system, 51, 52 wheel speed sensor, 53 pinion angle sensor, 54 camera, 55, 56 radar sensor, 60 power switch.

Claims

1. A vehicle control device connected between an autonomous driving system and a vehicle platform that performs autonomous driving according to a command from the autonomous driving system, A memory in which a program including a predetermined API defined for each signal is stored; a processor that executes the program to interface between the automated driving system and the vehicle platform; The vehicle control device has, as vehicle modes, a manual driving mode, an automatic driving mode, and a standby mode, The manual operation mode includes an unknown state, a pure manual state, and a pre-standby state, The vehicle platform includes: In the manual driving mode, a manual driving operation can be accepted, In the standby mode, a manual operation of the shift range to a parking range can be accepted, In the autonomous driving mode, a driving command from the autonomous driving system can be received, The processor, transitioning to the pure manual state on condition that a start command is received by a manual operation in the unknown state; Transitioning to the pre-standby state on condition that a start command is received from the automatic driving system in the unknown state, transitioning to the standby mode on condition that a transition condition to the standby mode is satisfied in the pre-standby state; A vehicle control device that transitions to the pure manual state on condition that a driver's intention to drive is detected in the pre-standby state.

2. The processor, Transitioning to the autonomous driving mode on condition that an autonomous driving transition command is received from the autonomous driving system in the standby mode and the shift range is the parking range; 2 . The vehicle control device according to claim 1 , wherein the vehicle control device transitions to an error state when the autonomous driving transition command is received from the autonomous driving system in the standby mode and the shift range is not the parking range.

3. The vehicle control device according to claim 1 , wherein the processor transitions to the autonomous driving mode on condition that an autonomous driving transition command is received in the pure manual state.

4. The vehicle control device according to claim 1 , wherein the processor transitions to the pure manual state on condition that a standby mode stop command is received from the autonomous driving system in the standby mode.

5. 5. The vehicle control device according to claim 1, wherein the processor transitions to the pure manual state on condition that an automatic driving stop command is received from the automatic driving system in the automatic driving mode.

Citation Information

Patent Citations

  • Hybrid vehicle and control method thereof

    JP2021160536A

  • Information presentation device for automatic operation vehicle

    JP2022039115A

  • Vehicle control device and vehicle control method

    JP2023009681A

  • Vehicle platform, vehicle control interface box and automatic driving system

    JP2023048306A

  • Control device, program, and control method

    JP2019177807A