KR100273061B1 - Apparatus for interfacing between network system and switching system and the method thereof - Google Patents

Abstract

The present invention relates to a network system of a large public telecommunication network having a CORBA interface on a distributed processing platform and a matching device of an ATM switching period having an SNMP interface. In particular, a CORBA operation related to resource configuration, connection, and failure of a networking system is performed. Networking system and exchange period matching device and its function to convert the SNMP operation to the exchange and provide the function to convert the fault-related SNMP operation provided by the exchange to the CORBA format operation and to the networking system. It is about a method.

Description

Networking system and switching period matching device and method

The present invention provides an asynchronous transfer mode having a networking system having a common object request broker architecture (CORBA) interface and a simple network management protocol (SNMP) interface, which is a distributed processing platform. Mode, hereinafter referred to as ATM) is a device for matching operations occurring between exchanges.

Networking systems can be broadly divided into unit systems for service and unit systems for network management.

The unit system for service functions as a subscription and access for the customer to use the networking system, and the unit system for network management manages network resources and functions as a physical connection.

Therefore, the unit systems for network management need to interact with the exchange for network resource management, connectivity functions, and coping with failures in the network.

The network management sub-systems that need to interact with the exchange include a resource configuration manager for network resource management, a connection manager for connection functions, and a failure manager for handling failures occurring in the network.

An ATM switch having an SNMP interface is a switch capable of controlling a managed object (hereinafter referred to as MO) in the switch, which is a controllable network element for network operation such as a switch port through SNMP.

However, since the exchange only has an SNMP interface and the networking system uses an interface provided by the CORBA platform, there is a problem in that the interface must be matched between the two systems.

Accordingly, the present invention has been devised to solve the above-mentioned problems, and converts the CORBA operations related to resource configuration, connection, and failure of the networking system into SNMP operations, and delivers them to the exchange, and the failures provided by the exchange. The aim is to provide a networking system, a switching period matching device, and a method for providing a function of converting a related SNMP operation into a CORBA format operation and delivering it to a networking system.

1 is a block diagram of an apparatus of the present invention,

2 is an operation flowchart showing an actual connection operation of the matching device and the exchange period of FIG. 1;

3 is an operation flowchart showing a connection command processing operation of the matching device of FIG. 1;

4 is an operation flowchart illustrating an operation of reading port information of an exchange in the matching device of FIG. 1;

FIG. 5 is an operational flow diagram illustrating operation of the matching device of FIG. 1 to send a fault in the exchange to the networking system.

<Description of Symbols for Major Parts of Drawings>

10: networking system 20: switchboard

30: matching device 11: resource configuration manager

12: connection manager 13: failure manager

14: CORBA 21: SNMP

22: SNMP delegate 31: Networking system interworking part

32: matching device interface 33: exchanger interlocking portion

34: SNMP trap processing unit 35: SNMP trap

36: SNMP get / set command

In order to achieve the above object, the present invention provides an interworking device between a networking system on a CORBA platform and an ATM switch using an SNMP interface.

A networking system interworking portion that converts the CORBA operations related to resource configuration, connection, and failure of the networking system into SNMP operations and forwards them to the exchange;

An exchange interworking part for establishing, deleting, and changing a connection between two points of an exchange;

It features a SNMP trap processing unit that converts fault-related SNMP operations provided by the exchange into CORBA format operations and delivers them to the networking system.

In addition, in order to achieve the above object, the present invention manages the mapping table between the link endpoint information and the port of the exchange and establishes the information in the table in order to establish a connection between two points of the exchange issued from the networking system to the matching device. A first process of reading and deleting;

A second step of creating and deleting a table of connection attributes in the exchange by using a connection characteristic table index (upc index) to designate an attribute of the connection in the first step;

A third step of creating and deleting a connection in the exchange by creating a pathRouteEntry for the actual connection in the first step;

In the first step, a fault cause table is managed in order to receive a fault from the switch and send it to a networking system in relation to a fault, and a fourth process of searching for, inserting, and deleting fault information in the table.

The operation principle according to the present invention will be described in detail as follows.

There must be a device between the networking system that uses CORBA and the exchange that uses SNMP to match them.

The present invention is largely composed of two parts that work with networking systems and two parts that convert it to SNMP and transfer it to the exchange.

Interworking with the networking system is an interface in Interface Description Language (IDL), which is an interface provided by CORBA for each subsystem. Get off and receive information from the exchange.

The part that converts to SNMP and delivers it to the exchange uses the Management Information Base (hereinafter referred to as MIB), which contains information on the MO of the ATM exchanger with SNMP protocol, to exchange the request received from the networking system. It is a combination of SNMP get / set commands to the MO and passes it through the socket to the exchange.

The SNMP get command designates a specific MO in the exchange to read the value for the state of that MO and pass it to the networking system, or make it available to the matching device.

The SNMP set command changes the state of the MO by changing the value for the state of the MO in the designated exchange to the desired value in the networking system.

Hereinafter, embodiments of the present invention will be described in detail.

As shown in FIG. 1, the instructions coming from the networking system 10 are largely divided into those coming from the resource configuration manager 11, the connection manager 12, and the failure manager 13 according to a command object.

The resource configuration manager 11 issues a command to read the information of the switch and the port of the switch from the switch, and maps the link endpoint and the port information, which is logical network information generated by the networking system 10. When creating a table and deleting a link endpoint, the command deletes the corresponding port information from the mapping table.

The connection manager 12 designates two link endpoints of the exchange to issue a command to create, delete, and change a connection between the two points.

The failure manager 13 receives a failure and sends it to the networking system 10 in preparation for a failure occurring in the exchange, and issues a command to create a trap table for analyzing the received failure. Instructs it to add or delete a trap table when it is newly added or deleted.

Indeed, when the networking system 10 and the matching device 30 are driven, the subsystems of this networking are on the CORBA 14 platform, so that the networking for interworking with the networking system 10 of the matching device 30 is achieved. The system interworking portion 31 must have a CORBA interface 32, and the exchange interworking portion 33 interoperating with the exchanger 20 has a corresponding exchange 20 having the SNMP interface 21 and the corresponding exchange 20. You must know the authority to issue SNMP commands to.

In the switch 20, there is an SNMP delegate 22 that converts commands received by the SNMP interface 21 into operations inside the switch.

In addition, an SNMP trap daemon 34 that detects a disabled SNMP trap 35 generated at the exchange for fault management must be present in the same host as the process of the matching device 30, and an SNMP get / set command 36 An SNMP library is needed to send the socket to the exchanger 20 as a socket.

In the present invention, a process of performing a command received from the networking system 10 will be described with reference to FIG. 3 as a case of establishing a connection between two points of the switch 20.

The networking system 10 passes the connection information to the matching device 30 to establish a connection between the two points.

The matching device 30 converts the link endpoint information, which is a part of the connection information, into the port information in the switch 20 to which the actual connection is to be established using the mapping table between the link endpoint and the port of the actual switch 20. .301

Then, for the requested connection attribute, an upc index is created to store the connection attribute in the exchange 20 (302).

This index is used in the exchange to indicate a specific connection attribute. Since this is for the connection requested by the matching device 30, there should be no connection attribute corresponding to this index at the time of designation.

On the other hand, the exchange 20 maps this index to the requested connection attribute and stores it in the connection attribute table, and uses this index as an identifier of the connection attribute.

Therefore, in the present invention, each time a connection request comes in, an upc index is generated to allow the exchange 20 to know the attributes of the requested connection.

After the index is generated, the device checks the directionality of the connection (303), and if the requested connection is not unidirectional or forward connection even in unidirectional connection, forward connection (304), or reverse connection (305). Set.

If the requested connection is bidirectional (306), if the properties of the forward and reverse connections are different (307), a new upc index is created (308); otherwise, a reverse connection is created with the previous upc index. (309).

A detailed process for creating a connection will be described with reference to FIG. 2.

The function for creating a connection sends a creation request to the exchange for upcContractEntry, which is an entry of a table having a content of a connection attribute in the exchange, with the specified upc index to SNMP (201).

When upcContractEntry is generated, the property of the connection is specified (202), and then the generated upcContractEntry is validated (203).

After you specify the connection properties, you create a real connection.

At this time, the connection is made by creating a pathRouteEntry which is an entry of a table relating to the connection of the exchange 20.

The connection creation function sends the send / receive port and the virtual path identifier (hereinafter referred to as VPI) of the requested connection to the exchange 20 together with the pathRouteEntry creation request (204).

After the port and virtual path identifier of the connection are specified, the pathRouteEntry is validated after informing the exchange of the upc index of the connection (205) so that the connection attribute for the connection can be found in the previously specified upcContractEntry (206).

An operation related to resource configuration will be described with reference to FIG. 4, for example, reading information on a designated port from an exchange.

After receiving the designated port, read it with SNMP get command.

According to the order of FIG. 4, first, a maximum reception virtual path identifier (receiveMaxVpi) of a designated port is read (401), and a maximum reception bandwidth (receiveMaxBandwidth) is read (402).

Similarly, the transmitting end reads the transmission maximum virtual path identifier (transmitMaxVpi) of the designated port (403), and then reads the transmission maximum bandwidth (transmitMaxBandwidth) of the designated port (404).

Then, the cell delay variation (hereinafter referred to as CDV) of the designated port is read (405).

Finally, the port policy of the designated port is read (406), and the result is sent to the networking system.

Regarding a failure, a process of receiving a failure from the switch 20 and sending the failure to the networking system 10 will be described with reference to FIG. 5.

The device makes a socket connection with the exchanger 20 when driven (501).

This socket connection waits for a trap signal to be sent in case of a failure in the exchange 20 (502).

When a trap arrives (503), the trap is received (504), the received trap is interpreted (505) to identify the failure, and the failure cause that matches the failure is found using the failure cause table (506).

A link endpoint that maps to the failed port in switch 20 is then identified (507) and information about the failure is sent to networking system 10 (508).

Other commands sent by the networking system 10 to the switch 20, such as deleting / modifying a connection or reading information of the switch, are likewise made up of several SNMP get / set commands 36.

As described in detail above, the present invention changes the structure of a networking system by changing a command sent from a networking system on a CORBA platform to a Fore exchange from a CORBA interface description language that is an interface of the networking system to an SNMP form that is an interface of the exchange. It can be matched to a Fore exchange, and it can also interface with networking systems through existing SNMP commands.

Thus, the networking system does not have to have an interface to a specific exchange and thus allows the networking system to match with multiple exchanges that differ in operation within the exchange. And it is possible to improve the efficiency of the networking system by matching with these different exchange and networking system.

In addition, from a carrier's perspective, when introducing an ATM exchanger having a heterogeneous interface, by using the matching device defined in the present invention, it is possible to improve the economics of the communication service by providing a quick communication service.

In addition, preferred embodiments of the present invention are disclosed for the purpose of illustration, and those skilled in the art will be able to make various modifications, changes, additions, etc. within the spirit and scope of the present invention, such modifications and modifications belong to the following claims Should be seen.

Claims (6)

In an interworking device between a networking system on a CORBA platform and an asynchronous transfer mode (ATM) exchange using a simple network management protocol (SNMP) interface, A networking system interworking portion that converts the CORBA operations related to resource configuration, connection, and failure of the networking system into SNMP operations and forwards them to the exchange; An exchange interworking part for establishing, deleting, and changing a connection between two points of an exchange; Networking system and switching period matching device, characterized in that it comprises an SNMP trap processing unit for converting the fault-related SNMP operation provided by the exchange to the CORBA format operation and forwarded to the networking system. Managing a mapping table between the link endpoint information and the ports of the exchange, and reading and deleting information from the table to establish a connection between two points of the exchange issued from the networking system to the matching device; A second step of creating and deleting a table of connection attributes in the exchange by using a connection characteristic table index (upc index) to designate an attribute of the connection in the first step; A third step of creating and deleting a connection in the exchange through a pathRouteEntry for the actual connection in the first step; And a fourth step of managing a failure cause table and retrieving, inserting, and deleting failure information from the table in order to receive a failure from the switch and send it to a networking system in relation to the failure in the first step. Period matching method. The method of claim 2, The first process, A first step of converting link endpoint information, which is part of the requested connection information, into port information at the exchange to which an actual connection is to be established using a mapping table between the link endpoint and a port of the actual exchange; Generating a connection property table index for storing the connection property in the exchange for the requested connection property; Creating an index, and then checking the directivity of the connection; A fourth step of establishing a forward connection if the requested connection is not one-way or even in one direction; On the other hand, if the requested connection is a unidirectional or reverse connection, a fifth step of establishing reverse connection; A sixth step of determining whether the requested connection is bidirectional; A seventh step of determining whether the attributes of the forward and reverse connections are different when the requested connection is bidirectional; An eighth step of creating a new connection characteristic table index if the attributes of the forward and reverse connections are different; On the other hand, if the attributes of the forward and reverse connections are the same, the networking system and the switching period matching method, characterized in that the sequential operation in the ninth step to establish the reverse connection to the previous connection characteristics table index. The method of claim 2, The second process, A first step of reading a reception maximum virtual path identifier value of a designated port; Reading a maximum receive bandwidth value of a specified port; A third step of reading the transmission maximum virtual path identifier value of the designated port also for the transmitting end; A fourth step of reading the transmission maximum bandwidth value of the designated port; A fifth step of reading a cell delay variation value of a designated port; A method of matching a switching period with a networking system, characterized in that the sixth step of reading a port policy value of a designated port and then sending the result to the networking system. The method of claim 2, The third process, In the function for creating a connection, the first step of sending a creation request for a connection property information entry (upcContractEntry), which is a table having contents of connection properties in the exchange, to a simple network management protocol having a specified connection property table index; A second step of specifying an attribute of a corresponding connection when the connection characteristic information entry is generated; Validating the generated connection characteristic information entry; Sending a send / receive port and a virtual path identifier of the requested connection to the exchange with a connection path entry creation request; A fifth step of designating a port and a virtual path identifier of the connection, and then informing the exchange of the connection property information index of the connection so that the connection attribute for the connection can be found in the previously specified connection path entry; And a sixth step of validating the generated connection characteristic path entries. The method of claim 2, The fourth process, Making a socket connection to receive a trap for a failure of the exchange; A second step of waiting for a trap to be sent in the event of a failure at the exchange via this socket connection; A third step of determining whether a trap is coming; A fourth step of receiving the trap when the trap comes; A fifth step of interpreting the received trap; A sixth step of finding out the interpreted fault, finding a fault cause for the fault, and using the fault cause table; A seventh step of finding a link endpoint mapped to the failed port in the exchange; An eighth step of sending information about the failure to the networking system; If the trap is not received in the third step, the network system and the switching period matching method, characterized in that the sequential operation in the ninth step to terminate the program.