1、 ETSI TS 125 444 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); Iuh data transport (3GPP TS 25.444 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 125 444 V14.0.0 (2017-04)13GPP TS 25.444 version 14.0.0 Release 14Reference RTS/TSGR-0325444ve00 Keywords UMTS ETSI
2、 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/
3、www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived dif
4、ference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or c
5、hange of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSuppor
6、tStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorizat
7、ion of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are
8、Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 125 444 V14.0.0 (2017-04)23GPP TS 25.444 version 14.0.0 Release 14Intellectual Property Rights IPRs es
9、sential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potent
10、ially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the 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
11、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 become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership P
12、roject (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 identities
13、 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 (Verbal for
14、ms 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 444 V14.0.0 (2017-04)33GPP TS 25.444 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Forew
15、ord . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Data Link Layer . 6g35 Circuit switched domain . 6g35.1 Transport Network User Plane without bandwidth efficiency mechanisms . 6g35.3 Transport Network User Plane with bandwidth effic
16、iency mechanisms 6g35.3.1 General 6g35.3.2 Transport format . 6g35.3.2.1 UDP. 6g35.3.2.2 RTP . 6g35.3.2.2.1 Transport Format for multiplexing RTP packets . 6g36 Packet switched domain . 8g36.1 Transport network user plane . 8g3Annex A (informative): Change history . 9g3History 10g3ETSI ETSI TS 125 4
17、44 V14.0.0 (2017-04)43GPP TS 25.444 version 14.0.0 Release 14Foreword This Technical 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.
18、Should the TSG modify the contents of the present document, it will be re-released 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 gre
19、ater indicates TSG approved document under change control. y the second digit is incremented 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 444
20、 V14.0.0 (2017-04)53GPP TS 25.444 version 14.0.0 Release 141 Scope The present document specifies the standards for user data transport protocols between the HNB and HNB-GW/CN. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the
21、 present document. uni25CF References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. uni25CF For a specific reference, subsequent revisions do not apply. uni25CF For a non-specific reference, the latest version applies. In the case of a
22、 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 Void 2 Void 3 Void 4 3GPP TS 25.414: “ UTRAN Iu interface data transport and transport signalling“. 5 Void 6 Void
23、 7 Void 8 IETF RFC 768 (1980-08): “User Datagram Protocol“. 9 IETF RFC 1889 (1996-01): “RTP: A Transport Protocol for Real-Time Applications“. 10 Void 11 Void 12 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present docu
24、ment, the terms and definitions given in TR 21.905 12 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 12. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 12 an
25、d the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 12. CN Core Network ETSI ETSI TS 125 444 V14.0.0 (2017-04)63GPP TS 25.444 version 14.0.0 Release 14CS Circuit Switched HNB Home Node B HNB-GW Hom
26、e Node B Gateway IP Internet Protocol PS Packet SwitchedRFC Request For Comment RTP Real-Time Transport Protocol UDP User Datagram Protocol 4 Data Link Layer Any data link protocol that fulfils the requirements toward the upper layer may be used. 5 Circuit switched domain 5.1 Transport Network User
27、Plane without bandwidth efficiency mechanisms Defined in Reference TS 25.414 4, subclause 5.1.3. NOTE: The Transport Network Layer as described in ref TS 25.414 4 subclause 5.1.3, may be directly between HNB and the CN. 5.3 Transport Network User Plane with bandwidth efficiency mechanisms 5.3.1 Gene
28、ral Bandwidth efficient transport of Uplink CS data payload PDUs may be supported over bearer transport mechanisms for the Iuh interface, using a bearer transport multiplexing scheme that allows transporting several RTP PDUs of different user plane connections within one packet. 5.3.2 Transport form
29、at UDP/IP shall be applied on Iuh between HNB and HNB GW as described in TS 25.414 4 for Iu between RNC and CN, subclause 5.1.3, except as stated below. 5.3.2.1 UDP The path protocol used shall be UDP (IETF RFC 768 8). If multiplexing is applied the source UDP port number shall indicate the local te
30、rmination used to combine the multiplexed packet and the destination UDP port number shall indicate the remote port number where PDUs are demultiplexed. 5.3.2.2 RTP RTP (IETF RFC 18899) shall be applied as described in TS 25.414 4, subclause 5.1.3.3 and requirements below. 5.3.2.2.1 Transport Format
31、 for multiplexing RTP packets Use of multiplexing shall be negotiated between the HNB and HNB-GW. Before each multiplexed RTP/codec payload PDU inserted into the UDP/IP packet a Multiplex Header, which identifies the multiplexed packet, shall be inserted. ETSI ETSI TS 125 444 V14.0.0 (2017-04)73GPP
32、TS 25.444 version 14.0.0 Release 14Bits 7 6 5 4 3 2 1 0 Number of OctetsSource IP, Dest IP, 20/40 IP Source Port, Dest Port=, Length, 8 UDP T=0 Mux ID = (Destination UDP Port of multiplexed PDU) / 2 2 Length Indicator (LI) = n 1 R Source ID = (Source UDP Port of multiplexed PDU) / 2 2 Multiplex Head
33、er RTP header Full RTP packet n RTP Payload Multiplex Header 5 Multiplex Header RTP header Full RTP packet m RTP Payload Figure 1: UDP/IP Packet with multiplexed RTP payload PDUs The Multiplex Header includes : - T bit. The field has two possible values. Value 0 shall be used for an uncompressed RTP
34、 header, as decribed in the present sub-clause. Value 1 is FFS. - Mux ID, 15 bits. For identification of different user plane connections. The value shall be the UDP destination port of the corresponding non-multiplexed RTP PDU packet divided by two (only even numbered ports are used for RTP session
35、s). - Length Indicator (LI), 8 bits, unsigned integer. Gives the length of the multiplexed RTP PDU packet (RTP header + RTP) in bytes (the last byte of the RTP PDU is padded to the next byte boundary if necessary). Maximum length is 255 bytes. This LI allows to calculate where the next Multiplex Hea
36、der for the next multiplexed RTP PDU packet starts. ETSI ETSI TS 125 444 V14.0.0 (2017-04)83GPP TS 25.444 version 14.0.0 Release 14- R bit. Reserved for future use. Shall be set to 0 by the sending entity and be ignored by the receiving entity. - Source ID, 15 bits. For identification of the differe
37、nt connections. The value shall be the source UDP port of the corresponding non-multiplexed RTP/codec PDU packet divided by two (only even numbered ports are used for RTP sessions). The multiplexed RTP PDU shall be inserted in the IP/UDP packet directly after the corresponding Multiplex Header. The
38、multiplexed RTP packet PDU shall follow the rules defined in IETF RFC 1889 9 and consists of the full RTP header and the RTP payload. If the multiplexed RTP packet PDU does not end at a byte boundary, then the remaining bits of its last byte shall be padded with zeros. The multiplexing method does n
39、ot limit the number of packets being multiplexed and it is thus the data link layer protocol that defines the maximum frame size. In order to avoid additional delay in the network the packets should not be delayed more than 1 ms to 2 ms, which also effectively limits the number of multiplexed packet
40、s and makes the multiplexing-jitter low. MUX ( 5 )UDP ( 8 ) IP ( 20 / 40 bytes ) RTP ( 12 ) Common headerIuUP frame ( 9 ) MUX ( 5 ) RTP ( 12 ) IuUP frame ( 9 ) 1. MUX packet 2. MUX packetIuUP frame ( 9 ) UDP ( 8 ) IP ( 20 / 40 bytes ) RTP ( 12 ) IuUP frame ( 9 ) UDP ( 8 ) IP ( 20 / 40 bytes ) RTP (
41、12 ) Dest. & SourceUDP Port: xxxxmax 255 bytesNegotiated UDP MUX port. Dest. & SourceUDP Port: yyyy Dest. & SourceUDP Port: xxxxDest. & SourceUDP Port: yyyy Figure 2: Example of multiplexed packet with two RTP frames 6 Packet switched domain 6.1 Transport network user plane Defined in Ref TS 25.414
42、4 subclause 6.1.3. NOTE: The Transport Network Layer as described in ref TS 25.414 4 subclause 6.1.3, may be directly between HNB and the CN. ETSI ETSI TS 125 444 V14.0.0 (2017-04)93GPP TS 25.444 version 14.0.0 Release 14Annex A (informative): Change history TSG # TSG Doc. CR Rev Subject/Comment New
43、 Initial Skeleton 0.1.0 Addition of TP for signalling for bandwidth efficiency 0.2.0 Presented for approval at RAN#46 2.0.0 46 RP-091104 Approved at RAN#46 9.0.0 Editoral clean up 9.0.1 Version number in the change history corrected 9.0.2 SP-49 SP-100629 Clarification on the use of References (TS 21
44、.801 CR#0030) 9.0.3 03/2011 Created Rel-10 version based on v9.0.3 10.0.0 52 RP-110684 0002 Corrrection of references 10.1.0 09/2012 Update to Rel-11 version (MCC) 11.0.0 09/2014 Update to Rel-12 version (MCC) 12.0.0 12/2015 Update to Rel-13 version (MCC) 13.0.0 Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2017-03 SA#75 Promotion to Release 14 without technical change 14.0.0 ETSI ETSI TS 125 444 V14.0.0 (2017-04)103GPP TS 25.444 version 14.0.0 Release 14History Document history V14.0.0 April 2017 Publication
