1、 ETSI TS 125 426 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); UTRAN Iur and Iub interface data transport Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the
2、 ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be
3、, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right
4、to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generat
5、ion Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP an
6、d ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting
7、Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 125 426 V15.0.0 (2018-07)33GPP TS 25.426 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs ter
8、minology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Data Link Layer . 7g34.1 ATM Transport Option 7g34.1.1 Protection Switching at ATM Layer 7g34.2 IP Transport Option 7g35 Iur and Iub Data Transport for DCH and E-DCH
9、Data Streams 7g35.1 Introduction 7g35.2 ATM Transport Option 8g35.3 IP Transport Option 8g36 Transport Signalling Application for DCH and E-DCH Data Streams 8g36.1 Introduction 8g36.2 ALCAP in ATM Transport Option 9g36.3 ALCAP in IP Transport Option 9g37 Signalling Bearer for ALCAP on Iub Interface
10、9g37.1 Introduction 9g37.2 Signalling Bearer in ATM Transport Option . 9g37.3 Signalling Bearer in IP Transport Option . 10g38 Signalling Bearer for ALCAP on Iur Interface 10g38.1 Introduction 10g38.2 Signalling Bearer in ATM Transport Option . 11g38.3 Signalling Bearer in IP Transport Option . 11g3
11、9 Interworking between ATM and IP Transport Options . 11g39.1 Introduction 11g39.2 Interworking Alternatives . 11g3Annex A (informative): Change history . 13g3History 14g3ETSI ETSI TS 125 426 V15.0.0 (2018-07)43GPP TS 25.426 version 15.0.0 Release 15Foreword This Technical Specification has been pro
12、duced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying ch
13、ange of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of subs
14、tance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 426 V15.0.0 (2018-07)53GPP TS 25.426 version 15.0.0 Release 151 Scope The present document specifies the transport bear
15、ers for the DCH/E-DCH data streams on UTRAN Iur and Iub interfaces. The corresponding Transport Network Control plane is also specified. The physical layer for the transport bearers is outside the scope of the present document. 2 References The following documents contain provisions which, through r
16、eference in this text, constitute provisions of the present document. g404 References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. g404 For a specific reference, subsequent revisions do not apply. g404 For a non-specific reference, th
17、e 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 3GPP TS 25.427: “UTRAN Iub/Iur interface user plane protocol for DCH da
18、ta streams“. 2 ITU-T Recommendation I.361 (1995-11): “B-ISDN ATM layer specification“. 3 ITU-T Recommendation I.363.2 (2000-11): “B-ISDN ATM Adaptation Layer specification; Type 2 AAL“. 4 ITU-T Recommendation I.366.1 (1998-06): “Segmentation and Reassembly Service Specific Convergence Sublayer for t
19、he AAL type 2“. 5 ITU-T Recommendation Q.2630.1 (1999-12): “AAL type 2 signalling protocol (Capability Set 1)“. 6 ITU-T Recommendation E.191 (2000-03): “B-ISDN addressing“. 7 ITU-T Recommendation X.213 (1995-11): “Information Technology - Open Systems Interconnection - Systems Interconnection - Netw
20、ork Service Definition“. 8 ITU-T Recommendation Q.2110 (1994-07): “B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)“. 9 ITU-T Recommendation Q.2130 (1994-07): “B-ISDN signalling ATM adaptation layer - Service Specific Coordination Function for Support of Signalling
21、 at the User-Network Interface (SSCF at UNI)“. 10 ITU-T Recommendation Q.2150.2 (1999-12): “AAL type 2 signalling transport converter on SSCOP)“. 11 ITU-T Recommendation Q.2210 (1996-07): “Message transfer part level 3 functions and messages using the services of the ITU-T Recommendation Q.2140“. 12
22、 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 at NNI)“. 13 ITU-T Recommendation Q.2150.1 (1999-12): “AAL type 2 signalling transport converter on broadband MTP“. 14 IETF RFC
23、791 (1981-09): “Internet Protocol“. 15 IETF RFC 1483 (1993-07): “Multiprotocol Encapsulation over ATM Adaptation Layer 5“. 16 IETF RFC 2225 (1998-04): “Classical IP and ARP over ATM“. 17 IETF RFC 768 (1980-08): “User Datagram Protocol“. ETSI ETSI TS 125 426 V15.0.0 (2018-07)63GPP TS 25.426 version 1
24、5.0.0 Release 1518 IETF RFC 2960 (2000-10): “Stream Control Transmission Protocol“. 19 IETF RFC 3332(2002-09): “Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) User Adaptation Layer (M3UA)“. 20 ITU-T Recommendation I.630 (1999-02): “ATM protection switching“. 21 ITU-T Recommendation Q.Imp22
25、10 (1996-07): “Implementors guide (03/99) for Recommendation Q.2210 (07/96)“. 22 ITU-T Recommendation Q.2630.2 (2000-12): “AAL type 2 signalling protocol (Capability Set 2)“. 23 IETF RFC 1661 (1994-07): “The Point-To-Point Protocol (PPP)“. 24 IETF RFC 1662 (1994-07): “PPP in HDLC-like Framing“. 25 I
26、ETF RFC 2507 (1999-02): “IP header compression“. 26 IETF RFC 1990 (1996-08): “The PPP Multilink Protocol (MP)“. 27 IETF RFC 2686 (1999-09): “The Multi-Class Extension to Multi-Link PPP“. 28 IETF RFC 2509 (1999-02): “IP Header Compression over PPP“. 29 IETF RFC 2460 (1998-12): “Internet Protocol, Ver
27、sion 6 (IPv6) Specification“. 30 IETF RFC 2474 (1998-12): “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers“. 31 IETF RFC 768 (1980-08): “User Datagram Protocol“. 32 IETF RFC 3153 (2001-08): “PPP Multiplexing“. 33 IETF RFC 2364 (1998-07): “PPP over AAL5“. 34 IE
28、TF RFC 3031 (2001-01): “Multiprotocol Label Switching Architecture“. 35 Void 36 ITU-T Recommendation E.164 (1997-05): “The international public telecommunication numbering plan “. 37 IETF RFC 3309 (2002-09): “SCTP Checksum Change“. 38 3GPP TS 25.414: “UTRAN Iu Interface data transport & transport si
29、gnalling“. 39 3GPP TS 25.401: “UTRAN overall description“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following term and definition applies: ALCAP: transport signalling protocol used to setup and tear down transport bearers 3.2 Abbreviations For the
30、 purposes of the present document, the following abbreviations apply: AAL2 ATM Adaptation Layer type 2 AESA ATM End System Address ATM Asynchronous Transfer Mode CPCS Common Part Convergence Sublayer CPS Common Part Sublayer ETSI ETSI TS 125 426 V15.0.0 (2018-07)73GPP TS 25.426 version 15.0.0 Releas
31、e 15DCH Dedicated Channel E-DCH Enhanced DCHHDLC High level Data Link Control HS-DSCH High Speed Downlink Shared Channel IP Internet Protocol LC Link CharacteristicsM3UA SS7 MTP3 User Adaptation layer ML/MC Multi-link / Multi-class MPLS Multiprotocol Label Switching MTP Message Transfer Part NNI Net
32、work-Node InterfaceNSAP Network Service Access Point PPP Point to Point Protocol PT Path Type SAAL Signalling ATM Adaptation Layer SAR Segmentation and Reassembly SCTP Stream Control Transmission Protocol SSCF Service Specific Co-ordination Function SSCOP Service Specific Connection Oriented Protoco
33、l SSCS Service Specific Convergence Sublayer SSSAR Service Specific Segmentation and Reassembly sublayer STC Signalling Transport Converter UDP User Datagram Protocol UNI User-Network Interface4 Data Link Layer 4.1 ATM Transport Option ATM shall be used in the transport network user plane and transp
34、ort network control plane according to ITU-T Rec. I.361 2. 4.1.1 Protection Switching at ATM Layer If redundancy of pathways at ATM Layer between RNC and Node B is supported, it shall be implemented using ATM Protection Switching according to ITU-T Rec. I.630 20. 4.2 IP Transport Option A UTRAN node
35、 supporting IP transport option shall support PPP protocol IETF RFC 1661 23 with HDLC framing (IETF RFC 1662 24). NOTE: This does not preclude the single implementation and use of any other L2/L1 protocols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 32), (IETF RFC 2364 33), PPP/AAL2/ATM, Ethernet, MPLS/ATM
36、 (IETF RFC 3031 34), etc.) fulfilling the UTRAN requirements towards the upper layers. A UTRAN node supporting IP transport option and having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 25) and the PPP extensions ML/MC-PPP (I
37、ETF RFC 1990 26, IETF RFC 2686 27). In this case the negotiation of header compression (ITU-T Rec. I.630 20) over PPP shall be performed via IETF RFC 2509 28. 5 Iur and Iub Data Transport for DCH and E-DCH Data Streams 5.1 Introduction The Frame Protocol for DCH and E-DCH data streams (TS 25.427 1)
38、is the user of the transport layer specified in the present document. ETSI ETSI TS 125 426 V15.0.0 (2018-07)83GPP TS 25.426 version 15.0.0 Release 15There are two options for the transport layer of the DCH and E-DCH data streams in Iur and Iub: 1) ATM based transport (ATM Transport Option) 2) IP bas
39、ed transport (IP Transport Option) The following figure shows the protocol stacks of the two options. Protocol stack for ATM transport option Protocol stack for IP transport option Figure 1: Transport network layer for DCH data streams over Iur and Iub interfaces 5.2 ATM Transport Option Asynchronou
40、s Transfer Mode (ATM) (ITU-T Rec. I.361 2) and ATM Adaptation Layer type 2 (AAL2) (ITU-T Rec. I.363.2 3, ITU-T Rec. I.366.1 4) are used as a transport layer for DCH and E-DCH data streams on Iur and Iub interfaces. Service Specific Segmentation and Reassembly (SSSAR) sublayer for AAL2 is used for th
41、e segmentation and reassembly of AAL2 SDUs. 5.3 IP Transport Option UDP (IETF RFC 768 17) over IP shall be supported as the transport for DCH and E-DCH data streams on Iub and Iur interfaces. The data link layer is as specified in chapter 4.2. An IP UTRAN Node shall support IPv6 (IETF RFC 246029). T
42、he support of IPv4 (IETF RFC 79114) is optional. NOTE: This does not preclude single implementation and use of IPv4. IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network. The transport bearer is identified by the UDP port number and the
43、IP address (source UDP port number, destination UDP port number, source IP address, destination IP address). The source IP address and destination IP address exchanged via Radio Network Layer on the Iur/Iub interface shall use the NSAP structure. See sub clause 6.1.8.2 of TS 25.401 39. IP Differenti
44、ated Services code point marking (IETF RFC 2474 30) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M. Traffic categories are implementation-specific and may be determined from the application parameters. 6 Transport Signalling Applicati
45、on for DCH and E-DCH Data Streams 6.1 Introduction This chapter specifies the ALCAP protocol(s) to be used in Iur and Iub interfaces for DCH data streams. UDP (RFC768)IPv6 (RFC2460)Dat a l i nk l ayerPhysical layerRadio Network LayerAAL2 SSSAR ( I .3 66 .1)AAL2 CPS (I.363.2)ATMPhysical layerRadio Ne
46、twork LayerTransport Net work LayerTr an spor t Network LayerIPv4 optional (RFC791)ETSI ETSI TS 125 426 V15.0.0 (2018-07)93GPP TS 25.426 version 15.0.0 Release 156.2 ALCAP in ATM Transport Option AAL2 signalling protocol Capability Set 2 (ITU-T Rec. Q.2630.2 22) is the signalling protocol to control
47、 AAL2 connections on Iub and Iur interfaces. ITU-T Rec. Q.2630.2 22 adds new optional capabilities to ITU-T Rec. Q.2630.1 5. Binding ID provided by the radio network layer shall be copied in SUGR parameter of ESTABLISH.request primitive of ITU-T Rec. Q.2630.2 22. User Plane Transport bearers for Iur
48、 interface are established, in all normal cases released and optionally modified by the ALCAP in the Serving RNC. The binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iur interface in the Drift RNC. User Pl
49、ane Transport bearers for Iub interface are established, in all normal cases released and optionally modified by the ALCAP in the Controlling RNC. Binding identifier shall already be assigned and tied to a radio application procedure when the Establish Request message is received over the Iub interface in the Node B. In case of a Reset initiated by the CRNC, the ALCAP in the Node B shall release the transport bearers involved in the impacted Node B Commun
