WO2016170641A1 - プログラム更新装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法 - Google Patents

プログラム更新装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法 Download PDF

Info

Publication number
WO2016170641A1
WO2016170641A1 PCT/JP2015/062391 JP2015062391W WO2016170641A1 WO 2016170641 A1 WO2016170641 A1 WO 2016170641A1 JP 2015062391 W JP2015062391 W JP 2015062391W WO 2016170641 A1 WO2016170641 A1 WO 2016170641A1
Authority
WO
WIPO (PCT)
Prior art keywords
unit
update
program
information
rule
Prior art date
Application number
PCT/JP2015/062391
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
鈴木　大輔
英之 小黒
瞬也 長谷川
友義 上野
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to PCT/JP2015/062391 priority Critical patent/WO2016170641A1/ja
Priority to JP2016514185A priority patent/JP5951162B1/ja
Priority to TW104132792A priority patent/TWI599906B/zh
Publication of WO2016170641A1 publication Critical patent/WO2016170641A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring

Definitions

  • the present invention also relates to a program update device, a composite unit device, an update determination program, and a program update method.
  • firmware software that defines the operation of embedded devices.
  • the firmware may be referred to as FW.
  • FW firmware that allows end users to update FW
  • the function of updating the FW is partially used not only in consumer products but also in industrial control devices used in plants and factories and electronic devices that control automobiles.
  • a function capable of updating the FW is referred to as an FW update function.
  • the FW update function is used in the following procedure by the end user. (1) The end user obtains an updated FW file from the manufacturer's website. (2) The end user inputs the manufactured and acquired file to the target embedded device via a network or a recording medium. (3) The embedded device rewrites the firmware based on the FW file.
  • Non-Patent Document 1 describes a technique for preventing arbitrary modification of FW by using falsification detection to a message using a digital signature or a message authentication code.
  • industrial control devices and electronic control devices for automobiles are not used alone by end users, and that final products using these devices as parts are produced by other manufacturers. is there.
  • the manufacturer of the final product is responsible for managing the FW of each device as the final product.
  • the industrial control device is made into a component and the final product is configured by combining a plurality of them. That is, it is necessary not only to manage the FW of each device as a single unit but also to manage it as a plurality of combinations.
  • systems such as control systems which have a large impact when interruption or stoppage due to the occurrence of some kind of failure occurs, eliminate events that may affect system operation such as FW updates as much as possible. It can be said that it tends to.
  • Non-Patent Document 2 For example, as shown in the example of “Copy Exactly!” Disclosed in Non-Patent Document 2, the risk of malfunction is reduced by constructing the production system without any shaking.
  • Componentized industrial control devices are not limited in application and are configured with versatile specifications. Of course, the operation of the industrial control device is guaranteed within its specifications.
  • a final product having an industrial control device as one of a plurality of components is system-up after grasping the specifications of the industrial control device.
  • the quality of the final product cannot be verified in consideration of all the fluctuations (variations within the specification allowable range) of each component such as an industrial control device.
  • the manufacturer that manufactures the final product needs to be able to control and limit the use of the end user of the FW update function of the industrial control device.
  • the final product consisting of a plurality of control devices must be managed as a combination of the FWs of the individual control devices. Therefore, the FW update function needs to be able to control and limit the use by the end user in consideration of the combination of FW.
  • the object of the present invention is to provide a configuration in which a manufacturer of a final product can control and limit the use of an end user of the FW update function of a control device.
  • the program update device of the present invention provides: A program storage unit for storing the program; A rule storage unit that stores rule information in which rules for updating the program are defined; An update information receiving unit for receiving update information for updating the program; A determination unit that determines whether the update information matches the rule information; And an update unit that updates the program stored in the program storage unit using the update information when it is determined that the determination unit is suitable.
  • This invention enables the manufacturer of the final product to control and limit the use of the end user of the FW update function of the control device.
  • FIG. 3 is a diagram illustrating the configuration of the FW update system 1 according to the first embodiment.
  • FIG. 2 shows the first embodiment, and shows FIG. 1 in a connected state to a communication network 40.
  • FIG. 5 shows the first embodiment, and is a diagram for explaining a process in which the set maker 20 ships a final product including the control device 105.
  • the figure which shows Embodiment 1 and shows the rule file 205 in which the update rule of the project file 202 and FW was described.
  • FIG. 3 is a diagram illustrating the first embodiment, and illustrates a control device 105 and a project file 202 that are passed from the set maker 20 to the end user 30.
  • FIG. 3 is a diagram illustrating the first embodiment and is a block diagram illustrating a configuration of a control device 105
  • FIG. 5 is a diagram illustrating the first embodiment, and is a sequence diagram illustrating operations of the end user device 300 and the control device 105 (30) in the end user 30.
  • FIG. 5 shows the first embodiment, and shows a state in which a plurality of units A to E use firmware A to E.
  • FIG. 3 is a diagram illustrating the first embodiment and is a block diagram illustrating a configuration of a unit A.
  • FIG. 5 shows the first embodiment, and shows a rule file 205A of unit A.
  • FIG. 5 is a diagram illustrating the first embodiment, and is a block diagram illustrating a configuration in which the control device 105 (30) includes a version acquisition unit.
  • FIG. 5 shows the first embodiment, and shows a sequence in which unit A obtains a version.
  • FIG. 9 is a diagram illustrating the second embodiment and illustrates a hardware configuration of a control device.
  • FIG. 1 shows a configuration of an FW update system 1 necessary for FW update.
  • FIG. 2 is a diagram illustrating FIG. 1 in a state of connection to the communication network 40. 2 shows a block configuration diagram of the FW distribution server apparatus 100 (hereinafter, distribution server 100), the set maker apparatus 200, and the end user apparatus 300.
  • the distribution server 100 includes a control unit 110, an update information generation unit 120, a communication unit 130, and a storage unit 140.
  • the control unit 110 controls the operation of the distribution server 100.
  • the update information generation unit 120 generates an update FW 102 to be described later.
  • the communication unit 130 communicates with the set maker device 200 and the end user device 300 via the communication network 40.
  • the storage unit 140 stores information such as the update FW 102.
  • the set maker apparatus 200 includes a development tool execution unit 210, a communication unit 220, and a storage unit 230.
  • the development tool execution unit 210 executes the development tool 201 that is a program stored in the storage unit 230.
  • the communication unit 220 communicates with the distribution server 100 and the end user device 300 via the communication network 40.
  • the storage unit 230 stores information such as the development tool 201.
  • the development tool execution unit 210 includes a project file generation unit 211 that generates a project file 202 described later, and a rule information generation unit 212 that generates a rule file described later.
  • the end user device 300 includes a development tool execution unit 310, a communication unit 320, and a storage unit 330.
  • the development tool execution unit 310 executes the development tool 301 that is a program stored in the storage unit 330.
  • the communication unit 320 communicates via the communication network 40.
  • the storage unit 330 stores information such as the development tool 301.
  • the control apparatus manufacturer 10 in FIG. 1 has a distribution server 100 that distributes FW, and manages the update FW 102.
  • the control device manufacturer 10 is a manufacturer that manufactures a control device. As a specific example, when the final product is a PLC (programmable logic controller), a CPU unit, a communication unit, or the like constituting the PLC is a control device. A control device is a device that controls other devices.
  • the update FW 102 is information for updating the FW included in the control device 105. Note that FW is a program. Therefore, the update FW 102 is update information for updating a program included in the control device 105.
  • the update FW 102 may be difference information between the FW before the update and the FW after the update, or may be overall information that replaces all of the FW before the update. Note that the rule file 205 is also updated, but the rule file 205 may also be difference information or overall information, similar to the update FW 102.
  • the distribution server 100 is connected to the communication network 40 and accepts access from the set maker device 200 and the end user device 300 via the communication unit 130.
  • the 1 has a set maker apparatus 200 in which a development tool 201 provided from the control apparatus maker 10 is stored.
  • the set maker device 200 is connected to the control device 105 (20).
  • the set maker 20 uses the development tool 201 stored in the set maker apparatus 200 for the control apparatus 105 (20) to perform additional development according to its own purpose.
  • the set maker 20 recognizes the necessity of FW update by the notification from the control device maker 10 or the periodic confirmation.
  • the set maker 20 downloads the update FW 102 from the distribution server 100 using the set maker apparatus 200.
  • the downloaded update FW 102 is transmitted to the control device 105 (20) of the set maker 20 via the set maker device 200.
  • the control device 105 (20) updates its own FW with the received update FW102.
  • control device 105 is shown for each of the control device manufacturer 10, the set manufacturer 20, and the end user 30, but the control device 105 is the same.
  • the control device 105 (10) indicates that the control device 105 exists in the control device manufacturer 10.
  • the control device 105 (20) indicates that the control device 105 (10) has been carried into the set maker 20.
  • the control device 105 (30) indicates that the control device 105 (10) is carried into the end user 30 via the set maker 20.
  • it is described as a control device 105.
  • the update FW 102 is protected by a method disclosed in Non-Patent Document 1 or a similar method. There are no particular restrictions on the protection method.
  • the end user 30 of FIG. 1 has an end user device 300 in which a development tool 301 provided by the control device manufacturer 10 is stored.
  • the control device 105 (20) is released in the form of being included in the final product developed by the set maker 20.
  • the set maker 20 is a maker that assembles a final product including a plurality of control devices by using a plurality of control devices manufactured by the control device maker 10.
  • the control device is a CPU unit or a communication unit.
  • the end user device 300 is connected to the control device 105 (30), and the end user 30 also uses the development tool 301 stored in the end user device 300 for the control device 105 (30) as in the case of the set manufacturer 20.
  • the end user 30 also recognizes the necessity of FW update by notification from the control device manufacturer 10 or by periodic check, and downloads the update FW 102 from the distribution server 100 via the end user device 300.
  • the downloaded update FW 102 is transmitted to the control device 105 (30) via the end user device 300.
  • the control device 105 (30) updates its own FW with the received update FW102.
  • FIG. 3 is a diagram illustrating a process in which the set maker 20 ships the final product including the control device 105 to the end user 30.
  • FIG. 4 is a diagram showing a rule file 205 in which project file 202 and FW update rules are described.
  • FIG. 5 shows the control device 105 and the project file 202 delivered from the set maker 20 to the end user 30.
  • the set maker 20 develops the program of the control device 105 (20) with the set maker device 200 in which the development tool 201 is stored. At that time, the development tool 201 generally stored in the set maker apparatus 200 has a management function for managing that the program of the control apparatus 105 (20) is for the control apparatus 105 (20).
  • One of the management functions is a project file 202 shown in FIGS.
  • a group of files such as programs, parameters, and data managed by the project file 202 is a set of files necessary for control of the control device 105 (20).
  • the project file 202 includes programs, parameters, or data as a file group, as shown in FIG.
  • the development tool execution unit 210 of the set maker apparatus 200 manages a project file 202 to manage a file group such as a program, a parameter, or data.
  • the update FW URL 203 in FIG. 4 is one of data managed by the project file 202.
  • the update FW URL 203 is a website location specifier published by the control device manufacturer 10.
  • the update FW 102 of the control device 105 can be downloaded from this website.
  • Rule file The URL 204 is one of data managed by the project file 202.
  • the rule file URL 204 is a location specifier of a website published by the set maker 20. From this website, a rule file 205 in which FW update rules are defined can be downloaded for the FW update of the final product.
  • the FW update rule is a condition for FW update. Examples of update conditions include FW version 205-1, attribute 205-2 related to the updated function, vulnerability attribute 205-3 resolved by update, and the like.
  • the FW version 205-1 is also attribute information, and the attribute information including the FW version 205-1 is described in the update FW102.
  • the rule file 205 is also updated. This update will be described later.
  • the development tool execution unit 210 of the set maker apparatus 200 installs the rule file 205-1 to the control apparatus 105 (20).
  • the rule file 205-1 means the installed rule file 205.
  • the rule file 205 is described as the rule file 205-2. .
  • a digital signature 207 generated using the secret key of the set maker 20 is added to the rule file 205-1.
  • the set maker 20 installs the public key 206 for verifying the digital signature 207 added to the rule file 205-1 to the control device 105 (20).
  • the digital signature 207 and the public key 206 are verification information 2060.
  • the project file 202 is released from the set maker 20 together with the final product to the end user 30.
  • FIG. 6 is a diagram illustrating a case where the end user 30 updates the FW of the control device 105 (30).
  • FIG. 7 is a block diagram illustrating a configuration of the control device 105. The FW is stored in the program storage unit 1051.
  • FIG. 8 is a sequence diagram showing operations of the end user device 300 and the control device 105 (30) in the end user 30.
  • the control device 105 that is the program update device 11 includes a program storage unit 1051, a rule storage unit 1052, an update information reception unit 1053, a determination unit 1054, an update unit 1055, a rule information reception unit 1056, a request transmission unit 1057, and a verification unit 1058.
  • the program storage unit 1051 stores firmware that is a program.
  • the rule storage unit 1052 stores a rule file 205 that is rule information 2051 in which firmware update rules are defined.
  • the update information receiving unit 1053 receives the update FW 102 that is update information 1020 for updating the firmware.
  • the determination unit 1054 determines whether the update information 1020 matches the rule information 2051.
  • the update unit 1055 updates the firmware stored in the program storage unit 1051 using the update information 1020 when it is determined that the determination unit 1054 is suitable.
  • the update unit 1055 updates rule information.
  • the rule information receiving unit 1056 receives the new version rule information 2052 in which the rule information 2051 is updated.
  • the request transmission unit 1057 transmits a transmission request 51 for requesting transmission of the update information 1020.
  • the update information receiving unit 1053 receives the update information 1020 as a response to the transmission request 51, and the determination unit 1054 matches the new version rule information 2052 with the update information 1020 received as a response by the update information receiving unit 1053. Determine whether to do.
  • the rule information 2051 stored in the rule storage unit 1052 has verification information 2060.
  • the verification unit 1058 verifies whether or not the new version rule information 2052 is valid based on the verification information 2060 and the new version rule information 2052 received by the rule information reception unit 1056, and determines that the new version rule information 2052 is not valid as a result of the verification.
  • the new version rule information 2052 is discarded.
  • the rule information receiving unit 1056 receives the new version rule information 2052 from the download device 3000 that downloads the new version rule information 2052 uploaded to the website 103 from the website 103.
  • the download device 3000 is the end user device 300.
  • the end user 30 recognizes the necessity of FW update by notification from the control device manufacturer 10 or the set manufacturer 20 or by periodic confirmation.
  • the end user 30 performs maintenance of the control device 105 (30) included in the final product using the end user device 300 in which the development tool 301 and the project file 202 are stored.
  • the development tool execution unit 310 of the end user device 300 refers to the rule file URL 204 defined in the project file 202 using the communication unit 320, and checks whether there is a new version of the rule file 205-1.
  • the version of the rule file 205 is managed by the project file 202 as shown in FIG.
  • Step S102> When there is a new version, the development tool execution unit 310 downloads the rule file 205-2 from the website page.
  • Step S103> When the development tool execution unit 310 downloads a new version of the rule file 205-2, the development tool execution unit 310 transmits the rule file 205-2 to the control device 105 (30) via the communication unit 320. Note that the end user device 300 stores the rule file 205 in the storage unit 330. The rule file 205 transmitted from the development tool execution unit 310 to the control device 105 is a copy of the rule file 205 in the storage unit 330.
  • the rule information receiving unit 1056 of the control device 105 (30) receives the rule file 205-2 which is the new version rule information 2052.
  • the verification unit 1058 verifies the validity of the digital signature 207 of the rule file 205-1 using the public key 206 installed in advance by the set maker 20.
  • the rule file 205-1 is stored in the rule storage unit 1052.
  • the verification unit 1058 executes a normal digital signature 207 verification method. Specifically, the verification unit 1058 decrypts the digital signature 207 with the public key 206 and generates a decrypted value h1.
  • Step S105> In the case of verification failure, the verification unit 1058 discards the received rule file 205-2 and notifies the end user device 300 of an error.
  • Step S106> When the verification by the verification unit 1058 is successful, the update unit 1055 updates the rule file 250-1 held by the update unit 1055 with the received update rule file 205-2. Further, the request transmission unit 1057 transmits a notification of successful update to the end user device 300.
  • the notification of successful update is a transmission request 51 for requesting transmission of the update FW 102.
  • the communication unit 320 of the end user device 300 receives the transmission request 51.
  • the development tool execution unit 310 accesses the update FW URL 203 via the communication unit 320 and checks whether there is an update FW 102 that conforms to the rule indicated by the rule file 205-2.
  • the entity of the update FW URL 203 is the distribution server 100 as shown in FIG.
  • the development tool execution unit 310 downloads the update FW 102 that matches the rule from the update FW URL 203 (S108; YES).
  • the development tool execution unit 310 outputs to the display device and notifies that the firmware update is not required ( S108; NO).
  • the development tool execution unit 310 transmits the downloaded update FW 102 to the control device 105 (30) via the communication unit 320.
  • the update information receiving unit 1053 receives the update FW 102 that is the update information 1020.
  • the determination unit 1054 confirms whether or not the received update FW 102 conforms to the rule indicated by the rule file 205-2. At this time, as described above, it is assumed that the update FW 102 is protected from tampering by the method disclosed in Non-Patent Document 1 or a similar method, and the protection method and method are not particularly limited.
  • Step S111> When the rule is met (YES in S110), the update unit 1055 is the update FW 102 for which the match is confirmed (YES in S110) and the validity is confirmed (YES in S104), and the controller 105 (30 ) FW is updated. After completing the update, the update unit 1055 transmits a normal end to the end user device 300.
  • step S110> If the rule does not match (NO in S110), the update unit 1055 does not update the FW and transmits an update impossible message to the end user device 300.
  • rule file 205 of the first embodiment is not a single one, and may be divided for each end user 30 or for each version of the final product.
  • FIG. 9 shows a state in which the control device 105 (30) has a plurality of units A to E, and the plurality of units A to E use the firmware A to E, respectively.
  • the control device 105 (30) is a composite unit device including a plurality of units.
  • the update FW group 401 includes update firmware A to E.
  • the firmware A and B for update are referred to as update FW (A), update FW (B), and the like.
  • the update FW (A) corresponds to the update FW 102 described in FIG.
  • the update FW (B) to the update FW (E) correspond to the update FW 102, respectively.
  • FIG. 10 is a block diagram showing a configuration of unit A serving as a master unit.
  • Unit A has the same configuration as the control device 105 of FIG.
  • the program storage units 1051 to 1058 in FIG. 7 correspond to the program storage units 1051M to 1058M in FIG. 10 and have the same functions.
  • FIG. 11 shows a rule file 205A of unit A.
  • the rule file 205A is stored in the rule storage unit 1052M.
  • the operation of the unit A shown in FIG. 10 is the same as that of the control device 105 (30) of FIG. 8, and the control device 105 (30) of FIG. However, the contents of the rule file 205A are different.
  • the control device 105 (30) shown in FIG. 9 includes five units, units A, B, C, D, and E, with which the FW may be updated. This is an example, and the configuration is not limited. Here, it is assumed that the unit A plays the role of a master in the control device 105 (30). Hereinafter, unit A is referred to as master unit A. If the control device 105 (30) is a PLC, the master unit A is a CPU unit, and the slave units B, C, D, and E are communication units other than the CPU unit.
  • Each update FW group 401 is downloaded by the method shown in FIG. 8 (S109 in FIG. 8).
  • the update FW group 401 passes through the route 41 in FIG. That is, the update FW group 401 always passes through the master unit A, and the FW of each unit A to E is updated.
  • the master unit A confirms whether the update FW (A), FW (B), and the like match the rules of the rule file 205A. That is, when updating the update FW group 401, the master unit A plays the role of the control device 105 (30) in FIG. 8, and in the case of the path 41, the control device 105 (30) in FIG. Replaced with master unit A.
  • the tampering with the update FW (A) or the like is protected by the method disclosed in Non-Patent Document 1 or a similar method.
  • the slave units B to E do not permit the FW update for the path 42 in FIG. 9, that is, the direct slave unit.
  • the master unit A is always used.
  • the slave unit includes a control unit, a communication unit, and a storage unit that stores the FW (not shown).
  • the control unit rejects the request.
  • the rule storage unit 1052M of the master unit A stores the rule file 205A of FIG.
  • the rule file 205A has whether or not the FW of each unit can be updated as update availability information 205A-0.
  • the determination unit 1054M of the master unit A includes the update FW (A) of the master unit A, the update FW (B) to FW (E) of the slave units B to E, and the set maker 20 as the rule file 205A. It is checked whether the FW conforms to the rule shown. This check corresponds to S110 in FIG. 8, and in S110, the determination unit 1054M of the master unit A refers to the rule indicated by the rule file 205A and determines whether the FW to be updated conforms to the rule.
  • the determination unit 1054M refers to the update availability information 205A-0 and determines that the conformity is possible because the update is possible.
  • the determination unit 1054M determines that it does not conform to the rule because the update is not possible with the update availability information 205A-0.
  • the operation is the same as that of the control device 105 (30) in FIG. 8 except that the determination unit 1054M determines whether the update FW group 401 conforms to the rule.
  • the update unit 1055M updates the FW.
  • the control device 105 includes units A to E.
  • FIG. 12 shows the operation in the case where the combination of FW is changed unintentionally by parts replacement. Note that FIG. 12 is an example, and the configuration and attributes are not limited.
  • FIG. 13 shows a rule file 205A held by the master unit A. In the FW version 205A-1 of the rule file 205A, the upper limit of the FW version allowed for each unit is defined. In FW version 205A-1, the FW can be updated up to version 1.2.
  • FIG. 14 shows a configuration in which the master unit A further includes a version acquisition unit 1059M that acquires the FW version from each unit.
  • FIG. 15 shows an operation when the version acquisition unit 1059M acquires a version from the FW.
  • the unit B of the control device 105 (30) has a hardware failure and is replaced with the unit B-1.
  • the FW version of the unit B is 1.1, which conforms to the FW version 205A-1 of the rule file 205A installed in the unit A.
  • FW version 205A-1 FW can be updated up to version 1.2, but update to the latest 1.3 is not permitted. Therefore, if the latest version 1.3 FW is installed in the unit B-1 to be replaced, it does not conform to the FW version 205A-1.
  • the version acquisition unit 1059M of the master unit A acquires the FW version of each of the units B to E from each FW in addition to its own FW version when the control device 105 (30) is activated.
  • the determination unit 1054M confirms the consistency between the rules described in the rule file 205A and the acquired version.
  • Step S203 When the latest version 1.3 FW is installed in the unit B-1, the determination unit 1054M confirms that the unit B-1 has the FW version 205A-1 of the rule file 205A by checking the consistency with the rule. Discover that the rules are not met. In this case, the request transmission unit 1057M transmits a non-conformance signal 52 indicating unsuitability to the end user device 300.
  • This nonconforming signal 52 is a transmission request 51.
  • the transmission request 51 includes information on the update FW that is desired to be transmitted.
  • the notification of non-conformity is not limited to the end user device 300, but a display function unit (not shown) of the master unit A having a function of receiving and displaying the notification, or an HMI (Human Machine Interface) via the network. , May be transmitted to other terminal apparatuses such as SCADA (Supervision Control And Data Acquisition).
  • Steps S204 and S205> When the end user apparatus 300 receives the transmission request 51, the development tool execution unit 310 accesses the update FW URL 203, and the distribution server 100 sends an update FW (B) (version 1.2) that conforms to the rules of the rule file 205A. It is acquired and transmitted to the control device 105 (S205).
  • update FW (B) (version 1.2) that conforms to the rules of the rule file 205A. It is acquired and transmitted to the control device 105 (S205).
  • the update unit 1055M updates the FW of the unit B-1 using the update FW (B).
  • the firmware of the unit B-1 is updated to “1.2” by the end user device 300 and the master unit A, and the process is completed.
  • the control device 105 stores a rule file 205 provided by the set maker 20. Therefore, the set maker 20 that manufactures the final product can control and limit the use of the end user of the FW update function of the control device 105.
  • the rule file 205 can be updated. Therefore, the set maker 20 can control and restrict the end user's use of the FW update function of the industrial control device in more detail and flexibly.
  • the rule file 205 can be downloaded from the website, but the set maker 20 can upload the new version rule file updated by the set maker apparatus 200 to the website. Therefore, the rules can be easily changed by the set maker 20, and the changed rules can be easily provided to the end user 30.
  • the master unit determination unit 1054M checks the slave update FW using the rule file 205A, so that the combination of FWs can be managed, and an inappropriate FW update is performed by the end user 30. Can be controlled. That is, the set manufacturer 20 can manage and control the update of the combination of FWs by defining the update conditions of the individual update FWs in the rule file 205A shown in FIG. Also, only the master unit determination unit 1054M of the master unit A determines whether or not the FW can be updated, and the slave unit itself does not update the FW. Therefore, the combination of FW can be integrated and managed.
  • the version acquisition unit 1059M acquires the version of the FW, and the determination unit 1054M determines whether the acquired version matches the rule file 205A. Therefore, even when the unit is replaced by the end user 30, the combination of FW can be managed. In addition, when the version does not match, a compatible version update FW is acquired, so even if the version of the FW does not match, it can be quickly switched to the version compatible FW.
  • FIG. 16 is a hardware configuration example when the distribution server 100, the set maker device 200, the end user device 300, the control device 105, the master unit A, and the like are realized by a computer. This will be described with reference to FIG.
  • the control device 105 which is a computer, will be described as an example. The description of the control device 105 also applies to the distribution server 100, the set maker device 200, and the end user device 300.
  • the control device 105 includes hardware such as a processor 901, an auxiliary storage device 902, a memory 903, a communication device 904, an input interface 905, and a display interface 906.
  • the processor 901 is connected to other hardware via the signal line 910, and controls these other hardware.
  • the input interface 905 is connected to the input device 907.
  • the display interface 906 is connected to the display 908.
  • the processor 901 is an IC (Integrated Circuit) that performs processing.
  • the processor 901 is, for example, a CPU (Central Processing Unit), a DSP (Digital Signal Processor), or a GPU (Graphics Processing Unit).
  • the auxiliary storage device 902 is, for example, a ROM (Read Only Memory), a flash memory, or an HDD (Hard Disk Drive).
  • the memory 903 is, for example, a RAM (Random Access Memory).
  • the communication device 904 includes a receiver 9041 that receives data and a transmitter 9042 that transmits data.
  • the communication device 904 is, for example, a communication chip or a NIC (Network Interface Card).
  • the input interface 905 is a port to which the cable 911 of the input device 907 is connected.
  • the input interface 905 is, for example, a USB (Universal Serial Bus) terminal.
  • the display interface 906 is a port to which the cable 912 of the display 908 is connected.
  • the display interface 906 is, for example, a USB terminal or an HDMI (registered trademark) (High Definition Multimedia interface) terminal.
  • the input device 907 is, for example, a mouse, a keyboard, or a touch panel.
  • the display 908 is, for example, an LCD (Liquid Crystal Display).
  • the auxiliary storage device 902 stores programs that realize the functions of the program storage unit 1051 to the verification unit 1058 shown in FIG.
  • programs that realize the functions of the program storage unit 1051M to the version acquisition unit 1059M are stored.
  • the program storage unit 1051 to verification unit 1058 and the program storage unit 1051M to version acquisition unit 1059M are collectively referred to as “unit”.
  • This program is loaded into the memory 903, read into the processor 901, and executed by the processor 901. More specifically, among the “units”, the storage unit is realized by a program, an auxiliary storage device 902, a memory 903, and the like. In addition, among the “units”, the transmission unit and the reception unit are realized by a program, the communication device 904, and the like.
  • the auxiliary storage device 902 also stores an OS (Operating System). Then, at least a part of the OS is loaded into the memory 903, and the processor 901 executes a program that realizes the function of “unit” while executing the OS.
  • the control device 105 may include a plurality of processors 901. A plurality of processors 901 may execute a program for realizing the function of “unit” in cooperation with each other.
  • information, data, signal values, and variable values indicating the processing results of “unit” are stored in the memory 903, the auxiliary storage device 902, or a register or cache memory in the processor 901.
  • Parts may be provided by “Circuitry”. Further, “part” may be read as “circuit”, “process”, “procedure”, or “processing”. “Circuit” and “Circuitry” include not only the processor 901 but also other types of processing circuits such as logic IC, GA (Gate Array), ASIC (Application Specific Integrated Circuit), or FPGA (Field-Programmable Gate Array). It is a concept to include.
  • the operations of the “unit” of the control device 105 and the master unit of the first embodiment can also be grasped as an update determination program or a program update method.
  • M master unit 1 FW update system, 10 control device manufacturer, 11 program update device, 20 set manufacturer, 30 end user, 40 communication network, 41, 42 route, 51 transmission request, 52 nonconforming signal, 100 distribution server, 102 update FW, 1020 update information, 103 website, 110 control unit, 120 update information generation unit, 130 communication unit, 140 storage unit, 105, 105 (10), 105 (20), 105 (30) control device, 1050 unit Device, 1051, 1051M program storage unit, 1052, 1052M rule storage unit, 1053, 1053M update information reception unit, 1054, 1054M determination unit, 1055, 1055M update unit, 1056, 1056M rule information Communication unit, 1057, 1057M request transmission unit, 1058, 1058M verification unit, 1059M version acquisition unit, 200 set maker device, 201 development tool, 202 project file, 203 update FW URL, 204 rule file URL, 205 rule file, 2051 rule Information, 2052 new version rule information, 205-1 FW version, 205-2, 205-3 attributes, 206

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)
PCT/JP2015/062391 2015-04-23 2015-04-23 プログラム更新装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法 WO2016170641A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/JP2015/062391 WO2016170641A1 (ja) 2015-04-23 2015-04-23 プログラム更新装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法
JP2016514185A JP5951162B1 (ja) 2015-04-23 2015-04-23 制御装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法
TW104132792A TWI599906B (zh) 2015-04-23 2015-10-06 Program update device, complex cell device, update decision program product and program update method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/062391 WO2016170641A1 (ja) 2015-04-23 2015-04-23 プログラム更新装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法

Publications (1)

Publication Number Publication Date
WO2016170641A1 true WO2016170641A1 (ja) 2016-10-27

Family

ID=56375125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/062391 WO2016170641A1 (ja) 2015-04-23 2015-04-23 プログラム更新装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法

Country Status (3)

Country Link
JP (1) JP5951162B1 (zh)
TW (1) TWI599906B (zh)
WO (1) WO2016170641A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019053345A (ja) * 2017-09-12 2019-04-04 アセンテック株式会社 端末装置、シンクライアント変換方法およびシンクライアント変換プログラム
CN111078249A (zh) * 2019-11-08 2020-04-28 泰康保险集团股份有限公司 软件更新方法、系统、设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018055465A (ja) * 2016-09-29 2018-04-05 セイコーエプソン株式会社 印刷装置、及び印刷装置の制御方法
TWI761917B (zh) * 2020-08-19 2022-04-21 鴻海精密工業股份有限公司 程式調試方法、裝置及可讀存儲介質

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005202503A (ja) * 2004-01-13 2005-07-28 Hitachi Ltd 車載情報装置、車載機器管理システム、車両の制御機器のプログラムのバージョンアップ情報の配信方法、車両の制御機器のプログラムのバージョンアップ方法及び車両の制御機器のプログラムのバージョンアップシステム
JP2008546318A (ja) * 2005-06-03 2008-12-18 グッド テクノロジー インコーポレイテッド 無線デバイスを監視及び維持するためのシステム及び方法
JP2013232077A (ja) * 2012-04-27 2013-11-14 Samsung Techwin Co Ltd 半導体製造装置の制御プログラムの更新システム

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009193218A (ja) * 2008-02-13 2009-08-27 Fuji Xerox Co Ltd ファームウェア更新装置およびファームウェア更新システム
US8364598B2 (en) * 2009-10-13 2013-01-29 Microsoft Corporation Use of software update policies
JP5392203B2 (ja) * 2010-08-19 2014-01-22 株式会社リコー 情報処理装置、情報処理システム、インストール支援方法、及びインストール支援プログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005202503A (ja) * 2004-01-13 2005-07-28 Hitachi Ltd 車載情報装置、車載機器管理システム、車両の制御機器のプログラムのバージョンアップ情報の配信方法、車両の制御機器のプログラムのバージョンアップ方法及び車両の制御機器のプログラムのバージョンアップシステム
JP2008546318A (ja) * 2005-06-03 2008-12-18 グッド テクノロジー インコーポレイテッド 無線デバイスを監視及び維持するためのシステム及び方法
JP2013232077A (ja) * 2012-04-27 2013-11-14 Samsung Techwin Co Ltd 半導体製造装置の制御プログラムの更新システム

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019053345A (ja) * 2017-09-12 2019-04-04 アセンテック株式会社 端末装置、シンクライアント変換方法およびシンクライアント変換プログラム
CN111078249A (zh) * 2019-11-08 2020-04-28 泰康保险集团股份有限公司 软件更新方法、系统、设备及存储介质

Also Published As

Publication number Publication date
TWI599906B (zh) 2017-09-21
TW201640407A (zh) 2016-11-16
JPWO2016170641A1 (ja) 2017-04-27
JP5951162B1 (ja) 2016-07-13

Similar Documents

Publication Publication Date Title
US11533187B2 (en) Device birth certificate
US11824847B2 (en) Device programming with system generation
TWI741041B (zh) 用於可程式化設備的統一程式設計環境
TWI744373B (zh) 使用安全演算法嵌入基礎性的信任根
US20230047575A1 (en) Managing privileges of different entities for an integrated circuit
US9686278B1 (en) Method and system for configuring computing devices
US10587451B2 (en) Device programming with system generation
KR20200098561A (ko) 연결된 엔드포인트 장치의 가입 및 등록을 위한 장치 식별 시스템 및 방법, 그리고 블록 체인 서비스
WO2018027190A1 (en) Counterfeit prevention
JP5951162B1 (ja) 制御装置、複合ユニット装置、更新判定プログラム及びプログラム更新方法
US20180131520A1 (en) Method and arrangement for securely interchanging configuration data for an apparatus
EP3772008A1 (en) Device programming with system generation
US20210357198A1 (en) Controlled scope of authentication key for software update
JP5472708B2 (ja) 検証装置とこれを用いたフィールド機器ソフトウェア更新システム

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016514185

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15889880

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15889880

Country of ref document: EP

Kind code of ref document: A1