1、 ETSI TS 125 424 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); UTRAN Iur 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 ETSI We
2、b 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, or may
3、 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 to use o
4、r 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 Generation Part
5、nership 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 and ETSI i
6、dentities 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 Rules (V
7、erbal 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 424 V15.0.0 (2018-07)33GPP TS 25.424 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology
8、 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g33.3 Specification Notations 7g34 Data Link Layer . 7g34.1 ATM Transport Option 7g34.2 IP Transport Option 8g35 IurData Transport for Common Transport Channel Data Streams . 8g3
9、5.1 Introduction 8g35.2 ATM Transport Option 8g35.3 IP Option 9g36 IurTransport Signalling Application for Common Transport Channel Data Streams . 9g36.1 Introduction 9g36.2 Transport Signalling in case of ATM option 9g36.3 Transport Signalling in case of IP Transport Option 9g37 Signalling Bearer f
10、or ALCAP on IurInterface 10g37.1 ATM Transport Option 10g37.2 IP Transport Option 10g38 Interworking between ATM and IP Transport Options . 10g3Annex A (informative): Change history . 11g3History 12g3ETSI ETSI TS 125 424 V15.0.0 (2018-07)43GPP TS 25.424 version 15.0.0 Release 15Foreword This Technic
11、al Specification (TS) has been produced 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
12、 by the TSG with an identifying change 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 i
13、ncremented for all changes of substance, 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 424 V15.0.0 (2018-07)53GPP TS 25.424 version 15.0.0 Release 151 Scope The present doc
14、ument shall provide a specification of the UTRAN RNC-RNC (Iur) interface Data Transport and Transport Signalling for Common Transport Channel data streams. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. Re
15、ferences 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 GS
16、M 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 type 2“. 3 ITU-
17、T Recommendation I.366.1 (1998-06): “Segmentation and Re-assembly Service Specific Convergence Sublayer for the AAL type 2“. 4 ITU-T Recommendation Q.2630.1 (1999-12): “AAL Type 2 signalling protocol (Capability Set 1)“. 5 ITU-T Recommendation E.191 (2000-03): “B-ISDN addressing“. 6 3GPP TS 25.426:
18、“UTRAN Iur and Iub interface data transport & transport signalling for DCH data streams“. 7 Void 8 ITU-T Recommendation Q.2630.2 (2000-12): “AAL Type 2 signalling protocol (Capability Set 2)“. 9 ITU-T Recommendation X.213 (1995-11): “Information Technology - Open Systems Interconnection - Network Se
19、rvice Definition“. 10 IETF RFC 1661 (1994-07): “The Point-To-Point Protocol (PPP)“. 11 IETF RFC 1662 (1994-07): “PPP in HDLC-like Framing“. 12 IETF RFC 2507 (1999-02): “IP header compression“. 13 IETF RFC 1990 (1996-08): “The PPP Multilink Protocol (MP)“. 14 IETF RFC 2686 (1999-09): “The Multi-Class
20、 Extension to Multi-Link PPP“. 15 IETF RFC 2509 (1999-02): “IP Header Compression over PPP“. 16 IETF RFC 2460 (1998-12): “Internet Protocol, Version 6 (Ipv6) Specification“. 17 IETF RFC 791 (1981-09): “Internet Protocol“. 18 IETF RFC 2474 (1998-12): “Definition of the Differentiated Services Field (
21、DS Field) in the IPv4 and IPv6 Headers“. 19 IETF RFC 768 (1980-08): “User Datagram Protocol“. 20 IETF RFC 3153 (2001-08): “PPP Multiplexing“. ETSI ETSI TS 125 424 V15.0.0 (2018-07)63GPP TS 25.424 version 15.0.0 Release 1521 IETF RFC 2364 (1998-07): “PPP over AAL5“. 22 IETF RFC 3031 (2001-01):“Multip
22、rotocol Label Switching Architecture“. 23 ITU-T Recommendation E.164 (1997-05): “ The international public telecommunication numbering plan “. 3 Definitions and abbreviations 3.1 Definitions Common Transport Channels are defined as transport channels that are shared by several users i.e. RACH, FACH,
23、 DSCH TDD, USCH TDD and HS-DSCH. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AAL2 ATM Adaptation Layer type 2 AAL5 ATM Adaptation Layer type 5 AESA ATM End System Address ALCAP Access Link Control Application Part ATM Asynchronous Transfer Mode CPS
24、Common Part Sublayer DiffServ Differentiated ServicesDSCH Downlink Shared Channel FACH Forward Access ChannelHDLC High level Data Link Control HS-DSCH High Speed Downlink Shared Channel IP Internet Protocol IPv4 Internet Protocol, version 4 IPv6 Internet Protocol, version 6 IWF Interworking Function
25、 IWU Interworking Unit LC Link CharacteristicsML/MC PPP Multilink-Multiclass PPP MPLS Multiprotocol Label Switching MTP Message Transfer Part NNI Network-Node InterfaceNSAP Network Service Access Point PPP Point-to-Point Protocol PPPMux PPP Multiplexing PT Path Type QoS Quality of Service RACH Rando
26、m Access Channel SAAL Signalling ATM Adaptation Layer SDU Service Data Unit SSCOP Service Specific Connection Oriented Protocol SSCF Service Specific Co-ordination Function SSCS Service Specific Convergence Sublayer SSSAR Service Specific Segmentation and Re-assembly sublayer STC Signalling Transpor
27、t Converter TNL Transport Network Layer UDP User Datagram Protocol UNI User-Network InterfaceUSCH Uplink Shared Channel ETSI ETSI TS 125 424 V15.0.0 (2018-07)73GPP TS 25.424 version 15.0.0 Release 153.3 Specification Notations For the purposes of the present document, the following notations apply:
28、FDD This tagging of a word indicates that the word preceding the tag “FDD“ applies only to FDD. This tagging of a heading indicates that the heading preceding the tag “FDD“ and the section following the heading applies only to FDD. TDD This tagging of a word indicates that the word preceding the tag
29、 “TDD“ applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “TDD“ and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. 3.84Mcps TDD This tagging
30、of a word indicates that the word preceding the tag “3.84Mcps TDD“ applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “3.84Mcps TDD“ and the section following the heading applies only to 3.84Mcps TDD. 1.28Mcps TDD This tagging of a word indicates tha
31、t the word preceding the tag “1.28Mcps TDD“ applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “1.28Mcps TDD“ and the section following the heading applies only to 1.28Mcps TDD. 7.68Mcps TDD This tagging of a word indicates that the word preceding th
32、e tag “7.68Mcps TDD“ applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag “7.68Mcps TDD“ and the section following the heading applies only to 7.68Mcps TDD. FDD - This tagging indicates that the enclosed text following the “FDD - “ applies only to FDD.
33、 Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. TDD - This tagging indicates that the enclosed text following the “TDD - “ applies only to TDD including 3.84Mcps TDD, 7.68Mcps
34、 TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. 3.84Mcps TDD - This tagging indicates that the enclosed text following the “3.84Mcps TDD - “ applies only
35、 to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. 1.28Mcps TDD - This tagging indicates that the enclosed text following the “1.28Mcps
36、 TDD - “ applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. 7.68Mcps TDD - This tagging indicates that the enclosed text fo
37、llowing the “7.68Mcps TDD - “ applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. 4 Data Link Layer 4.1 ATM Transport Option
38、 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 Iur interface is the cell header format and encoding at NNI (see Figure 3/I.361 1). ETSI ETSI TS 125 424 V15.0.
39、0 (2018-07)83GPP TS 25.424 version 15.0.0 Release 154.2 IP Transport Option A UTRAN Node supporting IP transport option shall support PPP protocol with HDLC framing (IETF RFC 1661 10, IETF RFC 1662 11). Note: This does not preclude the single implementation and use of any other data link layer proto
40、cols (e.g. PPPMux/AAL5/ATM (IETF RFC 3153 20, IETF RFC 2364 21), PPP/AAL2/ATM, Ethernet, MPLS/ATM (IETF RFC 3031 22), etc.) fulfilling the UTRAN requirements toward the upper layers. An RNC using IP transport option having interfaces connected via slow bandwidth PPP links like E1/T1/J1 shall also su
41、pport IP Header Compression (IETF RFC 2507 12) and the PPP extensions ML/MC-PPP (IETF RFC 1990 13), (IETF RFC 2686 14). In this case, negotiation of header compression (IETF RFC 2507 12) over PPP shall be performed via IETF RFC 2509 15. 5 IurData Transport for Common Transport Channel Data Streams 5
42、.1 Introduction This clause specifies the transport layers that support Common Channels (FACH, RACH, DSCH TDD, USCH TDD, HS-DSCH) Iur data streams. There are two options for the transport layer of the Common Channels data streams in Iur and Iub: 1) ATM based Transport (ATM transport option) 2) IP ba
43、sed 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 ATM (ITU-T
44、 Rec. I.361 1), AAL type 2 (ITU-T Recommendations I.363.2 2 and ITU-T Rec. I.366.1 3) is used as the standard transport layer for RACH, FACH, USCH TDD, DSCH TDD and HS-DSCH Iur data streams. These AAL2 connections are established via the transport signalling protocol described in clause 5. Figure 1
45、shows the protocol stack for the transport of RACH, FACH, USCH TDD, DSCH TDD and HS-DSCH Iur data streams using the ATM Transport Option. Service Specific Segmentation and Re-assembly (SSSAR) is used for the segmentation and re-assembly of AAL2 SDUs (i.e. SSSAR is only considered from ITU-T Recommen
46、dation I.366.1 3). 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 Network LayerTransport Net work LayerTr an spor t Network LayerIPv4 optional (RFC791)ETSI ETSI TS 125 424 V15.0.0 (2018-07)93GPP TS 25.424
47、 version 15.0.0 Release 155.3 IP Option UDP (IETF RFC 768 19) over IP shall be used as the transport for RACH, FACH, USCH TDD, DSCH TDD and HS-DSCH data streams on Iur. The data link layer is as specified in subclause 4.2. An IP UTRAN Node shall support IPv6 (IETF RFC 2460 16). The support of IPv4 (
48、IETF RFC 791 17) is optional. Note: This does not preclude single implementation 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 IP address (source UDP port
49、 number, destination UDP port number, source IP address, destination IP address). IP Differentiated Services code point marking (IETF RFC 2474 18) 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 IurTransport Signalling Application for Common Transport
