1、 ETSI TR 123 979 V15.0.0 (2018-06) Universal Mobile Telecommunications System (UMTS); LTE; 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 (3GPP TR 23.979 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 123 979 V15.0.0 (2018-06)13GPP TR 23.97
2、9 version 15.0.0 Release 15Reference RTR/TSGS-0223979vf00 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 de Grasse (06
3、) 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 modified without t
4、he 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. Users of the pr
5、esent 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your commen
6、t 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. The
7、 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit
8、 of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 123 979 V15
9、.0.0 (2018-06)23GPP TR 23.979 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members a
10、nd 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.etsi.org/
11、). 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 the pres
12、ent document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/
13、or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present d
14、ocument 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 ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/we
15、bapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “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 “
16、must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 123 979 V15.0.0 (2018-06)33GPP TR 23.979 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6
17、g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Architectural Requirements 8g34.1 General Requirements 8g34.2 PoC specific requirements relevant to 3GPP 8g35 Architectural Concept. 9g35.1 General overview . 9g35.2 Architecture assumptions . 10g35.2.1 Charg
18、ing architecture aspects . 10g35.3 Signalling plane impacts 10g35.3.1 General aspects for PoC signalling . 10g35.3.2 On-demand Session 11g35.3.2.1 On-demand session general . 11g35.3.2.2 On-demand session with automatic answer 11g35.3.2.3 On demand session with manual answer . 14g35.3.3 Pre-establis
19、hed Session. 17g35.3.3.1 Pre-established session general . 17g35.3.3.2 Pre-established session with automatic answer . 17g35.3.3.3 Pre-established session with manual answer . 19g35.4 User plane impacts . 22g35.4.1 General 22g35.4.2 GPRS interactions in relation to PoC 22g35.4.2.1 General 22g35.4.2.
20、2 QoS traffic class considerations 22g35.4.3 PoC and SBLP/Go functions 23g35.5 Notification of Parallel Services . 23g35.5.1 Notification of incoming CS service during a PoC session 23g35.5.2 Notification of PoC Session during an ongoing CS service. . 23g35.6 PoC Charging Correlation 23g36 Conclusio
21、ns 23g3Annex A: Recommended QoS settings and configuration parameters for PoC . 25g3A.1 Introduction 25g3A.2 QoS attribute settings . 25g3A.2.1 QoS attribute settings for general purpose PDP context . 25g3A.2.2 QoS attribute settings when separate PDP contexts are used for signalling and media . 26g
22、3A.3 Radio Network Configuration 28g3Annex B: Delay analysis of PoC session establishment 29g3B.1 Introduction 29g3B.2 On demand session with manual answer 30g3ETSI ETSI TR 123 979 V15.0.0 (2018-06)43GPP TR 23.979 version 15.0.0 Release 15B.3 On demand session with automatic answer 32g3B.4 On pre-es
23、tablished session . 33g3Annex C: Required SigComp performance . 36g3C.1 Introduction 36g3C.2 Assumptions . 36g3C.3 Estimation of SIP compression ratios 36g3C.4 SigComp requirements . 37g3Annex D: Change history 38g3History 39g3ETSI ETSI TR 123 979 V15.0.0 (2018-06)53GPP TR 23.979 version 15.0.0 Rele
24、ase 15Foreword This Technical Report has been produced by the 3rd Generation 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 wil
25、l 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 approved document under change control. y the s
26、econd 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. Introduction Advanced interactive conferencing applications like Push to talk over Cel
27、lular (PoC) service enablers are being developed in OMA. It is expected that some enhancements of the 3GPP specifications will be needed in order to use IMS Stage 2. 5 3GPP TS 23.141: “Presence Service; Stage 2“. 6 OMA-AD-PoC-V1.0: OMA PoC Specification, Architecture Document. 7 OMA-RD-PoC-V1_0: OMA
28、 PoC Specification, Requirements Document. 8 Void. 9 3GPP TS 23.207: “End-to-end Quality of Service (QoS) concept and architecture“. 10 3GPP TS 23.107: “Quality of Service (QoS) concept and architecture“. 11 3GPP TS 26.071: “AMR speech Codec; General description“. 12 IETF RFC 3267: (June 2002): “Rea
29、l-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs“. 13 3GPP TS 23.221: “Architectural requirements“. 14 IETF RFC 3320: (January 2003): “Signaling Compression (SigComp)“. 15 3GPP TS 24.228: “
30、Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 16 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 17 3GP
31、P TS 32.240: “Telecommunication management; Charging management; Charging architecture and principles“. 18 3GPP TS 32.260: “Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging“. 19 3GPP TS 32.299: “Telecommunication management; Charging management; Diameter char
32、ging applications“. ETSI ETSI TR 123 979 V15.0.0 (2018-06)73GPP TR 23.979 version 15.0.0 Release 1520 IETF RFC 2507: “IP Header Compression“. 21 IETF RFC 3095: “RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed“. 3 Definitions, symbols and abbreviations 3
33、.1 Definitions For the purposes of the present document, the terms and definitions given in TS 21.905 2 and the following apply. PoC session: This is an established connection between PoC users where the users can communicate using voice one at a time. Right to Speak: In the PoC session establishmen
34、t, the originating subscriber receives within a pre-determined time, an indication before he can speak, this is known as “Right to Speak (RtS)“. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AMR Adaptive Multi-Rate AS Application ServerBER Bit Error R
35、ate CCF Charging Collection Function CN Core Network CS Circuit SwitchedCSCF Call Session Control Function DL DownLinkDTM Dual Transfer Mode ECF Event Charging Function FBC Flow Based Charging GERAN GSM EDGE Radio Access Network GGSN Gateway GPRS Support Node GPRS General Packet Radio Service I-CSCF
36、 Interrogating-CSCF IE Information ElementIM IP MultimediaIMS IP Multimedia Subsystem IP Internet Protocol ISC IP multimedia Service Control NAS Non-Access Stratum OCS Online Charging System OMA Open Mobile Alliance P-CSCF Proxy-CSCF PCO Protocol Configuration Options PDP Packet Data Protocol PoC Pu
37、sh to talk over Cellular PS Packet Switched PSI Public Service Identity QoS Quality of Service RAB Radio Access Bearer RB Radio Bearer RD Requirements Document RL Radio Link RLC Radio Link Control RRC Radio Resource Control RTP Real-Time Transport Protocol RtS right-to-speak indication S-CSCF Servin
38、g-CSCF SBLP Service Based Local Policy ETSI ETSI TR 123 979 V15.0.0 (2018-06)83GPP TR 23.979 version 15.0.0 Release 15SDP Session Description Protocol SDU Session Data Unit SGSN Serving GPRS Support Node SIP Session Initiation Protocol SMS State Memory Size TBF Temporary Block Flow TCP Transport Con
39、trol Protocol UDP User Datagram Protocol UE User Equipment UMTS Universal Mobile Telecommunications System UTRAN UMTS Terrestrial Radio Access Network XDMS XML Document Management Server 4 Architectural Requirements 4.1 General Requirements The 3GPP system shall provide the capabilities to support t
40、he PoC service architecture as specified in OMA. It is assumed that the PoC architecture makes use of the following IMS capabilities in the 3GPP system, which are described in TS 23.228 4 and TS 23.141 5: - Registration; - IMS routing capabilities, including discovery and address resolution; - IMS s
41、ecurity including authentication and authorization; - IMS charging; - SIP compression; - IMS group management; - Public service identities; - Presence Service. Commonality and differences with IMS conferencing require further study. 4.2 PoC specific requirements relevant to 3GPP In order for 3GPP sy
42、stem to support services like PoC, certain PoC requirements will require additional analysis within 3GPP in order to determine that all necessary architectural support is in place via capabilities provided by the GERAN/UTRAN, GPRS and IMS. This clause captures the possible relevant requirements for
43、the purposes of additional evaluation to ensure proper support is in place within 3GPP infrastructure: - The PoC service entity may provide the originating user with an early indication to start to speak even before invited users accept the call. - If the above condition is applied then the initiati
44、ng PoC subscriber shall receive an indication if no participants receive the talk burst. - The originating subscriber receives right-to-speak (RtS) indication after certain time depending on the answer mode setting of the target PoC subscriber. - Depending on the setting by the PoC subscriber, the r
45、ight-to-speak indication can be given to the originating PoC subscriber before the target PoC subscriber is reached or at least one of the target PoC subscribers has to accept the PoC session before the right-to-speak indication is given to the originating PoC subscriber. ETSI ETSI TR 123 979 V15.0.
46、0 (2018-06)93GPP TR 23.979 version 15.0.0 Release 15- During the PoC session, the PoC service entity provides right-to-speak indication to a PoC subscriber requesting to speak. - In case of a chat group session, the communication between chat group participants shall be possible at the time the PoC
47、chat group session is established, that is at least one participant has joined the chat session. - The timing requirements for capabilities such as RtS shall be taken into account within 3GPP as specified in OMA PoC RD 7. - Charging architecture requirements shall be taken into account as specified
48、in OMA PoC AD 6. - The user equipment, depending on its capabilities, shall support notification of incoming CS call during an ongoing PoC session as well as a notification of an incoming PoC session set up during an ongoing CS call. 5 Architectural Concept 5.1 General overview PoC service is introd
49、uced as an application within the frame of the IP Multimedia Subsystem (IMS). Figure 5.1 below illustrates how the PoC service elements fit into the IMS architecture. UE ISC IMS core PoC Server P-CSCF XDMS Mw Gm Ut S-CSCF PresenceServer Figure 5-1: PoC service elements in the IMS architecture NOTE: The I-CSCF is not shown in figure 5-1 for the sake of simplicity. Application servers (XDMS, PoC Server, Presence Server), and interfaces between these application servers shown within the dotted box in figure 5-1 are defined by OM
