KR100385219B1 - Method for Overload Controlling in Real-Time System - Google Patents

Abstract

The present invention relates to an overload control method of a real-time system that can automatically solve the instantaneous overload using a transaction ID.

In the conventional real-time system, if it is determined that an overload occurs in a predetermined application process, there is a problem that all the subscribers cannot receive any service by unconditionally deleting all messages currently stored in the message queue provided in the application process.

The present invention divides the degree of overload into several stages, determines the priority of the message to be deleted at each overload stage, and if the server is overloaded, the overload stage is identified based on the transaction ID usage rate, and the identified overload is determined. By separating and processing the message received from the client based on the priority of the message to be deleted in the step, it is possible to provide an uninterrupted service while minimizing the system failure by detecting an overload in advance. In addition, by controlling the overload step by step, it is possible to dynamically control the overload, it is possible to use resources efficiently.

Description

Overload Controlling in Real-Time System

The present invention relates to an overload control method of a real-time system, and more particularly, to an overload control method of a real-time system that can automatically solve the instantaneous overload using a transaction ID.

Real-time processing systems such as Home Location Register (HLR), Authentication Center (AuC), Equipment Identification Register (EIR), Gateway Mobile Location Center (GMLC), Service Control Point (SCP), Authentication Authorization and Accounting (AAA) When there are multiple processes for accessing various databases in a server such as a mobile communication system or a banking system, each process in the server has a message queue for temporarily storing messages received from a client. In turn, messages are processed in the order in which they are sent through the message queue.

1 is a road showing the configuration of an overload control device of a conventional real-time system, in the overload control process 10 detects the overload occurring in a plurality of application processes (AP1, AP2, ..., APn) application process (AP1, AP2, ..., APn) is managed.

2 is a road illustrating an overload control method of a conventional real-time system, and the overload control process 10 includes message queues Q1, Q2, ..., Qn provided in respective application processes AP1, AP2, ..., APn. The state information request message is transmitted to each application process AP1, AP2, ..., APn through S10.

In the process S10, each application process AP1, AP2, ..., APn, which has received the status information request message from the overload control process 10 through the message queues Q1, Q2, ..., Qn, has its own state information. It is included in the response message to pass to the overload control process 10.

The overload control process 10 which has transmitted the status information request message to each of the application processes AP1, AP2,..., APn in step S10 described above has each application process AP1, AP2, within a predetermined time, for example, 3 seconds. …, It is checked whether a response message is transmitted from APn (S12).

When the response message is received within the preset time as a result of the checking of the process S12, it is determined that the corresponding application process is normally performing the message processing, and when the response message is not received within the preset time, it is determined that the corresponding application process is overloaded. To read and delete all the messages accumulated in the message queue provided in the application process (S14, S16).

As described above, in the conventional real-time system, if it is determined that an application process is overloaded, all the messages currently stored in the message queue provided in the application process are unconditionally deleted so that all the subscribers cannot receive any service. There is a problem.

The present invention has been made to solve the above-mentioned problem, divides the degree of overload into several stages, sets the priority of the message to be deleted in each overload stage, and if the server is overloaded, the transaction ID usage rate Understand the overload phase based on the message, and separate / delete / process the message received from the client based on the priority of the message to be deleted at the identified overload level to provide uninterrupted service while minimizing the system failure. The purpose is to provide an overload control method for a real-time system.

1 is a view showing the configuration of an overload control device of a conventional real-time system.

2 is a view for explaining the overload control method of a conventional real-time system.

3 is a view showing the configuration of an overload control apparatus of a real-time system to which the overload control method of the real-time system according to the present invention is applied.

Figure 4 is a flow chart for explaining the overload control method of a real-time system according to the present invention.

5 is a diagram illustrating a configuration of a mobile communication network to which an overload control method according to the present invention is applied.

*** Explanation of symbols for the main parts of the drawing ***

20. Overload control process, 30. Mobile terminal,

40.Node_B, 50.RNC,

60.MSC / VLR, 70.SGSN / GGSN,

80.SMSC, 90.MTT-2000 HLR / AuC / EIR

95.TCAP

An overload control method of a real-time system according to the present invention for achieving the above object comprises: a setting process of dividing the degree of overload into several steps and setting a priority of a message to be deleted at each overload step; Determining whether an overload has occurred in the server when a message is received from the client in the overload control process of the server; Determining that the overload occurs in the server when the server is overloaded, and determining whether the received message has a higher priority than a message to be deleted in the identified overload step; ; And if the priority of the received message is not higher than the priority of the message to be deleted in the identified overload step, deleting the received message.

In this case, if the priority of the received message is higher than the priority of the message to be deleted in the identified overload step, the received message is selected by selecting one of the transaction IDs not used by the overload control process. Assigning to the transaction ID and registering the selected transaction ID as a transaction ID used by the overload control process; Delivering the received message and a transaction ID assigned to the received message to a corresponding application process; Receiving a response message to the message together with the transaction ID from the application process; And transmitting the received response message to a corresponding client and registering the transaction ID as a transaction ID not used by the overload control process.

The determination as to whether or not an overload has occurred in the server is based on a ratio of transaction IDs not used by the overload control process.

The step of identifying which stage the generated overload belongs to is based on a ratio for a transaction ID not used by the overload control process.

Hereinafter, an overload control method of a real time system according to a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings.

3 is a road communication, a mobile communication system such as HLR, AuC, EIR, GMLC, SCP, AAA or the like, which shows the configuration of an overload control device of a real-time system to which the overload control method of the real-time system according to the present invention is applied. The server comprises a plurality of application processes (AP1, AP2, ..., APn) and the overload control process 20.

The server is a system that has a database. When a server receives a message that needs to be processed from a client that is mapped with the server, the server should be able to immediately process the response in real time and respond to it.

As described above, the plurality of application processes AP1, AP2,..., APn receive a message and a transaction ID through the overload control process 20 to a client that generates a transaction (a pair of messages transmitted and received between the client and the server). A series of procedures is performed until the response message is sent.

The overload control process 20 is a process in charge of overload control, and manages a message received from a client using a transaction ID. The transaction ID is a transaction ID used by the overload control process 20 (Busy), Managed in list format, separated by idle IDs.

Therefore, initially all transaction IDs are stored in an idle list that is not used, and when a message is received from the client, the overload control process 20 selects one of the transaction IDs stored in the idle list from the client. It is assigned to the received message, and the selected transaction ID is stored in the busy list.

As described above, when the overload control process 20 receives a message from the client, the overload control process 20 assigns a transaction ID to the received message, and then transmits the message along with the transaction ID to the application process that will process the message. Receives a response message with a transaction ID from the application process that processed the and sends the response message to the client, and stores the transaction ID in the idle list.

As described above, the maximum value of the transaction ID varies depending on the processing capacity of the server and the client.

4 is a flowchart for explaining an overload control method of a real-time system according to the present invention.

First, the degree of overload is divided into several stages, and the priority of messages to be deleted in each overload stage is set (S20).

Subsequently, when a message is received from the client in the overload control process 20 of the server, the message reception from the client is concentrated at any moment to determine whether the server is overloaded (S22 and S24).

The determination as to whether or not an overload has occurred in the server in step S24 is made based on the number of transaction IDs not used by the overload control process 20 or the number of transaction IDs used by the overload control process 20. If the number of transaction IDs not used by the overload control process 20 is less than or equal to a certain percentage, or the number of transaction IDs used by the overload control process 20 is more than or equal to a certain percentage, then the server is overloaded. .

That is, if message reception from the client is concentrated at any moment, the number of transaction IDs used by the overload control process 20 increases, and the number of transaction IDs not used by the overload control process 20 decreases. do. Thus, the server is overloaded.

As a result of the determination of step S24, if an overload occurs in the server, it is determined to which step the overload currently occurs and determines whether the message received in step S22 is a message to be deleted (S26, S28). .

The grasp of which step the overload currently occurring in the above-mentioned process S26 belongs is determined based on the ratio with respect to the transaction ID not used by the overload control process 20. FIG.

The determination as to whether or not the message received in step S22 is a message to be deleted in step S28 is determined based on the priority of the message to be deleted in each overload step set in step S20. If the priority of the message received in step S22 is not higher than the priority of the message to be deleted in the overload step identified in step S26, the message received in step S22 is deleted.

As a result of the determination in step S28, if the message received in step S22 is a message to be deleted, the corresponding message is deleted (S30).

Meanwhile, as a result of the determination of step S28, the priority of the message received in step S22 is higher than the priority of the message to be deleted in the overload step identified in step S26, and the message received in step S22 should be deleted. If it is not a message, one of the transaction IDs stored in the idle list is selected and assigned to the message received in step S22, and the selected transaction ID is stored in the busy list (S32).

Thereafter, the message received in step S22 and the transaction ID assigned to the message are transferred to the corresponding application process (S34).

The application process that has received the message and the transaction ID from the overload control process 20 in step S34 processes the message and then transfers the response message to the overload control process 20 to the overload control process 20. When the response message is transmitted to step 20, the transaction ID received with the message is transmitted together with the message in step S34.

Subsequently, when receiving the response message and the transaction ID for the corresponding message from the application process that has received and processed the message delivered in step S34, the response message received from the application process is transmitted to the client and received together with the response message. The received transaction ID is stored in the idle list (S36, S38).

Hereinafter, an operation process according to the overload control method of the present invention will be described with reference to FIG. 5.

5 is a road showing an example of the configuration of a mobile communication network to which the overload control method according to the present invention is applied, location registration, call processing, and various additional services in a wideband code division multiple access (WCDMA); A mobile terminal 30 requesting the user's request, a Node_B 40 serving as a base station, a Radio Access Network Controller (RNC) 50 serving as a controller of the Node_B 40, location registration, call processing, and various additions. MSC / VLR (Mobile Switched Center / Visited Location Register) 60 processing services, SGSN / GGSN (Serving GPRS Service Node / Gateway GPRS Service Node) 70 processing packet data services, and Short Message Service SMSC (Short Message Service Center) processing 80, and network elements such as IMT-2000 HLR / AuC / EIR (90) for storing subscriber information in the third generation mobile communication network.

As described above, the IMT-2000 HLR / AuC / EIR 90 includes a plurality of ASEs (ASE1, ASE2, ..., ASEn) that process location registration, call processing, and various additional services, and MSC / VLR ( 60), a Transaction Capability Application Part (TCAP) 95 for receiving a message from a client such as SGSN / GGSN 70, SMSC 80, etc., and delivering the message to the ASC.

First, IMT-2000 HLR / AuC / EIR (90) divides the degree of overload into five steps as shown in Table 1, assuming the maximum value of transaction ID is 2,000, and the priority of the message to be deleted at each overload step. Set.

Overload Stage 1 If there are less than 400 transaction IDs left in the idle list Delete additional service related messages Overload Stage 2 If there are less than 300 transaction IDs left in the idle list Deleting messages related to location-based services Overload Stage 3 If there are less than 200 transaction IDs left in the idle list Delete messages related to incoming call processing Overload Stage 4 If there are less than 100 transaction IDs left in the idle list Delete Short Message Related Messages Overload Level 5 If there are 0 transaction IDs left in the idle list Delete location registration message

When there is a request for location registration, call processing, and various additional services from the mobile terminal 30, the IMT-2000 HLR / AuC / EIR 90 performs an MSC / VLR 60, SGSN / GGSN 70, and SMSC 80. The mobile terminal 30 receives and processes a request for location registration, call processing, and various additional service requests requested by the mobile terminal 30, and then responds to the mobile terminal 30 requesting location registration, call processing, and various additional services. ), If a message receives a lot at a moment, the transaction ID is stored a lot in the busy list and decreased in the idle list. Thus, the IMT-2000 HLR / AuC / EIR 90 leads to an overload condition, and the TCAP 95 identifies the stage of the overload that occurred in the IMT-2000 HLR / AuC / EIR 90, and the identified overload stage Based on this, messages are processed in order of priority.

For example, if the currently identified overload phase is three levels, the location-based service-related message and the additional service-related message having a lower priority than the incoming call processing-related message, including the incoming call processing-related message, are deleted, and the incoming call processing is deleted. Only short service-related messages and location registration-related messages that have higher priority than the related messages are delivered to ASE.

The overload control method of the real-time system of the present invention is not limited to the above-described embodiment, and may be variously modified and implemented within the range allowed by the technical idea of the present invention.

According to the overload control method of the real-time system of the present invention as described above, by dividing the degree of overload into several stages, after determining the priority of the message to delete at each overload stage, if the server is overloaded, use of transaction ID It identifies the overload phase based on the rate and separates / processes the message received from the client based on the priority of the message to be deleted at the identified overload stage. To provide services.

In addition, by controlling the overload step by step, it is possible to dynamically control the overload, it is possible to use resources efficiently.

Claims (4)

A setting process of dividing the degree of overload into several steps and setting a priority of messages to be deleted in each overload step; Determining whether an overload has occurred in the server when a message is received from the client in the overload control process of the server; Determining that the overload occurs in the server when the server is overloaded, and determining whether the received message has a higher priority than a message to be deleted in the identified overload step; ; If the priority of the received message is not higher than the priority of the message to be deleted in the identified overload step, deleting the received message. The method of claim 1, wherein if the priority of the received message is higher than the priority of the message to be deleted in the identified overload step, Selecting one of the transaction IDs not used by the overload control process and assigning the received message to the received message and registering the selected transaction ID as a transaction ID used by the overload control process; Delivering the received message and a transaction ID assigned to the received message to a corresponding application process; Receiving a response message to the message together with the transaction ID from the application process; And transmitting the received response message to a corresponding client, and registering the transaction ID as a transaction ID not used by the overload control process. The method of claim 1, wherein the determination as to whether or not the server is overloaded, Overload control method of the real-time system, characterized in that based on the ratio to the transaction ID not used by the overload control process. The method of claim 1, wherein the grasp of which step the generated overload belongs to, Overload control method of the real-time system, characterized in that based on the ratio to the transaction ID not used by the overload control process.