iwce 2015 ptig-p25 foundations part 1
TRANSCRIPT
IWCE 2015, Las Vegas, NevadaMarch 16, 2015
Presented by:
PTIG - The Project 25 Technology Interest Groupwww.project25.org – Booth 1853
Project 25 College of Technology
© 2015 PTIG
Project 25 FoundationsPanel Discussion for 2015
Steve NicholsProject 25 Technology Interest Group Director
2-24-15
© 2015 PTIG2
PTIG - Project 25 Technology Interest Group IWCE 2015
• Moderator – Steve Nichols, Project 25 Technology Interest Group (PTIG), Director
• Panelists – Neil Horden, Chief Consultant, Federal Engineering
– Darek Wieczorek, Senior Director, Tait Radio
– Cheryl Giggets, Senior Vice President, AECOM
– Andy Davis, Senior Resource Manager, Motorola Solutions
– Bill Janky, Director Systems Design, Harris Corporation
– Cynthia Wenzel Cole, CTO, Cynergyze
– Chris Wilson, Senior Technologist, Cynergyze
– Chris Lougee, Vice President, ICOM
Program Participants
© 2015 PTIG3
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25 Foundations Agenda
Topic Speaker Workshop Overview
PTIG Introduction, New P25 Documents on the WEB
Steve Nichols
PTIG
The Goals, The Standards Process, P25 Standards Today Neil Horden
Federal Engineering
Conventional System Configurations and Wireline Interfaces for Project 25 Darek Wieczorek
Tait Radio
Trunking System Configurations and Wireline Interfaces for Project 25
+How to avoid ID Duplication
Cheryl Giggetts
AECOM
Break
Project 25 Standards Update: Newly Released Documents, Work in Process.
Project 25 Capabilities Matrix: Guided tour/How to use it
Andy Davis
Motorola Solutions
Security Services Update Project 25.
P25 Vocoder Improvements, P25 Range comparison
Bill Janky
Harris
Public Safety LTE Broadband and Project 25: P25 + PS LTE Use Cases and PS
3GPP standards update
Cynthia Wenzel Cole,
Chris Wilson
Cynergyze
Project 25; Products and Services available
CAP testing Update. PTIG CAP product list and links
Chris Lougee
ICOM
Open Forum and Discussion, Questions and Answers Steve Nichols
© 2015 PTIG4
PTIG - Project 25 Technology Interest Group IWCE 2015
• 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 Security services and their importance
• 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
v2
Who and What is PTIG?
© 2015 PTIG6
PTIG - Project 25 Technology Interest Group IWCE 2015
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
© 2015 PTIG7
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25 Technology Interest Group: Sustaining Members
© 2015 PTIG8
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25 Technology Interest Group: Commercial Members
© 2015 PTIG9
PTIG - Project 25 Technology Interest Group IWCE 2015
Console
power audio Channel A Channel B
Available in VHF, UHF, 700, 800, and 900 MHz
15 fixed station/repeater suppliers
14 Subscriber suppliers
13 console suppliers
15 network providers
4 test equipment suppliers
5 consultant services
34 Vendors for Project 25 Equipment and Services
© 2015 PTIG10
PTIG - Project 25 Technology Interest Group IWCE 2015
PTIG Member Organizations
www.Project25.org
Fixed
Stations &
Repeaters
Mobile &
Portable
Radios
Consoles Networks SoftwareTest
Equipment
Systems
Integration
Consultant
Services
AECOM
AEROFLEX
AIRWAVE SOLUTIONS
AIRBUS DS COMMS (FORMERLY CASSIDIAN)
ANRITSU
AVTEC
CATALYST COMMUNICATIONS
COBHAM AVIONICS
CODAN RADIO (FORMERLY DANIELS)
CYNERGYZE
DVSI
EF JOHNSON
ETHERSTACK
FEDERAL ENGINEERING, INC
GENESIS GROUP
HARRIS CORPORATION
ICOM AMERICA
IDA CORPORATION
JVC KENWOOD
MIDLAND RADIO
MOD-U-COM
MOTOROLA SOLUTIONS
PANTEL INTERNATIONAL
POWERTRUNK
RELM WIRELESS
SIMOCO
SPECTRA ENGINEERING
STANDARD COMM PTY LTD - GME
TAIT COMMUNICATIONS
TECHNISONICS
TELEX RADIO DISPATCH
VERTEX STANDARD
WIRELESS PACIFIC
ZETRON
34 15 14 13 15 5 4 15 5
Project 25 Products and Services Available
© 2015 PTIG11
PTIG - Project 25 Technology Interest Group IWCE 2015
What do we do:
– Provide an information 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 such as THIS SESSION.
Project 25 Technology Interest Group
© 2015 PTIG12
PTIG - Project 25 Technology Interest Group IWCE 2015
New Documents available at www.Project25.org
• P25 Frequently Asked QuestionsWritten to officer, firefighter (non technologist) level
• P25 Updated Capability Guide Added Infrastructure interfaces and link to Statement of Requirements
• P25 Standards Update SummarySummary of the latest 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 GroupPTIG
© 2015 PTIG13
PTIG - Project 25 Technology Interest Group IWCE 2015
New Documents available at www.Project25.org
• P25 CAP Tested Radio Products listingThe DHS sponsored Website that has hosted CAP test data and SDOCs for P25 manufacturers has been off air and unavailable. PTIG now provides a P25 CAP tested Product List document with direct links to Company data bases or POC info to improve accessibility to each manufacturer’s copies of CAP test documents and SDOCs. PTIG does not intend to become the repository for CAP test data but offers this in the interim until the DHS site is renewed.
• New White paper: P25 Vocoder Improvements A detailed report of the numerous audio improvements made possible through the latest P25 Vocoder design.
Project 25 Technology Interest GroupPTIG
© 2015 PTIG14
PTIG - Project 25 Technology Interest Group IWCE 2015
Projects Underway 2015
• New Point of Contact list (POC) for Project 25 system operators/administrators. This resource will allow Information sharing between P25 systems in different regions. It will be used by visiting agencies to get access to the Local/Statewide P25 systems to facilitate interoperable communications for mutual aid
• Valuing mission critical radio services: A study of the economic value of land mobile radio spectrum in Australia. Thanks to Australian Radio Communications Industry Association and
Geoff Spring APCO Austrailasia
• New Whitepaper: Need for continued funding for P25 systems
Project 25 Technology Interest GroupPTIG
© 2015 PTIG15
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Presentations at IWCE This Week
Project 25 Foundations and System Technology Updates for 2015
Monday, March 16, 2015 (You are in this Session Now)8:30AM-12:00PM
Room: N253
P25 User’s Perspective, Interoperability, and Customer Applications Update for 2015
Tuesday, March 17, 20158:30AM-12:00PM
Room: N257
Estudios de Caso: TETRA, LTE y P25
Wednesday, March 18, 20154:15PM- 5:30PM
Room: N255, Ramone Mouynes, Zetron
National Emergency Communications Plan - Update
Wednesday, March 18, 20154:15PM- 5:30PM
Room: N257, Chris Essid DHS OEC
© 2015 PTIG16
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Presentations at IWCE This Week
An Update on P25 Compliance Assessment Program (CAP)
Thursday, March 19, 2015
9:45AM-11:00AM
Room: N252, Chris Lougee, ICOM John Merrill, DHS
Best Practices in P25
Thursday, March 19, 2015
11:15AM-12:30PM
Room: N255, Dean Hane, MACC911
ISSI for Interoperable Communications
Friday, March 20, 2015
8:30AM- 9:30AM
Room: N255, Marty Christianson Airbus DSC
Town Hall: We Are OEC
When: Wednesday, March 18, 2015
10:30AM-11:00AM
Room: Keynote Area, Ronald Hewitt, DHS
© 2015 PTIG17
PTIG - Project 25 Technology Interest Group IWCE 2015
• AECOM• Airbus DS Communications• Aeroflex• Airwave Solutions• Anritsu• Avtec• Catalyst Communications• Cobham Avionics• Codan Radio (formerly Daniels)• Cynergyze• DVSI• EF Johnson Technologies• Etherstack• Federal Engineering, Inc• Genesis Group• Harris Corporation• Icom America
PTIG Commercial Members
• IDA Corporation• JVCKenwood• Midland Radio• Moducom• Motorola Solutions• Pantel International• Powertrunk• Relm Wireless• Simoco• Spectra Engineering• Standard Comm Pty Ltd - GME• Tait Communications• Technisonic• Telex Radio Dispatch• Vertex Standard• Wireless Pacific• Zetron
© 2015 PTIG18
PTIG - Project 25 Technology Interest Group IWCE 2015
OUR MEMBER ORGANIZATIONS AS IWCE EXHIBITORS
THANK YOU
Aeroflex * 1053
Airbus DSC * 1521
Anritsu 1034
Avtec 1443
Catalyst 1567
Cobham * 1846
Codan * 8027
EFJohnson * 1031
Etherstack 1721
Genesis Group, The 521
Harris * 1361
Icom * 621
IDA Corporation 1371
JVCKenwood * 1221
Midland Radio 1153
ModUcom 1821
Motorola Solutions * 921
Powertrunk 1161
RELM * 1451
Simoco 441
Tait * 823
Telex Bosch 1261
Vertex Standard * 1041
Zetron 1121* Sustaining Member of PTIG
Visit
PTIG in
Booth
#1853
© 2015 PTIG19
PTIG - Project 25 Technology Interest Group IWCE 2015
Thank You!
Steve NicholsDirector, Project 25 Technology Interest Group
www.project25.org
Presented by:PTIG - The Project 25 Technology Interest Group
www.project25.org – Booth 1853
IWCE 2015, Las Vegas, NevadaMarch 16, 2015
Presented by:
PTIG - The Project 25 Technology Interest Groupwww.project25.org – Booth 1853
Project 25 College of Technology
© 2015 PTIG
Project 25 Standards UpdateNeil Horden
Chief Consultant
Sponsored by:
© 2015 PTIG21
PTIG - Project 25 Technology Interest Group IWCE 2015
• Origins and History of P25
• The Goals of P25
• The User Requirements
• The Standards
• Interoperability
• P25 Meeting it Goals
• The Continuing Evolution of P25
Project 25 Introduction: Topics
© 2015 PTIG22
PTIG - Project 25 Technology Interest Group IWCE 2015
THE ORIGINS OF P25:WHERE WE CAME FROM
© 2015 PTIG23
PTIG - Project 25 Technology Interest Group IWCE 2015
• FCC mandating improvements in VHF/UHF efficiency
• Opening of 800 MHz band
• FCC announces plans for new trunking spectrum
• First seem 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
© 2015 PTIG24
PTIG - Project 25 Technology Interest Group IWCE 2015
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, Thee National Security Agency
Agree to the Creation of;APCO – NASTD – FED Project 25(later shortened to Project 25)
Project 25 Established:Broad Support Found
© 2015 PTIG25
PTIG - Project 25 Technology Interest Group IWCE 2015
• Driven by a formalized Steering Committee:
– Four members represent the Association of Public-Safety Communications Officials-International (APCO):
– Four members represent the National Association of State Telecommunications Directors (NASTD)
– Three members represent combined interests of the Federal Government
– APCO and NASTD appoint co-project directors
Maintaining a User Focusin the world of industry driven
standards…
© 2015 PTIG26
PTIG - Project 25 Technology Interest Group IWCE 2015
• Formally Structured under the Telecommunications Industry Association (TIA)
• A Memorandum of Understanding (The MoU)
– The MoU defined the roles, responsibilities, and the relationship between TIA and P25
– The MoU defines the relationship among P25vendor participants
Establishing Credibilityas a Formal Standard
© 2015 PTIG27
PTIG - Project 25 Technology Interest Group IWCE 2015
• 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
© 2015 PTIG28
PTIG - Project 25 Technology Interest Group IWCE 2015
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
© 2015 PTIG29
PTIG - Project 25 Technology Interest Group IWCE 2015
• Public safety communication users are responsible for providing and maintaining their user needs in a system requirements document.
– Project 25 is the only user-driven, land mobile radio standard that currently exists
• The Project 25 Steering Committee and the Project 25 User Needs Subcommittee (P25 UNS) establishes the priorities and scope for;– Technical development of new standards
– Revision of existing P25 standards
• P25 standards are driven by the user-defined P25 Statement of Requirements document known as the P25 SoR.
– The P25 SoR plays an essential role in Developing standards that meet users’ needs
– The P25 UNS updates the SoR annually• Clarify requirements,
• Add new requirements
• Remove outdated requirements
Project 25: The User Requirements
© 2015 PTIG30
PTIG - Project 25 Technology Interest Group IWCE 2015
The P25 Standard is not one document• It is a suite of over 75 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
© 2015 PTIG31
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25: Interfaces & Services
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
Trunking/Conventional
TRUNKING/CONVENTIONAL
© 2015 PTIG32
PTIG - Project 25 Technology Interest Group IWCE 2015
Over 89 documents developed and publishedsupporting the Project 25 suite of standards and features
• The P25 standard is organized into documents relating to;– System interfaces
– Services
– Equipment
• For each P25 interface, service, and equipment item there is a set of documents that:– Describes and specifies the appropriate standards
– Describes the tests to demonstrate conformance, performance and interoperability
– Describes the suite of tests selected to demonstrate compliance
Project 25: The Documents
© 2015 PTIG33
PTIG - Project 25 Technology Interest Group IWCE 2015
Two types of documents are used to describe and specify the interface, service, or equipment
• The Overview document– Typically an informative Telecommunications Systems Bulletin (TSB) that
describes the operation and function associated with a standard
– Provides background information relating to the P25 SoR, shows its relationship to the overall P25 system model, and provides guidance to users, system designers, and manufacturers
• The Protocol documents– These documents provide the required messages, formats, and specifications
necessary for the P25 interfaces, services, and equipment to be interoperable and meet the Project 25 Statement of Requirements.
Types of Documents
© 2015 PTIG34
PTIG - Project 25 Technology Interest Group IWCE 2015
Core Definition documents are those TIA-102 standards documents
that enable manufacturers to independently develop and implement
interoperable equipment.
Test Documents are those TIA-102 standards documents that enable
manufacturers to verify that their product implementation adheres to
the respective core definition documents
The TIA-102 suite of standards are in various stages of completion for
each of the P25 Interfaces and Services
Project 25: Enabling Interoperability
CORE DEFINITION DOCUMENTS
TESTING DOCUMENTS
USED TO ENABLE DEVELOPMENT
USED TO VERIFY IMPLEMENTATION
TIA-102
STANDARDS
DOCUMENTS
© 2015 PTIG35
PTIG - Project 25 Technology Interest Group IWCE 2015
• Conformance Testing – Conformance testing includes verification of the messages as specified
in the P25 standard
• Performance Testing – Performance testing includes measurements that verify product
specifications as specified in the P25 standard
• Interoperability Testing – Interoperability testing includes functional testing between
manufacturer A’s equipment and manufacturer B’s equipment per the Project 25 standard
• Recommended Compliance Assessment Tests (RCAT)– Subset of tests collected from above test documents related to a
specific interface or service
Testing Documents
© 2015 PTIG36
PTIG - Project 25 Technology Interest Group IWCE 2015
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
© 2015 PTIG37
PTIG - Project 25 Technology Interest Group IWCE 2015
• Designed for public safety by public safety
• Developed in partnership between APCO 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 toTDMA 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
© 2015 PTIG38
PTIG - Project 25 Technology Interest Group IWCE 2015
Neil Horden
Chief Consultant
Federal Engineering, Inc.“Unleashing the Power of Technology”
Thank You!
Presented by:PTIG - The Project 25 Technology Interest Group
www.project25.org – Booth 1853
Sponsored by:
IWCE 2015, Las Vegas, NevadaMarch 16, 2015
Presented by:
PTIG - The Project 25 Technology Interest Groupwww.project25.org – Booth 1853
Project 25 College of Technology
© 2015 PTIG
Project 25 Conventional System Configurations and Wireline Interfaces
Darek Wieczorek, Tait Radio
Sponsored by:
© 2015 PTIG40
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25: Interfaces & Services
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
Trunking/Conventional
TRUNKING/CONVENTIONAL
© 2015 PTIG41
PTIG - Project 25 Technology Interest Group IWCE 2015
Network Management
P25 General Systems Model
Adopted from TSB-102-B
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
Telephone
Interconnect
Fixed
Station
Trunked
Console Sub System
Interface ISSI
Inter RF Sub System Interface
ISSI/CSSI
Conventional
FSI
RF Subsystem B (Trunked RFSS)
TO PSTN
RF Subsystem A (Trunked RFSS)
Eg
Ec
Et
Ec
RF Subsystem C (Conventional RFSS)
Console Sub-
system
Data Network Interface
MDP Int.
Trunked
FDMA/TDMA
CAI
KFD Int.
Ed
MDP Int.
A
v7
A
Ef
Conventional
Console Sub System
Interface
CSSI
Ed
KMF
KMF
En
P25
Conventional
CAIFS
© 2015 PTIG42
PTIG - Project 25 Technology Interest Group IWCE 2015
ConventionalStandard Interfaces and Services
• Configurations Using the FDMA Common Air Interface
• Voice/Supplementary Services
• Adding Data
• Configurations Using Wireline Interfaces
• Fixed Station Interface
• Conventional Console Subsystem Interface
© 2015 PTIG43
PTIG - Project 25 Technology Interest Group IWCE 2015
FDMA CAI
Conventional ConfigurationsVoice and Supplementary 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 Capability Guide
Direct
© 2015 PTIG44
PTIG - Project 25 Technology Interest Group IWCE 2015
• 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
Conventional ConfigurationsVoice and Supplementary Services
Repeated
© 2015 PTIG45
PTIG - Project 25 Technology Interest Group IWCE 2015
Conventional ConfigurationsVoice and Supplementary Services
• 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 CAIFDMA CAI
© 2015 PTIG46
PTIG - Project 25 Technology Interest Group IWCE 2015
Conventional ConfigurationsVoice and Supplementary Services
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
Repeated with Wireline Dispatch
© 2015 PTIG47
PTIG - Project 25 Technology Interest Group IWCE 2015
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 Capability Guide
© 2015 PTIG48
PTIG - Project 25 Technology Interest Group IWCE 2015
FDMA CAI
Repeated
MDP Int.
FDMA CAI
MDP Int.CONVENTIONAL
RF Sub-System A
Conventional ConfigurationsAdding Data
• Fixed Station repeats the data signal•Note: 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 Capability Guide
© 2015 PTIG49
PTIG - Project 25 Technology Interest Group IWCE 2015
FDMA CAI
RF Sub-System BDataHost
Data Host Network Int.Data Gateway
MDP Int.
Fixed Network Data
Conventional ConfigurationsAdding Data
• 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 datagrams
•Note: 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 Capability Guide
© 2015 PTIG50
PTIG - Project 25 Technology Interest Group IWCE 2015
FDMA CAI
RF Sub-System B
DataHostData Host Network Int.
KFD Int.
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
Data Gateway
© 2015 PTIG51
PTIG - Project 25 Technology Interest Group IWCE 2015
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
© 2015 PTIG52
PTIG - Project 25 Technology Interest Group IWCE 2015
ConventionalFSI – Fixed Station Interface Configurations
RF Sub-System A
FixedStn
HostDigital FSI-EF
dFSI
FDMA CAI-Um
• Voting or multicast sub-system requires DFSI• Capabilities of FSI + Fixed Station Sub-System working together
vary considerably • Certain capabilities subject to equipment configurations•Note: PTIG Capability Guide is currently being updated to include capabilities associated
with these combinations of AFSI/DFSI and Analog/FDMA CAI air interfaces
Multiple Station Subsystem
Fixed Station Sub-System B
RcvAudioVoting
AudioDist
Xmit
Rcv Audio
Xmit Audio
Voted Audio
Rcv
Xmit
© 2015 PTIG53
PTIG - Project 25 Technology Interest Group IWCE 2015
Digital FSI
DFSI
Analog FSI
AFSI
or
ConventionalConsole and Fixed Station Interface Configurations
• 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
Fixed Station Sub-System AConsole Sub-
System A
Analog Air Int.
FDMA CAI
© 2015 PTIG54
PTIG - Project 25 Technology Interest Group IWCE 2015
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
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 B
A
© 2015 PTIG55
PTIG - Project 25 Technology Interest Group IWCE 2015
ConventionalFSI – Fixed Station Interface Configurations
Fixed StationSUB-SYSTEM A
Analog Air Int.
RF Sub-System A
FixedStnHost
Digital FSI
DFSI
Analog FSI
AFSI
or
FDMA CAI
• AFSI: • Use with either Air Interface• 2 or 4 wire analog transport, • clear analog voice, • Tone Remote Control
Single Station Subsystem
• DFSI: • Use with either Air
Interface• IPv4 digital transport, • P25 (clear or encrypted) or
PCM audio, • P25 control signaling
© 2015 PTIG56
PTIG - Project 25 Technology Interest Group IWCE 2015
Darek Wieczorek, Tait Radio
Thank You!
Presented by:PTIG - The Project 25 Technology Interest Group
www.project25.org – Booth 1853
Sponsored by:
IWCE 2015, Las Vegas, NevadaMarch 16, 2015
Presented by:
PTIG - The Project 25 Technology Interest Groupwww.project25.org – Booth 1853
Project 25 College of Technology
© 2015 PTIG
Project 25 Trunking System Configurations & Wireline Interfaces
+ (How to Avoid ID Duplication)Cheryl Giggetts
Senior Vice President, Technology Solutions
Sponsored by:
© 2015 PTIG58
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25 TrunkingAgenda Topics
• Introduction to P25 Trunking Interfaces• P25 Trunking Common Air Interface (CAI) Overview
• P25 Trunking Basic Services
• Single and Multi Site Configurations
• P25 Packet Data Services
• P25 Trunking Wireline Interfaces Overview• ISSI & CSSI Overview
• P25 ISSI & CSSI Multi-System Use Cases
• Telephone Interconnect
• Network Management Interface
• Avoiding ID Duplication
© 2015 PTIG59
PTIG - Project 25 Technology Interest Group IWCE 2015
Adopted from TSB-102-B
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
Fixed
Station
Conventional
FSI
Ec
RF Subsystem C (Conventional RFSS)
KFD Int.
MDP Int.
A
v8
Ef
Conventional
Console Sub System
Interface
CSSI
P25
Conventional
CAI
FS
P25 General Systems Model
MDP Int.
Network Management
Telephone
Interconnect
Trunked
Console Sub System
Interface
ISSI
Inter RF Sub System Interface
ISSI/CSSI
RF Subsystem B (Trunked RFSS)
TO PSTN
RF Subsystem A (Trunked RFSS)
Eg
Et
Ec
Console Sub-
system
Data Network Interface
Trunked
FDMA/TDMA
CAI
Ed
Ed
KMF KMF
En
CC WC WC WC
© 2015 PTIG60
PTIG - Project 25 Technology Interest Group IWCE 2015
Network Management
P25 General Systems Model
Adopted from TSB-102-B
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
Telephone
Interconnect
Fixed
Station
Trunked
Console Sub System
Interface
ISSI
Inter RF Sub System Interface
ISSI/CSSI
Conventional
FSI
RF Subsystem B (Trunked RFSS)
TO PSTN
RF Subsystem A (Trunked RFSS)
Eg
Ec
Et
Ec
RF Subsystem C (Conventional RFSS)
Console Sub-
system
Data Network Interface
MDP Int.
Trunked
FDMA/TDMA
CAI
KFD Int.
Ed
v7
Ef
Conventional
Console Sub System
Interface
CSSI
Ed
KMF KMF
En
MDP Int.
A
P25
Conventional
CAI
FS
CC WC WC WC
Trunking
Conventional
© 2015 PTIG61
PTIG - Project 25 Technology Interest Group IWCE 2015
RF Subsystem
(Trunked RFSS)Trunked
FDMA/TDMA
CAI
•Operates on 12.5 kHz Narrowband Channels
•Supports Integrated Voice and Data
•Supports 256 bit AES Encryption
• Control Channel (CC) - 9600 bps FDMA
•Traffic Channels
• Voice FDMA: 1 Talkpath / channel - 9600 bps • Voice TDMA: 2 Talkpaths/channel - 12000 bps (2x efficiency)• DATA FDMA: 9600 bps
CC WC WC WC
Project 25 Trunking Common Air Interface (CAI)
© 2015 PTIG62
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25 TrunkingCommon Air Interface (CAI)
All operate on 12.5 kHz Narrowband Channels
P25 TDMA (Phase 2)
VOICE Services
• 2 talkpaths per channel
• 12000 bps OTA bit rate
• Half Rate AMBE Vocoder
• Requires TDMA-capable radios
• Supports Encrypted Mode
P25 PACKET
DATA Services
• 9600 bps OTA bit rate
• Supports Integrated
Voice & Data
P25 FDMA (Phase 1)
VOICE Services
• 1 talkpath per channel
• 9600 bps OTA bit rate
• Full Rate IMBE or AMBE Vocoder
• Supports Encrypted Mode
Control Channel
• Controls traffic on the network
• 9600 bps OTA bit rate
• Assigns to FDMA or TDMA Voice
or DATA
CC
© 2015 PTIG63
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 FDMA (Phase 1) - 2 Voice Talkpaths / 1 Data
P25 TDMA (Phase 2) - 3 Voice Talkpaths / 1 Data
FDMA ControlChannel
FDMA ControlChannel
12.5 kHz 12.5 kHz 12.5 kHz 12.5 kHz
12.5 kHz 12.5 kHz
FDMA Voice
Channel
FDMA Voice
Channel
FDMA Voice
Channel
FDMA Data
Channel
FDMA Data
Channel
12.5 kHz12.5 kHz
TDMA Voice
TDMA Voice
P25 CAI Examples for 4 Channel Systems
© 2015 PTIG64
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Trunking - Basic Services
• Integrated Voice & Data Services
• Mobility & Registration
• End-to-End Voice & Data Encryption
• Supplementary Services– Radio Inhibit / Uninhibit
– Call Alert
– Emergency Alarm
– Priority Call
– Pre-emptive Priority
– Radio Check
– Discreet Listening
– Radio Unit Monitoring
– Short Message
• Telephone Interconnect
© 2015 PTIG65
PTIG - Project 25 Technology Interest Group IWCE 2015
System Configurations
• Single Site
• Multi Site
– Simulcast
– Multicast
Single Site Trunked RFSS
Project 25 Trunked
RF Sub-System
Multi-Site Trunked RFSS
Project 25 Trunked
RF Sub-System
WC WC WCCC
CC
CC
CC WC WC WC
WC WC WC
WC WC WC
© 2015 PTIG66
PTIG - Project 25 Technology Interest Group IWCE 2015
• 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 DataSERVICES
• 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
Project 25 Trunked
RF Sub-System
Data NetworkInterface
Hosts
Data Gateway
Subscriber Peripheral Interface
P25 CAI
DATA
CC
CC
CC CC CCWC WC WC WC WC WC WC WC WC
© 2015 PTIG67
PTIG - Project 25 Technology Interest Group IWCE 2015
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
© 2015 PTIG68
PTIG - Project 25 Technology Interest Group IWCE 2015
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.
© 2015 PTIG69
PTIG - Project 25 Technology Interest Group IWCE 2015
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
© 2015 PTIG70
PTIG - Project 25 Technology Interest Group IWCE 2015
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
© 2015 PTIG71
PTIG - Project 25 Technology Interest Group IWCE 2015
Telephone Interconnect (Et)
Telephone
Interconnect Et
PSTN
RF Subsystem A (Trunked RFSS)
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.
© 2015 PTIG72
PTIG - Project 25 Technology Interest Group IWCE 2015
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.
RF Subsystem B (Trunked RFSS)
Network Management
En
© 2015 PTIG73
PTIG - Project 25 Technology Interest Group IWCE 2015
Trunking ID Duplication
Planning is necessary to avoid 2 radios from having the same ID!
2 General Scenarios
1. Manage Radio IDs within your home system, or frequent visitors to your system
2. Manage Radio IDs for infrequent visitors to your system and special events
© 2015 PTIG74
PTIG - Project 25 Technology Interest Group IWCE 2015
Use the TIA-102 / P25 Addressing Rules
– Provides radios IDs that adhere to the Subscriber Unit ID standard WACN.System.UID
– Use the P25 Guidelines to Assign WACN & System IDs to find a good approach for your jurisdiction/domain
Trunking ID Duplication
© 2015 PTIG75
PTIG - Project 25 Technology Interest Group IWCE 2015
• If You Have Frequent Visitors…– Consider giving them a local ID on your home system
– Use the common feature where radios can have multiple IDs (multiple personalities)
Manual Roaming of “foreign” Users
– Roamers manually switch between multiple personalities - 1 for each visited system
– Roamer registers with WACN/SYSTEM ID of the visited system
– UID must be reserved for these roamers as if they were home to the system
– Temporary Working ID defaults to the UID
Trunking ID Duplication
© 2015 PTIG76
PTIG - Project 25 Technology Interest Group IWCE 2015
• If You Have Infrequent Visitors…
1) To kindly loan them RF Resources (ex: the FBI is in town)
2) I need help in a disaster or special event
Automatic Roaming of “foreign” Users
– Roamer uses their home system personality on visited systems
– Roamer registers with WACN/SYSTEM ID of their home system
– UID need only be unique in their home system
– Temporary Working ID is dynamically assigned from a pool of unused UIDs
Trunking ID Duplication
© 2015 PTIG77
PTIG - Project 25 Technology Interest Group IWCE 2015
• Again…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
Trunking ID Duplication
© 2015 PTIG78
PTIG - Project 25 Technology Interest Group IWCE 2015
Thank You!Cheryl Giggetts
Senior Vice President, Technology Solutionsemail: [email protected]
Presented by:PTIG - The Project 25 Technology Interest Group
www.project25.org – Booth 1853
Sponsored by:
IWCE 2015, Las Vegas, NevadaMarch 16, 2015
Presented by:
PTIG - The Project 25 Technology Interest Groupwww.project25.org – Booth 1853
Project 25 College of Technology
© 2015 PTIG
Project 25 Standards Activity Update
Andy Davis, Senior Resource Manager
Chair of TIA TR-8 Committee, Mobile and Personal Private Radio
Sponsored by:
© 2015 PTIG80
PTIG - Project 25 Technology Interest Group IWCE 2015
• Process Background
• 2014 Activity Summary
• 2015 Activity Summary
Agenda
© 2015 PTIG82
PTIG - Project 25 Technology Interest Group IWCE 2015
Project 25 Steering
Committee (users)
APCO P25 Interface
Committee (users & manufacturers)
Telecommunications Industry
Association (TIA), TR.8 Committee(s)
User
needs
P25 Process Background:From SoR to Publication
• P25 Statement of Requirements (SoR)
• Maintained by P25 User Needs Subcommittee
• Drives P25 Standard content
• APIC drafts new documents
• Industry and Users collaborate
• Drafts forwarded to TR-8 via Steering Committee
• TR-8 subcommittees prepare, publish and maintain TIA-102 series documents
• Standards and Bulletins
• Steering Committee P25 document adoption decision prior to TIA publication
© 2015 PTIG83
PTIG - Project 25 Technology Interest Group IWCE 2015
• The P25 Standard is not just one document.
• It is a suite of over 65 Standard documents and over 20 TIA
Telecommunication Systems Bulletins.
• P25 Steering Committee Approved List of Documents• http://www.project25.org/images/stories/ptig/docs/20151028-P25Approved-TIA-StandardsQ4-2014.pdf
P25 Process Background:P25 Suite of Standards
CORE DEFINITION DOCUMENTS
TESTING DOCUMENTS
USED TO ENABLE DEVELOPMENT
USED TO VERIFY IMPLEMENTATION
TIA-102
STANDARDS
DOCUMENTS
• Core Definition documents are those TIA-102 standards documents that
enable manufacturers to independently develop and implement interoperable
equipment.
• Test documents are those TIA-102 standards documents that enable
manufacturers to verify that their product implementation adheres to the
respective core definition documents in a consistent manner
© 2015 PTIG84
PTIG - Project 25 Technology Interest Group IWCE 2015
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
Trunking/Conventional
TRUNKING/CONVENTIONAL
P25 Process Background:P25 Suite of Standards
© 2015 PTIG85
PTIG - Project 25 Technology Interest Group IWCE 2015
2014 Activity Summary (1)
• Air Interfaces
• A standard for Dynamic Regrouping for the Air Interface was
approved for publication.
• The dynamic regrouping function was formerly manufacturer
specific. The new P25 Dynamic Regrouping Standard creates a
common specification for multi-vendor interoperability.
• A revision of the Trunking Procedures Standard was approved
for publication.
• The revision corrects several errata that have been noted since
the last publication.
• A revision of the TDMA Transceiver Measurement Methods,
TDMA Transceiver Performance Recommendations Standards
were approved for publication.
• A new test and associated performance specs were added.
© 2015 PTIG86
PTIG - Project 25 Technology Interest Group IWCE 2015
2014 Activity Summary (2)
• Security
• A revision of the OTAR standard (multi-year effort) was
approved for publication.
• The Standard was clarified to prevent interoperability issues as an
increasing number of vendors implement P25 OTAR.
• A revision of the Key Fill Interface for mobiles and portables
was approved for publication.
• USB and RS-232 interfaces were included to expand applications
and devices available.
• An Addendum to the Security Services Overview standard was
approved for publication.
• The addendum adds an Informative overview of the key
management service as it applies to voice, data, and
authentication.
© 2015 PTIG87
PTIG - Project 25 Technology Interest Group IWCE 2015
2014 Activity Summary (3)
• Data
• A revision of the IP Data Bearer Services Specification was
approved for publication.
• The Standard was clarified to prevent interoperability issues as an
increasing number of vendors implement P25 Data applications.
• A revision of the Tier 1 Location Standard was approved for
publication.
• The Standard was clarified to prevent interoperability issues as an
increasing number of vendors implement P25 Location Standard
Data applications.
• Wireline Interfaces
• A revision of the ISSI Interoperability Tests to include TDMA
was approved for publication.
• The revisions adds a standard testing method of new Phase 2
TDMA systems interconnected with FDMA systems using the P25
ISSI multi-system interface
© 2015 PTIG88
PTIG - Project 25 Technology Interest Group IWCE 2015
2015 Activity Summary (1)
• Data
• A revision of the Tier 2 Location Standard was approved for publication
• The Standard was clarified to prevent interoperability issues as an
increasing number of vendors implement P25 Location services.
• Air Interfaces
• A revision of the Trunking Control Channel Messages Standard was approved
for publication
• The revision corrects several errata that have been noted since the last
publication.
• A revision of the Link Control Word Formats and Messages Standard was
approved for publication
• The revision corrects several errata that have been noted since the last
publication.
• A revision of the Conventional Conformance Tests, Basic and Advanced
completed ballot
• The revisions update the list of standard references and correct some
errata noted since the last publication
© 2015 PTIG89
PTIG - Project 25 Technology Interest Group IWCE 2015
2015 Activity Summary (2)
• Compliance Assessment Bulletins
• TIA subject matter experts review published TIA test documents and
recommend tests appropriate for use in P25 Compliance Assessment
• The list of tests are documented in Recommended Compliance Assessment Test
(RCAT) Telecommunications System Bulletins
• The Steering Committee may then forward these to the DHS Compliance
Assessment Program Governing Board for consideration when creating Compliance
Assessment Bulletins (Testing CABs)
• A revision to multiple RCATs were approved for publication
• RCAT for Trunked Interoperability (FDMA and TDMA tests)
• RCAT for TDMA Voice Channel Air Interface (Conformance and Performance tests)
• RCAT for Conventional Mode Fixed Station Performance
• RCAT for Conventional Mode Subscriber Performance
• RCAT for Trunked Mode Subscriber Performance
• RCAT for Trunked Mode Fixed Station Performance
• These revision efforts primarily update all references to TIA published test
documents. The FDMA Trunking Interoperability testing RCAT was also revised to
include Trunking Conformance test recommendations.
© 2015 PTIG90
PTIG - Project 25 Technology Interest Group IWCE 2015
2015 Work in Progress (1)• Security
• Link Layer Encryption is in progress.
• This is a significant technology upgrade effort for improved Security for all air
interfaces of P25. It protects control channel control messages, and hides group and
individual IDs.
• An addendum to the Key Fill Interface standard is in progress.
• This will enable Key Fill Device (KVL) interface to a KMF, an Authentication Facility
and another Key Fill Device
• A revision to the OTAR Interoperability Test Standard is in progress.
• This revision will align the Interoperability tests with the recently revised OTAR
Messages and Procedures Standard.
• Wireline Interfaces
• 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.
© 2015 PTIG91
PTIG - Project 25 Technology Interest Group IWCE 2015
2015 Work in Progress (2)• Air Interfaces
• A revision to the Conventional Procedures Standard is in progress.
• This revision provides additional detail for the procedures associated with
Conventional Data and a number of errata comments that have been noted since the
last publication.
• A revision to the Trunking Procedures Standard is in progress.
• This revision provides additional detail for the procedures associated with Trunking
Data
© 2015 PTIG92
PTIG - Project 25 Technology Interest Group IWCE 2015
PROJECT 25 TECHNOLOGY INTEREST GROUP
CAPABILITIES GUIDE
http://www.project25.org/images/stories/ptig/11-022-R10_PTIG_P25Capabilities_Guide_9.29.14.pdf
© 2015 PTIG93
PTIG - Project 25 Technology Interest Group IWCE 2015
• Background and Purpose of the Guide
• Organization of the Guide
• Tables in the Guide
• Table Examples: Subscriber Interfaces
• Table Examples: Fixed Network Equipment
Interfaces
Agenda
© 2015 PTIG94
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Background and Purpose
PTIG’s P25 Capabilities Guide was created and is maintained by a Working Group within PTIG
–Manufacturer and User Agency representatives active in P25/TIA-102 Standards
Intended to be an aid to identify what P25 Interfaces, Services and Functionality are covered by published P25/TIA-102 Standards
–Customers may use the guide to spec standard equipment capabilities in bid situations–Neighboring system operators may use the guide to compare existing standard capabilities to set interoperability expectations–Manufacturers may use the guide to identify supported standard capabilities
P25/TIA-102 Standard content is traceable to the P25 Statement of Requirements (P25 SoR)
–P25/TIA-102 Standard content is driven by the P25 Statement of Requirements
Not all P25 SoR content is traceable to published P25/TIA-102 Standards
–P25 SoR includes important equipment capabilities unrelated to interoperability–P25/TIA Standard creation lags SoR updates–P25 Steering Committee, P25 User Needs Subcommittee, APIC Task Groups and TR-8 subcommittees collaborate on standards work priorities
© 2015 PTIG95
PTIG - Project 25 Technology Interest Group IWCE 2015
Capabilities Guide • Identifies Interfaces, Services and Functionality/Features in the published standards
• Organized into functional areas (Trunking or Conventional, Subscribers or Infrastructure)
P25 Capabilities Guide;Organization
© 2015 PTIG96
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Tables
Summary and Detailed Tables• Each section has a Summary Table listing the major categories of “features”
• Each section has a Detailed Table which expands the major categories into “features”
© 2015 PTIG97
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Summary Table Example; SubscriberSummary Table Example• This summary table shows 4 major categories of Voice Services
• Columns for the P25 Subscriber Interfaces (FDMA CAI and Analog)– Black shading in header rows
– Grey shading in individual table cells (feature category not related to the interface)
– Blank cells (feature category supported by the interface)
© 2015 PTIG98
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Detailed Table Example; Subscriber
© 2015 PTIG99
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Detailed Table Example; Subscriber
Detailed Table Example• The Detailed table expands each of the 4 major categories of Voice
Services to list out individual Voice Service category “features”
• Column for the P25 Common Air Interface and an Analog Air Interface
• Additional column for Analog Air Interface with “signaling”– “De Facto” standard examples include but are not limited to: CTCSS, DCS, MDC-1200,
Type 99, GE-STAR
– Grey cell shading indicates the feature is not supported in the standards for the interface
• Additional column for published document references– Published documents contain details of standard feature operation
• Additional column for SoR traceability– Next version will add SoR references
© 2015 PTIG100
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Summary Table Example; FNE
Summary Table Example• This summary table shows 5 major categories of Voice Services
• Columns for the P25 Fixed Network Equipment Interfaces (FDMA CAI and ISSI/CSSI)– For Trunking, a single set of protocols (SIP & RTP) are used for both a Trunked ISSI and/or
a Trunked CSSI application
– the majority of features apply to both applications
© 2015 PTIG101
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Detailed Table Example; FNE
Detailed Table Example; Voice Services• This table expands the Voice Service category “features”
• Grey cell shading indicates the feature is not relevant to or supported by the interface
© 2015 PTIG102
PTIG - Project 25 Technology Interest Group IWCE 2015
P25 Capabilities Guide;Detailed Table Example; FNE
Detailed Table Example; RF Sub System (RFSS) Roles and Capabilities• This table shows the different RF Sub System Roles and Capabilities supported by the
Standard
• The capabilities of the RF Sub System with Console equipment dictates whether a particular interface is acting as a Trunked ISSI or a Trunked CSSI.
• Based on these points, the RFSS Roles and Capabilities section can be used to differentiate a Trunked ISSI or Trunked CSSI application
© 2015 PTIG103
PTIG - Project 25 Technology Interest Group IWCE 2015
Thank You!
Andy Davis, Senior Resource ManagerChairman of TIA TR-8 Committee; Mobile and Personal Private Radio
email: [email protected]
Sponsored by:
Presented by:PTIG - The Project 25 Technology Interest Group
www.project25.org – Booth 1853