KR20010004513A - Transaction measurement table in the switching system - Google Patents

Abstract

PURPOSE: A transaction managing table of a message processing task in a switching system is provided to make a transaction behavior table, a transaction state managing table, and a transaction ID for allocating table manage transactions according to IDs, and to divide each transaction into many transaction states and sub transactions and to manage the divided transactions with transaction state units, so that the message processing task may simultaneously process many messages without time delay. CONSTITUTION: A transaction behavior table is composed of a transaction type definition part and a transaction state/operation definition part. The transaction type definition part stores transaction type IDs, transaction message IDs, a first transaction state number, and an operation function routing indicator relating to the first transaction state, according to transaction types, respectively. The transaction state/operation definition part stores transaction state numbers, acknowledge message IDs, time-out message IDs, an operation function routine indicator and a time-out operation function routine indicator, according to transaction states, respectively. A transaction state managing table is allocated by corresponding to inputted transaction messages. The inputted transaction messages are composed of transaction IDs which are transaction identifiers, transaction type IDs corresponding to the transaction messages, present transaction state numbers, timer IDs and transaction state number indicators. The transaction IDs are recorded in each entry of a transaction ID allocating table. Values of a transaction ID canceling index and a transaction ID generating index are controlled in a mathematical formula5(Transaction ID release index value = transaction ID release index value ++ %(K+1) : K which is larger than 1 is the entry number of transaction ID allocation table) and a formula6(Transaction ID allocation index value = transaction ID allocation index value ++ %(K+1) : K which is larger than 1 is the entry number of transaction ID allocation table), respectively, after performing transaction ID canceling/allocating operations of a task in the transaction ID allocating table.

Description

Transaction management table for message processing tasks in a switching system. {TRANSACTION MEASUREMENT TABLE IN THE SWITCHING SYSTEM}

The present invention relates to a message processing method in a message driven system, and more particularly, to a plurality of message processing methods in a switching system.

The exchange system is composed of a plurality of operating processors and handles work by exchanging messages between processors. And when a task processes a message in an exchange system, if the interaction through the message exchange with an external task becomes frequent, there is a need to limit the load in the system to a certain level.

Generally, there are two methods of processing a message by assigning a task to each message and processing a message sequentially in one task.

However, the first method is a method in which a task is generated each time a message arrives, and there is a concern that the system may be overloaded due to excessive task generation when the message is congested. In addition, the second method can process the next message only after one message processing is completely completed. Therefore, there is a problem that the efficiency is inferior when the message blocking occurs. In addition, in the second method, when it is frequently necessary to send another message to another task to process one message, the task cannot process another message while waiting for the response message. This problem greatly reduces the task's message processing efficiency.

Accordingly, an object of the present invention is to provide a transaction management table in which a single task can simultaneously process a plurality of messages without blocking in an exchange system.

Another object of the present invention is to provide a transaction operation table, a transaction state management table, and a transaction ID allocation table for managing transactions by ID in a switching system and dividing each transaction into a plurality of transaction states and sub-transactions. have.

In order to achieve the above objects, the present invention provides a transaction management table of a message processing task in a switching system according to transaction type ID, transaction message ID, first transaction status number and first transaction status. A transaction type definition portion for storing the operation function routine indicators for each function, a transaction status number, a response message ID, a time-out message ID, and an operation function routine indicator for each transaction number of the transaction type. And a transaction action table consisting of a transaction state and an action definition portion respectively storing a time-out action function routine indicator, a transaction identifier, a transaction identifier, a transaction type ID corresponding to the corresponding transaction message, and a current transaction state number. , Timer IDs, and tracks Characterized a transaction made of an assignment status management table in correspondence with the plurality of transaction messages to be input consists of a transaction number status indicator.

1 is a block diagram showing the concept of a transaction operation table according to an embodiment of the present invention.

2 illustrates a transaction type definition portion of a transaction action table according to an embodiment of the present invention.

3 illustrates a transaction state and action definition portion of a transaction action table in accordance with an embodiment of the present invention.

4 illustrates a transaction state management table in accordance with an embodiment of the present invention.

5 is a diagram illustrating a transaction ID allocation table according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Specific details appear in the following description, which is provided to aid a more general understanding of the present invention, and it should be understood by those skilled in the art that the present invention may be practiced without these specific details. It will be self explanatory. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

The present invention enables a switching system to process a plurality of messages using a single task, thereby preventing the system load from being generated due to task generation. In addition, the present invention allows a plurality of messages to be processed simultaneously without blocking in a single task.

That is, the transaction operation table, the transaction state management table, and the transaction ID allocation table according to an embodiment of the present invention manage transactions by ID, divide each transaction into a plurality of transaction states and sub-transactions, and manage them by dividing them into transaction state units. This allows the task to process multiple messages simultaneously, with no time delay, for transaction messages, response messages, and time-out messages.

First, terms according to embodiments of the present invention are defined.

A transaction is a series of processes from when a task receives a message request to processing a message and then sending a response message. At this time, the message input to the task is called a transaction message. In addition, an operation of processing a task varies according to the transaction message, and a type of one processing operation of the task is classified by a transaction type. That is, when a task receives a message defined with the same transaction type, the task processes the message in the same way. However, even with the same transaction type, different message processing results may be different. That is, when the task receives the transaction execution request message defined in the transaction type, the task creates the corresponding transaction, and each transaction is identified by the transaction ID. Meanwhile, a task may generate a new transaction by sending a transaction execution request message to another task while executing one transaction. The generated transaction is called a sub transaction in terms of a task that sent the transaction execution request message, and the transaction execution request message is called a sub transaction message. One transaction consists of several subtransactions and is executed with the same transaction ID. When a task executes a transaction, the unit that the task processes until the sub transaction occurs is called a transaction state. The transaction is composed of several transaction states, and the movement between the transaction states is performed by a task sending a sub transaction message to another task to generate a sub transaction and receiving a response message corresponding to the sub transaction from the another task. Lose. Historical information such as information shared between transaction states, environmental information, message transfer parameters of previous states, and result values are stored by the transaction state information indicator.

1 is a block diagram illustrating the concept of a transaction behavior table according to an embodiment of the present invention.

The transaction action table is composed of a transaction type definition part 110 and a transaction state and action definition part 120. The transaction type definition part 110 stores information on the transaction type definition for each of the first transaction types 111 through N-th transaction type 11N. As illustrated, the first transaction type 111 is an operation process of the first transaction state TS # 1 121, the third transaction state TS # 3 123, and the fifth transaction state TS # 5 125. Is done. In addition, the second transaction type 112 is an operation process of a single fourth transaction state TS # 4 124, and the Nth transaction type 11N is the first transaction state TS # 1 121, the second transaction. An operation process of the state TS # 2 122, the third transaction state TS # 3 123, and the fourth transaction state TS # 4 124 is performed.

2 is a diagram illustrating a transaction type definition portion of a transaction operation table according to an embodiment of the present invention. A description with reference to FIG. 1 is as follows.

The transaction type definition part includes a transaction type ID, a triggering message ID, and an operation function routine indicator for the first transaction state and the first transaction state for each transaction type. That is, the first transaction type 111 may include a first transaction type ID 210, a triggering message ID 212, a first transaction state number 214, and an operation function routine indicator 216 for the first transaction state. ) Is provided. Similarly, the second transaction types 112 through N-th transaction type 11N also have operation function routine indicators for the corresponding transaction type ID, the triggering message ID, the first transaction status number, and the first transaction status.

3 illustrates a transaction state and action definition portion of a transaction action table according to an embodiment of the present invention. Hereinafter, a description will be given with reference to FIGS. 1 and 2.

In the transaction state and operation definition, there are two messages that activate each transaction state for transaction state management. One of them is a response message input to the task by performing a sub-transaction of another task, and the other is a response message not received within a preset time after the task transmits a message to perform the sub-transaction. Time-out message originating from the entity. The two messages are provided with a corresponding transaction ID. According to an embodiment of the present invention, the transaction state and operation definition portion includes an operation function routine indicator and a time-out operation function routine indicator that are respectively performed according to the two transaction state activation messages for each transaction state. That is, the task according to an embodiment of the present invention performs a function by the operation function routine indicator set for each transaction state when the ID of the input message corresponds to the response message. If the ID of the input message corresponds to a time-out message, the task performs a function by a time-out operation function routine indicator.

3 illustrates a portion of the transaction state and operation definition portion of FIG. 1. As described above with reference to FIG. 1, each transaction type of a transaction state and an operation definition portion is composed of an operation of a corresponding number of transaction states, and for each transaction state, that is, the first transaction state TS # 1 in FIG. 3. Transaction status number # 1 (310), response message ID # 1 (312), time-out message ID # 1 (314), operation function routine indicator # 1 (316), and time-out operation function routine indicator by (121). # 1 318. Similarly, in the transaction state and operation definition part, each transaction type is a transaction state number # 3 (330), response message ID # 3 (332), and time-out message ID # 3 for each third transaction state TS # 3 (123). 334, operation function routine indicator # 3 336 and time-out operation function routine indicator # 3 338.

If the ID of the input message corresponds to the response message ID # 1 312, the task performs the corresponding function by the operation function routine indicator # 1 316. The function terminates after determining a next transaction state, that is, transaction state number # 3 330, and transmitting a sub transaction message to the task. In this case, the task may include a transaction ID to be described later in the sub-transaction message. If the ID of the newly input message corresponds to the response message ID # 3 (332), the task performs the corresponding function by the operation function routine indicator # 3 (336). The function terminates after determining the next transaction state and transmitting a sub transaction message to the task.

In the description of FIG. 3, the transaction state and operation definition portion of the transaction action table according to the embodiment of the present invention manages the transaction by dividing the transaction into a plurality of sub-transactions and state units, and the task includes a plurality of response messages and a time. -out Messages can be processed simultaneously without delay.

4 illustrates a transaction state management table according to an embodiment of the present invention. Hereinafter, a description will be given with reference to FIGS. 1 to 3.

The entry number M for limiting the number of transaction IDs managed in the transaction state management table is the number of transactions that can be processed simultaneously by the task.

The transaction ID is a transaction delimiter that is allocated whenever a triggering message or a transaction message that requires transaction creation is entered into the task. That is, the task in accordance with an embodiment of the present invention, if the ID of the input message is a message requesting the creation of a transaction, or if the ID of the message is a triggering message ID defined in the transaction type definition of the transaction action table of FIG. The task assigns a new transaction ID to the message and assigns the newly assigned transaction ID, transaction type ID, current transaction status number, timer ID, and transaction status information indicator to the corresponding entry number 450 in the transaction status management table. 418). In this case, the transaction type ID and the current transaction state number refer to the transaction type definition of the transaction operation table of FIG. 2. At this time, the current transaction state number becomes the number of the first transaction state of the corresponding transaction type.

The task performs an operation function according to an operation function routine indicator for the first transaction state of the transaction type by referring to the transaction type definition of the transaction operation table of FIG. 2. The function terminates after determining the next transaction status number and sending a sub transaction message to the task. At this time, the task updates the current transaction state number of the corresponding entry number in the transaction state management table to the determined transaction state number.

And when the ID of a newly input message is a corresponding response message transmitted by performing a sub transaction of another task, the corresponding task has an ID of the message in a transaction type definition portion of the transaction operation table of FIG. 2. Since it is not a defined triggering message, the transaction ID included in the message is found. The task checks the current transaction status number and transaction type with reference to the found transaction ID in the transaction state management table of FIG. 4. The task checks the ID of the newly input response message in the transaction state and operation definition of FIG. 3. The task calls the operation function by the operation function routine indicator of the current transaction state number.

Meanwhile, in the corresponding task according to the embodiment of the present invention, when the ID of a newly input message is a time-out message input from the corresponding entity, the corresponding task may be a transaction type of the transaction operation table of FIG. 2. Since it is not a triggering message defined in the definition part, the transaction ID included in the message is found. The task checks the current transaction status number and transaction type with reference to the found transaction ID in the transaction state management table of FIG. 4. The task checks the ID of the newly input time-out message in the transaction state and operation definition of FIG. 3. The task calls the operation function by the corresponding time-out operation function routine indicator for each current transaction state number.

As described above, the time-out message is a message generated when the corresponding task does not receive a response message within a preset time after transmitting the sub transaction message. That is, when the corresponding task transmits the sub-transaction message, a timer operates for each transaction ID. When the corresponding response message is received within a preset time, the timer should be initialized. Accordingly, the task manages a timer ID for each transaction ID in the transaction state management table of FIG. 4.

The task manages a transaction status information indicator for each transaction ID. The transaction state information indicator stores historical information such as information shared between state of a corresponding transaction, environment information, message transmission parameter of previous state, and result value.

On the other hand, each transaction has a different processing time. As a result of this, each transaction ID entry in the transaction state management table of FIG. 4 randomly mixes a transaction entry that is currently being processed and an entry of an already terminated transaction. Therefore, in order to process a new transaction, the task must find an unused entry among the entries in the transaction state management table and assign it to the transaction execution request message.

In the description of FIG. 4, the transaction state management table according to the embodiment of the present invention manages a plurality of transaction messages for each transaction ID, so that the task can simultaneously process a plurality of transaction generation request messages without delay. There is a number.

5 illustrates a transaction ID allocation table according to an embodiment of the present invention. Hereinafter, a description will be given with reference to FIGS. 1 to 4.

Each transaction ID assignment table entry is provided with a transaction ID. K in FIG. 5 is one greater than the number M of entries in the transaction management table of FIG. 4 (K = M + 1). The transaction ID release index 510 and the transaction ID allocation index 520 are tasks. After the transaction ID releasing and allocating operations, the values are adjusted as in Equations 1 and 2, respectively.

Transaction ID Release Index Value = Transaction ID Release Index Value ++% (K + 1)

Herein, the transaction ID release index value means an index position of a transaction ID allocation table in which a transaction ID to be released is recorded when the task returns a corresponding transaction ID, where K is an entry in the transaction ID allocation table. As a number, the number is one greater than the number of entries in the transaction management table.

Transaction ID Allocation Index Value = Transaction ID Allocation Index Value ++% (K + 1)

Herein, the transaction ID allocation index value means an index position of a transaction ID allocation table in which a transaction ID to be allocated is recorded when the task allocates a corresponding transaction ID to the transaction management table to perform a new task. Is the number of entries in the transaction ID allocation table, which is one greater than the number of entries in the transaction management table.

Each entry of the transaction ID allocation table may be configured as a circular list. In this case, the transaction ID release index 510 and the transaction ID allocation index 520 become '0' after the value is increased by K. When the transaction ID release index 510 and the transaction ID allocation index 520 have the same value, all of the transaction IDs are allocated. At this time, the task can no longer allocate the transaction ID until the value of the transaction ID release index 510 is increased again.

In the description of FIG. 5, it can be seen that the transaction ID allocation table according to the embodiment of the present invention can minimize the time for searching for an unused transaction ID entry when allocating a new transaction ID.

On the other hand, a transaction message input to a task according to an embodiment of the present invention is a request for a new task to the task, the task is assigned a new transaction ID for the transaction message. The response message inputted to the task is generated by performing a sub transaction of another task, and includes a transaction ID previously assigned by the task. In addition, the time-out message input to the task is generated from a corresponding entity when the task does not receive a response message within a preset time after the sub-transmission message is transmitted to the task, and is previously assigned by the task. The transaction ID will be included.

Hereinafter, when a task according to an embodiment of the present invention is input to the three messages, a method of processing the message will be described in detail with reference to FIGS. 1 to 5.

The task checks whether the incoming message is a transactional message. In this case, the operation may be performed by the corresponding task checking whether the ID of the input message is a triggering message ID defined in the transaction type definition of the transaction operation table of FIG. 2. If the input message is a transaction message, the task assigns a new transaction ID for the input message. In this case, the task allocates a transaction ID indicated by the transaction ID allocation index of the transaction allocation table of FIG. 5. The task stores the newly allocated transaction ID in a corresponding entry number or index of the transaction state management table of FIG. 4. The task stores the transaction type ID and the first transaction state number in the transaction type definition of the transaction operation table of FIG. 2. The task stores a corresponding timer ID and a transaction state information indicator in a corresponding entry number or index of the transaction state management table.

The task performs an operation function according to the operation function routine indicator for the first transaction state of the transaction type stored in the transaction state management table by referring to the transaction type definition of the transaction operation table of FIG. 2. At this time, the corresponding function ends after referring to the transaction state and operation definition of the transaction action table of FIG. 3, determining the next transaction state number, and transmitting the sub transaction message to another task. In this case, the corresponding transaction ID may be included in the sub transaction message. The task updates the current transaction state number of the entry number of the transaction state management table of FIG. 4 with the determined transaction state number.

When the corresponding task transmits the corresponding sub transaction message, the task operates a timer corresponding to the timer ID of the transaction state management table and stores transaction state information generated by the transaction state information indicator. In this case, the transaction state information may be historical information such as information shared between transaction states, environment information, message transmission parameters of previous states, and result values.

In this case, when the corresponding task transmits the corresponding sub-transaction message, the task performs an operation function on the first transaction state of the transaction, thereby enabling processing of a newly input message.

Meanwhile, the task checks whether an input message is a response message. In this case, the operation may be performed by the corresponding task to check whether the ID of the input message is a triggering message ID defined in the transaction type definition of the transaction operation table of FIG. 2, and when the trigger message is not the triggering message ID. The task of finding a transaction ID included in the input message, the task identifying the current transaction status number and a transaction type in the transaction state management table of FIG. 4 with reference to the found transaction ID, and The corresponding task may be performed to determine whether the ID of the input message is a corresponding response message ID according to the current transaction status number in the transaction state and operation definition of FIG. 3. If the input message is a response message, the task performs an operation function corresponding to the current state.

In this case, the corresponding task may terminate the transaction or generate a new sub-transaction message and transmit it to another task. When the corresponding transaction ends, the corresponding task releases the assigned transaction ID and adjusts the transaction ID release index of the transaction allocation table of FIG. 5.

In addition, the task checks whether an input message is a time-out message. In this case, the operation may be performed by the corresponding task to check whether the ID of the input message is a triggering message ID defined in the transaction type definition of the transaction operation table of FIG. 2, and when the trigger message is not the triggering message ID. The task of finding a transaction ID included in the input message, the task identifying the current transaction status number and a transaction type in the transaction state management table of FIG. 4 with reference to the found transaction ID, and The corresponding task may be performed to determine whether the ID of the input message is a corresponding time-out message ID for each current transaction status number in the transaction status and operation definition of FIG. 3. If the input message is a time-out message, the task performs a time-out operation function corresponding to the current state. In this case, the task may terminate the transaction or retransmit the sub transaction message to another task. When the corresponding transaction ends, the corresponding task releases the assigned transaction ID and adjusts the transaction ID release index of the transaction allocation table of FIG. 5. When retransmitting the sub transaction message, the transaction state information is used.

The transaction ID return operation of the task according to the embodiment of the present invention is as follows. That is, the transaction ID to be released is recorded in the entry indicated by the transaction ID release index of the transaction ID allocation table of FIG. 5. The transaction ID release index is adjusted as in Equation 3 below.

Transaction ID Release Index Value = Transaction ID Release Index Value ++% (K + 1)

Herein, the transaction ID release index value means an index position of a transaction ID allocation table in which a transaction ID to be released is recorded when the task returns a corresponding transaction ID, where K is an entry in the transaction ID allocation table. As a number, the number is one greater than the number of entries in the transaction management table.

When the transaction overflow value is set to '1', the task is set to '0' again to release the transaction overflow.

Transaction ID allocation of the task according to an embodiment of the present invention is as follows. That is, the task allocates the transaction ID of the entry indicated by the transaction ID allocation index of the transaction ID allocation table of FIG. 5 to the input transaction message. The transaction ID allocation index is adjusted as shown in Equation 4 below.

Transaction ID Allocation Index Value = Transaction ID Allocation Index Value ++% (K + 1)

Herein, the transaction ID allocation index value means an index position of a transaction ID allocation table in which a transaction ID to be allocated is recorded when the task allocates a corresponding transaction ID to the transaction management table to perform a new task. Is the number of entries in the transaction ID allocation table, which is one greater than the number of entries in the transaction management table.

The task then checks whether a transaction overflow occurs. The checking operation may be performed by checking whether the transaction ID release index value and the transaction ID allocation index value are the same. If the transaction ID release index value and the transaction ID allocation index value are the same, it means that a transaction overflow occurs without a transaction ID allocated to the transaction ID.

If the transaction overflow value is set to '1', the task no longer processes a new transaction. In addition, the task preferentially processes the input sub-transaction response message and the time-out message to solve the transaction overflow.

1 to 5, the transaction operation table, the transaction state management table, and the transaction ID allocation table according to the embodiment of the present invention in the exchange system manage transactions by ID and manage each transaction in a plurality of transaction states and subtransactions. You can see that it manages by transaction state unit. This shows that the task can simultaneously process multiple messages, ie transaction messages, response messages, and time-out messages.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

As described above, in the exchange system, the transaction operation table, the transaction state management table, and the transaction ID assignment table according to the embodiment of the present invention manage transactions by ID, and divide each transaction into a plurality of transaction states and sub-transactions. This allows the task to process multiple messages simultaneously without time delay.

Claims (1)

In the transaction management table of the message processing task in a switching system: A transaction type definition portion for storing a transaction type ID, a transaction message ID, a first transaction state number, and an operation function routine indicator for the first transaction state for each transaction type, and the corresponding transaction types Transaction action consisting of transaction state and action definition part that stores transaction state number, response message ID, time-out message ID, D, action function routine indicator, and time-out action function routine indicator for each transaction state. Table, A transaction state management table that is allocated to correspond to a plurality of input transaction messages consisting of a transaction ID, a transaction identifier, a transaction type ID, a current transaction status number, a timer ID, and a transaction status number indicator. , The transaction ID is recorded in each entry, and after the transaction ID release and allocation operation of the task, the transaction ID release index and the transaction ID creation index are respectively represented by Equations 5 and 6, respectively. A transaction management table, characterized in that it consists of a transaction ID-allocation table whose value is adjusted. Transaction ID Release Index Value = Transaction ID Release Index Value ++% (K + 1) Herein, the transaction ID release index value means an index position of a transaction ID allocation table in which a transaction ID to be released is recorded when the task returns a corresponding transaction ID, where K is an entry in the transaction ID allocation table. As a number, the number is one greater than the number of entries in the transaction management table. Transaction ID Allocation Index Value = Transaction ID Allocation Index Value ++% (K + 1) Herein, the transaction ID allocation index value means an index position of a transaction ID allocation table in which a transaction ID to be allocated is recorded when the task allocates a corresponding transaction ID to the transaction management table to perform a new task. Is the number of entries in the transaction ID allocation table, which is one greater than the number of entries in the transaction management table.