Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.979  Word version:  17.0.0

Top   Top   None   None   Next
0…   5…

 

0  Introductionp. 6

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 & its capabilities as a base for the PoC services.

1  Scopep. 7

The present document studies the architectural requirements in order to enable services like PoC over 3GPP systems. The report looks into aspects of using 3GPP PS domain and radio access technologies (GERAN, UTRAN) for bearer services and IMS for reachability and connectivity for applications like PoC.

2  Referencesp. 7

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 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 non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]  Void.
[2]
TS 21.905: "Vocabulary for 3GPP Specifications".
[3]
TS 23.002: "Network architecture".
[4]
TS 23.228: "IP Multimedia (IM) Subsystem; Stage 2.
[5]
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]
TS 23.207: "End-to-end Quality of Service (QoS) concept and architecture".
[10]
TS 23.107: "Quality of Service (QoS) concept and architecture".
[11]
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]
TS 23.221: "Architectural requirements".
[14]
RFC 3320:  (January 2003): "Signaling Compression (SigComp)".
[15]
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]
TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[17]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[18]
TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[19]
TS 32.299: "Telecommunication management; Charging management; Diameter charging applications".
[20]
RFC 2507:  "IP Header Compression".
[21]
RFC 3095:  "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed".
Up

3  Definitions, symbols and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TS 21.905 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, an indication before he can speak, this is known as "Right to Speak (RtS)".

3.2  Abbreviationsp. 8

For the purposes of the present document, the following abbreviations apply:
AMR
Adaptive Multi-Rate
AS
Application Server
BER
Bit Error Rate
CCF
Charging Collection Function
CN
Core Network
CS
Circuit Switched
CSCF
Call Session Control Function
DL
DownLink
DTM
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 Element
IM
IP Multimedia
IMS
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
Push 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
Serving-CSCF
SBLP
Service Based Local Policy
SDP
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 Control Protocol
UDP
User Datagram Protocol
UE
User Equipment
UMTS
Universal Mobile Telecommunications System
UTRAN
UMTS Terrestrial Radio Access Network
XDMS
XML Document Management Server
Up

4  Architectural Requirementsp. 9

4.1  General Requirementsp. 9

The 3GPP system shall provide the capabilities to support the 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 and TS 23.141:
  • Registration;
  • IMS routing capabilities, including discovery and address resolution;
  • IMS security 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.
Up

4.2  PoC specific requirements relevant to 3GPPp. 9

In order for 3GPP system 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 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 initiating 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 right-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.
  • 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 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 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.
Up

Up   Top   ToC