KR20030003365A - Method for state management of communication session in ATM-based high speed data network - Google Patents

Abstract

PURPOSE: A system for managing a communication session state in an ATM(Asynchronous Transfer Mode) based high-speed data network is provided to selectively activate maintenance functions according to communication sessions through the interworking with individual NMSs. CONSTITUTION: Session management clients(131,132,133) are arranged in an SML(Service Management Layer). Sub NMSs(121,122,123) are arranged in an NML(Network Management Layer). A communication session state management server(11) manages a fault state and a performance state of a communication session, on the basis of a performance event and a fault event for the communication session generated from the session management clients(131,132,133) and the sub NMSs(121,122,123). If a session control event for the communication session is generated from the session management clients(131,132,133), the communication session state management server(11) controls the sub NMSs(121,122,123) to operate a network device in accordance with the control event and reflects an operation result as a control state. If a notification and alarm event is generated from the sub NMSs(121,122,123), the communication session state management server(11) changes a fault state or a performance alarm state for the communication session.

Description

Method for state management of communication session in ATM-based high speed data network

The present invention relates to a communication session state management system in an ATM (Asynchronous Transfer Mode) based high speed data network. More particularly, the present invention relates to a complex network environment by handling a failure event and a performance event of a communication session in an ATM based high speed data network. The present invention relates to a communication session state management system in an ATM-based high-speed data network that can efficiently manage an operation state of a communication session corresponding to the present invention.

In the data network environment before the high-speed data network using ATM technology, network management technology that monitors or controls the operation status of network devices through individual network management systems (NMS) that provide facility management functions related to most network devices. This was used. This network management method corresponds to the element management layer (EML) or network management layer (NML) for managing the operation of the network device from the perspective of the TN management layer (TMN) management layer. The network structure could play its own role in a simple and independent environment.

However, with the introduction of high-speed communication technologies such as ATM and FR (Frame Relay), the network management system (NMS: Network Management System) in the high-speed data network environment where the interworking and connection between the individual data networks as well as the high speed of the data network are achieved. Service management management from the point of view of service management layer (SML) that manages communication services provided to users as well as facility management of each network performed in the element management system (EMS). Required.

Meanwhile, a communication session provided to a user in an ultra-high speed data network environment in which an ATM network and a HiNET network interwork and an ATM network and an IP network device are interconnected is intra- or inter-network. It may be configured in various forms such as a connection. Therefore, the event processing related to the operation status of the communication session in the high-speed data network environment should cover all the events from the individual network management perspective and provide the user with the integrated operation status of the session. In addition, it is necessary to differentiate the operation management functions supported by the respective lower network management systems to support operation control functions unique to a specific session according to the configuration of the communication session.

Accordingly, the present invention has been made in consideration of the above-described points, and receives failure and performance related events generated from a lower network management system of an ATM-based high-speed data network environment and reflects them as an operation state of a corresponding communication session and manages an individual network management system. This function enables the selective activation of the maintenance function required for the operation of the communication session by the specific communication session so that the operation state of the communication session can be expressed and managed from the viewpoint of failure and performance management. The purpose of the present invention is to provide a communication session state management system in an ATM-based high speed data network.

1 is a block diagram of a system to which a communication session state management system is applied in an ATM-based high speed data network according to an embodiment of the present invention.

2 to 3 is a flow chart illustrating a communication session state management system in an ATM-based high speed data network according to an embodiment of the present invention.

<Description of Symbols for Major Parts of Drawings>

11: communication session state management system 111: failure state management server

112: performance state management server 113: communication session state management database

121: HiNET network management system 122: ATM network management system

123: IP network management system 131: customer network management system

132: integrated network management system 133: failure management system

According to the communication session state management system in the ATM-based high-speed data network according to an embodiment of the present invention to achieve the above object,

A session management client existing in the service management layer;

A lower network management system existing in the network management layer; And

By configuring a communication session state management server for managing the failure state and performance state for the communication session based on the performance event and failure event for the communication session generated from the client and the lower network management system,

When a control event for the communication session occurs from the management client, the communication session state management server calls the lower network management system to perform an operation operation according to the control event, and accordingly, The control state for the communication session, and when the failure or performance related notification event is generated from the lower network management system, the communication session state management server may perform a failure state or a performance alert state for the communication session according to the received event type. It characterized in that to change.

Basically, the present invention classifies the control and notification event types that affect the operational status of the communication session in terms of management functional classification into fault management and performance management functions. The management functions for managing and controlling the operational status of the system are implemented as the fault management server and the health management server so that failure events and performance events can be handled in independent management areas. To be integrated into the status.

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

1 is a block diagram of a communication session state management system in an ATM-based high-speed data network according to an embodiment of the present invention, and communication session management (CSM) in an ATM-based high-speed data network environment to which the present invention is applied. The external management system that interacts with the communication session state management server inside the communication session management system mainly shows the overall management structure including the session management client and the lower network management system.

In FIG. 1, the communication session state management server 11 is an ATM network management system 122, a HiNET network management system 121, and an IP network management, each of which is a lower network management system that is in charge of failure and performance management functions unique to individual networks. When receiving a notification failure event or a performance alert event from the system 123, the session operation state is managed by changing the failure state information and the performance state information of the corresponding communication session according to the event type generated in the network management system 121, 122, 123. If necessary, a session management client existing in the service management layer may be a customer network management (CNM) system 131, an integrated network management (ISNM) system 132, or a trouble management (HelpDesk). ) To propagate a notification or alarm event generated in the network management system 121, 122, 123 to an external server such as the system 133.

In addition, the communication session management server 11 activates, deactivates, and sets performance thresholds for maintenance functions required for operation management of a specific session from the integrated network management system 132 or the failure management system 133 which is a management client of the communication session. Receiving a control event related to the request to call the management interface of the network management system (121, 122, 123) to control the activation state of the maintenance function required for the operation management of a particular session and to manage the items and thresholds for generating performance alarms Do this.

The communication session state management server 11 described above includes a failure state management server 111 that manages a failure event generated from the network management system 121, 122, 123 or the management client 132, 133 as shown in FIG. 1; A performance state management server 112 that manages performance events generated from the management clients 132 and 133 or the network management systems 122 and 123, and basic information (configuration form, physical characteristics, identifiers, etc.) of each communication session; In addition, it consists of a communication session state management database 113 for storing the failure status information according to the failure event and the performance status information according to the performance event.

Next, a process of processing the failure event by the failure state management server 111 will be described in detail with reference to the flowchart shown in FIG. 2.

When the failure state management server 111 receives a failure event from the HiNET network management system 121, the ATM network management system 122, and the IP network management system 123 (S21), it is shown in <Table 1>. Classify the received event based on the fault event interface called externally.

Event calling system Failure Event Type (Fault Event Interface) Detailed Properties for Managing Communication Session Failure States NAP Status NFC status CC OAM activation status CC alarm status IP NAP Status ATM NMS ATM connection failure notification (F1) ○ ATM NMS ATM connection failover notification (F2) ○ ATM NMS ATM connection failover failure notification (F3) ATM NMS ATM port failure notification (F4) ○ ○ ATM NMS ATM port failover notification (F5) ○ HiNETNMS HiNET Port Failure Notification (F6) ○ ○ HiNETNMS HiNET port failover notification (F7) ○ ○ IP NMS IP Endpoint Failure Notification (F8) ○ IP NMS IP endpoint failover notification (F9) ○ ISNM orHelpDesk ATM Connect CC OAM Activation Request (F10) ○ ISNM orHelpDesk ATM Connection CC OAM Deactivation Request (F11) ○ ATMNMS ATM Connection CC Alarms (F12) ○

<Table 1> Correlation between communication session failure event and communication session failure status

Referring to <Table 1>, the event call system represents a lower network management system or a management client system that generates a fault related event, and the fault event interface calls for handling the fault related event in a fault state management server. Interface, and detailed attributes for managing a communication session failure state indicate failure state attributes in which an operation state thereof is changed when the failure-related event is received.

As shown in Table 1, in the present invention, a failure state of a communication session is largely composed of a combination of five operational state attributes.

First, a communication session corresponding to a connection between subscriber ports or between trunk ports is modeled and represented by the concept of a network flow connection (NFC). The operational state of the communication session is represented by the fault state of the NFC attribute, and any type of fault on the connection path between ports is reflected as the NFC fault state. In this case, the communication port management system (CSM) manages the exchange port accommodated by a network access point (NAP) attribute called a network access point, while the operational state of the port is expressed through a failure state of the corresponding NAP attribute. Since there can be multiple NFCs (connections) in one NAP (port), NAP failure implicitly means all NFC failures belonging to that point, which is actually a failure of the subscriber access port, i.e. the user port. This is because the failure of all connections belonging to.

In addition to the NFC failure state that represents the operational state of the communication session, the CC OAM activation state and the CC alert state are each treated and managed as separate failure attributes for the communication session including the ATM connection. And finally, if the communication session is a connection providing an Internet access service, IP NAP information is configured by modeling an IP endpoint for generating a subscriber logical interface in the IP relay router where the session is terminated. The failure state management server 111 includes an IP NAP failure state as well as a failure state management domain of a communication session to determine an operation state of the Internet access service.

Looking at the relationship between the failure event interface type and the detailed attributes for managing the communication session failure state, referring to <Table 1>, when the F1, F2 failure event interface is called, the NFC state of the corresponding session is changed, and F4, F5 When a fault event interface is called, it changes the NAP state of the corresponding port. In the same manner as described above, the NAP state, NFC state, CC OAM enabled state, CC alarm state, and IP NAP state are appropriately changed for each fault event interface call. The communication session state management database 113 stores the NAP state, the NFC state, the CC OAM activation state, the CC alarm state, and the IP NAP state for each communication session and network access point.

Referring to FIG. 2 again, a failure event processing process of the failure state management server 111 will be described. The failure state management server 111 may notify of a failure event received based on a failure event interface called. The event is classified into a CC activation control event and a CC alarm event for a continuity check (hereinafter referred to as CC) maintenance function for an ATM connection (S22).

Here, the failure state management server 111 classifies as a failure event notification event when failure event interfaces F1 to F9 are called from the network management systems 121, 122, and 123, and a failure event from the session management client system 132, 133. When the interfaces F10 and F11 are called, they are classified as CC activation control events, and when the failure event interface F12 is called from the ATM network management system 122, they are recognized as CC alarm events.

Meanwhile, when the failure event received as a result of the event classification is a CC activation control event triggered by the failure management system 133 or the integrated network management system 132 which is a session management client system, the failure state management server 111 communicates with the communication. The CC OAM activation state information of the corresponding communication session is collected from the session state management database 113 (S220), and the appropriateness of the received control event is checked (S221). That is, the communication session is in the current CC OAM activation state. If an event (F10) for requesting the connection CC OAM activation is called or an event (F11) for requesting the ATM connection CC OAM deactivation is called in the current CC OAM deactivation state, it is determined to be inappropriate (N), and conversely, a communication session Event (F11) is called requesting ATM connection CC OAM deactivation with the current state of CC OAM enabled, or the current state is CC OAM disabled. When the ATM connection CC event (F10) requesting the OAM activation in the call is determined (Y) to be appropriate and proceeds to the next step (S222).

In S222, the failure state management server 111 calls a control operation for activating or deactivating CC OAM to the ATM network management system ATM NMS, and if the call succeeds (Y in S222), manages the communication session state. After changing the CC OAM activation state of the database 113 (S223), the event processing ends. The end of the control event processing automatically informs the session management client system that triggered the event whether the control operation succeeded or failed.

If the failure event received as a result of the event classification in step S22 is a CC alarm event, the failure state management server 111 collects CC alarm state information of the corresponding communication session from the communication session state management database 113 (S230). ), The appropriateness is checked (S231). In step S231, it is determined that the event call requesting processing that overlaps with the currently set CC alarm state is not appropriate (N), otherwise it is determined to be proper (Y), and the next step is step 232. Proceed.

In S232, the failure state management server 111 changes the CC alarm state stored in the communication session state management database, and sends a CC alarm event to the failure management system 133 or the integrated network management system 132 which is a session management client system. The event processing is terminated by notifying (S233).

Here, the failure state management server 111 notifies the CC alarm event to the failure management system 133 when the communication session is connected between subscriber ports, and integrates the CC alarm event when the communication session is connected between trunk ports. Notify the network management system 132.

On the other hand, if it is determined that the failure event is a failure-related notification event as a result of the event classification in step S22, the failure state management server 111 from the communication session state management database 113, NAP, NFC, IP of the communication session Collect NAP state information (S240), and check the appropriateness (S241), the type of the failure-related notification event is accepted in the current NAP, NFC, IP NAP state stored in the communication session state management database 113 If it is possible event, that is, if it is possible to transition to a new state when receiving an event generated in the current state (Y), it is determined that it is appropriate (Y), detailed attribute information corresponding to the fault-related notification event type, that is, NAP state, NFC State, IP NAP state is changed (S242).

Then, the failure state management server 111 terminates event processing without external propagation, if the event call system that triggered the failure notification event is IP network management (Y in S243), otherwise activates the failure notification event. If the event call system is not the IP network management system, that is, the ATM network management system or the HiNET network management system (N in S243), the event processing is propagated after propagating a failure event to a failure management session managing client (S244).

Here, the failure state management server 111, if the subject of the communication session (NFC) or network access point (NAP) related to the failure notification event is a service subscriber, and is registered in the customer network service, the failure notification event is sent to the customer. It propagates to the network management system 131 and notifies the integrated network management system 132 of the failure notification event if the subject of the communication session and network access point related to the failure notification event is the network manager.

Next, a process of processing the performance event by the performance state management server 112 will be described in detail with reference to the flowchart shown in FIG. 3.

In the present invention, performance-related events of a communication session are classified into activation control events for performance management functions of ATM connections, performance management threshold control events and performance management alarm events in terms of ATM or IP, and the performance management functions of the ATM connections. For the activation control event, PM OAM activation, traffic load data logging activation, and UPC (Usage Parameter Control) data logging activation control event are defined.

The relationship between the communication session performance related event and the communication session performance state attribute is shown in Table 2.

Event calling system Performance Event Type (Performance Event Interface) Detailed attributes for managing communication session health PM OAM activated Traffic data logging enabled UPC data logging enabled state ATM performance threshold setting & alarm status IP Performance Threshold Setting & Alarm Status ISNM orHelpDesk ATM Connection PM OAM Activation Request (P1) ○ ISNM orHelpDesk ATM Connection PM OAM Deactivation Request (P2) ○ ISNM orHelpDesk ATM Connection Traffic Load Datalogging Activation Request (P3) ○ ISNM orHelpDesk ATM Connection Traffic Load Data Logging Disable Request (P4) ○ ISNM orHelpDesk ATM connection UPC data logging activation request (P5) ○ ISNM orHelpDesk ATM Connection UPC Data Deactivation Request (P6) ○ ISNM orHelpDesk Setting ATM Port / Connection Performance Metrics Thresholds (P7) ○ ATMNMS ATM Port / Connection Performance Alarms (P8) ○ HelpDesk Set IP Endpoint Performance Management Metrics Threshold (P9) ○ IPNMS IP Endpoint Performance Alert (P10) ○

<Table 2> Correlation between communication session performance event and communication session performance attribute

As shown in FIG. 3, when the performance related event is received (S40), that is, when a specific performance event interface is called from an external system, the performance management server 112 is based on the interface of the performance related event called. Performance management activation control event, performance management alarm event, performance management threshold control event is classified (S41).

When the failure management system 133 or the integrated network management system 132, which is the session management client, calls the performance event interface P1 to P6 of the performance management server 112, it is activated by the performance management server 112. After that, the health management server 112 collects the performance state attributes of the corresponding communication session, that is, PM OAM activation state information, traffic data logging activation state information, and UPC data logging activation state information. Check (S421).

As a result of the check, if it is determined that each state information according to the attribute is changeable according to the type of performance event received in the current performance state (Y in S421), the ATM network management system 122 is determined to have appropriateness. Calls the performance management activation control operation. That is, the performance state management server 112 calls the PM OAM activation control operation of the ATM network management system 122 when the performance event interface P1 or P2 is called, and when the performance event interface P3 or P4 is called Calls the traffic data logging activation control operation of the ATM network management system 122, and calls the UPC data logging activation control operation of the ATM network management system 122 when the performance event interface P5 or P6 is called.

Then, if the call result is successful (Y in S423), the performance state management server 112 based on the received performance event type and the current activation state, the current performance stored in the communication session state management database 113. After changing the management activation state (S424), the event processing ends. Once the activation control operation of the ATM network management system 122 is called, the call result is automatically returned to the client system at the end of event processing regardless of success or failure.

On the other hand, if the operation management function for performance management is activated for a specific session including the ATM connection through the above-described control procedure, the client of the service management layer, that is, the integrated network management system 132 or the failure management system 133 Performance based on a threshold control event to the health management server 112 to set thresholds for receiving alerts for performance management metrics collected and managed by the underlying network devices for performance management of ATM connections, ports, and IP endpoints. Calling the event interface P7 or P9 transmits a threshold setting item and a threshold value (upper limit / lower limit).

Accordingly, the performance state management server 112 proceeds to step S431 according to the event classification result in step S41 to check the adequacy of the performance management threshold control event, the integrated network management system 132 or the failure management system ( If it is determined that the threshold setting item information transmitted from 133 is an approved threshold setting item (Y in step S431), the network management system that is the control target of the performance management threshold control event is analyzed (S432), and the ATM network management is performed. Call the performance management threshold operation of the system 122 (S4321), or call the performance management threshold control operation of the IP network management system 123 (S4322).

That is, through the above-described steps, the performance state management server 112 calls the performance management threshold control operation of the ATM network management system 122 when the performance event interface called in step S40 is P7, and calls the performance event interface. If P9 is called the performance management threshold control operation of the IP network management system 123.

Subsequently, the performance state management server 112 controls the performance management threshold control state and threshold value of the communication session stored in the communication session state management database 113, if the above-mentioned call in steps S4321 and S4322 is successful (Y in S433). After changing the value (upper limit / lower limit), event processing ends (S434).

Meanwhile, the ATM network management system 122 or the IP network management system 123 collects performance management data by a performance management threshold control operation called and an upper limit or a lower limit of a threshold defined by comparing with a threshold set by the client. When passing, the performance management alert event is transmitted to the performance management server 112, in which case the performance event interface P8 or P10 of the performance management server 112 is called.

Accordingly, the performance state management server 112 proceeds to step S44 according to the event classification result in step S41 and collects the ATM alarm status information and IP alarm status information stored in the communication session state management database 113 to check adequacy. If the ATM alarm status information and the IP alarm status information stored in the communication session state management database 113 are transitionable, it is determined to be appropriate (Y in step S441).

According to the determination result, the performance state management server 112 based on the performance event interface type and the current performance alert state received in step S40, the ATM alarm status information and the IP alarm of the communication session state management database 113. After changing the state information (S442), the performance alert event is propagated to the associated session management client (S443).

In step S443, the performance state management server 111 sends the performance alert event to the failure management system 131 if the subject of the communication session (NFC) or network access point (NAP) related to the performance alert event is a service subscriber. Propagates and notifies the integrated network management system 132 if the subject of the communication session and network access point related to the performance alert event is the network manager.

2 and 3 described above, the present invention is a communication session in the client (customer network management system (CNM), integrated network management system (ISNM), failure management system (HelpDesk) existing in the service management layer Through the interaction with the lower network management system (HiNET network management system, ATM network management system, IP network management system) which is mediated by the state management system (CSM), information on the failure status of communication sessions occurring in various lower network devices and Health status information can be obtained and control of the activation of session maintenance functions, thresholds of performance alerts, and so on.

According to the communication session state management system in the ATM-based high-speed data network according to the embodiment of the present invention as described above, by grasping the operating state of various types of communication sessions established between the lower network devices, It is possible to facilitate the management of the state of the network and the operation of the communication session for each subscriber, and to facilitate the subsequent reconfiguration process or network reconfiguration procedure for performance improvement.

Accordingly, the present invention not only increases the availability and utilization efficiency of network devices in ATM-based high-speed data networks by using communication session failure state information, but also selectively activates maintenance functions and performance management items for performance management of communication sessions. It is possible to increase the operational efficiency by identifying and coping with the network performance by using the threshold control function.

On the other hand, the present invention is not limited to the above-described embodiment, but can be modified and modified within the scope not departing from the gist of the present invention, such modifications and changes should be regarded as belonging to the following claims. will be.

Claims (5)

A session management client existing in the service management layer; A lower network management system existing in the network management layer; And By configuring a communication session state management server that manages the failure state and performance state for the communication session based on the performance event and failure event for the communication session generated from the client and the lower network management system, When a session control event for the communication session occurs from the client, the communication session state management server controls the lower network management system to perform an operation operation of the network device according to the control event and reflects the result of the operation in a control state. And when a notification and alarm event occurs from the lower network management system, the communication session state management server changes a failure state or a performance alert state for the communication session. Management system. The method of claim 1, The communication session state management server includes a communication session state management database for storing fault state information and performance state information about a communication session according to the performance event and the failure event; A failure state management server for determining whether a failure event occurs from the lower network management system and changing failure state information stored in the communication session state management database; When a performance event occurs from the client system, it is determined whether it is appropriate, and a control operation for performing an operation according to the performance event is called from a corresponding lower network device through the network management system, and the result is the communication session state management database. A communication session state management system in an ATM-based high speed data network, characterized in that the performance state management server reflects the performance state information stored in the system. The method of claim 1, The failure state management server transfers the failure state information to a network access point (NAP) state, a network flow connection (NFC) state, a CC Continuity Check Operation and Maintenance (CAO) state, a CC alarm state, and an IP (Internet Protocol) NAP state. Communication session state management system in the ATM-based high speed data network, characterized in that the classification and management. The method of claim 1, The performance state management server classifies and manages the performance state information into PM OAM activation state, traffic data logging activation state, UPC data logging activation state, ATM performance threshold setting / alarm state, IP performance threshold setting / alarm state. Communication session state management system in ATM-based high speed data network. The method of claim 1, If the lower network management system generating the failure event is an ATM or HiNET network management system, the failure status management server changes the failure status information of the failure event and notifies the failure event to the client. Communication session management system based on high speed data network.