VEHICLE CONTROL INTERFACE, AUTONOMOUS DRIVING SYSTEM AND VEHICLE EQUIPPED WITH SAME, AND VEHICLE CONTROL METHOD

Abstract

To appropriately switch between a manual mode and an automatic mode in a vehicle that can be mounted with an automatic operation system.SOLUTION: A VCIB 40 establishes an interface between an automatic operation system (ADS) 11 and a vehicle platform (VP) 20. A vehicle 1 has a normal manual mode which is set when the VP 20 is started, a manned manual mode in which the VP 20 is under the control of an operator, and a manned automatic mode in which the VP 20 is under the control of the ADS 11. The VCIB 40 comprises a processor. The processor is configured (1) to receive from the ADS 11 an operator instruction for transferring a mode of the vehicle 1 from the normal manual mode to the manned manual mode and (2) to output to the ADS 11 an automatic operation preparation signal showing the automatic operation of the VP 20 is prepared, and receive from the ADS 11 an automatic operation request for transferring the mode of the vehicle 1 from the manned manual mode to the manned automatic mode.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to a vehicle control interface. vinegar, The present invention relates to an autonomous driving system, a vehicle equipped with the system, and a method for controlling the vehicle. [Background technology]

[0002] In recent years, the development of autonomous driving technology for vehicles has progressed. For example, JP 2018-132015 A (Patent Document 1) discloses an autonomous driving system that comprehensively executes autonomous driving control of a vehicle. This autonomous driving system includes a camera, a laser device, a radar device, an operation device, a gradient sensor, an autonomous driving device, and an autonomous driving ECU (Electronic Control Unit). [Prior art documents] [Patent documents]

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

[0004] It is possible to mount the autonomous driving system externally on the vehicle itself. In this case, autonomous driving is achieved by the vehicle platform (described later) controlling the vehicle according to commands from the autonomous driving system.

[0005] A vehicle capable of being equipped with an automated driving system may have a manual mode in which the vehicle platform is under the control of an operator (e.g., a driver) and an automated mode in which the vehicle platform is under the control of the automated driving system. There is a need to gracefully switch between the manual mode and the automated mode.

[0006] The present disclosure has been made to solve the above-mentioned problems, and an object of the present disclosure is to appropriately switch between manual mode and automatic mode in a vehicle that can be equipped with an automatic driving system. [Means for solving the problem]

[0007] (1) A vehicle control interface according to an aspect of the present disclosure includes: An autonomous driving system that can be mounted on a vehicle platform; The vehicle platform includes a base vehicle equipped with an integrated control manager, a brake system, a steering system, and a powertrain system, and controls the vehicle according to control requests from the autonomous driving system. Platform The vehicle control interface has a first manual mode that is set when the vehicle platform is activated and does not require an operator to be within the vehicle platform, a second manual mode that requires an operator to be within the vehicle platform and the vehicle platform is under the control of the operator, and an automatic mode in which the vehicle platform is under the control of the automated driving system. The vehicle control interface includes a processor and a memory that stores a program executable by the processor. The processor is configured to determine whether an operator is within the vehicle platform and whether the vehicle platform is under the control of the automated driving system. Platform from the autonomous driving system, and outputs an autonomous driving preparation signal to the autonomous driving system indicating that the vehicle platform is ready for autonomous driving, and Platform An automatic driving request for transitioning from the second manual mode to the automatic mode is received from the automatic driving system.

[0008] (2) The automatic driving request can be switched between a request to set the automatic mode and a request to cancel the automatic mode. In the automatic mode, the processor receives an automatic driving request from the automatic driving system requesting cancellation of the automatic mode.

[0009] (3) Vehicles PlatformThe vehicle control interface further includes a sleep mode in which the vehicle control interface is stopped. Platform A power mode request is received from the autonomous driving system to transition the vehicle from the second manual mode to the sleep mode.

[0010] (4) Vehicles Platform is a vehicle Platform The processor, in transitioning from the first manual mode to the maintenance mode, outputs to the automated driving system a power mode status signal indicating that the vehicle platform is ignition-on, outputs to the automated driving system a driving direction status signal indicating that the shift range is in the P range, and outputs to the automated driving system an actual movement direction signal indicating that the vehicle platform is stopped, Platform A maintenance request is received from the autonomous driving system requesting maintenance of the autonomous driving system.

[0011] (5) The maintenance request can be switched between requesting maintenance of the vehicle platform and not requesting maintenance of the vehicle platform. In the transition from the maintenance mode to the first manual mode, the processor outputs to the automated driving system a power mode status signal indicating that the ignition of the vehicle platform is on, outputs to the automated driving system a driving direction status signal indicating that the shift range is in the P range, and outputs to the automated driving system an actual movement direction signal indicating that the vehicle platform is stopped. Platform A maintenance request is received from the automated driving system stating that no maintenance is required.

[0012] (6 )

[0013] (7) An automated driving system according to still another aspect of the present disclosure, Included in the vehicle vehicle PlatformThe autonomous driving system can be mounted on a vehicle. The vehicle includes a vehicle platform. The vehicle platform includes a base vehicle equipped with an integrated control manager, a brake system, a steering system, and a powertrain system, and controls the base vehicle according to a control request from the autonomous driving system. The vehicle platform has a vehicle control interface that interfaces between the autonomous driving system and the vehicle platform. The vehicle Platform The vehicle control system includes a first manual mode that is set when the vehicle platform is activated and does not require an operator to be within the vehicle platform, a second manual mode that requires an operator to be within the vehicle platform and the vehicle platform is under the control of the operator, and an automatic mode in which the vehicle platform is under the control of the automatic driving system. The automatic driving system includes a computer and a communication module configured to communicate with the vehicle control interface. The computer indicates whether an operator is within the vehicle platform and indicates whether an operator is within the vehicle platform and indicates whether an operator is within the vehicle platform. Platform outputting an operator command to the vehicle control interface for transitioning the vehicle platform from the first manual mode to the second manual mode, receiving an automatic driving preparation signal from the vehicle control interface indicating that the vehicle platform is ready for automatic driving, and Platform An automatic driving request for transitioning the vehicle from the second manual mode to the automatic mode is output to the vehicle control interface.

[0014] (8) The automatic driving request can be switched between requesting the setting of the automatic mode and requesting the cancellation of the automatic mode. In the automatic mode, the computer outputs an automatic driving request to the vehicle control interface to request cancellation of the automatic mode.

[0015] (9) Vehicles Platform The computer further includes a sleep mode in which the vehicle control interface is shut down. Platform A power mode request for transitioning the vehicle from the second manual mode to the sleep mode is output to the vehicle control interface.

[0016] (10) Vehicles Platform is a vehicle Platform The computer further has a maintenance mode for servicing the vehicle platform. In transitioning from the first manual mode to the maintenance mode, the computer receives from the vehicle control interface a power mode status signal indicating that the vehicle platform is ignition-on, receives from the vehicle control interface a drive direction status signal indicating that the shift range is in the P range, receives from the vehicle control interface an actual movement direction signal indicating that the vehicle platform is stopped, and Platform A maintenance request for requesting maintenance of the vehicle is output to the vehicle control interface.

[0017] (11) The maintenance request can be switched between requesting maintenance of the vehicle and not requesting maintenance of the vehicle. When transitioning from the maintenance mode to the first manual mode, the computer receives a power mode status signal from the vehicle control interface indicating that the vehicle platform is ignition on, receives a driving direction status signal from the vehicle control interface indicating that the shift range is in P range, and receives an actual movement direction signal from the vehicle control interface indicating that the vehicle platform is stopped, and outputs a maintenance request to the vehicle control interface indicating that maintenance of the vehicle is not required.

[0018] (12) A vehicle according to yet another aspect of the present disclosure includes the above-described autonomous driving system and a vehicle platform. The vehicle platform includes a base vehicle having an integrated control manager, a braking system, a steering system, and a powertrain system. The vehicle platform has a vehicle control interface that interfaces between the automated driving system and the vehicle platform. The vehicle platform has a first manual mode that is set when the vehicle platform is activated and does not require an operator to be within the vehicle platform, a second manual mode that requires an operator to be within the vehicle platform and the vehicle platform is under the control of the operator, and an automated mode in which the vehicle platform is under the control of the automated driving system.

[0019] (13) According to yet another aspect of the present disclosure, there is provided a method for controlling a vehicle, the vehicle comprising: Equipped with an autonomous driving systemThe vehicle platform includes a base vehicle equipped with an integrated control manager, a brake system, a steering system, and a powertrain system, and controls the base vehicle according to a control request from the autonomous driving system. The vehicle platform includes a vehicle control interface that interfaces between the autonomous driving system and the vehicle platform. The control method controls the vehicle when the vehicle platform is activated without requiring an operator to be in the vehicle platform. Platform a first manual mode; and in the first manual mode, when an operator is within the vehicle platform, Platform transitioning from a first manual mode to a second manual mode; and when, in the second manual mode, the vehicle platform is ready for autonomous driving and an autonomous driving request is output from the autonomous driving system to the vehicle control interface, Platform and transitioning from the second manual mode to the automatic mode, where the second manual mode is a mode in which an operator is required to be present within the vehicle platform and the vehicle platform is under the control of the operator, and the automatic mode is a mode in which the vehicle platform is under the control of the automated driving system.

[0020] (14) The automatic driving request can be switched between a request to set the automatic mode and a request to cancel the automatic mode. The control method includes: when an autonomous driving request for requesting cancellation of the autonomous mode is output from the autonomous driving system to the vehicle control interface, Platform The method further includes the step of transitioning from the automatic mode to a second manual mode.

[0021] (15) Vehicles Platform The control method further includes a sleep mode in which the vehicle control interface is stopped. Platform The method further includes the step of transitioning from the second manual mode to the sleep mode when a power mode request for transitioning the power mode from the second manual mode to the sleep mode is output.

[0022] (16) Vehicles Platform is a vehicle Platform The control method further includes a maintenance mode for servicing the vehicle when the first to fourth conditions are satisfied. Platform The method further includes a step of transitioning from the first manual mode to the maintenance mode. The first condition is a condition that a power mode status signal indicating that the vehicle platform is ignition-on is output from the vehicle control interface to the automated driving system. The second condition is a condition that a driving direction status signal indicating that the shift range is in the P range is output from the vehicle control interface to the automated driving system. The third condition is a condition that an actual movement direction signal indicating that the vehicle platform is stopped is output from the vehicle control interface to the automated driving system. The fourth condition is a condition that a vehicle control interface outputs to the automated driving system an actual movement direction signal indicating that the vehicle platform is stopped. Platform The condition is that a maintenance request has been output requesting maintenance of the equipment.

[0023] (17) The maintenance request can be switched between requesting maintenance of the vehicle platform and not requesting maintenance of the vehicle platform. The control method includes: Platform The method further includes a step of transitioning from the maintenance mode to the first manual mode. The fifth condition is a condition that a power mode status signal indicating that the ignition of the vehicle platform is on is output from the vehicle control interface to the automated driving system. The sixth condition is a condition that a driving direction status signal indicating that the shift range is in the P range is output from the vehicle control interface to the automated driving system. The seventh condition is a condition that an actual movement direction signal indicating that the vehicle platform is stopped is output from the vehicle control interface to the automated driving system. The eighth condition is a condition that a real movement direction signal indicating that the vehicle platform is stopped is output from the vehicle control interface to the automated driving system. Platform The condition is that a maintenance request has been output stating that no maintenance is required. Effect of the Invention

[0024] According to the present disclosure, in a vehicle capable of being equipped with an autonomous driving system, it is possible to appropriately switch between manual mode and autonomous mode. [Brief description of the drawings]

[0025] [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 configuration of ADS, VCIB and VP in more detail. [Diagram 3] This is a state machine that shows the mode transition of the VP. [Figure 4] FIG. 2 is a diagram showing the transmission directions of various signals related to transitions between modes. [Diagram 5] FIG. 13 is a diagram for explaining an operator command. [Figure 6] FIG. 13 is a diagram for explaining an operator feedback signal. [Figure 7] FIG. 11 is a diagram for explaining a power supply mode request. [Figure 8] FIG. 11 is a diagram for explaining a power supply mode status signal. [Figure 9] FIG. 2 is a diagram for explaining a VP automatic driving preparation signal. [Figure 10] FIG. 13 is a diagram for explaining an automatic driving request. [Figure 11] FIG. 2 is a diagram for explaining a VP automatic driving status signal. [Figure 12] FIG. 4 is a diagram for explaining a driving direction status signal. [Figure 13] FIG. 11 is a diagram for explaining an actual movement direction signal. [Figure 14] FIG. 11 is a diagram for explaining a maintenance request. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0026] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference characters, and the description thereof will not be repeated.

[0027] [Embodiment Mode] 1 is a diagram showing an overview of a vehicle according to an embodiment of the present disclosure. The vehicle 1 includes an autonomous driving kit (ADK) 10 and a vehicle platform (VP) 20. The ADK 10 is configured to be attachable to the VP 20 (to be mounted on the vehicle 1). The ADK 10 and the VP 20 are configured to be able to communicate with each other via a vehicle control interface (VCIB 40 described later).

[0028] The VP20 can perform automatic driving according to control requests from the ADK10. Although the ADK10 is shown in a position separate from the VP20 in FIG. 1, the ADK10 is actually attached to the rooftop of the VP20 or the like. The ADK10 can also be removed from the VP20. When the ADK10 is removed, the VP20 performs driving control in manual mode (driving control according to user operation).

[0029] The ADK10 includes an autonomous driving system (ADS) 11 for autonomously driving the vehicle 1. The ADS11 creates, for example, a driving plan for the vehicle 1. The ADS11 outputs various control requests for driving the vehicle 1 according to the driving plan to the VP20 according to an API (Application Program Interface) defined for each control request. The ADS11 also receives various signals indicating the vehicle state (state of the VP20) from the VP20 according to an API defined for each signal. The ADS11 then reflects the vehicle state in the driving plan. A detailed configuration of the ADS11 will be described with reference to FIG. 2.

[0030] The VP 20 includes a base vehicle 30 and a vehicle control interface box (VCIB) 40 .

[0031] The base vehicle 30 executes various vehicle controls in accordance with control requests from the ADK 10 (ADS 11). The base vehicle 30 includes various systems and sensors for controlling the base vehicle 30. More specifically, the base vehicle 30 includes an integrated control manager 31, a brake system 32, a steering system 33, a powertrain system 34, an active safety system 35, a body system 36, wheel speed sensors 51, 52, a pinion angle sensor 53, a camera 54, and radar sensors 55, 56.

[0032] The integrated control manager 31 includes a processor and a memory, and controls the above-mentioned systems related to the operation of the vehicle 1 (the brake system 32, the steering system 33, the powertrain system 34, the active safety system 35, and the body system 36) in an integrated manner.

[0033] The brake system 32 is configured to control a braking device provided on each wheel of the base vehicle 30. The braking device includes, for example, a disc brake system (not shown) that operates in response to hydraulic pressure adjusted by an actuator.

[0034] Wheel speed sensors 51, 52 are connected to the brake system 32. The wheel speed sensor 51 detects the rotation speed of the front wheels of the base vehicle 30 and outputs the detected rotation speed of the front wheels to the brake system 32. The wheel speed sensor 52 detects the rotation speed of the rear wheels of the base vehicle 30 and outputs the detected rotation speed of the rear wheels to the brake system 32. The brake system 32 outputs the rotation speed of each wheel to the VCIB 40 as one of the pieces of information included in the vehicle state. In addition, the brake system 32 generates a braking command for the braking device according to a predetermined control request output from the ADS 11 via the VCIB 40 and the integrated control manager 31. The brake system 32 controls the braking device using the generated braking command. The integrated control manager 31 can calculate the speed (vehicle speed) of the vehicle 1 based on the rotation speed of each wheel.

[0035] The steering system 33 is configured to be able to use a steering device to control the steering angle of the steering wheels of the vehicle 1. The steering device includes, for example, a rack-and-pinion type electric power steering (EPS) that is capable of adjusting the steering angle by an actuator.

[0036] A pinion angle sensor 53 is connected to the steering system 33. The pinion angle sensor 53 detects a rotation angle (pinion angle) of a pinion gear connected to a rotating shaft of the actuator, and outputs the detected pinion angle to the steering system 33. The steering system 33 outputs the pinion angle to the VCIB 40 as one piece of information included in the vehicle state. In addition, the steering system 33 generates a steering command for the steering device according to a predetermined control request output from the ADS 11 via the VCIB 40 and the integrated control manager 31. The steering system 33 controls the steering device using the generated steering command.

[0037] The powertrain system 34 controls an electric parking brake (EPB) system 341 provided on at least one of the wheels, a parking lock (P-Lock) system 342 provided on the transmission of the vehicle 1, and a propulsion system 343 including a shift device (not shown) configured to be able to select a shift range. A more detailed configuration of the powertrain system 34 will be described with reference to FIG. 2.

[0038] The active safety system 35 detects obstacles (pedestrians, bicycles, parked vehicles, utility poles, etc.) in front or behind the vehicle 1 using the camera 54 and radar sensors 55, 56. The active safety system 35 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 35 determines that there is a possibility of a collision, it outputs a braking command to the brake system 32 via the integrated control manager 31 so as to increase the braking force.

[0039] The body system 36 is configured to control parts such as turn signals, a horn, and windshield wipers (none of which are shown) according to the driving state or environment of the vehicle 1. The body system 36 controls each of the above parts in accordance with a predetermined control request output from the ADS 11 via the VCIB 40 and the integrated control manager 31.

[0040] The VCIB40 is configured to be able to communicate with the ADS11 via a CAN (Controller Area Network) or the like. The VCIB40 executes a predetermined API defined for each signal to receive various control requests from the ADS11 and output a vehicle state to the ADS11. When the VCIB40 receives a control request from the ADK202, it outputs a control command corresponding to the control request to a system corresponding to the control command via the integrated control manager 31. In addition, the VCIB40 acquires various information about the base vehicle 30 from various systems via the integrated control manager 31, and outputs the state of the base vehicle 30 to the ADS11 as a vehicle state.

[0041] The vehicle 1 can be used as one of the components of a MaaS (Mobility as a Service) system. In addition to the vehicle 1, the MaaS system includes, for example, a data server and a mobility service platform (MSPF) (neither of which is shown).

[0042] The MSPF is a unified platform to which various mobility services are connected. Autonomous driving-related mobility services are connected to the MSPF. In addition to autonomous driving-related mobility services, mobility services provided by ride-sharing operators, car-sharing operators, rental car operators, taxi operators, insurance companies, etc. can be connected to the MSPF.

[0043] Vehicle 1 further includes a Data Communication Module (DCM) (not shown) capable of wireless communication with a data server. The DCM outputs vehicle information such as speed, position, and autonomous driving state to the data server. In addition, the DCM receives various data for managing the traveling of autonomous vehicles including vehicle 1 in an autonomous driving-related mobility service from the mobility service via the MSPF and the data server.

[0044] In MSPF, APIs for using various vehicle status and vehicle control data required for the development of ADS11 are published. Various mobility services can use the APIs published on MSPF to use various functions provided by MSPF according to the service content. For example, an autonomous driving-related mobility service can use the APIs published on MSPF to obtain vehicle 1's driving control data and information stored in a data server from MSPF. In addition, an autonomous driving-related mobility service can use the above APIs to send data for managing autonomous driving vehicles, including vehicle 1, to MSPF.

[0045] <Detailed configuration> Fig. 2 is a diagram showing in more detail the configurations of the ADS 11, the VCIB 40, and the VP 20. As shown in Fig. 2, the ADS 11 includes a computer 111, an HMI (Human Machine Interface) 112, a recognition sensor 113, an attitude sensor 114, and a sensor cleaner 115.

[0046] 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 (described later), and also acquires the vehicle state from the VP 20 via the VCIB 40 to set the next operation of the vehicle 1 (acceleration, deceleration, turning, etc.). The computer 111 outputs various commands to the VCIB 40 to realize the next operation. The computer 111 includes communication modules 111A and 111B. Each of the communication modules 111A and 111B is configured to be able to communicate with the VCIB 40.

[0047] The HMI 112 presents information to the user and accepts user operations during automatic driving, during driving requiring user operation, during transition between automatic driving and driving requiring user operation, etc. The HMI 112 is configured to be connected to an input / output device (not shown) such as a touch panel display provided on the base vehicle 30, for example.

[0048] The recognition sensor 113 is a sensor for recognizing the environment of the vehicle 1. The recognition sensor 113 includes at least one of, for example, a LIDAR (Laser Imaging Detection and Ranging), a millimeter wave radar, and a camera (none of which are shown). The LIDAR measures the distance and direction of an object by, for example, emitting infrared pulse laser light and detecting the reflected light of the laser light from the object. The millimeter wave radar measures the distance and direction of an object by emitting millimeter waves and detecting the reflected wave of the millimeter waves from the object. The camera is, for example, disposed behind the rear-view mirror, and captures an image of the area ahead of the vehicle 1.

[0049] 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) (neither shown). The IMU detects, for example, the acceleration in the forward / backward, left / right, and up / down directions of the vehicle 1, and the angular velocities in the roll, pitch, and yaw directions of the vehicle 1. The GPS detects the position of the vehicle 1 using information received from multiple GPS satellites orbiting the Earth.

[0050] 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.

[0051] The VCIB40 includes a VCIB41 and a VCIB42. Although neither of the VCIB41 and VCIB42 is shown, each of the VCIB41 and VCIB42 includes a processor such as a CPU (Central Processing Unit) and a memory such as a ROM (Read Only Memory) and a RAM (Random Access Memory). The memory stores a program executable by the processor. The VCIB41 and the communication module 111A are connected to each other so as to be able to communicate with each other. The VCIB42 and the communication module 111B are connected to each other so as to be able to communicate with each other. Furthermore, the VCIB41 and the VCIB42 are connected to each other so as to be able to communicate with each other.

[0052] Each of the VCIBs 41 and 42 relays control requests and vehicle information between the ADS 11 and the VP 20. More specifically, the VCIB 41 uses an API to generate a control command from a control request from the ADS 11. The control command corresponding to the control request supplied from the ADS 11 to the VCIB 40 includes, for example, a propulsion direction command requesting switching of the shift range, a stationary command requesting activation / deactivation of the EPB system 341 and the P-Lock system 342, an acceleration command requesting acceleration or deceleration of the vehicle 1, a tire turning angle command requesting the tire turning angle of the steering wheel, and an autonomy command requesting switching between an autonomous mode and a manual mode. The VCIB 41 then outputs the generated control command to a corresponding system among the multiple systems included in the VP 20. The VCIB 41 also uses an API to generate information indicating a vehicle state from vehicle information from each system of the VP 20. The information indicating the vehicle state may be the same information as the vehicle information, or may be information extracted from the vehicle information to be used in the processing executed by the ADS 11. The VCIB 41 outputs the generated information indicating the vehicle state to the ADS 11. The same applies to the VCIB 42.

[0053] The brake system 32 includes brake systems 321 and 322. The steering system 33 includes steering systems 331 and 332. The powertrain system 34 includes an EPB system 341, a P-Lock system 342, and a propulsion system 343.

[0054] Although the VCIB41 and VCIB42 basically have the same functions, there are some differences between the VCIB41 and VCIB42 in the connections to the systems including the VP20. Specifically, the VCIB41, the brake system 321, the steering system 331, the EPB system 341, the P-Lock system 342, the propulsion system 343, and the body system 36 are connected to each other via a communication bus so as to be able to communicate with each other. The VCIB42, the brake system 322, the steering system 332, and the P-Lock system 342 are connected to each other via a communication bus so as to be able to communicate with each other.

[0055] In this way, the VCIB 40 includes the VCIBs 41 and 42 that have equivalent functions for some system operations (braking, steering, etc.), making the control system between the ADS 11 and the VP 20 redundant. Therefore, if any failure occurs in the system, the function of the VP 20 can be maintained by appropriately switching the control system or cutting off the control system in which the failure occurs.

[0056] Each of the brake systems 321 and 322 is configured to be able to control a brake device. The brake system 321 generates a braking command for the brake device according to a control request output from the ADS 11 via the VCIB 41. The brake system 322 generates a braking command for the brake device according to a control request output from the ADS 11 via the VCIB 42. The brake systems 321 and 322 may have equivalent functions. Alternatively, one of the brake systems 321 and 322 may be configured to be able to independently control the braking force of each wheel, and the other may be configured to be able to control the same braking force to be generated in each wheel. For example, the brake systems 321 and 322 may control the brake device using a braking command generated by one of the brake systems, and when an abnormality occurs in the brake system, control the brake device using a braking command generated by the other brake system.

[0057] Each of the steering systems 331 and 332 is configured to be able to control the steering angle of the steering wheels of the vehicle 1 using a steering device. The steering system 331 generates a steering command for the steering device according to a control request output from the ADS 11 via the VCIB 41. The steering system 332 generates a steering command for the steering device according to a control request output from the ADS 11 via the VCIB 42. The steering systems 331 and 332 may have equivalent functions. Alternatively, the steering systems 331 and 332 may control the steering device using a steering command generated by one of the steering systems, and when an abnormality occurs in the steering system, control the steering device using a steering command generated by the other steering system.

[0058] The EPB system 341 controls the EPB in accordance with a control request output from the ADS 11 via the VCIB 41. The EPB is provided separately from a braking device (such as a disc brake system) and fixes the wheels by operating an actuator. For example, the EPB fixes the wheels by operating drum brakes for parking brakes provided on some of the multiple wheels using an actuator, or fixes the wheels by operating the braking device using an actuator that can adjust the hydraulic pressure supplied to the braking device, separate from the brake systems 321 and 322.

[0059] In this embodiment, the EPB system 341 has a brake hold function and is configured to be able to switch between activation and release of the brake hold. The brake hold function of the EPB system 341 will be described in detail with reference to FIGS.

[0060] The P-Lock system 342 controls the P-Lock device in accordance with a control request output from the ADS 11 via the VCIB 41. For example, the P-Lock system 342 activates the P-Lock device when the control request includes a control request to set the shift range to a parking range (P range), and deactivates the P-Lock device when the control request includes a control request to set the shift range to a range other than the P range. The P-Lock device engages a protrusion at the tip of a parking lock pole, the position of which can be adjusted by an actuator, with the teeth of a gear (lock gear) that is connected to a rotating element in the transmission of the vehicle 1. This fixes the rotation of the output shaft of the transmission, and locks the wheels.

[0061] The propulsion system 343 switches the shift range of the shift device and controls the driving force from the driving source (motor generator, engine, etc.) in accordance with a control request output from the ADS 11 via the VCIB 41. In addition to the P range, the shift range includes, for example, a neutral range (N range), a forward driving range (D range), and a reverse driving range (R range).

[0062] The active safety system 35 is communicatively connected to the brake system 321. As described above, the active safety system 35 detects an obstacle ahead using the camera 54 and / or the radar sensor 55, and outputs a braking command to the brake system 321 to increase the braking force when it determines that there is a possibility of a collision.

[0063] The body system 36 controls components such as turn indicators, a horn, and wipers in accordance with a control request output from the ADS 11 via the VCIB 41.

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

[0065] <Mode transition> 3 is a state machine showing mode transitions of the vehicle 1. In this example, the vehicle 1 has a sleep mode, two manual modes, one automatic mode, and a maintenance mode. The two manual modes are a normal manual mode and an attended manual mode. The one automatic mode is an attended automatic mode.

[0066] <Sleep mode> Sleep mode is a mode in which most of the system, including the VCIB40, is stopped. Immediately after startup, the VP20 (including the VCIB40) is in sleep mode. In sleep mode, the ADS11 cannot output any control commands to the VP20. Device authentication by the VCIB40 for the ADS11 has not been performed either.

[0067] In the sleep mode, the integrated control manager 31 and the VCIB 40 are both stopped, so that the operator feedback signal, the power supply mode status signal, and the VP automatic operation state signal are not used. Each signal will be described in detail later.

[0068] <Normal manual mode> The normal manual mode is a mode similar to that of a normal vehicle (a vehicle not compatible with autonomous driving), i.e., a mode in which the VP20 is under the control of an operator (driver, passenger, etc.). In the normal manual mode, the operator may or may not be present in the vehicle cabin (inside the VP20). The normal manual mode corresponds to the "first manual mode" according to the present disclosure.

[0069] In normal manual mode, the operator feedback signal = "unknown". The power mode status signal = "ignition on" or "drive mode". The VP automatic operation status signal = "manual mode".

[0070] <Manned manual mode> The attended manual mode is a manual mode in which an operator is present in the vehicle cabin. In the attended manual mode, the VCIB 40 is authenticated and can communicate with the VP 20 (integrated control manager 31). However, the VP 20 is under the control of the operator, not the ADS 11. The attended manual mode corresponds to the "second manual mode" according to the present disclosure.

[0071] In attended manual mode, the operator feedback signal = "attended". The power mode status signal = "ignition on" or "drive mode". The VP automatic operation status signal = "manual mode".

[0072] It is possible to determine whether an operator is in the vehicle cabin by various known methods. For example, the presence / absence of an operator can be determined by analyzing images from a camera that captures the interior of the vehicle cabin. Instead of or in addition to a camera, the operation status of an HMI (Human Machine Interface) in the vehicle cabin, the detection value of a load sensor installed in the seat, the fastening status of a seat belt, the opening / closing status of a door, etc. may be used.

[0073] <Manned automatic mode> The attended automatic mode is a mode in which the VP 20 is under the control of the ADS 11 and automatic driving of the vehicle 1 is possible. The attended automatic mode corresponds to the "automatic mode" according to the present disclosure.

[0074] In attended automatic mode, the operator feedback signal = "attended", the power mode status signal = "drive mode", and the VP automatic operation status signal = "automatic mode".

[0075] <Maintenance mode> The maintenance mode is a mode for servicing the vehicle 1. In the maintenance mode, the wheels are locked by the P-Lock system 342 to prevent the vehicle 1 from moving. Furthermore, the integrated control manager 31 rejects a power-on request even if the operator presses a start button (not shown). This is to prevent the engine from starting (which would result in the generation of exhaust gas indoors) if the vehicle 1 is a hybrid vehicle or the like.

[0076] A vehicle configuration having only one manual mode is also conceivable. In contrast, the vehicle 1 according to the present embodiment has two manual modes (normal manual mode and manned manual mode). The vehicle 1 transitions from the normal manual mode to the manned manual mode once, and then to the manned automatic mode. In other words, the vehicle 1 interposes the manned manual mode between the normal manual mode and the manned automatic mode. When directly transitioning from the normal manual mode to the manned automatic mode, it is required to determine whether or not an operator is present in the vehicle cabin. However, by interposing the manned manual mode, it is guaranteed that an operator is present in the vehicle cabin when determining whether or not to transition to the manned automatic mode. Thus, according to the present embodiment, switching from the manual mode to the automatic mode becomes smooth, and an appropriate mode transition can be realized.

[0077] Next, the transitions between the above five modes will be described in detail. Figure 4 is a diagram showing the transmission directions of various signals or commands related to the transitions between modes. During the mode transition, the VCIB 40 receives a power mode request, an operator command, an automatic operation request, or a maintenance request from the ADS 11. The VCIB 40 also outputs a power mode status signal, an operator feedback signal, a VP automatic operation state signal, a VP automatic operation preparation signal, a drive direction status signal, or an actual movement direction signal to the ADS 11.

[0078] 5 to 13 are diagrams for explaining signals or commands related to mode transitions. Transitions a to f, transition l, and transition m shown in FIG.

[0079] ≪Transition a≫ In the sleep mode, when an operator presses the start button with a physical key (not shown) such as a smart key being present inside the vehicle cabin, the vehicle 1 transitions from the sleep mode to the normal manual mode.

[0080] ≪Transition b≫ In the normal manual mode, when the operator presses the start button with the physical key present inside the vehicle cabin, the vehicle 1 transitions from the normal manual mode to the sleep mode.

[0081] ≪Transition c≫ In the normal manual mode, when (1) the VCIB 40 is authenticated by the VP 20 (integrated control manager 31) and (2) an operator is present in the vehicle cabin, the vehicle 1 transitions from the normal manual mode to the attended manual mode.

[0082] More specifically, the ADS11 outputs an operator command to the VCIB40, which indicates whether an operator is present in the vehicle cabin. The VCIB40 interfaces with the integrated control manager 31 for operator commands (or commands equivalent to the operator command). As shown in FIG. 5, the operator command indicates one of "no request", "attended", and "unattended". When the operator command = "attended", the integrated control manager 31 can determine that an operator is present in the vehicle cabin. The integrated control manager 31 feeds back the presence or absence of an operator in the vehicle cabin to the ADS11 using an operator feedback signal (see FIG. 6). Note that when the VP20 is started, the operator feedback signal = "unknown".

[0083] ≪Transition d≫ In the attended manual mode, (1) when VP20 transitions to the vehicle power off state (ReadyOFF), or (2) when the operator presses the start button with the physical key present in the vehicle cabin, the vehicle 1 transitions from the attended manual mode to the sleep mode.

[0084] More specifically, the ADS 11 outputs a power mode request to the VCIB 40 to control the power mode of the vehicle 1. The VCIB 40 interfaces with the integrated control manager 31 for the power mode request (or a request equivalent to the power mode request). As shown in FIG. 7, the power mode request indicates any one of "no request", "sleep" indicating a vehicle power off state (ReadyOFF), "wake" indicating that the VCIB 40 is running, "ignition on", and "drive mode" indicating a vehicle power on state (ReadyON). When the power mode request = "sleep", the integrated control manager 31 transitions the VP 20 to a vehicle power off state.

[0085] The VCIB 40 outputs a power mode status signal indicating the power mode of the vehicle 1 to the ADS 11 based on a signal from the integrated control manager 31. As shown in Fig. 8, the power mode status signal indicates one of "sleep", "wake", "ignition on", and "drive mode".

[0086] ≪Transition e≫ manned In the manual mode, when (1) the VP20 is ready for automatic driving and (2) automatic driving is requested from the ADS11 to the VCIB40, the vehicle 1: manned Transition from manual mode to manned automatic mode.

[0087] More specifically, the VCIB 40 outputs a VP Autonomy Ready signal indicating whether the vehicle 1 can transition to the manned automatic mode to the ADS 11. The VP Autonomy Ready signal is generated by the VCIB 40 based on a signal from the integrated control manager 31. As shown in Fig. 9, the VP Autonomy Ready signal indicates any one of "Not Ready For Autonomy", "Ready For Autonomy", and "Invalid".

[0088] Meanwhile, the ADS 11 outputs an autonomy request that controls the transition between manual mode and auto mode to the VCIB 40. The VCIB 40 interfaces with the integrated control manager 31 for autonomy requests (or requests equivalent to autonomy requests). As shown in FIG. 10, an autonomy request indicates either "No Request For Autonomy," "Request For Autonomy," or a "Deactivation Request," which is a request for transition to manual mode. The VP autonomy state signal indicates either "manual mode" or "autonomy mode" (see FIG. 11).

[0089] Vehicle 1 transitions from normal manual mode to manned automatic mode when the VP automatic driving preparation signal = "automatic driving preparation complete" and the automatic driving request = "automatic driving requested".

[0090] ≪Transition f≫ In the manned automatic mode, when a transition to the manual mode is requested from the ADS 11 to the integrated control manager 31 via the VCIB 40, the vehicle 1 switches from the manned automatic mode to the manned More specifically, when the autonomous driving request is "cancel request", the vehicle 1 transitions from the manned autonomous mode to the manual mode. manned Switch to manual mode.

[0091] ≪Transition l≫ In the normal manual mode, vehicle 1 transitions from normal manual mode to maintenance mode when (1) VCIB40 is authenticated by VP20, (2) VP20 has its ignition turned on, (3) the shift range is in P range, (4) vehicle 1 is stopped, and (5) there is a maintenance request from ADS11.

[0092] More specifically, the VCIB 40 outputs a propulsion direction status signal (Propulsion Direction Status) indicating the current shift range to the ADS 11. The propulsion direction status signal is generated by the VCIB 40 based on a signal from the integrated control manager 31. As shown in Fig. 12, the propulsion direction status signal indicates any one of "P range", "R range", "N range", "D range", "B range", and "Invalid (shift range undefined)".

[0093] The VCIB 40 also outputs an actual moving direction signal (Actual Moving Direction) indicating the traveling direction of the vehicle 1 to the ADS 11. The actual moving direction signal is also generated by the VCIB 40 based on a signal from the integrated control manager 31. As shown in Fig. 13, the actual moving direction signal indicates any one of "forward", "reverse", "standstill", and "undefined". The actual moving direction signal indicating "standstill" is output when the speed of the four wheels is 0 for a certain period of time.

[0094] On the other hand, the ADS 11 outputs a maintenance request indicating a request for maintenance of the vehicle 1 to the VCIB 40. The VCIB 40 interfaces with the integrated control manager 31 for the maintenance request (or a request equivalent to the maintenance request). As shown in Fig. 14, the maintenance request indicates either "no request" or "requested".

[0095] The vehicle 1 transitions from the normal manual mode to the maintenance mode when the driving direction status signal = "P range", the actual movement direction signal = "stopped", and the maintenance request = "requested".

[0096] ≪Transition m≫ In the maintenance mode, the vehicle 1 transitions from the maintenance mode to the normal manual mode when (1) the ignition of the VP 20 is on, (2) the shift range is in the P range, (3) the vehicle 1 is stopped, and (4) there is no maintenance request from the ADS 11. More specifically, the vehicle 1 transitions from the maintenance mode to the normal manual mode when the driving direction status signal = "P range", the actual movement direction signal = "stopped", and the maintenance request = "no request".

[0097] As described above, in this embodiment, the manned manual mode is used for transition from the manual mode to the automatic mode. The vehicle 1 transitions from the normal manual mode to the manned manual mode and then to the manned automatic mode. By interposing the manned manual mode between the normal manual mode and the manned automatic mode, it is ensured that an operator is present in the vehicle cabin when determining whether or not to transition to the manned automatic mode. Therefore, according to this embodiment, in the vehicle 1 capable of mounting the ADS11, switching from the manual mode to the automatic mode becomes smooth, and an appropriate mode transition can be realized.

[0098] In addition, the source of the transition to the maintenance mode in the vehicle 1 is the normal manual mode (transition l). This is because, unlike the manned automatic mode, the presence of an operator in the vehicle cabin is not required in the maintenance mode. If an attempt is made to realize the maintenance mode in a vehicle configuration that has only one manual mode, the conditions for determining whether the single manual mode can be transitioned to the automatic mode or whether the single manual mode can be transitioned to the maintenance mode become complicated, which may make the implementation of ADS11 complicated.

[0099] In contrast, in this embodiment, the manual mode is divided into a normal manual mode and a manned manual mode. This simplifies the conditions for determining whether or not a transition between the normal manual mode and the maintenance mode (transitions l and m) is possible, and also simplifies the conditions for determining whether or not a transition between the manned manual mode and the manned automatic mode (transitions e and f) is possible. This makes it possible to reduce the difficulty of implementing the ADS11.

[0100] [Example] TIFF0007643277000001.tif208144

[0101] TIFF0007643277000002.tif208147

[0102] TIFF0007643277000003.tif208144

[0103] TIFF0007643277000004.tif208144

[0104] TIFF0007643277000005.tif208147

[0105] TIFF0007643277000006.tif208147

[0106] TIFF0007643277000007.tif208144

[0107] TIFF0007643277000008.tif208144

[0108] TIFF0007643277000009.tif208144

[0109] TIFF0007643277000010.tif208144

[0110] TIFF0007643277000011.tif208144

[0111] TIFF0007643277000012.tif208144

[0112] TIFF0007643277000013.tif208144

[0113] TIFF0007643277000014.tif208144

[0114] TIFF0007643277000015.tif208144

[0115] TIFF0007643277000016.tif208144

[0116] TIFF0007643277000017.tif208144

[0117] TIFF0007643277000018.tif208144

[0118] TIFF0007643277000019.tif208144

[0119] TIFF0007643277000020.tif208144

[0120] TIFF0007643277000021.tif208144

[0121] TIFF0007643277000022.tif208144

[0122] TIFF0007643277000023.tif208144

[0123] TIFF0007643277000024.tif208146

[0124] TIFF0007643277000025.tif208144

[0125] TIFF0007643277000026.tif208146

[0126] TIFF0007643277000027.tif208144

[0127] TIFF0007643277000028.tif208144

[0128] TIFF0007643277000029.tif208144

[0129] TIFF0007643277000030.tif208144

[0130] TIFF0007643277000031.tif208146

[0131] TIFF0007643277000032.tif208146

[0132] TIFF0007643277000033.tif208144

[0133] TIFF0007643277000034.tif208144

[0134] TIFF0007643277000035.tif208144

[0135] TIFF0007643277000036.tif208144

[0136] TIFF0007643277000037.tif208144

[0137] TIFF0007643277000038.tif208144

[0138] TIFF0007643277000039.tif208144

[0139] TIFF0007643277000040.tif208144

[0140] TIFF0007643277000041.tif208144

[0141] TIFF0007643277000042.tif208144

[0142] TIFF0007643277000043.tif208144

[0143] TIFF0007643277000044.tif208144

[0144] TIFF0007643277000045.tif208144

[0145] TIFF0007643277000046.tif208144

[0146] TIFF0007643277000047.tif208144

[0147] TIFF0007643277000048.tif208144

[0148] TIFF0007643277000049.tif208144

[0149] TIFF0007643277000050.tif208144

[0150] TIFF0007643277000051.tif208144

[0151] TIFF0007643277000052.tif208144

[0152] TIFF0007643277000053.tif208144

[0153] TIFF0007643277000054.tif208144

[0154] TIFF0007643277000055.tif208144

[0155] TIFF0007643277000056.tif208144

[0156] TIFF0007643277000057.tif208144

[0157] TIFF0007643277000058.tif208144

[0158] TIFF0007643277000059.tif208144

[0159] TIFF0007643277000060.tif208144

[0160] TIFF0007643277000061.tif208144

[0161] TIFF0007643277000062.tif208144

[0162] TIFF0007643277000063.tif208144

[0163] TIFF0007643277000064.tif208144

[0164] TIFF0007643277000065.tif208144

[0165] TIFF0007643277000066.tif208144

[0166] TIFF0007643277000067.tif208144

[0167] TIFF0007643277000068.tif208144

[0168] TIFF0007643277000069.tif208144

[0169] TIFF0007643277000070.tif208144

[0170] TIFF0007643277000071.tif208144

[0171] TIFF0007643277000072.tif208144

[0172] TIFF0007643277000073.tif208144

[0173] TIFF0007643277000074.tif208144

[0174] TIFF0007643277000075.tif208144

[0175] TIFF0007643277000076.tif208144

[0176] TIFF0007643277000077.tif208144

[0177] TIFF0007643277000078.tif208147

[0178] TIFF0007643277000079.tif208144

[0179] TIFF0007643277000080.tif208144

[0180] TIFF0007643277000081.tif208144

[0181] TIFF0007643277000082.tif208144

[0182] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present disclosure is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0183] 1 Vehicle, 10 Autonomous Driving Kit (ADK), 11 Autonomous Driving System (ADS), 111 Computer, 111A, 111B Communication Module, 113 Recognition Sensor, 114 Attitude Sensor, 115 Sensor Cleaner, 20 Vehicle Platform (VP), 30 Base Vehicle, 31 Integrated Control Manager, 32, 321, 322 Brake System, 33, 331, 332 Steering System, 34 Power Train System, 341 EPB, 342 P-Lock System, 343 Propulsion System, 35 Active Safety System, 36 Body System, 40-42 Vehicle Control Interface Box (VCIB), 51, 52 Wheel Speed ​​Sensor, 53 Pinion Angle Sensor, 54 Camera, 55, 56 Radar Sensor.

Claims

1. A vehicle control interface that interfaces between an automated driving system mountable on a vehicle platform and the vehicle platform, comprising: The vehicle platform includes a base vehicle equipped with an integrated control manager, a brake system, a steering system, and a powertrain system; The vehicle platform includes: a first manual mode that is established when the vehicle platform is powered up and does not require an operator to be present within the vehicle platform; a second manual mode in which the operator is required to be within the vehicle platform and the vehicle platform is under the control of the operator; an autonomous mode in which the vehicle platform is under control of the autonomous driving system; The vehicle control interface includes: A processor; a memory for storing a program executable by the processor; The processor, receiving an operator command from the automated driving system indicating whether the operator is within the vehicle platform and to transition the vehicle platform from the first manual mode to the second manual mode; A vehicle control interface that outputs an autonomous driving readiness signal to the autonomous driving system indicating that the vehicle platform is ready for autonomous driving, and receives an autonomous driving request from the autonomous driving system to transition the vehicle platform from the second manual mode to the autonomous mode.

2. The automatic driving request can be switched between a request to set the automatic mode and a request to cancel the automatic mode, The vehicle control interface of claim 1 , wherein the processor receives, in the automatic mode, the automatic driving request from the automatic driving system requesting cancellation of the automatic mode.

3. the vehicle platform further having a sleep mode in which the vehicle control interface is shut down; 3. The vehicle control interface of claim 1, wherein the processor receives, in the second manual mode, a power mode request from the automated driving system to transition the vehicle platform from the second manual mode to the sleep mode.

4. the vehicle platform further having a maintenance mode for servicing the vehicle platform; In transitioning from the first manual mode to the maintenance mode, the processor outputting a power mode status signal to the automated driving system indicating that the vehicle platform is ignited; outputting a driving direction status signal indicating that the shift range is in the P range to the automatic driving system; outputting an actual movement direction signal to the automated driving system indicating that the vehicle platform is stopped; The vehicle control interface according to any one of claims 1 to 3, further comprising: a vehicle control interface configured to receive a maintenance request from the autonomous driving system requesting maintenance of the vehicle platform.

5. The maintenance request can be switched between requesting maintenance of the vehicle platform and not requesting maintenance of the vehicle platform; In transitioning from the maintenance mode to the first manual mode, the processor outputting the power mode status signal to the automated driving system indicating that the vehicle platform is ignited; outputting the driving direction status signal indicating that the shift range is the P range to the automated driving system; outputting the actual travel direction signal to the automated driving system indicating that the vehicle platform is stopped; 5. The vehicle control interface of claim 4, wherein the maintenance request received from the automated driving system does not require servicing of the vehicle platform.

6. An automated driving system that can be mounted on a vehicle platform included in a vehicle, The vehicle platform includes a base vehicle equipped with an integrated control manager, a brake system, a steering system, and a powertrain system; the vehicle platform includes a vehicle control interface for interfacing between the automated driving system and the vehicle platform; The vehicle platform includes: a first manual mode that is established when the vehicle platform is powered up and does not require an operator to be present within the vehicle platform; a second manual mode in which the operator is required to be within the vehicle platform and the vehicle platform is under the control of the operator; an autonomous mode in which the vehicle platform is under control of the autonomous driving system; The automated driving system includes: A computer, A communication module configured to be able to communicate with the vehicle control interface, The computer includes: outputting an operator command to the vehicle control interface indicating whether the operator is within the vehicle platform and for transitioning the vehicle platform from the first manual mode to the second manual mode; An autonomous driving system that receives an autonomous driving preparation signal from the vehicle control interface indicating that the vehicle platform is ready for autonomous driving, and outputs an autonomous driving request to the vehicle control interface to transition the vehicle platform from the second manual mode to the autonomous mode.

7. The automatic driving request is switchable between requesting the automatic mode to be set and requesting the automatic mode to be cancelled, The automatic driving system according to claim 6 , wherein the computer outputs the automatic driving request requesting cancellation of the automatic mode to the vehicle control interface in the automatic mode.

8. the vehicle platform further having a sleep mode in which the vehicle control interface is shut down; 8. The automated driving system of claim 7, wherein the computer, in the second manual mode, outputs a power mode request to the vehicle control interface to transition the vehicle platform from the second manual mode to the sleep mode.

9. the vehicle platform further having a maintenance mode for servicing the vehicle platform; In transitioning from the first manual mode to the maintenance mode, the computer receiving a power mode status signal from the vehicle control interface indicating that the vehicle platform is ignited on; receiving a drive direction status signal from the vehicle control interface indicating that the shift range is P range; receiving an actual direction of travel signal from the vehicle control interface indicating that the vehicle platform is stopped; The autonomous driving system according to any one of claims 6 to 8, further comprising: outputting a maintenance request requesting maintenance of the vehicle platform to the vehicle control interface.

10. The maintenance request can be switched between requesting maintenance of the vehicle platform and not requesting maintenance of the vehicle platform; In transitioning from the maintenance mode to the first manual mode, the computer receiving the power mode status signal from the vehicle control interface indicating that the vehicle platform is ignited on; receiving the driving direction status signal indicating that the shift range is a P range from the vehicle control interface; receiving the actual direction of travel signal from the vehicle control interface indicating that the vehicle platform is stopped; The automated driving system of claim 9 , further comprising: outputting the maintenance request to the vehicle control interface to not request servicing of the vehicle platform.

11. An automatic driving system according to any one of claims 6 to 10, a vehicle platform; The vehicle platform includes a base vehicle equipped with an integrated control manager, a brake system, a steering system, and a powertrain system; the vehicle platform includes a vehicle control interface for interfacing between the automated driving system and the vehicle platform; The vehicle platform includes: a first manual mode that is established when the vehicle platform is powered up and does not require an operator to be present within the vehicle platform; a second manual mode in which the operator is required to be within the vehicle platform and the vehicle platform is under the control of the operator; and an autonomous mode in which the vehicle platform is under control of the autonomous driving system.

12. A method for controlling a vehicle including a vehicle platform capable of mounting an autonomous driving system, comprising: The vehicle platform includes a base vehicle equipped with an integrated control manager, a brake system, a steering system, and a powertrain system; The vehicle platform further includes a vehicle control interface for interfacing between the automated driving system and the vehicle platform; The control method includes: placing the vehicle platform in a first manual mode when the vehicle platform is powered up, without requiring an operator to be within the vehicle platform; while in the first manual mode and the operator is within the vehicle platform, the vehicle platform transitioning from the first manual mode to a second manual mode; and when, in the second manual mode, the vehicle platform is ready for autonomous driving and an autonomous driving request is output from the autonomous driving system to the vehicle control interface, the vehicle platform transitions from the second manual mode to an autonomous mode; the second manual mode is a mode in which the operator is required to be within the vehicle platform and the vehicle platform is under the control of the operator; The method of controlling a vehicle, wherein the autonomous mode is a mode in which the vehicle platform is under the control of the autonomous driving system.

13. The automatic driving request can be switched between a request to set the automatic mode and a request to cancel the automatic mode, 13. The vehicle control method of claim 12, further comprising a step of transitioning the vehicle platform from the automatic mode to the second manual mode when the automatic driving request requesting cancellation of the automatic mode is output from the automatic driving system to the vehicle control interface.

14. the vehicle platform further having a sleep mode in which the vehicle control interface is shut down; 14. The vehicle control method according to claim 12 or 13, further comprising: a step of transitioning from the second manual mode to the sleep mode when a power mode request for transitioning the vehicle platform from the second manual mode to the sleep mode is output from the autonomous driving system to the vehicle control interface.

15. the vehicle platform further having a maintenance mode for servicing the vehicle platform; The control method further includes a step of transitioning the vehicle platform from the first manual mode to the maintenance mode when first to fourth conditions are satisfied, the first condition being a condition that a power mode status signal indicating that the vehicle platform is ignition-on is output from the vehicle control interface to the autonomous driving system, the second condition is a condition that a driving direction status signal indicating that the shift range is a P range is output from the vehicle control interface to the automated driving system; the third condition is a condition that an actual movement direction signal indicating that the vehicle platform is stopped is output from the vehicle control interface to the automated driving system; The vehicle control method according to any one of claims 12 to 14, wherein the fourth condition is a condition that a maintenance request requesting maintenance of the vehicle platform is output from the autonomous driving system to the vehicle control interface.

16. The maintenance request can be switched between requesting maintenance of the vehicle platform and not requesting maintenance of the vehicle platform; The method further includes the step of transitioning the vehicle platform from the maintenance mode to the first manual mode when fifth to eighth conditions are satisfied; the fifth condition is that the power mode status signal indicating that the vehicle platform is ignition-on is output from the vehicle control interface to the autonomous driving system; the sixth condition is a condition that the driving direction status signal indicating that the shift range is a P range is output from the vehicle control interface to the automated driving system; the seventh condition is that the actual movement direction signal indicating that the vehicle platform is stopped is output from the vehicle control interface to the automated driving system; 16. The vehicle control method according to claim 15, wherein the eighth condition is a condition that the maintenance request indicating no maintenance of the vehicle platform is output from the autonomous driving system to the vehicle control interface.

Images