KR20020087743A - Administraction method for derangement data base of a packet data serving node - Google Patents

Abstract

PURPOSE: A method of managing a failed database of a PDSN(Packet Data Serving Node) is provided to integrate distributed-failed database in an integrated failed database of the PDSN, in order to maintain consistency between each failed database, thereby efficiently managing database failures. CONSTITUTION: An NCP(Network Control Processor) reports periodic failure generation and cancellation states to a PCP(PSDN Control Processor). The PCP and a monitor report the periodic failure generation and cancellation states to a PDM(PDSN Manager). The PCP transmits a message of requesting consistency of failed databases to the NCP, and the PDM transmits a message of requesting consistency of failed databases to the PCP and the monitor. The NCP reports database to the PCP by the requested message, and the PCP and the monitor report database to the PDM.

Description

ADMINISTRACTION METHOD FOR DERANGEMENT DATA BASE OF A PACKET DATA SERVING NODE}

The present invention relates to a method of managing a failure management database. In particular, a distributed and managed failure database is integrated and managed in the integrated failure database of PDM to maintain consistency among each failure database to more effectively fail. To manage the failure database of PDNS

FIG. 1 is a hardware configuration diagram of a packet data serving node system, and as shown therein, a packet data serving node for selecting a path for accessing the internet at the request of a user and a base station. , PDSN) and PDMS 40 (PDSN Manager, PDM) for controlling the PDN 30.

The PSN 30 includes a connection unit 10 for detecting an Internet connection request and performing an operation for accessing the Internet, and a control unit 20 for controlling an operation of the connection unit 10.

In addition, the connection unit 10 includes a high-speed Internet connection 11 connected to the Internet for high-speed Internet access, a low-speed Internet connection 12 connected to the Internet for low-speed Internet access, and a base station connection 14 connected to the base station; It consists of a PPP (Point To Point Protocol, PPP) connection 14 for the Internet access of individual users.

The control unit 20 includes a PSDN control processor (PCP) 21 for controlling a plurality of boards used in the connection unit 10 and an NC 22 for controlling network settings connected to the connection unit. (Network Control Processor, NCP), and the monitoring unit 23 for monitoring the operating state of the PC 21 and NC 22.

In the PDNS system configured as described above, when the individual Internet user requests the Internet connection through the PPI connection unit 13 or the base station requests the Internet connection through the base station connection unit 14, the NCP 22 connects to the high-speed Internet connection unit. (11) and the network line of the low-speed Internet connection unit 12 is set. By the network setting of the NC 22, the PC 21 connects the base station and the personal Internet user to the Internet through the high speed Internet connection unit 11 and the low speed Internet connection unit 22. In addition, the monitoring unit 23 monitors the operating states of the PC 21 and NC 22 so that individual users and base stations can easily connect to and maintain the connection to the Internet.

In addition, the PC 21, NC 22, the monitoring unit 23 and the PD 40 is a PC 21, NC to manage the failure during the operation of the PD system (30) (22), the failure database of the monitoring unit 23 and PD 40 is included. Each fault database manages faults generated on each physical board.

Therefore, conventionally, when a failure occurs in the PDN system, the failure is distributed and managed in a failure database of each component.

However, in the conventional technology as described above, since the failure database of the PDNS system is distributed and managed, the management system of the failure database is complicated, and there is a problem in that it cannot maintain consistency with each individual failure database.

Accordingly, the present invention devised in view of the above problems provides a failure database management method of PDNS which operates the PDNS system smoothly by integrating the respective failure databases into PDMS to manage failures. There is a purpose.

1 is a hardware configuration diagram of the PDNS system.

Figure 2 is a block diagram showing the configuration of the present invention DS database.

Figure 3 is a signal flow diagram illustrating a failure database management method of the present invention PDNS.

*** Explanation of symbols for the main parts of the drawing ***

30, 70: PD 10, 50: connection

11, 51: high-speed Internet connection 12, 52: low-speed Internet connection

13, 53: PPI connection 14, 54: base station connection

20, 60: control unit 21, 61: PC

22, 62: NC 23, 63: monitoring unit

40, 80: PD90: Disability Integration Database

91: local database 92: link database

93: NC database 94: Monitoring unit database

In order to achieve the above object, the present invention provides a fault reporting step in which the NC reports the occurrence and release of cycle-by-cycle failures and the PD and the monitoring unit report the occurrence and release of cycle-by-cycle failures by PDs. A consistency request step of sending a request for coherence of the fault database to the NC and a message of requesting consistency of the fault database to the PC and the monitoring unit, and the NC by the request message of the consistency step. PPI reports the database as PPI, and the PPC and the monitoring unit is characterized in that the database reporting step of reporting the database to the PD.

Hereinafter, with reference to Figs. 2 and 3 attached to the operation and effect of the failure database management method of PDN according to the present invention.

FIG. 2 is a block diagram showing the configuration of the present invention's PD database, as shown in FIG. 70, which selects a path for accessing the Internet at the request of a user and a base station (Packet Data Serving Node (PDSN)). And a PD 80 for controlling the PD 70 (PDSN Manager, PDM).

The PSN 70 is composed of a connection unit 50 for detecting an Internet connection request and performing an operation for accessing the Internet, and a control unit 60 for controlling the operation of the connection unit 50.

In addition, the connection unit 50 includes a high speed internet connection unit 51 connected to the Internet for high speed internet access, a low speed internet connection unit 52 connected to the internet for low speed internet access, a base station connection unit 54 connected to a base station, It consists of a PPP (Point To Point Protocol, PPP) connection portion 53 for the Internet access of the individual user.

The controller 60 is a PS61 (PSDN Control Processor, PCP) for controlling a plurality of boards used in the connection unit 50, and the NC for controlling the network settings connected to the connection unit 50 Network 62 (Network Control Processor, NCP), and the monitoring unit 63 for monitoring the operating state of the PC 61 and NC 62.

In addition, the PD 80 is configured by adding a failure integrated database 90 for managing the failure of the PD 70 to the conventional PD 80.

In addition, the failure integration database 90 includes a local database 91 for managing failures related to boards managed inside the PC, a link database 92 for managing failures related to connection with external systems, The monitoring unit database 94 for managing the failure of the monitoring unit 63 and the NC database 62 for managing the failure of the switching network of the DS 70 networking board in the NC 62.

In addition, the PC 61, NC 62, the monitoring unit 63 and the PD 80 is a PC 61, NC 62 for managing the failure occurred during the operation of the PD system , The failure database of the monitoring unit 63 and the PD 80, and if the number of failures managed in the integrated failure database 90 is too large to maintain the consistency of each failure database Since the resource and time must be consumed, the total number of failures managed by the failure integration database 90 is limited to about 200 to 300.

FIG. 3 is a signal flow diagram illustrating a failure database management method of the present invention. As illustrated in FIG. 3, the NC 62 and the PC 61 are integrated to manage the failure database of the NC 62. The first step for maintaining consistency of the failure database to manage each, and the failure data of the PD 61 and the failure integrated data of the PD 80 in order to integrate management of the failure database of the PC 61 A second step for maintaining the consistency of the base 90, and the failure database of the monitoring unit 63 and the failure integration database of the PD 80 (integrated management of the failure database of the monitoring unit 63) 90), the third step is to maintain consistency.

The first step is the fourth step in which the NC 62 reports the occurrence and release of the failure by cycle to the PC 61, and the message to the PC 61 to maintain the failure database consistency at a predetermined cycle The fifth step of transmitting to the NC and the sixth step of receiving the message of the PC 61, the 62 is a sixth step of reporting the failure database to the PC 61.

In addition, the second step is a seventh step that the PC 61 reports the occurrence and release of the failure per cycle to the PD 80, and the message for the PD 80 to maintain the failure database at regular intervals The eighth step of transmitting to the PC 61 and the ninth step of receiving the message of the PD 80 and the ninth step of reporting the failure database to the PD 80. .

In addition, the third step is a tenth step in which the monitoring unit 63 reports the occurrence and release of the failure per cycle to the PD 80, and the message for the PD 80 to maintain the failure database in a certain cycle The eleventh step of transmitting to the monitoring unit 63 and the monitoring unit 63 receiving the message of the PD 80 is the twelfth step of reporting the failure database to the PD 80. .

In the failure database management method configured as described above, since NCPC is not directly connected to PDMS, it operates to maintain consistency between NC failure database and PDM integrated failure database through PD. .

As described in detail above, the present invention integrates and manages the distributed and managed fault databases in PD, so that failures can be more effectively managed by maintaining consistency among the fault databases.

Claims (5)

The failure reporting step in which NCCP reports the occurrence and release of cycle-by-cycle failures by PPI and the PD and monitoring unit reports failure and release of cycle-by-cycle failures in PDM, and the request for consistency of NCCP failure database. A consistency request step of sending a message and requesting the consistency of the fault database to the PC and the monitoring unit; and the NC reports the database as a PCP by the request message of the consistency step, and the PC And the monitoring unit comprises a database reporting step of reporting a database to the PD. 2. The method of claim 1, wherein the PD is integrated management of all the failures generated during the operation of the PD system. The method of claim 1, wherein the NC manages a failure that occurs when performing an operation of controlling a network configuration. The method of claim 1, wherein the PC manages a failure occurring when performing an operation of connecting with an external system. 2. The method of claim 1, wherein the monitoring unit manages a failure occurring during the operation of the NC and the PC. 3.