Project 25 Foundations · codan radio (formerly daniels) dva consulting dvsi ef johnson etherstack federal engineering, inc 5 x 9 communications futurecom systems genesis group harris

March 20161Project 25 Technology Interest Group

International Wireless and Communications ExpoCollege of Technology Las Vegas, Nevada

March 21, 2016

Project 25 Foundations System Technology Updates for 2016

Presented by:PTIG - The Project 25 Technology Interest Group

www.project25.org – Booth 764

http://www.project25.org/


Program Participants

• Moderator

– Steve Nichols: Director, PROJECT 25 TECHNOLOGY INTEREST GROUP

• Panelists

– Neil Horden, Chief Consultant, FEDERAL ENGINEERING

– Jim Holthaus, Vice President Project 25 Solutions, RELM

– Nick Pennence, Vice President, ICOM AMERICA

– Bill Janky, Director System Design, HARRIS CORPORATION

– Doug Chapman, Vice President, Business Development, ETHERSTACK

– Andy Davis, Senior Resource Manager, Project 25 MOTOROLA SOLUTIONS

– Cheryl Giggetts, Senior Vice President, AECOM


Steve Nichols

Director, Project 25 Technology Interest Group

Welcome, Panel Agenda PTIG: Who We are and What we do.

Niel Horden

Chief Consultant, FEDERAL ENGINEERING

P25 Standards Process, Overview, Interfaces, Interoperability

examples using the Interfaces

Jim Holthaus

Vice President Project 25 Solutions, RELM

Conventional System Configurations and Wireline Interfaces for

Project 25.

Nick Pennance

Vice President, ICOM

Trunking System Configurations and Wireline Interfaces for Project

25.

Bill Janky

Director System Design, HARRIS

P25/LTE evolution and interface, P25 Auto Roaming User Id

Management

Doug Chapman

Vice President, Business Development,

ETHERSTACK

ISSI and CSSI capabilities and interoperability

Andy Davis

Senior Resource Manager, Project 25

Standards, MOTOROLA SOLUTIONS

P25 Standards 2015-2016 update, Project 25 CAP testing, CAP FAQs,

P25 Capabilities Matrix

Cheryl Giggetts

Senior Vice President, AECOM

Project 25 Products and Services Available. P25 Market acceptance.

All Question and Answer Session

Agenda


• What P25 resources are available through PTIG

• P25: A Suite of Standards, the Process, why P25 is user driven

• P25 Interfaces defined with examples of P25 Conventional and Trunking systems configurations.

• A P25 Standards update: recently released documents and future priorities

• P25 Network Interfaces and Interoperability: ISSI, CSSI, FSI

• How P25 LMR and PS LTE can work together

• The Reality of Multiple Vendor Interoperability with P25

• A look at P25 in the Market, Products and Services available

Take Away Topics To Look For


PTIG?What we Do, and Who we Are.


What do we do:

– Provide a forum for users and manufacturers

– Manage education and training on Project 25

– Create and distribute Project 25 information

– Support the TIA standards process

– Offer Users access to the standards process without the rigor of TIA membership

– Maintain a “neutral ground” among the competing manufacturers and providers

And…

– Present Classroom Training and Panels such as THIS SESSION.

Project 25 Technology Interest Group



Who we are:

– Supporters of Project 25 technology, nurturing Project 25’s adoption, growth, and expansion

– A venue fostering an atmosphere encouraging Users to contribute to and benefit from a close interaction with the vendor community driving the on-going development of the Project 25 Standards

Set your browser to www.project25.org


Project 25 Technology Interest Group: Founding Member

Project 25 Technology Interest Group: Sustaining Members


Project 25 Technology Interest Group: Commercial Members

NICATION


Project 25 Products and Services Available

PTIG Member Organizations

www.Project25.org Fix

ed

Sta

tion

s &

Rep

eate

rs

Mob

ile

&

Port

ab

le

Rad

ios

Pag

ers

Veh

icle

Rep

eate

rs

Con

sole

s

Net

work

s

Soft

ware

Tes

t

Eq

uip

men

t

Sy

stem

s

Inte

gra

tion

Con

sult

an

t

Ser

vic

es

AECOM

AIRBUS DS COMMS

AVTEC

BAI (FORMERLY AIRWAVE)

CATALYST

CISCO

COBHAM

CODAN RADIO (FORMERLY DANIELS)

DVA CONSULTING

DVSI

EF JOHNSON

ETHERSTACK

FEDERAL ENGINEERING, INC

5 x 9 COMMUNICATIONS

FUTURECOM SYSTEMS

GENESIS GROUP

HARRIS CORPORATION

ICOM AMERICA

IDA CORPORATION

JVC KENWOOD

MIDLAND RADIO

MOTOROLA SOLUTIONS

PANTEL INTERNATIONAL

POWERTRUNK (TELTRONIC)

RELM WIRELESS

SIMOCO

SPECTRA ENGINEERING

STANDARD COMM PTY LTD - GME

TAIT COMMUNICATIONS

TECHNISONICS

TELEX RADIO DISPATCH (BOSCH)

TIMCO ENGINEERING

UNICATIONS USA

VERTEX STANDARD

ZETRON

35 15 13 1 4 12 15 6 4 17 7


WWW.Project25.org


Project 25 Technology Interest Group (PTIG)

Documents available at www.Project25.org

• P25 Frequently Asked QuestionsWritten to officer, firefighter (non technologist) level

• P25 Updated Capability Guide Added Infrastructure interfaces and links to Statement of Requirements. Remains the best tool for managing P25 features and capabilities for system planning and RFP development

• P25 Standards Update SummarySummary of the latest TIA TR-8 P25 Standards Meetings with user benefits defined

• P25 Steering Committee Approved List of StandardsUpdated from the most recent P25 Standards meeting

• P25 Feature Translator link to NPSTC PAM tool



Project 25 Technology Interest Group (PTIG)

New Documents available at www.Project25.org

• New White paper: P25 Automatic Roaming A detailed description of Automatic and Manual Roaming capability for Project 25 systems.

• P25 System of the Month Each month a new Project 25 system is featured describing the system, coverage, agencies served, interoperability achieved and other unique details of this application of Project 25 technology.

• New White Paper: Is Project 25 Public Safety Grade?Project 25 has been defined since it’s inception by requirements from the Public Safety User Community. The result is a Suite ofStandards with well defined features, capabilities, and interoperable interfaces applied in over 700 Public Safety Systems across the US today.

Projects Underway 2016;

• New entries for International P25 systems and USA P25 Conventional will be added to the P25 Master System listing. This resource will be expanded to include P25 systems beyond the systems currently listed for the USA, Australia, Canada, NewZealand, and the UK.


PROJECT 25 TECHNOLOGY

INTEREST GROUP

Visit PTIG in Booth # 764 IWCE 2016

OUR MEMBER ORGANIZATIONSAS EXHBITORS ALSO

SAY

THANK YOU

PROJECT 25

Technology Interest Group

MEMBERS EXHIBITING

Booth Number

• AVTEC 935

• CATALYST COMMUNICATIONS TECHNOLOGIES 1752

• CISCO 755

• COBHAM (Aeroflex) 1055

• CODAN RADIO COMMUNICATIONS 1857

• EFJOHNSON TECHNOLOGIES 1229

• ETHERSTACK 755

• FUTURECOM SYSTEMS 1021

• GENESIS GROUP 1741

• HARRIS CORPORATION 1455

• ICOM AMERICA 1465

• IDA CORP 1065

• JVC KENWOOD 1229

• MOTOROLA SOLUTIONS 1029

• POWERTRUNK 1829

• PROJECT 25 TECHNOLOGY INTEREST GROUP (PTIG) 764

• RELM WIRELESS CORP 1255

• SIMOCO 1149

• TAIT COMMUNICATIONS 943

• TELEX 955

• TIMCO ENGINEERING 922

• UNICATION 2351

• VERTEX STANDARD 1039

• ZETRON 1429

SUSTAINING MEMBERS

FOUNDING MEMBERS


Project 25 Standards UpdateThe Standards Process, The Interfaces, and Interoperability

Neil Horden

Chief Consultant

Federal Engineering, Inc.

Sponsored by:


• Origins and History of P25

• The Goals of P25

• The Standards

• Interoperability

• P25 Meeting it Goals

• The Continuing Evolution of P25

Project 25 Introduction: Topics


• FCC mandating improvements in VHF/UHF efficiency

• Opening of 800 MHz band

• FCC announces plans for new trunking spectrum

• First seen as a new “Community Repeater”; - then Public Safety adoption

• Many proprietary implementations of APCO Project 16

• Public Safety organizes to support standards

• Voice processing and advances in digital technologies and modulation techniques offer new opportunities

• The Federal Government joins the movement

• Growing emphasis on encryption and data

1980s LMR EnvironmentLeading to the Creation Project 25


October 1989:

The Association of Public-Safety Communications Officials (APCO), The National Association of State Telecommunications Directors (NASTD), The National Communications System (NCS), The National Telecommunications and Information Administration (NTIA), The Department of Defense (DoD), The National Security Agency (NSA)

Agree to the Creation of;APCO – NASTD – FED Project 25(later shortened to Project 25)

Project 25 Established:Broad Support Found


• To create a digital radio standard for public safety that:– Uses radio spectrum efficiently

– Is interoperable

– Can by provided by multiple vendors

– Is easy to use

• This standard technology should be:– Frequency independent

– Should be compatible with existing equipment

– Enable gradual migration from existing systems

– Offer coverage as close as possible to existing analog coverage

– Able to integrate both voice and data

Project 25: The Goals


But, much more than a single standard

• P25 is a suite of standards

• Air Interfaces and Wireline Interfaces

P25: The Standard


The P25 Standard is not one document• It is a suite of over 85 standard documents and

over 25 TIA Telecommunication Systems Bulletins.

– Over 125 documents have been developed and published supporting the Project 25 suite of standards and features

• The P25 suit of standards defines– The system interfaces of P25

– The services offered by P25

• Dividing the P25 system up into defined standardized interfaces allows manufacturers to develop products specific to their areas of expertise

– Allows users to buy products that best meet their specific needs

– Enables the goal to provide users the flexibility to choose from various manufacturers’ offerings to build out their P25 systems

• P25 Documentation Suite Overview (TSB-102-B) describes how the users and manufacturers envision the P25 system

Project 25: A Suite of Standards


Project 25: Interfaces & Services

AUTHENTICATION

TRUNKING

AIR

INTERFACES

SECURITY

INTERFACESWIRELINE

INTERFACES

ISSI/CSSI

P25 FDMA

COMMON AIR

INTERFACE

TRUNKING

Voice/Data

CONVENTIONAL

Voice/Data

P25 TDMA

COMMON AIR

INTERFACE

TRUNKING

Voice

NETWORK

MANAGEMENT

KEY FILL

INTER- KMF

KMF KMF

DATA

SERVICES

DATA

INTERFACES

SUBSCRIBER

DATA

PERIPHERAL

INTERFACE

OTAR

KMF

DATA NETWORK

INTERFACE

Gateway

FSI

Conventional

Analog/Digital

Voice/Control

TRUNKING

Voice/Data/Control

CONVENTIONAL

Voice/Control

SECURITY

SERVICES

ENCRYPTION

Voice/Data

LOCATION

Gateway

TIER 1

Conventional

TIER 2

Trunking/Conventional

TRUNKING/CONVENTIONAL


P25 Interfaces

Not shown are encryption key

management, network management and

telephone interconnect interfaces

Fixed

Station

RF Subsystem B (Trunked RFSS)

RF Subsystem A (Trunked RFSS)

Eg

Ec

RF Subsystem C (Conventional RFSS)

Data Interface Data Interface

AA

Ef

Conventional

Digital Fixed Station Interface

DFSI

FS

P25 FDMA

Conventional CAI

Common Air Interface

P25 FDMA

Trunked CAI


Trunked

Console Sub System

Interface

CSSI

Inter Sub System Interface

ISSI Console Sub-

System (CSS)

Repeaters

P25 TDMA

Trunked CAI



• Interoperability is reliant on a common standard

– Within the system almost any standard will do, but between interoperability partners, a common standard must be selected

• Multiple agencies sharing a system

• Multiple jurisdictions cross sharing systems

• Multiple regions requiring transient operations

• Why P25 as the common standard

Standards and Interoperability


• The only user defined public safety standard

• Widely implemented across public safety

• Supports all operating modes

– Simplex, Repeater, Trunked

• A living standard that grows with technology

Why P25 as the common standard


• Technical barriers

– Standards

– Frequency Bands

– Common programming templates

• Compatible ID plans, etc.

• Operational barriers

– Operating Procedures

– Planning

Barriers to interoperability


Interoperability in Action

Fixed

Station



Eg

Ec

RF Subsystem C (Conventional Station,

Base or Repeater)

Data Interface

E

Conventional

Digital Fixed Station Interface

DFSI

FS

P25 FDMA

Conventional CAI


P25 FDMA

Trunked CAI


Trunked

Console Sub System

Interface

CSSI

Inter Sub System Interface

ISSI

Repeaters

P25 TDMA

Trunked CAI



P25 from Phase 1 to Phase 2


Ec

P25 FDMA

Conventional CAI

Common Air InterfaceP25 FDMA

Trunked CAI


Trunked

Console Sub System

Interface

CSSI

Repeaters

P25 TDMA

Trunked CAI


1

BR

2 1 1 1

Fixed

Station


Base or Repeater)

FS1

BR

2


Phase 1 and Phase 2 Interoperability


Ec

P25 FDMA

Conventional CAI

Common Air InterfaceP25 FDMA

Trunked CAI


Trunked

Console Sub System

Interface

CSSI

Repeaters

P25 TDMA

Trunked CAI


1 1 1 1

Fixed

Station


Base or Repeater)

FS

BR

1/2

BR

1/2

BR

1/2

BR

1/2


Compliance Assessment Program (CAP)

• P25 CAP testing ensures that there is a choice

– Multiple vendors subscriber equipment is tested on Multiple vendor Networking equipment

• Provides a mechanism for P25 equipment suppliers to formally demonstrate their products' compliance

– Testing a key subset of the P25 Standards

– Performed in CAP recognized labs

• CAP results

– After testing SDOCs and STRs are approved by the DHS

P25 Compliance Assessment


• Designed for public safety by public safety

• Developed in partnership between Public Safety and TIA– Project 25 formed in 1989

– Initial standards released in 1995

– Ongoing Development and Evolution

• P25 is a suite of mobile radio standards and bulletins which define interoperable communications for emergency services

• The result? – True multi-source procurement and interoperability

– Smooth migration from analog while retaining backwards compatibility

– Smooth migration from Phase 1 FDMA toPhase 2 TDMA and future interfaces

Project 25: Summary

Project 25 Steering

Committee (users)

APCO P25 Interface

Committee (users & manufacturers)

Telecommunications Industry

Association (TIA), TR.8 Committee(s)

User

needs


EnablingInteroperability

Multi-Vendor Sourcing Migration from

Legacy Equipment

Multiple Frequency

Bands

Conventional & Trunked Operation

Secure Communications

Global Standard with Worldwide Adoption

Coverage Flexibility

Voice and Data

Established

Public Safety User Driven

SpectralEfficiency

Evolving

EnablingInteroperabilityMulti-Vendor

Sourcing

Migration from Legacy Equipment

Multiple Frequency

Bands

Conventional & Trunked Operation

Secure Communications

Global Standard with Worldwide Adoption

Coverage Flexibility

Voice and Data

Established

Public Safety User Driven

SpectralEfficiency

Evolving

Project 25: The Goals


Neil Horden

Chief Consultant

[email protected]

Federal Engineering, Inc.“Unleashing the Power of Technology”

Thank You!



Sponsored by:


Project 25 Conventional System Configurations and Wireline Interfaces

Jim Holthaus

VP – Project 25 Solutions, RELM Wireless

Chair, Telecommunications Industry Association Private Radio

Section

Sponsored by:



AUTHENTICATION

TRUNKING

AIR

INTERACES

SECURITY

INTERFACESWIRELINE

INTERFACES

ISSI/CSSI

P25 FDMA

COMMON AIR

INTERFACE

TRUNKING

Voice/Data

CONVENTIONAL

Voice/Data

P25 TDMA

COMMON AIR

INTERFACE

TRUNKING

VoiceNETWORK

MANAGEMENT

KEY FILL

INTER- KMF

KMF KMF

DATA

SERVICES

DATA

INTERFACES

SUBSCRIBER

DATA

PERIPHERAL

INTERFACE

OTAR

KMF

DATA NETWORK

INTERFACE

Gateway

FSI

Conventional

Analog/Digital

Voice/Control

TRUNKING

Voice/Data/Control

CONVENTIONAL

Voice/Control

SECURITY

SERVICES

ENCRYPTION

Voice/Data

LOCATION

Gateway

TIER 1

Conventional

TIER 2




P25 General Systems Model

P25 Common Air Interface (CAI) Types

1. P25 Conv CAI - Conventional P25 FDMA Common Air Interface

2. P25 Trunked CAI - Trunked P25 FDMA/TDMA Common Air Interface

P25 Wireline Interface Types

1. Eg - Inter RF Sub-System Interface (ISSI)

2. Ec - Console Sub-System Interface (CSSI)

3. Ef - Conventional Fixed Station Interface (FSI)

4. Ed - Data Host Network Interface

5. MDP - Mobile Data Peripheral Interface (MDP)

6. IKI - Inter Key Management Facility Interfaces (IKI)

7. KFD - Key Fill Device Interface

8. Et - Telephone Interconnect

9. En - Network Management v7

Network Management

Adopted from TSB-102-B

Telephone

Interconnect

Fixed

Station

Trunked

Console Sub System Interface ISSI

Inter RF Sub System Interface

ISSI/CSSI

Conventional

FSI


TO PSTN

RF Subsystem A (Trunked

RFSS)E

g

Ec

Et

Ec


Console Sub-

system

Data Network Interface

MDP Int.

Trunked

FDMA/TDMA CAI

KFD Int.

Ed

MDP Int.

A

A

Ef

Conventional

Console Sub System Interface

CSSI

Ed

KMF

KMF

En

P25

Conventional

CAIFS


• Configurations Using the FDMA Common Air Interface

• Voice/Supplementary Services

• Adding Data

• Configurations Using Wireline Interfaces

• Fixed Station Interface

• Conventional Console Subsystem Interface

ConventionalStandard Interfaces and Services


• Conventional Voice services

• Group Call, Individual Call, All Call, Talking Party ID, etc• Conventional Supplementary Services

• Emergency Alarm, Call Alert, Status/Message, etc

Note: For a complete set of voice and supplementary services supported by the FDMA CAI for the 3 conventional configurations see section 2 of the PTIG Capabilities Guide

Conventional ConfigurationsVoice and Supplementary Services

FDMA CAI

Direct

http://www.project25.org/images/stories/ptig/docs/PTIG_P25Capabilities_Guide_v1.7.pdf


• The RFSS is a virtual element • RFSS may take on a variety of physical forms, i.e. there may be

• multiple channels at a site or • multiple sites, or • channel may be a voting, multicast or simulcast “sub-system” covering multiple

physical sites


FDMA CAI

CONVENTIONAL RF Sub-System A

FDMA CAI

Repeated


• RFSS B may still repeat• Console may participate in calls • Console may be the source or target of calls• Console equipment may interface to multiple stations• Console equipment and station(s) within the RFSS do not need a standard P25

interface


Repeated with Wireline Dispatch

CONVENTIONAL RF Sub-System B

FDMA CAI

FDMA CAI



• Encryption service applies to all 3 conventional configurations• Keys may be loaded from a Key Fill Device• Key ID designated in the voice stream • Transmit: Encryption keys may be selected per channel, per talkgroup or per conversation• Receive: may use preselected encryption keys or may search the device’s internally stored

keys

CONVENTIONAL RF Sub-System B

FDMA CAI

FDMA CAI

Repeated with Wireline Dispatch


FDMA CAIMDP Int.

Direct

MDP Int.

Conventional ConfigurationsAdding Data

• Data applications may reside in the radio itself• The FDMA CAI protocol supports a data signaling protocol• The CAI data packets may carry IPv4 datagrams• IP Data Bearer service for data applications that use IPv4Note: For a complete set of CAI data bearer and IP data bearer services supported by the FDMA CAI for the Direct

conventional configuration see sections 3 of the PTIG Capabilities Guide



FDMA CAI

Repeated

MDP Int.

FDMA CAI

MDP Int.CONVENTIONAL

RF Sub-System A

• Fixed Station repeats the data signalNote: For a complete set of CAI data bearer and IP data bearer services supported by the FDMA CAI for the Repeated conventional configuration see sections 3 of the PTIG Capabilities Guide





• Fixed Station does not repeat the data signal• Data Gateway device interfaces Data Host to Fixed Station

• within the RFSS; does not need a P25 standard interface• Data Host outside the RFSS: standard P25 Data Host Network Interface

• carries IP datagramsNote: For a complete set of CAI and IP data bearer services supported by the FDMA CAI for the Conventional Fixed

Network Data configuration see section 4 of the PTIG Capabilities Guide

FDMA CAI

RF Sub-System BDataHost

Data Host Network Int.Data Gateway

MDP Int.

Fixed Network Data



Conventional ConfigurationsAdding Encrypted Data

• Encryption may be added to any of the 3 Conventional data configurations• CAI data packet payload is encrypted• Decryption required before the IP datagrams can be routed • Encryption/decryption in radios and data gateway

FDMA CAI

RF Sub-System B

DataHostData Host Network Int.

KFD Int.

MDP Int.

Fixed Network Data

Data Gateway


ConventionalFSI – Fixed Station Interface Configurations

• The Fixed Station Sub-System is a virtual entity that may take different physical forms• Single Station• Voting sub-system• Multicast sub-system

Fixed Station Sub-System B

RcvAudioVoting

AudioDistribution

Xmit

Rcv

Xmit

Rcv Audio

Xmit Audio

Voted Audio



• Voting or multicast sub-system requires DFSI• Capabilities of FSI + Fixed Station Sub-System working together vary considerably • Certain capabilities subject to equipment configurationsNote: For more information on the capabilities associated with these combinations of AFSI/DFSI and Analog/FDMA

CAI air interfaces see section 11 of the PTIG Capabilities Guide.

RF Sub-System A

FixedStn

HostDigital FSI-EF

dFSI

FDMA CAI-Um

Multiple Station Subsystem


RcvAudioVoting

AudioDist

Xmit

Rcv Audio

Xmit Audio

Voted Audio

Rcv

Xmit



• FSI (AFSI or DFSI) may be used to connect the sub-systems directly when:• Single Console Sub-System and • Single fixed station or a single voting/multicast sub-system

• Console Sub-System takes on the role of RF Sub-System• Console equipment takes on the role of the virtual Fixed Station Host

ConventionalConsole and Fixed Station Interface Configurations

Digital FSI

DFSI

Analog FSI

AFSI

or

Fixed Station Sub-System A

Console Sub-System A

Analog Air Int.

FDMA CAI


ConventionalConsole and Fixed Station Interface Configurations

• RFSS/CAR performs routing Arbitration and Protocol Conversion• AFSI or DFSI to Fixed Station Sub-System• Conventional CSSI to Console Sub-System

Fixed Station Sub-System A

A

RF Sub-System A

ConventionalArbitrator

(CAR)

Console Sub-System A

Console Sub-System B

Conv CSSI

Analog Air Int.

FDMA CAI

Analog Air Int.

FDMA CAI


A



• AFSI: • Use with either Air Interface• 2 or 4 wire analog transport, • clear analog voice, • Tone Remote Control

Fixed StationSUB-SYSTEM A

Analog Air Int.

RF Sub-System A

FixedStnHost

Digital FSI

DFSI

Analog FSI

AFSI

or

FDMA CAI

Single Station Subsystem

• DFSI: • Use with either Air Interface• IPv4 digital transport, • P25 (clear or encrypted) or PCM audio, • P25 control signaling


Jim Holthaus

[email protected]

Thank You!



Sponsored by:

mailto:[email protected]



March 21, 2016

Project 25 FoundationsTrunking System Configurations and

Wireline Interfaces for Project 25



Nick PennanceVice President, ICOM America




AUTHENTICATION

TRUNKING

AIR

INTERACES

SECURITY

INTERFACESWIRELINE

INTERFACES

ISSI/CSSI

P25 FDMA

COMMON AIR

INTERFACE

TRUNKING

Voice/Data

CONVENTIONAL

Voice/Data

P25 TDMA

COMMON AIR

INTERFACE

TRUNKING

VoiceNETWORK

MANAGEMENT

KEY FILL

INTER- KMF

KMF KMF

DATA

SERVICES

DATA

INTERFACES

SUBSCRIBER

DATA

PERIPHERAL

INTERFACE

OTAR

KMF

DATA NETWORK

INTERFACE

Gateway

FSI

Conventional

Analog/Digital

Voice/Control

TRUNKING

Voice/Data/Control

CONVENTIONAL

Voice/Control

SECURITY

SERVICES

ENCRYPTION

Voice/Data

LOCATION

Gateway

TIER 1

Conventional

TIER 2

















8. Et – Telephone Interconnect

9. En - Network Management

Fixed

Station

Conventional

FSI

Ec


KFD Int.

MDP Int.

A

v8

Ef

Conventional

Console Sub System

Interface

CSSI

P25

Conventional

CAI

FS

MDP Int.

Network Management

Telephone

Interconnect

Trunked

Console Sub System

Interface

ISSI


ISSI/CSSI


TO PSTN


Eg

Et

Ec

Console Sub-

system


Trunked

FDMA/TDMA

CAI

Ed

Ed

KMF KMF

En

CC WC WC WC




Fixed

Station

Conventional

FSI

Ec


KFD Int.

MDP Int.

A

v8

Ef

Conventional

Console Sub System

Interface

CSSI

P25

Conventional

CAI

FS

MDP Int.

Network Management

Telephone

Interconnect

Trunked

Console Sub System

Interface

ISSI


ISSI/CSSI


TO PSTN


Eg

Et

Ec

Console Sub-

system


Trunked

FDMA/TDMA

CAI

Ed

Ed

KMF KMF

En

CC WC WC WC












8. Et - Telephone Interconnect

9. En - Network Management


• Traffic Channels– Voice FDMA: 1 Talkpath / channel - 9600 bps

– Voice TDMA: 2 Talkpaths/channel - 12000 bps (2x efficiency)

– DATA FDMA: 9600 bps

Project 25 TrunkingCommon Air Interface (CAI)

RF Subsystem

(Trunked RFSS)Trunked

FDMA/TDMA

CAI

CC WC WC WC• Control Channel (CC)– 9600 bps FDMA

• Operates on 12.5 kHz Channels

• Supports Integrated Voice and Data

• Supports 256 bit AES Encryption


Project 25 TrunkingCommon Air Interface (CAI)

Control Channel

• Controls traffic on the network

• 9600 bps OTA bit rate

• Assigns SU to FDMA or TDMA

Voice or DATA

P25 FDMA (Phase 1)

VOICE Services

• 1 talkpath per channel


• Full Rate IMBE or AMBE Vocoder

• Supports Encrypted Mode

P25 TDMA (Phase 2)

VOICE Services

• 2 talkpaths per channel


• Half Rate AMBE Vocoder

• Requires TDMA-capable radios

• Supports Encrypted Mode

P25 PACKET

DATA Services


• Supports Integrated

Voice & Data


• Integrated Voice & Data Services

• Mobility & Registration

• End-to-End Encryption

– Voice & Data

• Telephone Interconnect

P25 Trunking - Basic Services

• Supplementary Services

– Radio Inhibit / Uninhibit

– Call Alert

– Emergency Alarm

– Priority Call

– Pre-emptive Priority

– Radio Check

– Discreet Listening

– Radio Unit Monitoring

– Short Message


• The P25 Data Network Interface connects a data gateway device or functional element to the application Host(s) in the Public Safety Application Network (PSAN).

• In trunking, data service requests on the control channel result in assignment of a data channel.

– P25 Trunked FDMA Data channels may be assigned for single data transaction requests or a data channel may be assigned and then shared between multiple, independent data transactions.

P25 Trunking - P25 Packet Data

• P25 Packet Data

• SERVICES– Tier 2 Location Service

(GPS)

– Over the Air Rekeying (OTAR)

• Data CAI– 9600 bps Integrated Voice

& Data

– 12.5 kHz Narrowband Channel

– Supports Simulcast

– 256 bit AES Encryption


System Configurations

Single Site Trunked RFSS

Project 25 Trunked

RF Sub-SystemMulti-Site Trunked RFSS

Project 25 Trunked

RF Sub-System

• Multi Site– Simulcast

– Multicast

• Single Site


Primary P25 Wireline Interfaces

• Enhances interoperability

• Advanced services

• Multi-system connectivity with autonomy

• End-to-end encryption

• Coverage Extension

• Enabling multivendor networks and procurements

• More competitive environment

• Intricate call controls across systems

CSSI

Console Sub-System Interface

Project 25 Trunked

RF Sub-System BP25 Console

Sub-System B’

Telephone InterconnectInterface

Project 25 Trunked

RF Sub-System A

ISSI/CSSI

Inter RF Sub-System Interface

FDMA or TDMA,

Voice or Data

P25 CAI

CC WC WC WC Network Management


Wireline Interface Updates 2014

• An addendum to the ISSI Messages and Procedures Standard is in progress.

– The revision corrects several errata that have been noted since the last publication.

• A revision to the Fixed Station Interface Standard is in progress.

– This revision adds additional capabilities the most significant of which is Packet Data.


P25 Trunked ISSI/CSSI Overview

• Communications and control between P25 systems & supporting consoles

• Interoperability across vendor solutions

• Interoperability option with neighboring networks, regardless of how they evolve and change

• Connectivity while maintaining system autonomy

• Support of mixed vendor backbones

• End-to-end encryption

Enabling

• Inter-System Group Call• Emergency Group Call• Emergency Alarm• Transparent to AES• Inter-System Unit-to-Unit

Call

ISSI

Inter RF Sub-System Interface Features

• Broadcast Call• Status

Query/Update• Unit ID• Call Alert• Radio Inhibit

P25 CSSI Adds to P25 ISSI Features:• Monitor Simultaneous TalkGroups• Dispatcher Audio Takeover (also

called Console Priority)• Console Take Over by Another

Console • Parallel Console Audio

CSSI

Console Sub-System Interface

• Console-Initiated Group Call• Radio-Initiated Group Call• Console Priority• Emergency Group Call• Multiple TG Support

Which create console services, best described as:

ISSI/CSSI

CSSI

Project 25 Trunked

RF Sub-System AGROUP CALL CONTROL

Project 25 Trunked

RF Sub-System BGROUP CALL CONTROL P25 Console

Sub-System


P25 ISSI & CSSI - Multi-System Scenarios

Connecting RF Sub-Systems Using ISSI (no CSSI) • Creates interoperable P25 Services across disparate systems

• Console operate across ISSI but without CSSI features;

- Consoles behave like subscribers.Radios not shown.

Connecting Systems Using CSSI Only • CSSI can be used to connect a separate Console Sub-system B, allowing console operator (Console OP) positions to control traffic on System B

- Enables 3rd party P25 console options

• Consoles can operate on both sides of interfaceRadios not shown.

• This configuration supports all P25 ISSI/CSSI features between different subsystems and a separate Console Subsystem, allowing intricate controls over vast network resources.

Connecting Systems Using ISSI/CSSI

Radios not shown.

A


Telephone Interconnect (Et)

Telephone

Interconnect Et

PSTN


CC WC WC WC

• TSB-102.BADA-A *Telephone Interconnect Overview (Voice Service)

• Enables analog and digital voice

• Interface between:– Subscriber Units of a RF

Subsystem (RFSS)

– Telephones on a Public Switched Telephone Network (PSTN)

* Although Project 25 acknowledges the importance of this interface to the overall P25 General Systems Model, the strength of

established industry standards adequately covers the needs of this interface, avoiding the need for a potentially redundant

standard to be developed. For this reason, the Telecom Systems Bulletins (TSBs) are used to describe aspects of existing

standards specifically applicable to P25.


Network Management (En)

• TSB-102.BAFA-A *

• Interface between:– Operations and Maintenance

Center for RFSS (OMC-RF)

and

– System level Network Management Center (NMC)

• Current Focus is:– Fault management

– Performance management

* Although Project 25 acknowledges the importance of this interface to the overall P25 General Systems Model, the strength of

established industry standards adequately covers the needs of this interface, avoiding the need for a potentially redundant

standard to be developed. For this reason, the Telecom Systems Bulletins (TSBs) are used to describe aspects of existing

standards specifically applicable to P25.


Network Management

En



March 21, 2016

Thank You

Nick PennanceVice President, ICOM America

Project 25 Technology Information- LMR to LTE- Automatic vs. Manual Roaming - ID Duplication- P25 Security Services Update

Bill Janky

Director, System Design

Harris Corporation

68Project 25 Technology Interest GroupMarch 21, 2016

LMR and LTE

LMR to LTE

LMR vs. LTE


LTE

LMR

69March 21, 2016


NPSTC

NIST/PSCR

FirstNet

APCO

TIA

DHS/CAP

3GPP

APIC

FCC

OMA

NFPA/FM/ISA/CSA/UL

GSMA

PTIG

EIEIO

PRS

ATIS

70March 21, 2016

Topics

• Background information on 3GPP and Public Safety

• Brief status update on MCPTT and SA6

• LMR to LTE

– Interworking mainly (not migration)

– Status of multiple parallel working groups

• ATIS JLMRLTE

• ATIS LMR-to-LTE ad hoc

• NPSTC LMR to LTE working group

Project 25 Technology Interest Group 71March 21, 2016

A little background info…

Project 25 Technology Interest Group72March 21, 2016

Public Safety Broadband Standards

• There is (and was) much activity in 3GPP, ATIS, TIA, NPSTC, OMA, etc., focused on Public Safety

• 3GPP has done most of the heavy lifting with Public Safety capturing a lot of attention and meeting time in 3GPP

• In fact, 3GPP formed a new committee/working group to focus specifically on mission critical applications: SA6

• And work continues in other working groups on public safety aspects


3GPP (3rd Generation Partnership Project)organizational structure



3GPP Mission Critical workflow

SA6MCPTT, MCVideo,

MCData, …

requirements

CT WGs

SA WGs

SA2RAN WGs

• SA1 gathers service requirements from company contributions, reflecting user needs

• SA6 designs the overall architecture for mission critical applications in co-operation with SA2

• Other working groups create the detailed specifications

SA1

75March 21, 2016

SA6 and MCPTT

• There was so much public safety-related activity in 3GPP that they decided to create a separate working group to focus on mission critical applications – SA6.– Officially formed in January of 2015. There were eight face-to-face meetings last year, plus numerous conf

calls. – Current (and only) focus is Mission Critical PTT (MCPTT) architecture.– MCPTT application architecture is the only thing being worked in SA6 and it has been worked very hard

• Current Status:– MCPTT architecture Technical Specification (normative), TS 23.179, has been completed (206 pages...)– Sample of items covered:

• On-network architecture / Off-network architecture including direct mode and relay mode• Floor control aspects for these modes• Security issues, registration, authentication, affiliation, identity management• Call control signaling• Group/user management• Priority/Preemption• Service continuity• Specific features


SA6 and MCPTT (cont)

• Current Status (cont):

– The SA6 component of LTE R13 work is completed. Starting R14 (filling in missing pieces, correcting errors/omissions, plus new Mission Critical work items)

– A fair amount of open issues and deferred features, which may not be resolved in R13. • It’s hard to tell exactly what’s in and what’s out until the dust settles

• A new Work Item (WID) for R14 is in progress - “Study on MBMS* usage for mission critical communication services”

– It will cover service continuity to/from unicast, security, QoS, reception reporting, etc.

– Attempts to cover many, but not all, gaps in the current spec.

• In parallel, Change Requests (CRs) will be generated to clean up R13 issues


*MBMS – Multimedia Broadcast Multicast Services

77March 21, 2016

UE

E-UTRANUnicast path

MCPTT server

MCPTT

client

MBMS path

GC1

UuRx

MB2-U

MB2-CSGi

MCPTT high-level “transport” architecture


MCPTT version of a generic on-network “group communication” application architecture

MCPTT Application Plane


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-3MCPTT 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

Other MCPTT server

79March 21, 2016

PS/MC work in other WGs

• SA1– Working on requirements for Mission Critical Video and Mission Critical Data

• SA2– Continued work on enhancing “enablers” for MCPTT such as GCSE/MBMS (group communication/multicast) and ProSe

(Proximity Services / Direct Mode)

• SA3– Working on security aspects of MCPTT and ProSe

• SA4– Working to specify media codecs, media handling, and enhancements to enable delivery of MCPTT in accordance with

requirements defined by SA1 and architecture defined by SA2 and SA6. TS 26.179.

• CT – Working hard on detailed protocol work for MCPTT

• Note: Much of the protocol based on OMA PCPS

– As of this month, work on Stage 3 MCPTT is claimed to be complete.

• RAN– Completed work for ProSe/D2D and GCSE/MBMS for R12, but still cleaning up various things– Starting to shift focus to 5G.



LMR?LTE?LMR and LTE!

81March 21, 2016

LMR to LTE

• Lots of interest in Interworking between LMR and LTE, and migration from LMR to LTE

• Current activities (that I know of)

– IWF-1 and MCPTT-3 definition in 3GPP

– ATIS JLMRLTE

– LMRLTE (hosted by ATIS)

– NPSTC LMR to LTE working group

• Interworking is the main focus here


JLMRLTE

• ATIS/JLMRLTE– JLMRLTE is a joint project between ATIS WTSC and TIA TR-8 (specifically TR-8.8).

Work falls under ATIS Issue 39.• Creation of a requirements/architecture and possibly protocols for interworking LTE PTT

with LMR• Requirements and use cases completed. Started architecture work.

– Currently on hold pending architecture work in SA6. • Hoping to take it off hold soon after SA6 had made sufficient progress on the architecture so

that we know how we would be connecting.• However, interworking requirements have been deferred to R14. This happens quite

frequently in 3GPP.• Note: Interworking interface (IWF-1) is likely to be based on the MCPTT Server to Server

interface (MCPTT-3) which will probably be based on the OMA PoC NNI. As long as you look like an MCPTT Server then you can interwork. Hold that thought…


LMRLTE

• LMRLTE– A new ad hoc group has been created called “LMRLTE”; Hosted by ATIS;

Qualcomm is chair (Farokh Khatibi).• Purpose is to influence 3GPP MCPTT interworking architecture and protocol

development– Example, Tetra/P25 doesn’t work unless the interworking interface, IWF-1, does….this, or that

• Currently working on terminology alignment, call routing scenarios, taxonomy, and features/gaps

– What’s the output?• Need a way to transfer requirements and useful information to 3GPP• Current plan is to propose a new WID (Work Item) in SA6 specifically for the

interworking interface and bring results of this LMRLTE ad hoc into SA6 as contributions under that work item


LMR to LTE

• Confused yet? OK, there is another group: NPSTC LMR to LTE Migration Working Group (under the Technology Committee)– “It is important to fully explore the coexistence of, and simultaneous use of, LMR and LTE technologies to

determine necessary operational requirements to ensure continued interoperability.”

• The purpose of this working group is:– Examine ways in which LTE voice services may be used by public safety to supplement or replace LMR

systems, including administrative/secondary push to talk and mission critical voice/push to talk.– Examine existing interoperability systems and technologies that are in use today to determine if these

capabilities may be leveraged to support LMR to LTE interoperability.– Review the minimum requirements needed to support mission critical voice interoperability between LMR

and LTE networks.

• 5 meetings so far– Establishing baselines of knowledge. Some outputs of ATIS LMRLTE sent to this working group for

information.– Use case development starting now.


LMR to LTE summary

• All groups have similar goals

– Define the user requirements, usually through use cases

– Extract requirements

– Then ???

• JLMRLTE: Resume work when MCPTT IWF-1 is defined

• LMRLTE ad hoc: Disband after transferring work to SA6

• NPSTC LMR to LTE WG: Write a report and probably send it to FirstNet, SA6, and other interested parties


Ultimate goal is standards-based interworking

between legacy PTT on LMR and MCPTT on LTE

Abbreviations

• 3GPP – 3rd Generation Partnership Project

• ATIS – Alliance for Telecommunications Industry Solutions

• CT – Core Network and Terminals• EPC – Evolved Packet Core• GCSE: Group Communication System

Enabler• IMS – IP Multimedia Subsystem• JLMRLTE - Joint LMR and LTE• LMR – Land Mobile Radio• LTE – Long Term Evolution

• MBMS – Multimedia Broadcast Multicast Services

• MC – Mission Critical• MCPTT – Mission Critical Push To Talk• OMA: Open Mobile Alliance• P25 – Project 25• ProSe: Proximity Services• PS – Public Safety• QoS – Quality of Service• RAN – Radio Access Network• SA – System Architecture• TIA – Telecommunications Industry

Association


Automatic vs. Manual Roaming

88March 21, 2016 Project 25 Technology Interest Group

• Two roaming methods often discussed in P25:

– Automatic

– Manual

• What’s the difference? Let’s look at two areas:– User Experience

– Identity Management

Automatic vs. Manual Roaming

Note: This is all from a P25 Trunking perspective


• Automatic Roaming– “automatic roaming” refers to the radio’s ability to move from the

coverage of one RF site to another without user intervention• In theory, the user doesn’t know it happens

• However, P25 roaming is not completely “seamless”

– Requires cooperation between the two sites including broadcasting a standardized set of information about nearby sites to the radios to facilitate roaming

– The two sites (old and new) can be part of the same system, or can be part of two separate systems perhaps connected via ISSI

• Stay tuned for Identity Management discussion…

Roaming - User Experience


• Manual Roaming

– “manual roaming” from the user’s perspective requires the user to physically select the new site, or system using radio control methods (i.e. menu, selector, etc.)

– The radio tunes to the newly selected site frequency and attempts to register on the RF site’s control channel

– Manual selection might also include an identity change

• Hey, I said stay tuned for the Identity Management discussion…

Roaming - User Experience (cont)


• P25 addressing

– Subscriber Unit Identity, SUID is a 56-bit identifier unique in the universe

• Automatic Roaming

– From the perspective of a radio user, the term “automatic roaming” refers to the ability of a radio to move from the operational area of one system to the operational area of another system without changing the operating identities (individual and/or group) of the radio

Roaming - Identity Management

WACN20 bits

System12 bits

Unit ID24 bits

Home

System


• Automatic Roaming (cont)– Roaming within your home system is easy

– When roaming to another system (different WACN.System) the radio always uses the full SUID assigned by the individual radio’s home system when registering on the new (roamed to) RF site

– The new site can accept it or tell the radio to go away

– If there is an ISSI connection (not required), the ISSI will enable information exchange between the new system of operation and the home system of the SUID

Roaming - Identity Management (cont)

Note for advanced students: The term “automatic roaming” also allows a radio to affiliate to a

talkgroup that is homed to a system other than the system of current operation


• Manual Roaming– In “manual roaming”, the radio operator manually changes the parameters that

the radio uses to try and locate and register on a new site (frequencies, site identifiers, etc.), and may also change the operating identity (SUID) of the radio itself in order to operate on one system or another.

– Validation of the radio’s individual identity works exactly the same as with “automatic roaming” – the new site can validate the identity itself, or can use the ISSI for assistance. The new site can accept it or tell the radio to go away.

– Changing the individual unit ID can facilitate operation on foreign/visited systems that are not connected to the radio’s home system via ISSI.

Identity Management (cont)

This will all become clear very soon…


ID Duplication


• Now that we understand roaming a little better, how do we avoid ID “collisions” within and between systems?

• Well, proper planning and some discipline are necessary.

• Two general scenarios apply:

– Managing Radio IDs within your home system, and for frequent visitors to your system

– Managing Radio IDs for infrequent visitors to your system and special events

ID Duplication


ID Duplication

• What to do ahead of time

– First, use the TIA-102 / P25 Addressing Rules

• Program your radio IDs to adhere to the Subscriber Unit ID, SUID, format: WACN.System.UID

• Use the P25 Guidelines to Assign WACN & System IDs for your system– Remember that WACN.System is your radio’s “home”


ID Duplication

• What to do ahead of time (cont)

• If You Have Frequent Visitors…• Consider giving them an ID on your system

• Tell them to use Manual Roaming with identity change

• NOTE: Manual selection of the radio’s SUID is not standardized, but is a common feature available in most P25 radios (multiple profiles/personalities)

– For infrequent visitors, and other scenarios, consider installing an ISSI gateway

• More later………

Some planning is necessary to avoid having two radios on

your system with the same ID


• Manual Roaming of “visiting/foreign” Users – When the roaming user arrives at your system, he/she manually switches the radio to your

parameters (frequencies, etc) and the radio searches for and finds the control channel– When the radio attempts to register, two options exist:

• Identity change– Manual selection also changed the radio SUID to something homed here– An SUID has been reserved for this radio on the system, the radio uses it to register, and life is good

• No identity change– The radio attempts to register with its unique SUID assigned on its home system– The new site can either:

» Be nice and accept it, or» if there is an ISSI connection between the old and new system, the ISSI will enable information

exchange between the new system of operation and the home system of the SUID to validate the radio

(Well there is a 3rd option – the site can Deny the registration…)

Trunking ID Duplication


• Automatic Roaming of “visiting/foreign” Users – When the roaming radio switches to your system the radio has already figured out where it

is and it attempts to register

– In automatic roaming there is no identity change option

– So, the radio always attempts to register with its unique SUID assigned on its home system, and the same things can happen

• The new site can accept it, or check with the ISSI (if there is one)

– Note: In automatic roaming (or manual with no identity change), the UID (lower 24 bits of the SUID) is only guaranteed to be unique in the home system

• The visited system will assign a Temporary Working UID from a pool of unused UIDs



• Final thoughts

– Follow the P25 Subscriber Unit ID addressing rules!• The WACN.System.UID addressing method will facilitate the interoperability and

compatibility with different P25 systems and visitors.

– Use an ISSI connection back to another system • Consult your ISSI vendor or consultant for tips and tricks on managing IDs across the ISSI

– Have a plan ahead of time for foreign visitors!• Set up operational procedures and have agreements in place before you need them

– And in case you were wondering, P25 conventional only supports manual roaming…



P25 Security Status

Project 25 Technology Interest GroupMarch 21, 2016 102

Security Services Evolution

• 1998– End-to-End Voice Encryption

– Data CAI Encryption

– DES Encryption

– OTAR

– Multiple Keys

– Subscriber Validation

• 2005– 3DES Encryption

– AES Encryption

103March 21, 2016

• 2011– Subscriber and FNE

Authentication

– Inter-KMF Interface

• 2014+– OTAR overhaul

– KFD to SU/KMF/AF interface

– Link-Layer Encryption (Anti-Analysis)


What’s new, what’s coming

• KMF/AF to KFD interface – New

– Revised draft in progress. Working through comments with 101 comments left to resolve.

– When comment resolution is complete, the draft will be updated and sent to TIA TR8.3 for standards finalization and publication.

• Project 25 Digital Land Mobile Radio Block Encryption Protocol (TIA-102.AAAD-A) 5

Year Update Published on 24 Nov. 2015 Available on TIA Global HIS Site

• Project 25 Interoperability Testing for OTAR Messages and Procedures (TIA-

102.CABB-A) Published on 1 Nov. 2015 Available on TIA Global Site.


What’s new, what’s coming (cont)

• Link Layer Encryption standard – New– LLE provides confidentiality and replay protection for IDs and control messages

• Note: LLE is NOT a substitute for end-to-end encryption

– Requirements reviewed and agreed to. LLE SSO/ Architecture document ETG 14-024-R05 has been combined with Key Management section document ETG14-057-R7 into a new merged LLE SSO/ Architecture document ETG15-029-R4, and is in review with agreements on many key architecture concepts.

• On completion of this document other standards documents for LLE will resume development.

– Work Plan has been formulated with assignments for drafting standards and updates to existing standards.

– Changes to existing standards partially complete; awaiting completion of LLE SSO:• FDMA CAI TIA-102.BAAA

• TDMA MAC TIA-102.BBAC

• Trunking Formats (TSBKs/ MBTs) TIA-102.AABB

• Others as needed


Security standards continue to evolve in P25…

105March 21, 2016

Thank you!

email: [email protected]
