Center for controlling software updates

The center for controlling software updates in vehicles allows users to impose restrictions on OTA functions through a communication and control unit, addressing the lack of user control in existing OTA systems.

JP7586026B2Active Publication Date: 2024-11-19TOYOTA JIDOSHA KK
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2021129287
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-08-05
Publication Date
2024-11-19
Estimated Expiration
2041-08-05

AI Technical Summary

Technical Problem

Existing software update technologies using OTA do not allow vehicle users or administrators to freely set restrictions on OTA functions.

Method used

A center that controls software updates for vehicle ECUs, which includes a communication section and a control unit that receives update restriction requests from linked information terminals, allowing users to impose restrictions on OTA functions.

Benefits of technology

Enables vehicle users or administrators to restrict or allow OTA functions according to their preferences, providing enhanced control over software updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007586026000001
    Figure 0007586026000001
  • Figure 0007586026000002
    Figure 0007586026000002
  • Figure 0007586026000003
    Figure 0007586026000003
Patent Text Reader

Abstract

To provide a center that controls update of software, which can set a limit to some or all of OTA functions related to the update of the software.SOLUTION: A center for controlling update of software of an electronic control unit mounted on a vehicle, comprises: a communication unit that performs communication with the vehicle; and a control unit that controls update of the software on the basis of an update request from the vehicle. The control unit limits update of the software when there is an update limit request for the vehicle from a predefined first information terminal among information terminals associated with the vehicle.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a center for controlling software updates of electronic control units mounted on vehicles. [Background technology]

[0002] A vehicle is equipped with multiple electronic control units (ECUs) for controlling the operation of the vehicle. Each electronic control unit includes a processor, a temporary storage unit such as a RAM, and a non-volatile memory that is a non-volatile storage unit such as a flash ROM, and the processor executes software stored in the non-volatile memory to realize the control functions of the electronic control unit. The software stored in each electronic control unit is rewritable, and by updating the software to a newer version, it is possible to improve the functions of each electronic control unit or add new vehicle control functions.

[0003] As a technology for updating software in an electronic control unit, there is known an OTA (Over The Air) technology, in which an in-vehicle communication device connected to an in-vehicle network is wirelessly connected to a communication network such as the Internet, and a device responsible for updating the software in the vehicle downloads software from a server via wireless communication, writes and installs the downloaded software in the electronic control unit, and activates the installed software, thereby updating or adding software to the electronic control unit. For example, see Patent Document 1. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2017-149323 A Summary of the Invention [Problem to be solved by the invention]

[0005] In software updates using OTA, the OTA functions for software updates are uniformly provided by the center to all vehicle users and administrators, etc. For this reason, even if they wanted to impose restrictions on some or all of the OTA functions, vehicle users and administrators were not able to freely impose restrictions.

[0006] The present disclosure has been made in consideration of the above-mentioned problems, and aims to provide a center for controlling software updates that can impose restrictions on some or all of the OTA functions related to software updates. [Means for solving the problem]

[0007] In order to solve the above problems, one aspect of the disclosed technology is a center that controls software updates of an electronic control unit installed in a vehicle, and includes a communication unit that communicates with the vehicle, and a control unit that controls the software update based on an update request from the vehicle, and the control unit is a center that restricts the software update when an update restriction request is made to the vehicle from a predetermined first information terminal among information terminals linked to the vehicle. Effect of the Invention

[0008] According to the center of the present disclosure, a user or administrator of a vehicle that has a first information terminal can impose restrictions on some or all of the OTA functions related to software updates. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing an overall configuration of a network system according to an embodiment; [Diagram 2] Block diagram showing the general configuration of the center [Diagram 3] Center functional block diagram [Figure 4] Block diagram showing the schematic configuration of the OTA master [Diagram 5]OTA Master Functional Block Diagram [Figure 6] Flowchart of the process of adding an information terminal for which authority is to be set to the system [Figure 7A] Flowchart of OTA function restriction process for software updates [Figure 7B] Flowchart of OTA function restriction process for software updates DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] According to the present disclosure, a center that controls software updates for an electronic control unit mounted on a vehicle restricts software updates when a request for restricting updates is received from a specific information terminal among the information terminals linked to the vehicle. This allows a user or administrator of the vehicle who owns the specific information terminal to restrict some or all of the OTA functions related to software updates. Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the drawings.

[0011] <Embodiment> [System Configuration] Fig. 1 is a block diagram showing an overall configuration of a network system according to an embodiment of the present disclosure. The network system shown in Fig. 1 is a system for updating software of a plurality of electronic control units (ECUs) 50a to 50d mounted on a vehicle, and includes a center 10 located outside the vehicle, an in-vehicle network 90 built in the vehicle, and an information terminal 95 linked to the vehicle.

[0012] (1) Center The center 10 can communicate with an OTA master 30 (described later) provided in the in-vehicle network 90 via the network 100, and can control and manage software updates of the multiple electronic control units 50a-50d connected to the OTA master 30 by sending notifications to vehicle users and managers that software updates are available and explanations about the software updates, sending update data for the software of the electronic control units 50a-50d and information defining the procedure of the update process, and receiving notifications indicating the progress of the software update process. This center 10 has a function as a so-called server.

[0013] FIG. 2 is a block diagram showing a schematic configuration of the center 10 in FIG. 1. As shown in FIG. 2, the center 10 includes a central processing unit (CPU) 11, a random access memory (RAM) 12, a storage device 13, and a communication device 14. The storage device 13 is a device including a readable and writable storage medium such as a hard disk drive (HDD) or a solid state drive (SSD), and stores a program for performing software update management, information used for software update control and update management, and software update data for each electronic control unit. In the center 10, the CPU 11 executes a program read from the storage device 13 by using the RAM 12 as a working area, thereby performing a predetermined process related to software update. The communication device 14 is a device for communicating with the OTA master 30 via the network 100.

[0014] Fig. 3 is a functional block diagram of the center 10 shown in Fig. 2. The center 10 shown in Fig. 3 includes a storage unit 16, a communication unit 17, and a control unit 18. The storage unit 16 is realized by the storage device 13 shown in Fig. 2. The communication unit 17 and the control unit 18 are realized by the CPU 11 shown in Fig. 2 executing a program stored in the storage device 13 using the RAM 12.

[0015] The storage unit 16 stores information related to software update processing of one or more electronic control units mounted on the vehicle. As the information related to the software update processing, the storage unit 16 stores at least update management information in which information indicating software available in the electronic control units 50a to 50d is associated with each vehicle identification information (vehicle ID) that identifies the vehicle, and update data of the software of the electronic control units 50a to 50d. As the information indicating the software available in the electronic control units 50a to 50d, for example, a combination of the latest version information of each software of the multiple electronic control units 50a to 50d is defined. As the information related to the software update processing, the storage unit 16 can store an update status indicating an update state of the software being performed in the vehicle. Also, as the information related to the software update processing, the storage unit 16 can store information related to an update sequence indicating a procedure of the software update processing for issuing a control instruction to the OTA master 30. Also, the storage unit 16 can store information related to the restriction of the OTA function related to the software update acquired from the authority controller 70 of the vehicle, which will be described later.

[0016] The communication unit 17 functions as a transmitting unit and a receiving unit that transmits and receives data, information, notifications, requests, and the like between the OTA master 30 (vehicle) and the information terminal 95. The communication unit 17 receives a software update confirmation request from the OTA master 30 (receiving unit). The update confirmation request is information transmitted from the OTA master 30 to the center 10 when, for example, the power supply or ignition is turned on in the vehicle (hereinafter referred to as "power ON"), and is information for requesting the center 10 to confirm whether or not there is update data for the electronic control units 50a to 50d based on vehicle configuration information described later. In addition, in response to the update confirmation request received from the OTA master 30, the communication unit 17 transmits information indicating the presence or absence of update data to the OTA master 30 (transmitting unit). In addition, the communication unit 17 receives a transmission request (download request) for a distribution package from the OTA master 30 (receiving unit). Furthermore, when the communication unit 17 receives a download request for a distribution package (reception unit), it transmits a distribution package including software update data for the electronic control units 50a to 50d generated by the control unit 18 described below to the OTA master 30 (transmission unit). Furthermore, the communication unit 17 receives information regarding the presence or absence of an update restriction request and an update restriction release request from the vehicle (reception unit), and information regarding the authority of the OTA function related to software update for the information terminal linked to the vehicle. Furthermore, the communication unit 17 notifies the vehicle of restrictions on the OTA function related to software update based on the update restriction request and the update restriction release request (transmission unit).

[0017] When the communication unit 17 receives an update check request from the OTA master 30, the control unit 18 determines whether or not there is software update data for the electronic control units 50a to 50d mounted on the vehicle identified by the vehicle ID included in the update check request, based on the update management information stored in the storage unit 16. The determination result by the control unit 18 as to whether or not there is update data is transmitted to the OTA master 30 by the communication unit 17. When the control unit 18 determines that there is software update data for the electronic control units 50a to 50d, and receives a download request for a distribution package from the OTA master 30, the control unit 18 generates one or more distribution packages including the corresponding update data stored in the storage unit 16. Furthermore, when a specific information terminal (described later) among the information terminals 95 linked to the vehicle issues an update restriction request to the vehicle, the control unit 18 restricts the software update of the electronic control units 50a to 50d.

[0018] (2) Information terminal The information terminal 95 is a device such as a smartphone or a personal computer owned by a user or manager of the vehicle. This information terminal 95 is linked to the vehicle by, for example, registering and managing unique information (such as a terminal ID) in the vehicle. The number of information terminals 95 linked to the vehicle is not limited to one, and may be multiple. The information terminal 95 of this embodiment is provided with at least one information terminal 95 (hereinafter referred to as an "authority management information terminal 95") for managing the authority of the OTA function related to software update. One or more information terminals 95 can communicate with the authority control device 70 provided in the vehicle, and can restrict the OTA function related to software update in cooperation with the authority control device 70. The authority management information terminal 95 can determine which information terminal 95 is to be given the authority to restrict the OTA function related to software update.

[0019] (3) In-vehicle network The in-vehicle network 90 includes an OTA master 30, a plurality of electronic control units 50a to 50d, an authority control device 70, and a communication module 80. The OTA master 30 and the communication module 80 are connected via a bus 60a. The OTA master 30 and the electronic control units 50a and 50b are connected via a bus 60b. The OTA master 30 and the electronic control units 50c and 50d are connected via a bus 60c. The OTA master 30 and the authority control device 70 are connected via a bus 60d.

[0020] The OTA master 30 can communicate wirelessly with the center 10 via the bus 60a and the communication module 80 and the network 100. The OTA master 30 can also communicate wired with the electronic control units 50a to 50d and the authorized controller 70 via the buses 60b to 60d. The OTA master 30 is a device having a function of managing an OTA state, controlling an update sequence, which is a flow of a software update process, and performing a software update of an electronic control unit to be updated (hereinafter referred to as a "target electronic control unit"). The OTA master 30 controls software update of the target electronic control unit among the electronic control units 50a to 50d based on update data acquired from the center 10. The OTA master 30 can also control an appropriate screen display on a predetermined display device based on information and notifications related to software updates received from the center 10. The OTA master 30 may also be called a central gateway (CGW).

[0021] 4 is a block diagram showing a schematic configuration of the OTA master 30 in FIG. 1. As shown in FIG. 4, the OTA master 30 includes a CPU 31, a RAM 32, a ROM (Read-Only Memory) 33, a storage device 34, and a communication device 36. The CPU 31, the RAM 32, the ROM 33, and the storage device 34 constitute a microcomputer 35. In the OTA master 30, the CPU 31 executes a program read from the ROM 33 by using the RAM 32 as a working area, thereby executing a predetermined process related to software update. The communication device 36 is a device for communicating with the communication module 80, the electronic control units 50a to 50d, and the authority controller 70, respectively, via the buses 60a to 60d shown in FIG. 1.

[0022] Fig. 5 is a functional block diagram of the OTA master 30 shown in Fig. 4. The OTA master 30 shown in Fig. 5 includes a storage unit 37, a communication unit 38, and a control unit 39. The storage unit 37 is realized by the storage device 34 shown in Fig. 4. The communication unit 38 and the control unit 39 are realized by the CPU 31 shown in Fig. 4 executing a program stored in the ROM 33 using the RAM 32.

[0023] The storage unit 37 stores a program for executing software updates of the multiple electronic control units 50a to 50d (a control program for the OTA master 30), various data used when executing the software updates, and software update data downloaded from the center 10. The storage unit 37 can also store information regarding the type of non-volatile memory mounted in each of the multiple electronic control units 50a to 50d.

[0024] The communication unit 38 functions as a transmitting unit and a receiving unit that transmits and receives data, information, notifications, requests, and the like to and from the center 10. The communication unit 38 transmits a software update check request to the center 10, for example, when the power of the vehicle is turned on (transmitting unit). The update check request includes, for example, a vehicle ID for identifying the vehicle and information on the current version of the software of the electronic control units 50a to 50d connected to the in-vehicle network 90. ​​The vehicle ID and the current version of the software of the electronic control units 50a to 50d are used to determine whether or not there is update data for the software of the electronic control units 50a to 50d by comparing them with the latest version of the software held by the center 10 for each vehicle ID. In addition, the communication unit 38 receives a notification indicating the presence or absence of update data from the center 10 as a response to the update check request (receiving unit). When there is update data for the software of the electronic control units 50a-50d, the communication unit 38 transmits a download request for a distribution package including the software update data and the like to the center 10 (transmission unit), and receives (downloads) the distribution package transmitted from the center 10 (reception unit). The communication unit 38 also transmits the update status of the software transmitted by the electronic control units 50a-50d to the center 10 (transmission unit). Based on an instruction from the control unit 39, the communication unit 38 can display information related to the software update, a notification related to the transmission of the information, and the update status of the software on a display device.

[0025] The control unit 39 judges whether or not there is update data for the software of the electronic control units 50a to 50d, based on a response from the center 10 to the update confirmation request received by the communication unit 38. The control unit 39 also verifies the authenticity of the update data that the communication unit 38 receives (downloads) from the center 10 in a distribution package and stores in the storage unit 37. The control unit 39 also uses the update data downloaded from the center 10 to control the software update process (installation, activation, etc.) of the electronic control units 50a to 50d. Specifically, the control unit 39 transfers the downloaded update data to the target electronic control unit, and causes the target electronic control unit to install update software based on the update data. After the installation is completed, the control unit 39 instructs the target electronic control unit to activate the installed update software. During the software update process, the control unit 39 restricts and executes the software update based on an update restriction request from the information terminal 95 instructed by the center 10.

[0026] The electronic control units 50a to 50d are devices (ECUs) for controlling the operation of each part of the vehicle. Although an example in which the in-vehicle network 90 includes four electronic control units 50a to 50d is shown in Fig. 1, the number of electronic control units is not particularly limited. In addition, the number of buses connecting the electronic control units 50a to 50d to the OTA master 30 is not particularly limited.

[0027] The authority control device 70 is a device that can manage / determine the authority of the OTA function related to software update. The authority control device 70 can be a display device (HMI) such as a car navigation system that can perform various displays such as displaying the presence of update data during software update processing of the electronic control units 50a to 50d, displaying an explanation of the software update, displaying a consent request screen for requesting consent to the software update from the vehicle user or administrator, and displaying the result or status of the software update. In this embodiment, the authority control device 70 communicates with the center 10 and the information terminal 95 via the OTA master 30, but the authority control device 70 may communicate directly from the communication module 80 without the OTA master 30, or directly via another communication device (DCM, smartphone, etc.) not shown in the figure instead of the communication module 80. In addition to the authority control device 70, an electronic control unit or the like may be further connected to the bus 60d shown in FIG. 1.

[0028] Examples of the authority of the OTA function related to software update managed by the authority control device 70 include whether to notify the contents of the software update by OTA [update notification restriction], to what extent (download, installation, activation) the execution of the software update process by OTA is restricted or permitted [update execution restriction], and which functions of the functions to be updated (entertainment system, driving control system, brake system, etc.) are enabled [function selection]. Which of these OTA functions is enabled / disabled is set in advance by the information terminal 95 that has been granted the authority. As a setting method, examples include selectively displaying items related to restrictions on the display screen of the authority control device 70 and having the owner of the information terminal 95 select an item. The contents of the authority of the set OTA function are linked to the individual information (ID) of the information terminal 95 and managed by the authority control device 70 (and the center 10).

[0029] The communication module 80 is a unit having a function of controlling communication between the center 10 and the vehicle, and is a communication device for connecting the in-vehicle network 90 to the center 10 and the information terminal 95. The communication module 80 is wirelessly connected to the center 10 via the network 100, and performs vehicle authentication by the OTA master 30, downloading update data, and the like. This communication module 80 may be configured as being included in the OTA master 30.

[0030] [Software update process overview] The OTA master 30 transmits a software update check request to the center 10, for example, when the power supply of the vehicle is turned on. The update check request includes a vehicle ID for identifying the vehicle, and vehicle configuration information, which is information on the state (system configuration) of the electronic control units 50a to 50d connected to the in-vehicle network 90, such as the current versions of the hardware and software of the electronic control units 50a to 50d. The vehicle configuration information can be created by acquiring the identification numbers (ECU_ID) of the electronic control units and the identification numbers (ECU_Software_ID) of the software versions of the electronic control units from the electronic control units 50a to 50d connected to the in-vehicle network 90. ​​The vehicle ID and the current versions of the software of the electronic control units 50a to 50d are used to determine whether or not there is update data for the software of the electronic control units 50a to 50d by comparing them with the latest version of the software held by the center 10 for each vehicle ID. In response to the update check request received from the OTA master 30, the center 10 transmits to the OTA master 30 a notification indicating the presence or absence of update data, information on software updates, and the like. When there is update data for the software of the electronic control units 50a to 50d, the OTA master 30 transmits a download request for a distribution package to the center 10. Furthermore, the OTA master 30 transmits to the center 10, as necessary, the authority of the OTA function related to the software update based on the update restriction request / update restriction release request from the information terminal 95. The center 10 transmits a distribution package including the update data and the like to the OTA master 30 based on the download request and the authority of the OTA function related to the software update received from the OTA master 30. In addition to the update data, the distribution package may include verification data for verifying the authenticity of the update data, the number and type information of the update data, various control information used during the software update, and the like.

[0031] The OTA master 30 judges whether there is update data for the software of the electronic control units 50a to 50d based on the response to the update confirmation request received from the center 10. The OTA master 30 also verifies the authenticity of the distribution package received from the center 10 and stored in the storage device 13. The OTA master 30 also transfers the update data downloaded in the distribution package to the target electronic control unit based on the contents notified from the center 10 according to the authority of the OTA function related to software update, and causes the target electronic control unit to install the update data. After the installation is completed, the OTA master 30 instructs the target electronic control unit to activate the installed updated software to make it valid.

[0032] In addition, in the consent request process, the center 10 causes the output device to output information explaining the software update, a notification that consent is required for the software update, and a notification prompting input that the software update has been consented to, in accordance with the authority of the OTA function related to the software update. An authority control device provided in the in-vehicle network 90 can be used as the output device. For example, in the consent request process, if information that should be explained in advance to the user or administrator of the vehicle can be displayed on the screen of the authority control device 70, the authority control device 70 is used as the output device. When the authority control device 70 is used as the output device, the OTA master 30 can cause the authority control device 70 to display information regarding the software update, a consent request screen for requesting consent to the software update from the user or administrator, a notification prompting a specific input operation such as pressing an consent button if the user or administrator consents, and the like. When the center 10 receives input of consent from the user or administrator via the OTA master 30, it instructs the OTA master 30 to execute the above-mentioned installation and activation control processes in accordance with the authority of the OTA function related to software updates, and updates the software of the target electronic control unit.

[0033] Here, if the non-volatile memory of the target electronic control unit is a single bank memory having one storage area for storing data such as software, in principle, installation and activation are performed consecutively, so consent request processing for software update is performed before installation is performed. Note that even if the target electronic control unit is a single bank memory, depending on the information on the update sequence instructed by the center 10, it may be requested to temporarily stop the update processing in the state where installation is completed, that is, to suspend (standby) activation. Also, if the non-volatile memory of the target electronic control unit is a dual bank memory having two storage areas for storing data such as software, consent request processing for software update is performed at least after installation is performed and before activation is performed. Note that if the non-volatile memory of the target electronic control unit is a dual bank memory, consent request processing for software update before installation may be performed or may be omitted.

[0034] The software update process consists of a phase in which the OTA master 30 downloads update data from the center 10 (download phase), a phase in which the OTA master 30 transfers the downloaded update data to the target electronic control unit and installs update software based on the update data in the storage area of ​​the target electronic control unit (installation phase), and a phase in which the target electronic control unit activates the installed update software (activation phase).

[0035] Downloading is a process in which the OTA master 30 receives update data for updating the software of the electronic control unit, which is transmitted from the center 10 in a distribution package, and stores the data in the storage unit 37. When receiving update data by downloading, the download phase not only executes the download, but also includes control of a series of processes related to the download, such as determining whether the download can be executed and verifying the update data.

[0036] The update data transmitted from the center 10 to the OTA master 30 may include update software for the electronic control unit (all data or difference data), compressed data obtained by compressing the update software, or divided data obtained by dividing the update software or the compressed data. The update data may also include the ECU_ID (or serial number) of the target electronic control unit and the ECU_Software_ID of the target electronic control unit before the update. The update data is downloaded as the above-mentioned distribution package, and the distribution package includes update data for a single electronic control unit or multiple electronic control units.

[0037] The installation is a process in which the OTA master 30 writes update software (an updated program) into the non-volatile memory of the target electronic control unit based on the update data downloaded from the center 10. The installation phase not only executes the installation, but also includes control of a series of processes related to the installation, such as judging whether the installation can be executed, transferring the update data, and verifying the update software.

[0038] If the update data includes the update software itself (all data), the OTA master 30 transfers the update data (update software) to the target electronic control unit in the installation phase. If the update data includes compressed data, difference data, or divided data of the update software, the OTA master 30 may transfer the update data to the target electronic control unit and the target electronic control unit may generate the update software from the update data, or the OTA master 30 may generate the update software from the update data and then transfer the update software to the target electronic control unit. Here, the update software can be generated by decompressing the compressed data or assembling (integrating) the difference data or divided data.

[0039] The target electronic control unit can install the update software based on an installation request from the OTA master 30. Note that for a specific target electronic control unit that has received the update data, the installation may be performed autonomously without receiving an explicit instruction from the OTA master 30.

[0040] Activation is a process in which the target electronic control unit activates the update software installed in its own non-volatile memory. The activation phase includes not only the execution of activation, but also a series of controls related to activation, such as judging whether activation can be executed, requesting the vehicle user or administrator to consent to activation, and verifying the execution result.

[0041] The activation of the update software can be performed by the target electronic control unit based on an activation request from the OTA master 30. Note that, for a specific target electronic control unit that has received the update data, the activation may be performed autonomously after the installation is completed, without receiving an explicit instruction from the OTA master 30.

[0042] The software update process can be performed consecutively or in parallel for each of the multiple target electronic control units.

[0043] Furthermore, in this specification, the "software update process" includes not only a process in which download, installation, and activation are all performed consecutively, but also a process in which only some of the download, installation, and activation are performed.

[0044] [process] Next, with further reference to FIGS. 6, 7A, and 7B, the software update process executed in the network system of this embodiment will be described.

[0045] FIG. 6 is a flowchart for explaining an example of a process in which the authority management information terminal 95 adds an information terminal 95 that grants authority for the OTA function related to software update to the network system.

[0046] (Step S601) The authority management information terminal 95 communicates with the authority control device 70 (authentication, cooperation) and transitions the authority control device 70 from normal mode to authority management mode. The normal mode refers to a state in which the OTA function related to software update can be restricted based on an update restriction request and an update restriction release request received from the information terminal 95. The authority management mode refers to a state in which the authority of the OTA function related to software update can be set. When the authority control device 70 transitions to the authority management mode, the process proceeds to step S602.

[0047] (Step S602) The authority management information terminal 95 communicates (authenticates, cooperates) with the authority control device 70 with the information terminal 95 that is newly permitted to be granted authority for the OTA function related to software update, and adds this information terminal 95 as a "first information terminal" having authority for the OTA function related to software update. When the first information terminal 95 is added, the process proceeds to step S603.

[0048] (Step S603) The authority control device 70 sets the authority of the OTA function related to software update in the newly added first information terminal 95. The authority to be set may be set by the authority management information terminal 95, or may be set by the newly added first information terminal 95 itself. The contents of the set authority are registered in association with unique information of the first information terminal 95 (such as a terminal ID), and are managed by the authority control device 70 and / or the center 10. When the authority of the OTA function related to software update of the newly added first information terminal 95 is set, the process proceeds to step S604.

[0049] (Step S604) The authority management information terminal 95 switches the authority control device 70 from the authority management mode to the normal mode. When the authority control device 70 switches to the normal mode, this process ends.

[0050] 7A and 7B are flowcharts for explaining the procedure of a process for restricting a part or all of the OTA functions related to software updates performed by the center 10 and the authority controller 70. The process of FIG. 7A and the process of FIG. 7B are connected by connectors X, Y, and Z.

[0051] (Step S701) The center 10 judges whether or not there is software in the vehicle that needs to be updated. This judgment can be made based on, for example, the current version of the software in each of the electronic control units 50a to 50d mounted on the vehicle obtained from the vehicle configuration information included in the update confirmation request transmitted from the OTA master 30, and the latest version of each piece of software stored in the storage unit 16 of the center 10. If there is software in the target vehicle that needs to be updated (step S701, Yes), the process proceeds to step S702. On the other hand, if there is no software in the target vehicle that needs to be updated (step S701, No), this process ends.

[0052] (Step S702) The authority control device 70 judges whether or not an update restriction request has been received from the information terminal 95. That is, the authority control device 70 judges whether or not an update restriction request has been received from the first information terminal to which the authority to restrict a part or all of the OTA functions related to software updates has been granted. For example, the driver may get in the vehicle while carrying the information terminal 95 in which the OTA function restriction has been set, and the information terminal 95 and the authority control device 70 may cooperate (such as Bluetooth (registered trademark)) to allow the authority control device 70 to receive the update restriction request. If there is an update restriction request from the first information terminal 95 (step S702, Yes), the process proceeds to step S703. On the other hand, if there is no update restriction request from the first information terminal 95 (step S702, No), the process proceeds to step S707.

[0053] (Step S703) The authority control device 70 determines whether or not authentication of the first information terminal 95, which is the information terminal 95 for which the update restriction request was made, has been successful. If authentication of the first information terminal 95 has been successful (step S703, Yes), the process proceeds to step S704. The successful authentication of the first information terminal 95 (and the OTA function that is restricted as necessary) is notified to the center 10. On the other hand, if authentication of the first information terminal 95 has failed (step S703, No), the process proceeds to step S702.

[0054] (Step S704) The center 10 restricts and executes the software update process (transmission, instruction, notification, permission, etc.) based on the update restriction request received from the first information terminal 95 that has been successfully authenticated by the authority control device 70. For example, if the restriction on the update process based on the update restriction request is "prohibit software installation," the center 10 executes the processes (notification, transmission, etc.) required until the vehicle downloads the update software. When the software update is restricted and executed, the process proceeds to step S705.

[0055] (Step S705) The authority control device 70 judges whether or not an update restriction release request has been received from the information terminal 95. That is, the authority control device 70 judges whether or not an update restriction release request has been received from a first information terminal to which authority has been granted to restrict a part or all of the OTA functions related to software updates. This update restriction release request can be made not only by the first information terminal 95 that has sent the update restriction request, but also by an information terminal other than the information terminal 95 that has sent the update restriction request, or by the authority management information terminal 95. If there is an update restriction release request from the information terminal 95 (step S705, Yes), the process proceeds to step S706. On the other hand, if there is no update restriction release request from the information terminal 95 (step S706, No), the process proceeds to step S705.

[0056] (Step S706) The authority control device 70 judges whether or not authentication of the information terminal 95 that has requested the release of the update restriction has been successful. If authentication of the information terminal 95 has been successful (step S706, YES), the process proceeds to step S707. The center 10 is notified of the success of authentication of this information terminal 95. On the other hand, if authentication of the information terminal 95 has failed (step S706, NO), the process proceeds to step S705.

[0057] (Step S707) The center 10 performs the necessary processing (notification, transmission, etc.) to release the restriction and execute the software update based on the update restriction release request from the information terminal 95 that has been successfully authenticated by the authority control device 70. When the restriction is released and the software update is executed, this processing ends.

[0058] <Actions and Effects> As described above, according to the embodiment of the present disclosure, the center for controlling software updates of the electronic control unit mounted on the vehicle restricts software updates in the vehicle when an update restriction request is received from a specific information terminal for which authority has been set in advance among the information terminals linked to the vehicle. This process allows a user or administrator of the vehicle who owns the specific information terminal to restrict a part or all of the OTA functions related to software updates.

[0059] Although one embodiment of the disclosed technology has been described above, the present disclosure can be understood not only as a center, but also as a method executed by a center equipped with a processor and memory, a program, a computer-readable non-transitory storage medium storing a program, an OTA master capable of communicating with a center, or a vehicle equipped with an OTA master, etc. [Industrial Applicability]

[0060] The disclosed technique can be used in a center that controls software updates for electronic control units mounted on vehicles. [Explanation of symbols]

[0061] 10 Center 11, 31 CPU 12,32 RAM 13, 34 Storage device 14, 36 Communication equipment 16, 37 Memory section 17, 38 Communications Department 18, 39 Control section 30 OTA Master 33 ROM 35 Microcomputer 50a~50d Electronic Control Unit (ECU) 60a~60d Bus 70 Display device 80 Communication Module 90 In-vehicle network 95 Information terminal 100 Network

Claims

[Claim 1] A center for controlling software updates of an electronic control unit mounted on a vehicle, comprising: A communication unit that communicates with the vehicle; a control unit that controls the software update based on an update request from the vehicle, The control unit restricts the software update when an update restriction request is made to the vehicle from a predetermined first information terminal among information terminals linked to the vehicle.

Citation Information

Patent Citations

  • Software developing kit, printer system, and firmware update setting method

    JP2017041167A

  • Software update apparatus

    JP2017097620A

  • Vehicle control system

    JP2017149323A

  • Software managing system, and managing server, for wheeled vehicles, and wheeled vehicle

    JP2017167646A

  • Program update system, program update method, and program

    JP2019125141A