Content for TS 25.414 Word version: 18.0.0

3.1 Definitions 3.2 Abbreviations 4.1 ATM Transport Option 4.2 IP Transport Option
...

1 Scope p. 6

The present document specifies the standards for user data transport protocols and related signalling protocols to establish user plane transport bearers over the UTRAN Iu interface.

2 References p. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification".

[2]

ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation layer specification: Type 2 AAL".

[3]

ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation layer specification: Type 5 AAL".

[4]

ITU-T Recommendation I.366.1 (1998-06): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2".

[5]

ITU-T Recommendation E.164 (1997-05): "The international public telecommunication numbering plan".

[6]

ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)".

[7]

ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer - Service Specific Coordination Function for Support of Signalling at the Network Node Interface (SSCF-NNI)".

[8]

ITU-T Recommendation Q.2150.1 (1999-12): "AAL type 2 signalling transport converter on broadband MTP".

[9]

ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".

[10]

ITU-T Recommendation Q.2630.1 (1999-12): "AAL type 2 signalling protocol (Capability Set 1)".

[11]

ITU-T Recommendation X.213 (1995-11): "Information technology - Open systems interconnection - Network Service Definitions".

[12]

RFC 768 (1980-08): "User Datagram Protocol".

[13]

RFC 791 (1981-09): "Internet Protocol".

[14]

RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5".

[15]

RFC 2225 (1998-04): "Classical IP and ARP over ATM".

[16]

RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".

[17]

TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ".

[18]

RFC 793 (1981-09): "Transmission Control Protocol".

[19]

RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers".

[20]

ITU-T Implementor's guide (1999-12) for recommendation Q.2210 (1996-07).

[21]

ITU-T Recommendation Q.2630.2 (2000-12): "AAL type 2 signalling protocol (Capability Set 2)".

[22]

RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications".

[23]

RFC 1890 (1996-01): "RTP Profile for Audio and Video Conferences with Minimal Control".

[24]

TS 25.415: "UTRAN Iu Interface User Plane Protocols"

[25]

RFC 1661 (1994-07): "The Point-to-Point Protocol (PPP)".

[26]

RFC 1662 (1994-07): "PPP in HDLC-like Framing".

[27]

RFC 2507 (1999-02): "IP header compression".

[28]

RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)".

[29]

RFC 2686 (1996-09): "The Multi-Class Extension to Multi-Link PPP".

[30]

RFC 2509 (1999-02): "IP Header Compression over PPP".

[31] Void

[32]

RFC 3153 (2001-08): "PPP Multiplexing".

[33]

RFC 2364 (1998-07): "PPP over AAL5".

[34]

RFC 3031 (2001-01): "Multiprotocol Label Switching Architecture".

[35]

ITU-T Recommendation E.191 (2000-03): "B-ISDN addressing".

[36]

TS 25.401: "UTRAN overall description".

3 Definitions and abbreviations p. 7

3.1 Definitions p. 7

For the purposes of the present document, the following terms and definitions apply:

Access Link Control Application Part (ALCAP):

generic name for the transport signalling protocols used to set-up and teardown transport bearers

3.2 Abbreviations p. 7

For the purposes of the present document, the following abbreviations apply:

AAL

ATM Adaptation Layer

AESA

ATM End System Address

ALCAP

Access Link Control Application Part

ARP

Address Resolution Protocol

ATM

Asynchronous Transfer Mode

Core Network

GTP

GPRS Tunnelling Protocol

HDLC

High-level Data Link Control

Internet Protocol

Link Characteristics

LIS

Logical IP Subnet

MTP3b

Message Transfer Part level 3 for Q.2140

NSAP

Network Service Access Point

PDU

Protocol Data Unit

PPP

Point-to-Point Protocol

RFC

Request For Comment

RNC

Radio Network Controller

RTCP

Real-time Transport Control Protocol

RTP

Real-time Transport Protocol

Service Area

SABP

Service Area Broadcast Protocol

SABS

Service Area Broadcast Service

SAR

Segmentation and Reassembly

SCSF-NNI

Service Specific Coordination Function-Network Node Interface

SSCOP

Service Specific Connection Oriented Protocol

SSCS

Service Specific Convergence Sublayer

SSRC

Synchronisation Source

TCP

Transmission Control Protocol

TEID

Tunnel Endpoint Identifier

UDP

User Datagram Protocol

Virtual Circuit

4 Data Link Layer p. 8

ATM shall be used in the transport network user plane and the transport network control plane according to ITU-T Recommendation I.361 [1]. The structure of the cell header used in the UTRAN Iu interface is the cell header format and encoding at NNI (see figure 3/I.361).

4.2 IP Transport Option |R5| p. 8

An RNC/CN-node supporting IP transport option on the Iu interface shall support PPP protocol with HDLC framing (IETF RFC 1661 [25], IETF RFC 1662 [26]).

An RNC/CN-node supporting IP transport option on the Iu interface and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [27]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [28], IETF RFC 2686 [29]). In this case the negotiation of header compression (IETF RFC 2507 [27]) over PPP shall be performed via IETF RFC 2509 [30].