KR20000061040A - Linkage metnod of interface block and agent of the Telecommunication Management Network system - Google Patents

Abstract

PURPOSE: A method for interlocking an agent and an interface block in an integrated managing network system is provided to obtain a stability of an entire system by judging a disconnection state of a socket in a processor without forcibly topping a block using a return value and a signal of a read function between processors in an agent block and an interface block and changing a socket connection structure for preparing a re-connection of a socket. CONSTITUTION: A BIM block executes processors of a TMN system having an agent block and an interface block(S1-S4). If the agent block is down, down information is transmitted to the BIM for monitoring child-processors(S6). The BIM receives a down signal of the child-block, and identifies as to whether the received down signal is a signal generated in the agent block(S7). If the received down signal is the signal generated in the agent block, a signal for indicating that an agent is stopped is transmitted to the interface block(S8). The BIM repeatedly performs the agent block(S9).

Description

Linkage method of agent and interface block of integrated management network system {Linkage metnod of interface block and agent of the Telecommunication Management Network system}

The present invention relates to a PCS TMN (personal mobile phone integrated management network), and in particular, lowers the interdependence between the agent block in the TMN system and the block in charge of the message interface interface block even if the agent of the TMN system is down (Down) On the other hand, the present invention relates to a method of interworking between the agent and the interface block of the integrated management network system to enhance the safety of the TMN system by operating the agent block even when the interface block is down.

In general, the agent block and the interface block of the PCS TMN system perform an internal processor communication (IPC) using a socket.

The internal socket communication between processors consists of a structure of sending and receiving messages according to the TCP / IP protocol promised between two blocks.

According to the TCP / IP protocol, in order to open a socket, the sockets should be sequentially opened in a predetermined order of two blocks.

Therefore, if a problem occurs on one processor and the socket goes down, the other processor also restarts and returns to the opening of the first socket or prepares to retry the socket connection on its own without the processor restarting itself. It should be made possible.

That is, in the conventional method of reconnecting a socket between an agent block and an interface block, when one of the two blocks is down, the other block is also forcibly terminated, and both blocks are restarted from the beginning to naturally reconnect the socket during the initialization of each processor. To be connected.

As a result, the conventional method described above has a problem in that a block having no problem must be terminated and executed again, such as a problem block, and thus a message is lost because the messages sent from the BSM cannot be received during that time.

The present invention has been made to solve such a conventional problem, and an object of the present invention is to forcibly terminate a block by using a return value and a signal of an interprocessor read () function in an agent block and an interface block, respectively. It provides a method of interworking with the agent and interface block of the integrated management network system to obtain the stability of the whole system by changing the socket connection structure so that the processor can determine the socket disconnection status and prepare to reconnect the socket on its own It is.

1 is a block diagram of a socket reconnect structure according to the present invention;

2 is a flowchart of a BIM block including a socket reconnection method of the present invention.

3 is a flowchart of an agent block including a socket reconnection method of the present invention.

4 is a flowchart of an interface block including the socket reconnection method of the present invention.

<Explanation of symbols for main parts of drawing>

1: BIM 2: Socket block

3: agent block 4: interface block

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

1 is a block diagram of a socket reconnection structure of the present invention, a BIM 1 for firstly executing an agent block and an interface block, a socket buffer 2 for connecting an agent block and an interface block, and a read () function at startup. If the read () function returns a value of "0", the agent block (3) reconnects the socket, converts the message from the BSM at startup, and sends a signal that the agent has terminated. It consists of an interface block 4 for reconnecting sockets.

Referring to the operation of the present invention configured as described above is as follows.

First, the interaction of the BIM (1), the agent block (3), and the interface block (4) that includes socket reconnection will be described.

First, the processors of the TMN system including the agent block 3 and the interface block 4 are executed in the BIM 1 block (S1-S4).

The agent block 3 generated and started to run in the BIM 1 prepares a socket connection with the interface block 4 (S12-S14).

In addition, the interface block 4 generated and started to execute in the BIM 1 registers a signal which the BIM 1 sends when the agent is terminated in the signal table of the interface block 4 (S23-S25).

Here, the states after S24 (hereinafter referred to as SM-1) are interrupted by the step of processing the signal (hereinafter referred to as SM-2) when the receiver receives a signal sent from the BIM in any future state.

Next, the socket connection with the agent block 3 is prepared (S26), and the agent block 3 and the interface block 4, which prepare the socket connection according to their respective roles, have a socket connection synchronization with the other party so that the actual connection is established. Repeat the socket connection attempt until it is opened.

At this time, the agent block 3 becomes a server of a socket connection and the interface block 4 becomes a client.

That is, the agent, which is a server, prepares to open a socket, waits for a client's request, and opens a socket by accepting a connection request from the interface block 4 (S15, S14, S25, and S27 repeatedly).

Next, when the socket is established due to synchronization between the agent block 3 and the interface block 4, each block performs the next step (after S16 and after S28).

Second, the interaction when the agent block 3 is down will be described.

When the agent block 3 is down, it becomes a daemon processor and the down information of the agent is transmitted to the BIM 1 which is monitoring the self-processors (S6).

Then, the BIM 1 receives the down signal of the child block and checks whether the signal is generated from the agent block 3 (S7).

If the end signal received by the BIM 1 is confirmed to be a signal generated in the agent block 3, a promise signal indicating that the agent is terminated is sent to the interface block 4 (S8).

After the signal is sent, the BIM 1 executes the agent block 3 again (S9).

Therefore, since the agent block 3 has been re-executed, it returns to the first socket connection part and attempts to open a socket with the interface block 4 (S12-S14).

At this time, the interface block 4 receives the signal of the BIM (1) to stop the task that the interface block 4 was doing for a while to jump to the process of connecting the agent and the new socket (S35, S36).

That is, jumping from the state of SM-1 to the state of SM-2.

On the other hand, if the two blocks, each of which prepared for socket reconnection, successfully open the socket (S15, S37), the agent block 3 performs the next step of work, and the interface block 4 returns to the stopped work state and continues working. (S16 and S38).

That is, it returns to the original state of SM-1.

Third, the interaction process when the interface block 4 is down will be described.

When the interface block 4 is down, the socket is disconnected, sending the bad data to the agent block 3, and the agent block 3 receiving the bad data attempts to read () the data (S16).

At this time, since it is not actual data, the return value of the read () function is "0" (S17).

Next, the agent whose read () return value is "0" branches to the step of reconnecting the interface block 4 and the socket (S18).

At this time, the BIM 1 receives the down signal of the interface block 4 as in the case where the agent block 3 is down and checks whether the signal is generated from the agent block 3 (S6, S7).

In the BIM (1) where the termination of the interface block is confirmed, the interface block (4) is executed again (S9), and the interface block (4) thus performed is returned to the first socket connection part, and the socket connection is already prepared. The agent block 3 and the socket are opened (S14, S15, S23-S26).

Therefore, when the socket is re-opened, the agent block 3 and the interface block 4 both perform tasks of each block (after S16 and after S28).

As described above, according to the present invention, since the interdependence of the interface block and the agent block is lowered to enable separate operations, even if a problem occurs in one block, the other block does not affect the system stability. .

In addition, even if the agent block is down, the interface block can continue to receive the message of the BSM, restarting up to the interface block has an effect that the state consistency of the TMN / BSM system than the conventional method that the BSM message is lost.

Claims (3)

In a TMN system in which an agent block and an interface block are connected by a socket to perform internal processor communication, BIM block for performing the agent block and the interface block, Executing the processors of the TMN system including the agent block and the interface block in the BIM block, Monitoring the child block as a daemon processor and determining whether an end signal for the child block performed by the BIM has been received; Determining whether the terminated block is an agent block upon arrival of the termination signal for the child block, and if the agent is blocked, sending a signal indicating the termination of the agent from the interface block of the agent and rerunning the terminated block if not the agent block; Determining whether an execution message of the re-executed child block arrives, and when the arrival is completed, recovering the child block and returning to the daemon process state. In a TMN system in which an agent block and an interface block are connected by a socket to perform internal processor communication, The agent block, Executing an agent initialization process in an agent block start state and attempting a socket connection with an interface block, Reading a message from the interface block with a read () function when the socket connection is successful, and determining whether the result value of the read () function is 0, Preparing a socket reconnection when the read () function value is 0, and determining whether a result value> 0 when the read () value is not 0, Performing an agent task on the message if the result value is> 0, and recording an error occurrence of the read () function if the result value is <0, A method of interworking with an agent and an interface block of an integrated management network system, comprising: terminating a message receiving task and returning to a message waiting state. In a TMN system in which an agent block and an interface block are connected by a socket to perform internal processor communication, The interface block, Registering a signal promised with the BIM, attempting to establish a socket connection with the agent block after initializing the interface block; If the socket connection is successful, read the message sent from the BSM block, convert it into a TMN message, and then wrire () the converted message to the agent block. Judging whether the result value> 0, and if the result value> 0, the message write () is completed; if the result value <0, recording the write () error; SM-2 is completed by completing the processing of the message and returning to the BSM message waiting state. Receiving the termination signal of the agent sent from the BIM and attempts to reconnect the socket with the agent block, and if the socket connection is successful, returning to the state before receiving the termination signal is made SM-3 by the SM-2 and SM-3 Interworking method of the agent and the interface block of the integrated management network system, characterized in that the wireless connection.