KR100308251B1 - Integrated management method of runtime backup information and its system - Google Patents

Abstract

The present invention relates to a method and system for collectively managing execution time backup information of each module in a real-time system executing a plurality of work program modules ('modules'). The present invention includes a medium for recording / storing control information and execution time backup information of a plurality of modules, and a backup manager for integrally managing execution time backup information of the plurality of modules, wherein the backup manager stores the recording / storage. The recording / storage medium is accessed during a backup operation while maintaining the module control information of the medium. Accordingly, by managing the backup operation of all modules by the backup manager of the present invention, it is possible to solve the problems caused by each conventional module directly accessing the storage medium, and to easily maintain, maintain, and use the backup information. It works.

Description

INTEGRATED MANAGEMENT METHOD OF RUNTIME BACKUP INFORMATION AND SYSTEM THEREOF

The present invention relates to a real-time system for executing a plurality of work programs (hereinafter referred to as 'modules'), and more particularly, to a method and a system for managing runtime backup information of each module.

In computer operating systems, real-time systems require management systems such as creating, modifying, and maintaining runtime backup information of modules that perform different tasks. As a conventional execution time backup information management system, a method in which each module performs its own backup management on its own execution time backup information is used, and a technique for integrated management of the entire module is not known.

In the conventional method, all modules requiring runtime backup manage their respective backup information on their own and access the backup information directly to write / read to a recording / storage medium such as EEPROM, EPROM. At this time, each module must accurately predict and secure a space of a certain size in a specific location of the EEPROM in order to maintain runtime backup information. In addition, since each module does not know the location and size of the EEPROM to be used by different modules, it is necessary to artificially determine the starting position of the EEPROM for each module.

Therefore, the conventional runtime backup management method causes the following problems as all modules directly access the EEPROM.

First, each module needs a function for managing a runtime backup, and therefore, a program for the same function must be provided for each module. The same is true when creating a new module that uses runtime backup.

Second, the location and size of the EEPROM for runtime backup information of each module must be determined in advance. Therefore, the following problems may occur when changing the runtime backup structure (adding new contents and deleting existing contents). . First, if the size of backup information to be newly added to the backup structure exceeds a predetermined size, the existing backup information of another module may be overwritten. On the other hand, when the existing content is deleted, the remaining portion of the predetermined portion is not used, thereby reducing the efficiency of using the EEPROM. This has the disadvantage of making it very difficult to debug, especially when a problem occurs with the backup information.

Third, when the hardware of an existing system is changed or a new system is required, it is difficult to reprogram the runtime management.

Accordingly, the present invention has been made to solve the above problems, by adopting a backup manager that integrates and manages the execution time backup information of a plurality of modules to independently perform backup management, the efficiency of information maintenance and management And to provide a method and system for integrated management of runtime backup information that can ensure the stability.

According to an aspect of the present invention, there is provided a real-time system for performing a plurality of work program modules, comprising: a medium for recording / storing control information and execution time backup information of the plurality of modules; And a backup manager for integrally managing execution time backup information of the plurality of modules, wherein the backup manager is configured to access the recording / storage medium during a backup operation while maintaining the corresponding module control information of the recording / storage medium. It is characterized by.

According to another aspect of the present invention, there is provided a method for managing runtime backup information in a real-time system including means for recording / storing runtime backup information of a plurality of work program modules, wherein the recording / storing means is a backup. A first area for recording control information for a job and a second area for recording backup data information; The control information may be used to control a recording / reading operation of control information and execution time backup information of a module currently being executed in a specific area of the recording / storing means.

1 is an overall configuration diagram of a runtime management information integrated management system of the present invention.

2 is a backup manager initialization and backup internal information registration procedure of the present invention.

3 is a flowchart of a modification of the backup structure of the present invention.

<Explanation of symbols for the main parts of the drawings>

130: backup manager 131: backup management table (BMT)

132: EEPROM Mirror 110: EEPROM

111: EEPROM control information section 112: EEPROM data section

150: backup-related operation unit 10, 20, 30: module

Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings.

1 is an overall configuration diagram of a runtime management information integrated management system of the present invention. In the real-time system that performs the module 1 (10), the module 2 (20), and the module N (30), the management system 100 is an EEPROM such as an EEPROM that reads / stores control information and execution time backup information of each module. A recording / storage medium 110 and a backup manager 130 which integrally manages execution time backup information of the plurality of modules.

The internal structure of the EEPROM 110 is composed of a control information unit 111 and a data unit 112. The control information unit 111 is required by the backup manager 130 for each module such as a module identifier (ID), a version, a backup data size, a checksum, a backup data location, and the like. It is a space where internal information is recorded. The data section 112 is a space in which backup information data of each module is recorded. The recording area of each module is determined by the backup data position and data size information of the control information unit and can be stored in units of pages.

The backup manager 130 includes a backup management table (BMT) 131 and an EEPROM mirror 132. The BMT 131 includes the contents of the EEPROM control information unit 111 and maintains internal information required by the backup manager 130. Since the BMT 131 maintains backup-related information of all modules at the same time as the control information unit 111 of the EEPROM during the backup operation, the EEPROM access can be minimized during the backup operation. The EEPROM mirror 132 is used to relocate the entire backup storage location if the backup structure of a particular module has changed.

The backup manager 130 may include a backup manager initialization process performed at system boot, a backup internal information registration process performed at initialization of each module, a read / write process for specific backup information, as shown in block 150, and the like. Perform a process of changing a specific backup data structure. These processes will be described with reference to FIGS. 2 and 3.

2 is a procedure of initializing a backup manager and registering backup internal information of the present invention.

The backup manager initialization process is performed at system boot and operates according to the current state of the EEPROM 110. That is, when the system is booted, the backup manager 100 enters the backup manager initialization step 200 and determines whether backup information exists in the EEPROM 110 (210). If there is no backup information, a BMT is generated (211). If there is backup information, a BMT is generated and the contents of the EEPROM control information unit 111 are updated to the generated BMT (211).

After the initialization step is completed, if the module is initialized, it enters the backup internal information registration step 220 and determines whether the corresponding module ID exists in the BMT (230). If the module ID exists in the BMT, the registration procedure is ignored. If the module ID does not exist in the BMT, the backup internal information is registered in the BMT (240), and the registered information of the BMT is updated (250) in the control information unit 111 of the EEPROM. Then, the space used for the module is secured in the data unit 112 of the EEPROM depending on the control information updated in the control information unit 111 of the EEPROM (260).

The read / write process for the specific backup information is performed at the execution time of the specific module registered in the BMT after the registration step of the internal information is completed, and the EEPROM is accessed to read or write the backup information.

3 is a flowchart of a modification of the backup structure of the present invention.

The backup structure change process is performed to change the backup structure by adding or deleting new contents of a specific module.

When the backup structure change request of a specific module, the backup management system 100 enters the backup structure change step 300 and registers new internal information of the specific module with the backup manager 130 (310). The backup manager 130 determines whether a specific module ID exists in the BMT (320) and terminates the procedure if it does not exist. If the module ID exists, it is determined whether they are different by comparing the version between the newly registered specific module and the previously registered module (330).

If the versions are different from each other, the EEPROM mirror 132 is initialized (340), and the contents to be changed in the EEPROM 111 are relocated to the EEPROM mirror (132) (350). Then, according to the state of the EEPROM mirror 132, the BMT is updated 360 with contents (module ID, version, backup data size, checksum, backup data location) to be entered in the EEPROM control information unit 111. Now, the contents of the EEPROM mirror 132 are copied to the EEPROM 110 (370) to complete the change of the backup structure by adding or deleting new contents.

The present invention is not limited by the embodiments described above, and various changes and modifications can be made by those skilled in the art, which are included in the spirit and scope of the present invention as defined in the appended claims.

As described above, by independently managing the execution time backup information of a plurality of modules by the backup manager, it is easy to maintain and use the backup information, and to easily debug when a problem occurs in the backup information. There is this.

In addition, it is possible to avoid duplication of implementation of the same backup management function by each conventional module. In addition, since the present invention is applicable to all systems requiring runtime backup information, the same function in different systems can be avoided. Redundant implementations can be avoided and problems caused by changing the backup structure for a particular module can be solved.

Claims (4)

In a real-time system for creating, modifying, maintaining and managing backup information for a plurality of work program modules, backup control information such as identifier, version, backup data size and backup data storage location of each module for the plurality of modules; A recording / storing medium for recording / storing execution time backup information into a control information storage area and a data storage area; A backup manager table which is generated during an initialization process at system booting and registers and maintains backup control information having the same contents as each module internal information stored in the recording / storage medium; And a mirror means having the same storage area as the recording / storage medium and relocating to the backup structure of the recording / storage medium when the backup structure of a specific module is changed. . The integrated management system of claim 1, wherein the mirror unit copies the contents of the rearranged mirror unit to the recording / storage medium. A method for managing runtime backup information in a real-time system comprising means for recording / storing runtime backup information of a plurality of work program modules, the system being booted, determining whether backup information is present in the recording / storing means. If there is no backup information, a backup management table is created, and if there is backup information, a backup manager initialization process of creating a backup management table and updating control information to the backup management table; It is determined whether an ID exists in the backup management table. If a module ID exists, the registration procedure is ignored. If a module ID does not exist, the backup internal information is registered in the backup management table and the recording / storing is performed. Registering backup internal information for updating control information of the means to said backup management table; And accessing the recording / storing means to read or write backup information at the execution time of the specific module registered in the backup management table, and upon request to change the backup structure of the specific module, the ID of the specific module is the backup. If it exists in the management table, it is determined whether they are different by comparing the versions between a specific registered module and a previously registered module. If the versions are different, the contents to be changed are rearranged using a mirror, and then the And a backup structure for copying contents to the recording / storing means. The method of claim 3, wherein the changing of the backup structure further comprises updating control information (module ID, version, backup data size, checksum, backup data location) of the backup management table depending on the state of the mirror. Integrated management method of the runtime backup information comprising a.