JP5835090B2 - Malfunction prevention device for plural devices and malfunction prevention method for plural devices - Google Patents

Description

  The present invention relates to a technique for preventing malfunction of a plurality of devices.

  In an apparatus capable of operating a program, the user of the apparatus can update the version of the program by obtaining the upgraded program from the Internet or the like. However, the configuration and hardware version of a device that can be executed (guaranteed) are determined for the program, and the device does not operate if a non-guaranteed version of the program is written to the device.

  As a method of checking the combination of the device and the program and preventing malfunction of the program, the device identification information is compared with the hash code created from the program, and the embedded device is operated according to the comparison result. There is a method for restricting the execution of this program (see, for example, Patent Document 1).

JP-A-2005-301968

  When the device's encrypted device identification information and the digest (hash value) generated from the program are executed by the device, the device's individual identification information and the digest regenerated from the program in the device are decrypted. The purpose of the comparison check with the digest is to prevent the program from being altered and illegally copied by associating the device with the program in advance. For this reason, when a plurality of devices having different functions are combined and configured, there is a problem that it is not possible to determine whether the program is executable in the combination of the plurality of devices.

  The present invention has been made to solve the above-mentioned problems, and in the case where a plurality of devices having different functions are combined to constitute a program that can be executed in a combination of a plurality of devices. The purpose is to judge.

  The present invention is one-way from a device configuration ID generating unit that generates a device configuration ID using device information that can identify each type of a plurality of devices that are communicably connected, and a program stored in each device. The program digest generated using the sex function and the device configuration ID are executed by a combination of the execution feasibility judgment information generating means for generating the feasibility judgment information using the one-way function and the program operating on each device. Program execution feasibility judgment means for judging whether or not there is a match with the execution feasibility judgment information generated using the executable program information indicating the combination of possible program execution feasibility judgment information It is provided with.

  The present invention is one-way from a device configuration ID generating unit that generates a device configuration ID using device information that can identify each type of a plurality of devices that are communicably connected, and a program stored in each device. The program digest generated using the sex function and the device configuration ID are executed by a combination of the execution feasibility judgment information generating means for generating the feasibility judgment information using the one-way function and the program operating on each device. Program execution feasibility judgment means for judging whether or not there is a match with the execution feasibility judgment information generated using the executable program information indicating the combination of possible program execution feasibility judgment information Because it is determined whether it is a combination of programs that can be executed by a combination of type information of devices constituting a plurality of devices. It is possible to prevent the malfunction of the program.

The figure which shows the malfunction prevention apparatus for confirming that it is a program which can be performed according to the structure or combination of a some apparatus and several apparatus in Embodiment 1. FIG. 6 is a flowchart showing operations of the malfunction prevention apparatus and other apparatuses for confirming that the program is executable according to the configuration or combination of the plurality of apparatuses and the plurality of apparatuses in the first embodiment. The figure which shows the malfunction prevention apparatus for confirming that it is a program executable according to the structure or combination of a some apparatus and several apparatus in Embodiment 2. FIG. 7 is a flowchart showing the operation of a malfunction prevention device and other devices for confirming that the program is executable according to the configuration or combination of a plurality of devices and a plurality of devices in the second embodiment. FIG. 5 is a configuration diagram of the malfunction preventing apparatus 100 according to the third embodiment.

Embodiment 1 FIG.
In the first embodiment, a malfunction preventing apparatus for confirming that a program is executable according to the configuration or combination of a plurality of apparatuses will be described.

  FIG. 1 is a diagram illustrating a malfunction prevention apparatus for confirming that a program is executable according to the configuration or combination of a plurality of apparatuses and a plurality of apparatuses in the first embodiment.

The malfunction prevention apparatus 100 is connected to a plurality of other apparatuses 101, 102, and 103 so as to communicate with each other.
The configuration of the malfunction prevention device 100 will be described.
The device information extraction request unit 1 requests the other devices 101, 102, and 103 to collect device information in order to collect device information of all connected devices.
The device information storage unit 2a stores device information such as device type, connection order, model number, and hardware version that can identify the product type of the malfunction prevention device 100.

The device information extraction unit 3a extracts information stored in the device information storage unit 2a.
The program storage unit 4 a stores software (program) for controlling the operation of the malfunction prevention device 100.
The program digest generation unit 5a generates a program digest (hash value) using a one-way function (hash function) for the software (program) stored in the program storage unit 4a.

The device configuration ID generation unit 7 performs other operations based on the device information of the other devices 101, 102, and 103 collected by the device information extraction request unit 1 and the device information of the malfunction prevention device 100 acquired from the device information extraction unit 3a. A device configuration ID (abbreviation of identification) that is a code that can be identified from the combination of the devices is generated.
The executability determination information generation unit 8 is generated by the device configuration ID generated by the device configuration ID generation unit 7, the program digest generation unit 5a of the malfunction prevention device 100, and the program digest generation unit 5b of the other devices 101, 102, 103. Execution feasibility judgment information for judging whether or not the program can be operated by a combination of the malfunction prevention apparatus 100 using the one-way function and the other apparatuses 101, 102, 103 from the digest of the program obtained. .

The executable program information storage unit 9 is executable program information indicating a combination of program execution feasibility determination information that can be executed by a combination of a program or a program version that operates in the malfunction prevention apparatus 100 and the other apparatuses 101, 102, and 103. Is stored.
In the executable program information storage unit 9, information in the same format as the execution availability determination information generated by the execution availability determination information generation unit 8 is stored in a list by the number of combinations of all executable programs. Yes.
The program executability determination unit 10 compares the executability determination information generated by the executability determination information generation unit 8 with the executable program information stored in the executable program information storage unit 9, and stores the executable program information. If information matching the section 9 is found, it is determined that the program can be executed, and if it is not found, it is determined that the program cannot be executed.

The execution feasibility judgment result notifying unit 11 notifies the program execution unit 12a and the program execution unit 12b of the other devices 101, 102, 103 of the judgment result of the program execution feasibility judged by the program execution feasibility judgment unit 10.
The program execution unit 12a stores the control program storage unit 4a only when the determination result is determined to be executable based on the determination result of the program execution permission determination unit 10 in response to the notification from the execution permission determination result notification unit 11. Read and execute the stored program.

Next, the configuration of the other apparatuses 101, 102, 103 will be described. Note that, regarding the configuration of the other apparatus 101 described below, it is assumed that the same functions are included in the other apparatuses 102 and 103.
The device information storage unit 2b stores device information such as device type, connection order, model number, and hardware version that can identify the product type of another device.

The device information extraction unit 3b extracts information stored in the device information storage unit 2b.
The program storage unit 4b stores software (program) for controlling the operation of the other apparatus 101.
The program digest generation unit 5b generates a program digest (hash value) using a one-way function (hash function) for the software (program) stored in the program storage unit 4a.

  The request reception unit 6 receives the request from the device information extraction request unit 1 of the malfunction prevention device 100, analyzes the request content, and extracts the device information and sends a response to the device information extraction unit 3b according to the received request content. In addition to issuing a command and a program digest generation and reply command to the program digest generation unit 5b, the device information of the device information extraction unit 3b and the program digest from the program digest generation unit 5b are also used as device information of the malfunction prevention device 100. It is transmitted to the extraction request unit 1.

  The program execution unit 12b receives the notification from the execution feasibility judgment result notifying unit 11 of the malfunction prevention device 100 and determines that the judgment result is executable based on the judgment result of the program execution feasibility judgment unit 10 of the malfunction prevention device 100. Only when the program is stored, the program stored in the control program storage unit 4b is read and executed.

Next, the operation will be described.
FIG. 2 is a flowchart showing the operation of the malfunction preventing apparatus and other apparatuses for confirming that the program is executable according to the configuration or combination of the plurality of apparatuses and the plurality of apparatuses in the first embodiment.

In step S101, before the malfunction prevention apparatus 100 and the other apparatuses 101, 102, 103 start executing the programs, the apparatus information extraction request unit 1 of the malfunction prevention apparatus 100 requests the other apparatuses 101, 102, 103. Request device information such as device type, connection order, model number, and hardware version.
At this time, the malfunction preventing apparatus 100 confirms the connection order of the other apparatuses 101, 102, 103 and the number of connected apparatuses. The connection order and the number of connected devices may be used for the device configuration ID generated by the device configuration ID generation unit in FIG.

Upon receiving the instruction from the device information extraction request unit 1 in step S102, the request accepting unit 6 of the other device 101, 102, 103 receives the type of the other device stored in the device information storage unit 2b in the device information extraction unit 3b. Instructs to extract device information such as model number, hardware version, etc., and obtains device information.
The type of the other device means a function of the other device, and corresponds to, for example, a CPU, a communication function, a data display function, and a data management function in the device.
The request reception unit 6 returns the extracted device information to the device information extraction request unit 1 of the malfunction prevention device 100.

  In step S103, the device configuration ID generation unit 7 stores the device information received from the request reception unit 6 in the device information extraction request unit 1 and the device information storage unit 2a obtained by requesting the device information extraction unit 3a. The device configuration ID is generated from the device information of the malfunction prevention device 100 being used using information such as the connection order of other devices and the number of devices. Various methods can be considered as a method for generating the device configuration ID. Identification information may be assigned in advance to the type of device, and this identification information may be stored in the device information storage units 2a and 2b. The device configuration ID may connect the device connection order and the device model number indicated by the identification information assigned to the number of connected devices and the device type. In short, not only the malfunction prevention apparatus 100 but also each of the plurality of apparatuses whose normal operation has been confirmed by generating apparatus configuration IDs using part or all of the apparatus information for the other apparatuses 101, 102, 103. It is to manage multiple program information so that it can be recognized that the connected device has changed.

In step S <b> 104, the executability determination information generation unit 8 requests the request reception unit 6 of the other devices 101, 102, 103 to generate a digest of the program of each of the other devices 101, 102, 103.
In step 105, the request receiving unit 6 that has received the request instructs the program digest generating unit 5b to generate a program digest. The program digest generation unit 5b generates a program digest (hash value) from the program stored in the program storage unit 4b using a one-way function, and returns the generated program digest to the request reception unit 6.

In step S106, the execution possibility determination generation unit 8 generates the program digest generation unit 5a from the digest of each of the other devices 101, 102, 103 returned to the request reception unit 6 and the program stored in the program storage unit 4a. Executability determination information is generated using a one-way function using the program digest and the device configuration ID generated by the device configuration ID generation unit 7.
In addition to the malfunction prevention device 100, the other devices 101, 102, and 103 generate execution feasibility determination information by using a part or all of the device information, so that a plurality of devices that have been confirmed to operate normally and a plurality of devices that each has. The program information is managed so that not only the connected device but also each program can be recognized.

In step S <b> 107, the program execution determination unit 10 determines the combination of the execution determination information generated by the execution determination information generation unit 8 and the connected device stored in the executable program information storage unit 9. By comparing and checking executable program information indicating a combination of executable programs, it is confirmed whether there is a combination of executable programs by checking whether there is matching executable program information.
The executable program information stored in the executable program information storage unit 9 is executed by the executable determination information generating unit 8 when a program installed in advance at the time of product shipment of the malfunction prevention apparatus 100 is fixed. Executable program information for all combinations of programs that can be executed by the same method as the above algorithm may be generated and stored. In addition, when a program installed in advance at the time of product shipment is not fixed and a user installs and sets a program, executable program information may be downloaded and stored using a communication line.

  If it is a combination of executable programs, it is determined in step S108 that the program can be executed, and the program execution availability determination unit 10 sends the program execution availability determination result to the execution availability determination result notification unit 11. Then, the execution determination result notifying unit 11 notifies the program execution unit 12b of the other apparatuses 101, 102, and 103 and the program execution unit 12a of the malfunction preventing apparatus 100 of the determination result of the execution of the program. Based on the determination result, the program execution unit 12b of the other apparatus 101, 102, 103 or the program execution unit 12a of the malfunction prevention apparatus 100 executes the program.

  If it is not a combination of executable programs, it is determined in step S109 that the program cannot be executed, and the program execution availability determination unit 10 sends the program execution availability determination result to the execution availability determination result notification unit 11. Then, the execution determination result notifying unit 11 notifies the program execution unit 12b of the other apparatuses 101, 102, and 103 and the program execution unit 12a of the malfunction preventing apparatus 100 of the determination result of the execution of the program. Based on the determination result, the program execution unit 12b of the other apparatus 101, 102, 103 or the program execution unit 12a of the malfunction prevention apparatus 100 stops the execution of the program.

  Therefore, the malfunction prevention apparatus in this embodiment generates the apparatus configuration ID using the apparatus information that can individually identify the types of the malfunction prevention apparatus 100 and a plurality of other apparatuses 101, 102, and 103 that are communicably connected. A program digest and a device configuration generated using a one-way function from programs stored in the device configuration ID generation unit 7, the malfunction prevention device 100, and a plurality of other devices 101, 102, and 103 connected to be communicable Executable / non-executable / non-executable information generating unit 8 that generates ID / non-executable / non-executable / non-executable information by using a one-way function, and a combination of programs that respectively operate in malfunction prevention device 100 and other devices 101, 102, and 103 The execution feasibility judgment information generated by using the executable program information indicating the combination of the program execution feasibility judgment information. Since the program execution feasibility judgment unit 10 that judges whether or not there is a match is determined by the program execution feasibility judgment unit 10, it is a combination of programs that can be executed by a combination of type information of devices constituting a plurality of devices. Therefore, it is possible to prevent malfunction of the program.

Embodiment 2. FIG.
In the first embodiment, the malfunction of the program is prevented based on the executable program information operable in a combination of a plurality of devices. However, in the present embodiment, the program is executed only by the plurality of combined devices. If you want to make it possible, in addition to the configuration information of multiple devices and the digest of the program, combine the individual identification information of each device to check the combination of programs that can be executed on the embedded device before execution to prevent program malfunction The function for this is demonstrated.

FIG. 3 is a diagram showing a malfunction prevention device for confirming that the program is executable according to the configuration or combination of a plurality of devices and a plurality of devices in the second embodiment.
Since it is basically the same as that of the first embodiment, only different parts of the configuration and operation will be described.

  As an overview of the present embodiment, as in the first embodiment, when checking a combination of programs that can be executed according to the configuration of a plurality of devices, the malfunction prevention device 100 and the other devices 101, 102, 103 Combining each individual identification information (for example, serial number) to generate a device configuration ID and execution feasibility judgment information, and preventing malfunction of the program that controls the execution of the program based on the result judged by the program execution feasibility judgment unit 10 Device.

In FIG. 3, the device information extraction unit 3a of the malfunction prevention device 100 extracts information stored in the device information storage unit 2a and extracts device individual identification information stored in the device individual identification information storage unit 13a. .
The device individual identification information storage unit 13a stores preset device individual identification information for individual identification of the malfunction prevention device 100. The device individual identification information includes, for example, a device individual such as a manufacturing number and a MAC address. Any information can be used as long as it can be identified.

Similarly, the device information extraction unit 3b of the other devices 101, 102, 103 extracts the information stored in the device information storage unit 2b and extracts the device individual identification information stored in the device individual identification information storage unit 13b. Extract.
The device individual identification information storage unit 13b stores preset device individual identification information for individual identification of the other devices 101, 102, and 103. The device individual identification information includes, for example, a manufacturing number and a MAC address. Any information can be used as long as it can identify the individual device.

Next, the operation will be described.
FIG. 4 is a flowchart showing operations of the malfunction prevention apparatus and other apparatuses for confirming that the program is executable according to the configuration or combination of the plurality of apparatuses and the plurality of apparatuses in the second embodiment.
In step S201, before the malfunction prevention device 100 and the other devices 101, 102, 103 start executing the programs, the device information extraction requesting unit 1 of the malfunction prevention device 100 requests the other devices 101, 102, 103. Request device information such as device type, connection order, model number, hardware version, and device individual identification information.
At this time, the malfunction preventing apparatus 100 confirms the connection order of the other apparatuses 101, 102, 103 and the number of connected apparatuses. The connection order and the number of connected devices may be used for the device configuration ID generated by the device configuration ID generation unit in FIG.

Upon receiving the instruction from the device information extraction request unit 1 in step S202, the request accepting unit 6 of the other devices 101, 102, 103 receives the type of the other device stored in the device information storage unit 2b in the device information extraction unit 3b. The device information such as model number, hardware version is instructed to be extracted to obtain the device information, and the device individual identification information stored in the device individual identification information storage unit 13b is instructed to obtain the device individual identification information. .
The request reception unit 6 returns the extracted device information to the device information extraction request unit 1 of the malfunction prevention device 100.

  In step S203, the device configuration ID generation unit 7 receives the device information and device individual identification information received from the request reception unit 6 in the device information extraction request unit 1, and the device information obtained by requesting the device information extraction unit 3a. Using information such as the connection order of other devices and the number of devices from the device information of the malfunction preventing device 100 stored in the storage unit 2a and the device individual identification information stored in the device individual identification information storage unit 13a A device configuration ID is generated.

In step S <b> 204, the executability determination information generation unit 8 requests the request reception unit 6 of the other devices 101, 102, 103 to generate a digest of the program of each of the other devices 101, 102, 103.
In step S205, the request receiving unit 6 that has received the request instructs the program digest generating unit 5b to generate a digest of the program. The program digest generation unit 5b generates a program digest (hash value) from the program stored in the program storage unit 4b using a one-way function, and returns the generated program digest to the request reception unit 6.

  In step S206, the execution possibility determination generation unit 8 generates the program digest generation unit 5a from the digest of each of the other devices 101, 102, 103 returned to the request reception unit 6 and the program stored in the program storage unit 4a. Executability determination information is generated using a one-way function using the program digest and the device configuration ID generated by the device configuration ID generation unit 7.

In step S <b> 207, the program execution availability determination unit 10 determines the combination of the execution availability determination information generated by the execution availability determination information generation unit 8 and the connected device stored in the executable program information storage unit 9. By comparing and checking executable program information indicating a combination of executable programs, it is confirmed whether there is a combination of executable programs by checking whether there is matching executable program information.
The executable program information stored in the executable program information storage unit 9 is executed by the executable determination information generating unit 8 when a program installed in advance at the time of product shipment of the malfunction prevention apparatus 100 is fixed. Executable program information that combines all combinations of programs that can be executed by the same method as the above algorithm and the individual device information to be used is generated and stored.

  If it is a combination of executable programs, it is determined in step S208 that the program can be executed, and the program execution availability determination unit 10 sends the program execution availability determination result to the execution availability determination result notification unit 11. Then, the execution determination result notifying unit 11 notifies the program execution unit 12b of the other apparatuses 101, 102, and 103 and the program execution unit 12a of the malfunction preventing apparatus 100 of the determination result of the execution of the program. Based on the determination result, the program execution unit 12b of the other apparatus 101, 102, 103 or the program execution unit 12a of the malfunction prevention apparatus 100 executes the program.

  If it is not a combination of executable programs, in step S209, it is determined that the program cannot be executed, and the program execution availability determination unit 10 sends the program execution availability determination result to the execution availability determination result notification unit 11. Then, the execution determination result notifying unit 11 notifies the program execution unit 12b of the other apparatuses 101, 102, and 103 and the program execution unit 12a of the malfunction preventing apparatus 100 of the determination result of the execution of the program. Based on the determination result, the program execution unit 12b of the other apparatus 101, 102, 103 or the program execution unit 12a of the malfunction prevention apparatus 100 stops the execution of the program.

  Therefore, the malfunction prevention apparatus in this embodiment uses the apparatus configuration ID using the apparatus information that can identify the malfunction prevention apparatus 100 and the types of the plurality of other apparatuses 101, 102, and 103 that are communicably connected to each other. A program digest generated using a one-way function from programs stored in the device configuration ID generation unit 7, the malfunction prevention device 100, and a plurality of other devices 101, 102, and 103 connected so as to communicate with each other And an apparatus configuration ID using an unidirectional function to generate execution determination information, and a combination of programs that respectively operate in the malfunction prevention apparatus 100 and other apparatuses 101, 102, and 103. Execution feasibility judgment generated using executable program information indicating a combination of program execution feasibility judgment information executable by A program that can be executed by combining individual identification information of devices that constitute a plurality of devices, since the program execution availability determination unit 10 that determines whether or not there is a match to information is included. Therefore, it is possible to prevent malfunction of the program.

Embodiment 3 FIG.
In the present embodiment, the executable program stored in the executable program information storage unit 9 used to check the combination of executable programs according to the combination of the configurations of the plurality of apparatuses in the first or second embodiment. A function for updating program information will be described.
FIG. 5 is a configuration diagram of the malfunction preventing apparatus 100 according to the third embodiment.
The configuration will be described below, but only the parts different from the first or second embodiment will be described.

In FIG. 5, the update data acquisition unit 14 is information necessary for updating executable program information that is a combination of programs that can be executed according to the combination of the configurations of the malfunction prevention apparatus 100 and the other apparatuses 101, 102, and 103 ( Update data).
The executable program information update unit 15 updates information (update data) necessary for updating the executable program information acquired by the update data acquisition unit 14 in the executable program information storage unit 9.

An operation when updating executable program information will be described.
The update data acquisition unit 14 acquires update data necessary for updating executable program information in accordance with an instruction from the user to the malfunction prevention apparatus 100. As the acquisition method, for example, when the malfunction prevention device 100 can read the memory card, the acquisition is performed from the memory card, or the update data necessary for updating the executable program information is acquired via the network. A method is conceivable. The update data acquisition unit 14 passes the acquired update data to the executable program information update unit 15.

Next, the executable program information update unit 15 updates the executable program information stored in the executable program information storage unit 9 based on the received update data.
In the case of the second embodiment, since the malfunction prevention device 100 and other devices 101, 102, and 103 that are used are limited, the executable program information update unit 15 updates the device individual information including the device individual information. Executable program information is generated, and the executable program information is updated.

  Note that when the executable program information is stored in the executable program information storage unit 9, the version of the executable program information and the creation date and time information are also stored. The executable program information update unit 15 checks the executable program in the executable program information storage unit 9 and the creation date and version of the update data before updating the executable program information in the executable program information storage unit 9. Then, update is performed after confirming that the update data is newer, and the executable program information cannot be updated if the update data is older.

  Therefore, the malfunction preventing apparatus in this embodiment is an executable program that indicates a combination of program execution feasibility determination information that can be executed by a combination of programs that operate in the malfunction preventing apparatus 100 and the other apparatuses 101, 102, and 103, respectively. An executable program information storage unit for storing information, an update data acquisition unit for acquiring data for updating the executable program information, and generating executable program information updated using the acquired update data, Since the executable program information update unit for updating the executable program information stored in the executable program information storage unit is provided, a combination of executable programs corresponding to a combination of individual identification information of devices constituting a plurality of devices Can be updated.

DESCRIPTION OF SYMBOLS 1 Device information extraction request | requirement part 2a, 2b Device information storage part 3a, 3b Device information extraction part 4a, 4b Program storage part 5a, 5b Program digest production | generation part 6 Request reception part 7 Device structure ID production | generation part 8 Executability determination information generation part 9 Executable Program Information Storage Unit 10 Program Executability Determination Unit 11 Executability Determination Result Notification Units 12a and 12b Program Execution Units 13a and 13b Device Individual Identification Information Storage Unit 14 Update Data Acquisition Unit 15 Executable Program Information Update Unit 100 Malfunction Prevention Device 101 Other device 102 Other device 103 Other device

Claims (4)

A device configuration ID generating means for generating a device configuration ID using device information that can identify each type of the plurality of devices connected to each other in a communicable manner;
Executeability determination information generating means for generating executability determination information using the unidirectional function for the program digest generated from a program stored in each device using the unidirectional function and the device configuration ID; ,
It is determined whether there is a match with the generated execution determination information using executable program information indicating a combination of program execution determination information executable by a combination of programs operating on each of the devices. Program execution availability determination means for determining whether or not the program can be executed,
An apparatus for preventing malfunction. A device configuration ID generating means for generating a device configuration ID using device information capable of identifying each kind of the plurality of devices and other devices connected to be communicable with each other; and
The malfunction prevention apparatus according to claim 1, further comprising: Executable program information storage means for storing executable program information according to claim 1;
Update data acquisition means for acquiring data for updating the executable program information;
Executable program information updating means for generating executable program information updated using the acquired update data and updating executable program information stored in the executable program information storage means;
The malfunction prevention apparatus according to claim 1 or 2, further comprising: A device configuration ID generating step for generating a device configuration ID using device information that can identify each type of the plurality of devices connected to each other in a communicable manner;
An execution possibility determination information generating step for generating execution determination information using the one-way function for the program digest generated from the program stored in each of the apparatuses using the one-way function and the device configuration ID; ,
It is determined whether there is a match with the generated execution determination information using executable program information indicating a combination of program execution determination information executable by a combination of programs operating on each of the devices. A program execution availability determination step for determining whether or not the program can be executed,
A method for preventing malfunction .

Images