Control Systems and Control Devices

The control system manages software updates to prioritize automatic driving functions over updates, ensuring uninterrupted operation by suppressing updates during automatic driving, enhancing system design flexibility.

JP7587909B2Active Publication Date: 2024-11-21PANASONIC AUTOMOTIVE SYST CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021060628
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-31
Publication Date
2024-11-21
Estimated Expiration
2041-03-31

AI Technical Summary

Technical Problem

Existing automatic driving systems face challenges in prioritizing continued use of automatic driving functions over software updates, which can restrict these functions during software updates.

Method used

A control system and device that includes a detection unit, suppression request section, and operation control unit to manage software updates, allowing automatic driving to continue without interruption by detecting switching commands and requesting suppression of software updates.

Benefits of technology

Enables automatic driving without restricting functions, improving system design flexibility by avoiding software update processing during automatic operation, thus ensuring uninterrupted functionality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007587909000001
    Figure 0007587909000001
  • Figure 0007587909000002
    Figure 0007587909000002
  • Figure 0007587909000003
    Figure 0007587909000003
Patent Text Reader

Abstract

To provide a control system and a control device, which can perform automatic operations without limiting functions.SOLUTION: A control system according to the present disclosure includes: a detection section; a suppression request section; and an operation control section. The detection section detects a first switching command for instructing switching to an automatic operation. When the first switching command is detected by the detection section, the suppression request section sends an update suppression request for suppressing the update of software to a rewrite management section for controlling update processing of the software. The operation control section requests at least one of execution sections for executing automatic operation control to start the automatic operation when receiving a first response indicating that the update of the software is suppressed from the rewrite management section according to the update suppression request.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a control system and a control device. [Background technology]

[0002] Recently, the technology of automatic driving of a vehicle has been developed, and a technology for switching between automatic driving and manual driving by a driver is known. In addition, during automatic driving, the amount of processing of the CPU (Central Processing Unit) of the ECU (Electronic Control Unit) generally increases. In addition, a technology for wirelessly rewriting software using OTA (Over The Air) technology has been developed to update software processed by the ECU. As a technology for updating software installed in such a vehicle's ECU, a technology has been disclosed that, when software related to an automatic driving function or a driving assistance function needs to be updated, restricts the operation of the automatic driving function or the driving assistance function and prioritizes the software update (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6569771 Summary of the Invention [Problem to be solved by the invention]

[0004] There are cases where you may want to prioritize continued use of automated driving or driver assistance features over software updates.

[0005] The present disclosure aims to provide a control system and a control device that enable autonomous driving without restricting functions. [Means for solving the problem]

[0006] The control system according to the present disclosure includes a detection unit and A rewrite management unit; The control device includes a suppression request unit and an operation control unit. The detection unit detects a first switching command that instructs switching to the autonomous operation. The update management unit controls the software update process. When the detection unit detects the first switching command, the suppression request unit transmits an update suppression request for suppressing software updates to a rewrite management unit that controls software update processing. In response to the update suppression request, the operation control unit The suppression request unit: When a first response indicating that the software update has been suppressed is received from the rewrite management unit, a request is made to at least one execution unit that executes autonomous driving control to start autonomous driving. When the rewrite management unit receives an update suppression request, if the software is being updated, it sends an update control command to at least one execution unit to interrupt the software update, and when it receives a third response from the at least one execution unit indicating that the interruption has been completed, it sends the first response to the suppression request unit. Effect of the Invention

[0007] The control system and control device according to the present disclosure enable automatic driving without restricting functions. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of an overall configuration of a vehicle according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the vehicle control device according to the first embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a functional block configuration of the vehicle control device according to the first embodiment. [Figure 4] FIG. 4 is a diagram showing another example of the configuration of functional blocks of the vehicle control device according to the first embodiment. [Diagram 5] FIG. 5 is a flowchart showing an example of an operation flow of the control request unit of the vehicle control device according to the first embodiment when switching from manual driving to automatic driving. [Figure 6] FIG. 6 is a flowchart showing an example of an operation flow of the control request unit of the vehicle control device according to the first embodiment when switching from automatic driving to manual driving. [Figure 7]FIG. 7 is a flowchart showing an example of an operation flow of the rewrite management unit of the vehicle control device according to the first embodiment when switching from manual driving to automatic driving. [Figure 8] FIG. 8 is a flowchart showing an example of an operation flow of the rewrite management unit of the vehicle control device according to the first embodiment when switching from automatic driving to manual driving. [Figure 9] FIG. 9 is a flowchart showing an example of a flow of the software update operation of the execution unit of the vehicle control device according to the first embodiment. [Figure 10] FIG. 10 is a flowchart showing an example of a flow of the automatic / manual switching operation of the execution unit of the vehicle control device according to the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a functional block configuration of a vehicle control device according to the second embodiment. [Figure 12] FIG. 12 is a flowchart illustrating an example of an operation flow of the rewrite management unit of the vehicle control device according to the second embodiment when switching from manual driving to automatic driving. [Figure 13] FIG. 13 is a flowchart showing an example of an operation flow of the rewrite management unit of the vehicle control device according to the second embodiment when switching from automatic driving to manual driving. [Figure 14] FIG. 14 is a flowchart showing an example of an operation flow of the control request unit of the vehicle control device according to the third embodiment when switching from manual driving to automatic driving. [Figure 15] FIG. 15 is a flowchart illustrating an example of an operation flow of the rewrite management unit of the vehicle control device according to the third embodiment when switching from manual driving to automatic driving. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of a control system and a control device according to the present disclosure will be described with reference to the drawings.

[0010] [First embodiment] (Overall vehicle configuration) Fig. 1 is a diagram showing an example of the overall configuration of a vehicle according to the first embodiment. With reference to Fig. 1, the overall configuration of a vehicle 1 according to the present embodiment will be described.

[0011] As shown in FIG. 1, the vehicle 1 includes a body 2, wheels 3F, and wheels 3R. The wheels 3F are a pair of front wheels that are installed on the front side of the body 2 and contact the road surface. The wheels 3R ​​are a pair of rear wheels that are installed on the rear side of the body 2 and contact the road surface. The vehicle 1 can run using a pair of wheels 3F and a pair of wheels 3R ​​that are arranged along a predetermined direction. In this case, the predetermined direction in which the wheels 3F and the wheels 3R ​​are arranged becomes the direction of movement of the vehicle 1, and the vehicle 1 can move forward or backward by switching gears, etc. Note that when referring to any of the wheels 3F and the wheels 3R, or when referring to them collectively, they will simply be referred to as "wheels 3".

[0012] As shown in FIG. 1, the vehicle 1 is equipped with a seat 4, a vehicle drive unit 5, imaging units 6a and 6b, door mirrors 7L and 7R, a rear seat 8, a rearview mirror 9, an engine switch 10a, an automatic driving changeover switch 10b, a steering wheel 11, a shift lever 12, a parking brake 13, a door lock device 14, a display device 15, a speaker 19, a vehicle control device 20, and a temperature sensor 21.

[0013] The seat 4 is provided in the vehicle cabin of the vehicle 1 and serves as a driver's seat for the driver of the vehicle 1. While seated in the seat 4, the driver can steer the vehicle 1 by operating the steering wheel 11 and an accelerator pedal and a brake pedal (not shown).

[0014] The vehicle drive unit 5 is a drive device mounted on the vehicle 1. The vehicle drive unit 5 is, for example, an engine, a motor, a drive unit for the wheels 3, or the like.

[0015] The imaging unit 6a is a camera provided in the front part of the vehicle 1 and captures an image of the area in front of the vehicle 1. The imaging unit 6b is a camera provided in the rear part of the vehicle 1 and captures an image of the area behind the vehicle 1. As described later, the imaging units 6a and 6b are monocular cameras or stereo cameras capable of detecting the position, distance, speed, and the like of other vehicles. The imaging units 6a and 6b are used, for example, to grasp the surrounding situation when the vehicle 1 performs autonomous driving. Note that when referring to any imaging unit among the imaging units 6a and 6b, or when referring to them collectively, they are simply referred to as the "imaging unit 6."

[0016] The door mirror 7L is an exterior rear-view mirror attached to the front of the left door of the vehicle body 2 for viewing the left rear. The rear-view mirror 7R is an exterior rear-view mirror attached to the front of the right door of the vehicle body 2 for viewing the right rear. When referring to any of the door mirrors 7L and 7R or when referring to them collectively, they will be simply referred to as "door mirror 7." Door mirrors may also be referred to as side mirrors, etc. Instead of the door mirror 7, a fender mirror attached to the front end of the hood of the vehicle body 2 may be installed.

[0017] The rear seat 8 is provided at the rear side of the passenger compartment of the vehicle 1, and is a seat for passengers other than the driver of the vehicle 1 to sit in.

[0018] The room mirror 9 is an interior rear-view mirror that is installed on the ceiling above the windshield and allows the driver to see behind and to the sides of the vehicle. The room mirror is also called a back mirror.

[0019] The engine switch 10a is a switch that the driver operates when starting the engine of the vehicle 1. The engine switch 10a is also called an ignition switch. The driver operates the engine switch 10a to start or stop the engine of the vehicle 1. The operation of the engine switch 10a also controls the power supply to electronic devices mounted on the vehicle 1.

[0020] The automatic driving changeover switch 10b is a switch for switching the driving state of the vehicle 1 between automatic driving and manual driving. The automatic driving changeover switch 10b is an example of an "operation unit".

[0021] The steering wheel 11 is a steering wheel for steering the vehicle 1 and is installed on the dashboard in front of the seat 4.

[0022] The shift lever 12 is a lever that the driver operates when changing the shift position. The movable range of the shift lever 12 includes, for example, a parking position, a reverse position, a neutral position, and a drive position. When the shift lever 12 is in the parking position, the vehicle 1 is in a so-called parked state in which the power of the engine is not transmitted to the wheels 3. When the shift lever 12 is in the reverse position, the vehicle 1 is in a state in which it can move backward. When the shift lever 12 is in the drive position, the vehicle 1 is in a state in which it can move forward.

[0023] The parking brake 13 is one of the brake mechanisms of the vehicle 1. The parking brake 13 is a manual braking mechanism that allows the driver to manually stop the movement of the vehicle 1. When the parking brake 13 is applied, the movement of the vehicle 1 is stopped and the vehicle 1 is in a parked state. When the parking brake 13 is released, the vehicle 1 is in a movable state. The parking brake is also called a side brake.

[0024] The door lock device 14 is a device that switches the state of the doors of the vehicle 1 between a locked state and an unlocked state. For example, the door of the vehicle 1 can be switched between a locked state and an unlocked state by a key for the vehicle 1 or the like from outside the vehicle 1.

[0025] The display device 15 is a display device such as an LCD (Liquid Crystal Display) or an OELD (Organic Electro-Luminescent Display) that is installed on a dashboard or the like in front of the seat 4. The display device 15 performs various displays such as road guidance, weather forecasts, driving assistance displays, and displays indicating that the driving mode has been switched to automatic driving or manual driving. The display device 15 may have a voice output function and an input function in addition to an image display function.

[0026] The audio output function of the display device 15 may be realized by a speaker 19. The display device 15 may be configured as a touch panel having an input function for receiving operation input by a user. The display device 15 may also include a navigation device having a location information acquisition function and a route search function using map information.

[0027] The speaker 19 is a device that outputs audio. For example, the speaker 19 outputs audio notifying the driver that the driving mode has been switched to automatic driving or manual driving, audio of driving instructions for driving assistance, and the like.

[0028] The vehicle control device 20 is an ECU (Electronic Control Unit) or an OBU (On Board Unit) that controls various operations of the vehicle 1. The vehicle control device 20 is a device that not only controls a driving control function and a driving assistance function, but also controls operations based on various functions provided in the vehicle 1 as a whole.

[0029] The temperature sensor 21 is a sensor that detects the internal temperature or the ambient temperature of the vehicle control device 20. The temperature sensor 21 is installed, for example, inside or near the vehicle control device 20. The temperature sensor 21 corresponds to a "temperature detection unit." Note that, when the CPU 101 described below is an SoC, the temperature sensor 21 may be built into the SoC.

[0030] (Hardware configuration of vehicle control device) 2 is a diagram showing an example of a hardware configuration of the vehicle control device according to the first embodiment. With reference to FIG. 2, the hardware configuration of the vehicle control device 20 according to the present embodiment will be described.

[0031] 2, the vehicle control device 20 includes a CPU (Central Processing Unit) 101, a RAM (Random Access Memory) 102, a ROM (Read Only Memory) 103, an imaging I / F 104, a display I / F 105, a GPS (Global Positioning System) I / F 106, a vehicle speed I / F 107, a communication I / F 108, an audio I / F 109, an input I / F 110, and a sensor I / F 111. The CPU 101, the RAM 102, the ROM 103, the imaging I / F 104, the display I / F 105, the GPS I / F 106, the vehicle speed I / F 107, the communication I / F 108, the audio I / F 109, the input I / F 110, and the sensor I / F 111 are connected to each other via a bus 112 so as to enable data communication. Note that the bus 112 is not limited to a configuration in which all components are connected as shown in FIG. 2, and each component may be connected to the CPU 101 via a bus, for example.

[0032] The CPU 101 is a calculation device that controls the entire vehicle control device 20. The RAM 102 is a volatile storage device that serves as a work area for processing by the CPU 101. The ROM 103 is a non-volatile storage device that stores the control program for the vehicle control device 20, various data, and the like.

[0033] The CPU 101 is a concept including a micro processing unit (MPU), a micro controller unit (MCU), and a system on a chip (SoC), etc. The CPU 101 may include two or more of the MPU, the MCU, and the SoC.

[0034] The imaging I / F 104 is an interface for receiving captured images captured by the imaging units 6a and 6b. The imaging I / F 104 continuously receives the captured images captured by the imaging units 6a and 6b as frame images to obtain them as a moving image.

[0035] The display I / F 105 is an interface for transmitting various display data to the display device 15.

[0036] The GPS I / F 106 is an interface for receiving position information received by a GPS sensor 16 installed in the vehicle 1. The position information received by the GPS sensor 16 is, for example, a GPS signal. The vehicle speed I / F 107 is an interface for receiving speed information from a vehicle speed sensor 17 that detects the vehicle speed of the vehicle 1. The vehicle speed sensor 17 is installed, for example, near the wheels 3, and generates a vehicle speed pulse that indicates the rotation speed or number of rotations of the wheels 3.

[0037] The communication I / F 108 is an interface for transmitting and receiving data to and from a communication device 18 installed in the vehicle 1. The communication device 18 performs data communication with an external device such as a server via wireless communication. This allows the communication I / F 108 to perform data communication with the external device via the communication device 18.

[0038] The audio I / F 109 is an interface for outputting audio data to a speaker 19 installed in the vehicle 1 .

[0039] The input I / F 110 is an interface for inputting input data and operation signals from various input devices to the vehicle control device 20. For example, the automatic driving changeover switch 10b is connected to the input I / F 110, and the input I / F 110 is an interface for receiving a changeover command to automatic driving or manual driving from the automatic driving changeover switch 10b.

[0040] The sensor I / F 111 is an interface for inputting detection signals or detection data from various sensors arranged in the vehicle 1 to the vehicle control device 20. For example, a temperature sensor 21 is connected to the sensor I / F 111, and the sensor I / F 111 inputs the internal temperature or the ambient temperature of the vehicle control device 20 detected by the temperature sensor 21 to the vehicle control device 20.

[0041] It should be noted that the hardware configuration of the vehicle control device 20 shown in FIG. 2 is merely an example, and it is not necessary for the vehicle control device 20 to include all of the components shown in FIG. 2, or other components may be included.

[0042] (Configuration and operation of functional blocks of vehicle control device) Fig. 3 is a diagram showing an example of the configuration of functional blocks of the vehicle control device according to the first embodiment. Fig. 4 is a diagram showing another example of the configuration of functional blocks of the vehicle control device according to the first embodiment. The configuration and operation of the functional blocks of the vehicle control device 20 according to this embodiment will be described with reference to Figs. 3 and 4.

[0043] As shown in FIG. 3, the vehicle control device 20 includes a switch detection unit 201, a control request unit 202, a rewrite management unit 203, an execution unit 204, and an output control unit 205.

[0044] The switch detection unit 201 is a functional unit that detects a command to switch from manual operation to automatic operation or a command to switch from automatic operation to manual operation from the automatic operation changeover switch 10b. The switch detection unit 201 corresponds to a "detection unit." The switch detection unit 201 is realized, for example, by the input I / F 110 and the CPU 101 shown in FIG. 2 executing a program.

[0045] The command to switch between automatic driving and manual driving detected by the switch detection unit 201 is not limited to being detected from the automatic driving changeover switch 10b, and may be detected based on the occurrence of a predetermined event, for example. The switch detection unit 201 may detect the switch command from automatic driving to manual driving, for example, when a malfunction occurs in the operation of the vehicle control device 20 or when a fault occurs in the driving operation of the vehicle 1. The switch detection unit 201 may detect the switch command from manual driving to automatic driving, for example, when an event occurs that requires risk avoidance without manual driving, or when the driver is dozing or an abnormality is detected.

[0046] The control request unit 202 is a functional unit that performs suppression control of software updates and start / end control of automatic driving based on a switching command detected by the switch detection unit 201. The software is, for example, a program and data for realizing an automatic driving function, a driving assistance function, and functions other than these functions, and is installed in the ROM 103. As shown in FIG. 3, the control request unit 202 has a suppression request unit 2021, an automatic driving control request unit 2022, and a notification control unit 2023. The control request unit 202 is realized, for example, by the CPU 101 shown in FIG. 2 executing a program.

[0047] The suppression request unit 2021 is a functional unit that, when the switch detection unit 201 detects a command to switch from manual driving to automatic driving, sends an update suppression request to the rewrite management unit 203 to suppress software updates.

[0048] The automatic driving control request unit 2022 is a functional unit that sends an automatic driving start request to the execution unit 204 to request the start of automatic driving when the suppression request unit 2021 receives a response indicating that the software update has been suppressed from the rewrite management unit 203 in response to the update suppression request. The response indicating that the software update has been suppressed is, for example, a response indicating that the rewrite management unit 203 does not start the software update and that the execution unit 204 has interrupted the software update when the execution unit 204 is updating the software. In addition, the response indicating that the software update has been suppressed is, for example, a response indicating that the rewrite management unit 203 does not start the software update when the execution unit 204 is not updating the software. The automatic driving control request unit 2022 corresponds to a "driving control unit".

[0049] The notification control unit 2023 is a functional unit that notifies the output control unit 205 that autonomous driving has started when the autonomous driving control request unit 2022 receives a response from the execution unit 204 in response to a request to start autonomous driving that autonomous driving has started.

[0050] The rewrite management unit 203 is a functional unit that controls the update process of the software in the execution unit 204 when a module for software update is received from an external server via the communication device 18. Furthermore, when the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021, the rewrite management unit 203 sends an update control command to the execution unit 204 to interrupt a software update if one is in progress. The rewrite management unit 203 is realized, for example, by the communication I / F 108 and the CPU 101 shown in FIG. 2 executing a program.

[0051] The execution unit 204 is a functional unit that starts automatic driving and executes automatic driving control in response to an automatic driving start request from the automatic driving control request unit 2022. The execution unit 204 writes a module for software update to the ROM 103 under the control of the rewrite management unit 203. When the execution unit 204 receives an update control command from the rewrite management unit 203 to interrupt the update while the software is being updated, the execution unit 204 interrupts the write process to the ROM 103 while the software is being updated, and the rewrite management unit 203 controls its own state so as not to start the update. When the software is not being updated, the rewrite management unit 203 controls its own state so as not to start the software update. The execution unit 204 is realized, for example, by the CPU 101 shown in FIG. 2 executing a program. Although one execution unit 204 is shown in FIG. 3, the present invention is not limited to this, and multiple execution units 204 may be provided. In this case, at least one of the execution units 204 starts the autonomous driving and executes the autonomous driving control in response to the autonomous driving start request from the autonomous driving control request unit 2022.

[0052] When the output control unit 205 receives a notification from the notification control unit 2023 that autonomous driving has started, the output control unit 205 at least one of causing the display device 15 to display the notification and causing the speaker 19 to output the notification as audio. The output control unit 205 is realized, for example, by the CPU 101 shown in Fig. 2 executing a program. The display device 15 and the speaker 19 are examples of an "output device".

[0053] Of the display of the notification by the display device 15 and the audio output of the notification by the speaker 19, it is desirable that at least the notification be displayed by the display device 15. While the audio output by the speaker 19 may be overlooked by the driver, the display by the display device 15 can continuously inform the driver of the start of autonomous driving.

[0054] Moreover, each functional unit of the vehicle control device 20 shown in Fig. 3 is shown conceptually, and is not limited to such a configuration. For example, a plurality of functional units illustrated as independent functional units in the vehicle control device 20 shown in Fig. 3 may be configured as one functional unit. On the other hand, a function of one functional unit in the vehicle control device 20 shown in Fig. 3 may be divided into a plurality of functional units and configured as a plurality of functional units.

[0055] In addition, FIG. 3 shows a block configuration in which the vehicle control device 20 is configured by one ECU, but is not limited thereto, and the function of the vehicle control device 20 may be realized by a plurality of ECUs. For example, as shown in FIG. 4, the vehicle control devices 20a to 20c, which are three ECUs, may realize a function equivalent to that of the vehicle control device 20. In the example shown in FIG. 4, the vehicle control devices 20a, 20b, and 20c organically cooperate to configure one control system. In the example shown in FIG. 4, the vehicle control device 20a includes a switch detection unit 201, a control request unit 202, and an output control unit 205, the vehicle control device 20b includes a rewrite management unit 203, and the vehicle control device 20c includes an execution unit 204. The vehicle control devices 20a to 20c transmit and receive data and signals to each other, for example, by CAN (Controller Area Network) communication or the like. It should be noted that the control system is not limited to a system including multiple vehicle control devices, and each of the vehicle control devices 20a to 20c shown in FIG. 4, and one vehicle control device 20 as shown in FIG. 3 are also included in the concept of the control system.

[0056] (Operation flow of the control request unit) Fig. 5 is a flowchart showing an example of an operation flow when switching from manual driving to automatic driving of the control request unit of the vehicle control device according to the first embodiment. Fig. 6 is a flowchart showing an example of an operation flow when switching from automatic driving to manual driving of the control request unit of the vehicle control device according to the first embodiment. First, with reference to Fig. 5, the operation of the control request unit 202 of the vehicle control device 20 when switching from manual driving to automatic driving will be described.

[0057] <Step S11> If the switch detection unit 201 detects a command to switch from manual operation to automatic operation from the automatic operation changeover switch 10b (step S11: Yes), the process proceeds to step S12, and if not (step S11: No), the process waits until a switch command is detected. The command to switch from manual operation to automatic operation corresponds to the "first switch command."

[0058] <Step S12> The suppression request unit 2021 of the control request unit 202 sends an update suppression request for suppressing software updates to the rewrite management unit 203. Then, the process proceeds to step S13.

[0059] <Step S13> If the suppression request unit 2021 receives an affirmative response to the update suppression request from the rewrite management unit 203 indicating that the software update has been suppressed (step S13: Yes), the suppression request unit 2021 proceeds to step S14, and if an affirmative response has not been received (step S13: No), the suppression request unit 2021 waits until an affirmative response is received. The affirmative response to the update suppression request corresponds to a "first response." The first response includes at least one of a response that the rewrite management unit 203 will not start the software update and a response that at least one execution unit 204 has interrupted the software update.

[0060] <Step S14> The automatic driving control request unit 2022 of the vehicle control device 20 sends an automatic driving start request to the execution unit 204 to request the start of automatic driving. Then, the process proceeds to step S15.

[0061] <Step S15> If the autonomous driving control request unit 2022 receives an affirmative response from the execution unit 204 in response to the autonomous driving start request indicating that autonomous driving has started (step S15: Yes), it proceeds to step S16, and if an affirmative response has not been received (step S15: No), it waits until it receives an affirmative response. The affirmative response from the execution unit 204 indicating that autonomous driving has started corresponds to a "second response."

[0062] <Step S16> The notification control unit 2023 of the vehicle control device 20 notifies the output control unit 205 that the autonomous driving has started. Then, the processing of the control request unit 202 ends.

[0063] Through the flow of steps S11 to S16 described above, the control request unit 202 performs the operation for switching from manual operation to automatic operation.

[0064] Next, with reference to FIG. 6, an operation of the control request unit 202 of the vehicle control device 20 when switching from automatic driving to manual driving will be described.

[0065] <Step S21> If the switch detection unit 201 detects a command to switch from automatic operation to manual operation from the automatic operation changeover switch 10b (step S21: Yes), the process proceeds to step S22, and if not (step S21: No), the process waits until a switch command is detected. The command to switch from automatic operation to manual operation corresponds to a "second switch command."

[0066] <Step S22> The autonomous driving control request unit 2022 sends an autonomous driving end request to the execution unit 204 to request the end of autonomous driving. Then, the process proceeds to step S23.

[0067] <Step S23> If the autonomous driving control request unit 2022 receives an affirmative response from the execution unit 204 to the autonomous driving end request indicating that autonomous driving has been ended (step S23: Yes), it proceeds to step S24, and if an affirmative response has not been received (step S23: No), it waits until it receives an affirmative response. The affirmative response from the execution unit 204 indicating that autonomous driving has been ended corresponds to the "fourth response".

[0068] <Step S24> The notification control unit 2023 notifies the output control unit 205 that the autonomous driving has ended. Then, the process proceeds to step S25.

[0069] <Step S25> The suppression request unit 2021 sends an update suppression release request for releasing the suppression of software updates to the rewrite management unit 203. Then, the process proceeds to step S26.

[0070] <Step S26> If the suppression request unit 2021 receives a positive response to the update suppression cancellation request from the rewrite management unit 203 indicating to the execution unit 204 that the software update has been suspended or the suppression of starting the update has been cancelled (step S26: Yes), the suppression request unit 2021 terminates the processing, and if a positive response has not been received (step S26: No), it waits until a positive response is received.

[0071] Through the flow of steps S21 to S26 described above, the control request unit 202 performs the operation for switching from automatic driving to manual driving.

[0072] (Operation flow of rewrite management unit) Fig. 7 is a flowchart showing an example of an operation flow of the rewrite management unit of the vehicle control device according to the first embodiment when switching from manual driving to automatic driving. Fig. 8 is a flowchart showing an example of an operation flow of the rewrite management unit of the vehicle control device according to the first embodiment when switching from automatic driving to manual driving. First, with reference to Fig. 7, the operation of the rewrite management unit 203 of the vehicle control device 20 when switching from manual driving to automatic driving will be described.

[0073] <Step S31> If the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021 (step S31: Yes), the process proceeds to step S32, and if the update suppression request has not been received (step S31: No), the rewrite management unit 203 waits until an update suppression request is received.

[0074] <Step S32> If the rewrite management unit 203 confirms that the software is being updated in the execution unit 204 (step S32: Yes), the process proceeds to step S33, and if the rewrite management unit 203 confirms that the software is not being updated (step S32: No), the process proceeds to step S35.

[0075] <Step S33> The rewrite management unit 203 sends an update control command to the execution unit 204 to interrupt the software update, and then the process proceeds to step S34.

[0076] <Step S34> If the rewrite management unit 203 receives an affirmative response from the execution unit 204 indicating that the software update has been interrupted (step S34: Yes), the rewrite management unit 203 proceeds to step S35, and if the affirmative response has not been received (step S34: No), the rewrite management unit 203 waits until it receives an affirmative response. The affirmative response from the execution unit 204 indicating that the software update has been interrupted corresponds to the "third response."

[0077] <Step S35> The rewrite management unit 203 sets an update flag for internally controlling software updates to the execution unit 204 to "not allowed," and then the process proceeds to step S36.

[0078] <Step S36> The rewrite management unit 203 sends an affirmative response to the update suppression request, indicating that the software update has been suppressed, to the suppression request unit 2021. Then, the processing of the rewrite management unit 203 ends.

[0079] Through the above flow of steps S31 to S36, the rewrite management unit 203 performs the operation for switching from manual operation to automatic operation.

[0080] Next, the operation of the rewrite management unit 203 of the vehicle control device 20 when switching from automatic driving to manual driving will be described with reference to FIG.

[0081] <Step S41> If the rewrite management unit 203 receives an update suppression release request from the suppression request unit 2021 (step S41: Yes), it proceeds to step S42, and if the update suppression release request has not been received (step S41: No), it waits until the update suppression release request is received.

[0082] <Step S42> The rewrite management unit 203 sets an update flag for internally controlling software update to the execution unit 204 to "OK". Since the load of the software update process in the execution unit 204 is large, the temperature of the CPU 101 is expected to rise during the software update process. For example, even if the rewrite management unit 203 receives an update suppression release request, if the internal temperature or the ambient temperature of the vehicle control device 20 acquired from the temperature sensor 21 via the sensor I / F 111 is higher than a predetermined threshold, the rewrite management unit 203 may not start or resume the software update by setting the update flag to "NO". Alternatively, even if the rewrite management unit 203 sets the update flag to "OK", if the internal temperature or the ambient temperature is higher than a predetermined threshold. This makes it possible to suppress the occurrence of malfunctions such as frequency restrictions of the CPU 101 due to the temperature rise caused by the update process of the CPU 101. Specifically, the frequency restrictions are as follows. The CPU 101 may suppress heat generation due to an increase in the amount of processing by lowering the processing frequency. At this time, a decrease in the processing frequency may lead to a decrease in the processing speed of the CPU 101. Then, the process proceeds to step S43.

[0083] <Step S43> The rewrite management unit 203 sends an affirmative response to the update suppression release request, indicating that the software update has been suppressed, to the suppression request unit 2021. Then, the processing of the rewrite management unit 203 ends.

[0084] Through the above flow of steps S41 to S43, the rewrite management unit 203 performs the operation for switching from automatic operation to manual operation.

[0085] (Flow of operations of the execution part) Fig. 9 is a flowchart showing an example of the flow of a software update operation of the execution unit of the vehicle control device according to the first embodiment. Fig. 10 is a flowchart showing an example of the flow of an automatic / manual switching operation of the execution unit of the vehicle control device according to the first embodiment. First, with reference to Fig. 9, the software update operation in the execution unit 204 of the vehicle control device 20 will be described.

[0086] <Step S51> If the execution unit 204 is updating software (step S51: Yes), the process proceeds to step S52, and if the execution unit 204 is not updating software (step S51: No), the process proceeds to step S57.

[0087] <Step S52> If the execution unit 204 receives an automatic driving start request from the automatic driving control request unit 2022 (step S52: Yes), it proceeds to step S53, and if the execution unit 204 has not received an automatic driving start request (step S52: No), it proceeds to step S54.

[0088] <Step S53> Since the software is being updated, the execution unit 204 sends a negative response to the autonomous driving start request, indicating that autonomous driving cannot be started, to the autonomous driving control request unit 2022. Then, the process proceeds to step S54.

[0089] <Step S54> If the execution unit 204 receives an update control command from the rewrite management unit 203 to interrupt the software update (step S54: Yes), it proceeds to step S55, and if it has not received an update control command (step S54: No), it returns to step S52.

[0090] <Step S55> In response to the update control command, the execution unit 204 suspends the process of writing the software to be updated into the ROM 103. Then, the process proceeds to step S56.

[0091] <Step S56> The execution unit 204 sends an affirmative response to the update control command, indicating that the software update has been interrupted, to the rewrite management unit 203. Then, the processing of the execution unit 204 ends.

[0092] <Step S57> If the execution unit 204 is executing an automatic driving process or has received an automatic driving start request or an automatic driving end request from the automatic driving control request unit 2022 (step S57: Yes), the software update process cannot be started or resumed, and the process is terminated. On the other hand, if the execution unit 204 is not executing an automatic driving process and has not received an automatic driving start request or an automatic driving end request from the automatic driving control request unit 2022 (step S57: No), the process proceeds to step S58.

[0093] <Step S58> If the execution unit 204 receives an update control command from the rewrite management unit 203 to start or resume a software update (step S58: Yes), it proceeds to step S59, and if it has not received an update control command (step S58: No), it returns to step S57.

[0094] <Step S59> In response to the update control command, the execution unit 204 starts or resumes the process of writing the software to be updated into the ROM 103. Then, the process proceeds to step S60.

[0095] <Step S60> The execution unit 204 sends an affirmative response to the update control command, which indicates that the software update has been started or resumed, to the rewrite management unit 203. Then, the processing of the execution unit 204 ends.

[0096] Through the above flow of steps S51 to S60, the execution unit 204 starts, resumes, and suspends software update.

[0097] Next, the automatic / manual switching operation in the execution unit 204 of the vehicle control device 20 will be described with reference to FIG.

[0098] <Step S71> If the automatic driving process is not being executed in the execution unit 204 (step S71: No), the process proceeds to step S72, and if the automatic driving process is being executed (step S71: Yes), the process proceeds to step S76.

[0099] <Step S72> If the execution unit 204 is updating software or has received an update control command from the rewrite management unit 203 to start or resume the software update (step S72: Yes), the processing of the execution unit 204 is terminated since the automatic driving process cannot be started until the software update is interrupted. On the other hand, if the execution unit 204 is not updating software and has not received an update control command from the rewrite management unit 203 to start or resume the software update (step S72: No), the process proceeds to step S73.

[0100] <Step S73> If the execution unit 204 receives an automatic driving start request from the automatic driving control request unit 2022 (step S73: Yes), it proceeds to step S74, and if the execution unit 204 has not received an automatic driving start request (step S73: No), it returns to step S72.

[0101] <Step S74> The execution unit 204 starts the automatic driving process, and then the process proceeds to step S75.

[0102] <Step S75> The execution unit 204 sends an affirmative response to the autonomous driving start request, indicating that the autonomous driving process has started, to the autonomous driving control request unit 2022. Then, the process ends.

[0103] <Step S76> If the execution unit 204 receives an update control command from the rewrite management unit 203 to start or resume a software update while the autonomous driving process is being executed (step S76: Yes), it proceeds to step S77, and if the execution unit 204 has not received an update control command (step S76: No), it proceeds to step S78.

[0104] <Step S77> The execution unit 204 determines that software update will not be performed during execution of the autonomous driving process, and sends a negative response to the update control command for starting or resuming software update to the rewrite management unit 203. Then, the process proceeds to step S78.

[0105] <Step S78> If the execution unit 204 receives an autonomous driving end request from the autonomous driving control request unit 2022 (step S78: Yes), it proceeds to step S79, and if the execution unit 204 has not received an autonomous driving end request (step S78: No), it proceeds to step S76.

[0106] <Step S79> The execution unit 204 ends the automatic driving process, and then proceeds to step S80.

[0107] <Step S80> The execution unit 204 sends an affirmative response to the autonomous driving end request, indicating that the autonomous driving process has ended, to the autonomous driving control request unit 2022. Then, the process ends.

[0108] Through the above flow of steps S71 to S80, the execution unit 204 performs the switching operation to automatic operation or manual operation.

[0109] As described above, in the vehicle control device 20 according to the present embodiment, when the switch detection unit 201 detects a switching command, the suppression request unit 2021 sends an update suppression request to the rewrite management unit 203 to suppress the software update. When the suppression request unit 2021 receives a response indicating that the software update has been suppressed from the rewrite management unit 203 in response to the update suppression request, the automatic driving control request unit 2022 sends an automatic driving start request to the execution unit 204. As a result, when the driving state of the vehicle 1 is switched to automatic driving, the update of the software installed in the vehicle control device 20 is interrupted, so that the vehicle 1 can be automatically driven without restricting the function of the current software. In addition, when designing the system, it is not necessary to consider that the software writing process, which is generally infrequent, the processing of the CPU 101 during automatic driving, and the access processing of the RAM 102 and the ROM 103 are performed simultaneously. Therefore, the degree of freedom in system design is improved.

[0110] [Second embodiment] The vehicle control device according to the second embodiment will be described, focusing on the differences from the vehicle control device 20 according to the first embodiment. In the first embodiment, an operation was described in which software update in the vehicle control device is suspended or not started when the driving state of the vehicle 1 is switched to autonomous driving for all software executed in the execution unit 204. In this embodiment, an operation will be described in which the processing of the vehicle control device is made different depending on whether the software executed in the execution unit is related to autonomous driving operation or not.

[0111] (Configuration and operation of functional blocks of vehicle control device) Fig. 11 is a diagram showing an example of the configuration of functional blocks of a vehicle control device according to the second embodiment. The configuration and operation of the functional blocks of the control system according to the present embodiment will be described with reference to Fig. 11.

[0112] In this embodiment, as shown in FIG. 11, vehicle control devices 20a to 20d configure a control system. The vehicle control device 20a has a switch detection unit 201, a control request unit 202, and an output control unit 205. The vehicle control device 20b has a rewrite management unit 203. The vehicle control device 20c has an execution unit 204a. The vehicle control device 20d has an execution unit 204b. Note that the operations of the switch detection unit 201, the control request unit 202, and the output control unit 205 are similar to those described in the first embodiment. In addition, when referring to any vehicle control device among the vehicle control devices 20a to 20d, or when referring to them collectively, they will be simply referred to as "vehicle control device 20".

[0113] The rewrite management unit 203 is a functional unit that controls the update process of the software in the execution unit 204a and the execution unit 204b when a module for software update is received from an external server via the communication device 18. In addition, when the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021, the rewrite management unit 203 sends an update control command to the execution unit 204a that executes the function of the automatic driving operation to interrupt the update when the software is being updated. In addition, when the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021, the rewrite management unit 203 prioritizes the software update for the execution unit 204b that executes functions other than the automatic driving operation. In other words, the rewrite management unit 203 does not cause the execution unit 204b to interrupt the update when the execution unit 204b is updating the software, and does not cause the execution unit 204b to prohibit the update when the software is not being updated. The rewrite management unit 203 is realized, for example, by the communication I / F 108 and the CPU 101 shown in FIG. 2 executing a program.

[0114] The execution unit 204a is a functional unit that is the target of the automatic driving operation, and is a functional unit that starts automatic driving and executes automatic driving control in response to an automatic driving start request from the automatic driving control request unit 2022. The execution unit 204a also writes a module for software update to the ROM 103 under the control of the rewrite management unit 203. When the execution unit 204a receives an update control command from the rewrite management unit 203 to interrupt the update while the software is being updated, the execution unit 204a interrupts the write process to the ROM 103 while the software is being updated, and the rewrite management unit 203 controls its own state so as not to start the update. When the software is not being updated, the rewrite management unit 203 controls its own state so as not to start the software update. That is, the CPU 101 corresponding to the execution unit 204a is a suppression target CPU that is a target for suppressing software update. The execution unit 204a is realized, for example, by the CPU 101 shown in FIG. 2 of the vehicle control device 20c executing a program. The execution unit 204a corresponds to a "first execution unit." 11 shows one execution unit 204a, but is not limited thereto, and multiple execution units 204a may be provided. In this case, at least one of the multiple execution units 204a starts automatic driving and executes automatic driving control in response to an automatic driving start request from the automatic driving control request unit 2022.

[0115] The execution unit 204b is a functional unit that is not subject to the automatic driving operation and executes processing other than the automatic driving processing. The execution unit 204b is a functional unit that realizes, for example, RSE (Rear Seat Entertainment). The execution unit 204b writes a module for software update to the ROM 103 under the control of the rewrite management unit 203. The execution unit 204b continues the write process to the ROM 103 during software update even if the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021. That is, the CPU 101 corresponding to the execution unit 204b is a non-restriction target CPU that is not subject to suppression of software update. The execution unit 204b is realized, for example, by the CPU 101 shown in FIG. 2 of the vehicle control device 20d executing a program. The execution unit 204b corresponds to a "second execution unit." Note that, although one execution unit 204b is shown in FIG. 11, the present invention is not limited to this, and multiple execution units 204b may be provided.

[0116] In addition, when referring to any one of the execution units 204a and 204b, or when referring to them collectively, they will be simply referred to as "execution unit 204".

[0117] In addition, in FIG. 11, execution unit 204a is shown as the execution unit 204 corresponding to the CPU to be inhibited, and execution unit 204b is shown as the execution unit 204 corresponding to the CPU not to be inhibited, but multiple execution units 204 may each correspond to a CPU to be inhibited and a CPU not to be inhibited.

[0118] Moreover, the functional units of the vehicle control devices 20a to 20d shown in Fig. 11 are conceptually shown, and are not limited to such configurations. For example, the multiple functional units exemplified as the vehicle control devices 20a to 20d may be configured as one functional unit. On the other hand, in each of the functional units exemplified as the vehicle control devices 20a to 20d, the function of one functional unit may be divided into multiple parts and configured as multiple functional units.

[0119] Further, the control system configuration shown in FIG. 11 is composed of vehicle control devices 20a to 20d, but is not limited to this and may be composed of one vehicle control device or any other number of vehicle control devices.

[0120] (Operation flow of rewrite management unit) Fig. 12 is a flowchart showing an example of an operation flow of the rewrite management unit of the vehicle control device according to the second embodiment when switching from manual driving to automatic driving. Fig. 13 is a flowchart showing an example of an operation flow of the rewrite management unit of the vehicle control device according to the second embodiment when switching from automatic driving to manual driving. First, with reference to Fig. 12, the operation of the rewrite management unit 203 of the vehicle control device 20b when switching from manual driving to automatic driving will be described.

[0121] <Step S31a> If the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021 (step S31a: Yes), the process proceeds to step S32a. If the update suppression request has not been received (step S31a: No), the rewrite management unit 203 waits until an update suppression request is received.

[0122] <Step S32a> If the rewrite management unit 203 confirms that software is being updated and that there is an execution unit 204 corresponding to a CPU to be suppressed (step S32a: Yes), the process proceeds to step S33a. If it confirms that there is no execution unit 204 in the process of software updating, or that the execution unit 204 corresponds to a CPU that is not to be suppressed even if the software is being updated (step S32a: No), the process proceeds to step S35a.

[0123] <Step S33a> The rewrite management unit 203 sends an update control command for interrupting the software update to the execution unit 204 corresponding to the suppression target CPU during the software update, and then proceeds to step S34a.

[0124] <Step S34a> If the rewrite management unit 203 receives an affirmative response indicating that the software update has been interrupted from the execution unit 204 corresponding to the CPU to be inhibited (step S34a: Yes), the rewrite management unit 203 proceeds to step S35a, and if an affirmative response has not been received (step S34a: No), the rewrite management unit 203 waits until an affirmative response is received. The affirmative response indicating that the software update has been interrupted from the execution unit 204 corresponding to the CPU to be inhibited corresponds to the "third response."

[0125] <Step S35a> The rewrite management unit 203 sets an update flag for internally controlling software updates to the execution unit 204 corresponding to the suppression target CPU to "not allowed," and then proceeds to step S36a.

[0126] <Step S36a> The rewrite management unit 203 sends an affirmative response to the update suppression request, indicating that the software update has been suppressed, to the suppression request unit 2021. Then, the process proceeds to step S37a.

[0127] <Step S37a> If the rewrite management unit 203 confirms that there is an execution unit 204 corresponding to a non-restricted CPU waiting for a software update (step S37a: Yes), it proceeds to step S38a, and if there is no execution unit 204 corresponding to a non-restricted CPU waiting for a software update (step S37a: No), it terminates the processing of the rewrite management unit 203.

[0128] <Step S38a> The rewrite management unit 203 controls the software update process in the execution unit 204 corresponding to the non-restricted CPU, and then the process returns to step S37a.

[0129] Through the above flow of steps S31a to S38a, the rewrite management unit 203 performs the operation for switching from manual operation to automatic operation.

[0130] Next, the operation of the rewrite management unit 203 of the vehicle control device 20b when switching from automatic driving to manual driving will be described with reference to FIG.

[0131] <Step S41a> If the rewrite management unit 203 receives an update suppression release request from the suppression request unit 2021 (step S41a: Yes), it proceeds to step S42a, and if the update suppression release request has not been received (step S41a: No), it waits until it receives an update suppression release request.

[0132] <Step S42a> The rewrite management unit 203 sets an update flag for internally controlling software update to the execution unit 204 corresponding to the suppression target CPU to "OK". As described above, the software update process in the execution unit 204 corresponding to the suppression target CPU has a large load, so that the temperature of the CPU 101 is expected to rise during the software update process. For example, even if the rewrite management unit 203 receives an update suppression release request, if the internal temperature or the ambient temperature of the vehicle control device 20 corresponding to the suppression target CPU acquired from the temperature sensor 21 via the sensor I / F 111 is higher than a predetermined threshold, the rewrite management unit 203 may not start or resume the software update by setting the update flag to "NOT OK". Alternatively, even if the rewrite management unit 203 sets the update flag to "OK", if the internal temperature or the ambient temperature is higher than a predetermined threshold. This makes it possible to suppress the occurrence of malfunctions such as frequency restrictions of the CPU 101 due to the temperature rise caused by the update process of the CPU 101. Then, the process proceeds to step S43a.

[0133] <Step S43a> The rewrite management unit 203 sends an affirmative response to the update suppression cancellation request to the suppression request unit 2021, which indicates that the software update has been suspended or the suppression of the start of the update has been cancelled for the execution unit 204 corresponding to the suppression target CPU. Then, the processing of the rewrite management unit 203 ends.

[0134] Through the above flow of steps S41a to S43a, the rewrite management unit 203 performs the operation for switching from automatic operation to manual operation.

[0135] As described above, in the control system according to the present embodiment, when the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021, it sends an update control command to the execution unit 204a that is the target of software update suppression, and does not send an update control command to the execution unit 204b that is not the target of software update suppression. That is, even if the update suppression request by the suppression request unit 2021 occurs, the software update process for the execution unit 204b continues without interruption. In the execution unit 204a that executes the automatic driving control, if automatic driving and software update are performed simultaneously, the processing load of the execution unit 204a may increase. Therefore, by interrupting the update for the execution unit 204a, automatic driving can be started without increasing the processing load. In addition, in the execution unit 204b that executes procedures other than the automatic driving operation, the processing load does not change whether software update is performed simultaneously with automatic driving or when software update is performed when automatic driving is not performed. Therefore, by not interrupting the update for the execution unit 204b, it is possible to perform a function improvement resulting from the software update without increasing the processing load in the control system.

[0136] [Third embodiment] The vehicle control device according to the third embodiment will be described, focusing on the differences from the vehicle control device 20 according to the first embodiment. In the first embodiment, an operation was described in which software updates are suspended or updates are not started in the vehicle control device for all software executed by the execution unit 204 when the driving state of the vehicle 1 is switched to autonomous driving. In this embodiment, an operation is described in which the processing of the vehicle control device is made different according to the priority order of the software to be updated. Note that the configuration of the functional blocks of the vehicle control device 20 according to this embodiment is assumed to be the same as the configuration of the functional blocks of the vehicle control device 20 according to the first embodiment.

[0137] (Operation flow of the control request unit) Fig. 14 is a flowchart showing an example of an operation flow when switching from manual driving to automatic driving of the control request unit of the vehicle control device according to the third embodiment. With reference to Fig. 14, the operation of the control request unit 202 of the vehicle control device 20 when switching from manual driving to automatic driving will be described.

[0138] <Step S11b> If the switch detection unit 201 detects a command to switch from manual operation to automatic operation from the automatic operation changeover switch 10b (step S11b: Yes), the process proceeds to step S12a, and if not (step S11b: No), the process waits until a switch command is detected. The command to switch from manual operation to automatic operation corresponds to the "first switch command."

[0139] <Step S12b> The suppression request section 2021 of the control request section 202 sends an update suppression request for suppressing software updates to the rewrite management section 203. Then, the process proceeds to step S13b.

[0140] <Step S13b> If the suppression request unit 2021 receives a response to the update suppression request from the rewrite management unit 203 (step S13b: Yes), it proceeds to step S14b, and if a response has not been received (step S13b: No), it waits until a response is received. The positive response to the update suppression request corresponds to a "first response." The first response includes at least one of a response that the rewrite management unit 203 will not start the software update and a response that at least one execution unit 204 has interrupted the software update.

[0141] <Step S14b> If the response that the suppression request unit 2021 receives from the rewrite management unit 203 is an affirmative response indicating that the software update has been suppressed (step S14b: Yes), the process proceeds to step S15b. If the response is a negative response (step S14b: No), the process proceeds to step S18b.

[0142] <Step S15b> The automatic driving control request unit 2022 of the vehicle control device 20 sends an automatic driving start request to the execution unit 204 to request the start of automatic driving. Then, the process proceeds to step S16b.

[0143] <Step S16b> If the autonomous driving control request unit 2022 receives an affirmative response from the execution unit 204 in response to the autonomous driving start request indicating that autonomous driving has started (step S16b: Yes), it proceeds to step S17b, and if an affirmative response has not been received (step S16b: No), it waits until it receives an affirmative response. The affirmative response from the execution unit 204 indicating that autonomous driving has started corresponds to a "second response."

[0144] <Step S17b> The notification control unit 2023 of the vehicle control device 20 notifies the output control unit 205 that the autonomous driving has started. Then, the processing of the control request unit 202 ends.

[0145] <Step S18b> The notification control unit 2023 of the vehicle control device 20 notifies the output control unit 205 that the start of autonomous driving is not possible. Then, the processing of the control request unit 202 ends.

[0146] The operation of the control request unit 202 when switching from automatic driving to manual driving is the same as that in the first embodiment.

[0147] (Operation flow of rewrite management unit) Fig. 15 is a flowchart showing an example of the flow of operations of the rewrite management unit 203 of the vehicle control device 20 when switching from manual driving to automatic driving according to the third embodiment. The operations of the rewrite management unit 203 of the vehicle control device 20 when switching from manual driving to automatic driving will be described with reference to Fig. 15.

[0148] <Step S31b> If the rewrite management unit 203 receives an update suppression request from the suppression request unit 2021 (step S31b: Yes), the process proceeds to step S32b. If the rewrite management unit 203 has not received an update suppression request (step S31b: No), the rewrite management unit 203 waits until an update suppression request is received.

[0149] <Step S32b> If the rewrite management unit 203 determines that the software is being updated in the execution unit 204 (step S32b: Yes), the process proceeds to step S33b, and if the rewrite management unit 203 determines that the software is not being updated (step S32b: No), the process proceeds to step S36b. The rewrite management unit 203 determines that the software is being updated in the execution unit 204 when, for example, communication for software update is being performed between the rewrite management unit 203 and the execution unit 204.

[0150] <Step S33b> When the execution unit 204 determines that software is being updated, the rewrite management unit 203 determines whether the priority of the software being updated is low. For example, if the priority is low (step S33b: Yes), the rewrite management unit 203 proceeds to step S34b, and if the priority is high (step S33b: No), the rewrite management unit 203 proceeds to step S38b. Here, high-priority software is software that needs to be updated urgently, for example, to correct a defect. Low-priority software is software that needs to be updated to improve or add functions, for example.

[0151] <Step S34b> The rewrite management unit 203 sends an update control command to the execution unit 204 to interrupt the software update, and then the process proceeds to step S35b.

[0152] <Step S35b> If the rewrite management unit 203 receives an affirmative response from the execution unit 204 indicating that the software update has been interrupted (step S35b: Yes), the rewrite management unit 203 proceeds to step S36b, and if an affirmative response has not been received (step S35b: No), the rewrite management unit 203 waits until an affirmative response is received. The affirmative response from the execution unit 204 indicating that the software update has been interrupted corresponds to the "third response."

[0153] <Step S36b> The rewrite management unit 203 sets an update flag for internally controlling software updates to the execution unit 204 to "not allowed," and then the process proceeds to step S37b.

[0154] <Step S37b> The rewrite management unit 203 sends an affirmative response to the update suppression request, indicating that the software update has been suppressed, to the suppression request unit 2021. Then, the processing of the rewrite management unit 203 ends.

[0155] <Step S38b> If the priority of the software being updated is high, the rewrite management unit 203 sends a negative response to the update suppression request to the suppression request unit 2021, which disables the execution unit 204 from interrupting the software update or preventing the update from starting. Then, the processing of the rewrite management unit 203 ends.

[0156] As described above, in the vehicle control device 20 according to this embodiment, when the priority of the software to be updated is low, the rewrite management unit 203 sends an update control command to the execution unit 204, and when the priority of the software to be updated is high, the rewrite management unit 203 does not send an update control command to the execution unit 204. By interrupting the update of software with low priority, the vehicle control device 20 can start autonomous driving without increasing the processing load on the execution unit 204. Furthermore, for software with high priority, the vehicle control device 20 can improve functions resulting from software updates by prioritizing the update process.

[0157] The programs executed by the vehicle control device 20 according to each of the above-mentioned embodiments are provided in a state where they are pre-installed in a ROM or the like. The programs executed by the vehicle control device 20 may be provided by recording them in a computer-readable storage medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk) in an installable or executable format. The above-mentioned programs may be provided to the vehicle control device 20 via a network such as the Internet. The programs to be executed by the vehicle control device 20 according to each of the above-mentioned embodiments have a modular configuration including the above-mentioned functional units, and as actual hardware, for example, the CPU 101 reads out and executes the programs from the ROM 103, whereby each of the above-mentioned functional units is loaded onto the RAM 102, which is a main storage device, and each of the above-mentioned functional units is generated on the RAM 102.

[0158] Although each embodiment of the present disclosure has been described, these are presented as examples and are not intended to limit the technical scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, modifications, and combinations can be made without departing from the spirit of the invention. These embodiments are included within the scope and spirit of the invention, as well as within the scope of equivalents of the invention described in the claims. [Explanation of symbols]

[0159] 1 vehicle 2. Body 3, 3F, 3R wheels 4 seats 5 Vehicle drive unit 6, 6a, 6b Imaging section 7, 7L, 7R door mirrors 8. Back Seat 9. Rearview mirror 10a Engine switch 10b Automatic operation changeover switch 11 Handle 12 Shift lever 13 Parking brake 14 Door lock device 15 Display device 16 GPS Sensor 17 Vehicle speed sensor 18 Communication Equipment 19 Speaker 20, 20a to 20d Vehicle control device 21 Temperature Sensor 101 CPU 102 RAM 103 ROM 104 Imaging I / F 105 Display I / F 106 GPS I / F 107 Vehicle speed I / F 108 Communication I / F 109 Audio I / F 110 Input I / F 111 Sensor I / F 112 Bus 201 Switch detection unit 202 Control request section 203 Rewrite Management Department 204, 204a, 204b Executive Division 205 Output control section 2021 Suppression Request Department 2022 Autonomous Driving Control Requirements Division 2023 Notification Control Unit

Claims

1. A detection unit that detects a first switching command that instructs switching to automatic driving; A rewrite management unit that controls software update processing; a suppression request unit that transmits an update suppression request for suppressing the update of the software to the rewrite management unit when the first switching command is detected by the detection unit; an operation control unit that requests at least one execution unit that executes automatic driving control to start automatic driving when the suppression request unit receives a first response indicating that the software update has been suppressed from the rewrite management unit in response to the update suppression request; Equipped with A control system in which, when the rewrite management unit receives the update suppression request, if the software is being updated, it sends an update control command to the at least one execution unit to interrupt the update of the software, and when it receives a third response from the at least one execution unit indicating that the interruption has been completed, it sends the first response to the suppression request unit.

2. The control system according to claim 1 , wherein the first response includes at least one of a response indicating that the rewrite management unit will not start the software update and a response indicating that the software update has been interrupted in the at least one execution unit.

3. The control system according to claim 1 or 2, further comprising an output control unit that, when the driving control unit receives a second response from the at least one execution unit indicating that autonomous driving has started, outputs to an output device that autonomous driving has started.

4. the output device is a display device, The control system according to claim 3 , wherein when the driving control unit receives the second response, the output control unit causes the output device to display a notification that automatic driving has started.

5. The control system according to any one of claims 1 to 4, wherein the detection unit detects the first switching command from an operation unit for switching an operating state.

6. the at least one execution unit includes a first execution unit that executes software that is a target of suppression of updating, and a second execution unit that executes software that is not a target of suppression of updating; A control system as described in any one of claims 1 to 5, wherein when the rewrite management unit receives the update suppression request, if the software to be suppressed from updating is currently being updated, the rewrite management unit sends the update control command to the first execution unit, and does not send the update control command to the second execution unit.

7. A control system as described in any one of claims 1 to 6, wherein when the update suppression request is received, the rewrite management unit sends the update control command to the execution unit if the priority of the software to be updated is low, and does not send the update control command to the execution unit if the priority is high.

8. The detection unit detects a second switching command instructing switching to manual operation, When the second switching command is detected by the detection unit, the driving control unit requests the at least one execution unit to end the automatic driving; when receiving a fourth response from the at least one execution unit indicating that the autonomous driving has been terminated, the suppression request unit sends an update suppression release request to the rewrite management unit to release the suppression of the software update; A control system as described in any one of claims 1 to 7, wherein the rewrite management unit enables at least one execution unit to start or resume a software update, on the condition that the update suppression release request is received.

9. The control system of claim 8, wherein when the rewrite management unit receives a request to cancel the update suppression, the rewrite management unit does not cause the execution unit to start or resume the software update if the ambient temperature detected by a temperature detection unit that detects the ambient temperature is higher than a predetermined threshold value.

10. A detection unit that detects a first switching command that instructs switching to automatic driving; A rewrite management unit that controls software update processing; a suppression request unit that transmits an update suppression request for suppressing the update of the software to the rewrite management unit when the first switching command is detected by the detection unit; an operation control unit that requests at least one execution unit that executes automatic driving control to start automatic driving when the suppression request unit receives a first response indicating that the software update has been suppressed from the rewrite management unit in response to the update suppression request; Equipped with A control device in which, when the rewrite management unit receives the update suppression request, if the software is being updated, it sends an update control command to the at least one execution unit to interrupt the update of the software, and when it receives a third response from the at least one execution unit indicating that the interruption has been completed, it sends the first response to the suppression request unit.

Citation Information

Patent Citations

  • System and method for rewriting program

    JP2006268554A

  • Automatic drive support device and computer program

    JP2017159723A

  • Automatic driving vehicle and program for automatic driving vehicle

    JP2020042850A

  • Software management system for vehicle and vehicle

    JP6569771B2