1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelApplication of SIP-I core n(3GPP TS 29.2TECHNICAL SPECIFICATION129 231 V13.0.0 (2016communications system (Phaelecommunications System (I Protocols to Circuit Switchee network architecture; Stage 3 .231 version 13.0.0 Release 13GLOBAL SYSTEMOBILE
2、COMMUN16-01) hase 2+); (UMTS); hed (CS) 13) TEM FOR ICATIONSRETSI ETSI TS 129 231 V13.0.0 (2016-01)13GPP TS 29.231 version 13.0.0 Release 13Reference RTS/TSGC-0429231vd00 Keywords GSM,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47
3、 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:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in p
4、rint. 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 difference in contents between such versions and/or in print, the only prevailing document is the print of the
5、 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 change of status. Information on the current status of this and other ETSI documents is available at http:/p
6、ortal.etsi.org/tb/status/status.asp If you find errors in the present 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 m
7、echanical, 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 authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunicat
8、ions Standards Institute 2016. 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 Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GS
9、M logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 231 V13.0.0 (2016-01)23GPP TS 29.231 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 t
10、o 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 potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. L
11、atest 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 guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETS
12、I 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 Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMT
13、S 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 can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“,
14、 “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 forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in
15、direct citation. ETSI ETSI TS 129 231 V13.0.0 (2016-01)33GPP TS 29.231 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33
16、.3 Abbreviations . 8g34 Protocols . 8g34.1 Introduction 8g34.2 Call control protocol (Nc interface) 9g34.3 Resource control protocol (G)MSC and MGW (Mc Interface) 9g34.4 Bearer Framing Protocol between MGWs (Nb interface) 10g34.5 Signalling Transport . 10g34.5.1 Call Control protocols . 10g34.5.2 Re
17、source control protocol (G)MSC and MGW (Mc Interface) 10g34.5.3 IP Transport between MGWs (Nb interface) 10g34.6 Payload Types 10g35 Amendments and Endorsements to Referenced Specifications . 11g35.1 ITU-T Q.1912.5 (Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call C
18、ontrol protocol or ISDN User Part) 11g35.2 IETF RFC 2046 (Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types) 11g35.3 IETF RFC 4566 (SDP: Session Description Protocol) . 11g35.4 IETF RFC 3966 (The tel URI for Telephone Numbers) 12g35.5 IETF RFC 2976 (The SIP INFO method) 12g35.6 IETF
19、 RFC 3204 (MIME media types for ISUP and QSIG Objects) 12g35.7 IETF RFC 3261(SIP: Session Initiation Protocol) . 12g35.8 IETF RFC 3262 (Reliability of Provisional Responses in the Session Initiation Protocol) . 13g35.9 IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol) 13g35
20、.9.1 Multicast Streams . 13g35.9.2 3GPP Node Generating the Offer . 13g35.9.3 3GPP Node Generating the Answer . 13g35.9.4 3GPP Node as Offerer Processing of the Answer . 13g35.9.5 Modifying the session . 14g35.9.6 Unspecified Connection Address 14g35.10 IETF RFC 3311 (The Session Initiation Protocol
21、 (SIP) UPDATE Method) 14g35.11 IETF RFC 3312 (Integration of Resource Management and Session Initiation Protocol) . 14g35.12 IETF RFC 3323 (A Privacy Mechanism for the Session Initiation Protocol) 14g35.13 IETF RFC 3325 (Private Extensions to the Session Initiation Protocol (SIP) for Network Asserte
22、d Identity within Trusted Networks) . 15g35.14 IETF RFC 3326 (The Reason Header Field for the Session Initiation Protocol) . 15g35.15 IETF RFC 4028 (Session Timers in the Session Initiation Protocol) . 15g35.16 IETF RFC 4960 (Stream Control Transmission Protocol) . 15g35.17 Void 15g35.18 IETF RFC 41
23、68 (The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol) . 15g35.19 IETF RFC 791 (Internet Protocol, Version 4) 16g35.20 IETF RFC 2460 (Internet Protocol, Version 6) 16g35.21 IETF RFC 4715 (The Integrated Services Digital Network (ISDN) Subaddress Encod
24、ing Type for tel URI) 16g3ETSI ETSI TS 129 231 V13.0.0 (2016-01)43GPP TS 29.231 version 13.0.0 Release 135.22 IETF RFC 4320 (Actions Addressing Identified Issues with the Session Initiation Protocols (SIP) Non-INVITE Transaction) . 16g35.23 IETF RFC 5079 (Rejecting Anonymous Requests in the Session
25、Initiation Protocol (SIP) . 16g36 3GPP Extensions 17g36.1 Codec Negotiation 17g36.1.1 Encoding of 3GPP_OoBTC_Indicator 17g36.1.2 Encoding of SDP answer including 3GPP OoBTC Indicator . 17g36.2 MGW Identifier 17g36.2.1 Semantic and Usage of the MGW_Identifier 17g36.2.2 Encoding of MGW_Identifier . 17
26、g36.2.3 Procedures related to MGW_Identifier . 18g36.3 Additional MGW Ids 18g36.3.1 Semantic and Usage of the Additional_MGW_Ids . 18g36.3.2 Encoding of Additional_MGW_Ids 18g36.3.3 Procedures related to Additional_MGW_Ids 18g3Annex A (informative): IANA Registration of OoBTC Indicator 19g3A.1 Intro
27、duction 19g3A.2 Contact name, email address, and telephone number . 19g3A.3 Attribute Name (as it will appear in SDP) 19g3A.4 Long-form Attribute Name in English . 19g3A.5 Type of Attribute 19g3A.6 Is Attribute Value subject to the Charset Attribute? . 19g3A.7 Purpose of the attribute . 19g3A.8 Appr
28、opriate Attribute Values for this Attribute 19g3Annex B (informative): IANA Registration of MGW Identifier 20g3B.1 Introduction 20g3B.2 Contact name, email address, and telephone number . 20g3B.3 Attribute Name (as it will appear in SDP) 20g3B.4 Long-form Attribute Name in English . 20g3B.5 Type of
29、Attribute 20g3B.6 Is Attribute Value subject to the Charset Attribute? . 20g3B.7 Purpose of the attribute . 20g3B.8 Appropriate Attribute Values for this Attribute 20g3Annex C (informative): IANA Registration of Additional MGW Ids . 21g3C.1 Introduction 21g3C.2 Contact name, email address, and telep
30、hone number . 21g3C.3 Attribute Name (as it will appear in SDP) 21g3C.4 Long-form Attribute Name in English . 21g3C.5 Type of Attribute 21g3C.6 Is Attribute Value subject to the Charset Attribute? . 21g3C.7 Purpose of the attribute . 21g3C.8 Appropriate Attribute Values for this Attribute 21g3Annex
31、D (informative): Change history . 22g3History 23g3ETSI ETSI TS 129 231 V13.0.0 (2016-01)53GPP TS 29.231 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing wor
32、k 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 first digit: 1 presented to
33、 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 incremented when editorial only chang
34、es have been incorporated in the document. ETSI ETSI TS 129 231 V13.0.0 (2016-01)63GPP TS 29.231 version 13.0.0 Release 131 Scope The present document describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see 3GPP TS 23.2
35、31 1. The SIP-I protocol operates between (G)MSC servers. The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requ
36、irements imposed by 3GPP TS 23.231 1 and TS 23.153 2. Interworking of SIP-I on Nc to external networks is described by TS 29.235 3. The present document is valid for a 3rdgeneration PLMN (UMTS) complying with Release 8 and later. 2 References The following documents contain provisions which, through
37、 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 vers
38、ion 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 23.231: “SIP-I based Circuit Switched Core Network ; Stage 2“. 2 3GPP TS 23.
39、153: “Out of Band Transcoder Control; Stage 2“. 3 3GPP TS 29.235: “Interworking between the 3GPP CS domain with SIP-I as signalling protocol and other networks“. 4 ITU-T Recommendation Q.1912.5: “Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or I
40、SDN User Part“. 5 IETF RFC 2046: “Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types“. 6 IETF RFC 3966: “The tel URI for Telephone Numbers“. 7 IETF RFC 2976: “The SIP INFO method“. 8 IETF RFC 3204: “MIME media types for ISUP and QSIG Objects“. 9 IETF RFC 3261: “SIP: Session Initiatio
41、n Protocol“. 10 IETF RFC 3262: “Reliability of Provisional Responses in the Session Initiation Protocol (SIP)“. 11 IETF RFC 3264: “An Offer/Answer Model with the Session Description Protocol (SDP)“. 12 IETF RFC 3311: “The Session Initiation Protocol (SIP) UPDATE Method“. 13 IETF RFC 3312: “Integrati
42、on of Resource Management and Session Initiation Protocol (SIP)“. 14 IETF RFC 3323: “A Privacy Mechanism for the Session Initiation Protocol (SIP)“. 15 IETF RFC 3325: “Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks“. 16 IETF RFC 3326
43、: “The Reason Header Field for the Session Initiation Protocol (SIP)“. 17 IETF RFC 4566: “SDP: Session Description Protocol“. ETSI ETSI TS 129 231 V13.0.0 (2016-01)73GPP TS 29.231 version 13.0.0 Release 1318 3GPP TS 29.232: “Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3“. 1
44、9 3GPP TS 29.415: “Core network Nb data transport and transport signalling“. 20 3GPP TS 29.414: “Core Network Nb data transport and transport signalling“. 21 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 22 IETF RFC 3389: “Real-time Transport Protocol (RTP) Payload for Comfort Noise“. 23 IET
45、F RFC 4733: “RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals“. 24 IETF RFC 4028: “Session Timers in the Session Initiation Protocol (SIP)“. 25 IETF RFC 4960: “Stream Control Transmission Protocol“. 26 Void 27 IETF RFC 4168: “The Stream Control Transmission Protocol (SCTP) as a Tra
46、nsport for the Session Initiation Protocol (SIP)“. 28 IETF RFC 5407: “Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)“. 29 IETF RFC 791: “Internet Protocol (IP)“. 30 IETF RFC 2460: “Internet Protocol, Version 6 (IPv6)“. 31 IETF RFC 3550: “RTP: A Transport Protocol for
47、Real-Time Applications“. 31 3GPP TS 26.102: “Mandatory speech codec; Adaptive Multi-Rate (AMR) speech codec;Interface to Iu, Uu and Nb“. 32 3GPP TS 26.103: “Speech codec list for GSM and UMTS“. 33 3GPP TS 23.003: “Numbering, addressing and identification“. 34 IETF RFC 4715: “ The Integrated Services
48、 Digital Network (ISDN) Subaddress Encoding Type for tel URI “. 35 IETF RFC 4320: “Actions Addressing Identified Issues with the Session Initiation Protocols (SIP) Non-INVITE Transaction“. 36 IETF RFC 5079: “Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)“. 3 Definitions, symbo
49、ls and abbreviations 3.1 Definitions 3.2 Symbols For the purposes of the present document, the following symbols apply: Nc Interface between the(G)MSC servers. Mc Interface between the server and the media gateway. Nb Interface between media gateways (MGW). ETSI ETSI TS 129 231 V13.0.0 (2016-01)83GPP TS 29.231 version 13.0.0 Release 133.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 21 and the following apply. An abbreviation define
