KR100422149B1 - Apparatus and method for management PM data of EMS - Google Patents

Abstract

The present invention provides an apparatus and method for managing PM data of an EMS. In an EMS connected to an NE, if an operator wants to view the contents of the PM, the PM sends a PM request to the NE and processes a synchronous event according to a predetermined schedule. A PM core for performing a routine of PM related instructions; A synchronization processor connected to the PM core, receiving a bit string from the NE, and setting a sustain interval flag of a database to process a synchronization event; A database for storing scheduled PM data of the PM core at predetermined time intervals; Binary data exchanged with the NE is parsed and transmitted to the PM core and the synchronous processing unit, and the binary interface unit for formatting and transmitting the instructions generated from the PM core and the synchronous processing unit is transmitted to the NE. It is possible to minimize the traffic that may be caused by PM data of the system and to effectively synchronize the synchronization between the EMS and the NE.

Description

EMS Data Management System and Method thereof of MSS {Apparatus and method for management PM data of EMS}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus for managing performance monitor (PM) data of an element management system (EMS), and a method thereof. The present invention relates to an EMS PM data management apparatus and method for minimizing traffic that may be generated due to PM data and for effectively synchronizing the synchronization between the EMS and the NE.

In general, network management is to perform network configuration, performance management, and maintenance, and EMS is a system for comprehensive management and control of various transmission systems. Here, network management performs a function of monitoring the status of the network at all times and taking measures to control the inflow as necessary to enable efficient traffic communication. And NMS (Network Management System) is a computer system to support such network management tasks, and performs the following functions. That is, it collects and accumulates network status, alarm, traffic data, etc. from communication equipment. Calculate network management parameters or statistical data. Command to control the traffic inflow of communication equipment. Controls network monitors and network control terminals of network management centers. EMS is a device that manages network devices individually.

In addition, PM data is data that manages performance information. It uses local variables to read and update performance information for a period of time and to report such contents.

In case of equipment that accepts the Common Management Information Protocol (CMIP) standard of the Telecommunications Management Network (TMN), PM data of all the corresponding ports is sent to the EMS every 15 minutes to each equipment.

1 is a block diagram of a conventional PM data management apparatus of EMS.

Here, reference numeral 10 denotes an NE which is network configuration devices, and 20 denotes an EMS that is connected to the NEs 10 to perform network management.

In addition, reference numeral 21 in the EMS 20 is a PM management unit for managing scheduled PM (PM) data generated at regular intervals, 22 is a database for storing information managed by the PM management unit 21, 23 Is a CMIP machine (Machine) for processing a protocol in conjunction with the PM manager 21.

Thus, in the conventional case, each device is supposed to generate a scheduled PM once every 15 minutes according to the specification for the pod of the signal. The PM manager 21 of the EMS 20 stores the performance information received through the CMIP machine 23 from each NE 10 device in the database 22, and processes and reports the information if the operator desires it.

However, such a conventional technology transmits data at the same time every 15 minutes at all devices. When data is transmitted at the same time, excessive traffic is generated when the network is large, and this traffic may cause a temporary failure. In practice, there was a problem that can make the network operation required in EMS difficult.

Accordingly, the present invention has been proposed to solve the above conventional problems, and an object of the present invention is to provide traffic that may be generated due to a large amount of PM data generated from multiple NEs in an EMS managing an access network. It is to provide a PM data management device and method of EMS that can minimize the synchronization between the EMS and NE effectively.

In order to achieve the above object, the PM data management apparatus of the EMS according to an embodiment of the present invention,

In the EMS connected to the NE, if the operator wants to view the contents of the PM, the PM sends a PM request to the NE, processes a synchronous event according to a predetermined schedule, and updates the database if necessary to perform a PM related routine. A core; A synchronization processor connected to the PM core and processing a synchronization event by setting a sustain interval flag of the database when a bit string is received from the NE, when a different portion is found in comparison with the data stored in the database; A database for storing the scheduled PM data of the PM core at a predetermined time, and setting a sustain interval flag when a different part is found in comparison with the stored data when a synchronization event comes; And a binary interface for parsing binary data exchanged with the NE and transmitting it to the PM core and the synchronization processor, and formatting the command generated by the PM core and the synchronization processor and transmitting the command to the NE. Features of the jacket.

PM data management method of the EMS according to an embodiment of the present invention to achieve the above object,

Upon receiving a PM event or a synchronization event from the NE, checking whether it is null data or the end of the data, processing an event of each signal, and determining which event the processed event is; If the event is a PM event, processing the PM data and storing it in a database; If the event is a synchronous event, determining whether a presence interval flag is present; If the aspect interval flag is present, the method includes the step of identifying and storing the aspect listen in the database.

1 is a block diagram of a conventional PM data management device of EMS,

2 is a block diagram of a PM data management apparatus of EMS according to the present invention;

3 is a flowchart illustrating a PM data management method of an EMS according to the present invention;

4 is a diagram illustrating a PM data format when all PM data of a corresponding interval is transmitted in an NE used in the present invention.

5 is a view showing a PM data format in the case of selecting and transmitting only the necessary port used in the present invention,

6 illustrates a bit string format of a synchronization event used in the present invention.

Explanation of symbols on the main parts of the drawings

10: NE 20, 30: EMS

21: PM management unit 22, 33: database

23: CMIP Machine 31: PM Core

32: synchronization processing unit 34: binary interface unit

Hereinafter, an embodiment according to the present invention, the PM data management apparatus of the EMS and the method configured as described above will be described in detail with reference to the accompanying drawings.

2 is a block diagram of the PM data management apparatus of the EMS according to the present invention.

As shown in the figure, in the EMS 30 connected to the NE 10, if the operator wants to view the contents of the PM, a PM request is sent to the NE 10, and a synchronous event ( A PM core 31 which processes a Sync Event and updates the database 33 when necessary to perform a routine of PM related instructions; When a bit string is received from the NE 10 and compared with data stored in the database 33, a different portion is found and a sustain interval flag of the database 33 is detected. A synchronization processor 32 for processing a synchronization event by setting a Suspect Interval Flag); A database (33) for storing the scheduled PM data of the PM core (31) at a predetermined time, and setting a duration interval flag when a different part is found in comparison with the stored data when a synchronization event comes; Parse binary data exchanged with the NE 10 and transmit the binary data to the PM core 31 and the synchronization processor 32, and format the instructions generated by the PM core 31 and the synchronization processor 32. It is configured to include a binary interface 34 for transmitting to the NE (10).

3 is a flowchart illustrating a PM data management method of an EMS according to the present invention.

As shown therein, when receiving a PM event or a synchronization event from the NE 10, checking whether it is the end of the null data or the data, processing the event of each signal, and determining which event is the processed event (ST11). ~ ST14); If the event is a PM event, process PM data and store in the database 33 (ST15); If the event is a synchronous event, determining whether a Suspect Interval Flag is present (ST17); If the presence interval flag is present, a step (Suspect Reason) is identified and stored in the database 33 (ST18).

Operation of the PM data management apparatus and method of the EMS according to the present invention configured as described above will be described in detail with reference to the accompanying drawings.

First, the present invention is to minimize the traffic that can be generated due to the large amount of PM data generated from the multiple NE (10), and to effectively synchronize the synchronization between the EMS (30) and the NE (10).

Thus, the PM core 31 performs a routine for processing PM related instructions. That is, when the PM event occurs, the event data is stored in the database 33, and if the operator wants to see the contents of the PM, the PM transmits a PM request to the NE 10. In addition, the synchronization event (Sync Event) is processed according to a predetermined schedule, and the database 33 is updated when necessary. Thus, the PM core 31 sends this series of instructions to an appropriate destination and performs a function of processing as desired by the operator.

The synchronization processor 32 receives and processes a synchronization event and is carried in the form of a bit string format of the synchronization event of FIG. 6. In addition, when receiving a bit string indicating whether the PM value is generated at each interval every 24 hours from the NE (10) is compared with the data stored in the database (33). Thus, if a different portion is found between the bit string from NE 10 and the data in database 33, the operator sets the Suspect Interval Flag of database 33 to allow the operator to be in database 33 at that time. Notify that there is something wrong with the data.

The database 33 stores the scheduled PM every 15 minutes. In addition, when a synchronous event comes, the compare interval flag is set when a different part is found compared to the stored data.

The binary interface 34 parses the binary data exchanged with the NE 10 in accordance with a structure of a programming language such as C language, and transmits the binary data to the PM core 31 and the synchronization processor 32. In addition, it performs a function of formatting the instructions generated by the PM core 31 and the synchronization processor 32 and transmitting them to the NE 10.

In addition, as shown in FIG. 3, when receiving a PM event or a sync event from the NE 10, the terminal checks whether the null data or the end of the data is processed, processes an event of each signal, and determines which event is the processed event. Thus, if the event is a PM event, the PM data is processed and stored in the database 33. If the event is a synchronous event, it is determined whether there is a Suspect Interval Flag, and if there is a Suspect Interval flag, the Suspect Reason is checked and stored in the database 33.

FIG. 4 is a diagram showing a PM data format when all the PM data of a corresponding interval is transmitted by one NE used in the present invention. FIG. 5 is a diagram showing the PM data format when only the necessary port used in the present invention is selected and transmitted. Drawing.

Meanwhile, the operation of the present invention will be described in more detail in terms of event generation, synchronization, and binary interface.

Event occurrence:

If the PM is not " 0 " during the interval, " event occurrence " Since the transmission is performed only when the PM value is not "0", unnecessary data transmission can be prevented. 2, the generation interval is " 15 + ?? ". The amount of traffic generated at one time can be reduced by making a slight difference in occurrence time for each NE 10. This "??" The value is sent to the NE 10 by the EMS 30 as a random value at the time of initialization of the NE 10 through a command called Set Report Time.

- synchronization :

Every 24 hours, a bit string indicating whether a PM value is generated for each interval is transmitted (see FIG. 6). In the case of CV of port 1 of RS in FIG. 6, if the bit value is “1”, it indicates that a PM value has occurred. Therefore, after comparing each interval in the received bit string, if it is wrong, the Suspect Interval Flag is set, and if possible, the Listen information is included.

By simply setting a flag to simply verify the vast amount of PM data, we reduce traffic and let operators know that PM data was a problematic interval.

Binary Interface:

Parses binary data to and from the NE 10 in accordance with the structure of the C language, which is a programming language, and formats the instructions generated by the EMS 30 to be sent to the NE 10. In addition, since the amount of PM data is huge, it has two types of data formats (FIGS. 4 and 5).

In the case of transmitting all the PM data of the corresponding interval in one NE 10, the amount of data is reduced by proceeding to delete the address portion designating the occurrence port, and when the end of the table is executed, the buffer with the generated code is written to the predetermined file. do.

As such, the present invention minimizes traffic that may occur due to a large amount of PM data generated from multiple NEs in the EMS managing the access network, and effectively synchronizes the synchronization between the EMS and the NEs.

Although the preferred embodiment of the present invention has been described above, the present invention may use various changes, modifications, and equivalents. It is clear that the present invention can be applied in the same manner by appropriately modifying the above embodiments. That is, it is applicable to all transmission equipments such as 155M optical transmission equipment using the binary interface used in the present invention. Accordingly, the above description does not limit the scope of the invention as defined by the limitations of the following claims.

As described above, the EMS data management apparatus and method of the EMS according to the present invention minimizes traffic that may be generated due to a large amount of PM data generated from multiple NEs in the EMS managing the access network, and It is effective to effectively synchronize the NEs.

In addition, the present invention can efficiently distribute the network traffic. That is, for 155M transmission equipment, the total number of PMs generated at one time (number of PMs = number of signals * number of ports * (number of PM types, ie 945 (COMMON) + 924 (CHANNEL) = 1869)) is approximately equipment mounting. It depends on the state, but about 2K bytes. If there are 1000 devices in a network, about 2Mbytes of traffic suddenly occurs. In the case of DCC (Data Communication Channel), only 192Kbps speed is supported, which may cause delays or loss of traffic in the entire network. Therefore, the present invention provides a "??" The traffic was distributed by giving a value.

In addition, in view of efficiency, the present invention enables to efficiently verify a large amount of PM data. In other words, by judging only the integrity of the data at that time, and using the bit string to determine the accuracy of the current PM data using only the minimum amount of data, the operator is given a criterion for judging the data, and the impact on the load or traffic for network operation. There is a minimized effect as much as possible.

Claims (2)

For EMS connected to NE, A PM core which transmits a PM request to the NE, processes a synchronous event according to a predetermined schedule, updates a database if necessary, and executes a PM related instruction routine if an operator wants to view the contents of the PM; A synchronization processor connected to the PM core and processing a synchronization event by setting a sustain interval flag of the database when a bit string is received from the NE, when a different portion is found in comparison with the data stored in the database; A database for storing the scheduled PM data of the PM core at a predetermined time, and setting a sustain interval flag when a different part is found in comparison with the stored data when a synchronization event comes; And a binary interface unit for parsing binary data exchanged with the NE, transmitting the PM core and the synchronization processor, and formatting the command generated by the PM core and the synchronization processor. EMS PM data management device. Upon receiving a PM event or a synchronization event from the NE, checking whether it is null data or the end of the data, processing an event of each signal, and determining which event is the processed event; If the event is a PM event, processing the PM data and storing it in a database; If the event is a synchronous event, determining whether a presence interval flag is present; If there is the aspect interval flag, checking and storing a aspect listen in the database.