KR100258077B1 - Subscriber Management Method using Common Management Interface Protocol in Distributed Access Network Operation and Management System - Google Patents

Abstract

The present invention relates to a subscriber management method through an agent of each DANS using common management interface protocol (CMIP) communication in a distributed subscriber access network (DANS) management manager system (DOMS). The present invention provides a method for integrating and managing a subscriber from a service provided through an asynchronous subscriber access network (DANS). To this end, the present invention is based on the MIB, and delivers the registration function of the operator to the service subscriber in the DOMS and subscriber management events generated in each DANS through the agent through the interface with the agent using the CMIP. Accept and process it.

Description

Subscriber Management Method using Common Management Interface Protocol in Distributed Access Network Operation and Management System

The present invention provides a common management interface protocol (CMIP) in a DANS Operation and Management System (hereinafter referred to as DOMS) of a Distributed Access Node System (hereinafter referred to as DANS). The present invention relates to a subscriber management method through an agent of each DANS using communication.

Subscriber management in the existing distributed access network is managed through the local operation monitor of each distributed head node system, not managed by the network management system. Accordingly, in the related art, there is no method of remotely verifying service subscriber information on a distributed subscriber access network. Therefore, there is a need for a function of managing integrated subscribers by a management system.

Accordingly, an aspect of the present invention is to provide a method for an operator to comprehensively manage a subscriber of a service provided through an asynchronous subscriber access network (DANS) that is currently distributed and installed geographically.

1 is a configuration diagram of a connection between a distributed access network management system (DOMS) and a head node system of a distributed access network managed by a distributed access network (DANS).

2 is a software configuration diagram of DOMS to which subscriber management function is added;

3 is an overall subscriber management flow diagram in the DOMS according to the present invention;

4 is a detailed flowchart for collecting and storing initial subscriber information in FIG. 3;

5A to 5C are subscriber management flowcharts requested by an operator in FIG. 3;

6A and 6B are process flow diagrams for a subscriber management event of an agent in FIG.

The present invention is based on a standard Management Information Base (hereinafter referred to as MIB) and registers an operator to a service subscriber in DOMS through an interface with an agent using a common management interface protocol (hereinafter referred to as CMIP). Function and receives subscriber management event generated in each DANS through agent and processes it.

Hereinafter, with reference to the accompanying drawings will be described in detail the present invention.

FIG. 1 is a diagram illustrating a connection between a distributed access network operation and management system (DOMS) 102 and a managed access system (HN) 105 of a distributed access network (DANS) 104.

DOMS 102 is connected to up to eight DANS 104 and Ethernet 103 to manage subscribers through network management CMIP communication with TGB (Telecommunication Management Network Agent Block) 106 inside head node 105 of DANS 102. Perform the function. The TAGB 106 is located at the header node 105 of the DANS 102 to perform the network management agent function of the DOMS 102 via the Ethernet 103 and to communicate with the system software 107 to perform management functions. In addition, the network management agent functions from various events occurring in the system, and delivers necessary messages to the DOMS 102 through the Ethernet 103 as event messages.

2 is a DOMS software structure configured by adding a subscriber management function.

The X / Motif (X Window System / OSF Motif; where Motif is a trademark.) Unit 201 is a library for a graphical user interface between the DOMS and the operator.

The user interface function block (UIFB) 204 performs an interface function with an operator for subscriber management using the X / Motif library.

The Management Processing Function Block (MPFB) 206 is a functional unit that performs subscriber management functions. The Agent Interface Function Block (AIFB) 208 performs an interface function with the TAGB 106, which is an agent function unit, and uses an XOM / XMP API (X / Open OSI-Abstract-Data) for CMIP communication according to a standard MIB. Manipulation (XOM) / X / Open Management Protocols (XMP) Application Programming Interface, 210). The protocol stack unit 212 delivers the network management message to the corresponding TAGB unit and performs a function of receiving the received message.

3 is a general flow diagram for performing subscriber management in DOMS.

DOMS 102 collects and stores 301 all subscriber information registered in each TAGB 106 before performing functions related to subscriber management from operator and communication management network agent block (TAGB) 106. Perform an initialization function.

After performing the initialization function, the management system receives an event from the operator or the TAGB (302) and analyzes the operator request again (305) when the event is requested by the operator (303, 304). As a result of this analysis, when it is a message requesting the termination of the subscriber management function (306), when the operation of this management system is terminated (307), and when the subscriber management function is requested (308), the operator request processing function (309). Do this. In addition, in case of an event from the TAGB 106 (310), the TAGB event processing function 311 is performed.

4A and 4B are flowcharts illustrating initial subscriber information collection and storage of the DOMS in FIG. 3.

The DOMS 102 first transmits a message requesting all registered subscriber information except for network to network interface (NNI) information to each TAGB 106 (401), and transmits each subscriber information except the NNI information to the TAGB 106. Receive from 402. It checks (403) whether the received message is the message requested by DOMS 102, and waits for receipt of subscriber information if it is not valid (404). If the message is valid, the received information is analyzed (406) and the search result is checked. If the search fails, an error message is output (409) and the subscriber management function is terminated. If the search is successful (410) and one of the plurality of retrieved subscriber entries (413), the subscriber information is stored and the usage state for that information is set to " 0 ". In the case of one of the plurality of subscribers (416, 417) waits for the reception of subscriber information. When all the subscriber information reception ends (402 to 417), a request for retrieving NNI information of all stored subscriber information is transmitted (419) and the retrieved NNI information is received (420). If the received message is valid (421) and is invalid (422), it waits for receiving NNI information again. If the message is valid (423), the NNI information search result is analyzed (424, 425) from the received message. If the search fails (426), an error message is output (427) and the subscriber management function is terminated. If the search is successful (428), if the received message is a message indicating the end of the NNI information search (429, 430), if this initialization function is terminated and if it is not the end of the NNI information search (431), whether the subscriber information for the NNI information exists. If it is confirmed (432) and present (434), the corresponding information is stored (435) and the corresponding information flag is set to '1'. When there is a plurality of retrieved NNI information (437, 438), the NNI information is awaited to be received.

5A through 5C are subscriber management flowcharts requested by an operator in the DOMS of FIG. 3.

First, referring to FIG. 5A, when the operator requests a search by checking the operator's request (501,502), the subscriber information search function 503 to 505 is performed. The subscriber information for the requested item is retrieved (503) and output (504) to the operator, the search flag is set to '1' (505), and the subscriber management operator request processing function is terminated. At this time, the search flag means that the operator currently opens a table for searching subscriber information.

If the operator requests the end of the search (507,508), the search flag is set to '0' and the subscriber management operator request processing function ends.

When the operator requests the subscriber state change (511,512), the subscriber management state change function (513 to 525) is performed. First, a change request state is analyzed 513, a state change request is transmitted 514 to TAGB, and a change result is received 515 from the TAGB. If the received message is valid (516) and invalid (517), an error message is output (518) to the operator and the operator request processing function ends. If the received message is valid (516, 519), the result of the state change of the received message is analyzed, and if the state change in the TAGB is failed (520, 521), the failure and the cause of the failure are output to the operator (518), and the operator request processing function ends. . If the state change is successful (520, 523), the changed state information in the stored subscriber information is corrected and stored (524), the result is output to the operator (525), and the operator request processing function ends.

Subsequently to FIG. 5A and with reference to FIG. 5B, when the operator requests new subscriber registration (526, 527), the subscriber registration functions 528 ˜ 555 are performed. First, a new subscriber information input by the operator is analyzed (528), a message for requesting generation of NNI information is transmitted (529) to the corresponding TAGB (529), and a generation result is received (530). If the received message is valid (531) and invalid (532), it waits for receiving the NNI generation result from TAGB again. If the received message is valid (534), the generation result is checked from the received message (535), and if it is a generation failure (536), a new subscriber registration failure message and cause of failure are output to the operator (537), and the operator request processing function is performed. Quit. If the result of generation is successful (535,538), the generated NNI information is stored (539), the subscriber information flag is set to '0' (540), and a message requesting registration of subscriber information is sent to TAGB (541). Receive 542. If the received message is valid (543) and invalid (544), it waits again to receive a subscriber registration result. If the received message is valid (543, 546), the registration result of the received message is checked (547). If the registration fails (548), a failure message and a reason for the failure are output to the operator (549), and the stored NNI information is deleted. In operation 550, the NNI information deletion request message is transmitted to the TAGB to delete the NNI information generated by the TAGB (551). If the registration is successful (547,552), the subscriber information flag is set to '1' (553), the subscriber information requested for registration is stored (554), the registration result is output to the operator (555), and the operator request processing function is terminated. .

Next, referring to FIG. 5B, referring to FIG. 5C, when the operator requests deletion of a subscriber that is already registered (556, 557), the subscriber deletion function 558 to 582 may be performed. First, the deletion request of the operator is analyzed to identify the subscriber information identifier to be deleted (558). It checks whether the subscriber exists and if it does not exist (559,560), outputs an error message (561) and terminates the operator request processing function. If the subscriber exists (559, 562), the subscriber deletion request is transmitted (563) to the TAGB and receives the deletion result (564). If the received message is valid (565) and invalid (567) waits for reception of the subscriber information deletion result. If the message is valid (567), the deletion result is analyzed and if the deletion is not successful (568, 569) and outputs a failure message and the reason for the failure (570) to the operator and terminates the operator request processing function. If the deletion result is successful (571), the NNI information deletion request for the corresponding subscriber is transmitted (572) to the TAGB and receives the deletion result (573). If the received message is valid (574) and invalid (575), the deletion result awaits reception. If the received message is valid (574, 576) and the deletion result is analyzed (577, 578) if the deletion is failed (577, 578), the subscriber information deletion failure message and the cause of the failure (579) to the operator and the operator request processing function is terminated. If the deletion of the subscriber information is successful (577, 580), the deletion of the subscriber information (581), outputs the deletion result (582) to the operator and terminates the operator request processing function. If the operator's request cannot be confirmed (583), an error message is output (584) and the operator request processing function ends.

6A and 6B are software flow diagrams of DOMS for subscriber management events of agents in FIG.

First, referring to FIG. 6A, when the subscriber management event delivered from the TAGB 106 is analyzed and the event is analyzed to notify registration of subscriber information (601, 602), the subscriber information registration event processing function 603 to 631. ). First, a subscriber information entry is generated from the subscriber registration event (603), the information flag is set to '0' (604), the corresponding subscriber information request is sent (605) to TAGB, and the search result is received (606). The received message is analyzed (607) and invalid (608) and awaits reception of subscriber information. If it is valid (607, 609), the received information is analyzed and the search result is analyzed (610). If the search fails (612), the subscriber information entry is deleted (613) and the TAGB event processing function is terminated. If the search result is successful (614), the subscriber information is stored, the NNI information search request is transmitted (616) to the TAGB, and the search result is received (617). The received message is analyzed (618) and waits for NNI information to be received if it is invalid (619). If the received message is valid (620), the received information is analyzed (621). If the search result is unsuccessful (622, 623), the subscriber information entry is deleted (624) and the TAGB event processing function is terminated. If the search result is successful (625), the NNI information is stored (626), the information flag is set to '1' (627), and if the search flag is not set to '1', the TAGB event processing function is terminated. When the search flag is set to '1' (630), the subscriber registration fact and subscriber information are output to the operator 631 and the TAGB event processing function is terminated.

Next, referring to FIG. 6A, referring to FIG. 6B, when the event transmitted from the TAGB 106 is the subscriber information state change event (632,633), the change state information is analyzed (634) and the current state. And if it is the same (636), the TAGB event processing function is terminated. If it is different from the current state (637), the state information is modified and stored in the subscriber information (638), the search flag is checked (639), and the TAGB event processing function ends if the search flag is not set to '1'. If the search flag is set to '1', the change status is output to the operator and the TAGB event processing function is terminated.

If the event transmitted from the TAGB is a subscriber information deletion event (644, 645), the deleted subscriber information identifier is analyzed (646), the corresponding subscriber information is retrieved (647), and the existence of the corresponding subscriber information is checked (648). Otherwise (649), the TAGB event processing function ends. If the subscriber information exists (650) and deletes the subscriber information (651), if the search flag is not set to '1' (653), the TAGB event processing function is terminated. If the search flag is set to '1' (654), the subscriber information is output to the operator and the TAGB event processing function ends.

As described above, the present invention enables the management of the subscriber information of the DANS at a remote location using the CMIP for the service subscriber information on the distributed subscriber access network.

Claims (4)

A communications management network agent block (TAGB) 106 communicating with the system software 107 located at the head node 105 in the distributed access networks 104 connected to the Ethernet 103 is connected to the network management common management interface protocol (CMIP). A user interface function block (UIFB) 204 using the X / Motif library, a management processing function block (MPFB) 206 connected to the UIFB 204 to manage subscribers, and the like to manage subscribers through communication; An agent interface function block (AIFB) connected to the MPFB 206 to perform an interface function with the TAGB 106 and to perform CMIP communication according to a standard management information base (MIB) through the XOM / XMP API 210 unit. A method for managing subscribers by a distributed access network management and management system (DOMS) 102 comprising: 208, A first step of collecting, storing, and initializing all subscriber information registered in each TAGB 106; A second step of receiving and analyzing an event requested by an operator after the initialization and managing the subscriber if the request is a subscriber management request; And After the initialization, a subscriber management method using a common management interface protocol in a distributed access network operation and management system, characterized in that the third process of receiving a subscriber management event from the TAGB 106 to process the TAGB event. . The method of claim 1, wherein the first process comprises: If the DOMS 102 requests all the subscriber information from each TAGB 106 and the subscriber information is valid except for the NNI (network interface) information received from the TAGB 106, the DOMS 102 is one of the retrieved subscriber entries. A first step of storing the subscriber information and storing all the subscriber information until all of the subscriber information is received; If the DOMS 102 requests the TAGB to retrieve the NNI information of all stored subscriber information and the NNI information received therefrom is valid, the DOMS 102 stores the retrieved NNI information if it is not the last time and the user information exists, and then stores the NNI information. Subscriber management method using a common management interface protocol in a distributed access network operation and management system, characterized in that it comprises a second step of receiving until a certain number of retrieved NNI information is terminated when the number. The method of claim 1, wherein the second process comprises: A subscriber information retrieval process of retrieving subscriber information and outputting it to the operator when the operator requests a retrieval; A subscriber state change process of changing a subscriber management state when an operator requests a subscriber state change without requiring a search; A subscriber registration process of registering the subscriber information with the TAGB when an operator requests a new subscriber registration without requiring a change of subscriber status; And Subscriber using a common management interface protocol in a distributed access network operation and management system, characterized in that the subscriber deletion process for deleting the subscriber information if the operator does not require registration and delete the subscriber already registered in TAGB. How to manage. The method of claim 1, wherein the third process comprises: A registration event processing step of analyzing a subscriber management event received from the TAGB 106 and processing a subscriber information registration event when the event informs registration of subscriber information; A change event processing step of changing the state of the subscriber information by analyzing the change state information and modifying and storing the state information in the subscriber information when the subscriber information state change event is received instead of the registration event; And The common management interface in the distributed access network operation and management system, characterized in that the deletion event processing process of deleting the subscriber information by analyzing the deleted subscriber information identifier when the subscriber information deletion event is received instead of the change event. Subscriber management method using protocol.

Images