JP6748376B2 - Management device, management method, and management program - Google Patents

Description

The present invention relates to a management device, a management method, and a management program.

Conventionally, a technique has been developed for automatically updating device firmware in a vehicle from a remote location.

For example, Japanese Patent Laid-Open No. 2007-65856 discloses the following information rewriting device. That is, the information rewriting device receives a correction program for correcting the program from the program providing device outside the vehicle, and rewrites the vehicle control program for controlling the vehicle using the received correction program. The information rewriting device, when a program rewriting request is made from the program providing device, judges whether or not the vehicle control program can be rewritten, based on the operating state of the vehicle; And a notification unit for notifying the communication terminal of the user of the vehicle of information regarding rewriting based on the result of the determination by the determination unit.

JP, 2007-65856, A

The program providing device described in Patent Document 1 holds a correction program for each vehicle type of a vehicle, and has a function of distributing the held correction program to a target vehicle.

Upload of the correction program to the program providing device is performed by, for example, an OEM (Original Equipment Manufacture) that manufactures a vehicle to which the correction program is to be distributed.

Specifically, the user in charge of distributing the correction program performs an operation of inputting information specific to the program providing device to the terminal device using a user interface specific to the program providing device. The terminal device uploads the correction program to the program providing device according to a user operation.

However, when changing the program providing apparatus to another program providing apparatus for some reason, the user uses a user interface unique to the other program providing apparatus to send information specific to the other program providing apparatus to the terminal device. It is required to perform the input operation.

When at least one of the user interface and the information to be input is different before and after the change of the program providing device, the user is unfamiliar with the changed user interface or the information to be input, which increases the burden on the user. ..

The present invention has been made to solve the above-described problems, and an object thereof is to make a user's burden heavy in a configuration for performing a process related to data update of an in-vehicle device using a storage device that stores update data. To provide a management device, a management method, and a management program capable of preventing the above.

(1) In order to solve the above-mentioned problem, a management device according to an aspect of the present invention is provided with a content of a first process and an input of the first process regarding data update of one or a plurality of devices mounted on a vehicle. An acquisition unit for acquiring input information including input source identification information capable of identifying the source, information capable of recognizing the input source, information capable of recognizing the first process, and update data of the device are accumulated. Storage device identification information capable of recognizing the storage device and a storage unit that stores correspondence information indicating a correspondence relationship between the storage device and the information capable of recognizing the content of the second processing with respect to the storage device. The correspondence relationship between a plurality of storage devices that differ in information to be given to execute the same second process or that have different user interfaces for executing the same second process is shown. The information processing apparatus further includes a processing unit that executes the second process corresponding to the first process indicated by the input information to the storage device corresponding to the input source identification information indicated by the input information, based on the information.

(5) In order to solve the above problems, a management method according to an aspect of the present invention is a management method in a management device including a storage unit, which relates to data update of one or a plurality of devices mounted on a vehicle. And a step of acquiring input information including input source identification information capable of identifying the input source of the first process, wherein the storage unit includes information capable of recognizing the input source; Correspondence between information that can recognize the first process, storage device identification information that can recognize the storage device that stores the update data of the device, and information that can recognize the contents of the second process for the storage device. Corresponding information indicating that the information to be given for executing the same second processing is different, or a plurality of the user interfaces for executing the same second processing are different. The correspondence relationship of the storage devices is indicated, and further, based on the correspondence information, the storage device corresponding to the input source identification information indicated by the input information corresponds to the first process indicated by the input information. The method includes the step of performing the second process.

(6) In order to solve the above problems, a management program according to an aspect of the present invention is a management program used in a management device including a storage unit, and a computer is used as one or a plurality of devices mounted in a vehicle. Is a program for functioning as an acquisition unit that acquires the input information including the content of the first process related to the data update of the first process and the input source identification information that can identify the input source of the first process, and the storage unit. Is information for recognizing the input source, information for recognizing the first process, storage device identification information for recognizing a storage device that stores update data of the device, and second information for the storage device. The correspondence information indicating the correspondence relationship with the information capable of recognizing the contents of the processing is stored, and the correspondence information is different from or the same as the second information to be given to execute the same second processing. The storage device corresponding to the input source identification information indicated by the input information is displayed on the computer based on the correspondence information, the correspondence relationship between the storage devices having different user interfaces for executing processing. Is a program for functioning as a processing unit that executes the second process corresponding to the first process indicated by the input information.

The present invention can be realized not only as a management apparatus including such a characteristic processing unit but also as a management system including such a characteristic processing unit. Further, the present invention can be realized as a semiconductor integrated circuit that realizes part or all of the management device.

According to the present invention, it is possible to prevent the burden on the user from becoming heavy in the configuration for performing the process related to the data update of the vehicle-mounted device using the storage device that stores the update data.

FIG. 1 is a diagram showing the configuration of a comparative example of the management system according to the first embodiment of the present invention. FIG. 2 is a diagram showing an example of second processing for the vendor server in the management system according to the first embodiment of the present invention. FIG. 3 is a diagram showing an example of a second process for the vendor server in the management system according to the first embodiment of the present invention. FIG. 4 is a diagram showing an example of a second process for the vendor server in the management system according to the first embodiment of the present invention. FIG. 5 is a diagram showing the configuration of the management system according to the first embodiment of the present invention. FIG. 6 is a diagram showing the configuration of the management device in the management system according to the first embodiment of the present invention. FIG. 7 is a diagram showing an example of a template table registered in the storage unit in the management device according to the first embodiment of the present invention. FIG. 8 is a diagram showing an example of a routing table held by the storage unit in the management device according to the first embodiment of the present invention. FIG. 9 is a diagram showing an example of a sequence when the terminal device registers the ECU in the vendor server in the management system according to the first embodiment of the present invention. FIG. 10 is a diagram showing an example of a sequence when the management apparatus logs in to the vendor server in the management system according to the first exemplary embodiment of the present invention. FIG. 11 is a diagram showing an example of a sequence when the management device uploads the firmware to the vendor server in the management system according to the first embodiment of the present invention. FIG. 12 is a diagram for explaining the effect of the management system according to the first embodiment of the present invention. FIG. 13 is a diagram showing an example of a routing table held by the storage unit in the management device according to the first embodiment of the present invention. FIG. 14 is a diagram showing the configuration of the management system according to the second embodiment of the present invention. FIG. 15 is a diagram showing an example of a routing table held by the storage unit in the management device according to the second embodiment of the present invention.

First, the contents of the embodiments of the present invention will be listed and described.

(1) The management device according to the embodiment of the present invention is an input source capable of identifying the content of the first process relating to the data update of one or a plurality of devices mounted on the vehicle and the input source of the first process. An acquisition unit that acquires input information including identification information, information that can recognize the input source, information that can recognize the first process, and a storage device that stores update data of the device can be recognized. The storage device is provided with a storage unit that stores correspondence information indicating a correspondence relationship between the storage device identification information and information capable of recognizing the content of the second process for the storage device, and the correspondence information includes the same second process. The correspondence relation of the plurality of storage devices, which have different information to be given for execution or different user interfaces for performing the same second processing, is shown, and further, the input is performed based on the correspondence information. The information processing apparatus further includes a processing unit that executes the second processing corresponding to the first processing indicated by the input information to the storage device corresponding to the input source identification information indicated by the information.

When the user causes the storage device to execute the second process relating to the data update of the in-vehicle device without using the management device, the operation content required by the user differs depending on, for example, the storage device. On the other hand, when the user causes the storage device to execute the second process by using the management device, no matter which storage device the second process is executed by, the first operation is performed based on the correspondence information. Since the second process corresponding to the process is executed, the input operation for the content of the first process required by the user can be made common. Specifically, for example, when changing the storage device used for updating the data of the in-vehicle device, the input operation required by the user can be maintained before and after the change of the storage device. Therefore, it is possible to prevent the burden on the user from becoming heavy in the configuration for performing the process related to the data update of the vehicle-mounted device by using the storage device that stores the update data.

(2) Preferably, the storage device identification information is an address of the storage device.

As described above, by the configuration in which the above-mentioned address that is unique to the storage device and that can be used as the destination of the contents of the second process is used as the storage device identification information, the second process can be reliably and easily performed in the storage device. Can be run.

(3) Preferably, the input source identification information is an address of the input source device.

In this way, the storage device can be reliably and easily specified by the configuration in which the above-mentioned address that is unique to the input source device and can be used as a standard for transmitting input information is used as the input source identification information. You can

(4) Preferably, the acquisition unit is capable of acquiring the input information from a plurality of the input sources, and the storage unit stores the correspondence information about the plurality of the input sources.

With such a configuration, one management device can handle a plurality of users.

(5) The management method according to the embodiment of the present invention is a management method in a management device including a storage unit, and includes the contents of the first process regarding data update of one or a plurality of devices mounted on a vehicle and A step of acquiring input information including input source identification information capable of identifying an input source of the first process, wherein the storage unit is capable of recognizing the input source and the first process; Information, the storage device identification information capable of recognizing the storage device that stores the update data of the device, and the correspondence information indicating the correspondence relationship between the information capable of recognizing the content of the second process for the storage device are stored. , The correspondence information is different in information to be given in order to execute the same second process, or the correspondence relationship between a plurality of storage devices having different user interfaces for executing the same second process. Furthermore, based on the correspondence information, the second processing corresponding to the first processing indicated by the input information is executed for the storage device corresponding to the input source identification information indicated by the input information. Including the step of performing.

When the user causes the storage device to execute the second process relating to the data update of the in-vehicle device without using the management device, the operation content required by the user differs depending on, for example, the storage device. On the other hand, when the user causes the storage device to execute the second process by using the management device, no matter which storage device the second process is executed by, the first operation is performed based on the correspondence information. Since the second process corresponding to the process is executed, the input operation for the content of the first process required by the user can be made common. Specifically, for example, when changing the storage device used for updating the data of the in-vehicle device, the input operation required by the user can be maintained before and after the change of the storage device. Therefore, it is possible to prevent the burden on the user from becoming heavy in the configuration for performing the process related to the data update of the vehicle-mounted device by using the storage device that stores the update data.

(6) A management program according to an embodiment of the present invention is a management program used in a management device including a storage unit, and is a first program related to data update of one or a plurality of devices mounted on a vehicle. The storage unit recognizes the input source, which is a program for operating as an acquisition unit that acquires input information including the content of the process and the input source identification information that can identify the input source of the first process. Possible information, information capable of recognizing the first process, storage device identification information capable of recognizing a storage device that stores update data of the device, and content of the second process for the storage device Corresponding information indicating a correspondence relationship with other information, the correspondence information is different in information to be given to execute the same second processing, or the same user for executing the same second processing. The correspondence relationship between a plurality of storage devices having different interfaces is shown, and further, a computer is configured to, based on the correspondence information, input the input information to the storage device corresponding to the input source identification information indicated by the input information. It is a program for functioning as a processing unit that executes the second process corresponding to the first process shown.

When the user causes the storage device to execute the second process relating to the data update of the in-vehicle device without using the management device, the operation content required by the user differs depending on, for example, the storage device. On the other hand, when the user causes the storage device to execute the second process by using the management device, no matter which storage device the second process is executed by, the first operation is performed based on the correspondence information. Since the second process corresponding to the process is executed, the input operation for the content of the first process required by the user can be made common. Specifically, for example, when changing the storage device used for updating the data of the in-vehicle device, the input operation required by the user can be maintained before and after the change of the storage device. Therefore, it is possible to prevent the burden on the user from becoming heavy in the configuration for performing the process related to the data update of the vehicle-mounted device by using the storage device that stores the update data.

Embodiments of the present invention will be described below with reference to the drawings. It should be noted that the same or corresponding parts in the drawings are designated by the same reference numerals and description thereof will not be repeated. Further, at least a part of the embodiments described below may be arbitrarily combined.

<First Embodiment>
[Configuration and basic operation]
FIG. 1 is a diagram showing the configuration of a comparative example of the management system according to the first embodiment of the present invention.

Referring to FIG. 1, a management system 300 as a comparative example includes a terminal device 151 and vendor servers (storage devices) 181A, 181B, 181C. Hereinafter, each of the vendor servers 181A, 181B, 181C is also referred to as a vendor server 181.

The target vehicle 1 is equipped with one or a plurality of devices whose data can be updated externally. Specifically, the target vehicle 1 is equipped with, for example, an ECU (Electronic Control Unit) that operates according to firmware that can be updated from the outside.

The vendor server 181 is, for example, a server operated by an OTA (On-The-Air) vendor that provides a mechanism for distributing firmware, and is provided outside the target vehicle 1.

In this example, the vendor servers 181A, 181B, 181C are operated by OTA vendor A, OTA vendor B, and OTA vendor C, respectively.

Further, the vendor server 181 has an IP address, which is an example of storage device recognition information that can identify itself.

In this example, the IP addresses of the vendor servers 181A, 181B, and 181C are "192.168.11.2", "192.168.22.3", and "192.168.33.4", respectively.

The vendor server 181 stores the update data of the target device. Specifically, the vendor server 181 stores, for example, the firmware used for the ECU mounted on the target vehicle 1.

The vendor server 181 can perform wireless communication with the target vehicle 1, and updates the firmware by causing the ECU mounted on the target vehicle 1 to download the firmware for update. The vendor server 181 may update the firmware of the ECU by performing wired communication with the target vehicle 1.

The terminal device 151 is, for example, a personal computer including a screen. In this example, the IP address of the terminal device 151 is “10.1.1.x”.

The terminal device 151 is managed by, for example, an OEM (Original Equipment Manufacture) that manufactured the target vehicle 1.

A person in charge of the OEM (hereinafter, also referred to as a user) manages the firmware update of the ECU mounted on the target vehicle 1 manufactured by the own OEM. The user uploads the firmware for update to the vendor server 181 by operating the terminal device 151, for example.

2 to 4 are diagrams showing an example of the second process for the vendor server in the management system according to the first embodiment of the present invention.

With reference to FIGS. 2 to 4, the plurality of vendor servers 181 have different information to be given in order to execute the same second process, or different user interfaces for executing the same second process.

Here, the second process is, for example, a login process, an upload process, an update schedule registration process, an ECU registration process, or the like.

The login process is, for example, a process for receiving authentication from the vendor server 181. The upload process is, for example, a process for uploading firmware to the vendor server 181. The update schedule registration process is, for example, a process for the vendor server 181 to register a schedule for downloading firmware to the target vehicle 1. The ECU registration process is, for example, a process for registering the name of the ECU whose firmware is to be updated in the vendor server 181.

For example, the information to be given to the vendor servers 181A to 181C in order to execute the login process is different from each other.

Specifically, the vendor servers 181A to 181C implement different Web APIs (Web Application Programming Interfaces).

More specifically, the vendor server 181 prepares a URL (Uniform Resource Locator) for each second process, and accepts commands such as requests, responses, and posts according to, for example, the HTTP (Hypertext Transfer Protocol) protocol at the URL. ..

When the vendor server 181 receives the command, the vendor server 181 executes the second process corresponding to the URL that received the command, based on the received command.

Specifically, as shown in FIG. 2, the vendor server 181A can accept an http post COMa including an http method METa and an http body BODYa according to the http protocol in the login process URLa for the login process. It is possible.

As shown in FIG. 3, the vendor server 181B can accept the http post COMb including the http method METb and the http body BODYb according to the http protocol in the login process URLb for the login process.

As shown in FIG. 4, for the login process, the vendor server 181C can accept an http post COMc including an http method METc and an http body BODYc according to the http protocol at the login process URLc.

Further, the information to be given to the vendor servers 181A to 181C in order to execute the upload process, the update schedule registration process, and the ECU registration process is also different from each other.

The vendor server 181 can provide a GUI according to the content of the second processing. Here, the GUI is a user interface for drawing a field for parameter input, an explanatory text for explaining the field, buttons, and the like on a Web browser.

GUIs (Graphical User Interface) for login processing provided by the vendor servers 181A to 181C are different from each other.

More specifically, in the GUI for login processing provided by the vendor server 181A, a column for inputting ""name"", ""password"", and ""domain"", and a description corresponding to the column It includes a sentence, a send button, and the like.

Further, in the GUI for login processing provided by the vendor server 181B, a column for inputting each of ""id"", ""passwd"", and ""location"", a description corresponding to the column, and A send button and the like are included.

In addition, in the GUI for login processing provided by the vendor server 181C, a column for inputting ""username"", ""password"", ""timezone"", and ""domain"", respectively. Corresponding descriptive text, a send button, etc. are included.

In the GUI for login processing provided by each of the vendor servers 181A to 181C, the column and the description are different from each other.

The GUIs for upload processing provided by the vendor servers 181A to 181C are also different from each other. Further, the GUIs for the update schedule registration processing provided by the vendor servers 181A to 181C are also different from each other. The GUIs for ECU registration processing provided by the vendor servers 181A to 181C are also different from each other.

The vendor servers 181A to 181C may provide a CUI (character user interface) instead of the GUI.

With reference to FIG. 1 again, for example, operations of the terminal device 151 and the vendor server 181A when the user logs in the terminal device 151 to the vendor server 181A will be described. The operations of the vendor servers 181B and 181C are the same as those of the vendor server 181A, except for the contents of parameters.

A web browser is displayed on the screen of the terminal device 151. The user performs, on the Web browser, an operation of transmitting an http request indicating a GUI request for login processing to the URL for login processing in the vendor server 181A.

The terminal device 151 transmits the http request to the URL for login processing in the vendor server 181A according to the operation of the user.

When the vendor server 181A receives the http request from the terminal device 151, the vendor server 181A creates an http response indicating a GUI for login processing based on the URL that received the http request and the received http request, and sends the http response to the terminal device 151. ..

Upon receiving the http response from the vendor server 181A, the terminal device 151 draws a GUI for login processing on the Web browser based on the received http response.

The user enters ""OEM1"", ""aaaaaaaaa"" and ""OEM1-DOMAIN"" in the fields for entering ""name"", ""password"" and ""domain"", respectively. The input operation is performed on the Web browser. Then, the user performs an operation of selecting the send button on the Web browser.

The terminal device 151 transmits the http post COMa shown in FIG. 2 to the URLa in the vendor server 181A according to the operation of the user.

The vendor server 181A receives the http post COMa from the terminal device 151 at the URLa, and executes the login process based on the received http post COMa.

In the vendor servers 181A to 181C, the information to be given in order to execute the same second process is different, and the user interfaces for executing the same second process are different. It is not limited to this.

Any one of the information to be given for executing the same second process and the user interface for executing the same second process may have a different configuration between any two vendor servers 181. ..

[Task]
For example, when the user has a contract with the OTA vendor A, the user manages the firmware update of the ECU in the target vehicle 1 by using the vendor server 181A as shown in FIG.

In this case, the user causes the vendor server 181A to execute the second process using the GUI provided by the vendor server 181A. This GUI is, for example, a GUI for transmitting the http post COMa shown in FIG. 2 to the vendor server 181A.

For example, when the user changes the contract party from the OTA vendor A to the OTA vendor B, the user is required to manage the firmware update using the vendor server 181B.

However, since the http post COMa shown in FIG. 2 and the http post COMb shown in FIG. 3 are different, the GUI provided by the vendor server 181A and the GUI provided by the vendor server 181B are different from each other and provided by the vendor server 181B. The burden on the user to master the GUI is heavy.

Similarly, when the user changes the contracting party from the OTA vendor A to the OTA vendor C, the http post COMa shown in FIG. 2 is different from the http post COMc shown in FIG. The GUI provided by the vendor server 181C and the GUI provided by the vendor server 181C are different from each other, and the user has to become proficient with the GUI provided by the vendor server 181C.

That is, the burden on the user when changing the vendor server 181 used for updating the firmware of the ECU in the target vehicle 1 becomes heavy.

Therefore, the management system according to the embodiment of the present invention solves such a problem by the following configurations and operations.

FIG. 5 is a diagram showing the configuration of the management system according to the first embodiment of the present invention.

Referring to FIG. 5, management system 301 includes terminal device 151, management device 101, and vendor servers 181A, 181B, 181C.

The operations of the terminal device 151 and the vendor server 181 in the management system 301 are the same as those of the terminal device 151 and the vendor server 181 in the management system 300 shown in FIG. 1, respectively.

The management system 301 is not limited to the configuration including the three vendor servers 181, and may have the configuration including two vendor servers 181 or four or more vendor servers 181.

The management device 101 provides the terminal device 151 with a first processing GUI relating to the data update of the ECU mounted on the target vehicle 1. The management apparatus 101 may provide the terminal device 151 with the CUI for the first processing.

Here, the first process is a process corresponding to the second process, and is specifically a login process, an upload process, an update schedule registration process, an ECU registration process, or the like.

To enter the name of the ECU to be registered, the model of the target vehicle 1 in which the ECU is installed, and the name of the OTA vendor with which the contract is registered, in the GUI for ECU registration processing provided by the management device 101. Column, a description corresponding to the column, a send button, and the like are included.

FIG. 6 is a diagram showing the configuration of the management device in the management system according to the first embodiment of the present invention.

With reference to FIG. 6, the management device 101 includes a communication unit 21, a processing unit 22, and a storage unit 23.

The communication unit 21 in the management apparatus 101 performs wired communication with the terminal device 151 and the vendor server 181. The communication unit 21 may be configured to perform wireless communication with at least one of the terminal device 151 and the vendor server 181.

The storage unit 23 recognizes the input source of the first process (hereinafter, also referred to as input source recognition information), the information that can recognize the first process, the storage device identification information, and the vendor server 181. The correspondence information indicating the correspondence relationship with the information (hereinafter, also referred to as template information) capable of recognizing the content of the second processing for is stored. Here, the correspondence information indicates the correspondence relationship between the plurality of vendor servers 181.

Specifically, the storage unit 23, as an example of the correspondence information, a template table showing a correspondence relationship between the information capable of recognizing the first process, the storage device identification information, and the template information, and the input source recognition information and the storage device. It holds a routing table showing the correspondence with the identification information. Details of these tables will be described later.

The contents of the template table are registered in the storage unit 23 by the administrator of the management apparatus 101, for example. The contents of the routing table are registered by the management device 101, for example.

FIG. 7 is a diagram showing an example of a template table registered in the storage unit in the management device according to the first embodiment of the present invention.

With reference to FIG. 7, the storage unit 23 is a vendor server that is an example of the first process, the name of the vendor that operates the vendor server 181 that can be managed by its own management apparatus 101, and storage device identification information. A template table TT1 showing the correspondence relationship between the IP address of 181 or the destination IP address and the template for the second processing corresponding to the first processing is held.

The template for the second processing is a command template corresponding to the second processing.

Specifically, the second processing template in the case where the first processing and the destination IP address are “login processing” and “192.168.11.2”, respectively, is the http post-COMa http shown in FIG. In the body BODYa, this is a template TLa in which the areas ““OEM1””, ““aaaaaaaaa””, and ““OEM1-DOMAIN”” are blank.

The other second processing templates in the template table TT1 are the same as the template TLa.

The information that can recognize the first process is not limited to the name of the process such as the login process, but may be the URL or the like corresponding to the process.

FIG. 8 is a diagram showing an example of a routing table held by the storage unit in the management device according to the first embodiment of the present invention.

Referring to FIG. 8, storage unit 23 shows the correspondence relationship between the sender IP address that is the IP address of terminal device 151, the determination identifier that indicates the vehicle type and ECU name, the destination IP address, and the name of the vendor. It holds the routing table RT1a. The sender IP address is an example of input source recognition information.

[Operation flow]
Each device in the management system 301 includes a computer, and an arithmetic processing unit such as a CPU in the computer reads out a program including some or all of the steps of the following sequence diagram or flowchart from a memory (not shown) and executes the program. .. The programs of these plural devices can be installed from the outside. The programs of these plural devices are distributed in the state of being stored in the recording medium.

[ECU registration processing]
FIG. 9 is a diagram showing an example of a sequence when the terminal device registers the ECU in the vendor server in the management system according to the first embodiment of the present invention.

Referring to FIGS. 6 and 9, first, on the screen of terminal device 151, the user performs an operation of transmitting an http request indicating a GUI request for ECU registration processing to the URL for ECU registration processing in management device 101. This is performed for the displayed Web browser (step S102).

Next, the terminal device 151 creates the http request addressed to the URL for the ECU registration process according to the user's operation, and transmits the created http request to the management device 101 (step S104).

More specifically, the terminal device 151 creates an IP packet including the http request, and transmits the created IP packet to the management device 101.

The IP packet includes the IP address of the terminal device 151 and the IP address of the management device 101 as the source IP address and the destination IP address, respectively.

Next, when the management device 101 receives the http request from the terminal device 151, the management device 101 creates an http response indicating a GUI for ECU registration processing according to the received http request, and transmits the created http response to the terminal device 151 ( Step S106).

More specifically, when receiving the IP packet from the terminal device 151, the communication unit 21 extracts the http request from the received IP packet and outputs the extracted http request to the processing unit 22.

When the processing unit 22 receives the http request from the communication unit 21, the processing unit 22 recognizes the ECU registration process based on the destination URL of the received http request, and creates an http response including the contents of the GUI for the ECU registration process in the http body. .. The processing unit 22 transmits the created http response to the terminal device 151 via the communication unit 21.

Next, when the terminal device 151 receives the http response from the management device 101, the terminal device 151 draws a GUI for ECU registration processing on the Web browser based on the received http response (step S108).

Next, the user, for example, names the ECU to be registered, the model of the target vehicle 1 equipped with the ECU, the name of the contracted OTA vendor, and the IP of the vendor server 181 operated by the OTA vendor. The operation of inputting "ECU1", "vehicle type α", "OTA vendor A", and "192.168.11.2" as addresses is performed on the Web browser. Then, the user performs an operation of selecting the send button on the Web browser (step S110).

Next, the terminal device 151 creates an http post addressed to the URL for ECU registration processing in the management device 101 according to the user's operation, and transmits the created http post to the management device 101 (step S112).

More specifically, the terminal device 151 has the ECU name “ECU1”, vehicle type information indicating “vehicle type α”, the OTA vendor name “OTA vendor A” of the registration destination, and the IP address of the vendor server 181A. Create an http post that includes "192.168.11.2" in the http body.

The terminal device 151 creates an IP packet including the http post, and transmits the created IP packet to the management device 101.

Next, when the management device 101 receives the http post from the terminal device 151, the management device 101 registers the route from the terminal device 151 to the vendor server 181A in the routing table RT1a (see FIG. 8) based on the received http post (step 8). S114).

More specifically, the communication unit 21 in the management apparatus 101 acquires the input information including the content of the first process and the input source identification information that can identify the input source of the first process.

Specifically, the communication unit 21 receives an IP packet including an http post as input information. Here, the URL for ECU registration processing, the name of the ECU, and the vehicle type information included in the http post are examples of the content of the first processing. The IP address of the terminal device 151 included in the IP packet is an example of the input source identification information.

The communication unit 21 acquires the http post and the sender IP address from the received IP packet, and outputs the acquired http post and the sender IP address to the processing unit 22.

When the processing unit 22 receives the http post and the sender IP address from the communication unit 21, the processing unit 22 acquires the name of the ECU, the vehicle type information, the name of the OTA vendor of the registration destination, and the IP address of the vendor server 181A from the received http post. The acquired information and the sender IP address are registered in the routing table RT1a.

Next, the management apparatus 101 converts the http post from the terminal device 151 into a command suitable for the vendor server 181A (step S116).

More specifically, the processing unit 22 executes the second process corresponding to the first process indicated by the input information to the vendor server 181 corresponding to the input source identification information indicated by the input information, based on the correspondence information. To do.

Specifically, the processing unit 22 recognizes that the first process is the “ECU registration process” based on the destination URL of the http post.

The processing unit 22 refers to the template table TT1 (see FIG. 7) and acquires the template TRa corresponding to “ECU registration processing” and “192.168.11.2” from the template table TT1.

The processing unit 22 writes an ECU name, vehicle type information, and other necessary information in the acquired template TRa to create an http post (hereinafter, also referred to as a post-adaptation http post) compatible with the vendor server 181A. To do.

The processing unit 22 refers to the routing table RT1a, designates the destination as “192.168.11.2” corresponding to the sender IP address, and outputs the created post-adaptive http post to the communication unit 21.

Next, the management apparatus 101 transmits the post-matching http post to the vendor server 181A (step S118).

More specifically, when the communication unit 21 in the management apparatus 101 receives the post-match HTTP post from the processing unit 22, the communication unit 21 includes the received post-match HTTP post and the destination IP address is “192.168.11.2”. It creates a certain IP packet and sends the created IP packet to the vendor server 181A.

Next, when the vendor server 181A receives the post-adaptation http post from the management device 101, the vendor server 181A registers the name of the ECU and vehicle type information based on the received post-adaptation http post (step S120).

Next, the vendor server 181A transmits, for example, response information indicating that registration is successful to the management apparatus 101 (step S122).

Next, when the management apparatus 101 receives the response information from the vendor server 181A, the management apparatus 101 recognizes the content of the received response information and transmits the response information to the terminal device 151 (step S124).

The content of the routing table RT1a is not limited to the configuration registered in the above sequence, and may be manually registered by the administrator of the management apparatus 101.

Further, when the login processing to the vendor server 181A is not performed, the management apparatus 101 indicates that the authentication processing is not completed between the steps S114 and S116 or between the steps S116 and S118. After the response information is transmitted to the terminal device 151 to cause the user to perform the login processing described below, the post-matching http post is transmitted to the vendor server 181A (step S118).

[Login process]
FIG. 10 is a diagram showing an example of a sequence when the management apparatus logs in to the vendor server in the management system according to the first exemplary embodiment of the present invention.

With reference to FIG. 10, first, the user performs an operation of transmitting an http request indicating a GUI request for login processing to the URL for login processing in the management apparatus 101, the Web browser displayed on the screen of the terminal device 151. (Step S202).

Next, the terminal device 151 creates the http request addressed to the URL for login processing according to the user's operation, and transmits the created http request to the management device 101 (step S204).

Next, when the management device 101 receives the http request from the terminal device 151, the management device 101 creates an http response indicating a GUI for login processing according to the received http request, and transmits the created http response to the terminal device 151 (step S206).

The GUI for login processing is, for example, a user interface for inputting the parameter set Set1 shown in FIG. The GUI includes columns for inputting “user”, “password”, “domain”, and “location”, descriptive text corresponding to the columns, a send button, and the like.

Next, when the terminal device 151 receives the http response from the management device 101, the terminal device 151 draws a GUI for login processing on the Web browser based on the received http response (step S208).

Next, the user enters “OEM1”, “aaaaaaaaa”, “OEM1-DOMAIN” and “Asia/Tokyo” in the fields for inputting “user”, “password”, “domain” and “location”, respectively. Each input operation is performed on the Web browser. Then, the user performs an operation of selecting the send button on the Web browser (step S210).

Next, the terminal device 151 creates an http post addressed to the URL for login processing in the management device 101 according to the user's operation, and transmits the created http post to the management device 101 (step S212).

More specifically, the terminal device 151 uses “OEM1”, “aaaaaaaaa”, “OEM1-DOMAIN”, and “Asia/Tokyo” as the http body as the user name, password, domain name, and location of the base of use, respectively. Create the containing http post.

The terminal device 151 creates an IP packet including the http post, and transmits the created IP packet to the management device 101.

Next, when the management device 101 receives the IP packet from the terminal device 151, the management device 101 acquires the IP address of the vendor server 181 corresponding to the sender IP address included in the received IP packet (step S214).

More specifically, the communication unit 21 in the management apparatus 101 acquires the http post and the sender IP address from the IP packet received from the terminal device 151, and outputs the acquired http post and the sender IP address to the processing unit 22. ..

The processing unit 22 receives the sender IP address from the communication unit 21, refers to the routing table RT1a (see FIG. 8), and refers to the sender IP address as the IP address of the vendor server 181 "192.168.11. 2” is acquired.

Next, the management apparatus 101 creates a command suitable for the vendor server 181A based on the http post from the terminal device 151 (step S216).

More specifically, the processing unit 22 recognizes that the first process is the “login process” based on the destination URL of the http post.

The processing unit 22 refers to the template table TT1 (see FIG. 7) and acquires the template TLa corresponding to “login process” and “192.168.11.2” from the template table TT1.

The processing unit 22 writes a user name, a password, and a domain name in the acquired template TLa to create a post-adaptation http post that conforms to the vendor server 181A, that is, an http post COMa (see FIG. 2).

The processing unit 22 designates the destination as “192.168.11.2” and outputs the created post-adaptive http post to the communication unit 21.

Next, the management apparatus 101 transmits the post-matching http post to the vendor server 181A (step S218).

More specifically, when the communication unit 21 in the management apparatus 101 receives the post-match HTTP post from the processing unit 22, the communication unit 21 includes the received post-match HTTP post and the destination IP address is “192.168.11.2”. It creates a certain IP packet and sends the created IP packet to the vendor server 181A.

Next, when the vendor server 181A receives the post-matching http post from the management apparatus 101, the vendor server 181A authenticates the management apparatus 101 based on the received post-matching http post (step S220).

Next, the vendor server 181A transmits, for example, response information indicating that the authentication has succeeded to the management apparatus 101 (step S222).

Next, when the management apparatus 101 receives the response information from the vendor server 181A, the management apparatus 101 recognizes the content of the received response information and transmits the response information to the terminal device 151 (step S224).

[Upload process]
FIG. 11 is a diagram showing an example of a sequence when the management device uploads firmware to the vendor server in the management system according to the first embodiment of the present invention.

Referring to FIG. 11, first, the user performs an operation of transmitting an http request indicating a request for a GUI for upload processing to the URL for upload processing in the management apparatus 101, the Web browser displayed on the screen of the terminal device 151. (Step S302).

Next, the terminal device 151 creates an http request addressed to the URL for upload processing according to the user's operation, and transmits the created http request to the management device 101 (step S304).

Next, when the management device 101 receives the http request from the terminal device 151, the management device 101 creates an http response indicating a GUI for upload processing according to the received http request, and sends the created http response to the terminal device 151 (step S306).

In the GUI for upload processing, for example, the name of the ECU to be registered, the vehicle type of the target vehicle 1 in which the ECU is mounted, and the field for inputting the file path of the firmware, the description corresponding to the field, A send button and the like are included.

Next, when the terminal device 151 receives the http response from the management device 101, the terminal device 151 draws a GUI for upload processing on the Web browser based on the received http response (step S308).

Next, the user enters “ECU1”, “vehicle type α” and “c:\firmware\firmware-oem1.exe” in the fields for inputting the name of the ECU, the vehicle type of the target vehicle 1 and the file path of the firmware, respectively. Is input to the Web browser. Then, the user performs an operation of selecting the send button on the Web browser (step S310).

Next, the terminal device 151 creates an http post addressed to the URL for upload processing in the management device 101 according to the operation of the user, and transmits the created http post to the management device 101 (step S312).

More specifically, the terminal device 151 includes an http post including “ECU1”, “vehicle type α”, and “firmwere-oem1.exe” in the http body as the name of the ECU, the vehicle type of the target vehicle 1, and the firmware file, respectively. create.

The terminal device 151 creates an IP packet including the http post, and transmits the created IP packet to the management device 101.

Next, when the management device 101 receives the IP packet from the terminal device 151, the management device 101 refers to the routing table RT1a (see FIG. 8) and refers to the IP address of the vendor server 181 corresponding to the sender IP address included in the received IP packet. That is, “192.168.11.2” is acquired (step S314).

Next, the management apparatus 101 converts the http post from the terminal device 151 into a command suitable for the vendor server 181A (step S316).

More specifically, when the processing unit 22 in the management apparatus 101 receives the http post included in the IP packet from the communication unit 21 that has received the IP packet, the first process is performed based on the destination URL of the http post. Recognize that it is "upload process".

The processing unit 22 refers to the template table TT1 (see FIG. 7) and acquires the template TUa corresponding to “upload processing” and “192.168.11.2” from the template table TT1.

The processing unit 22 writes necessary information based on the http post in the acquired template TUa to create a post-fit http post that includes the firmware file and is suitable for the vendor server 181A.

The processing unit 22 designates the destination as “192.168.11.2” and outputs the created post-adaptive http post to the communication unit 21.

Next, the management apparatus 101 transmits the post-matching http post to the vendor server 181A (step S318).

Next, when the vendor server 181A receives the post-adaptation http post from the management apparatus 101, the vendor server 181A stores or registers the firmware file, specifically, “firmwere-oem1.exe” based on the received post-adaptation http post. Step S320).

Next, the vendor server 181A transmits, for example, response information indicating that the registration is successful to the management apparatus 101 (step S322).

Next, when receiving the response information from the vendor server 181A, the management apparatus 101 recognizes the content of the received response information and transmits the response information to the terminal device 151 (step S324).

[effect]
FIG. 12 is a diagram for explaining the effect of the management system according to the first embodiment of the present invention.

FIG. 12 shows, for example, the management system 301 after the user changes the contract partner from the OTA vendor A to the OTA vendor B.

FIG. 13 is a diagram showing an example of a routing table held by the storage unit in the management device according to the first embodiment of the present invention.

With reference to FIG. 13, the administrator of the management apparatus 101 rewrites the routing table RT1a (see FIG. 8) held by the management apparatus 101 into the routing table RT1b, for example, when the user changes the contract partner. Assume the situation.

More specifically, in the routing table RT1b, “destination IP address” and “vendor name” are rewritten, as compared with the routing table RT1a.

The http post transmitted from the terminal device 151 to the management apparatus 101 after the routing table is rewritten to RT1b is converted into the adapted post by the management apparatus 101, which is adapted to the vendor server 181B.

On the other hand, since the management device 101 provides the same GUI to the terminal device 151 regardless of the rewriting of the routing table, the user of the terminal device 151 allows the user of the terminal device 151 to rewrite the routing table to RT1b before rewriting the routing table. The same GUI is used to operate the Web browser.

With such a configuration, even if the vendor server 181 used for updating the firmware of the ECU in the target vehicle 1 is changed, the GUI to be operated by the user can be maintained, so that the burden on the user is prevented from becoming heavy. it can.

In the management device according to the first embodiment of the present invention, the storage unit 23 is configured to store the template table TT1 and the routing table RT1a as correspondence information, but the present invention is not limited to this. The storage unit 23 may be configured to store input source recognition information, information capable of recognizing the first process, storage device identification information, and correspondence information indicating a correspondence relationship with template information. Specifically, the storage unit 23 is configured to store the template table TT1 excluding the item "vendor name" and the routing table RT1a excluding the items "determination identifier" and "vendor name". Good.

Further, in the management system according to the first embodiment of the present invention, the storage device identification information is the IP address of the vendor server 181, but the present invention is not limited to this. The storage device identification information may be the name of the OTA vendor. Such a configuration can be applied to, for example, a system capable of transmitting a command using the name of the vendor server 181.

Further, in the management system according to the first embodiment of the present invention, the input source identification information is the IP address of the terminal device 151, but the present invention is not limited to this. The input source identification information may be the determination identifier. In this case, the terminal device 151 transmits an IP packet including the determination identifier to the management device 101.

By the way, the program providing device described in Patent Document 1 holds a correction program for each vehicle type of a vehicle, and has a function of distributing the held correction program to a target vehicle.

Uploading of the modification program to the program providing device is performed by, for example, an OEM that manufactures a vehicle to which the modification program is distributed.

Specifically, the user in charge of distributing the correction program performs an operation of inputting information specific to the program providing device to the terminal device using a user interface specific to the program providing device. The terminal device uploads the correction program to the program providing device according to a user operation.

However, when changing the program providing apparatus to another program providing apparatus for some reason, the user uses a user interface unique to the other program providing apparatus to send information specific to the other program providing apparatus to the terminal device. It is required to perform the input operation.

When at least one of the user interface and the information to be input is different before and after the change of the program providing device, the user is unfamiliar with the changed user interface or the information to be input, which increases the burden on the user. ..

On the other hand, in the management device according to the first embodiment of the present invention, the communication unit 21 includes the contents of the first process regarding the data update of one or a plurality of devices mounted on the target vehicle 1 and the first process. The input information including the input source identification information capable of identifying the input source of the process of (1) is acquired. The storage unit 23 can recognize the input source of the first process, the information that can recognize the first process, and the storage device identification information that can recognize the vendor server 181 that stores the update data of the device. Correspondence information indicating a correspondence relationship with the information that can recognize the contents of the second process with respect to the vendor server 181 is stored. The correspondence information indicates a correspondence relationship between a plurality of vendor servers 181 that have different information to be given to execute the same second process or that have different user interfaces for executing the same second process. Then, the processing unit 22 executes the second process corresponding to the first process indicated by the input information to the vendor server 181 corresponding to the input source identification information indicated by the input information, based on the correspondence information.

When the user causes the vendor server 181 to execute the second process related to the data update of the in-vehicle device without using the management apparatus 101, the operation content required by the user differs depending on the vendor server 181, for example. On the other hand, when the user uses the management apparatus 101 to cause the vendor server 181 to execute the second process, whichever vendor server 181 executes the second process, based on the correspondence information, Since the second process corresponding to the first process is executed, it is possible to make common the input operation for the content of the first process required by the user. Specifically, for example, when changing the vendor server 181 used for updating the data of the in-vehicle device, it is possible to maintain the input operation required by the user before and after the change of the vendor server 181. Therefore, it is possible to prevent the burden on the user from becoming heavy in the configuration for performing the process related to the data update of the vehicle-mounted device by using the storage device that stores the update data.

In the management device according to the first embodiment of the present invention, the storage device identification information is the address of the vendor server 181.

As described above, the configuration unique to the vendor server 181 and capable of being used as the destination of the contents of the second process, for example, is the storage device identification information, so that the vendor server 181 can reliably perform the second process. And it can be executed easily.

In the management device according to the first embodiment of the present invention, the input source identification information is the address of the input source device.

In this way, the vendor server 181 can be reliably secured by the configuration in which the above-mentioned address, which is unique to the input source device of the first processing and can be used as a standard for transmitting the input information, is used as the input source identification information. And it can be easily specified.

Next, another embodiment of the present invention will be described with reference to the drawings. It should be noted that the same or corresponding parts in the drawings are designated by the same reference numerals and description thereof will not be repeated.

<Second Embodiment>
The present embodiment relates to a management system including a plurality of terminal devices as compared with the management system according to the first embodiment. The management system is the same as the management system according to the first embodiment except for the contents described below.

[Configuration and basic operation]
FIG. 14 is a diagram showing the configuration of the management system according to the second embodiment of the present invention.

Referring to FIG. 14, management system 302 includes terminal devices 151A, 151B, 151C that are terminal devices 151, management device 101, and vendor servers 181A, 181B, 181C.

The management system 301 is not limited to the configuration including the three vendor servers 181, and may have the configuration including two vendor servers 181 or four or more vendor servers 181.

The management system 301 is not limited to the configuration including the three terminal devices 151, and may have the configuration including two terminal devices 151 or four or more terminal devices 151.

The operations of the terminal device 151 and the vendor server 181 in the management system 302 are the same as those of the terminal device 151 and the vendor server 181 in the management system 300 shown in FIG.

The vehicle types of the target vehicles 1A, 1B, and 1C that are the target vehicle 1 are, for example, vehicle types α, β, and γ.

The vendor servers 181A to 181C respectively store, for example, the firmware used in the ECUs mounted on the target vehicles 1A to 1C.

The vendor servers 181A to 181C update the firmware by causing the ECUs mounted on the target vehicles 1A to 1C to download the firmware for updating, respectively.

The user A manages the firmware update of the ECU in the target vehicle 1A using the vendor server 181A. Specifically, the user A uploads the firmware for update to the vendor server 181A by operating the terminal device 151A, for example.

Similarly, the user B manages the firmware update of the ECU in the target vehicle 1B using the vendor server 181B. Specifically, the user B uploads the firmware for updating to the vendor server 181B by operating the terminal device 151B, for example.

Similarly, the user C manages the firmware update of the ECU in the target vehicle 1C by using the vendor server 181C. Specifically, the user C uploads the update firmware to the vendor server 181C by operating the terminal device 151C, for example.

In this example, the IP addresses of the terminal devices 151A, 151B, and 151C are "10.1.1.x", "204.41.212.y", and "46.105.97.z", respectively.

Referring again to FIG. 6, the communication unit 21 in the management device 101 can acquire input information from a plurality of input sources, for example.

Specifically, the communication unit 21 receives an IP packet including an http post from the terminal devices 151A to 151C as input information.

FIG. 15 is a diagram showing an example of a routing table held by the storage unit in the management device according to the second embodiment of the present invention.

With reference to FIGS. 6 and 15, storage unit 23 stores, for example, correspondence information about a plurality of input sources. Specifically, the storage unit 23 holds the template table TT1 (see FIG. 7) and the routing table RT2.

The user A registers the route Rta from the terminal device 151A to the vendor server 181A in the routing table RT2 held by the storage unit 23, for example, in a sequence similar to the sequence shown in FIG.

Similarly, the user B registers the route Rtb from the terminal device 151B to the vendor server 181B in the routing table RT2 held by the storage unit 23, for example, by a sequence similar to the sequence shown in FIG.

Similarly, the user C registers the route Rtc from the terminal device 151C to the vendor server 181C in the routing table RT2 held by the storage unit 23, for example, in a sequence similar to the sequence shown in FIG.

Note that a part of the routes Rta to Rtc in the routing table RT2 may be manually registered by the administrator of the management apparatus 101.

With reference to FIGS. 14 and 15, for example, when the management apparatus 101 receives an IP packet Pra including an http post from the terminal device 151A, based on the content of the received IP packet Pra, the template table TT1 and the routing table RT2. , Creates a post-fitting http post that is compatible with the vendor server 181A.

The management apparatus 101 transmits the created IP packet Pta including the post-adaptive http post to the vendor server 181A.

Further, for example, when the management apparatus 101 receives the IP packet Prb including the http post from the terminal apparatus 151B, the management apparatus 101 conforms to the vendor server 181B based on the content of the received IP packet Prb, the template table TT1 and the routing table RT2. Create an http post later.

The management apparatus 101 transmits the created IP packet Ptb including the post-adaptive http post to the vendor server 181B.

Further, for example, when the management apparatus 101 receives the IP packet Prc including the http post from the terminal apparatus 151C, the management apparatus 101 conforms to the vendor server 181C based on the content of the received IP packet Prc, the template table TT1 and the routing table RT2. Create an http post later.

The management apparatus 101 transmits the created IP packet Ptc including the post-adaptive http post to the vendor server 181C.

As described above, in the management device according to the second embodiment of the present invention, the communication unit 21 can acquire input information from a plurality of input sources of the first process. Then, the storage unit 23 stores the correspondence information regarding the plurality of input sources.

With such a configuration, one management apparatus 101 can deal with a plurality of users.

Other configurations and operations are similar to those of the management device according to the first embodiment, and therefore detailed description will not be repeated here.

Note that it is possible to appropriately combine some or all of the constituent elements and operations of the respective devices according to the first and second embodiments of the present invention.

It should be considered that the above-described embodiments are illustrative in all points and not restrictive. The scope of the present invention is shown not by the above description but by the claims, and is intended to include meanings equivalent to the claims and all modifications within the scope.

The above description includes the following additional features.

[Appendix 1]
An acquisition unit for acquiring input information including the content of the first processing relating to the data update of one or a plurality of devices mounted on the vehicle and the input source identification information capable of identifying the input source of the first processing;
Information capable of recognizing the input source, information capable of recognizing the first process, storage device identification information capable of recognizing a storage device that stores update data of the target device, and second information for the storage device. A storage unit that stores correspondence information indicating a correspondence relationship with the information that can recognize the content of the process,
The correspondence information indicates the correspondence relationship among a plurality of the storage devices, which are different in information to be given to execute the same second process or different in user interface for executing the same second process. ,
further,
A processing unit that executes the second process corresponding to the first process indicated by the input information to the storage device corresponding to the input source identification information indicated by the input information, based on the correspondence information. Prepare,
The device is an ECU (Electronic Control Unit),
The second processing is login processing, upload processing, update schedule registration processing or ECU registration processing,
The first process is a process corresponding to the second process,
The input source identification information is a determination identifier indicating the IP address of the input source device, or the vehicle type of the vehicle and the name of the device,
The storage device identification information is an IP address of the storage device or a name of the storage device,
The management device, wherein the user interface is a GUI (Graphical User Interface) or a CUI (character user interface).

1 Target Vehicle 21 Communication Unit 22 Processing Unit 23 Storage Unit 101 Management Device 151 Terminal Device 181 Vendor Server (Storage Device)
300,301,302 management system

Claims (6)

An acquisition unit for acquiring input information including the content of the first processing relating to the data update of one or a plurality of devices mounted on the vehicle and the input source identification information capable of identifying the input source of the first processing;
Information capable of recognizing the input source, information capable of recognizing the first process, storage device identification information capable of recognizing a storage device that stores update data of the device, and second processing for the storage device. A storage unit that stores correspondence information indicating a correspondence relationship with information that can recognize the content of
The correspondence information indicates the correspondence relationship among a plurality of the storage devices, which are different in information to be given to execute the same second process or different in user interface for executing the same second process. ,
further,
A processing unit that executes the second process corresponding to the first process indicated by the input information to the storage device corresponding to the input source identification information indicated by the input information, based on the correspondence information. A management device equipped. The management device according to claim 1, wherein the storage device identification information is an address of the storage device. The management device according to claim 1, wherein the input source identification information is an address of the input source device. The acquisition unit is capable of acquiring the input information from a plurality of the input sources,
The management device according to any one of claims 1 to 3, wherein the storage unit stores the correspondence information about a plurality of the input sources. A management method in a management device including a storage unit, comprising:
A step of acquiring input information including contents of a first process relating to data update of one or a plurality of devices mounted on the vehicle and input source identification information capable of identifying an input source of the first process;
The storage unit is capable of recognizing the input source, information capable of recognizing the first process, storage device identification information capable of recognizing a storage device that stores update data of the device, and the storage device. The correspondence information indicating the correspondence relationship with the information capable of recognizing the content of the second processing for
The correspondence information indicates the correspondence relationship among a plurality of the storage devices, which are different in information to be given to execute the same second process or different in user interface for executing the same second process. ,
further,
The step of executing the second process corresponding to the first process indicated by the input information to the storage device corresponding to the input source identification information indicated by the input information, based on the correspondence information. ,Management method. A management program used in a management device having a storage unit,
Computer,
An acquisition unit that acquires input information including the content of the first process relating to the data update of one or more devices mounted on the vehicle and the input source identification information that can identify the input source of the first process.
Is a program to function as
The storage unit is capable of recognizing the input source, information capable of recognizing the first process, storage device identification information capable of recognizing a storage device that stores update data of the device, and the storage device. The correspondence information indicating the correspondence relationship with the information capable of recognizing the content of the second processing for
The correspondence information indicates the correspondence relationship among a plurality of the storage devices, which are different in information to be given to execute the same second process or different in user interface for executing the same second process. ,
In addition, the computer
A processing unit that executes the second processing corresponding to the first processing indicated by the input information to the storage device corresponding to the input source identification information indicated by the input information, based on the correspondence information;
Management program to function as.

Images