ETSI TR 129 949-2016 Universal Mobile Telecommunications System (UMTS) LTE Study on technical aspects on roaming end-to-end scenarios with Voice over LTE(VoLTE) IP Multimedia subsy.pdf

《ETSI TR 129 949-2016 Universal Mobile Telecommunications System (UMTS) LTE Study on technical aspects on roaming end-to-end scenarios with Voice over LTE(VoLTE) IP Multimedia subsy.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 129 949-2016 Universal Mobile Telecommunications System (UMTS) LTE Study on technical aspects on roaming end-to-end scenarios with Voice over LTE(VoLTE) IP Multimedia subsy.pdf（107页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 1Universal Mobile TelStudy on technical aspewith Voice over LTE (Voan(3GPP TR 29.9TECHNICAL REPORT 129 949 V12.2.0 (2016elecommunications System (LTE; pects on roaming end-to-end(VoLTE) IP Multimedia Subsysand other networks .949 version 12.2.0 Release 1216-01) (UMTS); d scenarios ystem (IM

2、S) 12) ETSI ETSI TR 129 949 V12.2.0 (2016-01)13GPP TR 29.949 version 12.2.0 Release 12Reference RTR/TSGC-0329949vc20 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

3、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 print. The content of any electronic and/or print versi

4、ons 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 Portable Document Format (PDF) version kept on a spec

5、ific 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:/portal.etsi.org/tb/status/status.asp If you find errors

6、 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 mechanical, including photocopying and microfilm except

7、 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 Telecommunications Standards Institute 2016. All rights reserved. DE

8、CTTM, 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 GSM logo are Trade Marks registered and owned by the GSM

9、 Association. ETSI ETSI TR 129 949 V12.2.0 (2016-01)23GPP TR 29.949 version 12.2.0 Release 12Intellectual 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

10、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. Latest updates are available on the ETSI Web server (ht

11、tps:/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 become, ess

12、ential to the present document. Foreword This Technical Report (TR) 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 a

13、s 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“, “wil

14、l“, “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 TR 129 949 V12.2.0 (2016-01)33GPP

15、TR 29.949 version 12.2.0 Release 12Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 9g34 Overview 10g34.1 General . 10g34.2 3GPP specifications releva

16、nt for roaming architecture and procedures . 10g34.3 Consideration of SIP header fields and elements . 11g34.3.1 Inter Operator Identifier 11g34.3.1.1 Type of IOIs . 11g34.3.1.2 Format of IOIs 12g34.3.1.3 Basic IMS roaming scenario without loopback. 12g34.3.1.4 Originating visited network with loopb

17、ack routeing scenario . 13g34.3.1.5 Rules for transit-ioi . 14g34.3.2 Naming of URIs 16g34.3.2.1 General 16g34.3.2.2 Home Network Domain 16g34.3.2.3 Private user identity. 16g34.3.2.4 Public user identity 16g34.3.2.5 Instance-ID 17g34.4 Identifying the II-NNI traversal scenario 17g34.5 Use of precon

18、ditions in IMS networks . 17g34.6 Loopback-indication header field parameter 17g35 Description of Scenarios 18g35.1 General . 18g35.1.1 Methodology . 18g35.1.1.1 Key required to interpret signalling flow in message coding examples 18g35.1.1.2 Functional entities covered in example flows . 19g35.1.1.

19、3 Notation conventions 19g35.1.1.3.1 Introduction . 19g35.1.1.3.2 Public user Identities, public service identities and IP addresses 20g35.1.1.3.3 Network Entities 20g35.1.1.3.3.1 Served user UE-As associated entities 20g35.1.1.3.3.2 Remote users associated entities . 21g35.1.1.3.3.3 Interconnection

20、 networks associated entities . 21g35.1.1.4 IOI values 21g35.2 Registration when roaming. 21g35.2.1 General 21g35.2.2 Registration via IC SIP proxies . 22g35.2.3 Subscription to the registration-state event package . 28g35.2.3.1 General 28g35.2.3.2 The UE subscribes to the registration-state event p

21、ackage . 28g35.2.3.3 The P-CSCF subscribes to the registration-state event package . 36g35.3 Originating roaming without loopback . 43g35.3.1 General 43g35.3.2 Call flow . 43g35.4 Originating roaming with loopback 52g3ETSI ETSI TR 129 949 V12.2.0 (2016-01)43GPP TR 29.949 version 12.2.0 Release 125.4

22、.1 General 52g35.4.2 Call flow . 52g35.5 Routeing when the originating and terminating user reside in the same home network 71g35.6 Routeing from originating home to terminating home network . 71g35.7 Routeing from originating visited network to terminating home network . 71g35.8 Routeing in termina

23、ting home network when user resides in this network 72g35.9 Routeing from terminating home network to the terminating visited network . 72g35.10 Insertion of service related media in the originating home network 80g35.10.1 General 80g35.10.2 Insertion of service related media in the originating home

24、 network with loopback . 81g35.10.3 Insertion of service related media in the originating home network without loopback 84g35.11 PS to CS SRVCC access transfer scenarios . 86g35.11.1 General 86g35.11.2 PS to CS SRVCC information transfer during registration. 86g35.11.3 PS to CS SRVCC access transfer

25、 for a call in the active phase without loopback . 94g35.11.4 PS to CS SRVCC access transfer for a call in the active phase with loopback 102g35.12 Invocation and configuration of services during roaming in a visited network 104g3Annex A: Change history . 105g3History 106g3ETSI ETSI TR 129 949 V12.2

26、.0 (2016-01)53GPP TR 29.949 version 12.2.0 Release 12Foreword This Technical Report 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 modif

27、y 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 greater indicates TSG a

28、pproved 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 TR 129 949 V12.2.0 (2016-01)63

29、GPP TR 29.949 version 12.2.0 Release 121 Scope The present document describes end-to-end use cases and signalling flows based on the roaming architecture for voice over IMS with local breakout. It summarizes the contents of existing 3GPP technical specifications which are needed for roaming use case

30、s. The scenarios used cover the following use cases: - registration when roaming; - routeing from originating visited network to originating home network; - loopback routeing from originating home network to originating visited network; - routeing when the originating and terminating user reside in

31、the same home network; - routeing from the originating home network to the terminating home network; - routeing from the originating visited network to the terminating home network; - routeing in terminating home network when user resides in this network; - routeing from terminating home network to

32、the terminating visited network; - insertion of service related media in the originating home network; - routeing through transit networks; and - access transfer scenarios (SRVCC). Editors note: It is ffs if the call forwarding service invocation in a Call Deflection case will be considered. 2 Refer

33、ences The following documents contain provisions which, through 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 re

34、visions 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 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:

35、 “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.002: “Network architecture“. 3 3GPP TS 23.228: “IP multimedia subsystem; Stage 2“. 4 3GPP TS 24.229: “IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 5 3GPP TS 29.079:

36、 “Optimal Media Routeing within the IP Multimedia Subsystem; Stage 3“. 6 3GPP TS 29.165: “Inter-IMS Network to Network Interface (NNI)“. 7 3GPP TR 23.850: “Study on roaming architecture for voice over IP Multimedia Subsystem (IMS) with local breakout“ (Release 11). 8 GSMA IR.92: “IMS Profile for Voi

37、ce and SMS“. 9 IETF RFC 3261: “SIP: Session Initiation Protocol“. ETSI ETSI TR 129 949 V12.2.0 (2016-01)73GPP TR 29.949 version 12.2.0 Release 1210 IETF RFC 1594: “FYI on Questions and Answers to Commonly asked “New Internet User“ Questions“. 11 Void. 12 3GPP TS 23.218: “IP Multimedia (IM) Session H

38、andling; IM call model“. 13 IETF RFC 3263: “Session Initiation Protocol (SIP): Locating SIP Servers“. 14 3GPP TS 29.228: “IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents“. 15 GSMA IR.88: “LTE Roaming Guidelines“. 16 3GPP TS 23.003: “Numbering, addressing and

39、identification“. 17 IETF RFC 4282: “The Network Access Identifier“. 18 IETF RFC 3966: “The tel URI for Telephone Numbers“. 19 IETF RFC 4122: “A Universally Unique IDentifier (UUID) URN Namespace“. 20 3GPP TS 24.237: “IP Multimedia Subsystem (IMS) Service Continuity; Stage 3“. 21 IETF RFC 6809: “Mech

40、anism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)“. 22 3GPP TS 24.628: “Common Basic Communication procedures using IP Multimedia (IM)“. 23 IETF RFC 3455: “Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generati

41、on Partnership Project (3GPP)“. 24 IETF RFC 2782: “A DNS RR for specifying the location of services (DNS SRV)“. 25 3GPP TS 32.260: “Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging“. 26 IETF RFC 7549: “3GPP SIP URI Inter Operator Traffic Leg parameter“. 27 IE

42、TF RFC 3323: “A Privacy Mechanism for the Session Initiation Protocol (SIP)“. 28 IETF RFC 3325: “Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks“. 30 3GPP TS 29.212: “Policy and Charging Control (PCC); Reference Points“. 31 3GPP TS 29.214: “P

43、olicy and charging control over Rx reference Point“. 32 IETF RFC 3262 (June 2002): “Reliability of provisional responses in Session Initiation Protocol (SIP)“. 33 IETF RFC 3312 (October 2002): “Integration of resource management and Session Initiation Protocol (SIP)“. 3 Definitions and abbreviations

44、 3.1 Definitions For the purposes of the present document, the terms and definitions given in 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, in TR 21.905 1. For the purposes of the present document, the follo

45、wing terms and definitions given in TS 24.229 4 apply: ETSI ETSI TR 129 949 V12.2.0 (2016-01)83GPP TR 29.949 version 12.2.0 Release 12Entry point: In the case that “border control concepts“, as specified in TS 23.228 3, are to be applied in an IM CN subsystem, then these are to be provided by capabi

46、lities within the IBCF, and the IBCF acts as an entry point for this network (instead of the I-CSCF). In this case the IBCF and the I-CSCF can be co-located as a single physical node. If “border control concepts“ are not applied, then the I-CSCF is considered as an entry point of a network. If the P

47、-CSCF is in the home network, then the I-CSCF is considered as an entry point for this document. Exit point: If operator preference requires the application of “border control concepts“ as specified in TS 23.228 3, then these are to be provided by capabilities within the IBCF, and requests sent towa

48、rds another network are routed via a local network exit point (IBCF), which will then forward the request to the other network (discovering the entry point if necessary). For the purposes of the present document, the following terms and definitions given in TS 23.228 3 subclauses 3.1, 4.3.3.1, 4.3.6

49、, 4.6, 4.13, 5.2, 5.4.12.1 and 5.10 apply: Border control concepts Geo-local service number Home local service number Implicit registration set Interconnection Border Control Function (IBCF) Interrogating-CSCF (I-CSCF) IMS Application Level Gateway (IMS-ALG) IMS application reference IMS Application Reference Identifier (IARI) IMS communication service IMS Communication Service Identifier (ICSI) Local service number IP-Connectivity Access Network (IP-CAN) Policy and Charging Rule Function (PCRF)