KR20010108868A - Method for connection deactivating of transmission system in network management system - Google Patents

Abstract

The present invention allows the network management system to periodically check the socket connection state with the transmission device, thereby improving the reliability of the event report transmitted from the transmission device and interworking the transmission device of the network management system to return the abnormal connection state to the normal connection state. The present invention provides a restoration method, the present invention comprises the first step of connecting to the client side when the connection request is received while waiting to open the socket on the server side; A second step of monitoring occurrence of an event after performing the first step; If the event does not occur in the second step, checking whether the connection is made and monitoring the occurrence of the event; A fourth step of performing an incident report by checking whether a connection occurs when an event occurs in the second step; If the third step and the fourth step are not connected, respectively, the fifth step of closing the socket and returning to the standby state is performed, thereby periodically checking the TCP / IP socket connection state, thereby ensuring the reliability of the event occurrence report by the transmission equipment. It is possible to restore the connection between the transmission equipment and the network management system in the event of abnormal socket operation.

Description

Method for connection deactivation of network management system {Method for connection deactivating of transmission system in network management system}

The present invention relates to interworking for data communication between a network management system and a transmission system, and in particular, by unilaterally transmitting data from a transmission device by granting a function of checking a connection state to the network management system. The present invention relates to a transmission interworking restoration method of a network management system suitable for increasing the reliability of an incident report.

In general, the network management system remotely monitors and manages the operation status of the transmission equipment. At this time, the events occurring in the transmission equipment should be reported reliably to the network management system, and it should be possible to quickly recover the abnormal operation of the client event processing daemon of the network management system.

Data communication between the network management system and the transmission device for performing the above function is performed by the client / server (Client / Server) structure through the TCP / IP (Transmission Control Protocol / Internet Protocol) socket. There are two types of TCP / IP socket connections, one of which is a command processing socket connection for processing a command to a transmitting device, and the other is an event processing socket connection for reporting an event when a sending device's event occurs.

Hereinafter, a socket connection between a network management system such as TNMS and a transmission device such as WDCS-800 will be described.

First, Figure 1 is a block diagram of the transmission equipment interworking function of the general network management system, Figure 2a is a block diagram of the command processing interworking function in Figure 1, Figure 2b is a block diagram of the event report interlocking function in Figure 1 to be.

As shown in FIG. 1, a transmission device interworking function of a general network management system includes a client command processing daemon 11 requesting a server for command processing and a client event processing daemon 12 for reporting the occurrence of an event on the server side. A network management system 10 for managing a communication network; Server command processing daemon 21 for performing command processing according to the command processing request from the client side, server event processing daemon 22 for reporting the occurrence of an event to the client side, and equipment monitoring daemon 23 for monitoring the operation status of each functional unit. It is provided with a transmission device 20 that is interlocked with the network management system (10).

Referring to the operation of the device according to the above configuration as follows.

First, in the command processing and event processing connection between the network management system 10 and the transmission device 20, the client command processing daemon (11) and the client event processing daemon (12) of the network management system (10) It becomes a client, and the server command processing daemon 21 and the server event processing daemon 22 on the transmission equipment 20 side become servers. That is, the transmission device 20 functioning as a server is configured to perform a service through a socket connection only when a management request on the network management system 10 side as a client occurs.

That is, when the network management system 10 manages the transmission device 20, the client command processing daemon 11 and the client event processing daemon 12 are started to transmit and receive management information, thereby transmitting the transmission device 20. The server command processing daemon 21 and the server event processing daemon 22 are requested.

As shown in FIG. 2A, when the client command processing daemon 11 of the network management system requests a connection to the server command processing daemon 21 of the transmission equipment, the server command processing daemon 21 sends a connection confirmation signal. The socket connection is performed by outputting to the client command processing daemon 11.

At this time, the TCP / IP socket connection is used for data transmission, and the server command processing daemon 21 of the transmission device operates in a standby state (Idle, not executing a command). It will wait on the socket to receive commands from it.

System calls to these sockets are done with read commands used by Unix systems. Since the read command returns an error signal when the client is in an abnormal connection state, by checking whether the error signal is returned, the server command processing daemon of the transmitting equipment is asynchronous with the client daemon of the network management system. Connection failure situation such as release) can be checked and the request for execution of the network management system can be handled.

When the socket connection is performed in the server / client structure as described above, the server command processing daemon 21 receives the command processing request from the client command processing daemon 11 and performs the command processing, and manages the result of the command processing on the network. It is passed to the client command processing daemon 11 of the system. When the operation according to the command processing request of the client command processing daemon 11 is completed, the client / server connection is released.

In addition, as shown in Figure 2b, the server event processing daemon 22 of the transmission equipment is to open the event processing socket and wait in advance for connection with the client event processing daemon 12 of the network management system.

Then, the client event processing daemon 12 of the network management system requests a connection, and the connection is performed, and the server event processing daemon 22 of the transmission device processes the asynchronous event generated in the equipment by the client event processing of the network management system. Report to daemon (12). At this time, the occurrence of the event reported by the server event processing daemon 22 to the client event processing daemon 12 is detected by the equipment monitoring daemon 23 and transmitted to the server event processing daemon 22.

Hereinafter, the connection restoration method of the network management system according to the prior art will be described.

First, Figure 3 is a flow diagram of a transmission device interlocking restoration method of a network management system according to the prior art.

As shown in FIG. 3, the connection restoration method of the network management system according to the prior art includes: a first step (ST11 to ST13) connected to a client side when a connection request is received while waiting for opening a socket on a server side; A second step (ST14) of monitoring an occurrence of an event after performing the first step (ST11 to ST13); A third step (ST15 to ST17) of performing an incident report by checking whether a connection occurs when an event occurs in the second step (ST14); If not connected in the third step (ST15 ~ ST17), and performs a fourth step (ST18) to close the socket and return to the standby state.

Referring to the operation of the method according to such a configuration as follows.

In the first step (ST11 ~ ST13), the client event processing daemon of the network management system opens a socket to receive a report of the occurrence of the event from the server event processing daemon of the transmission equipment (ST11). The socket opening is performed in a blocking mode that continuously waits until generation of data to be read.

When the socket is opened, the server event handling daemon waits for a connection request from the client event handling daemon to be entered (ST12). Thus, when a connection request is input from the client event handling daemon, the server event handling daemon outputs a signal confirming the connection to the client event handling daemon (ST13).

The server event processing daemon connected to the client event processing daemon in the first step (ST11 ~ ST13), receives the data from the equipment monitoring daemon in the second step (ST14) to check whether the event occurs.

Subsequently, in the third step (ST15 to ST17), if the occurrence of the event is not confirmed, that is, if no event occurs in the transmission equipment and no event occurrence data from the equipment monitoring daemon is input, the server event processing daemon passes after an appropriate delay time ( ST15) The work of checking whether an event occurs again is repeated.

Thus, when an event occurs in the transmitting device, the server event processing daemon checks whether it is connected to the client event processing daemon (ST16). When the connection with the client event processing daemon is confirmed in the step ST16, the server event processing daemon reports the occurrence of the event to the client event processing daemon (ST17).

If it is confirmed in step 3 (ST15 to ST17) that the connection with the client event processing daemon is not maintained (ST16), in step 4 (ST18), the server event processing daemon opens the socket opened for connection with the client. Close and return to the first step (ST11 ~ ST13) to open a new socket and wait for the connection with the client event handling daemon.

When the event occurrence report of the transmission device by the server event processing daemon is input as described above, the client command processing daemon may take an action according to the occurrence of the transmission device by sending an appropriate command to the server command processing daemon.

As described above, the transmission device interworking restoration method of the network management system according to the related art checks whether an occurrence of an event occurs in the transmission device when the transmission device and the network management system are connected, and confirms that the connection with the network management system is maintained when the event occurs. It is to report the occurrence of the incident to the network management system.

However, the transmission apparatus interworking restoration method of the network management system according to the related art as described above, because the server event processing daemon opens the blocking mode when the socket is opened in order to be connected to the client event processing daemon, it is confirmed that the socket connection state. Has the problem that it is only possible to send data to the socket (that is, write data calls).

In addition, when there is no event occurring in the transmission device for a certain time, the server event processing daemon of the transmission device has a problem that can not check the socket connection state of the client event processing daemon.

That is, if an attempt is made to reestablish a connection to a socket due to an abnormal operation of the client event processing daemon of the network management system, the server event processing daemon of the transmitting device does not respond when an event does not occur in the transmitting device.

Accordingly, the present invention has been proposed to solve the conventional problems as described above, an object of the present invention in the interworking between the network management system and the transmission equipment, the network management system periodically checks the socket connection state with the transmission equipment In order to improve the reliability of the event report transmitted from the transmission equipment and to restore the abnormal connection state to the normal connection state, the present invention provides a transmission device interworking restoration method of the network management system.

In order to achieve the above object, a transmission device interworking restoration method of a network management system according to the present invention includes a first step of connecting to a client side when a connection request is received while waiting for opening a socket on a server side; A second step of monitoring occurrence of an event after performing the first step; If the event does not occur in the second step, checking whether the connection is made and monitoring the occurrence of the event; A fourth step of performing an incident report by checking whether a connection occurs when an event occurs in the second step; If not connected in the third and fourth stages, the technical configuration is characterized in that the fifth step of closing the socket and returning to the standby state.

1 is a block diagram of a transmission equipment interworking function of a general network management system;

FIG. 2A is a detailed block diagram of an interlocking function in command processing in FIG. 1;

Figure 2b is a detailed block diagram of the interworking function when reporting an event in Figure 1,

3 is a flowchart of a transmission device interlocking restoration method of a network management system according to the prior art;

4 is a flowchart illustrating a transmission device interworking restoration method of a network management system according to an embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

10: network management system 11: the client command processing daemon

12: client event handling daemon 20: transmission equipment

21: server command processing daemon 22: server event processing daemon

23: equipment monitoring daemon

Hereinafter, with reference to the accompanying drawings, the configuration and operation of an embodiment according to the technical spirit of the transmission device interlocking restoration method of the present invention network management system as described above.

First, Figure 4 is a flow chart of the transmission device interlocking restoration method of the network management system according to an embodiment of the present invention.

As shown in FIG. 4, an embodiment of the present invention includes a first step (ST21 to ST23) connected to a client side when a connection request is received while waiting for opening a socket on a server side; A second step (ST24) for monitoring an occurrence of an event after performing the first step (ST21 to ST23); A third step (ST25 to ST26) of checking whether a connection is made and monitoring the occurrence of an event if an event does not occur in the second step (ST24); A fourth step (ST27 to ST28) of performing an incident report by checking whether a connection occurs when an event occurs in the second step (ST24); If not connected in the third step (ST25 ~ ST26) and the fourth step (ST27 ~ ST28), the fifth step (ST29) to close the socket and return to the standby state is performed.

Referring to the operation of the method according to such a configuration as follows.

In the first step (ST21 ~ ST23), the client event processing daemon of the network management system opens a socket to receive a report on the occurrence of the event from the server event processing daemon of the transmission equipment (ST21).

When the socket open is operated in the blocking mode as in the prior art, the socket open is kept in a waiting state when there is no data to be read in the read operation, so that the client event processing daemon of the network management system does not send data. It will be impossible to perform normal operations.

In other words, the client event processing daemon in the conventional network management system is waiting to receive data from the server event processing daemon in the transmitting device without sending data to the event processing connection socket. No data can be read from the socket, returning an error signal. At this time, the error signal returned by the Unix system is '-1'.

In contrast, the present invention reads data when the target data is read by performing a socket opening in a non-blocking mode, but returns an error signal when the target data does not exist. The returned error signal is '0' for Unix systems.

So when the socket is opened, the server event handling daemon waits for a connection request from the client event handling daemon (ST22). Thus, when a connection request is input from the client event handling daemon, the server event handling daemon outputs a signal confirming the connection to the client event handling daemon (ST23).

As described above, the server event processing daemon connected to the client event processing daemon in the first steps ST21 to ST23 receives data from the device monitoring daemon in the second step ST24 and checks whether an event has occurred.

If no event occurs in the second step ST24, the server event processing daemon checks whether the connection with the client event processing daemon is maintained in the third step ST25 through ST26 (ST25). Therefore, if it is confirmed that the connection with the client event processing daemon is not maintained, the server event processing daemon returns to the process of checking whether an event has occurred after a predetermined delay time has elapsed (ST26).

When the occurrence of the event is confirmed in the second step (ST24), the fourth step (ST27 ~ ST28) is confirmed whether the connection with the client event processing daemon (ST27). Therefore, if it is confirmed that the connection with the client event processing daemon is maintained, the server event processing daemon reports the event that occurred in the transmission device to the client event processing daemon of the network management system (ST28).

The two cases where the connection between the server event processing daemon and the client event processing daemon are not maintained are separated. One is a bad connection state without an event occurrence (ST25), and the other is a bad connection state during an event occurrence state. (ST27).

That is, if the client event handling daemon of the network management system disconnects or the client event handling daemon terminates, the server event handling daemon in the transmitting device cannot read data from the event handling socket and generates an error signal '0'. The server event handling daemon can see the connection status with the client event handling daemon.

If the connection failure state as in the above two cases, the server event processing daemon in the fifth step (ST29) closes the socket opened for connection with the client, returns to the first step (ST21 ~ ST23) to open a new socket and the client Wait for connection with the event handling daemon.

At this time, the server event processing daemon in the transmitting device reads data from the socket connected in the non-blocking mode to check the connection status of the socket without being affected by the client event processing daemon of the network management system.

Therefore, if the read system call through the event processing socket returns '0', the socket does not operate normally. Therefore, the server event processing daemon in the transmitting device closes the open event processing socket and the network management system. Waiting for a connection request from the client event handling daemon.

As such, when the transmission device and the network management system are connected in the non-blocking mode, the server event processing daemon checks whether an event occurs in the transmission device, and performs an operation of checking whether an event has occurred in the transmission device. By checking the connection status, it maintains a path to report the occurrence of the event to the network management system, and if the connection status of the event processing socket is bad, it is possible to close the open socket and open a new socket to perform the event occurrence report.

Although the preferred embodiment of the present invention has been described above, the present invention may use various changes, modifications, and equivalents. It is clear that the present invention can be applied in the same manner by appropriately modifying the above embodiments. Accordingly, the above description does not limit the scope of the invention as defined by the limitations of the following claims.

As described above, in the transmission device interworking restoration method of the network management system according to the present invention, the event processing daemon of the transmission equipment and the network optical system by periodically checking the TCP / IP socket connection status report the occurrence of the event by the transmission equipment This improves the reliability of the network management system and increases the utility of the network management system.

In addition, the method according to the present invention can recover the connection with the server event processing daemon in the transmission equipment during the abnormal operation of the client event processing daemon in the network management system, thereby preventing the abnormal operation of the client event processing daemon in the prior art. There is an effect of increasing the reliability of the operation of the network management system by solving the problem that there is no countermeasure.

Claims (1)

A first step of connecting to a client side when a connection request is received while waiting for a socket to be opened on the server side; A second step of monitoring occurrence of an event after performing the first step; If the event does not occur in the second step, checking whether the connection is made and monitoring the occurrence of the event; A fourth step of performing an incident report by checking whether a connection occurs when an event occurs in the second step; And if not connected in the third and fourth steps, respectively, performing a fifth step of closing the socket and returning to the standby state.