KR100205032B1 - How to manage subordinate network history data of broadband line distribution system - Google Patents

Abstract

The present invention relates to a sub-network history of a broadband line distribution system designed and implemented according to a relational data model in order to more quickly and accurately manage operation and maintenance data of network management systems connected to a sub-network of a broadband line distribution system (BDCS) The physical configuration of the system to which the subnetwork history data management method is applied is composed of a broadband line distribution system and subordinate systems connected thereto, and a logical configuration for managing the subordinate network history data management method is to manage subordinate network data Agents.

In the subnetwork history data management method, the network management history data transmitted between the manager and the agent is stored in the database defined according to the relational model, and can be processed as operation information to provide various information to the system operator.

The management data of the database is managed according to the recommendation of ITU G. 784 for at least 10 days. The management data records the state of the system generated based on the time that data is generated and stored in the database, Through the management, the operation status of the devices connected to the network and the history of the failure can be grasped through this database regardless of the installed positions of the systems. Thus, the present invention provides a more efficient and economical function for network management of a broadband line distribution system.

Description

How to manage subordinate network data of broadband line distribution system

The present invention relates to a sub-network history of a broadband line distribution system designed and implemented according to a relational data model in order to more quickly and accurately manage operation and maintenance data of network management systems connected to a sub-network of a broadband line distribution system (BDCS) The physical configuration of the system to which the subordinate network history data management method is applied is composed of a broadband line distribution system and subordinate systems connected thereto, and a logical configuration for managing the subordinate network history data management system Which are made up of agents.

Digital Cross Connection (DXC), which was manually handled in the existing asynchronous transmission network, is divided into operation and management information for each system because the dependent systems connected to the network are dispersed due to the characteristics of DXC, In the event of a system failure, it takes a long time to recover.

In addition, since accurate management of the distributed systems and management of the management information are not performed, it is difficult to accurately manage and manage the dependent systems in terms of the operation of managing the DXC, Recovery in the event of a failure is very difficult.

In addition, since the control information in which the configuration change of the DXC is performed by the complicated network configuration in the DXC operation is maintained by the operator's record, accurate information maintenance and management are not performed and it is difficult to use it.

In order to compensate for the above disadvantages, the present invention provides a method of managing subordinate network history data of a broadband line distribution system designed and implemented according to a relational data model capable of managing operation and maintenance data of a subordinate network, In order to manage the integrated data, operation and management information of the distributed systems is automatically collected through the network management function, and the collected data is integrated and managed in the database, thereby enabling quick and accurate data management.

The data stored in the database can be stored based on the history of the operation and management of the system connected to the network through the operator of the DXC, and can be searched by system or type of management information, By using such a database management system, it is possible to manage a large amount of information and it is possible to easily manage a large amount of information by integrally managing 14 management and management information based on a 2.5 Gb / s transmission device. In addition, DXC operation information retrieval also provides convenient operation through various functions and integrated management through the color user interface screen.

FIG. 1 is a configuration diagram of a broadband line distribution system subordinate network system according to an embodiment of the present invention,

FIG. 2 is a message processing path diagram according to an embodiment of the present invention,

FIG. 3 is a flowchart of network management data storage according to an embodiment of the present invention,

4 is a flowchart of operational information processing according to an embodiment of the present invention.

DESCRIPTION OF THE REFERENCE NUMERALS

1: Device Management Subsystem 2: DXC Configuration Management Unit

3: User interface management unit 4: Agent

5: System operation management section 6: Manager

7: Database management unit 8: Data storage unit

9: Slave network configuration diagram

A subnetwork history data management method of a broadband line distribution system designed and implemented according to the relational data model provided by the present invention includes a first message reception stage for receiving a message at an agent of a transmission system connected to a subnetwork, Analyzing, processing and storing a message according to a message identifier, and storing the received message in a message storage step; and storing the message stored in the message storage step To the operator.

A broadband line distribution system that handles a large capacity line distribution function can configure a subordinate network with a synchronous transmission device of 155 Mb / s, 622 Mb / s or 2.5 Gb / s, and the subordinate network management of a broadband line distribution system Each system is managed through agents that perform network management functions and managers that manage the edge agents. The manager performs the control commands necessary for the operation and management of each system connected to the subordinate network. The agent reports the response to the control command transmitted from the manager and the operation information, thereby controlling operation of all systems connected to the subordinate network And management functions.

A system capacity connected to a sub-network of a broadband line distribution system can be connected to a maximum of 15 inter-station transmission systems based on a 2.5 Gb / s system, and the connection type of the network is composed of a terminal type or annular type. A system connected to a subordinate network may be composed of systems constituting a subordinate subordinate network again.

The subordinate network history data management system of the broadband line distribution system according to the relational data model of the present invention for managing the history data of the system as described above can be used for managing / And a data storage unit for storing network management data processed by the data management block.

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

2 is a message processing path diagram according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a network management according to an exemplary embodiment of the present invention. Referring to FIG. 1, there is shown a network configuration diagram of a broadband line distribution system according to an exemplary embodiment of the present invention. FIG. 4 is a flowchart of operational information processing according to an embodiment of the present invention. FIG. 1, the broadband line distribution system according to the present invention is comprised of a device management subsystem 1 that processes operation and management functions and processes subordinate network management functions, and an existing subordinate network diagram 9 .

The device management subsystem 1 includes a system operation management block 5 (SOM) dedicated to system operation management and a DXC configuration management block (DCM) 2), an agent (MN) 3 for connecting the system and the user, an agent (MN) 3 for managing the network of the broadband digital cross-connect system (BDCS) 4), a manager 6 for managing BDCS subordinate networks, a database management block (DBM: DataBaseManangement) 7 for managing BDCS system operation / maintenance data and subordinate network data, And a network management database (NETDB) 8 for storing network management data processed by the DBM 7.

In the existing subordinate network configuration diagram (9), the relationship between the manager (6) that supervises the subordinate network management and the system connected to the subordinate network is shown. In the network connection form, each route is linearly or annularly connected, The connected system may be a 2.5Gb / s transmission system 10, a 622Mb / s transmission system 11 or a 155Mb / s transmission system 12, and the annularly connected system may also be a 2.5Gb / s transmission system 13), a 622 Mb / s transmission system 14 or a 155 Mb / s transmission system 15 can be configured.

The network management function of the systems connected to the subordinate network 9 comprises an agent 100 dedicated to transferring information to the manager 6 through a message and an MIB 200 managing data of the agent.

In this network management environment, the subordinate network management history data management method of the present invention is a method of more efficiently managing the operation and control data collected through the manager 6 and the agent 100, Storage, and user interface of the user interface. The information storage function collects, analyzes, processes and stores information of systems connected to the subnetwork, and provides the information stored by the information function to the operator Information output function.

The information storage function transmits the control command requested by the manager 6 to the system connected to the subnetwork, and the processed result is transmitted to the DBM (7) via the manager (6) And the operation data reported from the connected system is stored in the DBM 7 via the manager 6.

In this case, the data for storing the data is transmitted through the message queue by composing the controlled and modified data into the agreed type message between the functional blocks, and the message delivered to the DBM (7) And is stored in the NETDB 8 after being converted into data that can be stored in the base.

The information output function provides various information to the operator through the screen of the color user interface.

2, the network management data generated from the transmission system connected to the subnetwork is reported to the manager 18 by the agents 15 and 16 of each system and transmitted to the network 18 via the SMC 17, (20) module of the DBM (19) that processes the management data.

The received message is classified into a performance report message (pm), a failure occurrence message (am), and a configuration change message (cm) according to the identifier msg_id of the message in the msg analysis module 21, ) Module, the failure occurrence message is transmitted to the fault occurrence processing module 23, the configuration change message is transmitted to the configuration change processing module 24, converted into respective data, and stored in the database in the query language conversion module 25 . The converted query term is stored in the NETDB 26, which is a network management data storage unit.

Referring to FIG. 3, a message conversion flow step in which a performance report message, a failure occurrence message, and a configuration change message are converted into data and stored is described below.

The information storage function firstly receives a message for receiving a message from a subordinate network system, and the message received in the message reception step 27 is an operation data message of a broadband line distribution system or a system connected to a subordinate network (28) whether the message is a network management message transmitted from the agent.

If the result of the network management message check (28) is an operation data message of the broadband line distribution system, it is transferred to the system operation message processing module (29). If the network management message is a network management message, (30) to generate system unique number data.

After the system identification step 30, it is checked whether a message identifier (msg-id) exists (31). If the message identifier is not found in the message identifier confirmation step 31, the error processing module 32 sends it. If the message identifier is present in the message identifier checking step 31, it is confirmed whether the message identifier is a performance report message (Pm) (33). If the message identifier is Yes, the message identifier is transmitted to the performance report message processing module 34, (35).

If the result is NO in step 33, it is checked whether the message identifier is am (fault occurrence message). If the result is YES, it is transmitted to the fault occurrence message processing module 37 And generates (38) failure occurrence data.

If the result is NO in step 36, it is checked whether the message identifier is cm (configuration change message). If the result is YES, the message is transmitted to the configuration change message processing module 40 (41) the configuration change data.

If the result is NO at the step 39 to confirm whether the identifier is cm, the process proceeds to the next step, the query term conversion step 42.

The data (35, 38, 41) generated in each message processing module is converted into a recognizable query term that is a database management system in the query term conversion module 42 and is stored in a database table which is the database storage section 43.

The process of converting the data stored in the database into the operational information, that is, the information output function will be described as follows.

Referring to FIG. 4, the process of converting the data stored in the database into the operational information, that is, the information output function will be described below.

In order to retrieve network management information, a desired system connected to the network must be selected. In the user interface screen of the broadband line distribution system, a node number of a desired system is selected (44), and a DB (45) A database screen is searched for information.

In the called network management information menu, desired network management information is selected (46). At this time, the selectable information type 47 includes performance history information, failure occurrence history information, and configuration change history information. When the desired information is selected in the network management information menu selection step 46, a menu 49 of the output method 49 is called up. The selected output method type 49 (i.e., table information and condition inquiry) )do.

When the table information is selected, the selected output method information is checked (50), and all the data of the corresponding table are searched (51) without any condition and outputted to the screen (55) In the method selection menu (53), a desired inquiry method is selected (52). The inquiry conditions include parameters according to date (year, month, day, hour, 15 minute period), signal level, unit name and information type.

At this time, all of the inquiry conditions can be selected, and only one of them can be selected to set the conditions.

Upon completion of the condition setting 52 as described above, the condition data retrieval module 54 retrieves the corresponding information, and the retrieved result is output to the screen by the result output module 55.

As described above, according to the sub-network history data management system and method of the broadband line distribution system of the present invention, it is possible to systematically store a large amount of data for network operation, to provide various network operation information, There is an advantage that it can cope promptly in the event of a failure.

In addition, the system operation status and history connected to the network can be grasped through the centralized network management, and the network operation convenience is provided.

Claims (8)

A method for managing network management data of systems connected to a subordinate network of a broadband line distribution system, the method comprising: receiving a first message from an agent of a transmission system connected to a subnetwork; Analyzing, processing and storing a message according to a message identifier and storing the message according to the message identifier; and a message providing step of storing the information stored in the message storage step to the operator A method of managing subnetwork history data of a broadband line distribution system by a relational data model including an output step. The method of claim 1, wherein the message storing step comprises: a second message receiving step of receiving a message from the manager by the message transmitting step; and a second message receiving step of checking whether the message received in the second message receiving step is a network management message A system identification step of generating system unique number data by checking a system node number in case of a resultant network management message in the network management message checking step and a system identification step of checking whether a message identifier exists to check whether a message identifier exists, Checking whether a message identifier is a performance report message if the message identifier exists in the step of checking existence of the message identifier; and if the message identifier is a performance report message, Performance to process messages A performance data generation step of generating performance report data after the operation of the performance report message processing step; a step of converting the data generated in the performance data generation step into a query word recognizable by the database management system And a database storing step of storing the converted data in the query term conversion step. The method of claim 1, 2. The method of claim 1, wherein the message storage step is performed when the network management message is the operation data message of the broadband line distribution system as a result of the network management message checking step, And if it does not, proceeds to an error processing step. The method of claim 1, wherein the message storage step comprises: if the result message identifier of the performance report message is not a performance report message, proceeding to a failure occurrence message confirmation step of checking whether the message identifier is a failure occurrence message, If the result message identifier of the check result step is a failure occurrence message, the process proceeds to a failure occurrence data generation step of generating failure occurrence data after the failure occurrence message process step. If the result message identifier of the failure occurrence message check step is not a failure occurrence message, And a configuration change data generation step of generating configuration change data after the configuration change message processing step if the configuration change message check result step message identifier is a configuration change message. If the result message identifier of the configuration change message is not a configuration change message, the process proceeds to a query term conversion step of converting the message identifier into a query term. In the failure occurrence data generation step and the configuration change data generation step, After the data is generated, the generated data is converted into a query term that can be recognized by the database management system. After the data is converted in the query term conversion step, the converted data is stored Wherein the subnetwork history data management method of the broadband line distribution system is based on the relational data model. The method of claim 1, wherein the message outputting step comprises: a node number selecting step of selecting a node number of a desired system connected to a network; a database selecting step of selecting a database; An output method selection step of selecting a desired output method among the table information and the condition inquiry; and an inquiry method selection step of selecting a desired inquiry method when the condition inquiry is selected in the output method selection step A condition data retrieval step of retrieving condition data by a method selected in the inquiry method selection step, and a result output step of outputting data retrieved in the condition data retrieval step. A method for managing subordinate network history data of a system. 2. The broadband line distribution system according to claim 1, wherein the network management selecting step of the message outputting step comprises: selecting the available information as the performance history information, the failure occurrence history information, and the configuration change history information. Medium - speed network history data management method. 2. The method according to claim 1, wherein, in the step of outputting the message, the output method selection step proceeds to the result output step after all data search steps when table information is selected. How to manage network history data. The method according to claim 1, wherein the selecting of the inquiry method in the message output step comprises: selecting the inquiry method as a parameter according to a date (year, month, day, hour, 15 minute period), signal level, unit name, A method for managing subordinate network history data of a broadband line distribution system using a relational data model characterized by: