Project 25 Equipment Testing

Transcription

1 Project 25 Technology Interest Group 1 Project 25 Equipment Testing Nick Pennance

2 Project 25 Technology Interest Group 2 Interoperability is the Goal The list of available P25 equipment is growing Different features and functionality Many different manufactures The number of available options and features is growing Does all P25 equipment support the options you need? P25 is a suit of open standard interfaces The number of interfaces is evolving and growing. How do you ensure it all works together?

3 Project 25 Technology Interest Group 3 Project 25 Key Interfaces AIR INTERACES WIRELINE INTERFACES SECURITY INTERFACES DATA INTERFACES DATA APPLICATIONS KMF KMF Gateway Gateway ISSI/CSSI INTER- KMF DATA NETWORK LOCATION (eg GPS) P25 FDMA COMMON AIR INTERFACE TRUNKING OPERATION CONVENTIONAL OPERATION FSI Key Fill Device KEY FILL SUBSCRIBER DATA PERIPHERAL KMF OTAR P25 TDMA COMMON AIR INTERFACE TRUNKING OPERATION NETWORK MANAGEMENT PSTN KEY RF Site TELEPHONE INTERCONNECT P25 System

4 Project 25 Technology Interest Group 4 Getting to Multi-Manufacturer Interoperability TIA-102 STANDARDS DOCUMENTS CORE DEFINITION DOCUMENTS TESTING DOCUMENTS USED TO ENABLE DEVELOPMENT USED TO VERIFY IMPLEMENTATION 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

5 Project 25 Technology Interest Group 5 Types of Tests TIA publishes? Interoperability Testing Interoperability testing includes functional testing between manufacturer A s equipment and manufacturer B s equipment per the Project 25 standard. Performance Testing Performance testing includes measurements that verify product specifications as specified in the P25 standard. Conformance Testing Conformance testing includes verification of the messages as specified in the P25 standard. Recommended Compliance Assessment Tests (RCAT) Subset of tests collected from above test documents related to a specific interface or service. This is vetted out in the TIA forum to provide a reasonable level of testing to insure proper operation among multiple manufacturers

6 Project 25 Technology Interest Group 6 Where does this testing occur? Best practice has industry running Conformance and Performance tests during development in manufacturer specific labs. Once a product is released multi-manufacturer interoperability testing can occur. This has been demonstrated in multi-manufacturer events both as part of the CAP program as well as independent of the CAP program. For P25 CAP testing must be conducted in recognized labs per grant guidance A rigorous on-site assessment of each laboratory is performed for technical competence and quality system management. This evaluation process ensures that tests are conducted correctly and the results are reliable.

7 Project 25 Technology Interest Group 7 TIA tests are currently published for P25 Common Air Interface P25 FDMA Common Air interface Conventional Performance Conventional Conformance Conventional Interoperability Trunking Performance Trunking Conformance basic services Trunking Conformance advanced services in progress Trunking Interoperability P25 TDMA Common Air interface Trunking Performance Trunking Conformance basic and advanced services Trunking Interoperability CAP Compliance Assessment Bulletin The CAB references a subset of TIA test procedures P25-CAB-CAI_TEST_REQ March 2010 includes: FDMA Conventional Performance FDMA Trunking Performance FDMA Trunking Interoperability

8 Project 25 Technology Interest Group 8 Compliance Assessment Program 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 Against a key subset of the P25 Standards Performed in CAP recognized labs Published results After testing SDOCs and STRs are published by the DHS on the Responder Knowledge Base

9 Project 25 Technology Interest Group 9 CAP Test Results Availability Project 25 Testing Results Posted by DHS on their RESPONDER KNOWLEDGE BASE: Supplier s Declaration of Compliance (SDoC) Declaration of P25 Compliance, includes Details of the tested Products. Details of the equipment tested against. Signature from the Manufacturer. Summary Test Reports (STR) Additional detail on the individual tests conducted on a product

10 Project 25 Technology Interest Group 10 CAP Certified? Each piece of P25 equipment must be tested with at least 3 manufactures P25 equipment. Each Piece of Subscriber equipment will be listed in at least 3 Network equipment's SDOC and STRS. Manufactures with published SDOCS and STRs Tait Kenwood Daniels EF Johnson Harris Motorola Icom Cassidian PowerTrunk Raytheon Simoco BK Relm Thales Datron

11 Project 25 Technology Interest Group 11 Requirements for your unique system Networks and Subscriber equipment do not need to be purchased together, or even from the same manufacture. Different user groups have different needs and requirements. Understand what you need and what is available early in the purchasing process. RFI Request for Information A great way to understand what each different manufacture can offer. Determine what aspects are important to you and your users. RPQ Request for PreQualification Determine what aspects are important to you and your users, and ensure the equipment meets those needs.

12 Project 25 Technology Interest Group 12 Testing Requirements for your unique system 1. Decide what interoperable P25 interfaces are important for your system (e.g. FDMA CAI, TDMA CAI, ISSI, CSSI, FSI) 2. Determine what features / services are important to you (e.g. Conventional operation, Encryption, OTAR, etc 3. Determine which features you would like to have interoperability between different manufacturers equipment. 4. Ask for testing results. A subset of P25 interfaces and features tested in CAP For those not covered in CAP look to TIA test documents For those not detailed in TIA test docs use Functional Acceptance Tests

13 Project 25 Technology Interest Group 13 Take away Understand what functionality is needed for the system and the needs of the users. Understand what different manufactures have and be open with your needs. Test results are good to have when selecting a manufacturer Use CAP test results when available not all P25 functionality covered by CAP When CAP results are not available request results of published TIA tests to ensure consistent test approaches When published TIA tests are not available work with the manufacturer to define tests that provide results of interest

14 Project 25 Technology Interest Group 14 Thank You Nick Pennance