OMA-TP-2014-0177
Comparison of MCPTT Requirements and
PCPS 1.0
Submitted To: TP, Critical Communications Workshop
Date: 15 Aug 2014
Availability: X Public
OMA Confidential
Contact: Jerry Shih and Bryan Sullivan, AT&T
Source: AT&T
USE OF THIS DOCUMENT BY NON-OMA MEMBERS IS SUBJECT TO ALL OF THE TERMS AND CONDITIONS OF THE USE
AGREEMENT (located at http://www.openmobilealliance.org/UseAgreement.html) AND IF YOU HAVE NOT AGREED TO THE
TERMS OF THE USE AGREEMENT, YOU DO NOT HAVE THE RIGHT TO USE, COPY OR DISTRIBUTE THIS DOCUMENT.
THIS DOCUMENT IS PROVIDED ON AN "AS IS" "AS AVAILABLE" AND "WITH ALL FAULTS" BASIS.
Intellectual Property Rights
Members and their Affiliates (collectively, "Members") agree to use their reasonable endeavours to inform timely the Open Mobile Alliance of Essential IPR as they become
aware that the Essential IPR is related to the prepared or published Specification. This obligation does not imply an obligation on Members to conduct IPR searches. This
duty is contained in the Open Mobile Alliance application form to which each Member's attention is drawn. Members shall submit to the General Manager of Operations of
OMA the IPR Statement and the IPR Licensing Declaration. These forms are available from OMA or online at the OMA website at www.openmobilealliance.org.
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TP-2014-0177
Slide #1
[OMA-Template-WIDpresentation-20130101-I]
Purpose of this Presentation
• Offer an initial analysis of the overlap & gaps between PCPS 1.0 and
MCPTT requirements (latest draft)
• Help focus the next level of detailed analysis
• Help focus 3GPP work on additional requirements detail as helpful
• Optimize future efforts to close the gaps in PCPS, wherever done
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TP-2014-0177
Slide #2
[OMA-Template-WIDpresentation-20130101-I]
Summary Table
MCPTT RD section
PCPS RD section
MCPTT
Requirement
Group Call
6.2 General Group Call 6.1.2 One-to-Many
Communication Feature
6.3 Commencement
Modes for MCPTT Calls
6.8 Dynamic Group
Management
6.1.4 Session Setup
Procedures
6.1.6 Management
6.1.9.6 Automatic
Notification of Limited
Participating Information
6.1.10 Enhanced PoC
Session Control
6.1.11.6 Moderated PoC
Groups
6.1.18 Dispatcher
Functions
6.1.21 Operational
Requirements
6.1.23 Multiple Group
Operation, Broadcast, Late
Call Entry
6.1.24 PoC Sessions with
Multiple PoC Groups
6.1.33 Separate 1-to-1 PoC
Session while having a PoC
session
PCPS Feature
Creation of the group
• By PoC subscriber/host/administrator; a PoC User may
belong to multiple PoC groups
• 1-to-1, 1-to-many, 1-to-many-to-1, moderated
(dispatcher)
• Pre-arranged, ad-hoc, and chat PoC group
• Max number of group can be created per subscriber
• If a user tries to re-join a previous ad-hoc group (already
terminated), a list of the users on that group session will
be provided for “restart”
• Assign QoE to each group, primary and secondary
groups
• Ad-hoc group to include other groups and users
• Group advertisement
• Two-level auth (UE, user)
• Invite to join vs affiliation
• Group hierarchy
• Regrouping with hierarchy
• Notification of regrouping
• Monitoring
• In progress call
cancellation
Group Operation
•
•
•
•
•
•
•
•
•
•
•
•
•
•
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
PCPS Gap
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
Invitation to join, leave and rejoin
Max number to participants
Talker ID provided (MSISDN, SIPURI)
Early indication to speak before anyone accept, as soon
as one accepted,
Conformation (accept, reject) from recipient on INVITE
PoC Admin or user with the rights can expel a member
during a PoC group session
Crisis handling request (should be assigned with high
enough priority in process)
Interworking with other P2T services
Dispatcher functions
PoC Group session search and join
Advertisement of group information (such as group ID,
administrator of the group etc.)
Monitor multiple PoC group sessions
One-to-one and group sessions co-exist
Support roaming
OMA-TP-2014-0177
Slide #3
[OMA-Template-WIDpresentation-20130101-I]
Summary Table
MCPTT RD section
PCPS RD section
MCPTT
Requirement
Floor Control 6.1.2 Floor Control 6.1.5 Floor Control
6.4 Queuing
6.1.11 Media Burst
Control
PCPS Feature
Request Rights to Speak
• granted, denied
Floor availability
• Finish speaking, about to speak,
forced to release,
PCPS Gap
• Private call in group call?
• Priority hierarchy
• Overriding and overridden
transmissions
Transmit
• Max time (duration) to transmit with
warning when reached
Media Burst Control
• Independent for media type
Floor Queuing
• Indication of request has been
queued
• Know queuing position
• More than one level of priority
support
• Cancel request
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TP-2014-0177
Slide #4
[OMA-Template-WIDpresentation-20130101-I]
Summary Table
MCPTT RD section
PCPS RD section
MCPTT
Requirement
6.2.5/6
6.1 High Level Requirements
Group
Membership Membership/affiliation 6.1.18 Dispatcher Functions
list
6.1.21.1 General Operational
Requirements
Private Call
5.5 Private Call
6.1.1 1-to-1
6.1.10.1 Full Duplex Call
Follow on Proceed
Talker ID
5.7 Talker ID
6.2.4 Identification and
location information
6.2.6
Membership/affiliation
list
6.1.7.2 Multiple PoC Clients
with same PoC Address
6.1.9.2 Invited Party
Identification Information
6.1.21.2 Identity
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
PCPS Feature
PCPS Gap
• Created by PoC Subscriber
• PoC Service Provider creates on
behalf of PoC Subscriber
• Any selected PoC User
• PoC User can be in more than one
group
• XDM
• one-to-one half duplex session
• Follow on full duplex voice call
• UE and user membership
• Affiliation
• Revoke of affiliation
• MSISDN, SIP URI and display
name
• Multi-device one PoC address
• Available during a group session
• Hidden PoC address
• Use for incoming barring
• Personality
• Alias ID vs display name
• Is private call two-way full
duplex?
• Authorization for private call
OMA-TP-2014-0177
Slide #5
[OMA-Template-WIDpresentation-20130101-I]
Summary Table
MCPTT
Requirement
Security
MCPTT RD
section
PCPS RD section
PCPS Feature
PCPS Gap
6.19 Security
6.1.36 Security
• Mutual authentication
• Secure transport on signaling and
speech
• PoC interaction log
• Signaling integrity
• No details on cryptographic
operations
• suspending or disabling
service access
Priority
6.1.3 Override
6.15 Priority
6.1.14 Quality of Experience
6.1.23 Multiple Group
Operation
• 4 levels of QoE profiles
• Specific for Government Official
Use profile with multiple level of
priorities
• Primary and secondary
• Pre-emption
• 3GPP TR 22.950 support
• Map to EPS
• Both overriding and overridden
transmission
• By call type
• Change priority while call in
progress
• Emergency Call
• Imminent Peril
• Emergency Alert
Roaming
6.22.2 Application
Layer roaming and
Interworking
6.1.21.7 Service Mobility
6.1.37.2 Roaming Charging
6.2 Overall System
• Initiate or respond to PoC services
• Possible limiting some PoC
capabilities
• [?] Performance may need
local breakout
• Affiliation with visiting group?
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TP-2014-0177
Slide #6
[OMA-Template-WIDpresentation-20130101-I]
Summary Table
MCPTT RD section
PCPS RD section
MCPTT
Requirement
Interworking 6.23 Interworking with 6.1.15 PCPS Interworking
Performance
Location
non LTE MCPTT
Service
systems
6.14 Audio MCPTT Call 6.1.13 Performance
Performance
6.18 Location
7.5 Location
Audio / Voice 6.14.3 Audio/Voice
Quality
Quality
PCPS Feature
• External P2T networks
•
•
•
•
•
RtS response time
StS time response
End-to-end channel delay
Voice quality
Turn around time
Not covered
6.1.13 Performance General
Objectives
Off Network
7 Off Network Use
Not covered
Broadcast/M
ulticast
5.2 Broadcast Group
Call
6.6 Broadcast Group
6.1.12 Multicast
6.1.28 Enterprise/Corporate
Environment
6.1.36.1 Multicast/Broadcast
Security
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
PCPS Gap
• No interworking with MCPTT
• With 70% load
• Late call entry performance
• OMA LOC Enabler
MOS >= 3 under nominal network
conditions
• Interworking with non-MCPTT
• Noise reduction
• Not Covered
• eMBMS over LTE
• Geographic area support
• Group hierarchy
OMA-TP-2014-0177
Slide #7
[OMA-Template-WIDpresentation-20130101-I]
Conclusions
PCPS supports most of the MCPTT requirements though enhancements are needed
• PCPS QoE needs further development to support MCPTT priority requirements using the
Government Official Use profile
• PCPS eMBMS needs to evolve to support MCPTT requirements
• Major features missing from PCPS are:
•
authorization to both UE and Application (user); difference in actors
• group hierarchy and group affiliation
• personality management
•
location (could be supported by OMA LOC enabler)
• off Network (ProSe Relay) support
• late call entry performance
• ability to forward support of new security evolution
•
•
interworking with non-LTE MCPTT systems (P25, TIA-603 etc.)
• Further analysis is needed to identify in detail how PCPS can be used
to support MCPTT
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TP-2014-0177
Slide #8
[OMA-Template-WIDpresentation-20130101-I]
Analysis Sources
PCPS 1.0 RD
http://member.openmobilealliance.org/ftp/Public_documents/COM/COMPCPS/Permanent_documents/OMA-RD-PCPS-V1_0-20140722-D.zip
MCPTT (TS 22.179)
http://www.3gpp.org/ftp/Specs/archive/22_series/22.179/22179-060.zip
© 2014 Open Mobile Alliance Ltd. All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TP-2014-0177
Slide #9
[OMA-Template-WIDpresentation-20130101-I]