E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

1

Mission Critical ApplicationProgress in 3GPP

David Chater-LeaMotorola Solutions UK Ltd

Vice Chairman, 3GPP SA6

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

2

Organizational Partners (SDOs)

• Regional standards organizations:

Market Representative Partners

• 14 Market partners representing the broader industry:

Partnership

• 4G Americas, • COAI (India), • GSA, • GSMA, • IMS Forum, • InfoCommunication

Union (Russia),• IPV6 Forum,

• MDG (formerly CDG), • NGMN Alliance, • Small Cell Forum, • TCCA, • TD Industry Alliance, • TD-Forum, • UMTS Forum

• ARIB (Japan), • ATIS (USA), • CCSA (China),

• ETSI (Europe),

• TTA (Korea), • TTC (Japan), • TSDSI (India)

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

3

Developing internetprotocol specs

ITU-R/TDeveloping Mobile application specs

Referring to 3GPP specs(contributed by individual

members)

Partners of 3GPPReferring to 3GPP specs for

the local specs

Referring to specs

Cross referenceDeveloping Wireless

LAN/MAN specs

Requirements

Input specs

JapanEU Korea China North America

MarketPartners

Developing Recommendations

Terminal Certification

Terminal certification based on 3GPP specs

Cross reference of specs

The 3GPP Eco-system

India

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

4

• ~400 Companies from 39 Countries• 50.000 delegate days per year• 40.000 documents per year• 1.200 specs per Release• New Release every ~18 months

3GPP Facts and Figures

0

5000

10000

15000

20000

25000

1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015

Change Requests

Total CRs each year

R99R4 R5 R6 R7 R8 R9 R10 R11

R12

R13

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

5

ServicesThe Core networkRadio Interfaces

Whole System Approach

All-IP network

Improved security

Support of non-3GPP accesses

Greater device diversity

More IMS applications

Greater session continuity

Higher data throughput

Lower latency

More spectrum flexibility

Improved CAPEX and OPEX

Legacy

Interworking

Mission Critical Applications (from January 2015)

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

6

TSG RANRadio Access Network

RAN WG1Radio Layer 1 spec

RAN WG2Radio Layer 2 spec

Radio Layer 3 RR spec

RAN WG3lub spec, lur spec, lu spec

UTRAN O&M requirements

RAN WG4Radio Performance

Protocol aspects

RAN WG5Mobile Terminal

Conformance Testing

RAN WG6GSM EDGE

Radio Access Network

TSG SAService & Systems Aspects

SA WG1Services

SA WG2Architecture

SA WG3Security

SA WG4Codec

SA WG5Telecom Management

SA WG6Mission-critical applications

TSG CTCore Network &

Terminals

CT WG1MM/CC/SM (lu)

CT WG3Interworking with external networks

CT WG4MAP/GTP/BCH/SS

CT WG6Smart Card Application

Aspects

Project Co-ordination Group (PCG)

SA WG6Mission-critical applications

Decision to form a new group for mission critical

applications was made at a joint OMA-ETSI-3GPP

meeting in Montreal in August 2014

Terms of Reference for SA6, and an accompanying

interpretation, agreed at SA Plenary in December

2014

SA6 is responsible for ‘stage 2 architecture’• Downstream groups responsible for detailed protocol work

First meeting January 2015; chairman elected at

second meeting in February 2015.

Current officers:• Chairman:

Yannick Lair (LG Electronics) – newly elected in January 2016

• Vice chairmen:

David Chater-Lea (Motorola Solutions) &

Suresh Chitturi (Samsung)

8 meetings held during 2015• Between 50 and 150 signed up attendees

MCPTT Stage 2 Technical Specification approved

at 3GPP SA plenary meeting in December 2015

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

7

3GPP Process

Identity management

client

MCPTT-1

CSC-1

CSC-2

CSC-3

Common services core

Floorcontrol server

Floorparticipant

MCPTT-4

Group management

client

Identity management

server

Group management

server

CSC-4 Configuration management

client

Configuration management

server

Interworking function to

legacy system

IWF-1

MCPTT-3Other MCPTT server

MCPTT server

MCPTT clientMCPTT-5

Media distribution

function

MCPTT UE

Media mixer

MCPTT-7

MCPTT-8

MCPTT-6

EPS

MCPTT user database

MCPTT-2

MB2C

Rx

CSC-5

Other group management

server

CSC-7

MCPTT-9

CSC-6

Key management

client

CSC-8Key management

server

CSC-10

CSC-9

CSC-13

Stage 1:

Requirements

Stage 2:

Architecture

Stage 3:

Protocols

SA1

• Requirements normally

come from operators

(MNOs)

• High public safety

presence from Europe

and USA for Mission

Critical applications

SA6

• Mission Critical application

architecture

SA3

Security architecture and

protocols

SA2

• Overall LTE (2G, 3G etc)

system architecture

Working groups involved in Mission Critical standardisation:

CT1

• Core protocols

CT4

• Database aspects

SA3

• Security protocols

SA4

• Codec and multicast

aspects

Work is completed in Releases of typically 15 – 18 months

New specifications issued at the completion of each release

Change requests then make corrections as needed

+ RAN groups for radio

specifications

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

8

MCPTT – Mission Critical Push to Talk

Voice services similar to existing radio systems• Private call• Group call• Broadcast call• Regrouping

Stage 3 completed and approved March 2016• There is now a complete suite of Release 13 specifications for

MCPTT

840 requirements in Stage 1• 70% covered in Release 13• 10% part covered in Release 13• 20% not covered in Release 13

Further requirements will be satisfied in following releases:• Some aspects of group call and group management• Call back• Ambient listening• Interworking between systems• Interworking with non-MCPTT systems (PMR/LMR)• UE to UE relay• Enable/disable

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

9

MCData – Mission Critical Data

Mission critical data service • Prioritisation• Group services• Connected to user organisation, not MNO/Internet

Simple messaging• Analogous to TETRA Short Data• Supports messaging and other applications

StatusFile distribution• User and group based service

Data streamingPoint to point IP connectivityPerformance suitable for remote control applications (robots, drones etc)

Progress: in requirements phase (stage 1)• Part of Release 14• Requirements phase to be complete June 2016• Release complete ~ March 2017

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

10

MCVideo – Mission Critical Video

Mission critical video service • Performance – latency etc• Prioritisation• Group services

Interoperable – does not replace other video applications, but ensures compatibility, e.g. during mutual aid etcReal time and non real time‘Push’ and ‘Pull’Standardised video codec(s) for interoperability• Control of resolution, frame rate etc

Support for camera control protocolsRobots and dronesOn and off-network (Direct Mode)

Progress: in requirements phase (stage 1)• Part of Release 14• Requirements phase to be complete June 2016• Release complete ~ March 2017

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

11

MCCore – identification of common requirements

Recognition that many aspects of mission critical service are common across all applications (speech, video etc)

• Identification of users and groups

• Group and broadcast communications

• Including affiliation, late entry to calls etc

• Prioritisation of services

• Security

May lead to common requirements and interfaces for future mission critical applications

Progress: in requirements phase (stage 1)

• Part of Release 14

• Requirements phase to be complete June 2016

• Release complete ~ March 2017

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

12

Release timescales

3GPP specifications are published in a series of Releases

• Each Release provides as full a set of specifications as time and resource permits

• Following releases add further functionality

• Change requests used to make corrections once a release has been finalised

Release timing is agreed at the start of each release

• Release 13: Stage 3 complete March 2016

• Release 14: Stage 3 complete June 2017

• Release 15: TBA, likely late 2018

• Release 16: TBA, likely end 2019/early 2020

• In time for ITU IMT-2020 selection of specifications

Product availability is determined by market demand, not 3GPP!

• Often around 18 months – 2 years following a release

• Some new functions can be compatible with existing devices, others need new devices

• E.g. for ProSe (Direct Mode), chipsets and filters in devices are affected

SCOPE

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

13

Future specifications

New requirements for each release are specified in SA1

To take part in the process, get involved – or ensure your needs are represented

• Various government agencies take part already, more are welcome

Market representation partners such as TCCA can also speak for market needs

• NOTE: Committing requirements to specifications needs 3GPP member contributions at

meetings

E E N A C o n f e r e n c e 2 0 1 6

© 3GPP 2012

14

www.3gpp.org

For more Information:

contact@3gpp.org

Search for WIDs at http://www.3gpp.org/specifications/work-plan and http://www.3gpp.org/ftp/Information/WORK_PLAN/ (See excel sheet)

Presenter: david.chater-lea@motorolasolutions.com