KR0132955B1 - Method of mutual back-up duplicaion in local management - Google Patents

Abstract

The present invention relates to a dual backup duplication method of a local management apparatus of a communication processing system for managing network components reliably and efficiently without additional installation of a system in connection with establishing a domestic communication service network. Monitoring each other through a normal operation step in which real-time data backup occurs to match data between systems M-OAM A and B; When the take-over is requested to the counterpart M-OAM based on the M-OAM self-diagnosis result, the counterpart M-OAM process is activated when the counterpart M-OAM is detected through the packet network and the operator's request is started. A take-over step of initializing an X.25 address change of the M-OAM in ISAP, and then re-adjusting the GDS processing capacity to a backup step; A backup operation step of recording and storing all activities related to both M-OAMs by simultaneously processing the M-OAM a function of one M-OAM system and the surrogate M-OAM b function of an opponent; The recovered M-OAM system receives information recorded and stored from the partner's surrogate M-OAM, matches the data in its M-OAM with the surrogate M-OAM, and backs it up to the surrogate M-OAM. After the retake-over of the M-OAM function to recover the M-OAM function is characterized in that it comprises a fault recovery step of entering a normal operation state.

Description

Redundancy method of mutual backup of local management devices of communication processing system

1 is an overall configuration diagram of an information and communication service network,

2 is a redundant configuration of mutual backup of the local network management device (M-OAM) according to the present invention,

3 is a flow chart of the mutual backup redundancy method,

Figure 4a is a signal sequence in normal operation,

4b shows the sequence of redundant take-over and backup operation signals

4c is an M-OAM recovery operation signal sequence.

The present invention provides an information communication service and mutually manages a local management device of a communication processing system for recovering a failure in a network management device managing various and complex network elements configuring a communication processing network. A backup duplication method.

Conventionally, in order to improve the reliability of the network management system for managing the network devices, the network management device has been implemented by the system redundancy method, but the system redundancy method makes two identical systems, one performs normal service operation and one keeps waiting. Because only about 50% of system resources are used, 50% of system resource loss is a big problem.

The present invention has been made to solve the problems of the prior art, the local management of the communication processing system to manage the network configuration devices reliably and efficiently without additional installation of the system in connection with the domestic communication service network construction The purpose of the present invention is to provide a device backup backup redundancy method.

In order to achieve the above object, the present invention is a normal operation step of monitoring each other through a packet network, the backup of the real-time data to match the data between the system M-OAM A, B occurs; When the take-over is requested to the counterpart M-OAM based on the M-OAM self-diagnosis result, the counterpart M-OAM process operating in the standby mode is detected when the counterpart M-OAM failure is detected through the packet network and at the request of the operator. A take-over step that is activated and transitions to a backup step after initialization of an X.25 address change of an M-OAM in ISAP, readjustment of GDS processing capability, and the like; A backup operation step of recording and storing all activities related to both M-OAMs by simultaneously processing the M-OAM a function of one M-OAM system and the surrogate M-OAM b function of an opponent; The recovered M-OAM system receives the recorded and archived information from the partner's surrogate M-OAM, matches the data in its M-OAM with the surrogate M-OAM, and backs it up to the surrogate M-OAM. After the retake-over of the M-OAM function to recover the M-OAM function is characterized in that it comprises a fault recovery step of entering a normal operation state.

Hereinafter, the present invention will be described in detail with reference to FIGS. 1 to 4.

1 is an overall configuration diagram of an information communication service network, in which NE1 to NEn use a communication terminal to enable a user to access a service provided to an information providing computer of NEn + 1 to NEm connected to an X.25 packet network. It is a processing device. The central network management device (C-OAM) and the local network management devices (M-OAM1 to M-OAMAk) are network management in charge of maintenance and operation management of communication processing devices and information providing computers of ISAP (NE1 to NEn). Device computers.

M-OAM consists of subscriber matching device (ISAP) and information guidance system. Local network management devices (M-OAM1 to k) are in charge of local NEs according to performance and capacity, and C-OAM network management device As a center for integrated management of multiple M-OAM devices, it has a hierarchical management structure.

FIG. 2 is a redundant backup redundant configuration of a local network management apparatus (M-OAM) according to the present invention. As shown in FIG. 2, during an M-OAM failure, another M-OAM computer fails during a computer repair time (average 3 hours). It replaces the service function necessary for regional management of the area, and since it is the original method after repair and repair, it is not necessary to prepare two identical systems, and it can use the system resources 100% because it acts as the function of other systems as needed. Do.

At this time, the operation of the information service system (GDS) is reduced from 98 to 48 ports, and the remaining CPU resources are used to back up the function of the failed M-OAM. The configuration method is to connect a single M-OAM by region to a backup redundancy system as a PSDN, and to have its own M-OAM process and its counterpart M-OAM process mixed in the M-OAM computer. Install the X-terminal (one and the other) of the formula, and change the M-OAM address in NE (ISAP) to a substitute M-OAM address when M-OAM take-over due to the failure of the counterpart M-OAM. Configure the system to report data.

In normal operation, each time data (User Profile) changes, mutual data backup (distributed transaction) is executed. When recovering after troubleshooting, perform M-OAM function by backing up changed data (billing data, user profile, GDS data) from M-OAM.

3 is a flow chart of a mutual backup duplication method, which is composed of four steps of normal operation 10, take over 20, backup operation 30, and recovery 40 as shown in case of a relative M-OAM failure. The backup process M-OAM b backs up the partner M-OAM state / shape data and operates on behalf of it. At this time, it reduces its GDS service processing capacity and uses the remaining CPU resources to back up the function of the failed M-OAM. This is the normal operation after receiving the status / shape data from the surrogate M-OAM b process after recovering the faulty system. The fault detection and transfer time is somewhat slow, and each data required by each application is always passed to the counterpart M-OAM. So that both M-OAMs have the same data.

The steps are as follows.

1) Normal operation phase

Each packet is monitored over the network and a backup of real-time data (subscriber profile, system configuration / status data and other GDS-related data) occurs to match data between system M-OAM A and B systems. At this stage, the counterpart M-OAM application processor mounted in the M-OAM operates in a sleep mode to maintain take-over capability of the counterpart M-OAM in a short time.

2) take-over phase

When the take-over is requested to the counterpart M-OAM based on the M-OAM self-diagnosis result, the take-over occurs when the counterpart M-OAM is detected through the packet network and at the request of the operator. At this time, the counterpart M-OAM process, which was operating in the standby mode, is started to initialize the X.25 address change of the M-OAM in ISAP, and the GDS processing capacity is readjusted, and then the backup step is performed.

3) Backup operation step

A M-OAM system processes its own M-OAM a function and its counterpart M-OAM b function at the same time, and records and stores all activities related to both M-OAMs. At this stage, the operation of the GDS is reduced.

4) Troubleshooting Step

The recovered M-OAM system receives the recorded and stored information from the partner M-OAM and matches the data in its M-OAM with the partner M-OAM. The M-OAM function is retaken to recover the M-OAM function backed up to the opponent M-OAM. Then it enters the normal operation state.

4A to 4C are M-OAM sequence charts. In the normal operation, the signal sequence is as shown in FIG. 4A. Each M-OAM manages an assigned NE (ISAP), and periodically the relative M-OAM. Check if this is normal. At this time, the counterpart M-OAM process operates in the sleep mode. The channel (X.25) connected to the PSDN network periodically sends and receives messages to check whether the operation is normal or abnormal, and backs up each other's user profile.

Figure 4b shows the sequence of redundant take-over and backup operation signals from failure. In the redundant take-over and backup operation, a procedure indicating the operation performance when the relative M-OAM is broken is as follows.

Relative local M-OAM process transitions from sleep mode to backup mode, readjusts GDS processing capacity and requests NEs (ISAPs) to change address from relative M-OAM address to relative M-OAM process and send shape / status data. And perform proxy work based on the data. Your M-OAM process is in Normal mode, and the GDS switches to Reduced mode. At this time, the counterpart M-OAM process switches to backup mode and operates in backup mode. The proxy execution result is kept in a log file, and the log file is transferred to the counterpart M-OAM upon recovery.

4C shows an M-OAM recovery operation signal sequence. During system recovery, a message is periodically sent to the X.25 channel to check whether the counterpart M-OAM has been restored as a normal recovery after normal system repair. When a response (ACK) is received from the counterpart M-OAM after troubleshooting, the substitute M-OAM process transmits the information stored in the log file to the counterpart M-OAM and operates by switching to sleep mode. The state is switched. The recovered counterpart M-OAM continues to perform the M-OAM function based on the log file information and requests the subordinate ISAPs to change the address from the surrogate M-OAM process address to the recovering M-OAM address and to request the status information. And perform normal M-OAM function.

The present invention made as described above reliably network management by duplication of the network management device when a failure occurs in the network management device that provides information communication services and manages a variety of complex network configuration devices constituting a communication processing network, Efficient operation management

Claims (1)

A normal operation step of monitoring each other through a packet network and generating a backup of real-time data to match data between systems M-OAM A and B; When the take-over is requested to the counterpart M-OAM based on the M-OAM self-diagnosis result, the counterpart M-OAM process operating in the standby mode is detected when the counterpart M-OAM failure is detected through the packet network and at the request of the operator. A take-over step 20, which is activated and transitions to a backup step after initialization of an X.25 address change of an M-OAM in ISAP, readjustment of GDS processing capability, and the like; A backup operation step 30 of simultaneously processing one M-OAM system's own M-OAM a function and the other's surrogate M-OAM b function and recording and storing all M-OAM related activities; The recovered M-OAM system receives information recorded and stored from the partner's surrogate M-OAM, matches the data in its M-OAM with the surrogate M-OAM, and backs it up to the surrogate M-OAM. Mutual backup of the local management apparatus of the communication processing system comprising a failure recovery step 40 of performing a retake-over of the M-OAM function and then entering a normal operation state to recover the M-OAM function of the system. Redundancy method.