KR0173209B1 - Synchronous digital hierarchy system - Google Patents

Abstract

The present invention relates to a method for maintaining a performance management object in a synchronous digital hierarchy (SDH) device, comprising: a first step of calculating an initialization of a performance monitoring object and a cumulative number of periodic requests; A second step of changing the elapsed time after receiving the response to the periodic request for the current data after the first step, and examining which of the 15-minute and 1-day reports; A third step of examining a cumulative frequency for 15 minutes if the 15 minute report is performed and accumulating the 15 minute performance value if all the performance values are 0; After performing the third step, create an instance by deleting the maximum 15-minute history data object based on the 15-minute threshold, and specify and initialize the threshold exceeded alarm release notification or recognition interval flag as a failure according to the presence of the threshold alarm; Step 4; A fifth step of investigating the cumulative number of times per day if the daily report is performed and accumulating the daily performance value if all the performance values are 0; After performing the fifth step, create an instance by deleting the longest one-day history data object based on the one-day threshold, and specify and initialize the threshold exceeded alarm release notification or recognition interval flag as a failure according to the existence of the threshold alert. Step 6; After performing the first step, if the alarm report is not available alarm and 1 day data, if the release alarm releases the communication alarm, if not released by notifying the communication alarm to delete / add to the current fault list, the unavailable alarm is also 1 day data Or seventh step of notifying and initializing an error; An eighth step of, after performing the first step, initiating an operation state change request from a higher level object if the request is the same as the previous state, and notifying and initializing the state if it is not the same; A ninth step of performing a modification and initializing a corresponding attribute when an M-SET service request is received from the communication management network OS or the MP after performing the first step; And a tenth step of notifying and deleting the object when the termination signal is performed after the first step is performed.

Description

How to Manage Performance Management Objects in Synchronous Digital Hierarchy Systems

1 is a structural diagram of a maintenance subsystem of a 10 Gbps optical transmission system to which the present invention is applied.

2 is a block diagram of a management information base block of an agent processor in a 10G optical transmission maintenance system.

3 is a flowchart of performance of a performance monitoring object function in a management information base block according to the present invention;

The present invention relates to a method for maintaining performance management objects in a synchronous digital hierarchy (SDH) system for performing standard performance management functions in a 10Gbps synchronous optical transmission system serving as a representative of a communication management network.

In general, the 10Gbps Synchronous Digital Hierarchy (SDH) optical transmission system has been developed in Korea as a part of the HAN / B-ISDN project at the Korea Institute of Electronics and Telecommunications since 1993.

When the transmission system acts as a representative of the communication management network, the management information base is a repository of management objects that provide a state for management functions of the OS (Operation System) while maintaining all the information of the system in a standardized form.

In the prior art, the management information base was operated as a passive information store between the administrator and the actual system. However, in order to keep the state of the system as inconsistent as possible, the objects that perform each management function in the delegate must actively collect the necessary information and maintain the state of the system by the combination of possible information.

Accordingly, an object of the present invention is to implement a standard information model and supplement the performance management object existing in the delegate to provide the actual system state as much as possible by actively collecting the state of the hardware even in the performance monitoring function performed by the transmission system. The purpose of the present invention is to provide a method for maintaining performance management objects in a synchronous digital hierarchy (SDH) system.

A method for maintaining a performance management object in a synchronous digital hierarchy (SDH) system, the method comprising: a first step of calculating an initialization of a performance monitoring object and a cumulative number of periodic requests; Changing an elapsed time in response to a periodic request for current data; A third step of investigating the cumulative number of time interval reports and all performance values if the report is for a specific time interval among the predetermined time interval reports; A fourth step of creating an instance by deleting the longest history data object based on the corresponding time interval threshold, and designating a threshold exceeded alarm release notification or recognition interval flag as a failure according to the existence of the threshold alert; A fifth step of notifying the communication alarm release if the corresponding alarm is a release alarm as a non-available alarm after performing the first step, and notifying the communication alarm to delete / add the current error list by notifying the release alarm; A sixth step of, if the operation state change request is received from a higher level object after performing the first step, comparing the same with the previous state and notifying the operation state after changing the state; A seventh step of performing a change to a corresponding attribute (management status, history retention) when a management status change or history retention change request from a communication management network or a management processor is received after performing the first step; And an eighth step of notifying and deleting the object when the end signal is received after the first step is performed, and maintaining the performance management object in the synchronous digital hierarchy (SDH) system.

Hereinafter, with reference to the accompanying drawings will be described an embodiment of the present invention;

1 is a structural diagram of a maintenance subsystem of a 10 Gbps optical transmission system to which the present invention is applied, and a physical structure of a management subsystem for connecting to a Telecommunications Management Network (TMN) in a 10G optical transmission system provides a management application function. It consists of a management processor 1 (hereinafter referred to as an MP) and an agent processor 2 (hereinafter referred to as an AP) that provides information of management objects for management applications.

The MP 1 is connected to a management user interface block 5 for application management processing, a management application block 7, a data processing block 9, a TMN OS for communication connection with a communication management network TMN and an agent. It consists of a block 6 and an agent connection block 8.

The data maintained in the MP 1 corresponds to the MDB 10 and there is a management unit maintenance block 11 for managing the processes performed in the MP 1.

The AP 2 includes an agent processing block 14 and an agent information base block 16 for storing and processing management information required by a management processor, and a user interface block 12 for supervisory control and a supervisor for an interface with the supervisory control. There is a control connection block 15, a manager connection block 13 for communication with a management processor.

The data maintained in the AP 2 corresponds to the MIB 17 and there is a maintenance block 18 for managing the processes performed in the AP 2. The TMN OS 3 represents the entity that the 10G optical transmission system will ultimately be connected to the TMN to perform the manager function, and obtain the status of actual resources from the Maintenance and Control Processing Subsystem (MCPS) 4 of the 10G system. do.

2 is a functional structure diagram of an agent (agent) information base 16 performed in the AP 2 of the 10G optical transmission maintenance system.

The delegate information base is composed of the configuration management object unit 21, the failure management object unit 22, the performance management object unit 23, the support object unit 24.

In the configuration management object unit 21, there are objects related to a signal that can be accommodated in the 10G optical transmission system, and facilities and state control functions of hardware constituting the same.

The failure management object unit 22 recognizes and reports a failure of a network and a network element, and performs a function related to diagnosis and recovery.

The performance management object unit 23 has an evaluation and reporting function for the performance of the network and the network elements.

In addition, the support object unit 24 is composed of objects of a function that supports configuration, failure, performance management objects.

The 10G optical transmission system needs an information base composed of the above-mentioned objects to perform standardized management functions as an agent connected to a communication management network.

In particular, the performance management object unit 23 enables performance management of the 10G system to be used in the inter-station transmission path by maintaining performance parameters of 15 minutes and 1 day, which are standard monitoring periods in the synchronous digital hierarchy (SDH) system.

When the 10G optical transmission system is connected to the communication management network and acts as an agent, the performance management object unit 23 performs performance evaluation and reporting of network elements through a standardized interface.

Therefore, it is possible to provide data for the administrator to evaluate the performance of the system through the implementation of 15 minutes and 1 day performance monitoring data and the history maintenance function recommended in the SDH system standard.

In addition, it can be provided when the administrator requests the current performance data at any time by periodically requesting the actual resource within a given monitoring period, and can generate a performance alert by comparing the thresholds.

In addition, it is possible to retain performance monitoring results for a desired period by maintaining the historical data. These functions can be connected to the communication management network in the future by maintaining standardized performance monitoring objects in the 10G optical transmission system. Do it.

As such, when the 10G system plays the role of agent in the communication management network, it acts as a process that permanently performs how to implement the performance monitoring object among management information, and responds to the current performance value request from the manager at any time or to actual resources. Fig. 3 shows that the system has a performance value and a function of generating a threshold exceeded alarm.

3 is a flowchart illustrating an embodiment of a method for maintaining a performance management object in a management information base block according to the present invention.

Performance monitoring in a synchronous transmission system is standard operating at 15 minute and 1 day intervals. Thus, all performance management objects are implemented to operate in two watch cycles.

First, when an operation of the 10G optical transmission system is started, a delegate function is performed and initialization of a performance monitoring object such as matching with actual resource information is performed (31). At this time, since the performance monitoring object must operate at a constant monitoring cycle, the number of periodic requests for requesting the performance data is calculated. All objects consist of communication between the part performing service request and the real device interworking with the OS of communication management network. A periodic request of the current data is made 32 to the monitoring and control unit for collecting the performance data. When the current performance collection value is received in response (33), the elapsed time value representing the required time is calculated and changed (34), and the monitoring period is checked (35). In the case of 15-minute report data, the cumulative number of times is checked in the 15-minute retention object instance (36). If the 15 minute period has not yet been exceeded, the performance value is compared to nonzero (37). In this process, if the performance value is 0, there is no need to perform a cumulative or monitoring report, so the cumulative number of 15 minutes is increased (55). If the cumulative number of 15 minutes is exceeded, since the zero value is continuously generated, the cumulative number is initialized so as not to generate historical data (56). If the performance value is not zero, it accumulates at the current value (38) and increases the cumulative number of times (39). The cumulative value is accessed 40 to compare with the threshold defined in each performance parameter. If the 15-minute data exceeds the threshold, it accumulates at its current value (38) and increases the cumulative number of times (39). The cumulative value is accessed 40 to compare with the threshold defined in each performance parameter. When the 15-minute data exceeds the threshold (41), the MP side is notified of the threshold exceeded alert (42). In this case, the alarm is added to the current problem list attribute (43). If the accumulated time point of the performance data reaches the reporting point of 15 minutes (44), the historical data generation process is performed. If the 15 minute monitoring has not yet completed, the process returns to the current data request. The current data object contains an attribute that holds a history retention period. When the history data is generated, the history retention period is compared (45), and when the history data is exceeded, the oldest 15-minute history data is deleted (46), and the latest 15-minute data is generated as new history data (47). After generating the historical data, the 15 minute performance value is notified to the MP for periodic performance data reporting (48). The current data is then initialized to collect new performance (49). When the 15 minute monitoring ends, it checks whether a threshold exceeded alarm has occurred during the current period (50), and if there was an alarm, sends a threshold alarm release notification (51). At this time, the corresponding alarm content is deleted from the current fault list attribute (52). At the end of monitoring, check whether or not a sus- tain interval flag on the monitoring data is set to 'true' (53), and set a failure as the new cycle starts. ).

Even for the daily report data, the operation is equal to 15 minutes. First, when the data response comes, the elapsed time value indicating the required time is calculated and changed (34), and after the comparison of the monitoring cycles (35), the cumulative number of times is checked in the holding object instance (57). If it has not yet exceeded the one-day period, the performance value is compared to nonzero (58). In this process, if the performance value is 0, there is no need to perform cumulative or monitoring reports, so only the cumulative number of days is increased (76). If the cumulative number of times is exceeded per day, since the performance value of 0 is continuously generated, the cumulative number is initialized so as not to generate the historical data (77). If the performance value is not 0, the accumulated value is accumulated at the current value (59) and the accumulated number is increased (60). The accumulated value is accessed (61) to compare with the threshold defined in the angular performance parameter. If the daily data exceeds the threshold (62), the MP side is notified of the threshold exceeded alert (63). At that time, add the alarm to the current fault list attribute (64). When the performance data accumulates as a result of the daily report (65), the historical data generation process is performed. If the daily monitoring has not been completed yet, the process returns to the current data request task. When the history data is generated, the history retention period is compared (66), and when the history data is exceeded, the oldest one-day history data is deleted (67), and the latest one-day data is generated as new history data (68). After generating the historical data, the daily performance value is notified to the MP for periodic performance data reporting (69). The current data is then vaporized to collect new performance (70). As the daily monitoring ends, it checks whether a threshold exceeded alarm has occurred during the current period (71), and if there was an alarm, sends a threshold alarm release notification (72). At this time, the corresponding alarm content is deleted from the current fault list attribute (73). At the end of the monitoring, it is determined whether a sus- tain interval flag on the monitoring data is set to 'true' (74), and the operation of a new cycle is started (75). If an operation state change request is received from an upper object (87), it is first compared with the previous state (88). When a request for designation enters another state, the state value is changed (89) and a state change notification is performed (90).

If an alert is received from the MCPS (78), first, it is determined whether the alert can be generated in the performance management object (79). Other alarms give error notifications (86). Since the unavailable alarm is generated for the daily monitoring data, it is compared whether it is a daily data object (80). If the alarm level is released (81), if the release message is a release notification (82) and the corresponding alarm content is deleted from the current fault list attribute (83). If an alarm is applicable, the communication alarm is notified at the given alarm level (84) and added to the current fault list attribute (85).

When M-SET service request comes from communication management network OS or MP (91), the attribute is changed. When an administrative state change request comes in (92), it is first compared with the previous state (93). When a designation request enters another state, the state value is changed (94) and a state change notification is performed (95). In operation 96, a status change request message is transmitted to control the operation of the monitoring controller. When a history retention change request comes in (98), it is first compared if the administrative state (administrative state) is locked (99). If not, an error notification is made (107). In case of the locked state, in order to confirm the history retention period according to the SDH standard recommendation, it is compared whether or not a history retention value of 16 or more is designated for the 15-minute data (100). In the case of daily data, it is compared whether a value of 1 or more is given (105). If the condition is met, the history retention value is changed (101). After the change, the attribute value change notification is performed to the MP side (102). In this case, the value of the index variable for maintaining the history is adjusted (104) when the history retention value is reduced by comparing with the previous value (103). If the history retention value does not satisfy the constraint condition, an error notification is made (106).

The performance management object is permanently executed in the delegate process. If receiving the termination signal from the operating system (OS) (108), the execution is terminated and the deletion of the object instance is performed (109).

The present invention described above is not limited to the above-described embodiments and the accompanying drawings, and various substitutions, modifications, and changes can be made in the art without departing from the technical spirit of the present invention. It will be apparent to those of ordinary knowledge.

The present invention constructed and operated as described above has the following effects.

1) It is possible to possess performance parameters according to the standard model in 10 optical transmission system.

2) It can perform the performance monitoring function of 10G optical transmission system from TMN OS.

3) Current status inquiry and history maintenance for performance monitoring data of 10G optical transmission system is possible.

4) Threshold comparison and alarm notification of 15 minutes and 1 day performance data of 10G optical transmission system is possible.

Claims (5)

A method for maintaining a performance management object in a synchronous digital hierarchy (SDH) system, the method comprising: a first step of calculating an initialization of a performance monitoring object and a cumulative number of periodic requests; Changing an elapsed time in response to a periodic request for current data; A third step of investigating the cumulative number of time interval reports and reporting all performance values if the report is for a specific time interval among the predetermined time interval reports; A fourth step of creating an instance by deleting the longest history data object based on the corresponding time interval threshold and designating a threshold exceeded alarm release control or recognition interval flag as a failure according to the existence of the threshold alert; A fifth step of notifying the communication alarm release if the corresponding alarm is a release alarm as a non-available alarm after performing the first step, and notifying the communication alarm to delete / add the current error list by notifying the release alarm; A sixth step of, if the operation state change request is received from a higher level object after performing the first step, comparing the same with the previous state and notifying the operation state after changing the state; A seventh step of performing a change to a corresponding attribute (management status, history retention) when a management status change or history retention change request from a communication management network or a management processor is received after performing the first step; And an eighth step of notifying and deleting the object when the end signal is received after the first step is performed. The method of claim 1, wherein the predetermined time interval of the third step is 15 minutes or 1 day. The method of claim 2, wherein the fourth step, when the 15-minute data exceeds the threshold, notifies the management processor side of the threshold exceeded alarm, and performs a history data generation process when the 15-minute report point is reached as a result of accumulating performance data. The ninth step; A tenth step of deleting the oldest 15-minute history data and generating the latest 15-minute data as new history data if the history maintenance period is exceeded when the history data is generated; An eleventh step of notifying the management processor of the 15-minute performance value for periodic performance data reporting after generating the historical data, and initializing the current data for collecting new performance; And 15 minutes monitoring is terminated, check if the threshold exceeded alarm occurred during the current period, and if there was an alarm, notify the threshold alarm release, delete the corresponding alarm contents in the current fault list, and monitor when the monitoring ends. If the recognition interval flag indicating the possibility of error in the data is 'true', a new cycle of operation is started, so performance management in a synchronous digital hierarchy (SDH) system including a twelfth step of specifying and initializing a failure How to keep an object. The method of claim 2, wherein in the fourth step, when the daily data exceeds the threshold, the management processor notifies the threshold exceeded alarm, and when the performance data accumulation result reaches the daily reporting time, the history data generation process is performed. The ninth step; A tenth step of generating the oldest daily data as new history data if the history retention period is exceeded when the history data is generated; An eleventh step of notifying the management processor of a daily performance value for periodic performance data reporting after generating historical data, and initializing current data for collecting new performance; And if one day monitoring is over, check whether the threshold exceeded alarm occurred during the current period, and if the alarm existed, notify the threshold alarm release, delete the corresponding alarm contents in the current error list, and monitor when the monitoring ends. If the recognition interval flag indicating the possibility of error in the data is 'true', a new cycle of operation is started, so performance management in a synchronous digital hierarchy (SDH) system including a twelfth step of specifying and initializing a failure How to keep an object. The method of claim 1, wherein the seventh step comprises: a ninth step of comparing a management state change request from a communication management network or a management processor with a previous state; A tenth step of changing a state value and notifying a state change when a request for designation of another state is received and transmitting a state change request message for controlling the operation of the monitoring controller; If a request for a change of history is entered, first check whether the management status is locked, and if it is open, give an error notification.In the locked state, to check the history retention period, if 15 minutes data is 16 or more or 1 day data, and more than 1 An eleventh step of notifying the attribute change by changing the history retention period; If the history retention value is reduced compared to the previous value, the synchronous digital hierarchy including the twelfth step of adjusting an index variable for history retention to notify an error when the history retention value does not satisfy the constraint condition is performed. SDH) How to maintain performance managed objects in the system.