US20210245654A1 - Vehicle - Google Patents

Vehicle Download PDF

Info

Publication number
US20210245654A1
US20210245654A1 US17/153,930 US202117153930A US2021245654A1 US 20210245654 A1 US20210245654 A1 US 20210245654A1 US 202117153930 A US202117153930 A US 202117153930A US 2021245654 A1 US2021245654 A1 US 2021245654A1
Authority
US
United States
Prior art keywords
mode
vehicle
operation mode
request
command
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US17/153,930
Other languages
English (en)
Inventor
Eisuke ANDO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toyota Motor Corp
Original Assignee
Toyota Motor Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toyota Motor Corp filed Critical Toyota Motor Corp
Assigned to TOYOTA JIDOSHA KABUSHIKI KAISHA reassignment TOYOTA JIDOSHA KABUSHIKI KAISHA ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ANDO, EISUKE
Publication of US20210245654A1 publication Critical patent/US20210245654A1/en
Priority to US17/659,541 priority Critical patent/US11560084B2/en
Priority to US18/090,559 priority patent/US11850997B2/en
Priority to US18/508,712 priority patent/US20240116431A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B60R16/037—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for occupant comfort, e.g. for automatic adjustment of appliances according to personal settings, e.g. seats, mirrors, steering wheel
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W60/00—Drive control systems specially adapted for autonomous road vehicles
    • B60W60/001—Planning or execution of driving tasks
    • B60W60/0023—Planning or execution of driving tasks in response to energy consumption
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60Q—ARRANGEMENT OF SIGNALLING OR LIGHTING DEVICES, THE MOUNTING OR SUPPORTING THEREOF OR CIRCUITS THEREFOR, FOR VEHICLES IN GENERAL
    • B60Q1/00—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor
    • B60Q1/02—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to illuminate the way ahead or to illuminate other areas of way or environments
    • B60Q1/04—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to illuminate the way ahead or to illuminate other areas of way or environments the devices being headlights
    • B60Q1/14—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to illuminate the way ahead or to illuminate other areas of way or environments the devices being headlights having dimming means
    • B60Q1/1415—Dimming circuits
    • B60Q1/1423—Automatic dimming circuits, i.e. switching between high beam and low beam due to change of ambient light or light level in road traffic
    • B60Q1/143—Automatic dimming circuits, i.e. switching between high beam and low beam due to change of ambient light or light level in road traffic combined with another condition, e.g. using vehicle recognition from camera images or activation of wipers
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W60/00—Drive control systems specially adapted for autonomous road vehicles
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W10/00—Conjoint control of vehicle sub-units of different type or different function
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60Q—ARRANGEMENT OF SIGNALLING OR LIGHTING DEVICES, THE MOUNTING OR SUPPORTING THEREOF OR CIRCUITS THEREFOR, FOR VEHICLES IN GENERAL
    • B60Q1/00—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor
    • B60Q1/0088—Details of electrical connections
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60Q—ARRANGEMENT OF SIGNALLING OR LIGHTING DEVICES, THE MOUNTING OR SUPPORTING THEREOF OR CIRCUITS THEREFOR, FOR VEHICLES IN GENERAL
    • B60Q1/00—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor
    • B60Q1/02—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to illuminate the way ahead or to illuminate other areas of way or environments
    • B60Q1/04—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to illuminate the way ahead or to illuminate other areas of way or environments the devices being headlights
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60Q—ARRANGEMENT OF SIGNALLING OR LIGHTING DEVICES, THE MOUNTING OR SUPPORTING THEREOF OR CIRCUITS THEREFOR, FOR VEHICLES IN GENERAL
    • B60Q1/00—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor
    • B60Q1/26—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to indicate the vehicle, or parts thereof, or to give signals, to other traffic
    • B60Q1/50—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to indicate the vehicle, or parts thereof, or to give signals, to other traffic for indicating other intentions or conditions, e.g. request for waiting or overtaking
    • B60Q1/52—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor the devices being primarily intended to indicate the vehicle, or parts thereof, or to give signals, to other traffic for indicating other intentions or conditions, e.g. request for waiting or overtaking for indicating emergencies
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60S—SERVICING, CLEANING, REPAIRING, SUPPORTING, LIFTING, OR MANOEUVRING OF VEHICLES, NOT OTHERWISE PROVIDED FOR
    • B60S1/00—Cleaning of vehicles
    • B60S1/02—Cleaning windscreens, windows or optical devices
    • B60S1/04—Wipers or the like, e.g. scrapers
    • B60S1/06—Wipers or the like, e.g. scrapers characterised by the drive
    • B60S1/08—Wipers or the like, e.g. scrapers characterised by the drive electrically driven
    • B60S1/0803—Intermittent control circuits
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60S—SERVICING, CLEANING, REPAIRING, SUPPORTING, LIFTING, OR MANOEUVRING OF VEHICLES, NOT OTHERWISE PROVIDED FOR
    • B60S1/00—Cleaning of vehicles
    • B60S1/02—Cleaning windscreens, windows or optical devices
    • B60S1/04—Wipers or the like, e.g. scrapers
    • B60S1/06—Wipers or the like, e.g. scrapers characterised by the drive
    • B60S1/08—Wipers or the like, e.g. scrapers characterised by the drive electrically driven
    • B60S1/0803—Intermittent control circuits
    • B60S1/0807—Intermittent control circuits using electronic control means, e.g. tubes, semiconductors
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W10/00—Conjoint control of vehicle sub-units of different type or different function
    • B60W10/04—Conjoint control of vehicle sub-units of different type or different function including control of propulsion units
    • B60W10/06—Conjoint control of vehicle sub-units of different type or different function including control of propulsion units including control of combustion engines
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W10/00—Conjoint control of vehicle sub-units of different type or different function
    • B60W10/18—Conjoint control of vehicle sub-units of different type or different function including control of braking systems
    • B60W10/184—Conjoint control of vehicle sub-units of different type or different function including control of braking systems with wheel brakes
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
    • B60W30/14—Adaptive cruise control
    • B60W30/16—Control of distance between vehicles, e.g. keeping a distance to preceding vehicle
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
    • B60W40/08—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
    • B60W40/08—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
    • B60W40/09—Driving style or behaviour
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
    • B60W40/10—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to vehicle motion
    • B60W40/105—Speed
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
    • G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
    • G05D1/0005—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots with arrangements to save energy
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
    • G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
    • G05D1/02—Control of position or course in two dimensions
    • G05D1/021—Control of position or course in two dimensions specially adapted to land vehicles
    • G05D1/0212—Control of position or course in two dimensions specially adapted to land vehicles with means for defining a desired trajectory
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W2050/0001—Details of the control system
    • B60W2050/0002—Automatic control, details of type of controller or control system architecture
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2540/00—Input parameters relating to occupants
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
    • Y02T10/00—Road transport of goods or passengers
    • Y02T10/60—Other road transportation technologies with climate change mitigation effect
    • Y02T10/70—Energy storage systems for electromobility, e.g. batteries

Definitions

  • the present disclosure relates to a vehicle capable of autonomous driving.
  • Japanese Patent Laying-Open No. 2018-132015 discloses a vehicle including a motive power system that manages motive power of the vehicle in a centralized manner, a power supply system that manages supply of electric power to various vehicle-mounted devices in a centralized manner, and an autonomous driving system that carries out autonomous driving control of the vehicle in a centralized manner.
  • a vehicle While autonomous driving is being carried out, a vehicle is controlled in accordance with an instruction from an autonomous driving system. While autonomous driving is being carried out, various devices such as a headlight, a hazard light, a front windshield wiper, and a rear windshield wiper can also be controlled in accordance with an instruction from the autonomous driving system.
  • Determination as to operations by the various devices may be different among users. Therefore, during autonomous driving, determination by the autonomous driving system as to operations by the various devices and determination as to operations by the various devices by the user who is in a vehicle may be different from each other. When the various devices are controlled in accordance with determination by the autonomous driving system in such a case, the user may feel uncomfortable.
  • the present disclosure was made to solve the problem above, and an object of the present disclosure is to suppress uncomfortable feeling given to a user during autonomous driving due to a difference in determination as to operations by various devices between an autonomous driving system and the user.
  • a vehicle according to the present disclosure is a vehicle on which an autonomous driving system is mountable, and the vehicle includes a vehicle platform that controls the vehicle in accordance with an instruction from the autonomous driving system and a vehicle control interface that interfaces between the vehicle platform and the autonomous driving system.
  • the vehicle platform includes a headlight system, a hazard light system, a front windshield wiper system, and a rear windshield wiper system.
  • the vehicle platform sets an operation mode of each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system in accordance with an operation mode request for each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system received from the autonomous driving system and/or an operation by a user onto an operation apparatus provided for each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system.
  • the vehicle platform sets the operation mode with the operation by the user being prioritized over the operation mode request.
  • an operation by a user is prioritized over an operation mode request from the autonomous driving system.
  • the user can set the operation mode of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system. Therefore, uncomfortable feeling given to the user during autonomous driving can be suppressed.
  • the vehicle platform sets the operation mode of the headlight system in accordance with the operation mode request.
  • the vehicle platform when the operation mode of the headlight system has been set to a mode other than the first prescribed mode by the operation by the user, the vehicle platform does not set the operation mode of the headlight system in accordance with the operation mode request.
  • the first prescribed mode includes an OFF mode and an AUTO mode.
  • the OFF mode is a mode in which a headlight is turned off.
  • the AUTO mode is a mode in which the operation mode of the headlight system is automatically set by the vehicle platform.
  • an operation mode request from the autonomous driving system is accepted only when the operation mode of the headlight system has been set to the first prescribed mode (the OFF mode or the AUTO mode) by the operation by the user.
  • the operation mode of the headlight system has been set to the first prescribed mode (the OFF mode or the AUTO mode) by the operation by the user.
  • the user is estimated to have left setting of the operation mode of the headlight system to the autonomous driving system or the vehicle. Therefore, by accepting the operation mode request from the autonomous driving system only in such a case, uncomfortable feeling given to the user can be suppressed.
  • the vehicle platform sets the operation mode of the front windshield wiper system in accordance with the operation mode request.
  • the vehicle platform when the operation mode of the front windshield wiper system has been set to a mode other than the second prescribed mode by the operation by the user, the vehicle platform does not set the operation mode of the front windshield wiper system in accordance with the operation mode request.
  • the second prescribed mode includes an OFF mode and an Auto mode.
  • the OFF mode is a mode in which a front windshield wiper is stopped.
  • the Auto mode is a mode in which the operation mode of the front windshield wiper system is automatically set by the vehicle platform.
  • the operation mode request from the autonomous driving system is accepted only when the operation mode of the front windshield wiper system has been set to the second prescribed mode (the OFF mode or the Auto mode) by the operation by the user.
  • the user has set the operation mode of the front windshield wiper system to the OFF mode or the Auto mode, the user is estimated to have left setting of the operation mode of the front windshield wiper system to the autonomous driving system or the vehicle. Therefore, by accepting the operation mode request from the autonomous driving system only in such a case, uncomfortable feeling given to the user can be suppressed.
  • the front windshield wiper system includes as the operation mode, an intermittent operation mode in which a front windshield wiper is intermittently operated.
  • the vehicle platform sets an operation interval in accordance with an operation interval request that indicates the operation interval of the front windshield wiper in the intermittent operation mode received from the autonomous driving system and/or the operation by the user onto the operation apparatus.
  • the vehicle platform sets the operation interval with the operation by the user being prioritized over the operation interval request.
  • the operation by the user is prioritized over the operation interval request from the autonomous driving system.
  • the user can set the operation interval of the front windshield wiper in the intermittent operation mode. Therefore, uncomfortable feeling given to the user during autonomous driving can be suppressed.
  • FIG. 1 is a diagram showing overview of a MaaS system in which a vehicle according to an embodiment of the present disclosure is used.
  • FIG. 2 is a diagram showing a detailed configuration of a vehicle control interface, a VP, and an ADK.
  • FIG. 3 is a diagram for illustrating a light operation mode request.
  • FIG. 4 is a flowchart showing a procedure of processing for setting an operation mode of a headlight.
  • FIG. 5 is a diagram for illustrating a hazard light operation mode request.
  • FIG. 6 is a flowchart showing a procedure of processing for setting an operation mode of a hazard light.
  • FIG. 7 is a diagram for illustrating a front windshield wiper operation mode request.
  • FIG. 8 is a flowchart showing a procedure of processing for setting an operation mode of a front windshield wiper.
  • FIG. 9 is a diagram for illustrating a front windshield wiper operation interval request in an intermittent operation mode.
  • FIG. 10 is a diagram for illustrating a rear windshield wiper operation mode request.
  • FIG. 11 is a flowchart showing a procedure of processing for setting an operation mode of a rear windshield wiper.
  • FIG. 12 is a diagram of an overall configuration of MaaS.
  • FIG. 13 is a diagram of a system configuration of a MaaS vehicle.
  • FIG. 14 is a diagram showing a typical flow in an autonomous driving system.
  • FIG. 15 is a diagram showing an exemplary timing chart of an API relating to stop and start of the MaaS vehicle.
  • FIG. 16 is a diagram showing an exemplary timing chart of the API relating to shift change of the MaaS vehicle.
  • FIG. 17 is a diagram showing an exemplary timing chart of the API relating to wheel lock of the MaaS vehicle.
  • FIG. 18 is a diagram showing a limit value of variation in tire turning angle.
  • FIG. 19 is a diagram illustrating intervention by an accelerator pedal.
  • FIG. 20 is a diagram illustrating intervention by a brake pedal.
  • FIG. 21 is a diagram of an overall configuration of MaaS.
  • FIG. 22 is a diagram of a system configuration of a vehicle.
  • FIG. 23 is a diagram showing a configuration of supply of power of the vehicle.
  • FIG. 24 is a diagram illustrating strategies until the vehicle is safely brought to a standstill at the time of occurrence of a failure.
  • FIG. 25 is a diagram showing arrangement of representative functions of the vehicle.
  • FIG. 1 is a diagram showing overview of a mobility as a service (MaaS) system in which a vehicle according to an embodiment of the present disclosure is used.
  • MoaS mobility as a service
  • this MaaS system includes a vehicle 10 , a data server 500 , a mobility service platform (which is also referred to as “MSPF” below) 600 , and autonomous driving related mobility services 700 .
  • MSPF mobility service platform
  • Vehicle 10 includes a vehicle main body 100 and an autonomous driving kit (which is also referred to as “ADK” below) 200 .
  • Vehicle main body 100 includes a vehicle control interface 110 , a vehicle platform (which is also referred to as “VP” below) 120 , and a data communication module (DCM) 190 .
  • ADK autonomous driving kit
  • VP vehicle platform
  • DCM data communication module
  • Vehicle 10 can carry out autonomous driving in accordance with commands from ADK 200 attached to vehicle main body 100 .
  • FIG. 1 shows vehicle main body 100 and ADK 200 at positions distant from each other, ADK 200 is actually attached to a rooftop or the like of vehicle main body 100 .
  • ADK 200 can also be removed from vehicle main body 100 .
  • vehicle main body 100 can travel by manual driving by a user.
  • VP 120 carries out travel control (travel control in accordance with an operation by a user) in a manual mode.
  • Vehicle control interface 110 can communicate with ADK 200 over a controller area network (CAN) or Ethernet®. Vehicle control interface 110 receives various commands from ADK 200 by executing a prescribed application program interface (API) defined for each communicated signal. Vehicle control interface 110 provides a state of vehicle main body 100 to ADK 200 by executing a prescribed API defined for each communicated signal.
  • API application program interface
  • vehicle control interface 110 When vehicle control interface 110 receives a command from ADK 200 , it outputs a control command corresponding to the command to VP 120 . Vehicle control interface 110 obtains various types of information on vehicle main body 100 from VP 120 and outputs the state of vehicle main body 100 to ADK 200 . A configuration of vehicle control interface 110 will be described in detail later.
  • VP 120 includes various systems and various sensors for controlling vehicle main body 100 .
  • VP 120 carries out various types of vehicle control in accordance with a command given from ADK 200 through vehicle control interface 110 .
  • ADK 200 autonomous driving of vehicle 10 is carried out.
  • a configuration of VP 120 will also be described in detail later.
  • ADK 200 includes an autonomous driving system (which is also referred to as “ADS” below) for autonomous driving of vehicle 10 .
  • ADK 200 creates, for example, a driving plan of vehicle 10 and outputs various commands for traveling vehicle 10 in accordance with the created driving plan to vehicle control interface 110 in accordance with the API defined for each command.
  • ADK 200 receives various signals indicating states of vehicle main body 100 from vehicle control interface 110 in accordance with the API defined for each signal and has the received vehicle state reflected on creation of the driving plan.
  • a configuration of ADK 200 (ADS) will also be described later.
  • DCM 190 includes a communication interface for vehicle main body 100 to wirelessly communicate with data server 500 .
  • DCM 190 outputs various types of vehicle information such as a speed, a position, or an autonomous driving state to data server 500 .
  • DCM 190 receives from autonomous driving related mobility services 700 through MSPF 600 and data server 500 , for example, various types of data for management of travel of an autonomous driving vehicle including vehicle 10 by mobility services 700 .
  • MSPF 600 is an integrated platform to which various mobility services are connected.
  • various mobility services for example, various mobility services provided by a ride-share company, a car-sharing company, an insurance company, a rent-a-car company, and a taxi company
  • Various mobility services including mobility services 700 can use various functions provided by MSPF 600 by using APIs published on MSPF 600 , depending on service contents.
  • Autonomous driving related mobility services 700 provide mobility services using an autonomous driving vehicle including vehicle 10 .
  • Mobility services 700 can obtain, for example, operation control data of vehicle 10 that communicates with data server 500 and/or information stored in data server 500 from MSPF 600 , by using the APIs published on MSPF 600 .
  • Mobility services 700 transmit, for example, data for managing an autonomous driving vehicle including vehicle 10 to MSPF 600 , by using the API.
  • MSPF 600 publishes APIs for using various types of data on vehicle states and vehicle control necessary for development of the ADS.
  • An ADS provider can use as the APIs, the data on the vehicle states and vehicle control necessary for development of the ADS stored in data server 500 .
  • FIG. 2 is a diagram showing a detailed configuration of vehicle control interface 110 , VP 120 , and ADK 200 .
  • ADK 200 includes a compute assembly 210 , a human machine interface (HMI) 230 , sensors for perception 260 , sensors for pose 270 , and a sensor cleaning 290 .
  • HMI human machine interface
  • compute assembly 210 obtains information on an environment around the vehicle and a pose, a behavior, and a position of vehicle 10 with various sensors which will be described later.
  • Compute assembly 210 obtains a state of vehicle 10 from VP 120 through vehicle control interface 110 and sets a next operation (acceleration, deceleration, or turning) of vehicle 10 .
  • Compute assembly 210 outputs various instructions for realizing a set next operation of vehicle 10 to vehicle control interface 110 .
  • HMI 230 accepts an input operation from a user for vehicle 10 .
  • HMI 230 can accept, for example, an input by a touch operation onto a display screen and/or an audio input.
  • HMI 230 presents information to a user of vehicle 10 by showing information on the display screen.
  • HMI 230 may present information to the user of vehicle 10 by voice and sound in addition to or instead of representation of information on the display screen.
  • HMI 230 provides information to the user and accepts an input operation, for example, during autonomous driving, during manual driving by a user, or at the time of transition between autonomous driving and manual driving.
  • Sensors for perception 260 include sensors that perceive an environment around the vehicle, and are implemented, for example, by at least any of laser imaging detection and ranging (LIDAR), a millimeter-wave radar, and a camera.
  • LIDAR laser imaging detection and ranging
  • millimeter-wave radar a millimeter-wave radar
  • the LIDAR measures a distance based on a time period from emission of pulsed laser beams (infrared rays) until return of the emitted beams reflected by an object.
  • the millimeter-wave radar measures a distance and/or a direction to an object by emitting radio waves short in wavelength to the object and detecting radio waves that are reflected and return from the object.
  • the camera is arranged, for example, on a rear side of a room mirror in a compartment and shoots an image of the front of vehicle 10 . As a result of image processing onto images shot by the camera, another vehicle, an obstacle, or a human in front of vehicle 10 can be recognized.
  • Information obtained by sensors for perception 260 is output to compute assembly 210 .
  • Sensors for pose 270 detect a pose, a behavior, or a position of vehicle 10 .
  • Sensors for pose 270 include, for example, an inertial measurement unit (IMU) and a global positioning system (GPS).
  • IMU inertial measurement unit
  • GPS global positioning system
  • the IMU detects, for example, an acceleration in a front-rear direction, a lateral direction, and a vertical direction of vehicle 10 and an angular velocity in a roll direction, a pitch direction, and a yaw direction of vehicle 10 .
  • the GPS detects a position of vehicle 10 based on information received from a plurality of GPS satellites that orbit the Earth. Information obtained by sensors for pose 270 is output to compute assembly 210 .
  • Sensor cleaning 290 can remove soiling attached to various sensors. Sensor cleaning 290 removes soiling on a lens of the camera or a portion from which laser beams and/or radio waves are emitted, for example, with a cleaning solution and/or a wiper.
  • Vehicle control interface 110 includes a vehicle control interface box (VCIB) 111 A and a VCIB 111 B.
  • VCIBs 111 A and 111 B includes an electronic control unit (ECU), and specifically contains a central processing unit (CPU) and a memory (a read only memory (ROM) and a random access memory (RAM)) (neither of which is shown).
  • ECU electronice control unit
  • CPU central processing unit
  • ROM read only memory
  • RAM random access memory
  • VCIB 111 A and VCIB 111 B are basically equivalent in function to each other.
  • VCIB 111 A and VCIB 111 B are partially different from each other in a plurality of systems connected thereto that make up VP 120 .
  • VCIBs 111 A and 111 B are communicatively connected to compute assembly 210 of ADK 200 over the CAN or the like.
  • VCIB 111 A and VCIB 111 B are communicatively connected to each other.
  • Each of VCIBs 111 A and 111 B relays various instructions from ADK 200 and provides them as control commands to VP 120 . More specifically, each of VCIBs 111 A and 111 B executes a program stored in a memory, converts various instructions provided from ADK 200 into control commands to be used for control of each system of VP 120 , and provides the converted control commands to a destination system. Each of VCIBs 111 A and 111 B processes or relays various types of vehicle information output from VP 120 and provides the vehicle information as a vehicle state to ADK 200 .
  • VCIBs 111 A and 111 B are configured to be equivalent in function to each other so that control systems between ADK 200 and VP 120 are redundant. Therefore, when some kind of failure occurs in a part of the system, the function (turning or stopping) of VP 120 can be maintained by switching between the control systems as appropriate or disconnecting a control system where failure has occurred.
  • VP 120 includes brake systems 121 A and 121 B, steering systems 122 A and 122 B, an electric parking brake (EPB) system 123 A, a P-Lock system 123 B, a propulsion system 124 , a pre-crash safety (PCS) system 125 , and a body system 126 .
  • EPB electric parking brake
  • PCS pre-crash safety
  • Brake system 121 B, steering system 122 A, EPB system 123 A, P-Lock system 123 B, propulsion system 124 , and body system 126 of the plurality of systems of VP 120 are communicatively connected to VCIB 111 A through a communication bus.
  • Brake system 121 A, steering system 122 B, and P-Lock system 123 B of the plurality of systems of VP 120 are communicatively connected to VCIB 111 B through a communication bus.
  • Brake systems 121 A and 121 B can control a plurality of braking apparatuses (not shown) provided in wheels of vehicle 10 .
  • the braking apparatus includes, for example, a disc brake system that is operated with a hydraulic pressure regulated by an actuator.
  • Brake system 121 A and brake system 121 B may be equivalent in function to each other.
  • any one of brake systems 121 A and 121 B may be able to independently control braking force of each wheel and the other thereof may be able to control braking force such that equal braking force is generated in the wheels.
  • a wheel speed sensor 127 is connected to brake system 121 B.
  • Wheel speed sensor 127 is provided in each wheel of vehicle 10 .
  • Wheel speed sensor 127 detects a rotation speed and a rotation direction of a wheel.
  • Wheel speed sensor 127 outputs the detected rotation speed and rotation direction of the wheel to brake system 121 B.
  • wheel speed sensor 127 provides pulses different between during rotation in a direction of forward travel of vehicle 10 and during rotation in a direction of rearward travel of vehicle 10 .
  • Brake system 121 B fixes or confirms the rotation direction of each wheel based on the pulses from wheel speed sensor 127 .
  • brake system 121 B provides information indicating the fixed rotation direction of each wheel to VCIB 111 A.
  • Brake system 121 B determines whether or not vehicle 10 has come to a standstill based on the fixed rotation direction of each wheel. Specifically, when the speed of all wheels is set to zero and when a certain time period has elapsed since the speed of all wheels was set to 0, brake system 121 B determines that vehicle 10 has come to a standstill. When brake system 121 B determines that vehicle 10 has come to a standstill, the brake system provides information indicating “Standstill” to VCIB 111 A.
  • Each of brake systems 121 A and 121 B receives a command from ADK 200 as a control command through vehicle control interface 110 and generates a braking instruction to the braking apparatus in accordance with the control command.
  • brake systems 121 A and 121 B control the braking apparatus based on a braking instruction generated in one of brake systems 121 A and 121 B, and when a failure occurs in one of the brake systems, the braking apparatus is controlled based on a braking instruction generated in the other brake system.
  • Steering systems 122 A and 122 B can control a steering angle of a steering wheel of vehicle 10 with a steering apparatus (not shown).
  • the steering apparatus includes, for example, rack-and-pinion electric power steering (EPS) that allows adjustment of a steering angle by an actuator.
  • EPS rack-and-pinion electric power steering
  • Steering systems 122 A and 122 B are equivalent in function to each other.
  • Each of steering systems 122 A and 122 B receives a command from ADK 200 as a control command through vehicle control interface 110 and generates a steering instruction to the steering apparatus in accordance with the control command.
  • steering systems 122 A and 122 B control the steering apparatus based on the steering instruction generated in one of steering systems 122 A and 122 B, and when a failure occurs in one of the steering systems, the steering apparatus is controlled based on a steering instruction generated in the other steering system.
  • a pinion angle sensor 128 A is connected to steering system 122 A.
  • a pinion angle sensor 128 B is connected to steering system 122 B.
  • Each of pinion angle sensors 128 A and 128 B detects an angle of rotation (a pinion angle) of a pinion gear coupled to a rotation shaft of the actuator.
  • Pinion angle sensors 128 A and 128 B output detected pinion angles to steering systems 122 A and 122 B, respectively.
  • EPB system 123 A can control an EPB (not shown) provided in at least any of wheels.
  • the EPB is provided separately from the braking apparatus, and fixes a wheel by an operation of an actuator.
  • the EPB for example, activates a drum brake for a parking brake provided in at least one of wheels of vehicle 10 to fix the wheel.
  • the EPB activates a braking apparatus to fix a wheel, for example, with an actuator capable of regulating a hydraulic pressure to be supplied to the braking apparatus separately from brake systems 121 A and 121 B.
  • EPB system 123 A receives a command from ADK 200 as a control command through vehicle control interface 110 and controls the EPB in accordance with the control command.
  • P-Lock system 123 B can control a P-Lock apparatus (not shown) provided in a transmission of vehicle 10 .
  • the P-Lock apparatus fixes rotation of an output shaft of the transmission by fitting a protrusion provided at a tip end of a parking lock pawl into a tooth of a gear (locking gear) provided as being coupled to a rotational element in the transmission.
  • a position of the parking lock pawl is adjusted by an actuator.
  • P-Lock system 123 B receives a command from ADK 200 as a control command through vehicle control interface 110 and controls the P-Lock apparatus in accordance with the control command.
  • Propulsion system 124 can switch a shift range with the use of a shift apparatus (not shown) and can control driving force of vehicle 10 in a direction of travel that is generated from a drive source (not shown).
  • the shift apparatus can select any of a plurality of shift ranges.
  • the drive source includes, for example, a motor generator and/or an engine.
  • Propulsion system 124 receives a command from ADK 200 as a control command through vehicle control interface 110 and controls the shift apparatus and the drive source in accordance with the control command.
  • PCS system 125 is communicatively connected to brake system 121 B.
  • PCS system 125 carries out control to avoid collision of vehicle 10 or to mitigate damage by using a result of detection by a camera/radar 129 .
  • PCS system 125 detects an object in front and determines whether or not vehicle 10 may collide with the object based on a distance to the object.
  • PCS system 125 determines that there is possibility of collision with the object, it outputs a braking instruction to brake system 121 B so as to increase braking force.
  • Body system 126 controls, for example, various devices in accordance with a state or an environment of travel of vehicle 10 .
  • the various devices include, for example, a direction indicator, a headlight, a hazard light, a horn, a front windshield wiper, and a rear windshield wiper.
  • Body system 126 receives a command from ADK 200 as a control command through vehicle control interface 110 and controls the various devices in accordance with the control command.
  • the various devices are each separately provided with an operation apparatus manually operable by a user (a driver).
  • Determination as to operations by the various devices may be different among users. Therefore, during autonomous driving, determination by ADK 200 as to operations by the various devices may be different from determination as to operations by the various devices by the user who is in vehicle 10 .
  • the various devices are controlled in accordance with determination by ADK 200 in such a case, the user may feel uncomfortable.
  • the operation by the user is prioritized over an instruction (a command) from ADK 200 .
  • an instruction a command
  • the headlight includes a “TAIL mode,” a “HEAD mode,” an “AUTO mode,” a “HI mode,” and an “OFF mode” as operation modes.
  • the “TAIL mode” refers to a mode in which a parking light (a sidelight) is turned on.
  • the “HEAD mode” refers to a mode in which the headlight is turned on and set to low beam.
  • the “AUTO mode” refers to a mode in which VP 120 (body system 126 in the present embodiment) automatically sets the operation mode based on brightness around vehicle 10 .
  • the “HI mode” refers to a mode in which the headlight is turned on and set to high beam.
  • the “OFF mode” refers to a mode in which the headlight is turned off.
  • the user can set the operation mode of the headlight by performing an operation onto the operation apparatus (for example, a light switch).
  • the operation apparatus provides to VP 120 (body system 126 ) every prescribed control cycle, a signal (which is also referred to as “a first driver input (Headlight_Driver_Input) below) indicating the operation mode (which is also referred to as a “first driver setting mode” below) of the headlight set by the operation by the user.
  • VP 120 recognizes the first driver setting mode based on the first driver input received from the operation apparatus.
  • VP 120 accepts a command from ADK 200 .
  • ADK 200 provides a light operation mode request (Headlight_Mode_Command) indicating an illumination state of the headlight to vehicle control interface 110 every prescribed control cycle.
  • Vehicle control interface 110 that has received the light operation mode request generates a control command corresponding to the light operation mode request and provides the generated control command to VP 120 (body system 126 ).
  • Headlight_Mode_Command is a command to control the headlight mode of the vehicle platform (VP 120 ).
  • VP 120 sets the operation mode of the headlight in accordance with the control command.
  • the first driver setting mode indicates neither the “OFF mode” nor the “AUTO mode,” that is, when the first driver setting mode indicates the “TAIL mode,” the “HEAD mode,” or the “HI mode”
  • VP 120 does not accept a command from ADK 200 .
  • a value corresponding to the operation mode requested by ADK 200 is set in the light operation mode request provided from ADK 200 in accordance with contents in FIG. 3 which will be described below.
  • FIG. 3 is a diagram for illustrating a light operation mode request.
  • FIG. 3 shows relation between a light operation mode request and a corresponding value. Specifically, a value is shown in a field “value” and a light operation mode request is shown in a field “Description”. Remarks are given in a field “remarks”.
  • a value 0 indicates that “there is no request (No request).” Though detailed description will be provided later, the value 0 is set when a current operation mode is maintained.
  • a value 1 indicates a “TAIL mode request.”
  • a value 2 indicates a “HEAD mode request.”
  • a value 3 indicates an “AUTO mode request.”
  • a value 4 indicates a “HI mode request.”
  • a value 5 indicates an “OFF mode request.” Though values 6 and 7 are not used in the present embodiment, they can also be set and used as appropriate.
  • vehicle control interface 110 When vehicle control interface 110 receives the light operation mode request from ADK 200 , it generates a control command corresponding to a value indicated in the light operation mode request and provides the control command to VP 120 .
  • vehicle control interface 110 When the light operation mode request indicates the value 0, vehicle control interface 110 generates a control command indicating “No request” and provides the control command to VP 120 .
  • vehicle control interface 110 When the light operation mode request indicates the value 1, vehicle control interface 110 generates a control command indicating the “TAIL mode request” and provides the control command to VP 120 .
  • vehicle control interface 110 When the light operation mode request indicates the value 2, vehicle control interface 110 generates a control command indicating the “HEAD mode request” and provides the control command to VP 120 .
  • vehicle control interface 110 When the light operation mode request indicates the value 3, vehicle control interface 110 generates a control command indicating the “AUTO mode request” and provides the control command to VP 120 . When the light operation mode request indicates the value 4, vehicle control interface 110 generates a control command indicating the “HI mode request” and provides the control command to VP 120 . When the light operation mode request indicates the value 5, vehicle control interface 110 generates a control command indicating the “OFF mode request” and provides the control command to VP 120 .
  • VP 120 accepts a control command.
  • the first driver setting mode does not indicate the “OFF mode” or the “AUTO mode,” that is, when the first driver setting mode indicates the “TAIL mode,” the “HEAD mode,” or the “HI mode,” VP 120 does not accept the control command.
  • VP 120 sets the operation mode of the headlight to the “TAIL mode” when it receives the control command indicating the “TAIL mode request,” VP 120 sets the operation mode of the headlight to the “HEAD mode” when it receives the control command indicating the “HEAD mode request,” VP 120 sets the operation mode of the headlight to the “AUTO mode” when it receives the control command indicating the “AUTO mode request,” VP 120 sets the operation mode of the headlight to the “HI mode” when it receives a control command indicating the “HI mode request,” and VP 120 sets the operation mode of the headlight to the “OFF mode” when it receives a control command indicating the “OFF mode request.”
  • VP 120 When VP 120 receives the control command indicating “No request” while the first driver setting mode indicates the “OFF mode” or the “AUTO mode,” it maintains the current operation mode.
  • VP 120 sets the operation mode of the headlight not in accordance with the control command but in accordance with the changed first driver setting mode. In other words, VP 120 prioritizes the operation by the user (a first driver input) over the command from ADK 200 .
  • FIG. 4 is a flowchart showing a procedure of processing for setting an operation mode of the headlight. Processing in the flowchart in FIG. 4 is repeatedly performed in VP 120 every prescribed control cycle. Though an example in which processing in the flowchart in FIG. 4 and FIGS. 6, 8, and 11 which will be described later is performed by software processing by VP 120 is described, a part or the entirety thereof may be implemented by hardware (electric circuitry) made in VP 120 .
  • VP 120 determines whether or not the first driver setting mode indicates the “OFF mode” or the “AUTO mode” (a step 1 , the step being abbreviated as “S” below). When the first driver setting mode indicates the “TAIL mode,” the “HEAD mode,” or the “HI mode” (NO in S 1 ), VP 120 maintains the first driver setting mode as the operation mode of the headlight and the process returns. In other words, VP 120 does not accept a command from ADK 200 .
  • VP 120 determines whether or not the user has performed an operation onto the operation apparatus (S 2 ). In other words, VP 120 determines whether or not the first driver setting mode has been changed.
  • VP 120 changes the operation mode of the headlight to the first driver setting mode indicated by the operation by the user (S 3 ).
  • VP 120 determines whether or not the light operation mode request from ADK 200 indicates “No request” (S 4 ). VP 120 determines contents of the light operation mode request based on a control command from vehicle control interface 110 .
  • VP 120 maintains the current operation mode (S 5 ).
  • VP 120 changes the operation mode of the headlight to the operation mode indicated in the light operation mode request (S 6 ).
  • VP 120 sets the operation mode of the headlight in accordance with the light operation mode request from ADK 200 .
  • ADK 200 By accepting the light operation mode request from ADK 200 only when the user is estimated to have left setting of the operation mode of the headlight system to ADK 200 or vehicle main body 100 , uncomfortable feeling given to the user during autonomous driving can be suppressed.
  • VP 120 prioritizes the operation by the user over the light operation mode request from ADK 200 . By prioritizing the operation by the user over determination by ADK 200 during autonomous driving, uncomfortable feeling given to the user during autonomous driving can be suppressed.
  • the hazard light includes an “OFF mode” and an “ON mode” as operation modes.
  • the “OFF mode” refers to a mode in which the hazard light is turned off.
  • the “ON mode” refers to a mode in which the hazard light flashes.
  • the user can set the operation mode of the hazard light by performing an operation onto the operation apparatus (for example, a hazard light switch).
  • the operation apparatus provides to VP 120 (body system 126 ) every prescribed control cycle, a signal (which is also referred to as a “second driver input” below) indicating the operation mode (which is also referred to as a “second driver setting mode” below) of the hazard light set by the operation by the user.
  • VP 120 recognizes the second driver setting mode based on the second driver input received from the operation apparatus.
  • VP 120 accepts a command from ADK 200 .
  • ADK 200 provides a hazard light operation mode request (Hazardlight_Mode_Command) indicating an illumination state of the hazard light to vehicle control interface 110 every prescribed control cycle.
  • Vehicle control interface 110 that has received the hazard light operation mode request generates a control command corresponding to the hazard light operation mode request and provides the generated control command to VP 120 (body system 126 ).
  • VP 120 sets the operation mode of the hazard light in accordance with the control command. That is, Hazardlight_Mode_Command is a command to control the hazardlight mode of the vehicle platform (VP 120 ).
  • a value corresponding to the operation mode requested by ADK 200 is set in the hazard light operation mode request provided from ADK 200 in accordance with contents in FIG. 5 which will be described below.
  • FIG. 5 is a diagram for illustrating a hazard light operation mode request.
  • FIG. 5 shows relation between a hazard light operation mode request and a corresponding value. Specifically, a value is shown in a field “value” and a hazard light operation mode request is shown in a field “Description”. Remarks are given in a field “remarks”.
  • a value 0 indicates a command for the hazard light “OFF”, that is, turn-off of the hazard light.
  • a value 1 indicates a command for the hazard light “ON”, that is, flashing of the hazard light.
  • vehicle control interface 110 When vehicle control interface 110 receives the hazard light operation mode request from ADK 200 , it generates a control command corresponding to a value indicated in the hazard light operation mode request and provides the control command to VP 120 . When the hazard light operation mode request indicates the value 0, vehicle control interface 110 generates a control command indicating “OFF” and provides the control command to VP 120 . When the hazard light operation mode request indicates the value 1, vehicle control interface 110 generates a control command indicating “ON” and provides the control command to VP 120 .
  • VP 120 When VP 120 receives the control command indicating “OFF”, it sets the operation mode of the hazard light to the “OFF mode,” and when VP 120 receives the control command indicating “ON”, it sets the operation mode of the hazard light to the “ON mode.”
  • VP 120 sets the operation mode of the hazard light not in accordance with the control command but in accordance with the changed second driver setting mode. In other words, VP 120 prioritizes the operation by the user (a second driver input) over the command from ADK 200 .
  • FIG. 6 is a flowchart showing a procedure of processing for setting an operation mode of the hazard light. Processing in the flowchart in FIG. 6 is repeatedly performed in VP 120 every prescribed control cycle.
  • VP 120 determines whether or not the user has performed an operation onto the operation apparatus (S 11 ). In other words, VP 120 determines whether or not the second driver setting mode has been changed.
  • VP 120 changes the operation mode of the hazard light to the second driver setting mode indicated by the operation by the user (S 12 ).
  • VP 120 determines whether or not the hazard light operation mode request from ADK 200 indicates “ON” (S 13 ). VP 120 determines contents of the hazard light operation mode request based on a control command from vehicle control interface 110 .
  • VP 120 sets the operation mode of the hazard light to the ON mode and has the hazard light flash (S 14 ).
  • the hazard light operation mode request indicates “OFF” (NO in S 13 )
  • VP 120 sets the operation mode of the hazard light to the OFF mode and turns off the hazard light (S 15 ).
  • VP 120 changes the operation mode of the hazard light in accordance with the hazard light operation mode request from ADK 200 .
  • VP 120 prioritizes the operation by the user over the hazard light operation mode request from ADK 200 .
  • the front windshield wiper includes an “OFF mode,” a “Lo mode,” a “Hi mode,” an “intermittent operation mode,” an “Auto mode,” and a “Mist mode” as operation modes.
  • the “OFF mode” refers to a mode in which the front windshield wiper is stopped.
  • the “Lo mode” refers to a mode in which the front windshield wiper is operated at a first speed.
  • the “Hi mode” refers to a mode in which the front windshield wiper is operated at a second speed higher than the first speed.
  • the “intermittent operation mode” refers to a mode in which the front windshield wiper is intermittently operated. Though details will be described later, an operation interval of the front windshield wiper is set in the intermittent operation mode.
  • the “Auto mode” refers to a mode in which VP 120 automatically selects the Lo mode or the Hi mode based on a result of detection by a raindrop sensor provided in a windshield.
  • the “Mist mode” refers to a mode in which the front windshield wiper is activated only a prescribed number of times (for example, once).
  • the user can set the operation mode of the front windshield wiper by performing an operation onto the operation apparatus (for example, a windshield wiper switch).
  • the operation apparatus provides to VP 120 (body system 126 ) every prescribed control cycle, a signal (which is also referred to as a “third driver input (Windshieldwiper_Front_Driver_input)” below) indicating an operation mode (which is also referred to as a “third driver setting mode” below) of the front windshield wiper set by the operation by the user.
  • VP 120 recognizes the third driver setting mode based on the third driver input.
  • VP 120 accepts a command from ADK 200 .
  • ADK 200 provides a front windshield wiper operation mode request (Windshieldwiper_Mode_Front_Command) that indicates an operation state of the front windshield wiper to vehicle control interface 110 every prescribed control cycle.
  • Vehicle control interface 110 that has received the front windshield wiper operation mode request generates a control command corresponding to the front windshield wiper operation mode request and provides the generated control command to VP 120 (body system 126 ). That is, Windshieldwiper_Mode_Front_Command is a command to control the front windshield wiper of the vehicle platform (VP 120 ).
  • VP 120 sets the operation mode of the front windshield wiper in accordance with the control command.
  • VP 120 does not accept a command from ADK 200 .
  • a value corresponding to the operation mode requested by ADK 200 is set in the front windshield wiper operation mode request provided from ADK 200 in accordance with contents in FIG. 7 which will be described below.
  • FIG. 7 is a diagram for illustrating a front windshield wiper operation mode request.
  • FIG. 7 shows relation between a front windshield wiper operation mode request and a corresponding value. Specifically, a value is shown in a field “value” and a front windshield wiper operation mode request is shown in a field “Description”. Remarks are given in a field “remarks”.
  • a value 0 indicates a “stop request (an OFF mode request).”
  • a value 1 indicates a “Lo mode request.”
  • a value 2 indicates a “Hi mode request.”
  • a value 3 indicates an “intermittent operation mode request (Intermittent mode request).”
  • a value 4 indicates an “Auto mode request.”
  • a value 5 indicates a “Mist mode request.” Though values 6 and 7 are not used in the present embodiment, they can also be set and used as appropriate.
  • vehicle control interface 110 When vehicle control interface 110 receives the front windshield wiper operation mode request from ADK 200 , it generates a control command corresponding to a value indicated in the front windshield wiper operation mode request and provides the control command to VP 120 .
  • vehicle control interface 110 When the front windshield wiper operation mode request indicates the value 0, vehicle control interface 110 generates a control command indicating the “OFF mode request” and provides the control command to VP 120 .
  • vehicle control interface 110 indicates the value 1
  • vehicle control interface 110 When the front windshield wiper operation mode request indicates the value 1
  • vehicle control interface 110 When the front windshield wiper operation mode request indicates the value 1, vehicle control interface 110 generates a control command indicating the “Lo mode request” and provides the control command to VP 120 .
  • vehicle control interface 110 When the front windshield wiper operation mode request indicates the value 2, vehicle control interface 110 generates a control command indicating the “Hi mode request” and provides the control command to VP 120 .
  • vehicle control interface 110 When the front windshield wiper operation mode request indicates the value 3, vehicle control interface 110 generates a control command indicating the “Intermittent mode request” and provides the control command to VP 120 . When the front windshield wiper operation mode request indicates the value 4, vehicle control interface 110 generates a control command indicating the “Auto mode request” and provides the control command to VP 120 . When the front windshield wiper operation mode request indicates the value 5, vehicle control interface 110 generates a control command indicating the “Mist mode request” and provides the control command to VP 120 .
  • VP 120 accepts a control command.
  • the third driver setting mode does not indicate the “OFF mode” or the “Auto mode,” that is, when the third driver setting mode indicates the “Lo mode,” the “Hi mode,” the “intermittent operation mode,” or the “Mist mode,” VP 120 does not accept the control command.
  • VP 120 sets the operation mode of the front windshield wiper to the “OFF mode” when it receives the control command indicating the “OFF mode request”
  • VP 120 sets the operation mode of the front windshield wiper to the “Lo mode” when it receives the control command indicating the “Lo mode request”
  • VP 120 sets the operation mode of the front windshield wiper to the “Hi mode” when it receives the control command indicating the “Hi mode request”
  • VP 120 sets the operation mode of the front windshield wiper to the “intermittent operation mode” when it receives the control command indicating the “Intermittent mode request”
  • VP 120 sets the operation mode of the front windshield wiper to the “Auto mode” when it receives the control command indicating the “Auto mode request”
  • VP 120 sets the operation mode of the front windshield wiper to the “Mist mode” when it receives a control command indicating the “Mist mode request.”
  • VP 120 sets the operation mode of the front windshield wiper not in accordance with the control command but in accordance with the changed third driver setting mode. In other words, VP 120 prioritizes the operation by the user (a third driver input) over the command from ADK 200 .
  • FIG. 8 is a flowchart showing a procedure of processing for setting an operation mode of the front windshield wiper. Processing in the flowchart in FIG. 8 is repeatedly performed in VP 120 every prescribed control cycle.
  • VP 120 determines whether or not the third driver setting mode indicates the “OFF mode” or the “Auto mode” (S 21 ). When the third driver setting mode indicates the “Lo mode,” the “Hi mode,” the “intermittent operation mode,” or the “Mist mode” (NO in S 21 ), VP 120 maintains the third driver setting mode as the operation mode of the front windshield wiper and the process returns. In other words, VP 120 does not accept a command from ADK 200 .
  • VP 120 determines whether or not the user has performed an operation onto the operation apparatus (S 22 ). In other words, VP 120 determines whether or not the third driver setting mode has been changed.
  • VP 120 changes the operation mode of the front windshield wiper to the third driver setting mode indicated by the operation by the user (S 23 ).
  • VP 120 determines whether or not the front windshield wiper operation mode request from ADK 200 indicates the “Intermittent mode request” (S 24 ). VP 120 determines contents of the front windshield wiper operation mode request based on a control command from vehicle control interface 110 .
  • VP 120 changes the operation mode of the front windshield wiper to the operation mode indicated in the front windshield wiper operation mode request (S 26 ).
  • VP 120 sets the operation mode to the intermittent operation mode (S 25 ).
  • An operation interval of the front windshield wiper in the intermittent operation mode is set in accordance with the command from ADK 200 . The operation interval of the front windshield wiper in the intermittent operation mode will be described below.
  • FAST”, “SECOND FAST,” “THIRD FAST,” and “SLOW” can be set as the operation interval of the front windshield wiper in the intermittent operation mode.
  • the operation interval of the front windshield wiper increases in the order of “FAST”, “SECOND FAST,” “THIRD FAST,” and “SLOW”.
  • ADK 200 When ADK 200 provides the “Intermittent mode request” as the front windshield wiper operation mode request, it provides, in addition to the “Intermittent mode request,” an operation interval request (Windshieldwiper_Intermittent_Wiping_Speed_Command) indicating the operation interval in the intermittent operation mode of the front windshield wiper to vehicle control interface 110 .
  • Vehicle control interface 110 that has received the “Intermittent mode request” and the “operation interval request” generates a control command corresponding to the intermittent operation mode request and the operation interval request and provides the generated control command to VP 120 .
  • VP 120 sets the operation mode of the front windshield wiper to the intermittent operation mode, it sets the operation interval of the front windshield wiper in the intermittent operation mode in accordance with the control command. That is, Windshieldwiper_Intermittent_Wiping_Speed_Command is a command to control the windshield wiper actuation interval at the intermittent mode.
  • the user can also set the operation interval of the front windshield wiper in the intermittent operation mode by performing an operation onto the operation apparatus.
  • VP 120 applies the operation interval set through the operation apparatus.
  • FIG. 9 is a diagram for illustrating a front windshield wiper operation interval request in the intermittent operation mode.
  • FIG. 9 shows relation between an operation interval request and a corresponding value. Specifically, a value is shown in a field “value” and an operation interval request is shown in a field “Description”. A field “remarks” is used when there are remarks.
  • a value 0 indicates “FAST”.
  • a value 1 indicates “SECOND FAST.”
  • a value 2 indicates “THIRD FAST.”
  • a value 3 indicates “SLOW”.
  • vehicle control interface 110 When vehicle control interface 110 receives the operation interval request from ADK 200 , it generates a control command corresponding to a value indicated in the operation interval request and provides the control command to VP 120 . Specifically, when the operation interval request indicates the value 0, vehicle control interface 110 generates the control command indicating “FAST” and provides the control command to VP 120 . When the operation interval request indicates the value 1, vehicle control interface 110 generates the control command indicating “SECOND FAST” and provides the control command to VP 120 . When the operation interval request indicates the value 2, vehicle control interface 110 generates the control command indicating “THIRD FAST” and provides the control command to VP 120 . When the operation interval request indicates the value 3, vehicle control interface 110 generates the control command indicating “SLOW” and provides the control command to VP 120 .
  • VP 120 sets the operation interval of the front windshield wiper to “FAST” when it receives the control command indicating “FAST”
  • VP 120 sets the operation interval of the front windshield wiper to “SECOND FAST” when it receives the control command indicating “SECOND FAST”
  • VP 120 sets the operation interval of the front windshield wiper to “THIRD FAST” when it receives the control command indicating “THIRD FAST”
  • VP 120 sets the operation interval of the front windshield wiper to “SLOW” when it receives the control command indicating “SLOW”.
  • VP 120 changes the operation interval of the front windshield wiper not in accordance with the control command but in accordance with the operation by the user. In other words, VP 120 prioritizes the operation by the user over the command from ADK 200 .
  • VP 120 sets the operation mode of the front windshield wiper in accordance with the front windshield wiper operation mode request from ADK 200 .
  • ADK 200 By accepting the front windshield wiper operation mode request from ADK 200 only when the user is estimated to have left setting of the operation mode of the front windshield wiper system to ADK 200 or vehicle main body 100 , uncomfortable feeling given to the user during autonomous driving can be suppressed.
  • VP 120 prioritizes the operation by the user over the front windshield wiper operation mode request from ADK 200 . By prioritizing the operation by the user over determination by ADK 200 during autonomous driving, uncomfortable feeling given to the user during autonomous driving can be suppressed.
  • VP 120 sets the operation interval of the front windshield wiper in the intermittent operation mode in accordance with the operation interval request from ADK 200 .
  • VP 120 prioritizes the operation by the user over the operation interval request from ADK 200 .
  • the rear windshield wiper includes an “OFF mode,” a “Lo mode,” and an “intermittent operation mode” as operation modes.
  • the “OFF mode” refers to a mode in which the rear windshield wiper is stopped.
  • the “Lo mode” refers to a mode in which the rear windshield wiper is operated at a prescribed speed.
  • the “intermittent operation mode” refers to a mode in which the rear windshield wiper is intermittently operated.
  • the operation interval of the rear windshield wiper in the intermittent operation mode in the present embodiment is fixed to a prescribed interval.
  • the operation interval of the rear windshield wiper may be set similarly to the front windshield wiper described above.
  • the user can set the operation mode of the rear windshield wiper by performing an operation onto the operation apparatus (for example, a windshield wiper switch).
  • the operation apparatus provides to VP 120 (body system 126 ) every prescribed control cycle, a signal (which is also referred to as a “fourth driver input” below) indicating an operation mode (which is also referred to as a “fourth driver setting mode” below) of the rear windshield wiper set by the operation by the user.
  • VP 120 recognizes the fourth driver setting mode based on the fourth driver input.
  • VP 120 accepts a command from ADK 200 .
  • ADK 200 provides a rear windshield wiper operation mode request (Windshieldwiper_Mode_Rear_Command) that indicates an operation state of the rear windshield wiper to vehicle control interface 110 every prescribed control cycle.
  • Vehicle control interface 110 that has received the rear windshield wiper operation mode request generates a control command corresponding to the rear windshield wiper operation mode request and provides the generated control command to VP 120 (body system 126 ).
  • VP 120 sets the operation mode of the rear windshield wiper in accordance with the control command. That is, Windshieldwiper_Mode_Rear_Command is a command to control the rear windshield wiper mode of the vehicle platform (VP 120 ).
  • a value corresponding to the operation mode requested by ADK 200 is set in the rear windshield wiper operation mode request provided from ADK 200 in accordance with contents in FIG. 10 which will be described below.
  • FIG. 10 is a diagram for illustrating a rear windshield wiper operation mode request.
  • FIG. 10 shows relation between a rear windshield wiper operation mode request and a corresponding value. Specifically, a value is shown in a field “value” and a rear windshield wiper operation mode request is shown in a field “Description”. Remarks are given in a field “remarks”.
  • a value 0 indicates a “stop request (OFF mode request).”
  • a value 1 indicates a “Lo mode request.”
  • a value 3 indicates an “intermittent operation mode request (Intermittent mode request).”
  • values 2 and 4 to 7 are not used in the present embodiment, they can also be set and used as appropriate.
  • vehicle control interface 110 When vehicle control interface 110 receives the rear windshield wiper operation mode request from ADK 200 , it generates a control command corresponding to a value indicated in the rear windshield wiper operation mode request and provides the control command to VP 120 .
  • vehicle control interface 110 When the rear windshield wiper operation mode request indicates the value 0, vehicle control interface 110 generates a control command indicating the “OFF mode request” and provides the control command to VP 120 .
  • vehicle control interface 110 indicates the value 1
  • vehicle control interface 110 When the rear windshield wiper operation mode request indicates the value 1
  • vehicle control interface 110 When the rear windshield wiper operation mode request indicates the value 1, vehicle control interface 110 generates a control command indicating the “Intermittent mode request” and provides the control command to VP 120 .
  • VP 120 sets the operation mode to the “OFF mode” when it receives the control command indicating the “OFF mode request,” VP 120 sets the operation mode to the “Lo mode” when it receives the control command indicating the “Lo mode request,” and VP 120 sets the operation mode to the “intermittent operation mode” when it receives a control command indicating the “Intermittent mode request.”
  • VP 120 sets the operation mode of the rear windshield wiper not in accordance with the control command but in accordance with the changed fourth driver setting mode. In other words, VP 120 prioritizes the operation by the user (the fourth driver input) over the command from ADK 200 .
  • FIG. 11 is a flowchart showing a procedure of processing for setting an operation mode of the rear windshield wiper. Processing in the flowchart in FIG. 11 is repeatedly performed in VP 120 every prescribed control cycle.
  • VP 120 determines whether or not the user has performed an operation onto the operation apparatus (S 31 ). In other words, VP 120 determines whether or not the fourth driver setting mode has been changed.
  • VP 120 changes the operation mode of the rear windshield wiper to the fourth driver setting mode indicated by the operation by the user (S 32 ).
  • VP 120 changes the operation mode of the rear windshield wiper to the operation mode indicated in the rear windshield wiper operation mode request from ADK 200 (S 33 ).
  • VP 120 changes the operation mode of the rear windshield wiper in accordance with the rear windshield wiper operation mode request from ADK 200 .
  • VP 120 prioritizes the operation by the user over the rear windshield wiper operation mode request from ADK 200 .
  • a vehicle is a vehicle on which an autonomous driving system is mountable.
  • the vehicle includes a vehicle platform that controls the vehicle in accordance with an instruction from the autonomous driving system and a vehicle control interface that interfaces between the vehicle platform and the autonomous driving system.
  • the vehicle platform includes a headlight system, a hazard light system, a front windshield wiper system, and a rear windshield wiper system.
  • the vehicle platform sets an operation mode of each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system in accordance with (i) an operation mode request for each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system received from the autonomous driving system and/or (ii) an operation by a user onto an operation apparatus provided for each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system.
  • the vehicle platform sets the operation mode with the operation by the user being prioritized over the operation mode request.
  • the first prescribed mode includes an “OFF mode” and an “AUTO mode.”
  • the “OFF mode” is a mode in which a headlight is turned off.
  • the “AUTO mode” is a mode in which the operation mode of the headlight system is automatically set by the vehicle platform.
  • the second prescribed mode includes an “OFF mode” and an “Auto mode.”
  • the “OFF mode” is a mode in which a front windshield wiper is stopped.
  • the “Auto mode” is a mode in which the operation mode of the front windshield wiper system is automatically set by the vehicle platform.
  • the front windshield wiper system includes as the operation mode, an intermittent operation mode in which a front windshield wiper is intermittently operated.
  • the vehicle platform sets an operation interval in accordance with an operation interval request that indicates the operation interval of the front windshield wiper in the intermittent operation mode received from the autonomous driving system and/or the operation by the user onto the operation apparatus.
  • a vehicle includes an autonomous driving system that creates a driving plan, a vehicle platform that carries out vehicle control in accordance with an instruction from the autonomous driving system, and a vehicle control interface that interfaces between the vehicle platform and the autonomous driving system.
  • the vehicle platform includes a headlight system, a hazard light system, a front windshield wiper system, and a rear windshield wiper system.
  • the vehicle platform sets an operation mode of each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system in accordance with (i) an operation mode request for each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system received from the autonomous driving system and/or (ii) an operation by a user onto an operation apparatus provided for each of the headlight system, the hazard light system, the front windshield wiper system, and the rear windshield wiper system.
  • the vehicle platform sets the operation mode with the operation by the user being prioritized over the operation mode request.
  • the first prescribed mode includes an “OFF mode” and an “AUTO mode.”
  • the “OFF mode” is a mode in which a headlight is turned off.
  • the “AUTO mode” is a mode in which the operation mode of the headlight system is automatically set by the vehicle platform.
  • the front windshield wiper system includes as the operation mode, an intermittent operation mode in which a front windshield wiper is intermittently operated.
  • the vehicle platform sets an operation interval in accordance with (i) an operation interval request that indicates the operation interval of the front windshield wiper in the intermittent operation mode received from the autonomous driving system and/or (ii) the operation by the user onto the operation apparatus and sets the operation interval with the operation by the user being prioritized over the operation interval request.
  • This document is an API specification of Toyota Vehicle Platform and contains the outline, the usage and the caveats of the application interface.
  • ADS Autonomous Driving System ADK Autonomous Driving Kit VP Vehicle Platform. VCIB Vehicle Control Interface Box. This is an ECU for the interface and the signal converter between ADS and Toyota VP’s sub systems.
  • the overall structure of MaaS with the target vehicle is shown ( FIG. 12 ).
  • Vehicle control technology is being used as an interface for technology providers.
  • the system architecture as a premise is shown ( FIG. 13 ).
  • the target vehicle will adopt the physical architecture of using CAN for the bus between ADS and VCIB.
  • the CAN frames and the bit assignments are shown in the form of “bit assignment table” as a separate document.
  • the ADS should create the driving plan, and should indicate vehicle control values to the VP.
  • the Toyota VP should control each system of the VP based on indications from an ADS.
  • CAN will be adopted as a communication line between ADS and VP. Therefore, basically, APIs should be executed every defined cycle time of each API by ADS.
  • a typical workflow of ADS of when executing APIs is as follows ( FIG. 14 ).
  • the below diagram shows an example.
  • Acceleration Command requests deceleration and makes the vehicle stop. After Actual_Moving_Direction is set to “standstill”, any shift position can be requested by Propulsion Direction Command. (In the example below, “D” ⁇ “R”).
  • Acceleration Command has to request deceleration.
  • acceleration/deceleration is controlled based on Acceleration Command value ( FIG. 16 ).
  • Immobilization Command “Release” is requested when the vehicle is stationary. Acceleration Command is set to Deceleration at that time.
  • the vehicle is accelerated/decelerated based on Acceleration Command value ( FIG. 17 ).
  • Tire Turning Angle Command is the relative value from Estimated_Road_Wheel_Angle_Actual.
  • target vehicle deceleration is the sum of 1) estimated deceleration from the brake pedal stroke and 2) deceleration request from AD system.
  • ADS confirms Propulsion Direction by Driver and changes shift position by using Propulsion Direction Command.
  • the maximum is selected from
  • Tire Turning Angle Command is not accepted if the driver strongly turns the steering wheel.
  • the above-mentioned is determined by Steering_Wheel_Intervention flag.
  • Brake_Pedal_Intervention This signal shows whether the brake pedal is T.B.D. depressed by a driver (intervention) Steering_Wheel_Intervention This signal shows whether the steering wheel is T.B.D. turned by a driver (intervention) Shift_Lever_Intervention This signal shows whether the shift lever is controlled T.B.D.
  • the steering angle rate is calculated from the vehicle speed using 2.94 m/s 3
  • the threshold speed between A and B is 10 [km/h] ( FIG. 18 ).
  • This signal shows whether the accelerator pedal is depressed by a driver (intervention).
  • This signal shows whether the brake pedal is depressed by a driver (intervention).
  • This signal shows whether the steering wheel is turned by a driver (intervention).
  • This signal shows whether the shift lever is controlled by a driver (intervention).
  • VCIB achieves the following procedure after Ready-ON. (This functionality will be implemented from the CV.)
  • this signal may be set to “Occupied”.
  • the judgement result of buckling/unbuckling shall be transferred to CAN transmission buffer within 1.3 s after IG_ON or before allowing firing, whichever is earlier.
  • Vehicle power off condition In this mode, the high voltage battery does not supply power, and neither VCIB nor other VP ECUs are activated.
  • VCIB is awake by the low voltage battery. In this mode, ECUs other than VCIB are not awake except for some of the body electrical ECUs.
  • the high voltage battery supplies power to the whole VP and all the VP ECUs including VCIB are awake.
  • Transmission interval is 100 ms within fuel cutoff motion delay allowance time (1 s) so that data can be transmitted more than 5 times. In this case, an instantaneous power interruption is taken into account.
  • Target Vehicle Type This specification is applied to the Toyota vehicles with the electronic platform called 19ePF [ver. 1 and ver. 2].
  • the representative vehicle with 19ePF is shown as follows.
  • ADS Autonomous Driving System ADK Autonomous Driving Kit VP Vehicle Platform. VCIB Vehicle Control Interface Box. This is an ECU for the interface and the signal converter between ADS and Toyota VP's sub systems.
  • Vehicle control technology is being used as an interface for technology providers.
  • the system architecture on the vehicle as a premise is shown ( FIG. 22 ).
  • the target vehicle of this document will adopt the physical architecture of using CAN for the bus between ADS and VCIB.
  • the CAN frames and the bit assignments are shown in the form of “bit assignment chart” as a separate document.
  • the power supply architecture as a premise is shown as follows ( FIG. 23 ).
  • the blue colored parts are provided from an ADS provider. And the orange colored parts are provided from the VP.
  • the power structure for ADS is isolate from the power structure for VP. Also, the ADS provider should install a redundant power structure isolated from the VP.
  • the basic safety concept is shown as follows.
  • the entire vehicle achieves the safety state 2 by activating the immobilization system.
  • the Braking System is designed to prevent the capability from becoming 0.3 G or less.
  • the Steering System is designed to prevent the capability from becoming 0.3 G or less.
  • any single failure on the Power Supply System doesn't cause loss of power supply functionality. However, in case of the primary power failure, the secondary power supply system keeps supplying power to the limited systems for a certain time.
  • Toyota's MaaS vehicle adopts the security document issued by Toyota as an upper document.
  • the entire risk includes not only the risks assumed on the base e-PF but also the risks assumed for the Autono-MaaS vehicle.
  • the countermeasure for a remote attack is shown as follows.
  • the autonomous driving kit communicates with the center of the operation entity, end-to-end security should be ensured. Since a function to provide a travel control instruction is performed, multi-layered protection in the autonomous driving kit is required. Use a secure microcomputer or a security chip in the autonomous driving kit and provide sufficient security measures as the first layer against access from the outside. Use another secure microcomputer and another security chip to provide security as the second layer. (Multi-layered protection in the autonomous driving kit including protection as the first layer to prevent direct entry from the outside and protection as the second layer as the layer below the former)
  • the countermeasure for a modification is shown as follows.
  • measures against a counterfeit autonomous driving kit For measures against a counterfeit autonomous driving kit, device authentication and message authentication are carried out. In storing a key, measures against tampering should be provided and a key set is changed for each pair of a vehicle and an autonomous driving kit. Alternatively, the contract should stipulate that the operation entity exercise sufficient management so as not to allow attachment of an unauthorized kit. For measures against attachment of an unauthorized product by an Autono-MaaS vehicle user, the contract should stipulate that the operation entity exercise management not to allow attachment of an unauthorized kit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Transportation (AREA)
  • Automation & Control Theory (AREA)
  • Physics & Mathematics (AREA)
  • Combustion & Propulsion (AREA)
  • Chemical & Material Sciences (AREA)
  • Mathematical Physics (AREA)
  • Radar, Positioning & Navigation (AREA)
  • General Physics & Mathematics (AREA)
  • Remote Sensing (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Human Computer Interaction (AREA)
  • Lighting Device Outwards From Vehicle And Optical Signal (AREA)
  • Control Of Driving Devices And Active Controlling Of Vehicle (AREA)
US17/153,930 2020-01-31 2021-01-21 Vehicle Abandoned US20210245654A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US17/659,541 US11560084B2 (en) 2020-01-31 2022-04-18 Vehicle
US18/090,559 US11850997B2 (en) 2020-01-31 2022-12-29 Vehicle
US18/508,712 US20240116431A1 (en) 2020-01-31 2023-11-14 Vehicle

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020015727A JP7298497B2 (ja) 2020-01-31 2020-01-31 車両
JP2020-015727 2020-01-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/659,541 Continuation US11560084B2 (en) 2020-01-31 2022-04-18 Vehicle

Publications (1)

Publication Number Publication Date
US20210245654A1 true US20210245654A1 (en) 2021-08-12

Family

ID=74553564

Family Applications (4)

Application Number Title Priority Date Filing Date
US17/153,930 Abandoned US20210245654A1 (en) 2020-01-31 2021-01-21 Vehicle
US17/659,541 Active US11560084B2 (en) 2020-01-31 2022-04-18 Vehicle
US18/090,559 Active US11850997B2 (en) 2020-01-31 2022-12-29 Vehicle
US18/508,712 Pending US20240116431A1 (en) 2020-01-31 2023-11-14 Vehicle

Family Applications After (3)

Application Number Title Priority Date Filing Date
US17/659,541 Active US11560084B2 (en) 2020-01-31 2022-04-18 Vehicle
US18/090,559 Active US11850997B2 (en) 2020-01-31 2022-12-29 Vehicle
US18/508,712 Pending US20240116431A1 (en) 2020-01-31 2023-11-14 Vehicle

Country Status (7)

Country Link
US (4) US20210245654A1 (ko)
EP (1) EP3858682A1 (ko)
JP (2) JP7298497B2 (ko)
KR (1) KR102587697B1 (ko)
CN (2) CN113276868B (ko)
BR (1) BR102021001792A2 (ko)
RU (1) RU2753086C1 (ko)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220250648A1 (en) * 2020-01-31 2022-08-11 Toyota Jidosha Kabushiki Kaisha Vehicle and method of controlling vehicle

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116101303B (zh) * 2023-04-07 2023-07-07 成都理工大学工程技术学院 一种车辆辅助驾驶方法、系统、装置和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040176880A1 (en) * 1997-01-28 2004-09-09 American Calcar Inc. Multimedia information and control system for automobiles
US20170267256A1 (en) * 2016-03-15 2017-09-21 Cruise Automation, Inc. System and method for autonomous vehicle driving behavior modification
US20190212737A1 (en) * 2018-01-08 2019-07-11 Steer Tech Llc Automated Valet System
US20200156652A1 (en) * 2018-11-16 2020-05-21 Here Global B.V. Method, apparatus, and system for assessing safety and comfort systems of a vehicle

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3998533B2 (ja) 2001-08-09 2007-10-31 株式会社デンソー ワイパ制御装置
GB2492748B (en) * 2011-07-04 2014-05-07 Jaguar Land Rover Ltd Vehicle control system and method for controlling a vehicle
JP2014133425A (ja) 2013-01-08 2014-07-24 Mazda Motor Corp 雨滴検出装置
EP3027707B1 (de) 2013-07-30 2019-12-11 Merck Patent GmbH Materialien für elektronische vorrichtungen
JP6003854B2 (ja) * 2013-09-11 2016-10-05 トヨタ自動車株式会社 運転支援装置
JP6301376B2 (ja) * 2014-02-05 2018-03-28 本田技研工業株式会社 車両の制御装置および車両の制御方法
RU2690726C2 (ru) * 2014-03-12 2019-06-05 Ниссан Мотор Ко., Лтд. Устройство управления транспортного средства
US10101742B2 (en) 2014-12-07 2018-10-16 Toyota Motor Engineering & Manufacturing North America, Inc. Mixed autonomous and manual control of autonomous vehicles
JP6176263B2 (ja) * 2015-01-19 2017-08-09 トヨタ自動車株式会社 自動運転装置
JP2016132421A (ja) 2015-01-22 2016-07-25 トヨタ自動車株式会社 自動運転装置
US10167015B2 (en) 2015-05-11 2019-01-01 GM Global Technology Operations LLC System for retrofitting vehicle automation
KR20170015114A (ko) * 2015-07-30 2017-02-08 삼성전자주식회사 자율 주행 차량 및 자율 주행 차량 제어 방법
US9963012B2 (en) * 2015-12-07 2018-05-08 GM Global Technology Operations LLC Personalizing vehicular comfort settings for a specific user
JP6450980B2 (ja) 2016-05-02 2019-01-16 本田技研工業株式会社 車両制御システム、車両制御方法、および車両制御プログラム
US10086839B2 (en) 2016-09-21 2018-10-02 Ford Global Technologies, Llc Semiautonomous vehicle control system
KR101906197B1 (ko) * 2016-11-07 2018-12-05 엘지전자 주식회사 차량 및 그 제어방법
JP6705373B2 (ja) * 2016-12-27 2020-06-03 トヨタ自動車株式会社 自動運転システム
JP7001349B2 (ja) * 2017-02-16 2022-01-19 株式会社デンソー 自動運転制御装置
US20190100083A1 (en) * 2017-10-03 2019-04-04 Ford Global Technologies, Llc Controlling sun load in an autonomous vehicle to conserve energy

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040176880A1 (en) * 1997-01-28 2004-09-09 American Calcar Inc. Multimedia information and control system for automobiles
US20170267256A1 (en) * 2016-03-15 2017-09-21 Cruise Automation, Inc. System and method for autonomous vehicle driving behavior modification
US20190212737A1 (en) * 2018-01-08 2019-07-11 Steer Tech Llc Automated Valet System
US20200156652A1 (en) * 2018-11-16 2020-05-21 Here Global B.V. Method, apparatus, and system for assessing safety and comfort systems of a vehicle

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220250648A1 (en) * 2020-01-31 2022-08-11 Toyota Jidosha Kabushiki Kaisha Vehicle and method of controlling vehicle
US11702100B2 (en) * 2020-01-31 2023-07-18 Toyota Jidosha Kabushiki Kaisha Vehicle and method of controlling vehicle
US12084083B2 (en) 2020-01-31 2024-09-10 Toyota Jidosha Kabushiki Kaisha Vehicle and method of controlling vehicle

Also Published As

Publication number Publication date
KR102587697B1 (ko) 2023-10-12
US20220234493A1 (en) 2022-07-28
KR20210098353A (ko) 2021-08-10
US20230142470A1 (en) 2023-05-11
RU2753086C1 (ru) 2021-08-11
JP7559877B2 (ja) 2024-10-02
CN113276868A (zh) 2021-08-20
JP2021123147A (ja) 2021-08-30
BR102021001792A2 (pt) 2021-11-23
US11560084B2 (en) 2023-01-24
US20240116431A1 (en) 2024-04-11
JP7298497B2 (ja) 2023-06-27
CN118306423A (zh) 2024-07-09
CN113276868B (zh) 2024-05-17
JP2023140352A (ja) 2023-10-04
US11850997B2 (en) 2023-12-26
EP3858682A1 (en) 2021-08-04

Similar Documents

Publication Publication Date Title
US11667308B2 (en) Vehicle
US11673573B2 (en) Vehicle and vehicle control interface
US20220250647A1 (en) Vehicle, Vehicle Control Interface Box, and Autonomous Driving Vehicle
US11987284B2 (en) Vehicle and autonomous driving kit
US11731650B2 (en) Vehicle and method of controlling vehicle
US12084074B2 (en) Vehicle and vehicle control interface
US11850997B2 (en) Vehicle
US11586199B2 (en) Vehicle and power supply system of vehicle
US11951988B2 (en) Vehicle
US12084083B2 (en) Vehicle and method of controlling vehicle
US11733701B2 (en) Vehicle
US11673574B2 (en) Vehicle with mountable and removable autonomous driving system

Legal Events

Date Code Title Description
AS Assignment

Owner name: TOYOTA JIDOSHA KABUSHIKI KAISHA, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ANDO, EISUKE;REEL/FRAME:054977/0453

Effective date: 20201214

STPP Information on status: patent application and granting procedure in general

Free format text: APPLICATION DISPATCHED FROM PREEXAM, NOT YET DOCKETED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION