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

Abstract

PROBLEM TO BE SOLVED: To prevent the burden of a user from becoming heavy.SOLUTION: A management device of the present invention comprises: an acquisition unit for acquiring input information that includes the content of a first process relating to data updating of one or a plurality of apparatus(es) mounted in a vehicle and input source identification information by which the input source of the first process is identifiable; and a memory unit for storing correspondence information that indicates correspondence between information by which the input source is identifiable, storage device identification information by which a storage device for storing the update data of the first process and the apparatus is identifiable, and information by which the content of a second process for the storage device is identifiable. The correspondence information indicates correspondence between a plurality of the storage devices differing in information to be given in order to execute the second process of the same kind or differing in a user interface for executing the second process of the same kind. The management device further comprises a processing unit for executing, on the basis of the correspondence information, the second process that corresponds to the first process indicated by the input information on the storage device that corresponds to the input source identification information indicated by the input information.SELECTED DRAWING: Figure 6

Description

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

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

  For example, Patent Document 1 (Japanese Unexamined Patent Application Publication 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 there is a program rewriting request from the program providing device, based on the operating state of the vehicle, the determining means for determining whether or not the vehicle control program can be rewritten, Notification means for notifying information relating to rewriting to a communication terminal of a user of the vehicle based on a determination result by the determination means.

JP 2007-65856 A

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

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

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

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

  If at least one of the user interface and the information to be input is different before and after the change of the program providing apparatus, the user is unfamiliar with the user interface after the change or the information to be input, and the burden on the user becomes heavy. .

  The present invention has been made to solve the above-described problems, and its purpose is to increase the burden on the user in a configuration in which processing related to data update of in-vehicle devices is performed using a storage device that stores update data. A management apparatus, a management method, and a management program.

  (1) In order to solve the above-described problem, a management apparatus according to an aspect of the present invention provides the contents of a first process relating to data update of one or a plurality of devices mounted on a vehicle and the input of the first process. An acquisition unit that acquires input information including input source identification information that can identify a source, information that can recognize the input source, information that can recognize the first process, and update data of the device are stored. A storage unit that stores correspondence information indicating a correspondence relationship between storage device identification information capable of recognizing the storage device and information capable of recognizing the content of the second processing for the storage device, and the correspondence information includes: The correspondence between the plurality of storage devices is different in the information to be given to execute the same second process, or the user interface for executing the same second process is different. Affection Based on, it comprises a processing unit for executing the second process 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.

  (5) In order to solve the above-described problem, a management method according to an aspect of the present invention is a management method in a management apparatus including a storage unit, and is a method for updating data of one or more devices mounted on a vehicle. Including the step of obtaining input information including the content of one process and input source identification information capable of identifying the input source of the first process, wherein the storage unit recognizes the input source, Correspondence relationship between information capable of recognizing the first processing, storage device identification information capable of recognizing a storage device that accumulates update data of the device, and information capable of recognizing the content of the second processing for the storage device The correspondence information is different from each other in the information to be given in order to execute the same second process or the user interface for executing the same second process. The correspondence relationship of the storage device 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 processing indicated by the input information. Performing the second process.

  (6) In order to solve the above-described problem, a management program according to an aspect of the present invention is a management program used in a management apparatus including a storage unit, and includes one or more devices mounted on a vehicle. The storage unit is a program for causing the storage unit to function as an acquisition unit that acquires input information including the content of the first process related to data update and input source identification information that can identify the input source of the first process. Includes 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 information for the storage device. Storing correspondence information indicating a correspondence relationship with information capable of recognizing the contents of the processing, and the correspondence information is different in information to be given to execute the same second processing, or The correspondence relationship between the plurality of storage devices having different user interfaces for executing the same second processing is indicated, and the computer is further changed to the input source identification information indicated by the input information based on the correspondence information. This is a program for causing the corresponding storage device to function 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 apparatus.

  ADVANTAGE OF THE INVENTION According to this invention, in the structure which performs the process regarding the data update of vehicle equipment using the storage device which accumulate | stores update data, it can prevent that a user's burden becomes heavy.

FIG. 1 is a diagram showing a configuration of a comparative example of the management system according to the first embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a second process for the vendor server in the management system according to the first embodiment of the present invention. FIG. 3 is a diagram illustrating 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 illustrating 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 a configuration of a management apparatus 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 apparatus 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 apparatus according to the first embodiment of the present invention. FIG. 9 is a diagram showing an example of a sequence when the ECU is registered with the vendor server by the terminal device in the management system according to the first embodiment of the present invention. FIG. 10 is a diagram illustrating an example of a sequence when the management apparatus logs in to the vendor server in the management system according to the first embodiment of the present invention. FIG. 11 is a diagram showing an example of a sequence when the management apparatus uploads 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 illustrating an example of a routing table held by the storage unit in the management apparatus according to the first embodiment of the present invention. FIG. 14 is a diagram showing a configuration of a management system according to the second embodiment of the present invention. FIG. 15 is a diagram illustrating an example of a routing table held by the storage unit in the management apparatus according to the second embodiment of the present invention.

  First, the contents of the embodiment 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 related to data update of one or a plurality of devices mounted on a 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 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 between the plurality of storage devices is different in the information to be given to be executed or the user interface for executing the same second process is different, and further, the input based on the correspondence information Of information Comprising a processing unit for executing the second process to the storage device corresponding to be the input source identification information corresponding to said first processing indicated by the input information.

  When the user causes the storage device to execute the second process related to the data update of the in-vehicle device without using the management device, the operation content required by the user differs depending on the storage device, for example. On the other hand, when the user causes the storage device to execute the second process using the management device, the first process is performed based on the correspondence information in any case where the storage device is to execute the second process. 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 shared. Specifically, for example, when the storage device used for updating the data of the in-vehicle device is changed, the input operation required by the user before and after the change of the storage device can be maintained. Therefore, it is possible to prevent the burden on the user from becoming heavy in a configuration in which processing related to data update of the in-vehicle device is performed using a storage device that stores update data.

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

  As described above, the storage device identification information is used as the storage device identification information, which is unique to the storage device and can be used as the destination of the contents of the second processing, for example. Can be executed.

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

  As described above, the storage device can be specified reliably and easily by using the above-mentioned address that is unique to the input source device and can be used for transmission of input information as standard, for example. Can do.

  (4) Preferably, the acquisition unit can acquire the input information from a plurality of the input sources, and the storage unit stores the correspondence information for the plurality of input sources.

  With such a configuration, it is possible to deal with a plurality of users with one management apparatus.

  (5) A management method according to an embodiment of the present invention is a management method in a management device including a storage unit, and includes the contents of the first processing relating to data update of one or a plurality of devices mounted on a vehicle, and Including 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 can recognize the information capable of recognizing the input source and the first process Storing correspondence information indicating a correspondence relationship between the storage device identification information capable of recognizing the storage device for accumulating the update data of the device, and the information capable of recognizing the content of the second process for the storage device. , The correspondence information indicates the correspondence relationship of a plurality of storage devices with different information to be given to execute the same second process or different user interfaces for executing the same second process. In addition, based on the correspondence information, the second process corresponding to the first process indicated by the input information is executed on the storage device corresponding to the input source identification information indicated by the input information. Including the steps of:

  When the user causes the storage device to execute the second process related to the data update of the in-vehicle device without using the management device, the operation content required by the user differs depending on the storage device, for example. On the other hand, when the user causes the storage device to execute the second process using the management device, the first process is performed based on the correspondence information in any case where the storage device is to execute the second process. 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 shared. Specifically, for example, when the storage device used for updating the data of the in-vehicle device is changed, the input operation required by the user before and after the change of the storage device can be maintained. Therefore, it is possible to prevent the burden on the user from becoming heavy in a configuration in which processing related to data update of the in-vehicle device is performed using a storage device that stores 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 more devices mounted on a vehicle. A program for functioning as an acquisition unit that acquires input information including processing content and input source identification information that can identify an input source of the first process, and the storage unit recognizes the input source Recognizable 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 contents of the second process for the storage device can be recognized Correspondence information indicating a correspondence relationship with the information is stored, and the correspondence information is different in information to be given in order to execute the same second process, or executes the same second process A plurality of storage devices having different user interfaces for indicating the correspondence relationship, and further, on the basis of the correspondence information, a computer is connected 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 indicated by input information.

  When the user causes the storage device to execute the second process related to the data update of the in-vehicle device without using the management device, the operation content required by the user differs depending on the storage device, for example. On the other hand, when the user causes the storage device to execute the second process using the management device, the first process is performed based on the correspondence information in any case where the storage device is to execute the second process. 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 shared. Specifically, for example, when the storage device used for updating the data of the in-vehicle device is changed, the input operation required by the user before and after the change of the storage device can be maintained. Therefore, it is possible to prevent the burden on the user from becoming heavy in a configuration in which processing related to data update of the in-vehicle device is performed using a storage device that stores update data.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals and description thereof will not be repeated. Moreover, you may combine arbitrarily at least one part of embodiment described below.

<First Embodiment>
[Configuration and basic operation]
FIG. 1 is a diagram showing a 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, and 181C. Hereinafter, each of the vendor servers 181A, 181B, and 181C is also referred to as a vendor server 181.

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

  The vendor server 181 is a server operated by, for example, 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, and 181C are operated by an OTA vendor A, an OTA vendor B, and an OTA vendor C, respectively.

  The vendor server 181 has an IP address that is an example of storage device recognition information that can recognize 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 accumulates update data of the target device. Specifically, the vendor server 181 stores firmware used in an ECU mounted on the target vehicle 1, for example.

  The vendor server 181 can wirelessly communicate with the target vehicle 1 and updates the firmware by causing the ECU mounted on the target vehicle 1 to download the update firmware. 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 a personal computer including a screen, for example. 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 belonging to 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 OEM. For example, the user uploads firmware for update to the vendor server 181 by operating the terminal device 151.

  2-4 is a figure which shows an example of the 2nd process with respect to a vendor server in the management system which concerns on the 1st Embodiment of this invention.

  2 to 4, the plurality of vendor servers 181 have different information to be given 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, and the like.

  The login process is a process for receiving authentication of the vendor server 181, for example. The upload process is a process for uploading firmware to the vendor server 181, for example. The update schedule registration process is a process for registering, for example, a schedule for the vendor server 181 to download firmware to the target vehicle 1. The ECU registration process is, for example, a process for registering the name of the ECU for firmware update 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 are mounted with different Web API (Web Application Programming Interface).

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

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

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

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

  As shown in FIG. 4, 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 in the URLc for the login process for the login process.

  Also, 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 are different from each other.

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

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

  More specifically, in the login processing GUI provided by the vendor server 181A, a column for inputting "" name "", "" password "", and "" domain "", respectively, and an explanation corresponding to the column Sentence, send button, etc. are included.

  In addition, in the login processing GUI provided by the vendor server 181B, a column for inputting "" id "", "" passwd "", and "" location "", an explanatory text corresponding to the field, and Includes a send button.

  The login server GUI provided by the vendor server 181C includes a column for inputting “username”, “password”, “timezone”, and “domain”, respectively. Corresponding explanatory text, a send button, and the like are included.

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

  Also, the upload processing GUIs provided by the vendor servers 181A to 181C are different from each other. Also, the GUIs for update schedule registration processing provided by the vendor servers 181A to 181C are different from each other. Further, the GUIs for ECU registration processing provided by the vendor servers 181A to 181C are 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 the terminal device 151 into 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 parameter contents and the like.

  A web browser is displayed on the screen of the terminal device 151. The user performs an operation on the Web browser to transmit 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 an http request to the URL for login processing in the vendor server 181A in accordance with a user operation.

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

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

  The user enters "" OEM1 "", "" aaaaaa "" and "" OEM1-DOMAIN "in the fields for entering" "name" "," "password" "and" "domain" "respectively. An input operation is performed on the Web browser. Then, the user performs an operation for selecting a transmission 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 in accordance with a user operation.

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

  In the vendor servers 181A to 181C, the information to be given to execute the same second process is different, and the user interfaces for executing the same second process are different from each other. However, the present invention is not limited to this.

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

[Task]
For example, when the user contracts with the OTA vendor A, the user manages the ECU firmware update in the target vehicle 1 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 from 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 destination from OTA vendor A to OTA vendor B, the user is required to manage firmware updates 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 from the vendor server 181A and the GUI provided from the vendor server 181B are different from each other and provided from the vendor server 181B. The burden for the user to become familiar with the GUI becomes heavy.

  Similarly, when the user changes the contract destination from OTA vendor A to OTA vendor C, the http post COMa shown in FIG. 2 is different from the http post COMc shown in FIG. 4 and is therefore provided from the vendor server 181A. The GUI provided from the vendor server 181C is different from the GUI provided by the vendor server 181C, and a burden for the user to become familiar with the GUI provided from the vendor server 181C is increased.

  That is, the burden on the user when changing the vendor server 181 used for updating the ECU firmware 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 configuration and operation.

  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, the management system 301 includes a terminal device 151, a management device 101, and vendor servers 181A, 181B, and 181C.

  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.

  The management system 301 is not limited to the configuration including the three vendor servers 181, but may be configured to include the two vendor servers 181 or four or more vendor servers 181.

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

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

  In order to input the name of the ECU to be registered, the type of the target vehicle 1 on which the ECU is mounted, and the name of the OTA vendor with which the contract is registered, into the GUI for ECU registration processing provided by the management apparatus 101 Column, an explanation corresponding to the column, a send button, and the like.

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

  With reference to FIG. 6, the management apparatus 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 information that can recognize the input source of the first process (hereinafter also referred to as input source recognition information), information that can recognize the first process, storage device identification information, and vendor server 181. Correspondence information indicating a correspondence relationship with information capable of recognizing the content of the second process for the above (hereinafter also referred to as template information) is stored. Here, the correspondence information indicates a correspondence relationship between the plurality of vendor servers 181.

  Specifically, as an example of the correspondence information, the storage unit 23 includes a template table indicating 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. A routing table indicating a correspondence relationship with identification information is held. 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 apparatus 101, for example.

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

  Referring 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 manages the vendor server 181 that can be managed by the management apparatus 101, and storage apparatus identification information. A template table TT1 indicating the correspondence between the IP address of 181, that is, the destination IP address, and the template for the second process corresponding to the first process is held.

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

  Specifically, the second processing template when the first processing and the destination IP address are “login processing” and “192.168.11.2”, respectively, is http of the http post COMa shown in FIG. In the body BODYa, the template TLa has blanked areas ““ OEM1 ””, ““ aaaaaaaaa ””, and ““ OEM1-DOMAIN ””.

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

  Note that the information capable of recognizing the first process is not limited to the name of the process such as the login process, but may be a URL corresponding to the process.

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

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

[Flow of operation]
Each device in the management system 301 includes a computer, and an arithmetic processing unit such as a CPU in the computer reads and executes a program including a part or all of each step of the following sequence diagram or flowchart from a memory (not shown). . Each of the programs of the plurality of apparatuses can be installed from the outside. The programs of the plurality of apparatuses are distributed while being stored in a recording medium.

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

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

  Next, the terminal device 151 creates the http request addressed to the URL for ECU registration processing in accordance with 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 receiving 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 the communication unit 21 receives an IP packet from the terminal device 151, the communication unit 21 extracts an http request from the received IP packet and outputs the extracted http request to the processing unit 22.

  When receiving 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 content 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 receiving the http response from the management apparatus 101, the terminal device 151 renders the ECU registration processing GUI on the Web browser based on the received http response (step S108).

  Next, the user, for example, the name of the ECU to be registered, the vehicle type of the target vehicle 1 on which the ECU is mounted, the name of the OTA vendor with which the contract is registered, and the IP of the vendor server 181 operated by the OTA vendor. Operations for inputting “ECU1”, “vehicle type α”, “OTA vendor A”, and “192.168.11.2” as addresses are performed on the Web browser. And a user performs operation which selects a transmission button with respect to a 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 in accordance with a user operation, and transmits the created http post to the management device 101 (step S112).

  More specifically, the terminal device 151 includes “ECU1” which is the name of the ECU, vehicle type information indicating “vehicle type α”, “OTA vendor A” which is the name of the registered OTA vendor, 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 receiving 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 input information including the content of the first process and 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 an example of the contents of the first processing. The IP address of the terminal device 151 included in the IP packet is an example of input source identification information.

  The communication unit 21 acquires the http post and the source IP address from the received IP packet, and outputs the acquired http post and the source 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 registered OTA vendor, and the IP address of the vendor server 181A from the received http post. The acquired information and the source IP address are registered in the routing table RT1a.

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

  More specifically, the processing unit 22 performs a second process corresponding to the first process indicated by the input information on 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 an “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 the name of the ECU, the vehicle type information, and other necessary information in the acquired template TRa, thereby creating an http post that is compatible with the vendor server 181A (hereinafter also referred to as post-conforming http post). To do.

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

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

  More specifically, when the communication unit 21 in the management apparatus 101 receives the post-conformance http post from the processing unit 22, the communication unit 21 includes the received post-adaptation http post and the destination IP address is “192.168.11.2”. A certain IP packet is created, and the created IP packet is transmitted to the vendor server 181A.

  Next, upon receiving the post-adaptation http post from the management apparatus 101, the vendor server 181A registers the name of the ECU and the 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 has been successful to the management apparatus 101 (step S122).

  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 apparatus 151 (step S124).

  The contents of the routing table RT1a are not limited to the configuration registered by the above-described sequence, but may be manually registered by the administrator of the management apparatus 101.

  Further, when the login process to the vendor server 181A has not been performed, the management apparatus 101 indicates that the authentication process has not been completed between steps S114 and S116 or between steps S116 and S118. After the response information is transmitted to the terminal device 151, the user is allowed to perform a log-in process which will be described later, and then the post-conformance http post is transmitted to the vendor server 181A (step S118).

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

  Referring to FIG. 10, first, the user performs an operation of transmitting an http request indicating a login processing GUI request to the login processing URL in the management apparatus 101, and a 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 login processing URL in accordance with the user's operation, and transmits the created http request to the management device 101 (step S204).

  Next, when receiving the http request from the terminal device 151, the management device 101 creates an http response indicating a login processing GUI in accordance with the received http request, and transmits the created http response to the terminal device 151 (Step 1). S206).

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

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

  Next, the user inputs “OEM1,” “Aaaaaaa,” “OEM1-DOMAIN,” and “Asia / Tokyo” in the fields for entering “user”, “password”, “domain”, and “location”, respectively. Each input operation is performed on the Web browser. Then, the user performs an operation for selecting a transmission button on the Web browser (step S210).

  Next, the terminal device 151 creates an http post addressed to the URL for the login process 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” in the http body as the user name, password, domain name, and location of use, respectively. Create a 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 receiving the IP packet from the terminal device 151, the management apparatus 101 acquires the IP address of the vendor server 181 corresponding to the source 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 source IP address from the IP packet received from the terminal device 151, and outputs the acquired http post and the source IP address to the processing unit 22. .

  The processing unit 22 receives the source IP address from the communication unit 21, refers to the routing table RT1a (see FIG. 8), and sets the IP address of the vendor server 181 corresponding to the source IP address as “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 apparatus 151 (step S216).

  More specifically, the processing unit 22 recognizes that the first process is a “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 processing” 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, thereby creating a post-conforming http post that matches 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-adapted http post to the communication unit 21.

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

  More specifically, when the communication unit 21 in the management apparatus 101 receives the post-conformance http post from the processing unit 22, the communication unit 21 includes the received post-adaptation http post and the destination IP address is “192.168.11.2”. A certain IP packet is created, and the created IP packet is transmitted to the vendor server 181A.

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

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

  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 S224).

[Upload process]
FIG. 11 is a diagram showing an example of a sequence when the management apparatus 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 for transmitting an http request indicating a request for a GUI for upload processing to the URL for upload processing in management device 101, and a Web browser displayed on the screen of terminal device 151. (Step S302).

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

  Next, when receiving the http request from the terminal device 151, the management device 101 creates an http response indicating a GUI for upload processing in accordance with the received http request, and transmits the created http response to the terminal device 151 (Step 1 S306).

  The upload processing GUI includes, for example, a column for inputting the name of the ECU to be registered, the vehicle type of the target vehicle 1 on which the ECU is mounted, and the file path of the firmware, an explanation corresponding to the column, and Includes a send button.

  Next, when receiving the http response from the management apparatus 101, the terminal device 151 renders an upload processing GUI 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. Are input to the Web browser. Then, the user performs an operation for selecting a transmission button on the Web browser (step S310).

  Next, the terminal device 151 creates an http post addressed to the URL for the upload process in the management device 101 in accordance with the user's operation, 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 “farmwear-oem1.exe” in the http body as the ECU name, 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 apparatus 101 receives an IP packet from the terminal apparatus 151, the management apparatus 101 refers to the routing table RT1a (see FIG. 8), and the IP address of the vendor server 181 corresponding to the source 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 apparatus 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 an 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 processing”.

  The processing unit 22 refers to the template table TT1 (see FIG. 7), and acquires a 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 to the acquired template TUa, thereby creating a post-conformation http post that includes the firmware file and conforms to the vendor server 181A.

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

  Next, the management apparatus 101 transmits an http post after adaptation 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 accumulates, ie, registers, a firmware file, specifically “firmware-oem1.exe” based on the received post-adaptation http post ( Step S320).

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

  Next, when receiving the response information from the vendor server 181A, the management device 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 the management system 301 after the user has changed the contract destination from OTA vendor A to OTA vendor B, for example.

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

  Referring to FIG. 13, the administrator of management apparatus 101 rewrites routing table RT1a (see FIG. 8) held by management apparatus 101 to routing table RT1b in response to, for example, the user changing the contract destination. 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 device 101 after the routing table has been rewritten to RT1b is converted into a post-conformance http post adapted to the vendor server 181B in the management device 101.

  On the other hand, since the management apparatus 101 provides the same GUI to the terminal apparatus 151 regardless of the rewriting of the routing table, the user of the terminal apparatus 151 can use the GUI before the rewriting of the routing table even after the routing table is rewritten to RT1b. An operation is performed on a Web browser on which the same GUI is rendered.

  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 user's operation target GUI 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. However, 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 between 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”. Also good.

  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. However, 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 a system capable of transmitting a command using the name of the vendor server 181, for example.

  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. However, the present invention is not limited to this. The input source identification information may be a determination identifier. In this case, the terminal device 151 transmits an IP packet including the determination identifier to the management device 101.

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

  The upload of the correction program to the program providing apparatus is performed, for example, by an OEM that has manufactured a vehicle to which the correction program is to be distributed.

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

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

  If at least one of the user interface and the information to be input is different before and after the change of the program providing apparatus, the user is unfamiliar with the user interface after the change or the information to be input, and the burden on the user becomes heavy. .

  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 relating to the data update of one or a plurality of devices mounted on the target vehicle 1 and the first. The input information including the input source identification information that can identify the input source of the process is acquired. The storage unit 23 includes information that can recognize the input source of the first process, information that can recognize the first process, 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 information capable of recognizing the content of the second process for the vendor server 181 is stored. The correspondence information indicates a correspondence relationship between a plurality of vendor servers 181 that are different in information to be given to execute the same second process or have different user interfaces for executing the same second process. Based on the correspondence information, the processing unit 22 executes a second process corresponding to the first process indicated by the input information on the vendor server 181 corresponding to the input source identification information indicated by the input 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, for example, the operation content required by the user differs depending on the vendor server 181. On the other hand, in the case where the user causes the vendor server 181 to execute the second process using the management apparatus 101, in any case where the vendor server 181 executes the second process, based on the correspondence information, Since the second process corresponding to the first process is executed, the input operation for the contents of the first process required by the user can be shared. Specifically, for example, when the vendor server 181 used for data update of the in-vehicle device is changed, the input operation required by the user before and after the change of the vendor server 181 can be maintained. Therefore, it is possible to prevent the burden on the user from becoming heavy in a configuration in which processing related to data update of the in-vehicle device is performed using a storage device that stores 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 second server 181 is surely connected to the vendor server 181 by using the above-mentioned address that is unique to the vendor server 181 and can be used as the destination of the contents of the second process, for example, as storage device identification information. 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.

  As described above, the vendor server 181 can be surely configured by using the above-mentioned address that is unique to the input source device of the first process and that can be used for transmission of input information as input source identification information. And it can specify easily.

  Next, another embodiment of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted 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 to the management system according to the first embodiment. The contents other than those described below are the same as those of the management system according to the first embodiment.

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

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

  The management system 301 is not limited to the configuration including the three vendor servers 181, but may be configured to include the two vendor servers 181 or four or more vendor servers 181.

  In addition, the management system 301 is not limited to the configuration including the three terminal devices 151, and may be configured to include 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 γ.

  Vendor servers 181A-181C each store the firmware used for ECU mounted in object vehicles 1A-1C, for example.

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

  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 update firmware 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 update firmware to the vendor server 181B by operating the terminal device 151B, for example.

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

  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 to FIG. 6 again, the communication unit 21 in the management apparatus 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 illustrating an example of a routing table held by the storage unit in the management apparatus according to the second embodiment of the present invention.

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

  For example, 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 by 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, in 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.

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

  Referring to FIGS. 14 and 15, for example, when management apparatus 101 receives IP packet Pra including an http post from terminal apparatus 151 </ b> A, based on the contents of received IP packet Pra, template table TT <b> 1 and routing table RT <b> 2. Then, a post-conforming http post that conforms to the vendor server 181A is created.

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

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

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

  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 contents of the received IP packet Prc, the template table TT1, and the routing table RT2. Create a post after http.

  The management apparatus 101 transmits the created IP packet Ptc including the post-adaptation 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. And the memory | storage part 23 memorize | stores the correspondence information about the said several input source.

  With such a configuration, a single management apparatus 101 can handle a plurality of users.

  Since other configurations and operations are the same as those of the management apparatus according to the first embodiment, detailed description thereof will not be repeated here.

  Note that some or all of the components and operations of the devices according to the first embodiment and the second embodiment of the present invention can be combined as appropriate.

  The above embodiment should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  The above description includes the following features.

[Appendix 1]
An acquisition unit that acquires input information including content of a first process related to data update of one or more devices mounted on a vehicle and input source identification information that can identify an input source of the first process;
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 for storing correspondence information indicating a correspondence relationship with information capable of recognizing the content of the processing,
The correspondence information indicates the correspondence relationship between a plurality of the storage devices that are different in information to be given in order to execute the same second process or that have different user interfaces for executing the same second process. ,
further,
A processing unit configured to execute the second process corresponding to the first process indicated by the input information on the storage device corresponding to the input source identification information indicated by the input information based on the correspondence information; Prepared,
The device is an ECU (Electronic Control Unit),
The second process is a login process, an upload process, an update schedule registration process or an ECU registration process,
The first process is a process corresponding to the second process,
The input source identification information is an IP address of the input source device, or a determination identifier indicating the name of the vehicle model and the device,
The storage device identification information is an IP address of the storage device or a name of the storage device,
The management apparatus, 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 that acquires input information including content of a first process related to data update of one or more devices mounted on a vehicle and input source identification information that can identify an input source of the first process;
Information capable of recognizing the input source, information capable of recognizing the first processing, 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 for storing correspondence information indicating a correspondence relationship with information capable of recognizing the contents of
The correspondence information indicates the correspondence relationship between a plurality of the storage devices that are different in information to be given in order to execute the same second process or that have different user interfaces for executing the same second process. ,
further,
A processing unit configured to execute the second process corresponding to the first process indicated by the input information on the storage device corresponding to the input source identification information indicated by the input information based on the correspondence information; A management device.   The management device according to claim 1, wherein the storage device identification information is an address of the storage device.   The management apparatus according to claim 1, wherein the input source identification information is an address of the input source apparatus. The acquisition unit can acquire 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 for a plurality of the input sources. A management method in a management device including a storage unit,
Including the step of acquiring input information including the content of the first process relating to data update of one or more devices mounted on the vehicle and the input source identification information capable of identifying the input source of the first process;
The storage unit includes 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 the storage device Storing correspondence information indicating a correspondence relationship with information capable of recognizing the content of the second processing for
The correspondence information indicates the correspondence relationship between a plurality of the storage devices that are different in information to be given in order to execute the same second process or that have different user interfaces for executing the same second process. ,
further,
Performing the second process corresponding to the first process indicated by the input information on 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 including a storage unit,
Computer
An acquisition unit that acquires input information including content of a first process relating to data update of one or more devices mounted on a vehicle and input source identification information that can identify an input source of the first process;
As a program to function as
The storage unit includes 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 the storage device Storing correspondence information indicating a correspondence relationship with information capable of recognizing the content of the second processing for
The correspondence information indicates the correspondence relationship between a plurality of the storage devices that are different in information to be given in order to execute the same second process or that have different user interfaces for executing the same second process. ,
In addition, the computer
A processing unit configured to execute the second process corresponding to the first process indicated by the input information on 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