AUTOMATIC VEHICLE SOFTWARE SETTING SYSTEM, AUTOMATIC SETTING PROCEDURE FOR VEHICLE SOFTWARE AND VEHICLE CONTROL UNIT

Abstract

This automatic vehicle software adjustment system comprises a vehicle control unit and an administration unit. The vehicle control unit includes: a device change detection unit that recognizes a device mounted on a vehicle; a device information recognition unit that recognizes the device's identification information; and a suitability query unit that uses the identification information to query the suitability and feasibility of working on a device. The management unit contains: a suitability confirmation unit, which uses the identification information requested by the suitability query unit to confirm the suitability and feasibility of work on the equipment and responds to the vehicle control unit; and a software selection and distribution unit, which selects software belonging to the equipment for which the suitability confirmation unit has confirmed that work is permitted and distributes the software to the vehicle control unit.

Description

Technical field

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

[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 (service) for the car through software and hardware updates after the sale, it is possible to extend the car's lifespan without diminishing its value. In recent years, the use of wireless communication has become established for updating vehicle software, and therefore, automakers are currently exploring online update methods. For example, PTL 1 proposes a technology for updating a car's software via wireless communication.

[0003] PTL 1 describes: “In a case where the first update is a hardware update, the control unit notifies the user terminal that the first update should be performed in a branch. In a case where the first update is a software update, the control unit notifies the user terminal that the first update should be performed via wireless communication.”

[0004] Incidentally, a car's hardware is typically updated by physically installing, replacing, and adjusting various components at an original equipment manufacturer (OEM) dealer, a specific factory, or similar location. Once the hardware update is complete, the software is updated using specialized equipment. Additionally, the car owner may select a new service offered as needed to update the vehicle's hardware and software. It's worth noting that with the exponential increase in hardware and software combinations, rewriting, adjusting, and similar software becomes more complex, and therefore, the workload for a dealer, factory, or similar location is expected to increase.As a solution to this problem, automatic software updates using Universal Plug and Play (UPnP) technology in cooperation with an OEM's management center are expected to reduce the software work required for hardware updates and reduce work errors. Citation list for patent literature

[0005] PTL 1: JP 2022-174678 A Overview of the invention Technical problem

[0006] When updating a vehicle's hardware and software to provide a new service, an automaker is responsible for preventing incidents that could lead to an accident. However, with vehicle hardware updates using UPnP technology, it can be difficult for an automaker to provide a service safely, for example, in cases where a modification to an installed device occurs, such as the installation of an unauthorized device, installation work by an unauthorized employee, or similar situations. Furthermore, with UPnP technology, another problem arises, for example, when software updates for a device installed in the car are performed without the car owner's consent.Note that PTL 1 does not mention the problems described above regarding automatic vehicle software updates using UPnP technology.

[0007] The present invention was made to solve the above problems, and one objective of the present invention is to provide a safe automatic data update that can ensure the suitability of the assembly and assembly method of a vehicle device. Solution to the problem

[0008] The present invention comprises a vehicle control unit and a management unit. The vehicle control unit includes a device change detection unit that recognizes a device mounted on a vehicle, a device information recognition unit that recognizes the device's identification information, and a suitability query unit that uses the identification information to query the suitability and feasibility of work on the device.The management unit contains a suitability confirmation unit, which uses the identification information requested by the suitability query unit to confirm the suitability and feasibility of work on the device and responds to the vehicle control unit, and a software selection and distribution unit, which selects software belonging to the device for which the suitability confirmation unit has confirmed that the work is permitted and distributes the software to the vehicle control unit. Advantageous effects of the invention

[0009] According to the present invention, it is possible to ensure the suitability of the assembly and assembly method of a vehicle device and to provide a safe automatic data update. Brief description of the drawings [ Fig. 1] Fig. Figure 1 is a diagram illustrating an example of a functional configuration of an automatic vehicle software setting system according to a first embodiment of the present invention. [ Fig. 2] Fig. Figure 2 is a flowchart illustrating a method for automatic software setting processing during a vehicle device exchange in the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 3] Fig. Figure 3 is a flowchart illustrating a method for processing the detection of changes to a mounted device in a vehicle control unit of the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 4] Fig. Figure 4 is a flowchart illustrating a method for processing an assembly method suitability request at the vehicle control unit of the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 5] Fig. Figure 5 is a flowchart illustrating a method for processing the response to an assembly method suitability request at an administrative center of the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 6] Fig. Figure 6 is a flowchart illustrating a method for processing the query of the suitability of the state of a mounted device at the vehicle control unit of the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 7] Fig. Figure 7 is a flowchart illustrating a method for processing the response to the query regarding the suitability of a mounted device at the management center of the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 8] Fig. Figure 8 is a flowchart illustrating a method for processing the acquisition of software and setting information at the vehicle control unit of the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 9] Fig. Figure 9 is a flowchart illustrating a method for processing the software selection and distribution in the management center of the automatic vehicle software setting system according to the first embodiment of the present invention. [ Fig. 10] Fig. Figure 10 is a block diagram illustrating a hardware configuration example of the vehicle control unit and management center according to the first embodiment of the present invention. [ Fig. 11] Fig. Figure 11 is a flowchart illustrating a method for processing a request for the suitability of an assembly method for a vehicle control device of an automatic vehicle software setting system according to a second embodiment of the present invention. [ Fig. 12] Fig. Figure 12 is a flowchart illustrating a method for processing a response to a request for the suitability of an assembly method at an administration center of the automatic vehicle software setting system according to the second embodiment of the present invention. [ Fig. 13] Fig. Figure 13 is a flowchart illustrating a method for processing a response to a request for the suitability of an installed device in an administration center of an automatic vehicle software setting system according to a third embodiment of the present invention. Description of the embodiments

[0010] Embodiments of the present invention are described below with reference to the accompanying drawings. In this description and the drawings, components that have essentially the same function or configuration are designated by the same reference numerals, and redundant descriptions are omitted. The present invention is applicable, for example, to a computing device for vehicle control with which an advanced driver assistance system (ADAS) or an electronic control unit (ECU) for autonomous driving (AD) in a vehicle can communicate. <Erste Ausführungsform> [Example of a functional configuration of an automatic vehicle software setting system]

[0011] First, an example of a functional configuration of an automatic vehicle software setting system 1 according to a first embodiment of the present invention is described. Fig. Figure 1 is a diagram illustrating an example of the functional configuration of the automatic vehicle software setting system 1 according to the present embodiment. As shown in Fig. As shown in Figure 1, the automatic vehicle software setting system 1 includes a vehicle control unit 10 and an administration center 20 (an example of an administration unit). The vehicle control unit 10 and the administration center 20 are connected to each other via a network that includes a public line such as the internet, a leased line, or the like, so that they are able to send and receive information data between them.

[0012] The vehicle control unit 10 is an example of an information processing unit that includes a central processing unit (CPU) 12, which performs various calculations, and a storage unit 13, and is installed in a vehicle to control the vehicle's operation. The CPU 12 and the storage unit 13 are interconnected via an internal bus, an adapter, or the like. Furthermore, several devices 11_1 to 11_n, which can be installed, exchanged, and removed, are connected to the vehicle control unit 10 via an internal bus, a gateway, or the like. In the following description, devices 11_1 to 11_n are referred to collectively as "device 11" where they are not differentiated.Device 11, for example, contains an arithmetic device such as a sensor, an actuator and a controller, and is a device for implementing a new vehicle service provided by an automobile manufacturer.

[0013] As in Fig. As shown in Figure 1, the CPU 12 contains a device information recognition unit (ID recognition unit 121 for installed devices), a device change detection unit (unit 122 for detecting changes to installation information), and a suitability query unit (suitability confirmation unit 123). Furthermore, the CPU 12 contains a vehicle software transfer unit (vehicle software update unit 124) and a notification unit (unit 125 for notifying the result of the installed device verification). The CPU 12 controls the operation of each of the above components.

[0014] The device information recognition unit (ID recognition unit 121 for mounted devices) recognizes identification information (e.g. ID: identification) of the device (device 11).

[0015] The device change detection unit (unit 122 for detecting changes to mounting information) detects a device mounted on the vehicle. In addition, unit 122 for detecting changes to mounting information detects a connection change, such as the replacement or removal of device 11, which is detected by the ID detection unit 121 for mounted devices.

[0016] The suitability query unit (suitability confirmation unit 123) uses the device's identification information to query the suitability and feasibility of work on the device. Feasibility of work on the device includes the feasibility of work on the device's identification information and the feasibility of work on the device's assembly procedure, while suitability of the device includes the suitability of the device's identification information and the suitability of the device's assembly procedure.

[0017] The vehicle software transfer unit (vehicle software update unit 124) transfers (updates) the software selected and distributed by a software selection and distribution unit (software selection and distribution unit 212) of the administrative facility (administrative center 20), which will be described later, to the vehicle.

[0018] If a suitability confirmation unit (Suitability Confirmation Unit 211), to be described later, responds to the administrative unit (Administrative Center 20) that the device is not approved, the notification unit (Unit 125 for notification of the result of the installed device verification) will issue a warning indicating that the device is not approved. Unit 125 for notification of the result of the installed device verification will notify the vehicle owner of this warning via a central vehicle panel, an on-board information terminal, a smartphone application used by the vehicle owner, or similar means.

[0019] The storage device 13 stores assembly information 131, the identification information (device ID) of the device 11, information on the suitability and feasibility of work on the device 11's identification information, information on the suitability and feasibility of work on the device 11's assembly procedure, and information on the software and settings used. Note that the assembly information 131 is stored in conjunction with the device ID.

[0020] As in Fig. As shown in Figure 1, the management center 20 is an example of the management unit, which contains a CPU 21 that performs various calculations and a storage unit 22. For example, it processes the confirmation of the suitability of an installed device in response to a request from the vehicle and selects and distributes the requested software to the vehicle. Note that the management center 20 may have a different vehicle management function than the processing described above. The CPU 21 contains the suitability confirmation unit (Suitability Confirmation Unit 211), the software selection and distribution unit (Software Selection and Distribution Unit 212), and an installation information update unit 213, and controls the operation of each unit.Note that a graphics processing unit (GPU) can be used instead of the CPU 21, or that the CPU 21 and the GPU can be used in combination. Furthermore, the Management Center 20 can be configured on a dedicated server or in the cloud.

[0021] The suitability confirmation unit (suitability confirmation unit 211) uses the device identification information queried by the suitability query unit (suitability confirmation unit 123 of the vehicle control unit 10) to confirm the suitability and feasibility of work on the device and responds to the vehicle control unit (vehicle control unit 10).

[0022] The software selection and distribution unit (Software Selection and Distribution Unit 212) selects software belonging to the device for which the suitability confirmation unit (Suitability Confirmation Unit 211) has confirmed that the work is permitted, and distributes the software to the vehicle control unit (Vehicle Control Unit 10). Note that the software belonging to the device includes vehicle software, device software, and setting information necessary for the operation of the device.

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

[0024] The storage device 22 stores the assembly information 221 of devices connected to all vehicles managed by the management center 20, as well as software (SW) and setting management information 222 including vehicle software, device software and setting information required to implement the vehicle service provided by the vehicle manufacturer. [Method for automatic software configuration processing accompanying a vehicle device change]

[0025] Next, a procedure for automatic software setting processing accompanying a vehicle device change in the automatic vehicle software setting system 1 is described. Fig. Figure 2 is a flowchart illustrating a procedure for the automatic software configuration processing accompanying a vehicle device change in the automatic vehicle software configuration system 1 according to the present embodiment. The processing described below begins when the vehicle is started.

[0026] First, unit 122 detects changes to the assembly information of the vehicle control unit 10, identifying a change in an installed device (step S100). Details of this processing will be described later with reference to Fig. 3 described.

[0027] Next, Unit 122 checks whether a change to the assembly information has occurred in the assembled device (step S110). During this process, if Unit 122 detects a change to the assembly information, it determines that a change to the assembled device exists and registers "Yes" in step S110. Conversely, if it does not detect a change to the assembled device, Unit 122 determines that no change to the assembled device exists and registers "No" in step S110.

[0028] During the processing of step S110, if unit 122 detects changes to assembly information and finds that there is no change to the assembled device (No in step S110), the processing of step S500 described later is carried out.

[0029] If, however, unit 122 detects changes to assembly information during the processing of step S110 and determines that a change exists in the assembled device (Yes in step S110), the processing of step S200 is carried out. During the processing of step S200, the suitability verification unit 123 queries the administrative center 20 to verify the suitability of the assembly procedure of the assembled device with the change. Furthermore, in this processing step, the suitability verification unit 123 updates the suitability of the assembly procedure in the assembly information 131 based on the response to the suitability query received from the administrative center 20. Note that details of this processing are described later with reference to Fig. 4. In the following description, an assembled device in which a change is detected can be abbreviated as "device", and "assembly procedure" can be abbreviated as "procedure".

[0030] Next, Suitability Assessment Unit 123 examines the rejection of the procedure's work based on the response to the suitability request from Administrative Center 20 (Step S210). If, during this processing, the response from Administrative Center 20 includes a "Work-Permitted" answer, Suitability Assessment Unit 123 determines that the procedure's work is permissible, and Step S210 will show "Yes." Conversely, if the response from Administrative Center 20 includes a "Work-Rejected" answer, Suitability Assessment Unit 123 determines that the procedure's work is rejected, and Step S210 will show "No."

[0031] During the processing of step S210, if the suitability confirmation unit 123 determines the rejection of the work of the procedure (“work-rejected” in step S210), the processing of step S500 described later is carried out.

[0032] If, however, during the processing of step S210, the Suitability Confirmation Unit 123 determines that the work of the procedure is permissible (“work-permitted” in step S210), the processing of step S300 is carried out. During the processing of step S300, the Suitability Confirmation Unit 123 queries the Administrative Center 20 for the suitability of the identification information (device ID) of the assembled device that has undergone a modification (step S300). Furthermore, during this processing, the Suitability Confirmation Unit 123 updates the suitability of the device ID in the assembly information 131 based on the response to the suitability query from Administrative Center 20. Note that details of this processing will be provided later with reference to Fig. 6. In the following description, the suitability of the identification information of an assembled device is referred to as "device state suitability," and the failure of the identification information of the assembled device to function is referred to as "device state failure."

[0033] Next, the Suitability Verification Unit 123 examines the equipment status's work refusal based on the response to the suitability query from Administrative Center 20 (step S310). If the response from Administrative Center 20 includes "Work Permitted," Suitability Verification Unit 123 determines that the equipment status is work permitted, and step S310 registers "Yes." Conversely, if the response from Administrative Center 20 includes "Work Rejected," Suitability Verification Unit 123 determines that the equipment status is work rejected, and step S310 registers "No."

[0034] If the Suitability Verification Unit 123 determines during the processing of step S310 that the device status is Work-Rejected (“Work-Rejected” in step S310), the processing of step S500, described later, is carried out.

[0035] If, however, the Suitability Confirmation Unit 123 determines during the processing of step S310 that the device status is "Permitted to Work" ("Permitted to Work" in step S310), the processing of step S400 is carried out. During the processing of step S400, the Vehicle Software Update Unit 124 performs the processing to adopt software and set information relating to the installed device. Note that the detailed processing in step S400 is described later with reference to Fig. 8 is described.

[0036] Step S500 is processed if "No" is detected in step S110, if "Work Rejected" is detected in step S210, if "Work Rejected" is detected in step S310, or after processing in step S400. During step S500, the suitability confirmation unit 123 of the vehicle control unit 10 confirms the suitability of all installed devices of its own facility. Furthermore, during this processing, the suitability confirmation unit 123 confirms the suitability of the device condition and the suitability of the procedure in the installation information 131, which is assigned to each device's device ID. Additionally, during this process, the vehicle control unit 10 shares the installation information 131 with the management center 20 via the network.The assembly information update unit 213 of the administrative center 20 updates the assembly information 131 shared by the vehicle control unit 10 to the assembly information 221 of the administrative center 20.

[0037] Next, the Suitability Verification Unit 123 checks whether any of the assembled devices have a suitability that is not approved (Step S510). If, during this processing of Step S500, the Suitability Verification Unit 123 confirms that the device condition suitability and the procedure suitability are "approved" in the assembly information 131 associated with the device IDs of all devices, it determines that there is no non-approved device, and Step S510 returns "No". Conversely, if, during the processing of Step S500, the Suitability Verification Unit 123 confirms that there is a device whose device condition suitability and / or procedure suitability is "not approved" in the assembly information 131 associated with a device ID, it determines that there is a non-approved device, and Step S510 returns "Yes".

[0038] If, during the processing of step S510, the conformity verification unit 123 detects the presence of a non-approved device (Yes in step S510), the unit 125 notifies the vehicle owner of a warning condition indicating the non-approved condition of the installed device (step S520). Note that the warning notification to the vehicle owner can be delivered via the owner's smartphone application or displayed on a central control panel in the vehicle. During this processing, the warning notification for non-approved procedure conformity and non-approved device condition can be delivered separately.

[0039] If, however, the suitability confirmation unit 123 determines during the processing of step S510 that no non-approved device is present (No in step S510), the unit 125 cancels the warning notification (step S530) to notify the result of the verification of the installed device. After the processing of step S520 or step S530, the automatic software configuration processing associated with a vehicle device change ends. [Method for processing the detection of a change to a mounted device in a vehicle control unit]

[0040] Next, a method for processing the detection of a change in a mounted device in the vehicle control unit 10 of the automatic vehicle software setting system 1 is described. Fig. Figure 3 is a flowchart illustrating a method for processing the detection of a change in a mounted device in the vehicle control unit 10 of the automatic vehicle software setting system 1 according to the present embodiment. The processing described below is implemented as a subroutine in step S100 of the flowchart in Figure 3. Fig. The processing shown in section 2 was called and executed.

[0041] First, the ID recognition unit 121 for mounted devices of the vehicle control unit 10 recognizes the device IDs of all mounted devices of the vehicle (step S101).

[0042] Next, unit 122 for detecting changes to assembly information of the vehicle control unit 10 starts a loop processing for the number of devices detected by the ID recognition unit 121 for mounted devices (step S102).

[0043] Next, Unit 122, which detects changes to assembly information, captures a detected device ID (step S103). Note that each time the loop processing is repeated, Unit 122 captures the device IDs sequentially.

[0044] Next, unit 122, for the detection of changes to assembly information, checks whether the captured device ID is present in the assembly information 131 (step S104).

[0045] If, during the processing of step S104, it determines that the device ID is not present in the assembly information 131 (No in step S104), the unit 122 for detecting changes to assembly information updates (registers) the new assembly of the device in the assembly information 131 (step S105).

[0046] On the other hand, unit 122 for detecting changes to assembly information during the processing of step S104 terminates the current loop processing (step S106) if it determines that the device ID is present in the assembly information 131 (Yes in step S104), or after the processing of step S105.

[0047] After the processing in step S102 to step S106 has been carried out for all devices, unit 122 checks for changes to assembly information to see if there is an unsought device ID in the assembly information 131 (step S107).

[0048] If, during the processing of step S107, it detects that there is an unsought device ID in the assembly information 131 (Yes in step S107), the unit 122 for detecting changes to assembly information updates the disassembly of the device (performs a removal) in the assembly information 131 (step S108).

[0049] On the other hand, the processing to detect a change to an assembled device ends when the unit 122 for detecting changes to assembly information during the processing of step S107 determines that there is no unsearched device ID in the assembly information 131 (No in step S107), or after the processing of step S108. [Method for processing the query regarding the suitability of the procedure at the vehicle control unit]

[0050] Next, a method for processing the query regarding the suitability of an assembly procedure at the vehicle control unit 10 of the automatic vehicle software setting system 1 is described. Fig. Figure 4 is a flowchart illustrating a method for processing the query regarding the suitability of an assembly method at the vehicle control unit 10 of the automatic vehicle software setting system 1 according to the present embodiment. The processing described below is carried out in step S200 of the Fig. The processing shown in section 2 is called and executed as a subroutine.

[0051] First, the suitability confirmation unit 123 of the vehicle control unit 10 acquires position information of the vehicle at the time of the initial detection of the connection of the mounted device in order to identify the work location (step S201). Note that the vehicle's position information is calculated, for example, by comparing GPS information, camera or sensor data such as a light detection and ranging (LiDAR) system, and the like with map information.

[0052] Next, the suitability confirmation unit 123 sends the captured position information of the vehicle to the management center 20 and queries the suitability of the equipment assembly procedure (step S202). In this processing, the management center 20 confirms the feasibility of the work and the suitability of the assembly procedure in response to the procedure suitability query it received from the vehicle control unit 10, and returns a confirmation result to the vehicle control unit 10. Note that the processing of the assembly procedure suitability query in the management center 20 is later described with reference to Fig. 5 is described in detail.

[0053] Next, Suitability Confirmation Unit 123 determines the feasibility of the work based on the confirmation result returned by Administrative Centre 20 (Step S203).

[0054] If the suitability confirmation unit 123 determines during the processing of step S203 that “Job Rejected” is included in the returned confirmation result (“Job Rejected” in step S203), the processing of the procedure suitability query ends.

[0055] However, if the suitability confirmation unit 123, when processing step S203, determines that "authorised to work" is included in the returned confirmation result, the suitability of the procedure is established (step S204).

[0056] If, during the processing of step S204, the suitability verification unit 123 determines that the suitability of the procedure contained in the returned verification result is "approved" ("approved" in step S204), the processing of step S205 is carried out. During the processing of step S205, the suitability verification unit 123 updates the procedure suitability associated with the device ID of the assembled device in the assembly information 131 to "approved" (step S205).

[0057] If, however, the suitability confirmation unit 123 determines during the processing of step S204 that the suitability of the procedure contained in the returned confirmation result is "not approved" ("not approved" in step S204), the processing of step S206 is carried out. During the processing of step S206, the suitability confirmation unit 123 updates the procedure suitability associated with the device ID of the assembled device in the assembly information 131 to "not approved". If "Work rejected" is determined in step S203, the processing of the procedure suitability query ends after the processing of step S205 or step S206. [Procedure for processing the suitability query for assembly procedures in the administrative center]

[0058] Next, the processing of the suitability query for an assembly procedure in the administration center 20 of the automatic vehicle software setting system 1 is described. If, during this processing, it determines, based on the vehicle's position information, that the vehicle's position is a work site with a pre-registered work permit, the suitability confirmation unit (suitability confirmation unit 211) determines that the suitability of the device pre-assembly procedure is approved and that the feasibility of the work on the device pre-assembly procedure is work-permitted.Furthermore, if the Suitability Confirmation Unit (Suitability Confirmation Unit 211) determines, based on the vehicle's location information, that the vehicle's location is not a workplace with a pre-registered work permit, that the suitability of the equipment assembly procedure is not authorized, and confirms to the vehicle owner the feasibility of the work on the equipment assembly procedure. Furthermore, if the assembly procedure for the equipment is authorized by the owner, the Suitability Confirmation Unit (Suitability Confirmation Unit 211) determines that the feasibility of the work on the equipment assembly procedure is permitted. A specific processing procedure is described with reference to... Fig. 5 described.

[0059] Fig. Figure 5 is a flowchart illustrating a procedure for processing a response to a query regarding the suitability of the assembly procedure in the management center 20 of the automatic vehicle software setting system 1 according to the present embodiment. The processing described below begins when the management center 20 receives a suitability request for the assembly procedure from the vehicle.

[0060] First, the suitability confirmation unit 211 of the administrative center 20 receives a suitability request for the assembly procedure (step S251).

[0061] Next, the Suitability Confirmation Unit 211 examines whether the vehicle's location information included in the suitability request is a work location approved by the vehicle manufacturer (step S252). Note that a work location approved by the vehicle manufacturer is, for example, a dealership, a specific factory, or similar.

[0062] If, during the processing of step S252, it determines that the vehicle's position information represents a work site with a work permit previously registered in storage device 22 (Yes in step S252), the suitability confirmation unit 211 updates the suitability of the assembly procedure to "approved" (step S253). During this processing, the suitability confirmation unit 211 updates the procedure suitability associated with the device ID of the assembled device in the assembly information 221 to "approved".

[0063] On the other hand, if during the processing of step S252 it determines that the vehicle's position information does not represent a work location previously registered in the storage device 22 (No in step S252), the suitability confirmation unit 211 confirms to the vehicle owner the feasibility of the work (step S254).

[0064] Next, the Suitability Assessment Unit 211 investigates whether the owner's response is "Permitted to work" (Step S255).

[0065] If, during the processing of step S255, the owner's response is Work-rejected (No in step S255), the Suitability Confirmation Unit 211 responds Work-rejected to the Vehicle Control Unit 10 (step S256).

[0066] However, if the owner's response during processing step S255 is "Work permitted" (Yes in step S255), the suitability confirmation unit 211 updates the suitability of the assembly procedure to "not approved" (step S257). During this processing, the suitability confirmation unit 211 updates the procedure suitability associated with the device ID of the assembled device in the assembly information 221 to "not approved".

[0067] After processing step S253 or step S257, the suitability confirmation unit 211 responds to the vehicle control unit 10 with the work permit and the updated procedure suitability (step S258). After processing step S256 or step S258, the suitability query response processing of the assembly procedure ends in the administration center 20. [Method for processing the suitability query of the state of a mounted device in the vehicle control unit]

[0068] Next, a procedure for processing the suitability query of the state of a mounted device in the vehicle control unit 10 of the automatic vehicle software setting system 1 is described. Fig. Figure 6 is a flowchart illustrating a procedure for processing the suitability query of a mounted device state in the vehicle control unit 10 of the automatic vehicle software setting system 1 according to the present embodiment. The processing described below is carried out in step S300 of the Fig. The processing shown in section 2 is called and executed as a subroutine.

[0069] First, the suitability confirmation unit 123 of the vehicle control unit 10 queries the management center 20, using the device ID of the mounted device as a key, for the suitability of the device state (step S301). Furthermore, during this processing, the management center 20 confirms the suitability and feasibility of the work in response to the suitability query of the device state received from the vehicle control unit 10 and sends a confirmation result back to the vehicle control unit 10. Note that the processing of the response to the suitability query of the mounted device state in the management center 20 is later carried out with reference to Fig. 7 is described in detail.

[0070] Next, Suitability Confirmation Unit 123 examines the feasibility of the work based on the confirmation result returned by Administrative Centre 20 (Step S302).

[0071] If the returned confirmation result contains “Work Rejected” during the processing of step S302 (“Work Rejected” in step S302), the suitability confirmation unit 123 terminates the suitability query processing of the assembled device.

[0072] However, if the returned confirmation result contains “Work-permitted” during the processing of step S302 (“Work-permitted” in step S302), the suitability confirmation unit 123 examines the suitability of the equipment condition based on the confirmation result (step S303).

[0073] If, during the processing of step S303, the suitability verification unit 123 determines that the suitability of the device condition contained in the returned verification result is "approved" ("approved" in step S303), the processing of step S304 is carried out. During the processing of step S304, the suitability verification unit 123 updates the suitability of the device condition associated with the device ID of the mounted device in the assembly information 131 to "approved".

[0074] If, on the other hand, the suitability of the device condition contained in the returned confirmation result is "not permitted" ("not permitted" in step S303), the suitability confirmation unit 123 performs the processing of step S305 while processing step S303. During the processing of step S305, the suitability confirmation unit 123 updates the device condition suitability associated with the device ID of the mounted device in the assembly information 131 to "not permitted". If "Work-rejected" is determined in step S302, the suitability query processing of the mounted device condition ends after the processing of step S304 or step S305. [Procedure for processing the response to the suitability request regarding the condition of the installed device at the administrative center]

[0075] Next, the processing of the response to the suitability query regarding the condition of the mounted device in the management center 20 of the automatic vehicle software adjustment system 1 is described. If, during this processing, it determines that the device meets a safety standard based on the device's identification information, the suitability confirmation unit (suitability confirmation unit 211) determines that the suitability of the device's identification information is approved and that work on the device's identification information is permitted.Furthermore, if the Suitability Confirmation Unit (Suitability Confirmation Unit 211) determines, based on the device's identification information, that the device does not meet a safety standard, it determines that the suitability of the device's identification information is not approved and confirms to the vehicle owner the feasibility of working on the device's identification information. Furthermore, if the owner approves the device's identification information, the Suitability Confirmation Unit (Suitability Confirmation Unit 211) determines that the feasibility of working on the device's identification information is permitted. A specific processing procedure is described with reference to [reference to relevant document]. Fig. 7 described.

[0076] Fig. Figure 7 is a flowchart illustrating a procedure for processing responses to suitability requests from the mounted device in the management center 20 of the automatic vehicle software adjustment system 1 according to the present embodiment. The processing described below begins when the management center 20 receives a suitability request from the vehicle regarding the condition of the mounted device.

[0077] First, the Suitability Confirmation Unit 211 of Administrative Center 20 receives a suitability request regarding the condition of the installed equipment (step S351).

[0078] Next, the Suitability Verification Unit 211 examines whether a device with a device ID included in the suitability request meets a safety standard that represents the minimum standard in terms of safety or emission control technology (step S352).

[0079] If, during processing step S352, it determines that the device meets the safety standard (Yes in step S352), the suitability verification unit 211 updates the suitability of the mounted device's condition to "approved" (step S353). During this processing, the suitability verification unit 211 updates the device condition suitability associated with the mounted device's device ID in the mounting information 221 to "approved".

[0080] If, on the other hand, during the processing of step S352 it determines that the device does not meet the safety standard (No in step S352), the suitability confirmation unit 211 confirms to the owner of the vehicle the feasibility of the work (step S354).

[0081] Next, the Suitability Assessment Unit 211 investigates whether the owner of the vehicle's response is "Permitted to work" (Step S355).

[0082] If, during the processing of step S355, it determines that the owner's response is "Work-rejected" (No in step S355), the vehicle control unit 10's suitability confirmation unit 211 responds with "Work-rejected" (step S356).

[0083] However, if, during the processing of step S355, it determines that the owner's response is "Work permitted" (Yes in step S355), the Suitability Confirmation Unit 211 updates the suitability of the installed equipment's condition to "Not permitted" (step S357). During this processing, the Suitability Confirmation Unit 211 updates the equipment condition suitability associated with the installed equipment's device ID in the installation information 221 to "Not permitted".

[0084] After processing in step S353 or step S357, the suitability confirmation unit 211 responds with "Work permitted" and the updated device suitability to the vehicle control unit 10 (step S358). After processing in step S356 or step S358, the processing of the suitability query regarding the status of the mounted device ends in the management center 20. [Method for processing the transfer of software and setting information in the vehicle control unit]

[0085] Next, a procedure for the transfer processing of software and setting information at the vehicle control unit 10 is described. Fig. Figure 8 is a flowchart illustrating a procedure for the transfer processing of software and setting information at the vehicle control unit 10 of the automatic vehicle software setting system 1 according to the present embodiment. The processing described below is carried out in step S400 of the Fig. The processing shown in section 2 is called and executed as a subroutine.

[0086] First, the vehicle software update unit 124 of the vehicle control unit 10 requests the management center 20 to distribute software and setting information belonging to the installed device (step S401). In this processing, the management center 20 selects the software and setting information belonging to the installed device in response to the request received from the vehicle control unit 10 to distribute the software and setting information and distributes the selected software and setting information to the vehicle control unit 10. Note that the software selection and distribution processing in the management center 20 is later described with reference to Fig. 9 will be described in detail.

[0087] Next, the vehicle software update unit 124 receives the software and setting information from the management center 20 and performs a buffering operation (step S402).

[0088] Next, the vehicle software update unit 124 checks whether a vehicle software update is available (step S403). If the received software contains vehicle software, the vehicle software update unit 124 compares the received vehicle software version information with the version information of the vehicle software in operation and makes a decision based on the comparison result. If the received vehicle software version information differs from the version information of the vehicle software in operation, the vehicle software update unit 124 determines that an update is available, and "Yes" is determined in step S403.However, if the received version information of the vehicle software matches the version information of the vehicle software in operation, the vehicle software update unit 124 determines that no update is available, and in step S403, "No" is determined.

[0089] If, during the processing of step S403, it determines that an update for the vehicle software is available (Yes in step S403), the vehicle software update unit 124 adopts the received vehicle software (step S404).

[0090] If, however, during the processing of step S403, it determines that no update is available for the vehicle software (No in step S403), or after the processing of step S403, the vehicle software update unit 124 checks whether an update is available for the setting information (step S405). During this processing, the vehicle software update unit 124 compares the received setting information with the operating setting information and makes a decision based on the comparison result. If the received setting information differs from the operating setting information, the vehicle software update unit 124 determines that an update is available, and "Yes" is determined in step S405.However, if the received setting information matches the operating setting information, the vehicle software update unit 124 determines that no update is available, and step S405 indicates "No".

[0091] If, during the processing of step S405, it detects that an update for the setting information is available (Yes in step S405), the vehicle software update unit adopts the received setting information (step S406).

[0092] If, however, during the processing of step S405, it determines that no update is available for the settings information (No in step S405), or after processing step S406, the vehicle software update unit 124 checks whether an update is available for the device software (step S407). During this process, the vehicle software update unit 124 compares the received version information of the device software with the version information of the operating device software and makes a decision based on the comparison. If the received version information of the device software differs from the version information of the operating device software, the vehicle software update unit 124 determines that an update is available, and "Yes" is determined in step S407.However, if the received version information of the device software matches the version information of the operating device software, the vehicle software update unit 124 determines that no update is available, and in step S407, "No" is determined.

[0093] If, during the processing of step S407, it determines that an update for the device software is available (Yes in step S407), the vehicle software update unit 124 adopts the received device software (step S408).

[0094] However, if the vehicle software update unit 124 detects during the processing of step S407 that no update for the device software is available (No in step S407), or after the processing of step S408, the transfer processing of the software and setting information ends. [Procedure for software selection and distribution processing in the administrative headquarters]

[0095] Next, a procedure for software selection and distribution processing in the administrative center 20 is described. Fig. Figure 9 is a flowchart illustrating a procedure for software selection and distribution processing in the management center 20 of the automatic vehicle software setting system 1 according to the present embodiment. The processing described below begins when the management center 20 receives a software distribution request from the vehicle control unit 10.

[0096] First, the software selection and distribution unit 212 of the administrative center 20 receives a software distribution request (step 54011).

[0097] 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 uses the assembly information 131, which is associated with the device ID contained in the received distribution request, and a service menu provided by the vehicle manufacturer for the vehicle, as keys to select the vehicle software, device software, and setting information verified by the vehicle manufacturer from the software and setting management information 222 of the storage device 22.

[0098] Next, the software selection and distribution unit 212 distributes the selected software and setting information to the vehicle control unit 10 (step S4013). After processing step S4013, the software selection and distribution process ends. Note that a standardized wireless communication method can be used as the distribution method. [Hardware configuration example for the vehicle control unit and management center]

[0099] Next, a hardware configuration example of an information processing unit 30, which forms the vehicle control unit 10 and the management center 20, is described. Fig. Figure 10 is a block diagram showing a hardware configuration example of the vehicle control unit 10 and the management center 20 according to the present embodiment.

[0100] As in Fig. As shown in Figure 10, the information processing device 30 contains a CPU 30a, a read-only memory (ROM) 30b, a random-access memory (RAM) 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 interconnected by a bus 30f, enabling them to send and receive information data to and from each other.

[0101] The CPU 30a is an example of the CPU 12 of the vehicle control unit 10 and the CPU 21 of the management center 20, and controls the operation of each unit in the vehicle control unit 10 or the management center 20. Note that a graphics processing unit (GPU) can be used instead of the CPU 30a, or that the CPU 30a and the GPU can be used in combination.

[0102] The ROM 30b, for example, contains a storage medium such as non-volatile memory and stores programs, data, and the like, which are executed and referenced by the CPU 30a.

[0103] The RAM 30c, for example, contains a storage medium such as volatile memory and temporarily stores information (data) required for any processing performed by the CPU 30a.

[0104] The storage device 30d contains a non-volatile, computer-readable recording medium that stores a program to be executed by the CPU 30a, and includes a storage device 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 unit 20, and stores the assembly information 131, the assembly information 221, the software and settings management information 222, and the like, which are contained in Fig. The memory device 30d, as described in Section 1, stores a program for the CPU 30a to control each unit, a program such as an operating system (OS) and a controller, as well as data. Note that some of the program and data stored in the memory device 30d may be stored in the ROM 30b. The computer-readable, non-volatile recording medium that stores the program executed by the CPU 30a is not limited to the HDD and can be a recording medium such as a solid-state drive (SSD), a compact disc (CD)-ROM, or a digital versatile disc (DVD)-ROM.

[0105] The input and output interface 30e sends and receives information data to and from the exterior of the information processing unit 30 under the control of the CPU 30a. [Effects]

[0106] As described above, the vehicle control unit 10 of the automatic vehicle software setting system 1, according to the present embodiment, detects a modification to the installed device and queries the vehicle's management center 20 regarding the status of the modified device and the suitability of the device's installation procedure (device suitability). Furthermore, the management center 20 of the automatic vehicle software setting system 1 confirms the suitability and feasibility of the work and sends a confirmation result back to the vehicle control unit 10. In addition, the vehicle control unit 10 requests the management center 20 to distribute the software and setting information associated with the modification to the installed device and only transfers the software and setting information to the host vehicle if work on the device's status and installation procedure is permissible.Furthermore, the vehicle control unit 10 notifies the vehicle owner of a warning condition indicating the lack of approval for a device whose suitability has not been granted. That is, the automatic vehicle software setting system 1 selects software (a service) belonging to a device that meets a safety standard at a workplace approved by the vehicle manufacturer or the vehicle owner, and automatically installs (updates) the selected software on the vehicle. Additionally, the automatic vehicle software setting system 1 notifies the vehicle owner of devices whose suitability has not been granted, enabling the vehicle owner to verify the suitability of the device installed on the vehicle.Therefore, according to the automatic vehicle software setting system 1 of the present embodiment, it is possible to ensure the suitability of the assembly and assembly method of a vehicle device and to provide a safe automatic service update. <Zweite Ausführungsform>

[0107] Next, a method for processing a suitability query of an assembly process in a vehicle control unit 10 of an automatic vehicle software setting system 1 according to a second embodiment of the present invention is described. Since the automatic vehicle software setting system 1 according to the second embodiment of the present invention has the same configuration as the automatic vehicle software setting system 1 according to the first embodiment, a redundant description is omitted.

[0108] Fig. Figure 11 is a flowchart illustrating a method for processing a suitability query of the assembly process at the vehicle control unit 10 of the automatic vehicle software setting system 1 according to the present embodiment. As can be seen by comparing Fig. 11 and Fig. As can be seen in section 4, in the second embodiment, a suitability confirmation unit 123 does not record any position information of the vehicle at the time of the first detection of the connection of a mounted device (step S201 in Fig. 4), but instead introduces the in Fig. The processing of step S2011 is shown in section 11. Note that, with the exception of step S2011, every step in Fig. 11 processing shown with each in Fig. The processing described in step 4 is identical, and therefore a redundant description is omitted.

[0109] During the processing of step S2011, predetermined authentication information is collected to authenticate the worker who installed the device. The eligibility confirmation unit 123 of the vehicle control unit 10 collects predetermined authentication information at a dealer or a specific plant. This information includes authentication information from a certification body that certifies the worker's authorization to connect a vehicle-specific diagnostic tool (On-Board Diagnostics 2 (ODB2)) intended for each worker, and authentication information (password, biometric authentication, or the like) from an authentication device (e.g., the worker's smartphone) that is individually owned by the worker.In addition, the suitability confirmation unit 123 sends the captured predetermined authentication information to an administrative center 20 and queries the suitability of the assembly procedure (step S202).

[0110] Conversely, when the suitability query for the assembly procedure of the vehicle control device 10 is received, the management center 20 processes the response to the suitability query for the assembly process. In the present embodiment, a suitability confirmation unit (suitability confirmation unit 211), based on predetermined authentication information for authenticating the worker who assembled the device, determines that the worker is a worker with a pre-registered work permit, that the suitability of the device assembly procedure is approved, and that the feasibility of the work of the device assembly procedure is work-permitted.Furthermore, if, based on predetermined authentication information used to authenticate the worker who assembled the device, it determines that the worker is not a worker with a pre-registered work permit, the Suitability Confirmation Unit (Suitability Confirmation Unit 211) determines that the suitability of the device assembly procedure is not approved and confirms to the vehicle owner the feasibility of the work on the device assembly procedure. Additionally, in a case where the device assembly procedure is approved by the owner, the Suitability Confirmation Unit (Suitability Confirmation Unit 211) determines that the feasibility of the work on the device assembly procedure is work-approved. A specific processing procedure is described with reference to [reference to relevant document]. Fig. 12 described.

[0111] Fig. Figure 12 is a flowchart illustrating a procedure for processing the responses to suitability queries of the assembly process in the management center 20 of the automatic vehicle software setting system 1 according to the present embodiment. As can be seen by comparing Fig. 12 and Fig. As can be seen in Figure 5, the suitability confirmation unit 211 of the administrative center 20, in the second embodiment, performs the processing of step S2521 and step S2522, which are described in Figure 5. Fig. 12 are shown, instead of step S252 from Fig. 5 through.

[0112] During the processing of step S2521, the suitability confirmation unit 211 compares the predetermined authentication information contained in the received suitability request with the predetermined authentication information previously registered in the storage device 22 in order to authenticate the worker.

[0113] Next, the Eligibility Confirmation Unit 211 determines whether the worker is a worker with a work permit (step S2522). If, in this processing step, the predetermined authentication information contained in the received eligibility request matches the pre-registered predetermined authentication information, Eligibility Confirmation Unit 211 determines that the worker is a worker with a work permit, and "Yes" is determined in step S2522. Conversely, if the predetermined authentication information contained in the received eligibility request does not match the pre-registered predetermined authentication information, Eligibility Confirmation Unit 211 determines that the worker is not a worker with a work permit, and "No" is determined in step S2522.

[0114] If, during the processing of step S2522, it determines that the worker is a worker with a work permit (Yes in step S2522), the Suitability Confirmation Unit 211 carries out the processing of step S253.

[0115] If, however, during the processing of step S2522, it determines that the worker is not a worker with a work permit (No in step S2522), the Suitability Confirmation Unit 211 carries out the processing of step S254. Note that any processing after step S2522 is linked to any processing in Fig. The processing described in section 5 is identical, and therefore a redundant description is omitted. [Effects]

[0116] As described above, according to the second embodiment of the present invention, the automatic vehicle software setting system 1 does not confirm the suitability of the work location, but rather confirms whether the worker is at the dealership or is a worker with a work permit at the designated factory. That is, according to the second embodiment, the automatic vehicle software setting system 1 ensures an authorized worker and a work location by confirming authentication information, such as a dedicated device, tool, certification dongle, and the like, assigned to the worker and stored at a dealership, a specific factory, or the like.Therefore, the automatic vehicle software setting system 1 according to the second embodiment of the present invention has the same effect as the automatic vehicle software setting system 1 according to the first embodiment and can further improve the reliability of the automatic service update. Furthermore, according to the automatic vehicle software setting system 1 of the second embodiment of the present invention, even in a case where the vehicle position cannot be detected, it is possible to ensure the suitability of the mounting and mounting method of a vehicle device and to provide a reliable automatic service update. <Dritte Ausführungsform>

[0117] Next, a method for processing responses to suitability requests regarding the condition of an assembled device in an administration center 20 of an automatic vehicle software adjustment system 1 according to a third embodiment of the present invention is described. Since the automatic vehicle software adjustment system 1 according to the third embodiment of the present invention has the same configuration as the automatic vehicle software adjustment system 1 according to the first embodiment, a redundant description is omitted.

[0118] In the present embodiment, if, based on the device's identification information, it determines that the device has been previously authenticated, a suitability confirmation unit (Suitability Confirmation Unit 211) determines that the device's identification information is suitable and that work on the device's identification information is permitted. Furthermore, if, based on the device's identification information, it determines that the device has not been previously authenticated, the suitability confirmation unit (Suitability Confirmation Unit 211) determines that the device's identification information is not suitable and confirms to the vehicle owner that work on the device's identification information is permitted.If the owner permits the processing of the device's identification information, the Suitability Certification Unit (Suitability Certification Unit 211) also determines that the work on the device's identification information is feasible. A specific processing procedure is described with reference to [reference to relevant document]. Fig. 13 described.

[0119] Fig. Figure 13 is a flowchart illustrating a procedure for processing a response to a suitability query regarding the condition of the mounted device in the management center 20 of the automatic vehicle software setting system 1 according to the present embodiment. As can be seen by comparing Fig. 13 and Fig. As can be seen in Figure 7, the suitability confirmation unit 211 of the administrative center 20, in the third embodiment, performs the following: Fig. 13. Processing of step S3521 instead of step S352 shown. Fig. 7 through.

[0120] During the processing of step S3521, the suitability confirmation unit 211 checks whether the device with the device ID contained in the suitability query is an authenticated device. An authenticated device is one where the installed device has been previously authenticated by the vehicle manufacturer in the same vehicle type. That is, in the present embodiment, the suitability confirmation unit 211 confirms the safety standard (see step S352 in Fig. 7) to confirm the device's authentication information with greater security. Note that any processing after step S3521 is combined with any in Fig. The processing described in section 7 is identical, and therefore a redundant description is omitted. [Effects]

[0121] As described above, the automatic vehicle software setting system 1 according to the third embodiment of the present invention confirms the authentication information of a device that exhibits a higher level of security than the security standard when it confirms the suitability of the installed device. Therefore, the automatic vehicle software setting system 1 according to the third embodiment of the present invention has the same effect as the automatic vehicle software setting system 1 according to the first embodiment and can further improve the security of the automatic service update.

[0122] It should be noted that the present invention is not limited to the embodiments described above and that, of course, various other application examples and modifications can be made without deviating from the core of the invention described in the claims.

[0123] For example, the embodiments described above describe the configuration of the automatic vehicle software adjustment system in detail and specifically, in order to describe the present invention in an easily understandable way, but the invention does not necessarily include all described configurations. Furthermore, part of the configuration of the embodiment described here can be replaced by a configuration of another embodiment, and furthermore, the configuration of another embodiment can be added to the configuration of a particular embodiment. Moreover, it is also possible to add, remove, and replace other configurations for a part of the configuration of each embodiment.

[0124] Furthermore, the control and information lines indicate what is deemed necessary for the description and do not necessarily show all control and information lines on the product. In practice, it can be assumed that almost all configurations are interconnected. Reference symbol list 1 Automatic vehicle software setting system 10 Vehicle control unit 11 device 12, 21 CPU 13, 22 Storage device 20 Administrative Center 121 ID recognition unit for mounted devices 122 Assembly information Unit for detecting changes of 123, 211 Suitability Confirmation Unit 124 Vehicle software update unit 125 Unit for notification of the result of the inspection of the installed device 131, 221 Assembly information 212 Software Selection and Distribution Unit 213 Assembly Information Update Unit 222 Software and hiring management information QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] JP 2022-174678 A

[0005]

Claims

[1] Automatic vehicle software setting system comprising a vehicle control unit and a management unit, where The vehicle control unit contains: a device change detection unit that recognizes a device mounted on a vehicle, a device information recognition unit that recognizes the device's identification information, and a suitability query unit that uses the identification information to query the suitability and feasibility of work on the device, and The administrative facility contains: a suitability confirmation unit that uses the identification information queried by the suitability query unit to confirm the suitability and feasibility of work on the device, and responds to the vehicle control unit, and a software selection and distribution unit that selects software belonging to the device for which the suitability confirmation unit has confirmed that work is permitted and distributes the software to the vehicle control unit. [2] Automatic vehicle software setting system according to claim 1, wherein the vehicle control unit includes a notification unit that reports a warning condition indicating that the suitability of the device is not approved when the suitability confirmation unit responds that the suitability of the device is not approved. [3] Automatic vehicle software setting system according to claim 2, wherein the vehicle control unit includes a vehicle software takeover unit which takes over the software selected and distributed by the software selection and distribution unit on the vehicle. [4] Automatic vehicle software adjustment system according to claim 1, wherein the feasibility of work on the device includes the feasibility of work on the identification information and the feasibility of work on an assembly procedure of the device, and The suitability of the device includes the suitability of the identification information and the suitability of the device's assembly procedure. [5] Automatic vehicle software setting system according to claim 4, wherein the suitability confirmation unit, upon determining on the basis of position information of the vehicle that a position of the vehicle is a workplace with a pre-registered work permit, determines that the suitability of the assembly method of the device is approved and that the feasibility of work on the assembly method of the device is permitted. [6] Automatic vehicle software adjustment system according to claim 4, wherein the suitability confirmation unit, upon determining on the basis of position information of the vehicle that a position of the vehicle is not a workplace with a pre-registered work permit, determines that the suitability of the assembly method of the device is not permitted and confirms the feasibility of work on the assembly method of the device to an owner of the vehicle. [7] Automatic vehicle software setting system according to claim 4, wherein the suitability confirmation unit, when it determines, on the basis of predetermined authentication information for authenticating the worker who assembled the device, that a worker is a worker with a pre-registered work permit, determines that the suitability of the device assembly method is approved and that the feasibility of work on the device assembly method is work-approved. [8] Automatic vehicle software adjustment system according to claim 4, wherein the suitability confirmation unit, when it determines, on the basis of predetermined authentication information for authenticating the worker who assembled the device, that a worker is not a worker with a pre-registered work permit, determines that the suitability of the device assembly method is not approved and confirms to the vehicle owner the feasibility of carrying out work on the device assembly method. [9] Automatic vehicle software adjustment system according to claim 6, wherein the suitability confirmation unit determines, in a case where the assembly method of the device is approved by the owner, that the feasibility of work on the assembly method of the device is permitted. [10] Automatic vehicle software adjustment system according to claim 4, wherein the suitability confirmation unit, when it determines on the basis of the device's identification information that the device meets a safety standard, determines that the suitability of the device's identification information is approved and that work on the device's identification information is permitted. [11] Automatic vehicle software adjustment system according to claim 4, wherein the suitability confirmation unit, when it determines on the basis of the device's identification information that the device does not meet a safety standard, determines that the suitability of the device's identification information is not approved and confirms to the vehicle owner the feasibility of work on the device's identification information. [12] Automatic vehicle software adjustment system according to claim 4, wherein the suitability confirmation unit, when it determines on the basis of the device's identification information that the device is a previously authenticated device, determines that the suitability of the device's identification information is approved and the feasibility of work on the device's identification information is permitted. [13] Automatic vehicle software adjustment system according to claim 4, wherein the suitability confirmation unit, when it determines on the basis of the device's identification information that the device is not a previously authenticated device, determines that the suitability of the device's identification information is not permitted and confirms the feasibility of performing work on the device's identification information to a vehicle owner. [14] Automatic vehicle software adjustment system according to claim 11, wherein the suitability confirmation unit determines, in a case where the identification information of the device is permitted by the owner, that the feasibility of work on the identification information of the device is permitted. [15] Automatic vehicle software setting procedure in an automatic vehicle software setting system comprising a vehicle control unit and an administration unit, wherein the procedure includes the vehicle control unit performing the following: one step towards detecting a device mounted on a vehicle, a step towards recognizing the device's identification information, and a step towards using the identification information to assess the suitability and feasibility of working on the device, and that the administrative body performs the following: one step of using the identification information requested by the vehicle control unit to confirm the suitability and feasibility of work on the equipment and to respond to the vehicle control unit, and a step of selecting software that belongs to the device for which it has been confirmed that work is permissible, and distributing the software to the vehicle control unit. [16] Vehicle control device comprising: a unit for detecting changes to assembly information that recognizes a device mounted on a vehicle; a device information recognition unit that recognizes the device's identification information; and a suitability query unit that uses the identification information to query the suitability and feasibility of work on the device.

Images