JP2010218334A - Program dynamic updating system, management server, incorporated equipment, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To dynamically update a program even in incorporated equipment whose loaded memory capacity is small. <P>SOLUTION: A management server is configured to collect update information corresponding to a pre-update program operating in incorporated equipment, and to generate an update information file by solving an address on a memory for dynamically applying the update information to the incorporated equipment. On the other hand, the incorporated equipment is configured to dynamically update an incorporated program based on the update information file. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technique for dynamically updating a program without stopping the operation of the program running on the embedded device. The present invention also relates to a management server to which the program dynamic update technology is applied, an embedded device, and a corresponding program.

  In recent years, with the increase in the number of embedded devices such as information home appliances and higher functionality, programs installed in the embedded devices have been updated after product shipment. Here, updating refers to correcting a problem in a program, adding a new function, or the like. This update is generally performed by updating the firmware of the embedded device. However, the update method requires an operation of replacing the contents of a flash ROM (Read Only Memory) in which the firmware is written with the updated firmware. The embedded device cannot be used during the firmware update, and it is necessary to restart the embedded device after the update. In order to avoid such a situation, a method of dynamically updating the program while the program is activated may be used instead of the method of replacing the firmware. For example, a program update technique (see Patent Document 1) in an online system or the like that requires no service interruption is disclosed.

Japanese Patent Laid-Open No. 10-247143

  However, it is difficult to practically apply the method of Patent Document 1 to embedded devices such as information home appliances with a small amount of memory. In the method of Patent Document 1, it is necessary to read a new partial program into the memory every time a program operating in the system is updated. When the program is read into the memory, relocation and address resolution are performed. This process consumes memory. Therefore, in the above method, if the program is updated accumulatively, the memory consumption increases, the memory usage allowable in the embedded device is exceeded, and the operation of another program operating in the embedded device is affected. .

  Therefore, in the present invention, a method for creating an update information file that resolves an address when dynamically applying an update program to an embedded program that operates on the embedded device is created in the management server, and writing the updated information file to the embedded device. suggest. In the update information file, it is desirable that the post-update function, the address of the pre-update function in the memory, and the relative address in the update information file of the post-update function are written. In the update information file, an updated function, an address on the memory in which the function of the embedded program referred to from the updated function is described, and a relative address in the update information file to which the address is written are written. It is desirable that The update information file also includes a plurality of updated functions that have a reference relationship, a relative address in the update information file that describes the updated function that is the reference destination, and a relative address in the update information file to which the address is written. It is desirable that the address is written.

  On the other hand, the embedded device proposes a method of shifting the portion indicated by the relative address in the update information file by the address (real address) on the memory where the reference address of the relative address is written.

  According to the present invention, it is possible to dynamically update a program even in an embedded device having a small installed memory capacity such as an information home appliance.

It is a figure explaining the whole program dynamic update system composition concerning a form example. It is a figure which shows the example of a form of a management server. It is a figure which shows the example of a form of an embedded apparatus. It is a figure explaining the dynamic update operation | movement of a function. It is a figure explaining the relationship between the function before and behind an update, and the relationship between the functions after an update. It is a figure which shows the structural example of an update information file. It is a flowchart which shows the example of a preparation procedure of the update information file performed by the management server side. It is a flowchart which shows the example of an update procedure of the update program performed by the embedded apparatus side.

  Hereinafter, an example of a program dynamic update system to which the present invention is applied will be described with reference to the drawings.

-Embodiment (1-1) System Configuration FIG. 1 shows a system configuration diagram according to an embodiment. The program dynamic update system according to the embodiment assumes a case where one management server 101 and a plurality of embedded devices 103 (103A and 103B) are connected to each other via the network 102.

  The embedded device 103 corresponds to an information home appliance such as a television or a home gateway. Although FIG. 1 shows a case where there are two embedded devices 103 connected to the network 102, the number of embedded devices 103 may be arbitrary. Further, the number of management servers 101 may be arbitrary as with the embedded device 103. Furthermore, the network 102 may be arbitrary as long as the management server 101 and the embedded device 103 can be connected to each other. Therefore, the network 102 may be configured by one or both of wired connection and wireless connection. The network 102 corresponds to, for example, the Internet or a broadcast wave.

(1-2) Configuration of Management Server FIG. 2 shows a configuration example of the management server 101. The management server 101 is a computer system used by an administrator of the program dynamic update system. The management server 101 includes an input unit 201, a display unit 202, a data processing unit 203, a storage unit 205, and a network connection unit 209.

  The input unit 201 is a device used by an administrator to give an instruction to the management server 101. In the case of this embodiment, the administrator is used to give an instruction to create the update information file 208 used by the embedded device 103. For the input unit 201, for example, a keyboard or a mouse is used. The display unit 202 is an output device that displays input information to the management server 101 and various data as processing results. For the display unit 202, for example, a CRT display or a liquid crystal display is used.

  The data processing unit 203 includes a processing device and a memory. The processing device interprets the contents of the read program and executes data processing. The processing device is composed of, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), and the like. The memory is a storage device that temporarily stores processing data used in the processing device. The memory is composed of, for example, a RAM (Random Access Memory). The memory stores a program that supports creation of an update information file to be described later. In this embodiment, this program is referred to as an update information file generation unit 204.

  The update information file creation unit 204 creates an update information file 208 including information for updating the pre-update program 306 operating on the embedded device 103 side. In the drawing, the update information file 208 in FIG. 2, the update information file 307 in FIG. 3, and the update information file 601 in FIG. 6 all have the same contents, and different reference numerals are used for convenience of the drawing and description. Just doing.

  The storage unit 205 is a device that stores or reads various data. The storage unit 205 includes, for example, an HDD (hard disk drive), an optical storage device, or the like. In the case of this embodiment, the storage unit 205 stores, for example, a pre-update program 206, a post-update program 207, an update information file 208, and the like. The pre-update program 206 is a program currently operating on the embedded device. In the specification, this program is referred to as a pre-update program. The updated program 207 is a program that is newly operated by the embedded device. In the specification, this program is referred to as an updated program. The update information file 208 is a data file composed of a program necessary for dynamically changing the pre-update program to the post-update program, its address information, and the like.

  The network connection unit 209 is a communication device for connecting the management server 101 to the network 102. For the network connection unit 209, for example, a NIC (network interface card) is used. When the update information file 208 is transmitted by being superimposed on a broadcast wave, a broadcast wave transmission device is used for the network connection unit 209.

(1-3) Configuration of Embedded Device FIG. 3 shows a configuration example of the embedded device 103. The embedded device 103 in the program dynamic update system is a device on which the program to be updated operates. The embedded device 103 includes, for example, an input unit 301, a display unit 302, a data processing unit 303, a storage unit 305, and a network connection unit 308. However, the configuration of the embedded device 103 illustrated in FIG. 3 is an example, and is not limited to this configuration.

  The input unit 301 is a device used by a user to give an instruction to the embedded device 103. For the input unit 301, for example, a keyboard or a remote controller is used. The display unit 302 is an output device that displays input information for the embedded device 103 and various data as processing results. As the display unit 301, for example, a liquid crystal display is used.

  The data processing unit 303 includes a processing device and a memory. The processing device interprets the contents of the read program and executes data processing. The processing device is composed of, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), and the like. The memory is a storage device that temporarily stores processing data used in the processing device. The memory is composed of, for example, a RAM (Random Access Memory). The memory stores a program for dynamically applying the update information file 307 to the pre-update program 306. In this embodiment, this program is referred to as an update unit 304.

  The storage unit 305 is a device that stores or reads various data. The storage unit 305 is configured by, for example, a flash ROM, an HDD (hard disk drive), or the like. In the case of this example, the storage unit 305 stores, for example, a pre-update program 306, an update information file 307, and the like.

  The network connection unit 308 is a communication device for connecting the embedded device 103 to the network 102. The network connection unit 308 uses, for example, a NIC (network interface card). When the update information file 307 is superimposed on the broadcast wave, a broadcast wave receiver is used for the network connection unit 308.

(1-4) Dynamic Update Operation of Program FIG. 4 shows a method for updating a function in the program without stopping the operation of the program. The pre-update function 401 is a function in the program and includes a defect or the like. The post-update function 404 is a function in which a defect or the like of the pre-update function 401 is corrected. First, the updated function 404 is read into the memory. Next, the control transfer destination 403 is arranged on the memory. In the control transfer destination 403, the start address on the memory where the post-update function 404 is arranged is described. Finally, the control transfer instruction 402 is described at the top address on the memory where the pre-update function 401 is located. The control transfer instruction 402 plays a role of referring to the start address described in the control transfer destination 403 and transferring control to the start address of the description destination. When the pre-update function 401 is called by the above operation, the control is transferred to the post-update function 404 by the control transfer instruction 402. Accordingly, it is possible to replace the pre-update function 401 including the defect with the post-update function 404 that corrects the defect.

(1-5) Update Relationship Between Functions Described in Update Information File FIG. 5 shows an example of an update relationship between functions described in the update information file. Three types of update relationships are described in the update information file. One is a description for changing the pre-update function of the pre-update program to the post-update function. One is a description that refers to a function provided by the OS (operating system) from the function of the updated program. One is a description that refers to another function in the updated program from a function in the updated program.

<a> Update from Pre-Update Function to Post-Update Function FIG. 5 shows the pre-update function A (501), the pre-update function B (504), and the pre-update function C (507). (510), updated function 2 (513), and updated function 3 (516) are shown in a dynamically updated state. As in the case of the description of FIG. 4, the control transfer instruction A (502) is written at the head of the pre-update function A (501). For example, the control transfer destination A (503) referred to by the control transfer instruction A (502) stores the start address of the updated function 1 (510) on the memory. Similarly, the control transfer instruction B (505) is written at the head of the pre-update function B (504). The control transfer destination B (506) referred to by the control transfer instruction B (505) stores the start address on the memory of the updated function 2 (513). Similarly, a control transfer instruction C (508) is written at the head of the pre-update function C (507). The control transfer destination C (509) referred to by the control transfer instruction C (508) stores the start address of the updated function 3 (516) on the memory.

<B> Reference of OS Function from Function of Updated Program FIG. 5 shows a state in which a function (521) provided by the OS is called from updated function 1 (510). This operation is executed based on the control transfer instruction 1 (511) described at the corresponding position of the updated function 1 (510). In the control transfer destination (512) referred to by the control transfer instruction 1 (511), the address on the memory of the function (521) provided by the OS is stored.

<C> Reference of Other Functions in Updated Program from Functions in Updated Program FIG. 5 shows a state in which updated function 3 (516) is called from updated function 2 (513). This operation is executed based on the control transfer instruction 2 (514) described at the corresponding position of the updated function 2 (513). The control transfer destination 2 (515) referred to by the control transfer instruction 2 (514) stores the address on the memory of the updated function 3 (516).

(1-6) Update Information File FIG. 6 shows a configuration example of the update information file 601. The update information file 601 is used to dynamically update the embedded device program. The update information file 601 includes an updated function table 602, a control transfer table 603, and a cross reference table 604. Hereinafter, each element constituting the update information file 601 will be described.

  In the following description, the offset is defined as a displacement (relative address) from the head position of the update information file 601. In the case of this example, the post-update function 1 (FIG. 6) is arranged at the head of the update information file 601. Therefore, the offset of the post-update function 1 (FIG. 6) is given by “0”. That is, the offset can also be said to be a displacement from the head position of the post-update function 1 (FIG. 6).

  In the case of FIG. 5, the length of the arrow 517 (the unit of length is, for example, a byte) corresponds to the offset of the updated function 2 (513) with respect to the updated function 1 (510). Similarly, the length of the arrow 520 corresponds to the offset of the updated function 3 (516) with respect to the updated function 1 (510).

  The post-update function table 602 is composed of N post-update functions (1 to N). Here, the post-update function (1 to N) is a function having a difference in comparison between the pre-update program 306 and the post-update program 307, or a set of functions existing only in the post-update program 307. FIG. 6 shows that there are N of these functions in total. In the example of FIG. 5, three of the post-update functions 1 to 3 (FIG. 5) correspond, and N is 3.

  The control transfer table 603 includes M offset J (1 to M) and address J (1 to M) pairs. The control transfer table 603 describes (a) an address pair necessary for updating from the pre-update function to the post-update function, and (b) an address pair necessary for referring to the OS function from the function of the post-update program. Is done. Therefore, the offset of the control transfer table 603 does not include the offset used in the cross-reference table 604 described later.

  In the example of FIG. 5, the offset J of the control transfer table 603 is, for example, the displacement (518) in the update information file described in the control transfer destination 1 (512) or the update information file described in the control transfer destination 2 (515). The displacement (519) is given. The address J of the control transfer table 603 gives, for example, an address on the memory of the pre-update function (A to C) or an address (absolute address) on the memory of the function (521) provided by the OS. In this respect, the offset and the address are different.

  The cross-reference table 604 is composed of a pair of L offsets FR (1 to L) and offsets TO (1 to L). In the cross-reference table 604, address pairs necessary for calling between functions of the updated program are described. In the case of the example of FIG. 5, it is used to call the updated function 3 (516) from the updated function 2 (513). The offset FR gives the position of the control transfer destination 2 (515) referred to by the control transfer instruction 2 (514). The offset TO gives a displacement (520) that gives the head address of the post-update function 3 (516). This offset TO is described in the control transfer destination 2 (515).

(1-7) Procedure for Creating Update Information File Next, a procedure for creating the update information file 208 executed on the management server 101 side will be described. The update information file 208 is used in the update unit 304 of the embedded device 103.

  FIG. 7 shows an example of a processing procedure executed through the update information file generation unit 204 (FIG. 2).

  First, the update information file generation unit 204 performs a comparison operation between the pre-update program 206 designated and input by the operator and the post-update program 207 which is a correction program. By this process, a function that has been corrected between both programs or a function that exists only in the updated program is extracted (step S701). In the case of this embodiment, the total is N.

  Next, the update information file generation unit 204 sets the function extracted in step S701 as the post-update function (1 to N) (602) of the update information file 601, and creates the post-update function table 602 (step S702). In the case of FIG. 5, an updated function table 602 including three functions: an updated function 1 (510), an updated function 2 (513), and an updated function 3 (516) is created.

  Next, the update information file generation unit 204 starts the changed portion loop 1 with a counter i for the N updated functions (1 to N) extracted in step S701 (step S703).

  Next, if the i-th post-update function i is the post-update function 404 obtained by correcting the pre-update function 401 using the terms in FIG. 4, the update information file generation unit 204 stores the update information file 601 of the post-update function i. An offset Jk that is a displacement from the head is calculated. Here, k is a counter and counts up one by one from the initial value “1”. For example, when the update target program is a Linux (registered trademark) kernel, the pre-update function 401 is arranged in the memory of the embedded device 103. It can be examined using a map file or the like. System. In the map file, information is written in which a function name in the Linux (registered trademark) kernel is paired with an address on a memory where the function is arranged. The address of the pre-update function 401 acquired in this way is set as an address Jk.

  The update information file generation unit 204 adds the offset Jk and the address Jk obtained in this way as a pair to the control transfer table 603 (step S704). In the case of FIG. 5, the displacement of the offset 1 is 0 (zero), the address 1 is an address on the memory of the pre-update function A (501), the offset 2 is the displacement (517), and the address 2 is the pre-update function B (504). ), The offset 3 is the displacement (520), and the address 3 is the address of the pre-update function C (507) on the memory.

  Next, the update information file generation unit 204 determines whether the i-th updated function i calls an external function (step S705). Here, the external function is a function in the pre-update program that has not been determined to have a difference in step S701. In the example of FIG. 5, the function (521) provided by the OS called from the updated function 1 (510) corresponds to the external function.

  If step S705 is Yes, the update information file generation unit 204 performs address resolution (step S706). The address resolution is to determine at which address on the memory of the embedded device 103 when the i-th updated function i calls the external function. For example, when the update target program is a Linux (registered trademark) kernel, System. The address can be obtained from a map file. This address is Jk. The external function is called by referring to the control transfer destination by the control transfer instruction in the same way as a normal function call. The update information file generation unit 204 obtains the offset of the control transfer destination in the updated function i from the head of the update information file 601, sets this as the offset Jk, and sets the offset Jk and the address Jk in the control transfer table 603. Add. The update information file generation unit 204 performs the above processing operation on all the external functions in the post-update function i. In the case of FIG. 5, a pair of an address on the memory of the offset (518) and the function (521) in the OS is added to the control transfer table 603.

  When step S705 is No, the update information file generation unit 204 does nothing. Thereafter, the update information file generation unit 204 repeats the processing of steps S704 to S706 until the counter i exceeds N (step S707).

  Next, the update information file generation unit 204 starts the changed portion loop 2 with the counter set to j for the N updated functions (1 to N) extracted in step S701 (step S708).

  Next, the update information file generation unit 204 determines whether or not the j-th updated function j calls an internal function (step S709). Here, the internal function is a function in the pre-update program that is determined to have a difference in step S701. In the case of FIG. 5, the call of the internal function corresponds to the call of the updated function 3 (516) by the control transfer instruction 2 (514) in the updated function 2 (513).

  When step S709 is Yes, the update information file generation unit 204 creates a cross reference table (step S710). When the j-th updated function j calls an internal function, the update information file generation unit 204 determines the position of the updated function (1 to N) to be read (that is, the displacement from the top of the update information file 501). The offset is TOm. Here, m is a counter and is counted up one by one from the initial value “1”. Similarly, the update information file generation unit 204 sets the position described in the control transfer destination referred to by the control transfer instruction that calls the internal function (that is, the displacement from the top of the update information file 501) as the offset FRm. The update information file generation unit 204 adds the offset FRm and the offset TOm to the cross reference table 504 as a pair. The update information file generation unit 204 executes the above processing operation for all internal functions in the updated function j. In the case of FIG. 5, the displacement (519) is added to the cross-reference table 504 as the offset FR and the displacement (520) is added as the offset TO.

  If step S709 is No, the update information file generation unit 204 does nothing. Thereafter, the update information file generation unit 204 repeats the processes of steps S709 to S710 until the counter j exceeds N (step S711).

  The update information file 601 is created by executing the above processing operations. As described above, the address resolution is basically executed by the management server 101.

(1-8) Update Operation in Embedded Device Next, an update operation of the pre-update program 306 executed by the update unit 304 of the embedded device 103 using the update information file 307 will be described.

FIG. 8 shows a processing procedure example executed through the update information file 307.
First, the update unit 304 reads the update information file 307 into the storage unit 305 of the embedded device 103 (step S801). Hereinafter, the address on the memory where the update information file 307 is arranged is denoted as ADDR.

  Next, the update unit 304 extracts the values of the offset FRa and the offset TOa from the cross reference table 604, and adds ADDR to each of the offset FRa and the offset TOa (step S802). A represents 1 to L. By this addition processing, the update unit 304 converts the relative address in the update information file 307 given as an offset into a real address on the memory. Thereafter, the update unit 304 writes a control transfer destination having the description content of the address obtained by adding ADDR to the offset TOa to the address on the memory obtained by adding ADDR to the offset FRa.

  Finally, the update unit 304 extracts the value of the offset Jb from the control transfer table 603 and adds ADDR to this value (step S803). By this addition processing, the update unit 304 converts the relative address in the update information file 307 given as an offset into a real address on the memory. Thereafter, the updating unit 304 writes the control transfer destination having the address Jb as the description content to the address on the memory paired with the offset Jb (in the case of FIG. 5, 503, 506, and 509), and the start address of the corresponding function Write a control transfer command to. Note that b represents 1 to M.

  Here, when writing the control transfer instruction, the update unit 304 appropriately performs processing for preventing the pre-update program 306 from performing an unexpected operation based on the hardware specifications of the embedded device 103. .

  With the above update procedure, it is possible to shift the pre-update program 306 to a state in which processing equivalent to that of the post-update program 207 is performed without stopping the operation of the pre-update program 306 operating on the embedded device 103.

(1-9) Effect As described above, the update unit 304 of the embedded device 103 can dynamically update a program that operates on the embedded device 103 based on the update information file 307. Unlike the conventional method, in the case of this embodiment, it is not necessary to read the update program into the memory and execute it every time the program is updated. That is, in the embedded device 103 according to the embodiment, the memory consumption due to the rearrangement and the address resolution is greatly reduced.

  Actually, the update unit 304 can convert from an offset to an absolute address based only on the information of the start address (ADDR) on the memory from which the update information file 307 is read. Therefore, the memory consumption can be suppressed to the size of the update information file 307.

  As described above, even if a plurality of update information files 307 are sequentially and cumulatively applied to update the program, the memory consumption can be suppressed. Thereby, the dynamic update of the program can be practically executed even in an embedded device such as an information home appliance with a small amount of memory.

  As an example, a case where the program dynamic update method according to the embodiment is applied to the update operation of the pre-update program 306 that operates on the embedded device 103 will be described. First, the administrator creates an updated program 207 in which the management server 101 corrects the inconvenience. Next, the update information file generation unit 204 is used to create an update information file 208 from the pre-update program 206 and the post-update program 207. The management server 101 distributes the update information file 208 to the embedded device 103 via the network. Finally, the update unit 304 of the embedded device 103 uses the distributed update information file 307 to update the pre-update program 306 of the embedded device 103 to eliminate the inconvenience.

(2) Other Embodiments In the above embodiment, the procedure for transmitting the information update file has not been described. However, it can be executed by the following procedure. For example, a method may be employed in which the management server 101 forcibly transmits the update information file to the embedded device 103 and updates the program in the embedded device 103 at that timing. On the other hand, the embedded device 103 executes processing for confirming whether or not a new update information file exists with respect to the management server 101. If the existence is confirmed, the management server receives a request from the embedded device 103. A method of downloading an update information file from 101 may be adopted.

101 ... management server 102 ... network 103A ... embedded device 103B ... embedded device 201 ... input unit 202 ... display unit 203 ... data processing unit 204 ... update information file generation unit 205 ... storage unit 206 ... pre-update program 207 ... post-update program 208 ... update information file 209 ... network connection unit 301 ... input unit 302 ... display unit 303 ... data processing unit 304 ... update unit 305 ... storage unit 306 ... pre-update program 307 ... update information file 308 ... network connection unit 401 ... pre-update function 402 ... Control transfer instruction 403 ... Control transfer destination 404 ... Function after update 501 ... Function A before update
502 ... Control transfer instruction A
503 ... Control transfer destination A
504 ... Function B before update
505 ... Control transfer instruction B
506 ... Control transfer destination B
507 ... Function C before update
508 ... Control transfer instruction C
509 ... Control transfer destination C
510 ... Updated function 1
511 ... Control transfer instruction 1
512 ... Control transfer destination 1
513 ... Function 2 after update
514 ... Control transfer instruction 2
515 ... Control transfer destination 2
516 ... Function 3 after update
517 ... Offset to function 2 after update 518 ... Offset to control transfer destination 1 519 ... Offset to control transfer destination 2 520 ... Offset 521 to function 3 after update ... Function 601 in OS ... Update information file 602 ... Update Post-function 603 ... Control transition table 604 ... Cross reference table

Claims (9)

A management server that collects update information for pre-update programs running on embedded devices and generates an update information file that resolves addresses in memory for dynamically applying the update information to embedded devices;
A program dynamic update system comprising: an embedded device that dynamically updates an embedded program based on the update information file. 2. The program dynamic update according to claim 1, wherein the update information file includes a post-update function, an address in the memory of the pre-update function, and a relative address in the update information file of the post-update function. system. The update information file has an updated function, an address on the memory in which the function of the embedded program referred to from the updated function is described, and a relative address in the update information file to which the address is written. The program dynamic update system according to claim 1 or 2, characterized in that The update information file includes a plurality of post-update functions having a reference relationship, a relative address in the update information file in which the post-update function to be referred to is described, and a relative address in the update information file to which the address is written. The program dynamic update system according to any one of claims 1 to 3, wherein the program dynamic update system is provided. The embedded device changes the portion indicated by the relative address to an address shifted by an address on the memory in which the reference address of the relative address is written. The program dynamic update system according to item. A storage device for storing a pre-update program running on an embedded device and a post-update program to be newly applied;
Compares the pre-update program with the post-update program, collects update information for the pre-update program, and generates an update information file that resolves addresses in memory for dynamically applying the update information to embedded devices And an update information file generation unit. A storage device that stores a pre-update program, and an update information file for dynamically applying a corrected portion of the post-update program to the pre-update program;
An embedded device comprising: an update unit that dynamically updates an embedded program based on the update information file. A process of comparing the pre-update program and the post-update program and collecting update information for the pre-update program;
A program that causes a computer to execute a process of generating an update information file that resolves addresses in memory for dynamically applying update information to embedded devices. A process of reading an update information file from the storage device for dynamically applying the corrected part of the post-update program to the pre-update program;
A program that causes a computer to execute a process of dynamically updating an embedded program based on the update information file.

Images