1 / 25

OMA-TP-2014-0184 OMA MC Workshop PCPS WA Presentation

Submitted To: MC Workshop Date: 26 August 2014 Availability: Public OMA Confidential Contact: Jerry Shih, AT&T Source: OMA PCPS WA. OMA-TP-2014-0184 OMA MC Workshop PCPS WA Presentation. X.

sharla
Download Presentation

OMA-TP-2014-0184 OMA MC Workshop PCPS WA Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Submitted To: MC Workshop Date: 26 August 2014 Availability: Public OMA Confidential Contact: Jerry Shih, AT&T Source: OMA PCPS WA OMA-TP-2014-0184OMA MC WorkshopPCPS WA Presentation X 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.

  2. PCPS WID

  3. Work Item Title and Registration Name

  4. Supporting Companies The companies supporting this work item are:

  5. Description and Objectives (1) • Work Area: • This Work Item is the first in a series of Work Items intended to deliver a complete set of Push-to-Communicate for Public Safety (PC_PS) application and service layer standards (for voice and data). Hence “PC_PS ”. As such, this work item will have a very limited scope, serving as a limited OMA PoC Enabler Update from current version of PoC v2.1 with no specific Public Safety requirements because specific Public Safety requirements will be covered by future WIDs. • Issues this Work Item aims to solve: • PC_PS v1 – Update PoC v2.1 to support 3GPP Release 12 LTE and relevant key features based upon completed 3GPP requirements up through Release 12, in preparation of future upgrades from PC_PS v1 to be aligned with 3GPP Public Safety Requirements in subsequent 3GPP Releases. • This update (PC_PS v1) will be synchronized to 3GPP Release 12, but excluding: • Group Communication System Enablers for LTE (GCSE_LTE) • Proximity Services (ProSe) • This update (PC_PS v1) will be synchronized to 3GPP Release 12, and shall include: • Update PoC v2.1 SIP/IP Core operations to align with 3GPP Release 12 LTE architecture • Adapt PoC v2.1 Multicast (currently using MBMS over UTRA) to use eMBMS over LTE • Objectives • OMA will develop application and service layer standards in a synchronized manner with 3GPP. This Work Item is the first in a series of Work Items for PC_PS. This work item is in preparation of future PC_PS Work Items which take use cases based on harmonized global Public Safety requirements. • Note: OMA does not intend to generate Public Safety (PS) broadband requirements for PC_PS. Rather it is expected that 3GPP will collect and consolidate such inputs from government authorities (e.g., FirstNet and UK Home Office who have indicated a preference to coordinate via 3GPP for a set of globally harmonized requirements). • OMA intends to create PC_PS application and service layer technical specifications driven by Public Safety requirements developed by 3GPP • Example: It is anticipated that 3GPP Release 13 will define requirements for “Mission Critical Push-to-Talk over LTE” through direct member participation in 3GPP while drawing inputs from other relevant SDO/FORA (e.g., FirstNet, UK Home Office, US NPSTC, TCCA, APCO, ETSI EMTEL and other Public Safety related organizations around the world).

  6. Description and Objectives (2) • Market benefits: • Mobile Network Operators will be able to provide Push-To-Communicate voice and data application services for both Mission Critical Public Safety (or Public Protection and Disaster Relief PPDR) and Critical Communications Enterprise markets that operate across multiple 3G, 3.5G, 4G, WiFi, Satellite, etc. Technologies.Additionally, as PoCv2.1 predates LTE, update of this OMA Enabler is timely for the wireless industry. • Time to market: • PC_PS v1 – Align PoC v2.1 to 3GPP Release 12 using current PoC v2.1 PTT, etc. services (e.g., PC_PS v1) • October 2014 • * PC_PS v 2, 3, 4, ... – Enhance PC_PS v1 to fully support Public Safety in 3GPP Releases 13, 14, 15 • * Separate WIDs for each of these subsequent PC_PS releases is outside the scope of this WID • Expected market acceptance: • Global market deployments of PoC for Public Safety are expected to follow globally coordinated Public Safety broadband definition and deployment efforts (currently led by U.K and U.S. government authorities via 3GPP) • Complexity: • PC_PS v 1, 2, 3, 4, ...: Level of complexity1 will vary with each release; however previous efforts invested in OMA PoC Enabler v1.0, v2.0 and v2.1 afford considerable body of design knowledge in PTT over Cellular (PoC) networks that was contributed by a majority of industry experts in this field (from 2003 – 2011) from which PC_PS can draw • Uniqueness: • No global Push-To-Communicate for Public Safety application standards exist that are built upon all-IP and SIP infrastructures which can be instantiated and operate across multiple 3G, 3.5G, 4G, WiFi, Satellite, etc. wireless technologies Note 1: POC V2.1 comprises of 10 Specs and 19 Supp Docs

  7. Description and Objectives – Informative • This page is informative only. It describes the Objectives and Deliverables of future PC_PS releases. Each PC_PS release will be kicked off with a separate WID. • Considerations for Future Deliverables • Deliverables for Public Safety will be done over multiple PC_PS releases to synchronize with other SDOs in order to optimize the use of collective resources and avoid fragmentation and duplicate efforts. • OMA will work with other SDOs, as required, to achieve OMA PC_PS interoperability with legacy PS narrowband radio systems to support the 3GPP defined global PS requirements. • Issues for future PC_PS Work Items: • PC_PS v2 shall be aligned with 3GPP Releases 12 and 13 with respect to Public Safety Support; e.g.,: • Support Public Safety enhancements, features, applications, services, etc. as agreed in 3GPP Releases 12 and 13 use cases & requirements • Update PC_PS to align with other Public Safety relevant OMA enablers (e.g., Presence, XDM, CPM and Network APIs) to address the evolved PoC service environment while applying lessons learned from commercial deployments of OMA PoC • PC_PS v 3, 4, 5,... shall be aligned with 3GPP Release14, etc. ... with respect to Public Safety support; e.g., : • Support Public Safety enhancements, features, applications, services, etc. as agreed in 3GPP Release 14, 15, ... use cases & requirements

  8. Main Use Cases (1 – functional requirement examples) • PC_PS v1 to be optimized for LTE • PC_PS v1 to function across multiple types of wireless technologies (including 3GPP/3GPP2 3G/3.5G/4G, WiFi, Satellite, ...) • PC_PS v1 to function agnostically across multiple types (commercial, private, public) and/or combinations of spectrum bands (as regulated within each country) in accordance with the underlying radio technology specifications • This box is INFORMATIVE only. It shows the Use Cases (functional requirement examples) of a future PC_PS release. Each PC_PS release will be kicked off with a separate WID. • PC_PS v2 to support Group Communication System Enablers for LTE (GCSE_LTE) for Public Safety • PC_PS v2 to support Proximity Services (ProSe) for Public Safety • PC_PS v2 to interwork/interconnect with existing TETRA, P25 and other Public Safety narrowband networks (PoC Interworking Service) • PC_PS v2 to incorporate additional Public Safety broadband functionality

  9. Main Use Cases - Informative(2 – Future global Public Safety broadband) 3GPP Perspective [http://www.3gpp.org/Public-Safety, July 2013]: • Publicsafety users (i.e., first responders, fire fighters, law enforcement, terror incident & natural disaster response, emergency medical care, airport operations, etc.) are an important community both economically and socially but the market for systems based on public safety standards is much smaller than for commercial cellular. Specialised public safety and critical communications technology cannot attract the level of investment and global R&D that goes in to commercial cellular networks. Establishing common technical standards for commercial cellular and public safety offers advantages to both communities: • the public safety community gets access to the economic and technical advantages generated by the scale of commercial cellular networks, and • the commercial cellular community gets the opportunity to address parts of the public safety market as well as gaining enhancements to their systems that have interesting applications to consumers and businesses. • A strong standards-based approach will ensure interoperability between vendors leading to a competitive equipment market. • The U.S. National Public Safety Telecommunications Council (NPSTC) and other organizations recognized the desirability of having an interoperable national standard for a next generation public safety network with broadband capabilities. With NPSTC, TCCA, ETSI Technical Committee TETRA and other organizations backing LTE there is now a clear global consensus that LTE will be the baseline technology for next generation broadband public safety networks. U.S. First Responder Network Authority (FirstNet) Perspective [http://www.ntia.doc.gov/page/about-firstnet]: • Using a nationwide spectrum license, FirstNet will provide a single platform for daily public safety communications. When natural disasters, threats to national security, or other emergencies occur anywhere in the country, FirstNet will enable local, state, regional and national emergency responders to communicate at the direction of the incident commander. • FirstNet will be built to public-safety grade standards using Long-Term Evolution (LTE) wireless technology, the most advanced available today. FirstNet will deliver greater coverage, capacity, connectivity, cybersecurity and resiliency than the current multiplicity of diverse public safety wireless systems. • Police, firefighters and emergency medical service personnel will still rely on their land mobile radio (LMR) networks for mission-critical voice with FirstNet providing high-speed data, supplemental commercial grade voice and eventually mission-critical LTE voice. FirstNet also will support the integration of LMR networks, even after LTE voice is provided.

  10. NOTE: This logical use case description provides informational material to assist OMA members to better understand future Public Safety Broadband Use Cases (note that this is not a presumed architecture). Main Use Cases - Informative (3 – Future logical Public Safety broadband landscape) P25 Network OMA PoC SIP/IP Core** TETRA Network Application Server(s) PTC Other Msg. Video Broadband Consoles Other PS NB Network Satellite / Deployable Network Government Agency Network * 3GPP R12 GCSE ** Could be IMS Enterprise / other Network * * 3GPP/3GPP2 3G, 3.5G or 4G Network Technologies MuSe / eMBMS EPC 3GPP R12 GCSE Reference Architecture 3GPP Relay Direct Mode Apps Direct Mode Apps Client App 3GPP R12 ProSe ProSe ProSe

  11. Planned deliverables • Requirements & Architecture: • Phase 1 – Align PoC v2.1 to 3GPP Release 12: • Output: PC_PS v1 Requirements and PC_PS v1 Architecture • Phases 2, 3, 4, ...* – Enhance PoC to fully support 3GPP Release 13, 14, 15, ... Public Safety features • Output*: PC_PS Phase 2, 3, 4, … Requirements and PC_PS Phase 2, 3, 4, … Architecture • * Separate WIDs for each of these subsequent PC_PS releases is outside the scope of this WID • Technical Specifications: • Phase 1 – Align PoC v2.1 to 3GPP Release 12: • Output: PC_PS Phase 1 Specifications and Sup files • Phases 2, 3, 4, ...* – Enhance PoC to fully support 3GPP Release 13, 14, 15, ... Public Safety features • Output*: PC_PS Phase 2, 3, 4, … Specifications and Sup files • * Separate WIDs for each of these subsequent PC_PS releases is outside the scope of this WID

  12. Current Schedule

  13. Slides from RDFeatures/Functions Highlights

  14. Actors in PCPS (PoC)

  15. Actors Transition in PCPS

  16. PoC Group • 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 Operation • 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

  17. Floor Control • Request Rights to Speak • granted, denied • Floor availability • Finish speaking, about to speak, forced to release, • 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

  18. Session Priority and Pre-emption • Supported with QoE; user starts session with appropriate QoE profile • QoE Profiles: • Basic • Premium • Professional • Official government use with multi-level priorities • Support 3GPP 23.107 Levels of Priority • Primary and secondary groups • Crisis Handling Management; separated from other group sessions • Pre-emption based on QoE and Priority • Dispatcher over Fleet member • Transmission has higher priority over Reception

  19. Security • Mutual Authentication before service interactions • Speech communication and signaling transmitted in a secure manner • Log all PoC service interactions • Integrity of PoC signaling • Anonymous (hide user ID) and user ID protection • Multicast/Broadcast security • Interworking security

  20. Roaming and Interworking • Support Interworking with External P2T Networks • Support Remote Access Users • Support Roaming

  21. Other PoC Features/Functions • Support additional media types: Images, live video, file transfer, external media sources • Full Duplex Call Follow-on Proceed • Multicast, Broadcast • Instant Personal Alert • Presence • PoC Box with security • Operator Specified Warning Message • Browser-Based Client Invocation • Lawful Interception • Manual and Auto answer mode • Charging requirements

  22. Slides from ADPCPS/PoC Architecture

  23. Architecture Model

  24. Relationship Among Major Functions

  25. Interworking Supports

More Related