1、 ETSI TS 1Universal Mobile TelEvolved3GPP Sv interface (3GPP TS 29.2TECHNICAL SPECIFICATION129 280 V13.0.0 (2016elecommunications System (LTE; ed Packet System (EPS); e (MME to MSC, and SGSN tofor SRVCC .280 version 13.0.0 Release 1316-01) (UMTS); to MSC) 13) ETSI ETSI TS 129 280 V13.0.0 (2016-01)13
2、GPP TS 29.280 version 13.0.0 Release 13Reference RTS/TSGC-0429280vd00 Keywords LTE,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 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture d
3、e 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 the present document shall not be modifi
4、ed 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 network drive within ETSI Secretariat. Use
5、rs 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 present document, please send your comm
6、ent 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 authorized by written permission of ETSI. T
7、he 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, PLUGTESTSTM, UMTSTMand the ETSI logo are
8、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 Association. ETSI ETSI TS 129 280 V13.0.0 (201
9、6-01)23GPP TS 29.280 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 members and non-members, and can be fo
10、und 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.etsi.org/). Pursuant to the ETSI IPR P
11、olicy, 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 the present document. Foreword This T
12、echnical 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 being references to the corresponding
13、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“, “will not“, “can“ and “cannot“ are t
14、o 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 129 280 V13.0.0 (2016-01)33GPP TS 29.280 version 13.0.0 Release 13Conte
15、nts Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Symbols 6g33.3 Abbreviations . 6g34 General Description 6g35 Sv Messages and Information Elements 6g35.1 Introduc
16、tion 6g35.2 Sv Messages . 7g35.2.1 General 7g35.2.2 SRVCC PS to CS Request 8g35.2.3 SRVCC PS to CS Response 10g35.2.4 SRVCC PS to CS Complete Notification . 10g35.2.5 SRVCC PS to CS Complete Acknowledge 11g35.2.6 SRVCC PS to CS Cancel Notification 11g35.2.7 SRVCC PS to CS Cancel Acknowledge . 12g35.
17、2.8 SRVCC CS to PS Request 12g35.2.9 SRVCC CS to PS Response 13g35.2.10 SRVCC CS to PS Complete Notification . 14g35.2.11 SRVCC CS to PS Complete Acknowledge 14g35.2.12 SRVCC CS to PS Cancel Notification 15g35.2.13 SRVCC CS to PS Cancel Acknowledge . 15g35.3 Path Management Messages. 15g35.3.1 Intro
18、duction. 15g35.3.2 Echo Request message 15g35.3.3 Echo Response message . 16g35.3.4 Version Not Supported Indication message 16g35.4 Reliable Delivery of Signalling Messages 16g35.5 Error Handling 16g35.6 Restoration and Recovery 16g36 Sv Information Elements 16g36.1 General . 16g36.2 STN-SR 17g36.3
19、 Source to Target Transparent Container . 17g36.4 Target to Source Transparent Container . 18g36.5 MM Context for E-UTRAN (v)SRVCC 18g36.6 MM Context for UTRAN SRVCC . 19g36.7 SRVCC Cause 20g36.8 Target RNC ID . 20g36.9 Target Global Cell ID . 20g36.10 Tunnel Endpoint Identifier for Control Plane (T
20、EID-C) 21g36.11 Sv Flags 21g36.12 Service Area Identifier . 21g36.13 MM Context for CS to PS SRVCC 22g3Annex A (informative): Change history . 23g3History 24 ETSI ETSI TS 129 280 V13.0.0 (2016-01)43GPP TS 29.280 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the
21、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 change of relea
22、se 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 substance, i.e. t
23、echnical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 280 V13.0.0 (2016-01)53GPP TS 29.280 version 13.0.0 Release 131 Scope The present document describes the Sv interface between the Mo
24、bility Management Entity (MME) or Serving GPRS Support Node (SGSN) and 3GPP MSC server enhanced for SRVCC. Sv interface is used to support Inter-RAT handover from IMS based voice service over EPS to CS domain over 3GPP UTRAN/GERAN access or from UTRAN (HSPA) to 3GPP UTRAN/GERAN access and to support
25、 Inter-RAT handover from IMS based voice and video service over EPS to CS domain over 3GPP UTRAN access. Sv interface is also used to support Inter-RAT handover from voice service in CS domain over 3GPP UTRAN/GERAN access to IMS based service over LTE or UTRAN (HSPA). If there is no specific indicat
26、ion, the term “MSC server“ denotes 3GPP MSC server enhanced for SRVCC or 3GPP MSC server enhanced for vSRVCC as defined in 3GPP TS 23.216 2. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are ei
27、ther 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 GSM document), a
28、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 3GPP TR 23.216: “Single Radio Voice Call Continuity (SRVCC)“. 3 3GPP TS 29.274: “Evolved GPRS Tunnelling Protocol for
29、 Control Plane (GTPv2-C)“. 4 3GPP TS 23.003: “Numbering, addressing and identification“. 5 3GPP TS 23.007: “Restoration Procedures“. 6 3GPP TS 33.401: “3GPP System Architecture Evolution (SAE): Security architecture“. 7 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network prot
30、ocols; Stage 3“. 8 3GPP TS 48.008: “Mobile Switching Centre Base Station System (MSC - BSS) interface; Layer 3 specification“. 9 3GPP TS 25.413: “UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling“. 10 3GPP TS 33.102: “3G Security; Security architecture“. 11 3GPP TS 29.002:
31、“Mobile Application Part (MAP) specification; Stage 3“. 12 3GPP TS 24.301: “Non-Access-Stratum (NAS) protocol for Evolved Packet“. 13 3GPP TS 23.237: “IP Multimedia Subsystem (IMS) Service Continuity: Stage 2“. 14 3GPP TS 36.413: “S1 Application Protocol (S1AP)“. 15 3GPP TS 33.401: “3GPP System Arch
32、itecture Evolution (SAE); Security architecture“. 16 3GPP TS 23.251: “Network Sharing; Architecture and Functional Description“. 17 3GPP TS 29.276: “Optimized Handover Procedures and Protocols between E-UTRAN access and cdma2000 HRPD Access“. ETSI ETSI TS 129 280 V13.0.0 (2016-01)63GPP TS 29.280 ver
33、sion 13.0.0 Release 133 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any,
34、in 3GPP TR 21.905 1. For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.216 2 apply: SRVCC vSRVCC For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.251 16 apply: Anchor PLMN 3.2 Symbols For the purposes of
35、 the present document, the following symbols apply: 3.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP 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,
36、in 3GPP TR 21.905 1. C-MSISDN Correlation MSISDN. GWCN Gateway Core NetworkMME/SGSN MME or SGSN. MOCN Multi-Operator Core Network SRVCC Single Radio Voice Call Continuity. STN-SR Session Transfer Number for SRVCC: see 3GPP TS 23.003 4. vSRVCC Single Radio Video Call Continuity. 4 General Description
37、 This document describes the Sv interface related procedures, message parameters and protocol specifications. The Sv messages are based on GTP. The message format, IE coding, and protocol error handling for Sv is per GTP as specified in 3GPP TS 29.274 3. The general rules for IP address and UDP port
38、 number handling for the GTP messages on the Sv interface is per 3GPP TS 29.274 3. 5 Sv Messages and Information Elements 5.1 Introduction The Sv application defines a set of messages between the MME/SGSN and MSC Server to provide SRVCC as defined in 3GPP TS 23.216 2. The Sv message header shall be
39、conformant to the GTPv2-C Message Header, see 3GPP TS 29.274 3. The messages to be used and the information elements are described in the following sections. ETSI ETSI TS 129 280 V13.0.0 (2016-01)73GPP TS 29.280 version 13.0.0 Release 135.2 Sv Messages 5.2.1 General Sv Messages are used for both the
40、 Inter-RAT handover from IMS based voice service over EPS to CS domain over 3GPP UTRAN/GERAN access or from UTRAN (HSPA) to 3GPP UTRAN/GERAN access and the Inter-RAT handover from IMS based voice and video service over EPS to CS domain over 3GPP UTRAN access. Sv Messages are also used for the Inter-
41、RAT handover from voice service in CS domain over 3GPP UTRAN/GERAN access to IMS based service over LTE or UTRAN (HSPA). Sv Message Type value is defined in 3GPP TS 29.274 3. The message format is coded as per GTP in 3GPP TS 29.274 3. Table 5.2.1: Message types for Sv interface Message Type value (D
42、ecimal) Message Reference Initial Triggered 0 Reserved 3GPP TS 29.274 3 1 Echo Request 3GPP TS 29.274 3 X 2 Echo Response 3GPP TS 29.274 3 X 3 Version Not Supported Indication 3GPP TS 29.274 3 4-16 Reserved for S101 interface 3GPP TS 29.276 17 17-24 Reserved for S121 interface 3GPP TS 29.276 17 25 S
43、RVCC PS to CS Request 5.2.2 X 26 SRVCC PS to CS Response 5.2.3 X 27 SRVCC PS to CS Complete Notification 5.2.4 X 28 SRVCC PS to CS Complete Acknowledge 5.2.5 X 29 SRVCC PS to CS Cancel Notification 5.2.6 X 30 SRVCC PS to CS Cancel Acknowledge 5.2.7 X 31 SRVCC CS to PS Request 5.2.8 X 32-239 Reserved
44、 for GTPv2 3GPP TS 29.274 3 240 SRVCC CS to PS Response 5.2.9 X 241 SRVCC CS to PS Complete Notification 5.2.10 X 242 SRVCC CS to PS Complete Acknowledge 5.2.11 X 243 SRVCC CS to PS Cancel Notification 5.2.12 X 244 SRVCC CS to PS Cancel Acknowledge 5.2.13 X 245 to 247 For future Sv interface use - 2
45、48-255 Reserved for GTPv2 3GPP TS 29.274 3 The GTPv2-C messages shall be sent per UE on the Sv interface. There shall be one pair of TEID-C per UE on the Sv interface. The same tunnel shall be shared for the control messages related to the same UE operation. The TEID field in the SRVCC PS to CS Requ
46、est and in the SRVCC CS to PS Request message header shall be set to “0“ because this is the first message sent between the MME/SGSN and the MSC server to establish the tunnel for a UE. The TEID field in the SRVCC PS to CS Cancel Notification message header shall be set to “0“ if the message is sent
47、 before reception of the acceptance response to the SRVCC PS to CS Request. If the MME/SGSN sends the SRVCC PS to CS Cancel Notification message after the acceptance response to the SRVCC PS to CS Request, the TEID field of the SRVCC PS to CS Cancel Notification message may be set to the MSC Server“
48、s TEID value received in the SRVCC PS to CS Response message. Therefore the MSC Server shall be able to accept the SRVCC PS to CS Cancel Notification messages with “0“ or non-zero TEID in the message header. The TEID field in the SRVCC CS to PS Cancel Notification message header shall be set to “0“
49、if the message is sent before reception of the acceptance response to the SRVCC CS to PS Request. If the MSC Server sends the SRVCC CS to PS Cancel Notification message after the acceptance response to the SRVCC CS to PS Request, the TEID field of the SRVCC CS to PS Cancel Notification message may be set to the MME/SGSN TEID value received in the SRVCC CS to PS Response message. Therefore the MME/SGSN shall be able to accept the SRVCC CS to PS Cancel Notification messages with “0“ or no
