1、 ETSI TR 1Universal Mobile Tel3GPP enablers foPush-to-talk o(3GPP TR 23.9TECHNICAL REPORT 123 979 V13.0.0 (2016elecommunications System (LTE; for Open Mobile Alliance (OMk over Cellular (PoC) services;Stage 2 .979 version 13.0.0 Release 1316-01) (UMTS); MA); es; 13) ETSI ETSI TR 123 979 V13.0.0 (201
2、6-01)13GPP TR 23.979 version 13.0.0 Release 13Reference RTR/TSGS-0223979vd00 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-Prfe
3、cture 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 versions of the present document shall not be
4、 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 specific network drive within ETSI Secretari
5、at. 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 in the present document, please send yo
6、ur 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 as authorized by written permission of
7、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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI lo
8、go 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 Association. ETSI ETSI TR 123 979 V13.0
9、.0 (2016-01)23GPP TR 23.979 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 ca
10、n 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/). Pursuant to the ETS
11、I 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 present document. Foreword
12、 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 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 TR 123 979 V13.0.0 (2016-01)33GPP TR 23.979 version 13.0.0 Release 13Conte
15、nts Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Architectural Requirements 8g34.1 General Requirements 8g34.2 PoC specific r
16、equirements relevant to 3GPP 8g35 Architectural Concept. 9g35.1 General overview . 9g35.2 Architecture assumptions . 10g35.2.1 Charging 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 gen
17、eral . 11g35.3.2.2 On-demand session with automatic answer 11g35.3.2.3 On demand session with manual answer . 14g35.3.3 Pre-established 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 a
18、nswer . 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.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
19、a PoC session 23g35.5.2 Notification of PoC Session during an ongoing CS service. . 23g35.6 PoC Charging Correlation 23g36 Conclusions 24g3Annex A: Recommended QoS settings and configuration parameters for PoC . 25g3A.1 Introduction 25g3A.2 QoS attribute settings . 25g3A.2.1 QoS attribute settings f
20、or general purpose PDP context . 25g3A.2.2 QoS attribute settings when separate PDP contexts are used for signalling and media . 26g3A.3 Radio Network Configuration 28g3Annex B: Delay analysis of PoC session establishment 29g3B.1 Introduction 29g3ETSI ETSI TR 123 979 V13.0.0 (2016-01)43GPP TR 23.979
21、 version 13.0.0 Release 13B.2 On demand session with manual answer 30g3B.3 On demand session with automatic answer 32g3B.4 On pre-established session . 33g3Annex C: Required SigComp performance . 36g3C.1 Introduction 36g3C.2 Assumptions . 36g3C.3 Estimation of SIP compression ratios 36g3C.4 SigComp
22、requirements . 37g3Annex D: Change history 38g3History 39g3ETSI ETSI TR 123 979 V13.0.0 (2016-01)53GPP TR 23.979 version 13.0.0 Release 13Foreword This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing
23、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 release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented
24、 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. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only ch
25、anges have been incorporated in the document. Introduction Advanced interactive conferencing applications like Push to talk over Cellular (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
26、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 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 Servi
27、ce (QoS) concept and architecture“. 11 3GPP TS 26.071: “AMR speech Codec; General description“. 12 RFC 3267 (June 2002): “Real-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
28、.221: “Architectural requirements“. 14 RFC 3320 (January 2003): “Signaling Compression (SigComp)“. 15 3GPP TS 24.228 “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
29、 Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. ETSI ETSI TR 123 979 V13.0.0 (2016-01)73GPP TR 23.979 version 13.0.0 Release 133 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms a
30、nd 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 establishment, the originating subscriber receives within a pre-determined time,
31、 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 Rate CCF Charging Collection Function CN Core Network CS Circuit Swit
32、chedCSCF 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 Interrogating-CSCF IE Information ElementIM IP MultimediaIMS IP Mul
33、timedia 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 Push to talk over Cellular PS Packet Switched PSI Public Service Ident
34、ity 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 Serving-CSCF SBLP Service Based Local Policy SDP Session Description Proto
35、col SDU Session Data Unit SGSN Serving GPRS Support Node ETSI ETSI TR 123 979 V13.0.0 (2016-01)83GPP TR 23.979 version 13.0.0 Release 13SIP Session Initiation Protocol SMS State Memory Size TBF Temporary Block Flow TCP Transport Control Protocol UDP User Datagram Protocol UE User Equipment UMTS Univ
36、ersal 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 the PoC service architecture as specified in OMA. It is assumed that
37、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 security including authentication and authorization; - IMS charging;
38、- 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 system to support services like PoC, certain PoC requirements will req
39、uire 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 the purposes of additional evaluation to ensure proper support is in
40、 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 initiating PoC subscriber shall receive an indication if no participants rec
41、eive 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 right-to-speak indication can be given to the originating PoC subscri
42、ber 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. - During the PoC session, the PoC service entity provides right-to-speak indication to a PoC su
43、bscriber requesting to speak. ETSI ETSI TR 123 979 V13.0.0 (2016-01)93GPP TR 23.979 version 13.0.0 Release 13- In case of a chat group session, the communication between chat group participants shall be possible at the time the PoC chat group session is established, that is at least one participant
44、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 in OMA PoC AD 6. - The user equipment, depending on its capabilities
45、, 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 introduced as an application within the frame of the IP Multimedia Subsyst
46、em (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. Ap
47、plication servers (XDMS, PoC Server, Presence Server), and interfaces between these application servers shown within the dotted box in figure 5-1 are defined by OMA. The OMA PoC architecture specification 6 leverages IMS as the underlying SIP-based IP-core network. To understand the details of how I
48、MS capabilities relate to the overall PoC architecture, there is a need to map the reference points defined in the OMA PoC specification 6, and the reference points defined in TS 23.002 3 and TS 23.228 4. The PoC server implementing the application level network functionality for the PoC service is
49、essentially seen as an Application Server from the IMS perspective. Consequently, communications between the IMS core and the PoC server utilize the ISC interface defined in TS 23.228 4. As defined by OMA PoC AD 6, the XML Document Management Server (XDMS) is used by the PoC users to manage groups and lists (e.g. contact and access lists) that are needed for the PoC service. In the IMS architecture, the Ut interface provides these functions, hence communications between the XDMS and the UE utilize the Ut interface. As defi
