Software component management device, software component management system, and software component management method

Abstract

Provided is a management device (13) that manages, in accordance with vehicle functions realized by an electronic control unit (5) mounted on a vehicle (3), software components (51 to 53) used in combination in the electronic control unit. The management device includes a first distribution unit (131) and a second distribution unit (132). The first distribution unit distributes the latest version of a software component corresponding to a function that is not implemented in a vehicle, to all vehicles mounted with an electronic control unit that realizes the function. The software component distributed by the first distribution unit includes a first configuration file that disables software. The second distribution unit distributes, on the basis of a request to implement a specific function, which is not implemented in a specific vehicle, into the specific vehicle, a second configuration file that enables the software of the latest version of the software component corresponding to the specific function.

Description

Software Component Management Device, Software Component Management System, and Software Component Management Method

[0001] The present invention relates to a software component management device, a software component management system, and a software component management method.

[0002] In Patent Document 1, a method for updating software used in an electronic control unit (ECU: Electronic Control Unit) that controls the operation of a vehicle is proposed. In this method, for ECUs grouped by vehicle function unit, the version of the software actually used in the ECU is compared with the version of the software managed by the server at the center as the software currently in use in the ECU. When the software currently in use in the ECU is older than the software managed by the server, the older version of the software in the ECU is updated to the new version of the software. In the method described in Patent Document 1, OTA (Over The Air) technology is used for updating the software of the ECU.

[0003] Japanese Patent Application Laid-Open No. 2022-175460

[0004] For example, when updating the software of an ECU related to an added function by OTA technology to add a vehicle function, it is necessary to perform on-vehicle diagnosis for quality assurance of operating the updated software in combination with the software of other ECUs. Also, on the center side, it is necessary to manage and operate off-vehicle the version of the software of the ECU updated on the vehicle side as the software currently in use in the ECU. These diagnoses, management, and operations require corresponding man-hours regardless of whether they are on-vehicle or off-vehicle.

[0005] The present invention has been made in view of the above circumstances, and an object of the present invention is to reduce the man-hours required when adding a vehicle function when updating software by OTA technology.

[0006] One aspect of the present invention that solves the above-mentioned problems provides a device for managing software components used in combination in an electronic control unit, corresponding to the functions of a vehicle realized by the electronic control unit mounted on the vehicle. The software component management device according to this aspect comprises a first distribution unit and a second distribution unit. The first distribution unit distributes the latest version of the software component corresponding to a function not implemented in the vehicle to all vehicles equipped with an electronic control unit that realizes the function not implemented in the vehicle. The software component distributed by the first distribution unit includes a first configuration file that disables the software. The second distribution unit distributes a second configuration file to a specific vehicle that enables the software of the latest version of the software component corresponding to a specific function, based on a request to implement a specific function not implemented in that specific vehicle.

[0007] According to the present invention, when updating software using OTA technology, it is possible to reduce the man-hours required to add vehicle functions.

[0008] Figure 1 is a diagram showing an example configuration of a software component management system according to the embodiment. Figure 2 is a sequence diagram showing an example of the processing procedure when purchasing a specific function in the management system of Figure 1. Figure 3 is a diagram showing the changes in the version and state of the software component when adding vehicle functions to the management system according to the comparative example. Figure 4 is a diagram showing the changes in the version and state of the software component when adding vehicle functions to the management system according to the embodiment.

[0009] Embodiments and modifications thereof of the present invention will be described below with reference to the drawings. In the drawings, the same parts are denoted by the same reference numerals and their descriptions are omitted. The software component management system 1 of the embodiment shown in Figure 1 manages the software components used in the electronic control unit 5 mounted on the vehicle 3. The software components are used in combination, for example, in the electronic control unit 5 that realizes the functions of the vehicle 3, corresponding to the functions of the vehicle 3. Hereinafter, the software component management system 1 will be abbreviated as management system 1. Although two vehicles 3 are shown in Figure 1, one management system 1 manages the software components of the electronic control unit 5 in one vehicle 3 or three or more vehicles 3. In each vehicle 3, the electronic control unit 5 is connected to an in-vehicle network 7. In Figure 1, each vehicle 3 has one electronic control unit 5, but a vehicle 3 may have multiple electronic control units 5, and the number of electronic control units 5 may differ from vehicle 3 to vehicle 3. The electronic control unit 5 is sometimes called an ECU (Electronic Control Unit). The ECU has a general-purpose microcontroller. The general-purpose microcontroller includes an arithmetic unit and an input / output unit. The arithmetic unit comprises a CPU (Central Processing Unit) and memory. The memory includes read-only ROM (Read Only Memory) and read / write RAM (Random Access Memory). The ECU's arithmetic unit can virtually construct multiple information processing circuits by having the CPU execute a program stored in the ROM. The information processing circuits of the arithmetic unit may be configured with dedicated hardware. Dedicated hardware includes application-specific integrated circuits (ASICs) arranged to perform the necessary information processing functions, as well as devices such as conventional circuit components.

[0010] The software components of the electronic control unit 5 are independent software units that the electronic control unit 5 installs and runs to realize the functions of the vehicle 3. The software components are used in combination within the electronic control unit 5, for example, in accordance with the functions of the vehicle 3 realized by the electronic control unit 5. The software components can be wirelessly distributed to the vehicle 3 from a center 9 located remotely, for example, using OTA (Over The Air) technology. The software components distributed to the vehicle 3 are downloaded to the memory of the electronic control unit 5 that can use them. The electronic control unit 5 can update the software components by overwriting the currently used software components with the latest downloaded software components. The software components include configuration files. Configuration files are files that configure whether the software component is enabled or disabled. Software components enabled in the configuration file can be used in the electronic control unit 5 where they were downloaded. Software components disabled in the configuration file cannot be used in the electronic control unit 5 where they were downloaded. The configuration file is sometimes called a config file, an abbreviation for configuration file. Hereafter, the configuration file that disables the software will be referred to as the first configuration file, and the configuration file that enables the software will be referred to as the second configuration file.

[0011] The management system 1 includes a controller 11 and a software component management device 13. Hereinafter, the software component management device 13 will be abbreviated as management device 13. The software component management method according to this embodiment can be implemented in the management system 1 through the cooperation of the controller 11 and the management device 13.

[0012] The controller 11 is installed in the vehicle 3 and connected to the in-vehicle network 7. The controller 11 can be configured as an ECU, for example, like the electronic control unit 5. The controller 11 has a function for constant wireless connection to the internet.

[0013] The management device 13 is located in the center 9 and is connected to the internet. The management device 13 can communicate with the controller 11 of the vehicle 3 via the internet. The management device 13 manages the software components used in combination in the electronic control unit 5, corresponding to the functions of the vehicle 3 realized by the electronic control unit 5 installed in the vehicle 3. As part of this management, when a new version of the software components for the electronic control unit 5 is released, the management device 13 creates an update campaign. An update campaign is an event for distributing the latest version of the software components for version upgrade to the vehicle 3 equipped with the electronic control unit 5 that uses those software components. In an update campaign, all software components used in the electronic control unit 5 are distributed in the latest version combination. The latest version combination of software components is verified in advance to function correctly in the electronic control unit 5. The update campaign includes information specifying the target vehicle 3 and electronic control unit 5 to which the latest version of the software components will be distributed. The management device 13 receives an inquiry from the controller 11 of the vehicle 3 regarding the existence of an update campaign designated for that vehicle 3. If there is an update campaign targeting the vehicle 3 that made the inquiry, the management device 13 will distribute the latest version of the software components for the version upgrade related to that update campaign to the vehicle 3 that made the inquiry.

[0014] In addition to the management device 13, Center 9 is equipped with a first management server 15 and a second management server 17. The first management server 15 and the second management server 17 are connected to the management device 13 via a network 19. The network 19 may be the internet or a dedicated line.

[0015] The first management server 15 manages a parts database that associates the functions of the vehicle 3 with the parts used to realize those functions. The parts used to realize the functions of the vehicle 3 include software components corresponding to the functions to be realized, their configuration files, and the electronic control unit 5 that executes the software components. The parts database contains information about each part. The part information includes the part number, the name of the electronic control unit 5 in which the part is used, and the classification of the part. The classification of the part may include categories such as hardware, software, and configuration files. The parts database of the first management server 15 is updated to the latest content, for example, when a new version of the software component for the electronic control unit 5 is released. The first management server 15 can search the parts database in response to input from the management device 13 that specifies the functions of the vehicle 3, and output the part number of the configuration file of the software component used to realize the specified function. The first management server 15 can be configured to identify a specific unit that identifies a software component newly used in the electronic control unit 5 of the vehicle 3 when a specific function that is not currently implemented is newly implemented.

[0016] The second management server 17 manages, for each vehicle 3 managed by the management system 1, the enabled or disabled state of at least one of the software components downloaded to the electronic control unit 5 of the vehicle 3, according to the function of the vehicle 3. The second management server 17 can output the enabled or disabled state of the specified software component for the specified vehicle 3 in response to input from the management device 13 specifying the vehicle 3 and the software component. The second management server 17 can be configured as a management unit that manages the enabled or disabled state of at least one of the function-specific software components in the vehicle 3 for each vehicle 3.

[0017] When the management device 13 distributes the latest version of the software components to the vehicle 3 through an update campaign, it queries the second management server 17 to determine whether the software components to be distributed are enabled or disabled in the vehicle 3. If the status output by the second management server 17 in response to the query is disabled, the management device 13 distributes the software components including the first configuration file. If the status output by the second management server 17 in response to the query is enabled, the management device 13 distributes the software components including the second configuration file. The second management server 17 may update the status of the software components it manages for the vehicle 3 based on the contents of the configuration files of software components that the management device 13 has previously distributed to the vehicle 3.

[0018] The second management server 17 can be connected to, for example, one or more third management servers 21 via a network 19. A third management server 21 can be provided, for example, for each vehicle sales store. The third management server 21 manages information regarding the status of the software components of the electronic control unit 5 for each customer vehicle 3 at the sales store. The third management server 21 can obtain information about the customer's vehicle 3 from the second management server 17 and synchronize the information with the information about the customer's vehicle 3 managed by the second management server 17.

[0019] The management device 13 has a general-purpose microcontroller. The general-purpose microcontroller of the management device 13, like the general-purpose microcontroller of the ECU, includes an arithmetic unit and an input / output unit. Multiple information processing circuits virtually constructed by the arithmetic unit can constitute, for example, the first distribution unit 131, the second distribution unit 132, and the third distribution unit 133 of the management device 13.

[0020] The first distribution unit 131 distributes the latest version of a software component corresponding to a function not implemented in the vehicle 3 to the vehicle 3 equipped with the electronic control unit 5 that implements that function. The software component corresponding to a function not implemented in the vehicle 3 includes a first configuration file as a configuration file that sets the software to be disabled. The first distribution unit 131 may also distribute the latest version of a software component corresponding to a function implemented in the vehicle 3 to the vehicle 3 equipped with the electronic control unit 5 that implements that function. The software component corresponding to a function implemented in the vehicle 3 includes a second configuration file as a configuration file that sets the software to be enabled. For example, when upgrading the software component version, the first distribution unit 131 can distribute the latest version of the software component, including the first or second configuration file, to a designated vehicle 3 in an update campaign. In the destination vehicle 3, the controller 11 updates the software component of the designated electronic control unit 5 to the latest version of the software component distributed to the vehicle 3. Since the electronic control unit 5 is disabled by the first configuration file, it cannot use the software component corresponding to a function not implemented in the vehicle 3. Since the electronic control unit 5 is enabled by the second configuration file, it can use software components that correspond to the functions implemented in the vehicle 3.

[0021] The second distribution unit 132 distributes a second configuration file of the latest version of the software component corresponding to the specific function to the vehicle 3 that is the target of the request, based on a request to implement the specific function in a vehicle 3 that does not have the specific function implemented. The second distribution unit 132 designates an electronic control unit 5 and distributes the second configuration file to the vehicle 3 that is the target of the request. The electronic control unit 5 designated by the second distribution unit 132 as the distribution destination is the electronic control unit 5 that executes the latest version of the software component corresponding to the distributed second configuration file in the vehicle 3 that is the target of the request to realize the specific function. Hereinafter, the vehicle 3 that is the target of the request and does not have the specific function implemented will be referred to as the specific vehicle. A request to implement the specific function in the specific vehicle is input to the management device 13, for example, when the user of the specific vehicle goes through the procedure to purchase the specific function. For example, if the user of the specific vehicle operates the Human Machine Interface (HMI) of the specific vehicle and goes through the procedure to purchase the specific function, the controller 11 of the specific vehicle can input the request to the management device 13. For example, if a user of a specific vehicle purchases a specific function at a dealership for that specific vehicle through a terminal device (not shown) of the third management server 21, the third management server 21 can input a request to the management device 13. The management device 13 can then identify the software component of the specific vehicle corresponding to the requested specific function, for example, using the first management server 15 which constitutes the specific unit.

[0022] In a specific vehicle from which the second configuration file was distributed by the second distribution unit 132, the specific function is not implemented, so the configuration file of the software component for the specific function downloaded to the electronic control unit 5 that implements the specific function becomes the first configuration file. The controller 11 of the specific vehicle can download the distributed second configuration file into the memory of the electronic control unit 5 that implements the specific function. This download overwrites the first configuration file of the software component for the electronic control unit 5 that implements the specific function with the distributed second configuration file. The electronic control unit 5 can then implement the specific function using the software component whose configuration file has been overwritten from the first configuration file to the second configuration file and activated.

[0023] When a request to implement a specific function in a specific vehicle is input to the management device 13, the second distribution unit 132 may query the second management server 17 about the enabled or disabled status of the software component corresponding to the specific function of the specific vehicle before distributing the second configuration file. If the status output by the second management server 17 in response to the query is disabled, the second distribution unit 132 distributes the second configuration file of the latest version of the software component corresponding to the specific function to the vehicle 3 that is the target of the request. If the status output by the second management server 17 in response to the query is enabled, the second distribution unit 132 may determine that the specific function is implemented in the specific vehicle and may not distribute the second configuration file to the vehicle 3 that is the target of the request.

[0024] The third distribution unit 133 may, when a request to implement a specific function in a specific vehicle is input to the management device 13, distribute the latest version of the software components for version upgrade to the specific vehicle before the second distribution unit 132 distributes the second configuration file. In this case, the third distribution unit 133 distributes the latest version of the software components for version upgrade that corresponds to all functions of the specific vehicle to the specific vehicle, even if the controller 11 of the specific vehicle does not inquire about the presence or absence of an update campaign. The latest version of the software components that corresponds to functions not implemented in the specific vehicle will include the first configuration file, and the latest version of the software components that corresponds to functions implemented in the specific vehicle will include the second configuration file.

[0025] In this embodiment, an example of the procedure for managing software components used in combination in the electronic control unit 5, corresponding to the functions of the vehicle 3 realized by the electronic control unit 5, is described below. When the latest version of software components usable by the electronic control unit 5 of the vehicle 3 is released, the management device 13 creates an update campaign to distribute the released latest version of the software components. The latest version of the software components distributed in the update campaign includes a first configuration file for functions not implemented in the vehicle 3, and a second configuration file for functions implemented in the vehicle 3. When a user of a specific vehicle purchases a specific function not implemented in that vehicle, that information is entered into the third management server 21. Figure 2 shows an example of the processing procedure when purchase information of a specific function not implemented in a specific vehicle by a user 23 of that vehicle is entered into the third management server 21. When the third management server 21 receives purchase information of a specific function for a specific vehicle (step S11), it checks the status of the software components corresponding to the specific function that it manages for that vehicle (step S13). The third management server 21 can, for example, identify a software component corresponding to a specific function using the first management server 15, similar to the management device 13. If the third management server 21 confirms that the software component corresponding to the specific function is enabled, it determines that the specific function has been purchased and terminates the procedure. If the third management server 21 confirms that the software component corresponding to the specific function is disabled, it outputs a request to the management device 13 via the second management server 17 to enable the specific function (step S15).

[0026] When the management device 13 receives a request to activate a specific function, it specifies the specific vehicle and the specific function and requests the first management server 15 to output the part number of the second configuration file for the software component corresponding to the specific function of the specific vehicle (step S17). The third distribution unit 133 may create an update campaign targeting the specific vehicle before the request in step S17 and distribute the created update campaign to the specific vehicle without waiting for an inquiry from the specific vehicle (step S16). The latest version of the software component distributed in step S16 includes the first configuration file if the function is not implemented in the specific vehicle, and the second configuration file if the function is implemented in the specific vehicle. The first management server 15 searches for the part number of the second configuration file for the software component corresponding to the specific function of the specific vehicle, as requested in step S17, and outputs it to the management device 13 (step S19). The management device 13 creates a data package for the second configuration file of the software component corresponding to the specific function of the specific vehicle (step S21). This data package contains information specifying the electronic control unit 5 that implements the specific function. The second distribution unit 132 of the management device 13 distributes the created data package to the specified vehicle (step S23). Before distribution in step S23, the second distribution unit 132 may query the second management server 17 for the enabled or disabled status of the software component corresponding to the specific function of the specified vehicle. The second distribution unit 132 may perform the distribution in step S23 only if the response from the second management server 17 to the query is that it is disabled.

[0027] The controller 11 of the specified vehicle unpacks the data package distributed from the management device 13 (step S25) and transmits the second configuration file of the data package to the electronic control unit 5 specified in the data package information (step S27). Upon receiving the second configuration file, the electronic control unit 5 overwrites the first configuration file of the software component corresponding to the specific function with the received second configuration file and restarts the electronic control unit 5 (step S29). After restarting, the electronic control unit 5 notifies the controller 11 that the rewriting of the software component corresponding to the specific function with the second configuration file was successful (step S31). The controller 11 forwards the received notification to the management device 13 (step S33). The management device 13 notifies the third management server 21 via the second management server 17 that the activation of the specific function in the specified vehicle was successful and that the specific function has been implemented in the specified vehicle (step S35).

[0028] The second management server 17, which relays notifications from the management device 13, and the third management server 21, which receives notifications relayed by the second management server 17, update their respective management contents regarding the status of specific functions of a specific vehicle to match the contents of the notification. Through this update, the second management server 17 and the third management server 21 can update their respective management contents based on the second configuration file distributed to the specific vehicle by the management device 13, and synchronize their management contents with each other.

[0029] To implement a new function in vehicle 3 that is not currently implemented, it is necessary to update the software components used by the electronic control unit 5 to realize that function, upgrading them from the current version to a new version. Figure 3 shows an example of upgrading two software components corresponding to the newly implemented function when implementing a new function in vehicle 3. As shown in the example in Figure 3, if some software components 51 and 52 of vehicle 3 are upgraded one by one, the combination of versions of the three software components 51 to 53 used in the electronic control unit 5 will change as a result of the upgrade. In this case, in order to guarantee the quality of the upgraded software components, it is necessary to re-verify that the three software components 51 to 53 with the new version combination function correctly in the electronic control unit 5.

[0030] In this embodiment, all software components used in the electronic control unit 5 are updated to the latest version with each update campaign, regardless of whether they correspond to functions implemented in the vehicle 3. The electronic control unit 5 cannot use software components disabled by the first configuration file, and therefore cannot implement functions not implemented in the vehicle 3. The electronic control unit 5 can use software components enabled by the second configuration file, and therefore can implement functions implemented in the vehicle 3. By rewriting the first configuration file of a software component to the second configuration file, the software component is enabled and can be used by the electronic control unit 5, so that new functions can be implemented in the vehicle 3. Figure 4 shows a case where all three software components 51 to 53, including those corresponding to functions not implemented in the vehicle 3, are updated to the latest version during an update campaign. In the example in Figure 4, the three software components 51 to 53 of the electronic control unit 5 are updated from versions 1, 2, and 1 to the latest versions 3, 3, and 3 during the update campaign. Subsequently, when implementing new functions in the vehicle 3, the configuration file 54 of the software component corresponding to the new function is rewritten from the first configuration file to the second configuration file. Config A=0 represents the first configuration file, and Config A=1 represents the second configuration file.

[0031] As described above, in this embodiment, the software components 51 to 53 usable by the electronic control unit 5 of the vehicle 3 are updated to the latest version by the first distribution unit 131, even if they correspond to functions not implemented in the vehicle 3. The combination of software components 51 to 53 used by the electronic control unit 5 is always the latest version combination that has been verified in advance to function correctly. When implementing a new function in the vehicle 3, if only the software component corresponding to that function is updated to a new version, it would be necessary to verify that the updated combination of software components 51 to 53 functions correctly each time an update is performed. In this embodiment, this verification does not need to be performed each time the versions of the software components 51 to 53 are updated, so when updating the software components 51 to 53 using OTA technology, the man-hours required when adding functions to the vehicle 3 can be reduced.

[0032] In this embodiment, software components corresponding to a specific function are searched in the parts database of the first management server 15. In a request to implement a specific function in a specific vehicle, it is possible to identify which software components 51 to 53's second configuration file should be distributed to the second distribution unit 132 without directly specifying the software components 51 to 53. Therefore, the request procedure can be simplified by making it possible to identify the software components 51 to 53 that will rewrite the configuration file of the second configuration file to be distributed to the specific vehicle from the specific function that is requesting implementation in the specific vehicle.

[0033] In this embodiment, the status of the software component corresponding to a specific function is queried from the second management server 17. The second management server 17 manages the status of the function-specific software components 51 to 53 for each vehicle 3. If the second management server 17 manages that the software component corresponding to a specific function is disabled, the second distribution unit 132 distributes a second configuration file to the vehicle to enable the latest version of the software component corresponding to the specific function. Therefore, it is possible to suppress the unnecessary distribution of the second configuration file to a vehicle that has the requested specific function implemented, in order to enable the latest version of the software component corresponding to the specific function that is already enabled.

[0034] In this embodiment, regardless of whether the corresponding function is implemented in the vehicle 3, all software components 51 to 53 corresponding to the functions realized by the electronic control unit 5 of the vehicle 3 are distributed by the first distribution unit 131 in the latest version combination. Software components corresponding to functions not implemented in the vehicle 3 are disabled by the first configuration file, and software components corresponding to functions implemented in the vehicle 3 are enabled by the second configuration file. The latest versions of software components 51 to 53 have been separately verified to function correctly in the electronic control unit 5 even when used in combination. By setting the disabling and enabling of software components 51 to 53 in the configuration file, the software components 51 to 53 can be distributed to the vehicle 3 in the latest version combination that has been verified to function correctly.

[0035] In this embodiment, the latest versions of software components 51 to 53 are distributed to the vehicle 3 by an update campaign that distributes the upgraded software components 51 to 53 to the vehicle 3. In the update campaign, the first distribution unit 131 distributes the latest version of the software components, including the first configuration file, to the vehicle 3 for upgrading software components that correspond to functions not yet implemented in the vehicle 3. The update campaign distributes the latest versions of software components 51 to 53 that have been verified to function correctly in the electronic control unit 5 even when used in combination. With this distribution, even if the combination of versions of software components 51 to 53 that can be used in the electronic control unit 5 of the vehicle 3 changes, it is not necessary to verify that the software components 51 to 53 function correctly in the electronic control unit 5. By distributing the latest versions of software components 51 to 53 to the vehicle 3 through an update campaign, the man-hours required to update the software components 51 to 53 can be reduced by utilizing the update campaign process.

[0036] If a request to implement a specific function in a specific vehicle is made, and the software component corresponding to that function is not the latest version, then the configuration file of the latest version of the software component cannot be rewritten. If the third distribution unit 133 distributes the latest versions of the software components 51-53 to the specific vehicle before the second distribution unit 132 distributes the second configuration file, then the configuration file of the latest version of the software component can be rewritten in response to the request. By distributing the latest versions of the software components 51-53 to the specific vehicle before the second distribution unit 132 distributes the second configuration file, the specific function can be reliably implemented in the specific vehicle.

[0037] The embodiments described above are merely examples of the present invention. Therefore, the present invention is not limited to the embodiments described above, and various modifications are possible in forms other than those described above, as long as they do not depart from the technical spirit of the present invention, depending on the design and other factors.

[0038] 1 Software component management system 3 Vehicle 5 Electronic control unit 11 Controller 13 Software component management device 15 First management server (specific unit) 17 Second management server (management unit) 51-53 Software components 54 Configuration files 131 First distribution unit 132 Second distribution unit 133 Third distribution unit

Claims

1. A device for managing software components used in combination in an electronic control unit mounted on a vehicle, corresponding to a function of the vehicle realized by the electronic control unit mounted on the vehicle, comprising: a first distribution unit that distributes the latest version of the software component, which includes a first configuration file for disabling the software, corresponding to a function not implemented in the vehicle, to the vehicle equipped with the electronic control unit that realizes the function not implemented in the vehicle; and a second distribution unit that distributes to the specific vehicle, based on a request to implement a specific function not implemented in the specific vehicle, a second configuration file that enables the software of the latest version of the software component corresponding to the specific function.

2. The software component management device according to claim 1, wherein the second distribution unit distributes the second configuration file of the software component identified by the identification unit that identifies the software component corresponding to the specific function to the specific vehicle.

3. The software component management device according to claim 1 or 2, wherein the second distribution unit queries a management unit, which manages the status of at least one of the activation or deactivation of the software components for each function in the vehicle based on the first and second configuration files previously distributed to the vehicle, for the status managed by the management unit for the specific vehicle, and based on the response of the management unit to the query, distributes the second configuration file to the specific vehicle if the software of the software component corresponding to the specific function is deactivated in the specific vehicle.

4. A software component management device according to any one of claims 1 to 3, wherein the first distribution unit distributes the latest version of the software component, which includes the second configuration file, to the vehicle equipped with the electronic control unit that implements the function, to the vehicle.

5. A software component management device according to any one of claims 1 to 4, wherein the first distribution unit distributes the latest version of the software component, including the first configuration file, as the software component for version upgrade to the vehicle equipped with the electronic control unit that realizes the function not implemented in the vehicle, when the software component corresponding to the function not implemented in the vehicle is upgraded.

6. A software component management device according to any one of claims 1 to 5, further comprising a third distribution unit that, before the second distribution unit distributes the second configuration file to the specified vehicle based on the request, distributes the latest version of the software component corresponding to the function of the specified vehicle to the specified vehicle based on the request.

7. A system for managing software components used in combination in an electronic control unit, corresponding to a function of a vehicle realized by an electronic control unit mounted on the vehicle, comprising: a management device for distributing the software components to the vehicle; and a controller in the vehicle that causes the electronic control unit using the software components to download the software components distributed from the management device, wherein the management device comprises: a first distribution unit for distributing the latest version of the software component, which includes a first configuration file for disabling the software, corresponding to a function not implemented in the vehicle, to the vehicle equipped with the electronic control unit that realizes the function not implemented in the vehicle; and a second distribution unit for distributing the latest version of the software component corresponding to a specific function to the specific vehicle based on a request to implement a specific function not implemented in the specific vehicle, wherein the controller causes the electronic control unit on which the software component corresponding to the specific function is installed to overwrite the first configuration file included in the latest version of the software component corresponding to the specific function with the second configuration file distributed from the management device.

8. A method for managing software components used in combination in an electronic control unit mounted on a vehicle, in correspondence with the functions of the vehicle realized by the electronic control unit mounted on the vehicle, comprising: distributing the latest version of the software component, which includes a first configuration file for disabling the software and corresponds to the function not implemented in the vehicle, to the vehicle equipped with the electronic control unit that realizes the function not implemented in the vehicle; distributing a second configuration file for enabling the software of the latest version of the software component corresponding to the specific function, to the specific vehicle based on a request to implement a specific function not implemented in the specific vehicle; and in the specific vehicle, overwriting the first configuration file included in the latest version of the software component corresponding to the specific function in the electronic control unit from which the software component corresponding to the specific function has been downloaded, with the second configuration file distributed to the specific vehicle.

Images