KR20020039752A - Apparatus and method for transmitting event between task - Google Patents

Abstract

PURPOSE: A device and method for transmitting an event between tasks is provided to transmit and receive event information conveniently in a system, which uses many processors as a switching system. CONSTITUTION: A message transmission unit maintains a wait state(100). The message transmission unit checks whether event data are received or not in the wait state(102). If event data do not received, the message transmission unit checks whether an update signal of destination transmission table data is received(104). If update signal of destination transmission table data is received, the message transmission unit updates data using the destination data received from a man machine processor(106). If event data are received, the message transmission unit reads the destination transmission table and checks the destination of the received event(108). The message transmission unit checks whether a receiving task corresponded to the destination as the checking result is existed(110). If the receiving task corresponded to the destination is existed, the message transmission unit transmits the generated event message to the corresponding destinations(112).

Description

Apparatus and method for event transfer between tasks {APPARATUS AND METHOD FOR TRANSMITTING EVENT BETWEEN TASK}

TECHNICAL FIELD The present invention relates to apparatus and methods for transmitting signals, and more particularly, to apparatus and methods for transmitting signals in complex systems such as exchange systems.

Typically, systems such as switching systems, transmission systems, base station systems and base station controllers operate with at least one processor therein. As such, in systems having at least one processor, a task for processing information about the generated event is operated when an interprocessor event occurs. As described above, each task performs an event, and in some cases, the generated event may be notified to a predetermined task of another processor or may be operated by the control of another task.

As described above, when at least two processors need to exchange information about events between tasks, more and more processors become more frequent. In order to send and receive the information of the inter-task event, the form of the message sent and received between the tasks must be set, and the program must be changed accordingly. That is, in order to define data for each event, programs loaded in each processor must be modified. This task becomes more difficult as more types of processors become more complex. The reason for this system is that it must be tightly coupled between tasks. Therefore, in a system implementing many processors, such as an exchange system, there is a problem in that programs of many processors need to be modified when delivering event information. In addition, this phenomenon caused a lot of time and manpower as well as the problem of redesigning the system.

Accordingly, an object of the present invention is to provide an apparatus and method that can easily exchange event information between tasks in a system using many processors, such as an exchange system.

Another object of the present invention is to provide an apparatus and method capable of shortening a system development time by a message transmitted between tasks in a system using many processors such as an exchange system.

The present invention for achieving the above object is an apparatus for transferring events between tasks in a system having two or more processors, the operation of each of the devices and the operation of the sub-devices to detect the event occurrence and the detection of the event occurrence And a processor comprising: a plurality of processors each having outgoing tasks for outputting an event, a message forwarding unit for receiving an event message from the outgoing tasks, and having a destination transmission table for delivering the received event message; And a processor and a device for driving each task to receive the message by the message transfer unit.

The apparatus may further include an apparatus for receiving an operator command to update the destination transmission table of the message transfer unit and performing destination update.

The method for achieving the above object is a message delivery unit of a system consisting of two or more processors consisting of outgoing tasks for inspecting the state of a device and detects and transmits an event when the event occurs and receiving tasks for receiving the event message. A method for delivering a message in a method, the method comprising: checking whether an event message is received from the originating tasks; and checking a destination transmission table in response to the event when the event message is received as a result of the inspection. And, if there is a destination as a result of the destination check characterized in that the process of delivering the generated event message to the corresponding destinations.

In addition, if there is no destination of the generated event may be further provided to process in an exception routine,

The method may further include updating data of the destination transmission table according to the received data when the data update request signal of the destination transmission table is received.

1 is a block diagram illustrating a connection relationship between each task to which the present invention is applied and a message transfer unit that delivers a message of tasks;

2 is a control flowchart of event message delivery performed in a message delivery unit according to an exemplary embodiment of the present invention.

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

1 is a block diagram illustrating a connection relationship between each task to which the present invention is applied and a message transfer unit that delivers a message of tasks. Hereinafter, an operation of tasks and a message transfer unit according to the present invention will be described in detail with reference to FIG. 1.

The originating first task 11 and the originating second task 12 may be tasks that are mounted and operated on different processors, or may be tasks that are mounted and operated on the same processor. However, the contents to be dealt with in the present invention will be described on the assumption that they are implemented in different processors because they describe a method of delivering events from different processors. In addition, in the following description, it is assumed that each of the tasks is provided in each processor (not shown in FIG. 1) when the tasks are mounted on different processors in the switching system.

The originating first task 11 and the originating second task 12 perform a predetermined routine and check whether an event occurs in each of them. Such an event detects a failure according to the type of card mounted, a failure according to the type of links, or detects various failures such as a processor failure and a communication failure. It can be configured to process on a processor with a task having this function, rather than on one processor. When each of the tasks detects an event, it delivers the message to the message delivery unit 21 for delivering the event, instead of directly delivering it to the task of the destination to be delivered. That is, only the information on the generated failure is transmitted to the message transfer unit 21. In addition, the dispatch tasks generate and include in the system a task on the receiving side, that is, a message for delivering the generated event. Through this, each event has a unique name and is read from the message transfer unit 21 and included in the task of the destination. In this case, an example generated by the transmission task may be illustrated as shown in Table 1 below.

Event-Category Event-name Location State Onoff Operations OAM & P_OperStateChange STM_1 Function_Fail ON Operations OAM & P_AdminStateChange STM_1 Function_fail ON

As shown in Table 1, an event category is generated, and when the event name, location, and status are defined according to the generated event category, the message transmission unit 21 reads it and transmits a message. do. In the following description, data of a type such as <Table 1> will be referred to as an "event definition message".

The message transfer unit 21 receives the failure information and stores a database of a destination address for the task delivered for each received failure information. This storage may be stored in a table in advance. When each task generates data to be included in the system, it can be read and processed. That is, as shown in Table 1, when an event definition message is generated, it may be configured to read and process it. This change of information can also be configured to allow the operator to change the data directly.

The table of destination address for each task to which the failure information should be delivered is referred to as a "destination transfer table" in the following description, which is shown in Table 2 below.

Event name Event destination Card Type 1 Failure Fault function CLI function GUI function Log function - Card Type 2 Failure Fault function CLI function GUI function - - Link Type 1 Failure Fault function CLI function GUI function - - Link Type 2 Failure Fault function CLI function GUI function - - Processor failure Alarm function CLI function GUI function - - Communication failure Alarm function CLI function GUI function - - … … … … … …

As shown in Table 2, the names of the tasks for transmitting the corresponding events are described corresponding to the names of the events. Table 2 shown above summarizes the functions by function corresponding to the name of the task. In addition, the message transfer unit 21 may be mounted in an operation & maintenance processor (OPM) that is a processor that performs maintenance when mounted in an exchange system. Upon receiving the predetermined event information, the message transfer unit 21 checks a destination to be transmitted according to the received event based on the destination transmission table. The message is then sent to the checked tasks.

The receiving first task 31 and receiving second task 32,... The reception N-th task 33 becomes tasks corresponding to the destination address, respectively. Therefore, in the related art, each outgoing task and the receiving task are tightly coupled. Therefore, when it is necessary to change an event to be transmitted by adding an event, it is necessary to modify both the sending task and the receiving task. Can be solved. That is, the reception task may be configured to receive a message about an event and process it, the originating task may increase or decrease only a type for detecting a failure, and deliver the detected failure to a message delivery unit. Accordingly, when one message is to be delivered to another task, the message may be configured by adding the task to the destination transmission table of the message delivery unit 21.

Therefore, when configured in this way, the outgoing tasks can reduce the time load of inspecting the received event one by one for each outgoing event whenever an event occurs. Next, a process according to the message transfer performed by the message transfer unit 21 will be described with reference to FIG. 2.

2 is a control flowchart of event message delivery performed in a message delivery unit according to an exemplary embodiment of the present invention. Hereinafter, a control process for delivering an event in a message transfer unit will be described in detail with reference to FIGS. 1 and 2.

The message transfer unit 21 maintains the standby state in step 100. This standby state is a state in which an initialization process is performed. That is, as described in the description of FIG. 1, the originating tasks are configured to read the above-described event definition message to include the type of event they detect in the system, and to configure a destination transmission table, or preset in the configuration of the system. Refers to a state where the destination transfer table can be obtained and used. In the standby state, the message transfer unit 21 proceeds to step 102 and checks whether event data is received. The reception of such event data refers to the reception from the transmission tasks of FIG. If event data is received as the result of the check, the process proceeds to step 108;

The message transfer unit 21 checks whether an update signal of the destination transmission table data is received when event data is not received, that is, when proceeding to step 104. The data update signal of the destination transmission table is input by the operator, but the connection relationship is not shown in FIG. 1. Create and pass In step 104, the message transfer unit 21 checks whether a signal for requesting data update of the destination transmission table has been received. If there is a data update request of the destination transmission table as a result of the check, the process proceeds to step 106; otherwise, the process proceeds to step 100. If there is a destination update request signal, the message transfer unit 21 updates the data using the destination data received from the MMP in step 106. That is, the operation of deleting or adding or changing the destination is performed. After updating the destination transfer table in this manner, the standby state of step 100 is maintained.

Meanwhile, when the event data is received and the process proceeds from step 102 to step 108, the message transfer unit 21 reads the destination transmission table and checks the destination of the received event. That is, as shown in Table 2, the reception tasks for notifying each other are examined according to the type of the card, the type of the link, the processor failure, and the communication failure. In step 110, the message transfer unit 21 checks whether a reception task corresponding to a destination exists. If the result of the inspection, that is, the destination exists, the flow proceeds to step 112; otherwise, the flow proceeds to step 114. If the message delivery unit 21 checks that the destination exists, that is, proceeds to step 112, the message transfer unit 21 delivers the generated event message to the corresponding destinations. On the other hand, if the corresponding destination does not exist, that is, proceed to step 114, the exception routine is notified. After performing the above process, the process proceeds to step 100 to maintain the standby state.

As described above, by performing a message transmitted from each task to many processors, such as an exchange system, in the message transfer unit, the program can be easily changed and the development time and manpower can be reduced. It also has the advantage of reducing the load on the system by reducing the time for delivering messages in each task.

Claims (5)

An apparatus for communicating events between tasks in a system having two or more processors, the apparatus comprising: Each of said processors having outgoing tasks that monitor the state of operation of each device and the state of operation of subordinate devices to detect occurrence of an event and output the detected event; A processor for receiving an event message from each originating task, the processor comprising a message delivery unit having a destination transmission table for delivering the received event message; Inter-task event delivery device, characterized in that consisting of a processor and a device for driving each task to receive a message by the message delivery unit. The method of claim 1, And an apparatus for receiving an operator command for updating a destination transmission table of the message transfer unit to perform a destination update. In the method for delivering a message in a message delivery unit of a system consisting of two or more processors consisting of outgoing tasks for detecting the state of a predetermined device and detecting and transmitting when an event occurs and receiving tasks for receiving the event message , Checking whether an event message is received from the originating tasks; Checking a destination by checking a destination transmission table in response to the event when an event message is received as a result of the inspection; And transmitting the generated event message to the corresponding destinations when the destination exists as a result of the destination checking. The method of claim 3, And processing the exception routine if the destination of the generated event does not exist. The method according to claim 3 or 4, And when the data update request signal of the destination transmission table is received, updating the data of the destination transmission table according to the received data.