1、 ETSI TS 1Digital cellular telecoBase Station System - MUser plan(3GPP TS 48.1TECHNICAL SPECIFICATION148 103 V13.0.0 (2016communications system (PhaMedia GateWay (BSS-MGW)lane transport mechanism .103 version 13.0.0 Release 13GLOBAL SYSTEMOBILE COMMUN16-01) hase 2+); W) interface; 13) TEM FOR ICATIO
2、NSRETSI ETSI TS 148 103 V13.0.0 (2016-01)13GPP TS 48.103 version 13.0.0 Release 13Reference RTS/TSGG-0248103vd00 Keywords GSM ETSI 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 l
3、ucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/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 th
4、e present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference 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 netw
5、ork drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the p
6、resent document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.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 autho
7、rized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLU
8、GTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are 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 Associat
9、ion. ETSI ETSI TS 148 103 V13.0.0 (2016-01)23GPP TS 48.103 version 13.0.0 Release 13Intellectual Property Rights IPRs essential 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
10、members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); 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 Web server (https:/ipr.
11、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 become, essential to
12、 the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation 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
13、being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and 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“
14、, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting 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 148 103 V13.0.0 (2016-01)33GPP TS
15、 48.103 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Transport over TDM 7g34.1 General . 7g34.2 Transport d
16、uring local switching 7g35 Transport over IP 7g35.1 General . 7g35.2 IP 8g35.3 UDP 8g35.4 Transport without RTP multiplexing 8g35.4.1 Introduction. 8g35.4.2 RTP . 8g35.4.2.1 RTP Header . 8g35.4.2.1.1 Version 8g35.4.2.1.2 Padding 8g35.4.2.1.3 Extension . 8g35.4.2.1.4 Contributing Source (CSRC) count
17、. 8g35.4.2.1.5 Marker Bit . 9g35.4.2.1.6 Payload Type . 9g35.4.2.1.7 Sequence Number 9g35.4.2.1.8 Timestamp . 9g35.4.2.1.9 Synchronisation Source (SSRC) 9g35.4.2.1.10 CSRC list. 9g35.4.2.2 RTP Payload . 9g35.4.2.3 RTP Packetization Time . 10g35.4.3 RTCP 10g35.5 Transport with RTP multiplexing . 10g3
18、5.5.1 Introduction. 10g35.5.2 RTP . 11g35.5.2.1 Transport format for multiplexing without RTP header compression. 11g35.5.2.2 Transport format for multiplexing with RTP header compression 12g35.5.3 RTCP 13g35.5.3.1 General 13g35.5.3.2 Multiplexing negotiation via RTCP 13g35.5.3.3 RTCP Multiplexing p
19、acket . 14g35.6 Transport of CSData . 15g35.6.1 Introduction. 15g35.6.2 Transport formats for CSData . 16g35.6.2.1 Transport format for CSData without redundancy 16g35.6.2.2 Transport format for CSData with redundancy . 17g35.6.2.3 Start and Stop of RTP streams with redundancy . 18g35.7 Transport du
20、ring local switching 19g3Annex A (informative): Change History 20g3History 21 ETSI ETSI TS 148 103 V13.0.0 (2016-01)43GPP TS 48.103 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document a
21、re 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 change of release date and an increase in version number as follows: Version x.y.z where: x the
22、 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 substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is increment
23、ed when editorial only changes have been incorporated in the document. ETSI ETSI TS 148 103 V13.0.0 (2016-01)53GPP TS 48.103 version 13.0.0 Release 131 Scope The present document specifies the User Plane data transport protocols used between BSSs and the Core Network (MGWs) across the A interface. T
24、he main purpose of the present document is the AoIP description, however for the sake of completeness the AoTDM case is described as well. MGW Signalling and Data Transfer Interface Signalling Interface UTRAN GERAN Iu mode MSC server GMSC server Mc MGW Nb Nc Iu Iu Mc GERAN A/Gb mode A A Figure 1.1:
25、CS core network logical architecture Note that the present document does not preclude any Core Network Session Control Protocol implementation (BICC or SIP-I). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document
26、. 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
27、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 TR 21.905: “Vocabulary for 3GPP Specifications“. 2 IETF RFC 791: “Internet Protocol (IP)“. 3 IETF RFC 2460: “Internet Protocol, Version 6 (IPv6)“. 4
28、IETF RFC 768: “User Datagram Protocol. (UDP)“. 5 IETF RFC 3550: “RTP: A Transport Protocol for Real Time Applications“. 6 3GPP TS 29.414: “Core network Nb Interface data transport and transport signalling“. 7 IETF RFC 3551: “RTP Profile for Audio and Video Conference with Minimal Control“. 8 3GPP TR
29、 29.814: “Feasibility Study on Bandwidth Savings at Nb Interface with IP transport“. 9 IETF RFC 4040: “RTP Payload Format for a 64 kbits/s Transparent Call“ 10 IETF RFC 4867: “RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio
30、 Codecs“ ETSI ETSI TS 148 103 V13.0.0 (2016-01)63GPP TS 48.103 version 13.0.0 Release 1311 IETF RFC 2198: “RTP Payload for redundant Audio Data“ 12 3GPP TR 43.903 A-Interface over IP Study (AINTIP) 13 3GPP TS 48.001 “Base Station System Mobile-services Switching Centre (BSS - MSC) interface; General
31、 aspects“ 14 ITU-T Recommendation G.705: “Characteristics of plesiochronous digital hierarchy (PDH) equipment functional blocks“. 15 ANSI T1.102-1993: “Digital Hierarchy - Electrical Interface“. 16 ITU-T Recommendation G.711: “Pulse Code Modulation (PCM) of voice frequencies“. 17 3GPP TS 48.020: “Ra
32、te adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface“. 18 IETF RFC 5993 (2010) “RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)“. 19 3GPP TS 48.008: “Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer
33、3 specification“. 20 3GPP TS 26.102: “Adaptive Multi-Rate (AMR) speech codec; Interface to Iu, Uu and Nb“. 21 3GPP TS 23.284: “Local Call Local Switch; Stage 2“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 2
34、1.905 1 and the following apply. Intra-BSS call: A mobile to mobile voice call involving two mobile stations connected to the same BSS. Local call: An Intra-BSS call that can be locally switched by the BSS. For details on the Local Switch Service see 3GPP TS 23.284 21. Access MGW: The MGW interfacin
35、g to the Radio Access Network 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and 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 1. AoIP A (int
36、erface) over IP AoTDM A (interface) over TDM APP APPlication BICC Bearer Independent Call Control BSS Base Station Subsystem CS Circuit-Switched CSData CS Data and fax IETF Internet Engineering Task Force IP Internet Protocol IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 ITU-T In
37、ternational Telecommunications Union-Telecommunication sector MGW Media GateWay PCM Pulse-Coded Modulation RFC Request For Comment ETSI ETSI TS 148 103 V13.0.0 (2016-01)73GPP TS 48.103 version 13.0.0 Release 13RTP Real-Time Transport Protocol RTCP Real-Time Transport Control Protocol SIP-I Session I
38、nitiation Protocol with encapsulated ISUP SSRC Synchronisation Source SVC Switched Virtual Circuit TDM Time-Division MultiplexingUDP User Datagram Protocol UP User Plane 4 Transport over TDM 4.1 General The present chapter describes the transport on the A Interface UP over E1/T1 interface; for more
39、information see 3GPP TS 48.001 13. Figure 4.1 shows the protocol stack for the transport network user plane on the A interface. Payload (PCM encoded speech or CSData) E1 or T1 Figure 4.1: TDM Protocol stack for the A interface user plane Layer 1 shall utilise digital transmission: - at a rate of 2 0
40、48 kbit/s with a frame structure of 32 x 64kbit/s time slots, as specified in ITU-T Recommendation G.705 14 clause 3 for E1 interface; or - at a rate of 1 544 kbit/s with a frame structure of 24 x 64 kbit/s time slots, as specified in T1.102 specification for T1 interface 15. The payload is either P
41、CM encoded speech (see ITU-T Recommendation G.711 16) or CSData (see 3GPP TS 48.020 17). 4.2 Transport during local switching When a local switch path is established in the BSS for a local call, the user plane between the BSS and the Access MGWs for both the call legs in uplink and downlink shall no
42、t be released. 5 Transport over IP 5.1 General The present chapter describes the transport of the A-Interface User Plane Payload by RTP/UDP/IP. Figure 5.1 shows the protocol stack. Payload (PCM-coded speech, or compressed speech or CSData) RTP UDP IPv4 or IPv6 Figure 5.1: IP Protocol stack for the A
43、-Interface user plane The specific carrying way at physical/link layer of the IP protocol is not limited by the present document; if Ethernet is adopted, link layer will be MAC protocol while if IPoE1 or POS is adopted, link layer will be PPP protocol. Nevertheless at least Ethernet should be suppor
44、ted. ETSI ETSI TS 148 103 V13.0.0 (2016-01)83GPP TS 48.103 version 13.0.0 Release 135.2 IP IPv4 (RFC 791 2) shall be supported IPv6 (RFC 2460 3) may be supported as an option. One BSS/MGW pair may be connected via several IP interfaces. 5.3 UDP The UDP Protocol (see RFC 768 4) shall be applied. Two
45、consecutive port numbers shall be used at each BSS/MGW for the RTP connection and for the optional RTCP connection that corresponds to a single A interface UP connection. Two such consecutive port numbers are termed “port number block“ in what follows. The first port number shall be even and shall b
46、e assigned to the RTP protocol. For a given BSS/MGW, the same port shall be used to send and to receive RTP PDUs. The next port number shall be assigned to the RTCP protocol. This port shall be reserved even if the optional RTCP protocol is not used. If multiplexing is applied with or without header
47、 compression, the source UDP port number shall indicate the local termination used to combine the multiplexed packet and the destination UDP port number shall indicate the remote port number where PDUs are demultiplexed. The negotiation of whether multiplexing is applied and of the destination UDP p
48、ort is described in sub-clause 5.5.3.2. If multiplexing was negotiated for an A interface UP user plane connection, the BSS/MGW may apply multiplexing by sending all packets of the user plane connection (multiplexed with other user plane connections packets) towards the negotiated destination UDP po
49、rt. 5.4 Transport without RTP multiplexing 5.4.1 Introduction User Plane transport without RTP multiplexing is default and shall be supported. It shall be applied after call setup, until a User Plane transport with RTP-multiplexing is negotiated via RTCP, see clause 5.5. RTCP, see RFC 3550 5 may be applied in AoIP, it is optional. A BSS or MSC may ignore incoming RTCP packets on AoIP. 5.4.2 RTP The RTP protocol (see RFC 3550 5) shall be applied. 5.4.2.1 RTP Header The RTP Header Fields shall be us
