KR100418403B1 - Gateway for Interworking Communication System of CORBA And NON_CORBA Circumstance - Google Patents

Abstract

The gateway for interworking a communication system of a CORBA and a NON_CORBA environment according to the present invention processes a message output from a NON_CORBA environment, receives a message distribution block for processing a message output from a CORBA environment, and a message output from a CORBA environment. CORBA message control block for forwarding and forwarding, request / response message control block for forwarding messages from the message distribution block to the CORBA message control block, or for forwarding messages from the CORBA message control block to the message distribution block, and CORBA messages. It stores the notification message control block that receives the message delivered from the control block and delivers it to the message distribution block, an interface library related to one or more protocols and a service library related to one or more applications, and stores the necessary libraries. It consists of a relay knowledge repository that is optionally provided in the distribution block, CORBA message control block, request / response message control block, and notification message control block, so that the communication system of CORBA environment and NON_CORBA environment can be linked using a single gateway. do.

Description

Gateway for Interworking Communication System of CORBA And NON_CORBA Circumstance}

The present invention relates to a communication system of a CORBA (Common Object Request Broker Architecture) environment and a NON_CORBA environment, and more particularly, to a gateway for interworking a communication system of a CORBA and a NON_CORBA environment having an improved structure of one interworking gateway. .

CORBA is a structure and specification for creating, distributing, and managing distributed program objects on a network. It allows programs located at different locations on the network and developed by different vendors to communicate through an interface broker. . CORBA was developed by a developer federation called OMG. Both ISO and X / Open have licensed CORBA as the standard structure for distributed objects (also known as components), and CORBA 2.0 is now up to date.

The core concept of CORBA is the Object Request Broker (ORB). ORB support for client and server networks of heterogeneous computers means that a client program (which can be an object itself) can be derived from a server program or object without knowing where the server is in a distributed network or what interface the server program has. That means you can request a service. To establish requests and responses between ORBs, programs use the General Inter-ORB Protocol (GIOP) and the Internet Inter-ORB Protocol (IIOP) on the Internet. IIOP maps GIOP requests and responses to each computer's Internet Transmission Control Protocol (TCP) layer.

To date, the gateway developed for interworking communication system of CORBA environment and NON_CORBA environment has been implemented with fixed interface and information model. Therefore, each interworking gateway for each protocol was implemented, and accordingly, protocols and applications had to be implemented in independent pairs.

Therefore, when the interface is changed due to the upgrade of the system, the application of the interlocking gateway system must be newly modified or updated according to the changed matter.

Here, the CORBA environment is a common object request broker architecture (Common Object Request Broker Architecture), the object request broker (ORB: Object Request Broker) established by the Object Management Group (OMG), a standardization body of object type technology Standard specification.

CORBA 1.1 was completed in 1991 by a joint proposal from HP and Sun Microsystems. In 1994, an extension specification for CORBA 1.1, jointly proposed by three of HP, Sun Microsystems and IBM, was released as CORBA 2.0. CORBA 2.0 is an ORB specification that enables interoperability between different platforms. This specification is expected to spread the distributed object type information technology in which most of the developed systems are interconnected and treated as one system on most platforms such as Windows 95, Windows NT, Unix, Macintosh, and OS / 2. It's happening.

1 is a block diagram showing the structure of a gateway applied to a communication system of a conventional CORBA environment and a NON_CORBA environment. Referring to FIG. 1, a plurality of gateways 21-24 should be provided to interwork a CORBA environment 10 and various types of NON_CORBA environments 31-34.

For reference, in FIG. 1, SNMP is an abbreviation of Simple Network Management Protocol, and is a network agent such as a network management protocol (RFC 1157) of TCP / IP, a router or a hub. It is adopted as a standard communication protocol used to send network management information to a network manager. It was developed based on the Simple Gateway Management Protocol (SGMP), the gateway management protocol of TCP / IP. CMIP is an abbreviation of Common Management Information Protocol, a protocol based on international standards (ISO Recommendations), and is applied to the application layer of OSI, and is a basic procedure of management operation information between systems connected to communication lines. TL1 is an abbreviation of Transport Layer interface. The transport layer is located at the fourth layer of the OSI modem and is responsible for the accurate delivery of quality of service and information.

However, the conventional interworking gateway described above is difficult to separate each protocol and application, so when interworking a new protocol, it is very difficult to reuse an application previously applied by another protocol.

Therefore, in order to operate a communication system normally, there has been a problem of reimplementing an application according to a new protocol, and there is a problem that the number of interworking gateways must be implemented as many as the number of new protocols.

The present invention has been made to solve the above problems, and provides a gateway for interworking the communication system of CORBA and NON_CORBA environment that can interwork the communication system of CORBA environment and the NON_CORBA environment using one gateway. There is a purpose.

1 is a block diagram showing the structure of a gateway applied to a communication system of the conventional CORBA environment and NON_CORBA environment.

2 is a block diagram illustrating a schematic structure of a gateway for interworking a communication system of a CORBA environment and a NON_CORBA environment according to the present invention;

3 is a block diagram illustrating a detailed structure of a gateway for interworking a communication system of a CORBA environment and a NON_CORBA environment according to the present invention;

4 is a block diagram illustrating the configuration of the message distribution block shown in FIG.

5 is a block diagram illustrating the configuration of the request / response message control block shown in FIG. 3;

FIG. 6 is a block diagram illustrating a CORBA message processing block shown in FIG. 3; FIG.

7 is a block diagram illustrating a notification message control block shown in FIG. 3;

8 is a block diagram of the relay knowledge store shown in FIG. 3;

* Description of the symbols for the main parts of the drawings *

10: CORBA Environment 21-24: Gateway

30: NON_CORBA environment 31: SNMP environment

32: CMIP environment 33: TL1 environment

34: Proprietry Environment 40: Gateway

50: request / response message control block 51: basic thread

52: extended thread 60: message distribution block

61: request / synchronous response processing unit 62: case report / asynchronous response processing unit

70: relay knowledge storage 71: interface library unit

71a: CMIP encryption / decryption library

71b: SNMP encryption / decryption library

71c: TL1 encryption / decryption library

71d: CORBA encryption / decryption library

71e: Proprietry Encryption / Decryption Library

71f: XDR encryption / decryption library

72: service library unit 72a: timer

72b: Incident Reporting Filtering Library 72c: Message Store

72d: Mapper Library 72e: Message Distribution Library

80: CORBA message control block 81: CORBA message processing unit

90: notification message control block 91: the main thread

92: extended thread

The gateway for interworking the communication system of CORBA and NON_CORBA environment according to the present invention for achieving this object, the message distribution block for processing messages output from the NON_CORBA environment, the message output from the CORBA environment, CORBA environment CORBA message control block that receives and delivers the messages output from the server, and messages delivered from the message distribution block to the CORBA message control block, or request / response messages that deliver messages from the CORBA message control block to the message distribution block. Stores a control block, a notification message control block that receives messages delivered by a CORBA message control block and forwards them to a message distribution block, an interface library associated with one or more protocols, and a service library associated with one or more applications; The library is constructed into a message distribution block, CORBA message control block, a request / reply message control block, the relay knowledge store to selectively provide the notification message control block.

The message distribution block preferably includes a request / synchronous response processing unit for processing a message in a NON_CORBA environment, and an event reporting / asynchronous response processing unit for processing a message in a CORBA environment.

In addition, the request / response message control block or the notification message control block is preferably composed of one live primary thread and multiple extended threads that are created one per incoming message and are destroyed after executing the message as long as the process exists. Do.

In addition, the relay knowledge repository is composed of one or more interface library parts written with mappers related to protocols and one or more service library parts related to applications, and each component is configured to facilitate adding / deleting libraries, and the interface library part includes CMIP encryption / It is optionally included among decryption library, SNMP encryption / decryption library, TL1 encryption / decryption library, CORBA encryption / decryption library, Proprietry encryption / decryption library, XDR encryption / decryption library, and service library part includes timer, event report filtering library, and message store. It is optionally included among the mapper library and the message distribution library.

According to the characteristics of the present invention, when a communication system of a NON_CORBA environment having a plurality of various protocols and information models under a distributed environment and a communication system of a CORBA environment, it supports a necessary library by separating the protocol and the application, Even if the interface changes, the corresponding application does not change.

In addition, it supports the function of reflecting the change of information online when distributing messages, and minimizes the load by using a thread pool in the processing routine of the request / response message and the notification message. It can improve the efficiency of the overall operation of the gateway.

Hereinafter, a configuration and operation of a gateway for interworking a communication system of a CORBA and a NON_CORBA environment according to the present invention will be described in detail with reference to the accompanying drawings.

2 is a block diagram illustrating a schematic structure of a gateway for interworking a communication system between a CORBA environment and a NON_CORBA environment according to the present invention, and FIG. 3 illustrates a communication system between a CORBA environment and a NON_CORBA environment according to the present invention. A block diagram showing the detailed structure of a gateway.

2 and 3, a gateway for interworking a communication system of a CORBA environment and a NON_CORBA environment according to the present invention processes a request message and a synchronization response message output from the NON_CORBA environment 30, and generates a CORBA environment 10. Message distribution block (60) for processing the event report and asynchronous response message output from the; and CORBA message control block (80) for receiving the CORBA message output from the CORBA environment (10) to output the event report and asynchronous response message And request / response message control for forwarding the message delivered in the message distribution block 60 to the CORBA message control block 80 or for forwarding the message forwarded in the CORBA message control block 80 to the message distribution block 60. A block 50, a notification message control block 90 that receives the message delivered by the CORBA message control block 80 and delivers it to the message distribution block 60; It stores the interface library related to the protocol and the service library related to a plurality of applications. The necessary libraries are stored in the message distribution block 60, the CORBA message control block 80, the request / response message control block 50, and the notification message control block. It consists of a relay knowledge repository 70 optionally provided to 90.

Here, the message distribution block 60 is a request / synchronous response processing unit 61 for processing the request message and the synchronization response message of the NON_CORBA environment 30, as shown in Figure 4, the event report of the CORBA environment 10 And an event report / asynchronous response processor 62 for processing the asynchronous response message.

In addition, the request / response message control block 50 applies a thread pool concept as shown in FIG. 5 to generate one basic thread 51 that is alive and one for each received message as long as the process exists. It is preferably composed of multiple extension threads 52 which are then destroyed after performing the message.

In addition, the CORBA message control block 80 preferably includes one CORBA message processing unit 81 as shown in FIG.

In addition, as shown in FIG. 7, the notification message control block 90 is generated by applying a thread pool concept, one basic thread 91 that is alive and one for each received message as long as the process exists. It is preferable that it consists of multiple threads 92 that are destroyed after performing the message.

In addition, the relay knowledge store 70 is preferably composed of an interface library unit 71 in which a mapper related to a protocol is written and a service library unit 72 related to an application as shown in FIG. 8. Here, the interface library unit 71 includes a CMIP encryption / decryption library 71a, an SNMP encryption / decryption library 71b, a TL1 encryption / decryption library 71c, a CORBA encryption / decryption library 71d, and a Proprietry encryption / decryption library. 71e, an XDR encryption / decryption library 71f, and the service library unit 72 includes a timer 72a, an event report filtering library 72b, a message store 72c, a mapper library 72d, and a message distribution. The library 72e is included.

Let's look at the overall operation of the gateway for interworking the communication system of the CORBA environment and the NON_CORBA environment according to the present invention configured as described above.

First, as shown in FIGS. 2 and 3, the request message and the sync response message output from the NON_CORBA environment 30 are delivered to the message distribution block 60. The message distribution block 60 processes an event report and an asynchronous response message output from the Non_CORBA environment 30 by selectively using a library stored in the relay knowledge repository 70 and delivers it to the request / response message control block 50. . The request / response message control block 50 optionally delivers the message delivered by the message distribution block 60 to the CORBA message control block 80 using a library stored in the relay knowledge store 70. Accordingly, the CORBA message control block 80 may link the event report and asynchronous response message output from the Non_CORBA environment 30 to the CORBA environment 10.

2 and 3, the request message and the sync response message output from the CORBA environment 10 are forwarded to the CORBA message control block 80. CORBA message control block 80 optionally forwards the incident report and asynchronous response message to notification message control block 90 using the library stored in relay knowledge store 70 with the received message. Notification message control block 90 forwards the received message to message distribution block 60. The message distribution block 60 may process an event report and an asynchronous response message output from the CORBA environment 10 and interwork with the corresponding language environment of the Non_CORBA environment 30.

Hereinafter, a detailed operation of each component of the gateway for interworking a communication system of a CORBA environment and a NON_CORBA environment according to the present invention shown in FIG. 3 will be described in detail.

The request / synchronous response processor 61 of the message distribution block 60 processes the request message and the synchronous response message of the NON_CORBA environment 30, and the event report / asynchronous response processor 62 reports the event of the CORBA environment 10. And handle asynchronous response messages. Here, the request / synchronous response processor 61 transmits / receives a request / synchronous response message with the NON_CORBA environment 30, and transmits / receives a request / synchronous response message with the request / response message control block 50. In this case, information for transmitting and receiving to the request / response message control block 50 is obtained from the relay knowledge store 70 through the mapper / service API. Meanwhile, the incident report / asynchronous response processor 62 receives the incident report / asynchronous response message from the notification message control block 90 and uses the mapper / service API obtained from the relay knowledge store 70 to configure the NON_CORBA environment 30. Send an event report / asynchronous response message.

In addition, the basic thread 51 of the request / response message control block 50 applies the thread pool concept so that the process is alive as long as the process exists, and one extended thread 52 is created for each received message. It has the property to be destroyed after executing the message. Here, the basic thread 51 receives the request message from the message distribution block 60, and if the received request message is a message in the form of a synchronous request message, transmits it to the extension thread 52, and a message in the form of an asynchronous request message. In case it receives a mapper / service API from the relay knowledge store 70 and sends an asynchronous request message to the CORBA message control block 80. On the other hand, the extension thread 52 created to receive the synchronization request message from the basic thread 51 is the synchronization received from the CORBA message control block 80 using the mapper / service API received from the relay knowledge store 70. Send and receive request / response messages. The extension thread 52 processes the synchronization request / response message received from the CORBA message control block 80 using a mapper / service API obtained from the relay knowledge store 70, and processes the synchronization response message in the message distribution block 60. To send.

In addition, the CORBA message processing unit 81 of the CORBA message control block 80 transmits / receives a request / synchronous response message with the request / response message control block 50, and relays the received request / synchronous response message to the relay knowledge store 70. Sends / receives request / response / event report messages with CORBA environment 10 using the mapper / service API of the mapper and service, and also maps / services request / response / event report messages received from CORBA environment 10. Using the API, the request / synchronous response message is generated and transmitted to the request / response message control block 50 or the event report / asynchronous response message is determined to be sent to the notification message control block 90 and transmitted.

In addition, the basic thread 91 of the notification message control block 90 applies a thread pool concept, and a process exists. The multithreaded 92 is created one per received message and then destroyed after executing the message. Has the property of being. Here, the primary thread 91 receives the event report / asynchronous response message from the CORBA message control block 80 and distributes it to the extension thread 92. The extension thread 92 is the default thread 91. In the NON_CORBA environment 30, a function of transmitting an event report / asynchronous response message to the message distribution block 60 by using the mapper / service API and the event report / asynchronous response message transmitted. If the desired information is not collected properly, the synchronous response message may be used to obtain additional information from the CORBA environment 10.

In addition, the interface library unit 71 of the relay knowledge store 70 includes a CMIP encryption / decryption library 71a, an SNMP encryption / decryption library 71b, a TL1 encryption / decryption library 71c, CORBA encryption / decryption library 71d, Proprietry encryption / decryption library 71e, and XDR encryption / decryption library 71f. The service library unit 72 includes a timer 72a, an event report filtering library 72b, Message store 72c, mapper library 72d, and message distribution library 72e.

In this case, when the operator adds / deletes an interface, interface libraries are provided with wrappers so that they appear as one on the screen, and each library is componentized to add / delete plug and play. Play).

As described above, according to the gateway for interworking a communication system of CORBA and a NON_CORBA environment according to the present invention, a system of a NON_CORBA environment having a plurality of various protocols and information models can be integrated into a CORBA environment and one interworking gateway under a distributed environment. have.

In addition, the separation of protocols and applications and the implementation of each protocol and application in units of service-based components can be implemented in a plug and play form to ensure reuse and scalability.

In addition, the processing routine of the request / response message and the notification message processing routine can be minimized by using a thread pool to improve the overall operation efficiency of the interlocking gateway.

Therefore, it is easy to standardize the internal program of the interlocking gateway, it is easy to develop the component by producing code conforming to the standard, and the quality of the software product according to the consistent information flow can be improved.

In addition, due to the separation of interface and information during the development of the gateway, it can be developed independently of the protocol of the network component.

Claims (5)

A message distribution block that processes messages output from the NON_CORBA environment, processes messages output from the CORBA environment, A CORBA message control block for receiving and delivering a message output from the CORBA environment; A request / response message control block for delivering a message delivered from the message distribution block to the CORBA message control block, or for delivering a message delivered from the CORBA message control block to the message distribution block; A notification message control block for receiving a message delivered from the CORBA message control block and delivering the message to the message distribution block; Stores an interface library related to one or more protocols and a service library related to one or more applications, and optionally provides the necessary libraries to the message distribution block, the CORBA message control block, the request / response message control block, and the notification message control block. Gateway for interworking communication systems in CORBA and NON_CORBA environments consisting of relay knowledge repositories. The method of claim 1, wherein the message distribution block, A request / synchronous response processing unit for processing the message of the NON_CORBA environment, Gateway for interworking communication system of CORBA and NON_CORBA environment consisting of an event reporting / asynchronous response processing unit for processing a message of the CORBA environment. The method of claim 1, wherein the request / response message control block or notification message control block, As long as the process exists, one live primary thread, Gateway for interworking communication system of CORBA and NON_CORBA environment consisting of multiple extension threads that are created one per incoming message and are destroyed after executing the message. The method of claim 1, wherein the relay knowledge store, One or more interface library sections with a mapper associated with the protocol, It consists of one or more service library parts related to the application, Gateway for interworking communication system of CORBA and NON_CORBA environment which are each configured to easily add / delete the libraries. The method of claim 4, wherein The interface library unit is optionally included among CMIP encryption / decryption library, SNMP encryption / decryption library, TL1 encryption / decryption library, CORBA encryption / decryption library, Proprietry encryption / decryption library, XDR encryption / decryption library, The service library unit is a gateway for interworking a communication system of CORBA and NON_CORBA environment, which is optionally included among a timer, an event report filtering library, a message store, a mapper library, and a message distribution library.