KR100892200B1 - Method for resolving an erq collision at the time of establishing an alcap call in an atm system - Google Patents

Abstract

The present invention discloses a method for handling an ERQ collision when establishing an ALCAP call in an ATM system. The ATM system to which the ERQ collision processing method is applied when setting up an ALCAP call in the ATM system according to the present invention includes a first node and a second node, and each of the first node and the second node includes a protocol entity and a nodal function. In addition, a method for handling an ERQ collision in setting up an ALCAP call in an ATM system according to the present invention may include (a) a protocol entity of the first node sending a first ERQ message for a first resource to a protocol entity of the second node. Transmitting (b) receiving the first ERQ message at a protocol entity of the second node and passing the received first ERQ message to a nodal function of the second node, (c) the second node Delivering a second ERQ message for the first resource to a protocol entity of a second node prior to receiving the first ERQ message in a nodal function of (d) the protocol entity of the second node by the second entity; Forwarding an RLC message to a nodal function of the second node in response to receiving an ERQ message, and (e) a third ERQ for a second resource after the nodal function of the second node receives the RLC message; Me If a step of passing a protocol entity of the second node. According to the ERQ collision processing method according to the present invention, when the ERQ message for the same resource is respectively transmitted in the power system and the host system, one of the two ERQ messages is exchanged with the ERQ message for the new resource. All can be processed successfully.

Description

METHOD FOR RESOLVING AN ERQ COLLISION AT THE TIME OF ESTABLISHING AN ALCAP CALL IN AN ATM SYSTEM}

1 is a diagram illustrating a network connection between a large AAL2 node and a local AAL2 node according to an embodiment of the present invention.

2 is a diagram illustrating a process of processing an ERQ collision according to an embodiment of the present invention.

<Description of Major Symbols in Drawing>

110: power AAL2 node

120: National AAL2 node

112, 122: protocol entity

114, 124: Nodal functions

The present invention relates to ALCAP call setup in an ATM system, and more particularly to a method for handling ERQ collisions that occur during ALCAP call setup.

As mobile services evolved to 3G, the 3GPP (The Third Generation Partnership Project), a standardization organization, was formed around Europe and Japan to promote asynchronous IMT-2000 standardization. IMT-2000 Asynchronous WCDMA R4 is one of the asynchronous standards proposed by 3GPP. The release mechanism of 3GPP is named based on the year of the release of R99, R00, etc., and then, R4, R5, R6, etc. at the meeting under the Technical Specification Group (TSG) Service and System Aspects (SA) Working Group 2 (WG2). Corrected.

Of these, R4 is the most active release version. R4 has a new communication network structure in which a CS (Circuit Switched) Domain is separated into a mobile switching center server and a media gateway on a network reference model. This new network structure is required in the 3G asynchronous communication standard for integrating the existing network and packet networks, interworking of different call signaling protocols between the circuit network and the packet network, and the various types of media streams. This required a gateway to handle new functions such as format conversion and transmission. The separated gateway model has greater scalability than the integrated model of 2G and / or 2.5G to support a variety of services, and can be located anywhere in the media stream's transmission path, facilitating network configuration through the media gateway. Has an advantage.

On the other hand, ATM communication in the above-described IMT-2000 WCDMA R4 structure applies the AAL 2 protocol to the traffic data for the efficiency of the communication line. AAL2 (ATM2) is included in the asynchronous IMT-2000 international standard specified by the International Telecommunications Standardization Group (ITU-T). Under the AAL2 protocol, the host system and the host system exchange an AAL2 signaling message, that is, an Access Link Control Application Part (ALCAP) call by exchanging an ERQ (Establish Request) ERQ (Establish Confirm), REL (Release Request), or RLC (Release Confirm). Perform setting and clearing.

In the process of exchanging ERQ messages, the host system and the power system may transmit ERQ messages for the same resources. By the way, according to the conventional ALCAP call setup method, when the ERQ message is sent from the power system to the own system but before being transferred to the nodal function of the own system, the ERQ message is transmitted to the power system for the same resource in the nodal function. It is defined as a collision and both associated call setup requests fail. Accordingly, there is a problem that the call success rate is lowered in the prior art.

It is an object of the present invention that an ERQ message occurs in an ATM system when an ERQ message is sent from a supervisor system to a local system but before the ERQ message is transmitted to the supervisor system for the same resource in the nodal function, the ERQ collision occurs. In addition, the present invention provides a method for handling ERQ collision in an ATM system that can successfully handle all associated call setup requests.

In an ATM system according to an embodiment of the present invention, an ATM system to which a method for handling an ERQ collision when an ALCAP call is set up includes a first node and a second node, and each of the first node and the second node is a protocol. Includes entity and nodal functions. In addition, a method for handling an ERQ collision in setting up an ALCAP call in an ATM system according to the present invention may include (a) a protocol entity of the first node sending a first ERQ message for a first resource to a protocol entity of the second node. Transmitting (b) receiving the first ERQ message at a protocol entity of the second node and passing the received first ERQ message to a nodal function of the second node, (c) the second node Delivering a second ERQ message for the first resource to a protocol entity of a second node prior to receiving the first ERQ message in a nodal function of (d) the protocol entity of the second node by the second entity; Forwarding an RLC message to a nodal function of the second node in response to receiving an ERQ message, and (e) a third ERQ for a second resource after the nodal function of the second node receives the RLC message; Me If a step of passing a protocol entity of the second node.

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

Figure 1 shows a block diagram of a large country AAL2 node and a local AAL2 node according to an embodiment of the present invention. As shown in FIG. 1, the power AAL2 node 110 and the power station AAL2 node 120 are connected to each other through the network 150. The power station AAL2 node 110 and the self station AAL2 node 120 are nodes that process AAL2. In the case of WCDMA, the AAL2 node 110 and the local AAL2 node 120 may be MGW (Media Gateway) or RNC (Radio Network Controller) equipment, but are not limited thereto. In addition, in FIG. 1, the network 150 is a network using AAL2 such as a WCDMA network.

Each of the power AAL2 node 110 and the power station AAL2 node 120 includes protocol entities 112 and 122 and nodal functions 114 and 124 to process the Q.2630 specification. The protocol entity 112, 122 decodes the AAL2 signaling message received from the power or domestic AAL2 node 110, 120, passes it to the nodal functions 114 and 124, and receives the AAL2 signaling received from the nodal functions 114 and 124. It encodes a message and transmits the message to a large or local AAL2 node (110, 120). The nodal functions 114 and 124 perform resource reservation, reservation cancellation, connection establishment, connection release, and maintenance by the decoded AAL2 signaling message information. Each of the power AAL2 node 110 and the power station AAL2 node 120 may further include other components necessary for processing AAL2 in addition to the above-described protocol entities 112 and 122 and nodal functions 114 and 124. Since it is irrelevant to the features of the invention, the description thereof will be omitted herein.

Under the AAL2 protocol, a large AAL2 node 110 and a local AAL2 node 120 exchange an AAL2 signaling message, that is, Establish Request (ERQ) Establish Confirm (ECF), Release Request (RL), and Release Confirm (RLC). (Access Link Control Application Part) Perform call setup and release. The ERQ message is a call setup request message, and the ECF message is a message indicating that call setup is completed. In addition, the REL message is a message for requesting to release the call, and the RLC message is a message indicating that call release is completed. For example, when an ERQ message is sent from the local AAL2 node 120 to the large AAL2 node 110, the large AAL2 node 110 transmits an ECF message to the local AAL2 node 120, thereby completing the call setup. In addition, when a REL message is sent from the local AAL2 node 120 to the large AAL2 node 110 and the large AAL2 node 110 transmits an RLC message to the local AAL2 node 120 in response, the call setup release is released. Is done. According to an embodiment of the present invention, the RLC message indicating that the call setup release is completed is exchanged between the power AAL2 node 110 and the power station AAL2 node 120. 120) may be distinguished from an RLC message exchanged between a protocol entity and a nodal function within either side. The RLC message indicating the occurrence of the ERQ collision will be described again in the relevant part of the present specification.

On the other hand, for the call setup request, resources to be used for call setup must be determined. The resources used for call establishment are defined by the CEID (AAL type 2 Connection Element Identifier) parameter defined in the ALCAP specification. The CEID parameter consists of a Path Identifier (PI) and a Channel Identifier (CID). If two predetermined resources have the same PI and CID, the two resources are classified as the same resource.

2 is a view for explaining the ERQ collision processing method according to the present invention.

In step S100, the first ERQ message for resource A is transmitted from the power station AAL2 node 110. The first ERQ message sent is first received by protocol entity 122 at T1 and then by nodal function 124 at T3. The nodal function 124 transmits the first ECF message to the counterpart AAL2 node 110 at T6 in response to the received first ERQ message. The first ECF message sent from the nodal function 124 is passed through the protocol entity 122 (T7) to the power AAL2 node 110 (T8). That is, the first ECF message is transmitted from the local AAL2 node 120 to the large AAL2 node in response to the first ERQ message transmitted from the first large AAL2 node 110 to the large AAL2 node. As the power AAL2 node 110 receives the first ECF message, the call setup request from the power AAL2 node 110 is successfully completed.

Meanwhile, the nodal function 124 transmits a second ERQ message for the same resource A to the protocol entity 220 to T2 before receiving the first ERQ message from the protocol entity 122 (S200). In this case, according to the conventional ALCAP call setup method, before the first ERQ message is delivered to the nodal function 124, the second AER2 node 110 receives a separate second ERQ message for the same resource from the nodal function 124. Since the ERQ collision occurs between the first ERQ message and the second ERQ message, both ERQ messages fail. However, according to an embodiment of the present invention, as described below, both ERQ messages successfully perform a call setup request.

Protocol entity 122 receives a second ERQ message from nodal function 124 at T4. The protocol entity 122 has already received the first ERQ message from the power AAL2 node 110 at T1 and passed the received first ERQ message to the nodal function 124 for the same resource as the first ERQ message. Since the second ERQ message is received from the nodal function 124, the protocol entity 122 recognizes the ERQ collision. Recognizing the ERQ collision, the protocol entity 122 transmits the RLC message to the nodal function 124 at T5 without transmitting the received second ERQ to the power AAL2 node 110 (S220).

Here, the RLC message passed to the nodal function 124 is generated by the protocol entity 122 to inform the ERQ collision, and is different from the RLC message generated to indicate that the conventional call setup release is completed. According to an embodiment of the present invention, the RLC message generated to inform the ERQ collision further includes a flag value indicating that the message is generated by the ERQ collision. Specifically, the flag value is marked TRUE if the RLC message is caused by an ERQ collision, or FALSE otherwise, so that the nodal function 124 receiving the RLC message is different from the RLC message generated by the ERQ collision. RLC messages can be distinguished. Since only the external elements between the AAL2 node 110 and the AAL2 node 120 are defined in the AAL2 related standard, the protocol is transmitted between the protocol entity 122 and the nodal function 124 inside the AAL2 node 120 in this manner. The inclusion of additional flags in the RLC message does not deviate from the AAL2 specification.

The nodal function 124 receives the RLC message delivered from the protocol entity 122 at T9. Then, in response to receiving the RLC message, nodal function 124 allocates a new resource B rather than resource A to generate a third ERQ message for resource B. The nodal function 124 transfers the third ERQ message to the protocol entity 122 at T10 (S240). The protocol entity 122 receives the third ERQ message at T11 and transmits the received third ERQ message to the counterpart AAL2 node 110 in response. Upon receiving the third ERQ message at T12, the large country AAL2 node 110 transmits the second ECF message to the local AAL2 node 120 in response to the third ERQ message (S260). The second ECF message sent from the power AAL2 is finally delivered to the nodal function 124 via the protocol entity 122. Thus, the call setup request from the local AAL2 node 110 is also completed successfully.

In FIG. 2, the ERQ message exchange is shown in the protocol entity 122 and the nodal function 124 in the local AAL2 node 120, but in another embodiment in the large AAL2 node 110 rather than the local AAL2 node 120. The above-described ERQ message exchange may take place. Even in this case, since the basic process of processing the ERQ message is the same as in FIG. 2 described above, description thereof will be omitted.

Preferred embodiments of the present invention described above are disclosed for the purpose of illustration, and various substitutions, modifications and changes within the scope of the technical spirit of the present invention for those skilled in the art to which the present invention pertains. Modifications may be made, but such substitutions and changes should be regarded as falling within the scope of the following claims.

As described above, according to the ERQ collision processing method according to the present invention, when the ERQ message for the same resource is respectively transmitted in the power system and the host system, one ERQ message is exchanged with the ERQ message for the new resource. All call setup requests can be successfully processed.

Claims (9)

An ATM system, wherein the ATM system includes a first node and a second node, each of the first node and the second node including a protocol entity and a nodal function, the method for handling an ERQ collision when establishing an ALCAP call. (a) the protocol entity of the first node sending a first ERQ message for a first resource to the protocol entity of the second node, (b) receiving the first ERQ message at a protocol entity of the second node and passing the received first ERQ message to a nodal function of the second node, (c) forwarding a second ERQ message for the first resource to a protocol entity of a second node prior to receiving the first ERQ message in the nodal function of the second node, (d) forwarding an RLC message to a nodal function of the second node in response to the protocol entity of the second node receiving the second ERQ message; and (e) forwarding a third ERQ message for a second resource to a protocol entity of the second node after the nodal function of the second node receives the RLC message; Method for handling ERQ conflicts. According to claim 1, After the step (b), In response to the nodal function of the second node receiving the first ERQ message, forwarding a first ECF message for the first resource to a protocol entity of the second node. To handle ERQ collisions when setting up ALCAP calls on Windows. The method of claim 2, The protocol entity of the second node further comprises sending the first ECF message to the first node in response to receiving the first ERQ message. Way. The method of claim 1, wherein in step (e), And failing to process a second ERQ message for the first resource in response to the nodal function of the second node receiving the RLC message. The method of claim 1, And the RLC message includes a flag indicating that an ERQ message collision has occurred. According to claim 1, After the step (e), The protocol entity of the second node further comprises sending a third ERQ message for the second resource to the first node. The method of claim 6, In response to receiving the third ERQ message, the first node further comprising sending a second ECF message for the third ERQ message to the first node. Method for dealing with conflicts. The method of claim 1, And wherein the first and second resources are defined by CEID parameters. An ATM system, wherein the ATM system includes a first node and a second node, each of the first node and the second node including a protocol entity and a nodal function, the method for handling an ERQ collision when establishing an ALCAP call. (a) the first node sending a first ERQ message for a particular resource to the second node, (b) the nodal function of the second node forwarding a second ERQ message for the particular resource to a protocol entity of the second node, (c) recognizing the occurrence of an ERQ message collision at a protocol entity of the second node and delivering a message indicating the occurrence of the ERQ message collision to a nodal function of the second node; and (d) generating a third ERQ message for the particular resource and another resource in response to the nodal function of the second node receiving a message indicating the occurrence of the ERQ message conflict. How to handle ERQ conflicts in setup.

Images