KR20040035086A - Method for Processing of Emergency Message - Google Patents

Abstract

PURPOSE: A method for processing an emergency message is provided to define an emergency message delimiter on an MEGACO(Media Gateway Controller) message transceived between an MGC(Media Gateway Controller) and an MGW(Media Gateway), and to add information showing that the corresponding message is an emergency message, thereby quickly distinguishing the emergency message from a general message without a decoding process for quick processing. CONSTITUTION: An MGC or an MGW receives an MEGACO message(S31), confirms information set in an emergency message delimiter of the received message(S32), and decides whether the corresponding message is an emergency message(S33). If so, the MGC or the MGW immediately decodes/analyzes the corresponding message, and processes the message according to decoded/analyzed results(S34,S35). The MGC or the MGW firstly processes the emergency message than other general messages, and instantly gives a higher priority to the emergency message. If the corresponding message is not the emergency message, the MGC or the MGW stands by according to a general message processing policy, and processes the message. The MGC or the MGW drives a message processing timer(S36), and decodes/analyzes the message after the timer expires(S37). The MGC or the MGW processes the message(S34,S35).

Description

{Method for Processing of Emergency Message}

The present invention relates to a method for processing a MEGACO message transmitted and received between a MGC (Media Gateway Controller) and a MGW (Media Gateway), in particular, by defining an emergency message delimiter in the MEGACO message to quickly distinguish the MEGACO message requiring emergency processing without decoding It relates to an emergency message processing method for processing.

In general, the MGC transmits and receives a MEGACO message in association with a plurality of MGWs as shown in FIG. 1. That is, the MGC 10 receives MEGACO messages from a plurality of MGWs 20, which are clients as a server, decodes and analyzes the received messages, performs a corresponding processing operation, and then encodes the processing result to the corresponding MGW ( 20).

The MEGACO message is a message defined in the H.248 protocol of standard ITU-T and is a message transmitted and received between the MGC 10 and the MGW 20. The structure of the MEGACO message is ASN.1 and ABNF according to the encoding / decoding method.

The structure of the AAG.1 MEAGCO message is as follows.

MegacoMessage :: = SEQUENCE

{

authHeader AuthenticationHeader OPTIONAL,

mess Message

}

AuthenticationHeader :: = SEQUENCE

{

Contains multiple values for authentication.

}

Message :: = SEQUENCE

{

Includes protocol version, message ID, message itself, other priorities, emergency, etc.

}

Next, the structure of the MEGACO message of the ABNF method is as follows.

MegacoMessage = LWSP [authenticationHeader SEP] message

The LWSP is a function for indicating a comment, a space, a carriage return, or parentheses. The authentication header includes various values for authentication, and the message includes a protocol version, a message ID, a message itself, and various other information (priority, emergency, etc.).

In the existing MEGACO message as above, since emergency information is included in the message along with the protocol version or message ID, all messages are processed in the order in which they are received. It is possible to know whether the message exists or if it is a message requiring urgent processing.

2 is a flowchart illustrating an operation of processing a MEGACO message received at the message receiving side of the MGC 10 or the MGW 20.

The receiving side receiving the MEGACO message decodes and analyzes the received message (S21, S22). Then, it is determined whether the message is an emergency message, and if it is an emergency message, a high priority is assigned and processed immediately.

However, the MEGACO protocol, which uses text-based or binary-based encoding / decoding, takes a considerable amount of time to encode / decode, especially for text, and takes most of the load for a message.

Therefore, as described above, since the MEGACO message itself does not have a division indicating the emergency information and can be known only by decoding, the message that is to be processed in an emergency process or a high priority cannot be processed quickly. In addition, when a large number of MEGACO messages are received, the MGC or MGW may be heavily loaded and some messages may be retransmitted or lost over time.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and an object thereof is to define an emergency message delimiter capable of distinguishing an emergency message without decoding in a MEGACO message transmitted and received between the MGC and the MGW, and an emergency message at a receiving side of the MEGACO message The information set in the delimiter is used to quickly distinguish and process a message that requires urgent processing.

1 is a schematic diagram of a system in which a MEGACO message is transmitted and received.

2 is a flowchart illustrating a conventional emergency MEGACO message processing operation.

3 is a flowchart illustrating an emergency MEGACO message processing operation according to the present invention.

Explanation of symbols on the main parts of the drawings

10: MGC 20: MGW

In the emergency message processing method of the present invention for achieving the above object, a process for transmitting by setting a value indicating that the message is an emergency message in the emergency message delimiter of the corresponding message when the message to be urgent processing is to be transmitted and; Checking whether a corresponding message is an emergency message by extracting a value set in an emergency message identifier of the message at a receiving side; As a result of the check, if the message is an emergency message, the method includes a process of decoding and analyzing the message without waiting for a predetermined time.

The message for urgent processing includes an authentication header field for selectively storing authentication information for authenticating the message, an urgent message delimiter field for setting a corresponding value when the message requires urgent processing, and an actual message. And a message field in which the message content is stored.

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

The present invention further defines an urgent message delimiter indicating an urgent message in a MEGACO message composed of an authentication header and an actual message. It is possible to determine whether an emergency message can be processed quickly so that an emergency message received even when an MGC or MGW is overloaded.

According to the present invention, the structure of a MEGACO message to which an emergency message identifier (emergency / EmergencyToken) is added is as follows according to an encoding / decoding scheme.

First, MEGACO message structure of ASN.1 method is as follows.

MegacoMessage :: = SEQUENCE

{

authHeader AuthenticationHeader OPTIONAL,

emergency BOOLEAN OPTIONAL,

mess Message

}

AuthenticationHeader :: = SEQUENCE

{

Contains multiple values for authentication.

}

Message :: = SEQUENCE

{

Includes Protocol Version, Message ID, message itself, and other information (Priority, Emergency, etc.).

}

Next, the structure of the MEGACO message of the ABNF method is as follows.

MegacoMessage = LWSP [authenticationHeader SEP] [EmergencyToken SEP] message

The LWSP is a function for indicating a comment, a space, a carriage return, parentheses, and the like, and the AuthenticationHeader includes various values for authentication. In addition, EmergencyToken is an identifier indicating whether an emergency message is present.

The message is an actual message and includes a protocol version, a message ID, a message itself, and various other information (priority, emergency, etc.).

The message has a complicated tree structure and contains various information.

FIG. 3 is a flowchart illustrating a corresponding message processing operation at a receiving side that receives a MEGACO message to which an identifier indicating whether an emergency message is added is added.

However, the following emergency MEGACO message processing criteria is preferably applied at the time of system overload in which processing of the received MEGACO message is delayed.

Receiving the MEGACO message MGC or MGW (S31), by checking the information set in the emergency message identifier of the received message (S32), it is determined whether the message is an emergency message that requires urgent processing (S33).

Thus, if the message is an emergency message, it is immediately decoded and analyzed and processed according to the analysis result (S34, S35). That is, in case of an urgent message, it is prioritized over a general message, and the resource occupancy is immediately added with a high priority according to an urgent message processing policy.

In the case of a general message, the message is processed after a predetermined time wait according to the general message processing policy. That is, when the received message is a general message, the message processing timer is driven (S36), and after the timer expires (S37), the message is decoded and analyzed and processed according to the analysis result (S34, S35).

In addition, the embodiment according to the present invention is not limited to the above description, and various alternatives, modifications, and changes can be made within the scope obvious to those skilled in the art.

As described above, the present invention defines an emergency message delimiter in the MEGACO message transmitted and received between the MGC and the MGW, and adds information indicating that the message is a message that requires urgent processing, so that the receiver side of the message decodes even when the system is overloaded. There is an effect that can be processed quickly by distinguishing the emergency message from the normal message without processing.

Claims (2)

Transmitting and setting a value indicating that the message is an urgent message in an urgent message identifier of the corresponding message at a transmitting side of an urgent message; Checking whether a corresponding message is an emergency message by extracting a value set in an emergency message identifier of the message at a receiving side; And if the message is an emergency message, processing the message by decoding and analyzing the message without waiting for a predetermined time period. The method of claim 1, The message for urgent processing includes an authentication header field for selectively storing authentication information for authenticating the message, an urgent message identifier field for setting a corresponding value when the message requires urgent processing, and an actual message. Emergency message processing method characterized in that the content comprises a message field is stored.