1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelConference (COCore NeProt(3GPP TS 24.6TECHNICAL SPECIFICATION124 605 V13.0.0 (2016communications system (Phaelecommunications System (LTE; (CONF) using IP Multimedia (IMetwork (CN) subsystem; rotocol specification .605 version 13.0.0 Release 1316-
2、01) hase 2+); (UMTS); (IM) 13) ETSI ETSI TS 124 605 V13.0.0 (2016-01)13GPP TS 24.605 version 13.0.0 Release 13Reference RTS/TSGC-0124605vd00 Keywords GSM,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 00
3、017 - 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 print. The content of any e
4、lectronic 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 Portable Document Format
5、(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:/portal.etsi.org/tb/status/s
6、tatus.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 mechanical, including photo
7、copying 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 Telecommunications Standards Institute 2
8、016. 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 GSM logo are Trade Marks reg
9、istered and owned by the GSM Association. ETSI ETSI TS 124 605 V13.0.0 (2016-01)23GPP TS 24.605 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
10、 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. Latest updates are availabl
11、e 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 ETSI Web server) which are, o
12、r 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, UMTS identities or GSM identi
13、ties. 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“, “shall not“, “should“, “s
14、hould 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 direct citation. ETSI ETSI
15、 TS 124 605 V13.0.0 (2016-01)33GPP TS 24.605 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 CONFerence (CONF). 7g34.1
16、Introduction 7g34.2 Description . 7g34.2.1 General description . 7g34.3 Operational requirements . 8g34.3.1 Provision/withdrawal 8g34.3.2 Requirements on the originating network side 8g34.3.3 Requirements in the network 8g34.3.4 Requirements on the terminating network side . 8g34.4 Coding requiremen
17、ts 8g34.5 Signalling requirements 8g34.5.1 Activation/deactivation . 8g34.5.1a Registration/erasure 8g34.5.1b Interrogation . 8g34.5.2 Invocation and operation 8g34.5.2.1 Actions at the originating UE 9g34.5.2.1.1 User joining a conference 9g34.5.2.1.2 User inviting another user to a conference 9g34
18、.5.2.1.3 User leaving a conference 9g34.5.2.1.4 User creating a conference 9g34.5.2.1.5 Subscription for the conference event package . 9g34.5.2.2 Actions at the conferencing AS . 9g34.5.2.2.1 Conference focus . 9g34.5.2.2.1A Void . 10g34.5.2.2.2 Conference notification service . 10g34.5.2.2A Proced
19、ures at the AS serving the originating user . 10g34.5.2.3 Void. 10g34.5.2.4 Void. 10g34.5.2.5 Void. 10g34.5.2.6 Void. 10g34.5.2.7 Actions at the destination UE 10g34.5.2.8 Void. 11g34.5.2.9 Void. 11g34.6 Interaction with other services 11g34.6.1 Communication HOLD (HOLD) 11g34.6.2 Terminating Identi
20、fication Presentation (TIP) 11g34.6.3 Terminating Identification Restriction (TIR) 11g34.6.4 Originating Identification Presentation (OIP) . 11g34.6.5 Originating Identification Restriction (OIR) . 11g34.6.6 CONFerence calling (CONF) . 11g34.6.7 Communication DIVersion services (CDIV) 11g34.6.8 Mali
21、cious Communication IDentification (MCID) 11g34.6.9 Anonymous Communication Rejection and Communication Barring (ACR/CB) . 12g34.6.10 Explicit Communication Transfer (ECT) . 12g3ETSI ETSI TS 124 605 V13.0.0 (2016-01)43GPP TS 24.605 version 13.0.0 Release 134.7 Interworking with other networks 12g34.
22、7.1 Void 12g34.7.2 Void 12g34.7.3 Void 12g34.8 Parameter values (timers) . 12g3Annex A (informative): Signalling flows 13g3A.0 Scope of signalling flows . 13g3A.1 CONF interworking signalling flow in case of an active communication between IMS and PSTN . 13g3A.2 Call flow for 3PTY CONF . 19g3A.2.1 I
23、nvite other user to 3PTY CONF by sending REFER request 19g3A.2.2 Invite other user to 3PTY CONF by sending INVITE request with URI list . 21g3A.3 Void 23g3Annex B (informative): Example of filter criteria . 24g3Annex C (informative): Change history . 25g3History 26g3ETSI ETSI TS 124 605 V13.0.0 (201
24、6-01)53GPP TS 24.605 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 work within the TSG and may change following formal TSG approval. Should the TSG modif
25、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
26、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 TS 124 605 V13.0.0 (2016-01)63
27、GPP TS 24.605 version 13.0.0 Release 131 Scope The present document specifies the stage three Protocol Description of the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsyste
28、m based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). The present document specifies centralized conferencing, using a conference focus, distributed conferencing is out of scope. The present document does not cover the cases of : a) cascading conference service
29、s; and b) the support of the PSTN/ISDN conference service hosted in the PSTN. The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CONF supplementary service. 2 References The following documents contain provisions which, through re
30、ference 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 version
31、 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 22.173: “IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Servic
32、e and supplementary services; Stage 1“. 2 3GPP TS 24.229: “Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 3 Void 4 Void. 5 Void. 6 Void. 7 3GPP TS 24.147: “Conferencing using the IP Multimedia (IM)
33、Core Network (CN) subsystem; Stage 3“. 8 IETF RFC 3891: “The SIP Replaces header“. 9 Void. 10 ETSI TS 183 043 V3.4.1 (2011-04):“Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS - based PSTN/ISDN Emulation; Stage 3 specification“ 11 3GPP TS 24.628
34、: “Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification“. 12 3GPP TS 24.610: “Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification“. ETSI ETSI TS 124 605 V13.0.0 (2016-01)73GPP TS 24.605 v
35、ersion 13.0.0 Release 1313 IETF RFC 7090 (April 2014): “Public Safety Answering Point (PSAP) Callback“. 14 3GPP TS 24.166: “3GPP IMS Conferencing Management Object (MO)“. 15 3GPP TS 23.003: “Numbering, addressing and identification“. 3 Definitions and abbreviations 3.1 Definitions For the purposes o
36、f the present document, the terms and definitions given in 3GPP TS 22.173 1 and 3GPP TS 24.147 7 apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ACR/CB Anonymous Communication Rejection and Communication Barring AS Application Server CDIV Communi
37、cation DIVersion CONF CONFerence calling CS Circuit Switch ECT Explicit Communication Transfer HOLD communication HOLD IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Data Network MCID Malicious Communication IDentification MGCF Media Gateway Control Function OIP Originating
38、 Identification Presentation OIR Originating Identification Restriction PSAP Public Safety Answering Point P-CSCF Proxy CSCFPSTN Public Switched Telephone Network SIP Session Initiation Protocol TIP Terminating Identification Presentation TIR Terminating Identification Restriction UE User Equipment
39、4 CONFerence (CONF) 4.1 Introduction The CONFerence (CONF) service enables a user to participate in and control a simultaneous communication involving a number of users. 4.2 Description 4.2.1 General description When the CONF service is invoked, conference resources are allocated to the served user.
40、 Once a conference is active, users can join and leave a conference, and remote users can be added to or removed from the conference. ETSI ETSI TS 124 605 V13.0.0 (2016-01)83GPP TS 24.605 version 13.0.0 Release 13Conference participants can request to be informed of these actions. The Management Obj
41、ect as defined in 3GPP TS 24.166 14 provides a mechanism for the UE to discover the Conference Factory URI to be used for the CONF service. If the UE is not configured with the Conference Factory URI within the Management Object then the UE shall derive a Conference Factory URI for MMTEL as describe
42、d in subclause 13.10 of 3GPP TS 23.003 15 to be used for the CONF service. NOTE: Depending on the network operator, various mechanisms can be applied to discover the Conference Factory URI (e.g., include the Conference Factory URI in a letter written to the user or publish it on a website). A derive
43、d Conference Factory URI might not be a valid URI. 4.3 Operational requirements 4.3.1 Provision/withdrawal The CONF service shall be provided after prior arrangement with the service provider. 4.3.2 Requirements on the originating network side No specific requirements are needed in the network. 4.3.
44、3 Requirements in the network No specific requirements are needed in the network. 4.3.4 Requirements on the terminating network side No specific requirements are needed in the network. 4.4 Coding requirements For coding requirements see 3GPP TS 24.147 7, clause 5. 4.5 Signalling requirements 4.5.1 A
45、ctivation/deactivation The CONF service is activated at provisioning and deactivated at withdrawal. 4.5.1a Registration/erasure The CONF service requires no registration. Erasure is not applicable. 4.5.1b Interrogation Interrogation of CONF is not applicable. 4.5.2 Invocation and operation This subc
46、lause describes the usage of and the changes to the procedures of 3GPP TS 24.147 7 for invoking and operating a conference. ETSI ETSI TS 124 605 V13.0.0 (2016-01)93GPP TS 24.605 version 13.0.0 Release 134.5.2.1 Actions at the originating UE 4.5.2.1.1 User joining a conference Procedures according to
47、 3GPP TS 24.147 7, subclause 5.3.1.4 shall apply. 4.5.2.1.2 User inviting another user to a conference Procedures according to 3GPP TS 24.147 7, subclause 5.3.1.5 shall apply with the following additions to subclause 5.3.1.5.3 of 3GPP TS 24.147 7: - A UE that has initiated an emergency call, shall n
48、ot perform any procedures to add the remote user in that call to a conference. - In order to avoid the establishment of a second communication to the invited user, in case of an active session the UE may additionally include the Replaces header in the header portion of the SIP URI of the Refer-to he
49、ader of the REFER request. The included Replaces header shall refer to the active dialog that is replaced by the ad-hoc conference. The Replaces header shall comply with RFC 3891 8. NOTE 1: In case of an interworking to the PSTN the routing of the INVITE request from the conference focus to the MGCF that handles the Replaces information is not deterministic and the replacement of the active dialog might fail. EXAMPLE: Refer-To: . NOTE 2: If a conference participant invites another user to a conference by using a REFER re
