Browse Prior Art Database

ALCAP-Less AAL2 Channel Establishment

IP.com Disclosure Number: IPCOM000008235D
Original Publication Date: 2002-May-29
Included in the Prior Art Database: 2002-May-29
Document File: 5 page(s) / 61K

Publishing Venue

Motorola

Related People

Enrico Penas: AUTHOR [+2]

Abstract

In 3GPP UMTS Systems, AAL2 (ATM Adaptation Layer Type 2) connections are used on the Iu-CS, Iur, and Iub interfaces for transport of UMTS user data. The standardized way to establish AAL2 ATM Channels (hereafter referred to as AAL2 channels) is thru the use of the AAL2 Type 2 Signalling Protocol (aka ALCAP - Access Link Control Application Part). It has not been possible in the past to establish AAL2 channels without using ALCAP, at least in a standards compliant manner. There is a need to establish AAL2 channels without using ALCAP and actual implementations have used proprietary means to accomplish this. However these proprietary mechanisms are not standards compliant and implementations using the known proprietary mechanisms will not work with implementations that do support the standardized method. This paper proposes a method that can establish AAL2 channels without using ALCAP in a standards compliant manner which then allows compatibility with implementations using existing 3GPP standards (assuming implementation supporting ALCAP less method also supports standardized ALCAP).

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 31% of the total text.

ALCAP-Less AAL2 Channel Establishment

Enrico Penas and Alberto Montilla

                                           UMTS System Requirements and Architecture Group, GTSS                

Motorola Inc.

3223 N. Wilke

Arlington Heights, IL 60004

1                       Abstract

In 3GPP UMTS Systems, AAL2 (ATM Adaptation Layer Type 2) connections are used on the Iu-CS, Iur, and Iub interfaces for transport of UMTS user data.  The standardized way to establish AAL2 ATM Channels (hereafter referred to as AAL2 channels) is thru the use of the AAL2 Type 2 Signalling Protocol (aka ALCAP - Access Link Control Application Part).  It has not been possible in the past to establish AAL2 channels without using ALCAP, at least in a standards compliant manner.  There is a need to establish AAL2 channels without using ALCAP and actual implementations have used proprietary means to accomplish this.  However these proprietary mechanisms are not standards compliant and implementations using the known proprietary mechanisms will not work with implementations that do support the standardized method.  This paper proposes a method that can establish AAL2 channels without using ALCAP in a standards compliant manner which then allows compatibility with implementations using existing 3GPP standards (assuming implementation supporting ALCAP less method also supports standardized ALCAP).

2                       Introduction

In 3GPP UTRAN (UMTS Terrestrial Radio Access Network), the underlying transport provided for the radio specific protocols is ATM.  AAL2 [2] and AAL5 [3] are the standardized ATM adaptation layers specified for use in the UTRAN.  AAL2 channel establishment is mandated using ITU-T Q.2630 [1, 12].  In general, use of [1, 12] for AAL2 channel establishment is adequate and appropriate.  However, there are cases when use of [1, 12] is not optimal or even possible.  These cases include:

-          Early trial or demonstration.  Often times or most times, network operators desire to see demonstration of functionality and operation within a UMTS system.  These trials will use not fully completed, pre-commercial vendor implementations.  Not needing to develop a reliable ALCAP immediately would allow vendors to demonstrate the new UMTS radio technology sooner.

-          Easier validation of new UMTS radio protocols.   To better isolate testing of radio specific protocols, transport control protocol signalling (e.g. ALCAP) can be taken out of the testing environment.

-          Reduced product development and quicker time to market.  Not having to implement ALCAP but still having a product that can establish AAL2 channels.  The rationale for this would be an implementation that for first commercial release implements an ALCAP less solution (interworking then with another implementation that also supports this solution) and then later releasing a second or subsequent that may also support the standardized ALCAP.  Ability to save development on the standardized ALCAP by postponing this functionality allows quicker time to market.

The current known methods of an ALCAP less method are proprietary and incompatible....