Vehicle software automatic setting system, vehicle software automatic setting method, and vehicle control device

Abstract

This vehicle software automatic setting system comprises a vehicle control device and a management device. The vehicle control device includes: a device change detection unit that detects a device mounted to a vehicle; a device information recognition unit that recognizes identification information of the device; and an appropriateness inquiry unit that uses the identification information to inquire about the appropriateness and feasibility of work on a device. The management device includes: an appropriateness confirmation unit that uses the identification information inquired about by the appropriateness inquiry unit to confirm the appropriateness and feasibility of work on the device, and responds to the vehicle control device; and a software selection and distribution unit that selects software related to the device for which the appropriateness confirmation unit has confirmed that work is permitted, and distributes the software to the vehicle control device.

Description

Vehicle software automatic setting system, vehicle software automatic setting method, and vehicle control device

[0001] The present invention relates to a vehicle software automatic setting system, a vehicle software automatic setting method, and a vehicle control device.

[0002] Generally, a car's price is highest immediately after it is sold, and its value decreases over time. However, by continuously providing the latest technology (services) to the car through updates to the car's onboard software and hardware after the sale, the car's value can be maintained and its lifespan can be extended. In recent years, wireless communication has become the mainstream for updating onboard software, and automobile manufacturers are therefore considering online update methods. For example, Patent Document 1 proposes a technology for performing car software updates via wireless communication.

[0003] Patent document 1 states, "If the first update is a hardware update, the control unit notifies the user terminal that the first update will be performed at the store.If the first update is a software update, the control unit notifies the user terminal that the first update will be performed via wireless communication."

[0004] Typically, vehicle hardware updates are performed by OEM (Original Equipment Manufacturer) dealers or designated factories by physically installing, replacing, and adjusting various devices. After the hardware update process is complete, software updates are performed using dedicated equipment. Car owners can also update their vehicle's hardware and software by selecting new services as needed. As the number of hardware and software combinations increases, software rewriting and configuration become more complex, making the work more difficult for dealers and designated factories. As a solution to this problem, collaboration with OEM management centers and automatic software updates using UPnP (Universal Plug and Play) technology is expected to reduce the number of software tasks required for hardware updates and reduce operational errors.

[0005] Japanese Patent Application Laid-Open No. 2022-174678

[0006] When updating vehicle hardware and software to provide new services, automobile manufacturers have a responsibility to prevent incidents that could lead to accidents. However, when updating vehicle hardware using UPnP technology, it is difficult for automobile manufacturers to safely provide services if, for example, modifications to installed equipment, unauthorized installation of equipment, or installation work by unauthorized personnel occur. Furthermore, when updating vehicle hardware using UPnP technology, problems arise, such as software updates being performed on equipment installed in the vehicle without the vehicle owner's permission. Patent Document 1 does not mention the above-mentioned problems with automatic software updates for vehicles using UPnP technology.

[0007] The present invention has been made to solve the above problems, and an object of the present invention is to ensure the validity of the installation and installation procedures of vehicle equipment and to provide automatic safety service updates.

[0008] The present invention comprises a vehicle control device and a management device, wherein the vehicle control device has an equipment change detection unit that detects equipment attached to the vehicle, an equipment information recognition unit that recognizes identification information of the equipment, and a validity inquiry unit that uses the identification information to inquire about the feasibility and validity of work on the equipment, and the management device has a validity confirmation unit that uses the identification information inquired by the validity inquiry unit to confirm the feasibility and validity of work on the equipment and respond to the vehicle control device, and a software selection and distribution unit that selects software related to equipment that has been confirmed as work permitted by the validity confirmation unit and distributes it to the vehicle control device.

[0009] According to the present invention, it is possible to ensure the validity of the installation and installation procedure of vehicle equipment, and to provide automatic update of safety services.

[0010] FIG. 1 is a diagram showing an example of the functional configuration of a vehicle software automatic configuration system according to a first embodiment of the present invention. FIG. 2 is a flowchart showing the procedure of automatic software configuration processing associated with a change in vehicle equipment in the vehicle software automatic configuration system according to the first embodiment of the present invention. FIG. 3 is a flowchart showing the procedure of change detection processing of installed equipment in a vehicle control device of the vehicle software automatic configuration system according to the first embodiment of the present invention. FIG. 4 is a flowchart showing the procedure of installation procedure validity inquiry processing in a vehicle control device of the vehicle software automatic configuration system according to the first embodiment of the present invention. FIG. 5 is a flowchart showing the procedure of installation procedure validity inquiry response processing in a management center of the vehicle software automatic configuration system according to the first embodiment of the present invention. FIG. 6 is a flowchart showing the procedure of installed equipment validity inquiry processing in a vehicle control device of the vehicle software automatic configuration system according to the first embodiment of the present invention. FIG. 7 is a flowchart showing the procedure of software and configuration information application processing in a vehicle control device of the vehicle software automatic configuration system according to the first embodiment of the present invention. FIG. 8 is a flowchart showing the procedure of software selection and distribution processing in a management center of the vehicle software automatic configuration system according to the first embodiment of the present invention. FIG. 9 is a block diagram showing an example of the hardware configuration of a vehicle control device and a management center according to the first embodiment of the present invention. FIG. 10 is a flowchart showing the procedure of installation procedure validity inquiry processing in a vehicle control device of the vehicle software automatic configuration system according to a second embodiment of the present invention. 10 is a flowchart showing the procedure for a process for responding to an inquiry about the validity of an installation procedure in a management center of a vehicle software automatic configuration system according to a second embodiment of the present invention. 11 is a flowchart showing the procedure for a process for responding to an inquiry about the validity of an installed device in a management center of a vehicle software automatic configuration system according to a third embodiment of the present invention.

[0011] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functions or configurations are designated by the same reference numerals, and redundant description will be omitted. The present invention is applicable to, for example, a computing device for vehicle control capable of communicating with an on-board ECU (Electronic Control Unit) for an Advanced Driver Assistance System (ADAS) or Autonomous Driving (AD).

[0012] First Embodiment [Example of Functional Configuration of Vehicle Software Automatic Configuration System] First, an example of the functional configuration of a vehicle software automatic configuration system 1 according to a first embodiment of the present invention will be described. Fig. 1 is a diagram showing an example of the functional configuration of the vehicle software automatic configuration system 1 according to this embodiment. As shown in Fig. 1, the vehicle software automatic configuration system 1 includes a vehicle control device 10 and a management center 20 (an example of a management device). The vehicle control device 10 and the management center 20 are connected to each other so as to be able to send and receive information data to and from each other via a network formed of a public line such as the Internet, a dedicated line, or the like.

[0013] The vehicle control device 10 is an example of an information processing device having a CPU (Central Processing Unit) 12 that performs various calculations and a storage device 13, and is mounted on a vehicle to control the operation of the vehicle. The CPU 12 and the storage device 13 are connected to each other via an internal bus, an adapter, or the like. Furthermore, a plurality of devices 11_1 to 11_n that can be attached, replaced, and removed are connected to the vehicle control device 10 via an internal bus, a gateway, or the like. In the following description, when the devices 11_1 to 11_n are not distinguished from each other, they will be collectively referred to as "device 11." The devices 11 include, for example, calculation devices such as sensors, actuators, and controllers, and are used to realize new vehicle services provided by automobile manufacturers.

[0014] 1, the CPU 12 includes a device information recognition unit (installed device ID recognition unit 121), a device change detection unit (mounting information change detection unit 122), and a validity inquiry unit (validity confirmation unit 123). The CPU 12 also includes a vehicle software application unit (vehicle software update unit 124) and a notification unit (installed device confirmation result notification unit 125). The CPU 12 controls the operation of each of the above components.

[0015] The device information recognition unit (attached device ID recognition unit 121) recognizes identification information (for example, ID: Identification) of the device (device 11).

[0016] The device change detection unit (mounting information change detection unit 122) detects devices installed in the vehicle. The mounting information change detection unit 122 also detects connection changes such as replacement or removal of the device 11 recognized by the installed device ID recognition unit 121.

[0017] The validity inquiry unit (validity confirmation unit 123) inquires about the feasibility and validity of the equipment by using the equipment identification information. Here, the feasibility of the equipment includes the feasibility of the equipment identification information and the feasibility of the equipment installation procedure, and the validity of the equipment includes the validity of the equipment identification information and the validity of the equipment installation procedure.

[0018] The vehicle software application unit (vehicle software update unit 124) applies (updates) to the vehicle software selected and distributed by the software selection and distribution unit (software selection and distribution unit 212) described below of the management device (management center 20).

[0019] When a validity confirmation unit (validity confirmation unit 211) described below of the management device (management center 20) responds that the validity of the device has not been approved, the notification unit (installed device confirmation result notification unit 125) notifies a warning status indicating that the validity of the device has not been approved. The installed device confirmation result notification unit 125 notifies the vehicle owner of the warning status via the vehicle's center panel, an in-vehicle information terminal, the vehicle owner's smartphone app, etc.

[0020] The storage device 13 stores identification information (device ID) of the device 11, information on whether the identification information of the device 11 can be worked on and whether it is appropriate, information on whether the installation procedure for the device 11 can be worked on and whether it is appropriate, and installation information 131 including running software and setting information. The installation information 131 is stored in association with the device ID.

[0021] As shown in FIG. 1 , the management center 20 is an example of a management device and includes a CPU 21 that performs various calculations and a storage device 22. The management center 20 performs processes such as verifying the validity of installed devices in response to vehicle requests and selecting and distributing software requested by the vehicle. The management center 20 may also have vehicle management functions other than the above-described processes. The CPU 21 includes a validity verification unit (validity verification unit 211), a software selection and distribution unit (software selection and distribution unit 212), and an implementation information update unit 213, and controls the operation of each unit. A graphics processing unit (GPU) may be used instead of the CPU 21, or the CPU 21 and a GPU may be used together. The management center 20 may also be configured on a dedicated server or on the cloud.

[0022] The validity confirmation unit (validity confirmation unit 211) uses the identification information of the equipment inquired by the validity inquiry unit (validity confirmation unit 123 of the vehicle control device 10) to confirm whether the equipment can be worked on and its validity, and responds to the vehicle control device (vehicle control device 10).

[0023] The software selection and distribution unit (software selection and distribution unit 212) selects software related to equipment that has been confirmed as having a work permit by the validity confirmation unit (validity confirmation unit 211) and distributes it to the vehicle control device (vehicle control device 10). Note that the software related to the equipment includes in-vehicle software, equipment software, and setting information required to operate the equipment.

[0024] The mounting information update unit 213 updates the mounting information 221 stored in the storage device 22 using the mounting information 131 received from the vehicle control device 10 .

[0025] The storage device 22 stores implementation information 221 of the equipment connected to all vehicles managed by the management center 20, and SW (Software) and setting management information 222 including on-board software, equipment software, and setting information required to realize the vehicle services provided by the vehicle manufacturer.

[0026] [Procedure for Automatic Software Configuration Processing Accompanying a Change in Vehicle Equipment] Next, a procedure for automatic software configuration processing accompanying a change in vehicle equipment will be described in the vehicle software automatic configuration system 1. Figure 2 is a flowchart showing the procedure for automatic software configuration processing accompanying a change in vehicle equipment in the vehicle software automatic configuration system 1 according to this embodiment. The processing described below starts when the vehicle is started.

[0027] First, the mounting information change detection unit 122 of the vehicle control device 10 detects a change in the attached device (step S100). Details of this process will be described later with reference to FIG.

[0028] Next, the mounting information change detection unit 122 determines whether or not there has been a change in the attached device (step S110). In this process, if the mounting information change detection unit 122 detects a change in the attached device, it determines that there has been a change in the attached device, and step S110 returns Yes. On the other hand, if the mounting information change detection unit 122 does not detect a change in the attached device, it determines that there has been no change in the attached device, and step S110 returns No.

[0029] In the process of step S110, if the mounting information change detection unit 122 determines that there is no change in the attached device (if the determination in step S110 is No), the process proceeds to step S500, which will be described later.

[0030] On the other hand, if the mounting information change detection unit 122 determines in step S110 that there has been a change in the attached device (if step S110 returns Yes), the processing proceeds to step S200. In step S200, the validity confirmation unit 123 inquires of the management center 20 about the validity of the attachment procedure for the attached device that has changed. In addition, in this processing, the validity confirmation unit 123 updates the validity of the attachment procedure in the mounting information 131 based on the response to the validity inquiry received from the management center 20. Note that details of this processing will be described later with reference to FIG. 4. In the following description, the attached device for which a change has been detected will sometimes be abbreviated as "device," and the "attachment procedure" will sometimes be abbreviated as "procedure."

[0031] Next, the validity confirmation unit 123 determines whether to reject the work on the procedure based on the response to the validity inquiry from the management center 20 (step S210). In this process, if the response from the management center 20 includes a response of "work permitted," the validity confirmation unit 123 determines that the work on the procedure is permitted, and the result of the determination in step S210 is Yes. On the other hand, if the response from the management center 20 includes a response of "work rejected," the validity confirmation unit 123 determines that the work on the procedure is rejected, and the result of the determination in step S310 is No.

[0032] In the process of step S210, if the validity confirmation unit 123 determines that the procedure is a work refusal (if the determination in step S210 is "work refusal"), the process of step S500 described below is performed.

[0033] On the other hand, in the processing of step S210, if the validity confirmation unit 123 determines that the procedure is permitted to work (if the determination in step S210 is "permit to work"), the processing of step S300 is performed. In the processing of step S300, the validity confirmation unit 123 inquires of the management center 20 about the validity of the identification information (device ID) of the changed attached device (step S300). In addition, in this processing, the validity confirmation unit 123 updates the validity of the device ID in the mounting information 131 based on the response to the validity inquiry from the management center 20. Note that details of this processing will be described later in FIG. 6. In the following description, the validity of the identification information of the attached device will be referred to as "validity of the device status," and the refusal to work on the identification information of the attached device will be referred to as "work refusal on the device status."

[0034] Next, the validity confirmation unit 123 determines whether the equipment status is work-rejected based on the response to the validity inquiry from the management center 20 (step S310). In this process, if the response from the management center 20 includes a response of "work permitted," the validity confirmation unit 123 determines that the equipment status is work-rejected, and the determination in step S310 is Yes. On the other hand, if the response from the management center 20 includes a response of "work-rejected," the validity confirmation unit 123 determines that the equipment status is work-rejected, and the determination in step S310 is No.

[0035] In the process of step S310, if the validity confirmation unit 123 determines that the device status is work refusal (if the determination in step S310 is "work refusal"), the process of step S500, which will be described later, is performed.

[0036] On the other hand, if the validity confirmation unit 123 determines in step S310 that the equipment status is work permitted (if the determination in step S310 is "work permitted"), the process proceeds to step S400. In step S400, the vehicle software update unit 124 applies software and setting information related to the installed equipment. The details of step S400 will be described later with reference to FIG. 8.

[0037] If the determination in step S110 is No, if the determination in step S210 is "work refusal," if the determination in step S310 is "work refusal," or after the processing of step S400, the processing of step S500 is performed. In the processing of step S500, the validity confirmation unit 123 of the vehicle control device 10 confirms the validity of all attached devices of the vehicle control device 10. Also in this processing, the validity confirmation unit 123 confirms the validity of the device state and the validity of the procedure in the implementation information 131 linked to the device ID of each device. Also in this processing, the vehicle control device 10 shares the implementation information 131 with the management center 20 via the network. The implementation information update unit 213 of the management center 20 updates the implementation information 131 shared from the vehicle control device 10 to the implementation information 221 of the management center 20.

[0038] Next, the validity confirmation unit 123 determines whether there is any device whose validity has not been approved among all the installed devices (step S510). In this process, if the validity confirmation unit 123 confirms in the process of step S500 that the device state validity and procedure validity in the implementation information 131 linked to the device IDs of all the devices are "approved," it determines that there is no unapproved device, and step S510 results in "No." On the other hand, if the validity confirmation unit 123 confirms in the process of step S500 that there is any device whose device state validity and / or procedure validity in the implementation information 131 linked to the device ID is "unapproved," it determines that there is an unapproved device, and step S510 results in "Yes."

[0039] In the process of step S510, if the validity confirmation unit 123 determines that there is an unapproved device (if the determination in step S510 is Yes), the installed device confirmation result notification unit 125 notifies the vehicle owner of a warning status indicating the unapproved state of the installed device whose validity has not been approved (step S520). Note that the warning notification to the vehicle owner may be notified via the owner's smartphone app or may be displayed on the vehicle's center panel. In addition, in this process, warning notifications may be issued separately for unapproved procedure validity and unapproved device state validity.

[0040] On the other hand, if the validity check unit 123 determines in step S510 that there is no unauthorized device (if the determination in step S510 is No), the installed device check result notifying unit 125 cancels the warning notification (step S530). After the processing in step S520 or step S530, the automatic software setting process associated with the vehicle device change ends.

[0041] [Procedure for detecting a change in an installed device in a vehicle control device] Next, a procedure for detecting a change in an installed device will be described in the vehicle control device 10 of the automatic vehicle software setting system 1. Figure 3 is a flowchart showing the procedure for detecting a change in an installed device in the vehicle control device 10 of the automatic vehicle software setting system 1 according to this embodiment. The process described below is called and executed as a subroutine in step S100 of the process shown in Figure 2.

[0042] First, the attached device ID recognition unit 121 of the vehicle control device 10 recognizes the device IDs of all the attached devices in the vehicle (step S101).

[0043] Next, the mounting information change detection unit 122 of the vehicle control device 10 starts a loop process that is performed several times for the devices recognized by the attached device ID recognition unit 121 (step S102).

[0044] Next, the packaging information change detection unit 122 acquires one of the recognized device IDs (step S103). Note that each time the loop process is repeated, the packaging information change detection unit 122 acquires the device IDs one by one in order.

[0045] Next, the packaging information change detection unit 122 determines whether the acquired device ID exists in the packaging information 131 (step S104).

[0046] In the processing of step S104, if the mounting information change detection unit 122 determines that the device ID does not exist in the mounting information 131 (if the determination in step S104 is No), it updates (registers) the new installation of the device in the mounting information 131 (step S105).

[0047] On the other hand, in the processing of step S104, if the implementation information change detection unit 122 determines that a device ID exists in the implementation information 131 (if the judgment of step S104 is Yes), or after the processing of step S105, the current loop processing is terminated (step S106).

[0048] After the processes of steps S102 to S106 have been executed for all devices, the packaging information change detection unit 122 determines whether or not there is a device ID that has not been searched for in the packaging information 131 (step S107).

[0049] In the processing of step S107, if the mounting information change detection unit 122 determines that there is a device ID that was not searched for in the mounting information 131 (if the determination in step S107 is Yes), it updates (deletes) the removal of the device in the mounting information 131 (step S108).

[0050] On the other hand, in the processing of step S107, if the mounting information change detection unit 122 determines that there is no device ID that was not searched for in the mounting information 131 (if the determination is No in step S107), or after the processing of step S108, the change detection processing of the attached device ends.

[0051] [Procedure for querying the validity of a procedure in a vehicle control device] Next, a procedure for querying the validity of an installation procedure in the vehicle control device 10 of the automatic vehicle software setting system 1 will be described. Figure 4 is a flowchart showing the procedure for querying the validity of an installation procedure in the vehicle control device 10 of the automatic vehicle software setting system 1 according to this embodiment. The process described below is called and executed as a subroutine in step S200 of the process shown in Figure 2.

[0052] First, the validity confirmation unit 123 of the vehicle control device 10 acquires vehicle position information at the time of initial detection of connection of the attached device in order to identify the work location (step S201). Note that the vehicle position information is calculated by comparing, for example, GPS information and detection information from sensors such as cameras and LiDAR (Light Detection and Ranging) with map information.

[0053] Next, the validity confirmation unit 123 transmits the acquired vehicle position information to the management center 20 and makes an inquiry about the validity of the equipment installation procedure (step S202). In this process, the management center 20 confirms whether the work can be performed and the validity of the installation procedure in response to the procedure validity inquiry received from the vehicle control device 10, and returns the confirmation result to the vehicle control device 10. The installation procedure validity inquiry response process in the management center 20 will be described in detail later with reference to FIG. 5.

[0054] Next, the validity confirmation unit 123 determines whether the work can be performed based on the confirmation result returned from the management center 20 (step S203).

[0055] In the processing of step S203, if the validity confirmation unit 123 determines that the returned confirmation result includes "rejection of work" (if the determination is "rejection of work" in step S203), the procedure validity inquiry processing ends.

[0056] On the other hand, in the process of step S203, if the validity checking unit 123 determines that the returned confirmation result includes "work permission", it determines the validity of the procedure (step S204).

[0057] In the process of step S204, if the validity confirmation unit 123 determines that the validity of the procedure included in the returned confirmation result is "approved" (if the determination is "approved" in step S204), the validity confirmation unit 123 performs the process of step S206. In the process of step S206, the validity confirmation unit 123 updates the procedure validity linked to the device ID of the attached device in the mounting information 131 to "approved" (step S205).

[0058] On the other hand, in the process of step S204, if the validity confirmation unit 123 determines that the validity of the procedure included in the returned confirmation result is "unapproved" (if the determination in step S204 is "unapproved"), the validity confirmation unit 123 performs the process of step S206. In the process of step S206, the validity confirmation unit 123 updates the procedure validity linked to the device ID of the installation device in the mounting information 131 to "unapproved." If the determination in step S203 is "work refusal," the procedure validity inquiry process ends after the process of step S205 or step S206.

[0059] [Procedure for Response to Inquiries about the Validity of an Installation Procedure at the Management Center] Next, a description will be given of a process for response to inquiries about the validity of an installation procedure at the management center 20 of the vehicle software automatic configuration system 1. In this process, if the validity confirmation unit (validity confirmation unit 211) determines, based on the vehicle's location information, that the vehicle's location is a pre-registered work location for which work is permitted, the validity of the device installation procedure is approved and the possibility of performing the device installation procedure is confirmed as permitted. Furthermore, if the validity confirmation unit (validity confirmation unit 211) determines, based on the vehicle's location information, that the vehicle's location is not a pre-registered work location for which work is permitted, the validity confirmation unit (validity confirmation unit 211) confirms that the validity of the device installation procedure is not approved and asks the vehicle owner whether the device installation procedure can be performed. Furthermore, if the device installation procedure is permitted by the owner, the validity confirmation unit (validity confirmation unit 211) confirms that the possibility of performing the device installation procedure is permitted. Specific processing procedures will be described with reference to FIG. 5 .

[0060] 5 is a flowchart showing the procedure for handling an inquiry about the validity of an installation procedure in the management center 20 of the vehicle software automatic configuration system 1 according to this embodiment. The process described below starts when the management center 20 receives an inquiry about the validity of an installation procedure from a vehicle.

[0061] First, the validity confirmation unit 211 of the management center 20 receives an inquiry about the validity of the installation procedure (step S251).

[0062] Next, the validity confirmation unit 211 determines whether the vehicle location information included in the validity inquiry is a work location permitted by the vehicle manufacturer (step S252). Note that work locations permitted by the vehicle manufacturer include, for example, dealer factories, designated factories, etc.

[0063] In the process of step S252, if the validity confirmation unit 211 determines that the vehicle's location information is a work location for a work permit that has been registered in advance in the storage device 22 (if Yes in step S252), the validity confirmation unit 211 updates the validity of the installation procedure to "approved" (step S253). In this process, the validity confirmation unit 211 updates the procedure validity linked to the device ID of the installation device in the mounting information 221 to "approved".

[0064] On the other hand, in the processing of step S252, if the validity confirmation unit 211 determines that the vehicle's location information is not a work location pre-registered in the storage device 22 (if the judgment in step S252 is No), it confirms with the vehicle owner whether work can be performed (step S254).

[0065] Next, the validity confirmation unit 211 determines whether the response from the vehicle owner is permission to carry out the work (step S255).

[0066] In the process of step S255, if the owner's response is to refuse the work (if the determination in step S255 is No), the validity confirmation unit 211 responds to the vehicle control device 10 with a refusal to perform the work (step S256).

[0067] On the other hand, in the process of step S255, if the owner's response is permission to perform the work (if the determination of step S255 is Yes), the validity confirmation unit 211 updates the validity of the installation procedure to "unapproved" (step S257). In this process, the validity confirmation unit 211 updates the procedure validity linked to the device ID of the installation device in the mounting information 221 to "unapproved".

[0068] After the processing of step S253 or step S257, the validity confirmation unit 211 responds with the work permission and the updated procedure validity to the vehicle control device 10 (step S258). After the processing of step S256 or step S258, the installation procedure validity inquiry response processing in the management center 20 ends.

[0069] [Procedure for querying the validity of the installed device state in the vehicle control device] Next, a procedure for querying the validity of the installed device state in the vehicle control device 10 of the automatic vehicle software setting system 1 will be described. Figure 6 is a flowchart showing the procedure for querying the validity of the installed device state in the vehicle control device 10 of the automatic vehicle software setting system 1 according to this embodiment. The process described below is called and executed as a subroutine in step S300 of the process shown in Figure 2.

[0070] First, the validity confirmation unit 123 of the vehicle control device 10 makes an inquiry about the validity of the equipment status to the management center 20 using the equipment ID of the installed equipment as a key (step S301). In this process, the management center 20 confirms whether the work can be performed and the validity in response to the inquiry about the validity of the equipment status received from the vehicle control device 10, and returns the confirmation result to the vehicle control device 10. The process of responding to an inquiry about the validity of the installed equipment status in the management center 20 will be described in detail later with reference to FIG. 7.

[0071] Next, the validity confirmation unit 123 determines whether the work can be performed based on the confirmation result returned from the management center 20 (step S302).

[0072] In the process of step S302, if the returned confirmation result includes "rejection of work" (if the determination in step S302 is "rejection of work"), the validity confirmation unit 123 ends the validity inquiry process for the attached device.

[0073] On the other hand, in the processing of step S302, if the returned confirmation result includes "work permission" (if the "work permission" judgment is made in step S302), the validity confirmation unit 123 judges the validity of the equipment status based on the confirmation result (step S303).

[0074] In the process of step S303, if the validity confirmation unit 123 determines that the validity of the device status included in the returned confirmation result is "approved" (if the determination in step S303 is "approved"), the process proceeds to step S304. In the process of step S304, the validity confirmation unit 123 updates the device status validity associated with the device ID of the attached device in the mounting information 131 to "approved".

[0075] On the other hand, in the process of step S303, if the validity of the device status included in the returned confirmation result is "unapproved" (if the determination of step S303 is "unapproved"), the validity confirmation unit 123 performs the process of step S305. In the process of step S305, the validity confirmation unit 123 updates the device status validity linked to the device ID of the installed device in the mounting information 131 to "unapproved." If the determination of step S302 is "work refusal," the installed device status validity inquiry process ends after the process of step S304 or step S305.

[0076] [Procedure for Response to Inquiries Regarding Installed Device Status at Management Center] Next, a description will be given of a process for response to inquiries regarding the validity of installed device status at the management center 20 of the vehicle software automatic configuration system 1. In this process, if the validity confirmation unit (validity confirmation unit 211) determines that the device meets the safety standards based on the device identification information, the validity confirmation unit determines that the validity of the device identification information is approved and that the work permission for the device identification information is permitted. Furthermore, if the validity confirmation unit (validity confirmation unit 211) determines that the device does not meet the safety standards based on the device identification information, the validity confirmation unit determines that the validity of the device identification information is not approved and confirms with the vehicle owner whether the work permission for the device identification information is permitted. Furthermore, if the device identification information is permitted by the owner, the validity confirmation unit (validity confirmation unit 211) determines that the work permission for the device identification information is permitted. Specific processing procedures will be described with reference to FIG. 7 .

[0077] 7 is a flowchart showing the procedure for processing an inquiry about the validity of an installed device in the management center 20 of the vehicle software automatic configuration system 1 according to this embodiment. The processing described below starts when the management center 20 receives an inquiry about the validity of the status of an installed device from a vehicle.

[0078] First, the validity confirmation unit 211 of the management center 20 receives an inquiry about the validity of the state of the installed device (step S351).

[0079] Next, the validity confirmation unit 211 determines whether the device having the device ID included in the validity inquiry meets the safety standards, which are the minimum technical standards for safety or pollution prevention (step S352).

[0080] In the process of step S352, if the validity confirmation unit 211 determines that the device satisfies the safety standards (in the case of Yes determination in step S352), the validity confirmation unit 211 updates the validity of the installed device status to "approved" (step S353). In this process, the validity confirmation unit 211 updates the device status validity linked to the device ID of the installed device in the mounting information 221 to "approved".

[0081] On the other hand, in the processing of step S352, if the validity confirmation unit 211 determines that the equipment does not meet the safety standards (if the judgment at step S352 is No), it confirms with the vehicle owner whether the work can be performed (step S354).

[0082] Next, the validity confirmation unit 211 determines whether the response from the vehicle owner is permission to carry out the work (step S355).

[0083] In the process of step S355, if the validity confirmation unit 211 determines that the owner's response is a refusal to perform the work (if the determination at step S355 is No), it responds to the vehicle control device 10 with a refusal to perform the work (step S356).

[0084] On the other hand, in the process of step S355, if the validity confirmation unit 211 determines that the owner's response is permission to perform the work (if Yes in step S355), the validity confirmation unit 211 updates the validity of the installed device status to "unapproved" (step S357). In this process, the validity confirmation unit 211 updates the device status validity linked to the device ID of the installed device in the mounting information 221 to "unapproved".

[0085] After the processing of step S353 or step S357, the validity confirmation unit 211 responds with the work permit and the updated device validity to the vehicle control device 10 (step S358). After the processing of step S356 or step S358, the processing for responding to an inquiry about the installed device status in the management center 20 ends.

[0086] [Procedure for Applying Software and Setting Information in Vehicle Control Device] Next, a procedure for applying software and setting information in the vehicle control device 10 will be described. Figure 8 is a flowchart showing the procedure for applying software and setting information in the vehicle control device 10 of the vehicle software automatic setting system 1 according to this embodiment. The process described below is called and executed as a subroutine in step S400 of the process shown in Figure 2.

[0087] First, the vehicle software update unit 124 of the vehicle control device 10 requests the management center 20 to distribute software and setting information related to the installed device (step S401). In this process, the management center 20 selects software and setting information related to the installed device in response to the software and setting information distribution request received from the vehicle control device 10 and distributes them to the vehicle control device 10. The software selection and distribution process in the management center 20 will be described in detail later with reference to FIG. 9.

[0088] Next, the vehicle software update unit 124 receives the software and setting information from the management center 20 and buffers them (step S402).

[0089] Next, the vehicle software update unit 124 determines whether or not an update to the in-vehicle software is available (step S403). In this process, if the received software includes in-vehicle software, the vehicle software update unit 124 compares the version information of the received in-vehicle software with the version information of the in-vehicle software currently in operation, and makes a determination based on the comparison result. If the version information of the received in-vehicle software differs from the version information of the in-vehicle software currently in operation, the vehicle software update unit 124 determines that an update is available, and step S403 returns Yes. On the other hand, if the version information of the received in-vehicle software is the same as the version information of the in-vehicle software currently in operation, the vehicle software update unit 124 determines that no update is available, and step S403 returns No.

[0090] In the process of step S403, if the vehicle software update unit 124 determines that there is a vehicle software update (if the determination in step S403 is Yes), it applies the received in-vehicle software (step S404).

[0091] On the other hand, if the vehicle software update unit 124 determines in step S403 that there is no in-vehicle software update (if the determination in step S403 is No), or after the processing of step S403, it determines whether there is an update to the setting information (step S405). In this process, the vehicle software update unit 124 compares the received setting information with the setting information currently in operation and makes a determination based on the comparison result. If the received setting information differs from the setting information currently in operation, the vehicle software update unit 124 determines that there is an update, and step S405 is determined to be Yes. On the other hand, if the received setting information is the same as the setting information currently in operation, the vehicle software update unit 124 determines that there is no update, and step S405 is determined to be No.

[0092] In the process of step S405, if it is determined that there is an update to the setting information (if the determination in step S405 is Yes), the vehicle software update unit 124 applies the received setting information (step S406).

[0093] On the other hand, if the vehicle software update unit 124 determines in the processing of step S405 that there is no update to the setting information (if the determination in step S405 is No), or after the processing of step S406, it determines whether or not there is an update to the equipment software (step S407). In this processing, the vehicle software update unit 124 compares the version information of the received equipment software with the version information of the equipment software currently in operation, and makes a determination based on the comparison result. If the version information of the received equipment software differs from the version information of the equipment software currently in operation, the vehicle software update unit 124 determines that there is an update, and step S407 is determined to be Yes. On the other hand, if the version information of the received equipment software is the same as the version information of the equipment software currently in operation, the vehicle software update unit 124 determines that there is no update, and step S407 is determined to be No.

[0094] In the process of step S407, if it is determined that there is an update for the device software (if the determination in step S407 is Yes), the vehicle software update unit 124 applies the received device software (step S408).

[0095] On the other hand, in the processing of step S407, if the vehicle software update unit 124 determines that there is no equipment software update (if the judgment of step S407 is No), or after the processing of step S408, the software and setting information application processing ends.

[0096] [Software Selection and Distribution Processing Procedure at Management Center] Next, a description will be given of the software selection and distribution processing procedure at the management center 20. Fig. 9 is a flowchart showing the software selection and distribution processing procedure at the management center 20 of the vehicle software automatic configuration system 1 according to this embodiment. The processing described below starts when the management center 20 receives a software distribution request from the vehicle control device 10.

[0097] First, the software selection and distribution unit 212 of the management center 20 receives a software distribution request (step S4011).

[0098] Next, the software selection and distribution unit 212 selects software and setting information based on the received distribution request (step S4012). In this process, the software selection and distribution unit 212 selects in-vehicle software, device software, and setting information that have been verified by the vehicle manufacturer from the SW and setting management information 222 in the storage device 22, using the implementation information 131 linked to the device ID included in the received distribution request and the service menu provided by the vehicle manufacturer for the vehicle as keys.

[0099] Next, the software selection and distribution unit 212 distributes the selected software and setting information to the vehicle control device 10 (step S4013). After the processing of step S4013, the software selection and distribution process ends. Note that a standardized wireless communication method can be used as the distribution method.

[0100] [Hardware Configuration Example of Vehicle Control Device and Management Center] Next, a description will be given of a hardware configuration example of the information processing device 30 that constitutes the vehicle control device 10 and the management center 20. Fig. 10 is a block diagram showing a hardware configuration example of the vehicle control device 10 and the management center 20 according to this embodiment.

[0101] 10, the information processing device 30 includes a CPU 30a, a ROM (Read Only Memory) 30b, a RAM (Random Access Memory) 30c, a storage device 30d, and an input / output interface 30e. The CPU 30a, the ROM 30b, the RAM 30c, the storage device 30d, and the input / output interface 30e are connected via a bus 30f so as to be able to send and receive information data to and from each other.

[0102] The CPU 30a is an example of the CPU 12 of the vehicle control device 10 and the CPU 21 of the management center 20, and controls the operation of each part in the vehicle control device 10 or the management center 20. Note that a GPU (Graphics Processing Unit) may be used instead of the CPU 30a, or the CPU 30a and the GPU may be used together.

[0103] The ROM 30b is configured as a storage medium such as a nonvolatile memory, and stores programs and data that are executed and referenced by the CPU 30a.

[0104] The RAM 30c is configured by a storage medium such as a volatile memory, and temporarily stores information (data) required for each process performed by the CPU 30a.

[0105] The storage device 30d is a computer-readable, non-transitory recording medium storing the program executed by the CPU 30a, such as a hard disk drive (HDD). The storage device 30d is an example of the storage device 13 of the vehicle control device 10 and the storage device 22 of the management center 20. The storage device 30d stores the implementation information 131, implementation information 221, SW and setting management information 222, etc., described in FIG. 1, as well as programs and data for the CPU 30a to control each component, an operating system (OS), and controllers. Note that some of the programs and data stored in the storage device 30d may be stored in the ROM 30b. The computer-readable, non-transitory recording medium storing the program executed by the CPU 30a is not limited to an HDD and may be, for example, a solid state drive (SSD), a compact disc (CD)-ROM, a digital versatile disc (DVD)-ROM, or other recording medium.

[0106] The input / output interface 30e transmits and receives information data to and from the outside of the information processing device 30 under the control of the CPU 30a.

[0107] [Effects] As described above, the vehicle control device 10 of the vehicle software automatic configuration system 1 according to this embodiment detects changes in installed equipment and queries the vehicle management center 20 about the changed status of the installed equipment and the validity of the equipment installation procedure (equipment validity). The management center 20 of the vehicle software automatic configuration system 1 also confirms whether work can be performed and its validity, and responds with the confirmation result to the vehicle control device 10. The vehicle control device 10 also requests the management center 20 to deliver software and setting information associated with changes in the installed equipment and applies the software and setting information to the vehicle only if the equipment status and equipment installation procedure are approved. The vehicle control device 10 also notifies the vehicle owner of a warning status indicating that the validity of equipment whose validity has not been approved. That is, the vehicle software automatic configuration system 1 selects software (services) related to equipment that meets safety standards at a work location approved by the vehicle manufacturer or a work location approved by the vehicle owner, and automatically applies (updates) the software to the vehicle. Furthermore, the vehicle software automatic configuration system 1 notifies the vehicle owner of any device whose validity has not been approved, allowing the vehicle owner to ascertain the validity of the devices installed in the vehicle. Therefore, the vehicle software automatic configuration system 1 according to this embodiment can ensure the validity of the installation and installation procedure of vehicle devices, and provide a safe automatic update service.

[0108] Second Embodiment Next, a procedure for processing an inquiry about the validity of an installation procedure in a vehicle control device 10 of an automatic vehicle software configuration system 1 according to a second embodiment of the present invention will be described. Note that the automatic vehicle software configuration system 1 according to the second embodiment of the present invention has the same configuration as the automatic vehicle software configuration system 1 according to the first embodiment, and therefore a duplicated description will be omitted.

[0109] Fig. 11 is a flowchart showing the procedure for processing to inquire about the validity of an installation procedure in the vehicle control device 10 of the vehicle software automatic configuration system 1 according to this embodiment. As can be seen by comparing Fig. 11 with Fig. 4, in the second embodiment, the validity confirmation unit 123 does not acquire vehicle position information upon initial detection of connection of an installed device (step S201 in Fig. 4), but instead performs processing of step S2011 shown in Fig. 11. Note that the processes other than step S2011 shown in Fig. 11 are the same as the processes shown in Fig. 4, and therefore redundant explanations will be omitted.

[0110] In the process of step S2011, predetermined authentication information for authenticating the worker who installed the device is acquired. The validity confirmation unit 123 of the vehicle control device 10 acquires the predetermined authentication information, including authentication information of a certification device that certifies the work permission to connect to a vehicle-specific diagnostic device (ODB2: On-Board Diagnostics 2) provided for each worker at the dealer or designated factory, and authentication information (password, biometric authentication, etc.) of an authentication device individually owned by the worker (e.g., the worker's smartphone). The validity confirmation unit 123 then transmits the acquired predetermined authentication information to the management center 20 and queries the validity of the installation procedure (step S202).

[0111] Meanwhile, when the management center 20 receives an inquiry about the validity of the installation procedure of the vehicle control device 10, the management center 20 performs an installation procedure validity inquiry response process. In this embodiment, if the validity confirmation unit (validity confirmation unit 211) determines, based on predetermined authentication information for authenticating the worker who installed the device, that the worker is a worker with a pre-registered work permit, the validity of the installation procedure of the device is approved and the possibility of performing the installation procedure of the device is confirmed as permitted. Furthermore, if the validity confirmation unit (validity confirmation unit 211) determines, based on predetermined authentication information for authenticating the worker who installed the device, that the worker is not a worker with a pre-registered work permit, the validity confirmation unit (validity confirmation unit 211) confirms that the validity of the installation procedure of the device is not approved and confirms with the vehicle owner whether the installation procedure of the device is permitted. Furthermore, if the owner has permitted the installation procedure of the device, the validity confirmation unit (validity confirmation unit 211) confirms that the possibility of performing the installation procedure of the device is permitted. Specific processing procedures will be described with reference to FIG. 12 .

[0112] 12 is a flowchart showing the procedure for processing an inquiry about the validity of an installation procedure in the management center 20 of the vehicle software automatic configuration system 1 according to this embodiment. As can be seen by comparing FIG. 12 with FIG. 5, in the second embodiment, the validity confirmation unit 211 of the management center 20 performs the processes of steps S2521 and S2522 shown in FIG. 12 instead of step S252 in FIG.

[0113] In the process of step S2521, the validity confirmation unit 211 compares the predetermined authentication information included in the received validity inquiry with the predetermined authentication information registered in advance in the storage device 22 to authenticate the worker.

[0114] Next, the validity confirmation unit 211 determines whether the worker is a worker with a work permit (step S2522). In this process, if the predetermined authentication information included in the received validity inquiry matches the predetermined authentication information registered in advance, the validity confirmation unit 211 determines that the worker is a worker with a work permit, and step S2522 results in a Yes judgment. On the other hand, if the predetermined authentication information included in the received validity inquiry does not match the predetermined authentication information registered in advance, the validity confirmation unit 211 determines that the worker is not a worker with a work permit, and step S2522 results in a No judgment.

[0115] In the process of step S2522, if the validity confirmation unit 211 determines that the worker is a worker with a work permit (if the determination in step S2522 is Yes), the validity confirmation unit 211 performs the process of step S253.

[0116] On the other hand, in the process of step S2522, if the validity confirmation unit 211 determines that the worker is not a worker with a work permit (if the determination of step S2522 is No), the process of step S254 is performed. Note that the processes from step S2522 onwards are the same as the processes shown in Fig. 5, and therefore redundant explanations will be omitted.

[0117] [Effects] As described above, the vehicle software automatic configuration system 1 according to the second embodiment of the present invention does not verify the validity of the work location, but verifies whether the worker at the dealer or designated factory is a worker with work permit. That is, the vehicle software automatic configuration system 1 according to the second embodiment ensures that the worker and work location are authorized by verifying authentication information, such as dedicated equipment, tools, and dedicated certification dongles, that are associated with the worker and are held by the dealer or designated factory. Therefore, the vehicle software automatic configuration system 1 according to the second embodiment of the present invention has the same effects as the vehicle software automatic configuration system 1 according to the first embodiment and can further improve the safety of automatic service updates. Furthermore, the vehicle software automatic configuration system 1 according to the second embodiment of the present invention can ensure the validity of the installation of vehicle equipment and the installation procedure even when the vehicle location cannot be obtained, thereby providing safe automatic service updates.

[0118] Third Embodiment Next, a procedure for responding to an inquiry about the validity of the state of installed equipment at the management center 20 of the automatic vehicle software configuration system 1 according to a third embodiment of the present invention will be described. Note that the automatic vehicle software configuration system 1 according to the third embodiment of the present invention has the same configuration as the automatic vehicle software configuration system 1 according to the first embodiment, and therefore a duplicated description will be omitted.

[0119] In this embodiment, when the validity confirmation unit (validity confirmation unit 211) determines based on the device identification information that the device is a pre-authenticated device, the validity confirmation unit (validity confirmation unit 211) determines that the validity of the device identification information is approved and that the work permission for the device identification information is permitted. Furthermore, when the validity confirmation unit (validity confirmation unit 211) determines based on the device identification information that the device is not a pre-authenticated device, the validity confirmation unit (validity confirmation unit 211) determines that the validity of the device identification information is not approved and confirms with the vehicle owner whether the work permission for the device identification information is permitted. Furthermore, when the device identification information is permitted by the owner, the validity confirmation unit (validity confirmation unit 211) determines that the work permission for the device identification information is permitted. Specific processing procedures will be described with reference to FIG. 13 .

[0120] 13 is a flowchart showing the procedure for processing an inquiry about the validity of the state of an installed device in the management center 20 of the vehicle software automatic configuration system 1 according to this embodiment. As can be seen by comparing FIG. 13 with FIG. 7, in the third embodiment, the validity confirmation unit 211 of the management center 20 performs processing of step S3521 shown in FIG. 13 instead of step S352 in FIG.

[0121] In the process of step S3521, the validity confirmation unit 211 determines whether the device having the device ID included in the validity inquiry is an authenticated device. Here, an authenticated device is a device that has been pre-certified for the same vehicle model by the vehicle manufacturer. That is, in this embodiment, the validity confirmation unit 211 confirms the authentication information of a device with higher safety by checking the safety standards (see step S352 in FIG. 7). Note that the processes from step S3521 onwards are the same as the processes shown in FIG. 7, and therefore, repeated explanations will be omitted.

[0122] [Effects] As described above, the vehicle software automatic configuration system 1 according to the third embodiment of the present invention checks the authentication information of devices that are safer than the safety standards when verifying the validity of installed devices. Therefore, the vehicle software automatic configuration system 1 according to the third embodiment of the present invention has the same effects as the vehicle software automatic configuration system 1 according to the first embodiment and can further improve the safety of automatic service updates.

[0123] The present invention is not limited to the above-described embodiments, and various other applications and modifications are possible without departing from the spirit and scope of the present invention as defined in the claims. For example, the above-described embodiments provide detailed and specific descriptions of the configuration of the vehicle software automatic configuration system in order to clearly explain the present invention, and the present invention is not necessarily limited to systems including all of the described configurations. Furthermore, it is possible to replace some of the configurations of the embodiments described here with configurations of other embodiments, and it is also possible to add configurations of other embodiments to the configurations of one embodiment. Furthermore, it is also possible to add, delete, or replace other configurations with respect to some of the configurations of each embodiment. Furthermore, the control lines and information lines shown are those considered necessary for the explanation, and not all control lines and information lines are necessarily shown in the actual product. In reality, it is possible to consider that almost all of the configurations are interconnected.

[0124] 1... Vehicle software automatic setting system, 10... Vehicle control device, 11... Equipment, 12, 21... CPU, 13, 22... Storage device, 20... Management center, 121... Installed device ID recognition unit, 122... Implementation information change detection unit, 123, 211... Validity confirmation unit, 124... Vehicle software update unit, 125... Installed device confirmation result notification unit, 131, 221... Implementation information, 212... Software selection and distribution unit, 213... Implementation information update unit, 222... SW and setting management information

Claims

1. A vehicle software automatic configuration system comprising a vehicle control device and a management device, wherein the vehicle control device has an equipment change detection unit that detects equipment installed in a vehicle, an equipment information recognition unit that recognizes identification information of the equipment, and a validity inquiry unit that uses the identification information to inquire about the feasibility and validity of work on the equipment, and the management device has a validity confirmation unit that uses the identification information inquired by the validity inquiry unit to confirm the feasibility and validity of work on the equipment and respond to the vehicle control device, and a software selection and distribution unit that selects software related to the equipment that has been confirmed as work permitted by the validity confirmation unit and distributes it to the vehicle control device.

2. The vehicle software automatic configuration system of claim 1, wherein the vehicle control device is provided with a notification unit that, when the validity confirmation unit responds that the validity of the device is not approved, notifies a warning state indicating that the validity of the device is not approved.

3. The vehicle software automatic configuration system according to claim 2, wherein the vehicle control device includes a vehicle software application unit that applies the software selected and distributed by the software selection and distribution unit to the vehicle.

4. The vehicle software automatic configuration system of claim 1, wherein the feasibility of the work on the equipment includes the feasibility of the identification information and the feasibility of the installation procedure for the equipment, and the validity of the equipment includes the validity of the identification information and the validity of the installation procedure for the equipment.

5. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines, based on the vehicle's position information, that the vehicle's position is a work location for a pre-registered work permit, it determines that the validity of the equipment installation procedure is approved and that the work feasibility of the equipment installation procedure is work permit.

6. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines based on the vehicle's location information that the vehicle's location is not a work location for a pre-registered work permit, it determines that the validity of the equipment installation procedure is unapproved and confirms with the vehicle owner whether or not the equipment installation procedure can be carried out.

7. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines, based on specified authentication information for authenticating the worker who installed the equipment, that the worker is a worker with a pre-registered work permit, it determines that the validity of the equipment installation procedure is approved and that the suitability of the equipment installation procedure is permitted.

8. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines, based on specified authentication information for authenticating the worker who installed the equipment, that the worker is not a worker with a pre-registered work permit, it determines that the validity of the equipment installation procedure is not approved, and confirms with the owner of the vehicle whether or not the equipment installation procedure can be performed.

9. The vehicle software automatic configuration system according to claim 6, wherein the validity confirmation unit determines that the installation procedure of the device is permitted if the installation procedure of the device is permitted by the owner.

10. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines that the equipment meets the safety standards based on the identification information of the equipment, the validity of the identification information of the equipment is approved and the work permission for the identification information of the equipment is permitted.

11. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines that the equipment does not meet the safety standards based on the identification information of the equipment, it determines that the validity of the identification information of the equipment is unapproved and confirms with the owner of the vehicle whether or not work can be done on the identification information of the equipment.

12. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines that the equipment is a pre-authenticated equipment based on the identification information of the equipment, it determines that the validity of the identification information of the equipment is approved and that the work permission for the identification information of the equipment is permitted.

13. The vehicle software automatic configuration system of claim 4, wherein when the validity confirmation unit determines based on the identification information of the device that the device is not a previously authenticated device, it determines that the validity of the identification information of the device is unapproved and confirms with the owner of the vehicle whether or not work can be done on the identification information of the device.

14. The vehicle software automatic configuration system according to claim 11, wherein the validity confirmation unit determines that the work permission for the identification information of the device is permission for work when the identification information of the device is authorized by the owner.

15. A vehicle software automatic setting method in a vehicle software automatic setting system including a vehicle control device and a management device, wherein the vehicle control device includes a step of detecting equipment attached to the vehicle, a step of recognizing identification information of the equipment, and a step of inquiring about the possibility and validity of work on the equipment using the identification information, and the management device includes a step of confirming the possibility and validity of work on the equipment using the identification information inquired by the vehicle control device and responding to the vehicle control device, and a step of selecting software related to the equipment that has been confirmed to be permitted to be worked on, and distributing it to the vehicle control device.

16. A vehicle control device comprising: an implementation information change detection unit that detects equipment installed in a vehicle; an equipment information recognition unit that recognizes identification information of the equipment; and a validity inquiry unit that uses the identification information to inquire about the feasibility and validity of work on the equipment.

Images