KR19980030117A - Subnetwork History Data Management Method of Broadband Circuit Distribution System - Google Patents

Abstract

The present invention relates to a subnetwork history of a broadband circuit distribution system designed and implemented in accordance with a relational data model in order to more quickly and accurately manage operation and maintenance data of network management systems connected to a subordinate network of a broadband circuit distribution system (BDCS). Data management method, the physical configuration of the system to which the subnetwork history data management method is applied is composed of a broadband circuit distribution system and subordinate systems connected thereto, the logical configuration for managing this is to manage the subnetwork data It consists of agents.

In the dependent network history data management method, network management history data transferred between a manager and an agent may be stored in a database defined according to a relational model and processed into operational information to provide various information to a system operator.

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

Description

Subnetwork History Data Management Method for Broadband Circuit Distribution System

The present invention relates to a subnetwork history of a broadband circuit distribution system designed and implemented in accordance with a relational data model in order to more quickly and accurately manage operation and maintenance data of network management systems connected to a subordinate network of a broadband circuit distribution system (BDCS). The data management method relates to a physical configuration of a system to which the subnetwork history data management method is applied is composed of a broadband circuit distribution system and subordinate systems connected thereto. The logical configuration for managing the subnetwork data is to manage the subnetwork data. It consists of agents.

Digital Cross Connection (DXC), which was handled manually in the existing asynchronous transmission network, is distributed with subordinate systems connected to the network because of the characteristics of DXC, so that operation and management information for each system is distributed. It takes a long time to recover from a system failure.

In addition, since the history management for the accurate operation and management information of the distributed systems is not performed, it is difficult to collect the accurate operation and management information for the subordinate systems in terms of the operation of managing the DXC. Recovery is very difficult in the event of a failure.

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

In order to compensate for the above disadvantages, the present invention provides a method for managing dependent network history data of a broadband circuit distribution system designed and implemented according to a relational data model capable of integrated management of operation and maintenance data for a dependent network. For the integrated data management, the operation and management information of distributed systems are automatically collected through a network management function, and the collected data can be quickly and accurately managed by integrated management in a database.

Data stored in the database is 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 by the type of management information to quickly and systematically deal with failures. By using this database management system, it is possible to manage a large amount of information and easily manage a large amount of information by integrating and managing 14 volumes of operation and management information based on a 2.5 Gb / s transmission device.

In addition, the retrieval of operation information of DXC also provides convenience of operation through providing various functions and integrated management through color user interface screen.

1 is a diagram illustrating a configuration of a broadband network distribution system subordinate network system according to an embodiment of the present invention;

2 is a message processing path diagram according to an embodiment of the present invention;

3 is a flowchart illustrating network management data storage according to an embodiment of the present invention;

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

＊ Description of main parts of drawing

1: Device Management Subsystem, 2: DXC Configuration Manager, 3: User Interface Manager, 4: Agent, 5: System Operation Manager, 6: Manager, 7: Database Manager, 8: Data Storage, 9: Subordinate Network Configuration Degree

The slave network history data management method of the broadband circuit distribution system designed and implemented in accordance with the relational data model provided by the present invention includes a first message receiving step of receiving a message from an agent of a transmission system connected to the slave network; A message transmission step of passing the message received in the message reception step via a manager; a message storage step of collecting, analyzing, processing, and storing the message passed through the message transmission step according to a message identifier; and information stored by the message storage step; It includes a message output step that provides the operator with the.

A broadband line distribution system that handles large-capacity line distribution functions can be configured as a subordinate network with 155Mb / s, 622Mb / s, or 2.5Gb / s synchronous transmission devices. Each system is managed through the agent that manages the network and the manager who manages the agent. The manager executes the control commands necessary for the operation and management of each system connected to the subordinate network, and the agent reports the response and the operation information on the control commands sent from the manager, thereby controlling the operation of all the systems connected to the subordinate network. And perform administrative functions.

The capacity of a system connected to a subordinate network of a broadband circuit distribution system can be connected to a maximum of 15 inter-station transmission systems based on a 2.5Gb / s system, and the connection type of the network is configured as a terminal type or a ring type. The system connected to the subordinate network may be composed of systems forming the subordinate subordinate network again.

The slave network history data management system of the broadband line distribution system according to the relational data model of the present invention for managing the historical data of such a system includes data management for managing the operation / maintenance data of the broadband circuit distribution system and data of the slave network. Block and a data storage unit for storing network management data processed by the data management block.

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

1 is a diagram illustrating a configuration of a broadband network 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, and FIG. 3 is network management data according to an embodiment of the present invention. 4 is a storage flowchart, and FIG. 4 is a flowchart of an operation information processing according to an exemplary embodiment of the present invention.

Referring to FIG. 1, the broadband circuit distribution system provided by the present invention includes a device management subsystem 1 for processing an operation and management function and a subordinate network management function, and a conventional subnetwork configuration diagram 9. .

The device management subsystem 1 includes a system operation management block (SOM) 5 dedicated to system operation management, and a DXC configuration management block (DCM) that manages DXC configuration control functions (DCM). 2), an agent that performs network management functions of a Broadband Digital Cross-Connect System (BDCS), a System-User Connection Block (MMC) (3) that connects a system and a user, 4) a manager 6 which collectively manages the slave network of the BDCS, a database management block (DBM: 7) that manages the system operation / maintenance data of the BDCS and the data of the slave network, and the DBM It consists of a network management database (NETDB: NET Database) (8) which stores network management data processed in (7).

The existing subordinate network diagram (9) shows the relationship between the manager (6) who manages the subordinate network management and the system connected to the subordinate network. In the network connection form, the subnetwork is linearly or annularly connected to each route and linearly. The connected system may include 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 also includes a 2.5Gb / s transmission system ( 13), the 622Mb / s transmission system 14 or the 155Mb / s transmission system 15 may be configured.

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

In this network management environment, the dependent network management history data management method of the present invention is a method for more efficiently managing the operation and control data collected through the manager 6 and the agent 100, and systematically stores data and a large amount of information. It provides accurate information quickly and accurately through the user interface from the point of view of storage and the operator. The information storage function collects, analyzes, processes and stores the information of the systems connected to the subordinate network, and the information stored by the information storage function to the operator. Provides information output function.

The information storage function transmits the control command requested by the manager 6 to a system connected to the subordinate network, and the result of the processing is transferred to the operation control data and the subordinate network which are transmitted to the DBM 7 via the manager 6 again. It is a function of storing the operation report data that the operation data reported from the connected system is transmitted to the DBM 7 via the manager 6.

At this time, the data for storing the data is composed of the control and collected data in the form of a contracted form between the functional blocks are delivered through the message queue, the message delivered to the DBM (7) through the analysis and processing data It is converted into data that can be stored in the base and then stored in NETDB (8).

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

2, network management data generated from a transmission system connected to a subordinate network is reported to the manager 18 by the agents 15 and 16 of each system and via the SMC 17, which is a message relay block. It is passed to the msg receiving 20 module of the DBM 19 which processes the management data.

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

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

The information storage function first receives a message (27) for receiving a message from the slave network system, and the message received in the message receiving step (27) is an operational data message of the broadband circuit distribution system or is connected to the slave network. Check whether it is a network management message delivered from an agent (28).

If the result of the network management message check step 28 is an operation data message of the broadband circuit distribution system, the network management message is transmitted to the system operation message processing module, and if the network management message is a message generated by a system of the subordinate network. In order to check the system node number (30), the system unique number data is generated.

After the system identification step 30, it is checked whether a message identifier msg_id exists (31), and if there is no message identifier as a result, the message identifier msg_id is sent to the error processing module 32. If the message identifier exists in the message identifier checking step 31, it is determined whether the message identifier is pm (performance report message) (33). If the result is yes, the performance report data is transmitted to the performance report message processing module 34. Generate 35.

In step 33 of checking whether the identifier is pm, if the result is no, it is determined whether the message identifier is am (failure message) (36). If the result is yes, the result is transmitted to the failing message processing module 37. Generate fault data 38.

In step 36 of checking whether the identifier is am, if the result is no, it is determined whether the message identifier is cm (configuration change message) (39). If the result is yes, it is transmitted to the configuration change message processing module 40. Generate configuration change data (41).

If the result is no in step 39 of checking whether the identifier is cm, the process proceeds to the next step, query conversion step 42.

The data (35, 38, 41) generated in each message processing module is converted into a query language that can be recognized by the database management system in the query conversion module 42 and stored in a database table which is a database storage unit 43.

As such, the data stored in the database is processed into information suitable for system operation and used as operation information.

A process of converting data stored in a database into operational information, that is, an information output function will be described with reference to FIG. 4.

First, in order to retrieve the network management information, the desired system connected to the network should be selected. In the user interface screen of the broadband line distribution system, select the desired node number (44) and select the DB (45) button to manage the network. The database screen from which the information can be retrieved is called.

The desired network management information is selected from the called network management information menu (46). The selectable types of information (47) include 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, an output method 49 menu is called. The desired output method type among the called output method type 49, that is, table information and condition inquiry, is selected (48). )do.

If the table information is selected by checking the selected output method information (50), if all data of the table is searched (51) without any condition from the already selected information type, and outputted on the screen (55), if the condition inquiry is selected In the method selection menu 53, a desired inquiry method is selected 52. There are parameters according to the date (year, month, day, time, 15 minute period), signal level, unit name, and information type.

In this case, all of the inquiry conditions may be selected, or only one may be selected to set the conditions.

When the above condition setting 52 is completed, the corresponding data is searched by the condition data search 54 module, and the search result is output on the screen by the result output 55 module.

As described above, by using the subordinate network history data management system and the method of the broadband circuit distribution system of the present invention, it is possible to systematically store a large amount of data for network operation, provide various network operation information, and network components. It has the advantage of being able to cope quickly in case of failure.

In addition, through centralized network management, it is possible to grasp the system operation status and history connected to the network, and provide convenience of network operation.

Claims (8)

A method for managing network management data of systems connected to a subsidiary network of a broadband circuit distribution system, the method comprising: a first message means step of receiving a message at an agent of a transmission system connected to the subordinate network, and received at the first message receiving step; A message transmission step via a message, a message storage step of collecting, analyzing, processing, and storing the message passed through the message transmission step according to a message identifier; and a message output step of providing the operator with the information stored by the message storage step. Subnet network history data management method of a broadband circuit distribution system using a relational data model comprising a. The method of claim 1, wherein the storing of the message comprises: a second message receiving step of receiving a message from the manager by the message transmitting step, and confirming whether the message received at the second message receiving step is a network management message; A network management message checking step, a system identification step of generating system unique number data by checking a system node number when the network management message is a result of the network management message checking step, and whether a message identifier exists to check whether a message identifier exists A step of confirming whether the message identifier is a performance report message, if the result of the step of confirming whether the message identifier exists is a result of the message identifier; To process reporting messages A query data conversion step of processing a performance report message, a performance data generation step of generating performance report data after the performance report message processing step, and converting the data generated in the performance data generation step into a query language recognizable by a database management system. And a database storing step of storing the data converted in the query conversion step. The method of claim 1, wherein the storing of the message proceeds to a system operating message processing step when the network management message checking step is an operation data message of the broadband circuit distribution system, and the message identifier exists as a result of the message identifier checking step. If not, the slave network history data management method of the broadband circuit distribution system according to the relational data model characterized in that the process proceeds to error processing. The method of claim 1, wherein the storing of the message proceeds to a failure occurrence message checking step of checking whether a message identifier is a failure occurrence message if the message identifier is not a performance report message. If the result of the checking step is a failure message, the processing proceeds to the failure data generation step of generating failure data after the failure message processing step. If the message identification step result message identifier is not a failure message, the message identifier is configured. The configuration change message checking step of checking whether the message is a change message is performed. If the result of the configuration change message checking step is a configuration change message, the configuration change message processing step generates configuration change data after the configuration change message processing step. When the configuration change message checking step result message identifier is not a configuration change message, the process proceeds to a query conversion step of converting the message identifier into a query, and generates data in the failure data generation step and the configuration change data generation step, respectively. After the generation, the generated data is converted to a query conversion step in which the database management system is recognized as a query language. After the data is converted in the query conversion step, the database storage step is performed. A method for managing dependent network history data in a broadband circuit distribution system using a relational data model. The method of claim 1, wherein the message outputting step comprises: a node number selection step of selecting a node number of a desired system connected to a network, a database selection step of selecting a database, and desired network management information from a network management information menu; A network management information selection step of selecting a step, an output method selection step of selecting a desired output method among table information and 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; And a condition data search step of searching condition data by the method selected in the inquiry method selection step, and a result output step of outputting the data searched in the condition data search step. How to manage slave network history data of system. 2. The broadband network distribution system of claim 1, wherein the network management selection step of the message output step includes selectable information such as performance history information, failure occurrence history information, and configuration change history information. Subnetwork history data management method. 2. The method of claim 1, wherein the output method selection step of the message output step proceeds to the result output step after all data retrieval steps when table information is selected. How to manage network history data. The method of claim 1, wherein the inquiry method selection step of the message outputting step comprises selecting selectable information as parameters according to date (year, month, day, time, 15 minute period), signal level, unit name, and information type. A method for managing dependent network history data in a broadband circuit distribution system using a relational data model.