KR20160003505A - Dynamic module, Method and apparatus for dynamic upgrade having the same - Google Patents

Abstract

Provided are a dynamic module, a device and method for a dynamic upgrade having the same. The dynamic upgrade device includes: a dynamic module for upgrading a module core library without pausing a module processor for providing the functions of network equipment; and a dynamic upgrade management unit linked with the dynamic module for controlling the upgrade of the dynamic module.

Description

TECHNICAL FIELD [0001] The present invention relates to a dynamic module, a dynamic upgrade apparatus having the dynamic module,

The present invention relates to a dynamic module and a dynamic upgrading apparatus and method thereof. More particularly, the present invention relates to a dynamic module and a dynamic upgrading method for the network module without interrupting the network module processor itself, And more particularly, to a dynamic module for dynamically upgrading a software module of a device, and a dynamic upgrade apparatus and method having the same.

High Availability (HA) is a system or component that provides continuous service to enable continuous operation without interruption. The degree of availability is expressed as a ratio of service time to failure time. For example, 100% availability is the most ideal number, but because there is a clear probability that a faulty system will ever fail, a system that provides a high level of availability is called "Five Nine" %. That is, there is a probability of less than 52 minutes of downtime due to disability during the year.

In general, factors that impede the continuity of services are classified into Planned Downtime and Unplanned Downtime. During planned downtime, it is imperative to perform planned tasks with the necessary factors to operate the system, such as system change, new system introduction, data backup, software change, etc., and fail to provide service even during planned downtime. Unplanned downtime is caused by a sudden failure in the service system, and depending on the type and severity of the failure, the time required for recovery may vary and downtime may vary.

One of the reasons why high availability is important is that the downtime of the service system is immediately lost. Although the amount of loss will vary depending on the type and importance of the service, in general, a failure of a CORE ROUTER or a DNS SERVER may cause the entire network user to be unreachable, and the damage caused thereby may be an astronomical numerical value have. Therefore, the goal of high availability is to maximize availability by minimizing service downtime.

In order to implement the high-availability function in general, a lot of redundancy technology is used so that another system can continue to provide services even if one system is down. That is, the high availability function of the network equipment monitors the failure state of the equipment even if there is no administrator, and provides the continuity of service by processing the service in the redundant standby equipment when a failure is detected.

HA technology using redundancy is indispensable in large-capacity network equipment, and it is required to be implemented as an important element technology in many network systems. However, the HA technology using redundancy has a problem that the cost is increased because the equipment must be duplicated. Accordingly, although expensive high-capacity network equipment basically provides HA function using redundancy, there is a problem that HA function is not provided at all due to a cost problem in low-cost and low-performance network equipment.

Therefore, failures and software upgrades are indispensable for low-cost and low-performance network equipment, and service downtime may occur, so that when a failure occurs or a software upgrade is performed, the software upgrade can be performed in real- Dynamic software upgrade technology is required.

Korean Patent No. 10-0871778 ("Dynamic addressing method and apparatus using a centralized dynamic addressing manager ", InnoPath Software, Inc., published on July 27, 2006)

SUMMARY OF THE INVENTION It is an object of the present invention to solve the above problems and to provide a method and apparatus for upgrading a software module of a network device without interruption of the network module processor itself, And a dynamic upgrade apparatus and method having the same.

The technical objects of the present invention are not limited to the technical matters mentioned above, and other technical subjects not mentioned can be clearly understood by those skilled in the art from the following description.

In accordance with an aspect of the present invention, there is provided an apparatus for dynamically upgrading software of a network device, the method comprising: upgrading a module core library without stopping a module processor for providing functions of the network equipment; Dynamic module; And a dynamic upgrade manager for controlling the upgrade of the dynamic module in association with the dynamic module.

Wherein the dynamic module comprises: a module framework part for performing an upgrade by converting an upgrade request message transferred from the dynamic upgrade device into a control work; And a module core unit for upgrading the module core library without stopping the module processor using a module framework implementing function for processing the control work.

Wherein the dynamic upgrade management module comprises: an upgrade management module for delivering the upgrade request message to the dynamic module; And a process management module for managing the process operation of the dynamic module.

Wherein the dynamic upgrade management unit comprises: a command management module for processing an operator module upgrade command for requesting an upgrade of the dynamic module; A checkpoint management module for checking synchronization of internal data of the dynamic module; And a message management module for processing a message for communication with the dynamic module.

The upgrade management module requests the process management module to determine whether the dynamic module is operated or not when the upgrade command is received from the command management module.

And the upgrade management module transfers the upgrade request message to the dynamic module when it is determined that the process of the dynamic module is in operation.

According to another aspect of the present invention, there is provided a dynamic module operating in conjunction with a dynamic upgrade apparatus for controlling software upgrade of a network device from outside, the dynamic module comprising: A module core unit for upgrading the module core library without interrupting the module processor upon request for change of the library; And a module framework unit that operates in conjunction with the dynamic upgrade apparatus and controls the module core unit to upgrade the module core library.

The module framework includes a message thread for receiving an upgrade request message transmitted from the dynamic upgrade apparatus and converting the upgrade request message into a control work; A work queue receiving the work from the message thread and performing buffering; And a work thread for requesting a module framework implementing function for processing a work delivered via the work queue to the module core unit.

And the message thread sequentially transfers the control work for upgrading the module core library to the work queue when the upgrade request message is received.

The work thread determines a module framework implementation function according to the type of the control work delivered through the work queue and requests the module framework implementation unit.

Wherein the module core unit comprises: a module framework implementing unit for upgrading the module core library without interrupting the module processor using a set of module framework implementing functions for processing the control work; And a module core library unit having the module core library and modifying the module core library under the control of the module framework implementing unit.

According to another aspect of the present invention, there is provided a method for upgrading a module core library having a function of a network device in a dynamic upgrade apparatus, Transmitting a message; Converting the upgrade request message to a control work; And upgrading the module core library without interrupting a module processor for providing functions of the network equipment using a module framework implementing function for processing the control work.

Wherein the delivering comprises: receiving an upgrade command of a dynamic terminal having the module core library from an operator; Confirming whether or not the dynamic terminal is operating a process; And generating an upgrade request message for executing the command based on the checking result.

The step of confirming whether or not the operation is performed includes the steps of: transmitting an error message to terminate the upgrade if the process of the dynamic terminal is not in operation; And transmitting the upgrade request message to the dynamic terminal if the process of the dynamic terminal is in operation.

Upgrading the module core library comprises: copying and backing up a data block necessary for upgrading the module core library; Linking the module core library to a new module core library; And recovering the backup data by copying the data block of the new module core library.

In accordance with another aspect of the present invention, there is provided a method for performing an upgrade in a dynamic module operating in conjunction with a dynamic upgrade apparatus for controlling software upgrade of an external network device, Converting the upgrade request message transferred from the upgrade request message into a control work; Calling a module framework implementation function for processing the control work; And upgrading the module core library without interrupting the module processor for providing the function of the network equipment using the module framework implementing function.

Wherein the converting the request message to a control work includes: generating a first control work requesting a function interruption of the module core library; Generating a second control work requesting a backup of data of the module core library; Creating a third control work requesting an exchange to a new module core library; Generating a fourth control work that copies data of the new module core library and requests recovery of backup data; And a fifth control work requesting execution of the general work after completion of the upgrade.

The calling step may include sequentially calling first through fifth module framework implementing functions corresponding to the first through the fifth control work.

Wherein upgrading the module core library comprises: stopping the function of the module core library currently being executed using the first module framework implementation function; Copying and backing up data of the module core library using the second module framework implementing function; Linking the new module core library after terminating the link of the module core library using the third module framework implementation function; Recovering data copy and backup data of the new module core library using the fourth module framework implementation function; And processing the general work using the fifth module framework implementing function.

According to the above-described dynamic module and the dynamic upgrade apparatus and method having the same, the core functions of the module framework and the network equipment for performing the dynamic upgrade by linking the configuration of the dynamic module with the device for controlling the software upgrade of the network equipment from the outside As the module core library is completely separated and operated, it is possible to perform dynamic software upgrade by changing only the module core library function in real time without terminating the module process without analyzing the module to be upgraded.

In addition, according to the embodiment of the present invention, dynamic software upgrading based on a software architecture framework is performed differently from the dynamic patch method, so that all module developers can be provided with a standard external interface capable of developing a dynamic module, The core functions can be developed in the form of libraries and upgraded.

1 is a diagram showing an example of a software upgrade technique and a DSU technology through a general redundancy.
2 is a diagram showing an example of software module upgrade using general DSU technology.
3 is a diagram illustrating a dynamic upgrade apparatus according to an embodiment of the present invention.
Fig. 4 is a diagram showing the framework of the dynamic module shown in Fig. 3. Fig.
5 is a diagram showing a message processing procedure of the dynamic module shown in FIG.
6 is a diagram illustrating an interface procedure between a dynamic module and an overall dynamic upgrade software framework according to an embodiment of the present invention.
FIGS. 7 and 8 are diagrams illustrating a procedure of a dynamic upgrade protocol internal processing in a dynamic module according to an embodiment of the present invention.
9 is a flowchart illustrating a dynamic upgrade method according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail.

It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the relevant art and are to be interpreted in an ideal or overly formal sense unless explicitly defined in the present application Do not.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In order to facilitate the understanding of the present invention, the same reference numerals are used for the same constituent elements in the drawings and redundant explanations for the same constituent elements are omitted.

1 is a diagram showing an example of a software upgrade technique and a DSU technology through a general redundancy. 2 is a diagram showing an example of software module upgrade using general DSU technology.

As shown in FIG. 1, a dynamic software upgrade method such as a DSU (Dynamic Software Upgrading) 10 technique for implementing a high availability function is generally classified into an ISSU (In-Service Service Upgrading) Since hardware redundancy is not taken into consideration, it is advantageous in terms of cost, but implementation is very complicated and difficult. The DSU (10) technology changes only the software modules that are to be upgraded, while all other software modules must remain running while one software module is being modified. The DSU (10) technology should not affect the configuration and integrity of the entire software at all in one software module change. In addition, the DSU 10 technology must maintain state information prior to the change even after the changed software module is changed. Due to these requirements, the DSU (10) technology should also be carefully determined when software modules are upgraded.

For example, the (32) "Func-a 'g., Using a DSU (10) described as 2 software modules 30 of the Component A (31) the" Func-a () "of Component A function of () ", The change may occur while the" Func-a () "of Component A 31 is being executed, and thus the status of various local variables and information being executed may be changed, State consistency problems may occur. In other words, it must be changed to "Func-a ' ()" before "Func-a ()" is executed or when the execution is completed, and consistency can be maintained. In order to upgrade the software module 30 using the DSU 10 technology, the state before and after the upgrade must be consistent, and the state of the stable state or the quiescence state in which the state is not changed even when the upgrade is performed You must perform an upgrade.

Most of these dynamic software upgrade technologies are based on Dynamic Patches. To implement Dynamic Patches technology, we developed a separate compiler that supports Dynamic Patches, developed a source patch generator by analyzing source changes, and upgraded to apply to real running programs. And development of tools (udate control tools). However, it is not easy to develop a dedicated compiler and patch tool, and the Dynamic Patches technologies currently being used are being studied in the form of papers. Since the system is configured for a specific purpose, it is applied to all general software modules There are difficulties in doing so. In other words, the DSU (10) technology based on Dynamic Patch has been studied so far to meet only one specific purpose, requiring a level of product or system that is applicable to all general software in the industry.

Hereinafter, a dynamic software upgrade method based on a software architecture framework according to an embodiment of the present invention, which can freely control a software module without analyzing the software module unlike the conventional Dynamic Patches-based upgrade technology, will be described .

3 is a diagram illustrating a dynamic upgrade apparatus according to an embodiment of the present invention.

3, the dynamic upgrade apparatus 100 according to the embodiment of the present invention includes a dynamic upgrade management module 110 and a dynamic module module 120 as a dynamic upgrade software framework .

The dynamic upgrade management unit 110 provides a framework service (Framework Services) that supports a variety of service software managers to perform a dynamic software upgrade. The dynamic upgrade management unit 110 includes a command management module 111, an upgrade management module 112, a process management module 113, -Point Manager Module 114 and a Message Manager Module 115. Although the dynamic upgrade management module according to the embodiment of the present invention is configured as a software management module that supports five framework services, the present invention is not limited thereto and can be extended according to required service functions.

The comment management module 111 performs communication with the operator and processes commands transmitted from the operator.

The process management module 113 manages the processes of all the dynamic modules operating in the network equipment.

The upgrade management module 112 performs an upgrade procedure for the dynamic module.

The checkpoint management module 114 performs internal data synchronization of the dynamic module.

The message management module 115 processes messages transferred for mutual communication among all the modules.

Meanwhile, the dynamic module unit 120 includes dynamic modules 120 _{1 -} 120 _{N that} are mounted on the network equipment and perform core functions and can be dynamically upgraded. The dynamic modules 120 _{1 -} 120 _N interoperate with the management modules 111 - 115 of the dynamic upgrade manager 110 for a dynamic upgrade to a standardized interface. To this end, the dynamic modules 120 _{1 -} 120 _N have their own internal structure, and more details will be described later.

The dynamic upgrade software framework according to an embodiment of the present invention operates in a single OS (e.g., an OS (e.g., Linux / Unix / Window)) process in order to reduce interdependency between software modules, (Direct Access), and acts as an indirect call of the message communication method through the message management module 115.

Fig. 4 is a diagram showing the framework of the dynamic module shown in Fig. 3. Fig.

4, since the dynamic modules 120 ₁ -120 _N of the dynamic module 120 according to the embodiment of the present invention are identical to each other, the dynamic module 120 ₁ will be described in detail .

The dynamic module 120 ₁ includes a module framework part 121 and a module core part 122 as a dynamic upgrade module framework.

The module framework unit 121 operates in conjunction with the dynamic upgrade management unit 110 as a module framework. The module framework unit 121 includes a message thread 1211, a work queue 1212, and a work thread 1213.

The message thread 1211 converts the request message into an internal work (WORK) when the request message is transmitted from the outside. Then, the message thread 1211 delivers the work WORK to the work queue 1212.

The work queue 1212 receives the work WORK from the message thread 1211. The work queue 1212 performs buffering of the work WORK. The work queue 1212 delivers the work WORK to the work thread 1213 after a predetermined time.

The work thread 1213 receives the work WORK from the work queue 1212. The work thread 1213 transfers the delivered work WORK to the module core unit 122.

Meanwhile, the module core unit 122 functions as an actual module for operating in a network equipment as a module core dynamic library, and upgrades the module core library without terminating the module process. The module core section 122 includes a module framework implementation section 1221 and a module core library section 1222.

The module framework implementation unit 1221 includes a set of standardized module framework implementation APIs (application program interfaces) that the work thread 1213 can call for work processing. The module framework implementation unit 1221 upgrades the module core library of the dynamic module 120 _{1 in} conjunction with the dynamic upgrade software framework using a set of APIs. In other words, when a core function change is required, the module framework implementing unit 1221 changes only the module core library function of the module core library unit 1222 in real time without terminating the process of the dynamic module, Perform the upgrade.

The module core library unit 1222 includes a module core library in which core functions of software unit modules are implemented in the form of a dynamic library so that dynamic upgrading is possible.

As described above, the dynamic upgrade module framework of the dynamic module completely separates the module core portion 122 provided with the module framework portion 121 for interlocking with the external software framework and the module core library in which the core function of the network equipment is implemented , And a module external to the module framework section 121 to allow a module developer to develop a dynamic module. The module developer develops core functions in the form of a module core library and performs a dynamic software upgrade by a module framework can do.

5 is a diagram showing a message processing procedure of the dynamic module shown in FIG.

As shown in FIG. 5, the dynamic modules 120 ₁ -120 _N of the dynamic module 120 are the same in the embodiment of the present invention, so that the dynamic module 120 ₁ will be described in detail.

The message thread 1211 of the module framework unit 121 performs an iterative loop and checks whether there is a request message input from the outside (hereinafter referred to as an "external request message"). In the embodiment of the present invention, it is assumed that an external request message is input from the dynamic module 120 ₂ . If there is an external request message, the message thread 1211 converts the external request message into a work (WORK) and delivers it to the work queue 1212. Similarly, the work thread 1213 also performs an iterative loop and checks whether the work queue 1212 has a work WORK. If the work WORK exists in the work queue 1212, the work thread 1213 delivers the work WORK to the module core unit 122. [

The external request message according to the embodiment of the present invention is processed as one WORK. When the external request is processed as a unit transaction, the module needs to be upgraded in a quiescent state . In other words, when performing the upgrade of the module core library, the work thread 1213 determines that the dynamic operation of the work (WORK) performed before the execution of the previous work is completely completed, do. In addition, while the upgrade of the dynamic module 120 ₁ is being performed, since the work for the external request is buffered in the work queue 1212, the work thread 1213 is again able to request an external request Can be processed.

The following describes the types of work (WORK) processed by the dynamic module 120 ₁ . The dynamic module 120 ₁ processes it as a "request work" in the case of a general external message request and as an "upgrade work" in the case of an external message request for an upgrade.

1. Request Work: A typical work performed by a module

2. Control Work: Five control works (CW1-CW5) for performing upgrade work, and can be extended for control purpose if necessary

- TERM WORK (CW1): Request to interrupt the module core library

- Checkpoint outwork (CKPT-OUT WORK) (CW2): Module for core dynamic upgrade

- Exchange work (CHNG WORK) (CW3): exchange request to new module core library

- CKPT-IN WORK (CW4): New module replaced after dynamic upgrade. Request to read and recover critical data backed up to the core library.

- START WORK (CW5): Request to re-perform the functions of the module core library after completing the dynamic upgrade

On the other hand, when the work WORK is transferred from the work queue 1212 to the work thread 1213, the module framework implementation unit 1221 of the module core unit 122 transmits the module framework implementation function Lt; / RTI > A module framework implementation function according to an embodiment of the present invention is as follows, and is expandable as needed.

- processWork: invoked when processing the request work

- termWork: invoked when processing an end work during upgrade work

-checkpointWork: Called when handling Checkpoint Outwork and Checkpoint Inwork during upgrade work.

The following describes the Request Work protocol processing procedure in the dynamic module 120 ₁ .

In the dynamic module 120 ₁ , the message thread 1211 of the module framework part 121 receives the external request message from the dynamic module 120 ₂ (S 100). The message thread 1211 converts the external request message into a work (WORK) for internal processing (S110). The message thread 1211 delivers the converted work (WORK) to the work queue 1212 (S120). The work queue 1212 performs buffering of the work WORK.

The work thread 1213 fetches a work WORK from the work WORK (S130). The work thread 1213 judges whether or not the work WORK is a request work. The work thread 1213 calls the module framework implementation function "processWork" for the work (WORK) to the module framework implementation unit 1221 of the module core unit 122, if the work WORK is a request work (S140). The module core library unit 1222 processes the work WORK using "processWork" (S150).

Hereinafter, the dynamic upgrade protocol processing procedure will be described in detail with reference to FIGS. 6 to 8. FIG.

6 is a diagram illustrating an interface procedure between a dynamic module and an overall dynamic upgrade software framework according to an embodiment of the present invention. 6, an interface procedure between the dynamic upgrade management unit 110 and the dynamic module 120 ₁ of the dynamic upgrade apparatus 100 will be described.

As shown in FIG. 6, an operator according to an embodiment of the present invention may include a dynamic module 120 _{1 -} 120 _N of the dynamic module unit 120 (hereinafter, referred to as a "target dynamic module" A new module core library 200 is created. Then, the operator copies it to the module library registry 300 and inputs the "operator module upgrade command" generated by the operator command to the command management module 111 of the dynamic upgrade management unit 110 (S200). In the embodiment of the present invention, it is assumed that the dynamic module 120 ₁ is a target dynamic module. Here, the Module Library Repository may be a memory such as a disk. Then, the comment management module 111 receives the "operator module upgrade command" input by the operator command.

The comment management module 111 sends an "operator module upgrade command" to the upgrade management module 112 to request dynamic upgrade (S210). The upgrade management module 112 requests the process management module 113 to inform whether the process of the target dynamic module 120 ₁ is actually operating or not (S220). The process management module 113 transfers the operation result information of the process of the target dynamic module 120 ₁ to the upgrade management module 112.

The upgrade management module 112 receives the operation result information of the target dynamic module 120 ₁ from the process management module 113. The upgrade management module 112 transmits an upgrade request message to the target dynamic module 120 ₁ based on the operational result information (S230). That is, if it is determined that the process of the target dynamic module 120 ₁ is not in operation based on the operation result information, the upgrade management module 112 transmits an error message to the comment management module 111. If it is determined that the process of the target dynamic module 120 ₁ is in operation, the upgrade management module 112 transfers the upgrade request message to the target dynamic module 120 ₁ .

The target dynamic module 120 ₁ performs the dynamic module upgrade internal procedure when an upgrade request message is received. A detailed description of the dynamic module upgrade internal procedure will be given later with reference to FIGS. 7 and 8. FIG. The target dynamic module 120 ₁ generates an upgrade success completion message upon successful completion of the dynamic module upgrade and generates an upgrade failure message if the upgrade is not successfully completed. The target dynamic module 120 ₁ transmits an upgrade success completion message or an upgrade failure message to the upgrade management module 112 according to whether the dynamic module upgrade is successful (S240). When the upgrade success completion message is received from the target dynamic module 120 ₁ , the upgrade management module 112 updates the module core library of the module core part 122 of the target dynamic module 120 ₁ to the new module core library 200 (S250).

FIGS. 7 and 8 are diagrams illustrating a procedure of a dynamic upgrade protocol internal processing in a dynamic module according to an embodiment of the present invention.

7 and 8, the upgrade management module 112 of the dynamic upgrade management unit 110 according to the embodiment of the present invention delivers the upgrade request message to the target dynamic module 120 ₁ (S300). Then, the message thread 1211 of the module framework part 121 of the target dynamic module 120 ₁ performs an iterative loop to check whether there is an external request message.

The message thread 1211 determines whether the external request message is an upgrade request message. If the external request message is an upgrade request message, the message thread 1211 sequentially generates the control work CW1-CW5 and inputs it to the work queue 1212. [ Then, the work thread 1213 sequentially receives the control works CW1 to CW5 through the work queue 1212 (S301). The order of input to the work thread 1213 according to the embodiment of the present invention is the end work CW1, the check point out work CW2, the exchange work CW3, the check point work CW4 and the start work CW5, .

7, the work thread 1213 inputs the module framework implementation function "termWork" for the end work CW1 in the module framework implementation function to the module To the core unit 122 (S302). When "termWork" is called, the module core unit 122 stops all functions of the dynamic module library currently being executed, and stays in a stable state and waits.

The work thread 1213 receives the checkpoint out work CW2 from the work queue 1212. [ When the checkpoint outwork CW2 is input, the work thread 1213 calls the module framework implementation function "checkpointWork" for the checkpoint outwork CW2 in the module framework implementation function to the module core unit 122 (S303). At this time, specify as checkpoint-OUT as a parameter. When the " checkpointWork "is called, the module core unit 122 copies and backs up all the data blocks necessary for performing the module core library upgrade to the checkpoint management module 114 (S304).

The work thread 1213 receives the exchange work CW3 from the work queue 1212. [ When the exchange work CW3 is input, the work thread 1213 calls the termination function for terminating the module core library of the currently linked module core unit 122 to the module core unit 122 (S305). When the termination function is called, the module core unit 122 terminates the currently linked module core library (S306). For example, the work thread 1213 calls the "dlclose " function when the module core 122 operates on Linux, and calls the link termination function appropriate to the OS when operating on another OS, Terminate it and delete it from the memory.

The work thread 1213 performs a process for linking the new module core library 200 stored in the module library register 300 to the module core library unit 1222 in step S307, (S308). For example, the work thread 1213 calls the "dlopen" function when the module core unit 122 operates in Linux, and calls the link start function corresponding to the OS when operating as a different OS, (200). When the link of the new module core library 200 is normally completed, the work thread 1213 judges that the new module core library 200 is upgraded to the module core unit 122.

The next work thread 1213 receives the work CW4 as a check point from the work queue 1212 as shown in FIG. When the checkpoint work CW4 is input, the work thread 1213 calls the module framework implementation function "checkpointWork" for the work (CW4) as a checkpoint in the module framework implementation function to the module core unit 122 (S309). At this time, it is a checkpoint of the parameter (checkpoint-IN). When the " checkpointWork "is called, the module core unit 122 copies all the data blocks required for the execution of the new module core library 200 from the checkpoint management module 114, and restores the backup data, (S310).

The work thread 1213 receives the start work CW5 from the work queue 1212. [ When the start work CW5 is input, the work thread 1213 calls the module framework implementation function "processWork" for the start work CW5 among the module framework implementation functions to the module core unit 122 (S311). When the " processWork "is called, the module core unit 122 judges that the module core library has been successfully upgraded successfully and that general request work processing is possible, and receives the request work from the work queue 1212 and performs normal processing.

Finally, the message thread 1211 transmits an upgrade completion message to the upgrade management module 112 to inform the upgrade success of the module core library of the target dynamic module 120 ₁ (S312).

9 is a flowchart illustrating a dynamic upgrade method according to an embodiment of the present invention. In FIG. 9, it is assumed that the dynamic module 120 ₁ among the dynamic modules 120 _{1 -} 120 _N is a target dynamic module.

6 and referring to Figure 9, keomaenteu management module 111 of the dynamic upgrade management unit 110 in the dynamic upgrading apparatus 100 according to an embodiment of the present invention "for dynamic upgrading of the target dynamic module (120 ₁₎ Quot; operator module upgrade command "from the operator (S400). The comment management module 111 sends an "operator module upgrade command" to the upgrade management module 112 to request upgrade. The upgrade management module 112 requests the process management module 113 to inform whether or not the process of the target dynamic module 120 ₁ is actually operating. The process management module 113 transfers the operation result information of the process of the target dynamic module 120 ₁ to the upgrade management module 112.

The upgrade management module 112 receives operational result information from the process management module 113 (S410). The upgrade management module 112 determines whether the process of the target dynamic module 120 ₁ is in operation based on the operation result information (S420).

If it is determined in operation S420 that the process of the target dynamic module 120 ₁ is not in operation, the upgrade management module 112 transmits an error message to the comment management module 111 and terminates the dynamic software upgrade procedure. If it is determined in operation S420 that the process of the target dynamic module 120 ₁ is in operation, the upgrade management module 112 transmits an upgrade request message to the target dynamic module 120 ₁ (S 430).

Then, the module framework part 121 of the target dynamic module 120 ₁ receives the upgrade request message (S430). The module framework unit 121 converts the upgrade request message to generate the control work CW1 to CW5 and sequentially transmits the control work to the module core unit 122 at step S440.

Specifically, the module framework unit 121 calls the module framework implementation function for the control workloads CW1 and CW2 to the module core unit 122. [ The module core unit 122 stops all the functions of the current dynamic module library and copies and backs up all the data blocks necessary for performing the module core library upgrade to the checkpoint management module 114 in operation S450.

The module framework unit 121 calls the module framework implementation function for the control work CW3 to the module core unit 122. [ The module core unit 122 closes the currently linked module core library and links the new module core library 200 stored in the module library registry 300 to the module core library unit 1222 in operation S460.

The module framework unit 121 calls the module framework implementation function for the control work CW4 to the module core unit 122. [ The module core unit 122 copies all data blocks necessary for the execution of the new module core library 200 from the checkpoint management module 114 and restores the backup data to maintain the same state as that before the upgrade (S470) .

The module framework unit 121 calls the module framework implementation function for the control work CW5 to the module core unit 122. [ The module core unit 122 determines that the module core library has been successfully upgraded and that the general request work process is possible, receives the request work from the work queue 1212, and performs a normal process (S480). Then, the module framework unit 121 transmits a dynamic upgrade complete message to the upgrade management module 112 to inform the upgrade success of the module core library of the target dynamic module 120 ₁ (S490).

While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, And various modifications may be made by those skilled in the art without departing from the scope of the present invention.

100: dynamic upgrade device 110: dynamic upgrade management module
111: comment management module 112: upgrade management module
113: Process management module 114: Checkpoint management module
115: message management module 120: dynamic module module
121: module framework part 122: module core part

Claims (19)

1. An apparatus for dynamically upgrading software of a network equipment,
A dynamic module for upgrading the module core library without interruption of a module processor for providing the function of the network equipment; And
A dynamic upgrade management unit operable to control the upgrade of the dynamic module in cooperation with the dynamic module;
The dynamic upgrade apparatus comprising: The method according to claim 1,
The dynamic module comprises:
A module framework part for converting the upgrade request message transferred from the dynamic upgrading device into a control work and performing upgrading; And
And a module core unit for upgrading the module core library without stopping the module processor using a module framework implementation function for processing the control work. 3. The method of claim 2,
Wherein the dynamic upgrade management unit comprises:
An upgrade management module for delivering the upgrade request message to the dynamic module; And
And a process management module for managing whether or not the process of the dynamic module is operated. The method of claim 3,
Wherein the dynamic upgrade management unit comprises:
A command management module for processing an operator module upgrade command requesting an upgrade of the dynamic module;
A checkpoint management module for checking synchronization of internal data of the dynamic module; And
Further comprising a message management module for processing messages for communication with the dynamic module. 5. The method of claim 4,
The upgrade management module includes:
And requests the process management module to inquire whether or not the process of the dynamic module is operated when the operator module upgrade command is transmitted from the command management module. 6. The method of claim 5,
The upgrade management module includes:
And the upgrade request message is delivered to the dynamic module if it is determined that the process of the dynamic module is in operation. A dynamic module operating in conjunction with a dynamic upgrading device for controlling software upgrades of network equipment from outside,
A module core unit for upgrading the module core library without interrupting a module processor when a module core library in which functions of the network equipment are requested is changed; And
A module framework part operating in conjunction with the dynamic upgrading device and performing an upgrade of the module core library by controlling the module core part,
And a dynamic module. 8. The method of claim 7,
Wherein the module framework part comprises:
A message thread for receiving an upgrade request message transmitted from the dynamic upgrade apparatus and converting the upgrade request message into a control work;
A work queue receiving the work from the message thread and performing buffering; And
And a work thread for requesting a module framework implementing function for processing a work delivered via the work queue to the module core unit. 9. The method of claim 8,
The message thread,
And when the upgrade request message is received, transferring the control work for upgrading the module core library sequentially to the work queue. 10. The method of claim 9,
The work thread,
Wherein a module framework implementation function is determined according to a kind of control work delivered through the work queue and the module framework implementation unit requests the module framework implementation function. 11. The method of claim 10,
The module core portion includes:
A module framework implementing unit for upgrading the module core library without interrupting the module processor using a set of module framework implementing functions for processing the control work; And
And a module core library unit having the module core library and modifying the module core library under the control of the module framework implementing unit. A method for performing an upgrade of a module core library having a function of a network equipment in a dynamic upgrade apparatus,
Transferring an upgrade request message for upgrading the module core library;
Converting the upgrade request message to a control work; And
Upgrading the module core library without interruption of a module processor for providing the functionality of the network equipment using a module framework implementation function for processing the control work
And a dynamic upgrade method in the dynamic upgrade apparatus. 13. The method of claim 12,
The method of claim 1,
Receiving an upgrade command of a dynamic terminal having the module core library from an operator;
Confirming whether or not the dynamic terminal is operating a process; And
And generating an upgrade request message for executing the command based on the result of the checking. 14. The method of claim 13,
The method of claim 1,
If the process of the dynamic terminal is not in operation, transmitting an error message to terminate the upgrade; And
And forwarding the upgrade request message to the dynamic terminal if the process of the dynamic terminal is in operation. 13. The method of claim 12,
Wherein upgrading the module core library comprises:
Copying and backing up data blocks necessary for upgrading the module core library;
Linking the module core library to a new module core library; And
And copying the data block of the new module core library and restoring the backup data. 1. A method for performing an upgrade in a dynamic module operating in conjunction with a dynamic upgrade apparatus for controlling a software upgrade of a network equipment from outside,
Converting an upgrade request message delivered from the dynamic upgrade apparatus to a control work;
Calling a module framework implementation function for processing the control work; And
Upgrading the module core library without interrupting the module processor for providing the functions of the network equipment using the module framework implementing function
The dynamic upgrade method comprising: 17. The method of claim 16,
The step of converting the request message into a control work includes:
Generating a first control work requesting a function interruption of the module core library;
Generating a second control work requesting a backup of data of the module core library;
Creating a third control work requesting an exchange to a new module core library;
Generating a fourth control work that copies data of the new module core library and requests recovery of backup data; And
And generating a fifth control work requesting to perform a general work after completion of the upgrade. 18. The method of claim 17,
Wherein the calling comprises:
And sequentially calling the first through fifth module framework implementing functions corresponding to the first through the fifth control work. 19. The method of claim 18,
Wherein upgrading the module core library comprises:
Stopping the function of the module core library currently being executed using the first module framework implementing function;
Copying and backing up data of the module core library using the second module framework implementing function;
Linking the new module core library after terminating the link of the module core library using the third module framework implementation function;
Recovering data copy and backup data of the new module core library using the fourth module framework implementation function; And
And processing the general work using the fifth module framework implementation function. ≪ Desc / Clms Page number 21 >

Images