1 / 30

April 10-12, 2007

The National Institute of Standards and Technology: Office of Law Enforcement Standards Public Safety Communications Program SDO Emergency Services Coordination Workshop (ESW07) Washington , DC. April 10-12, 2007. Overview. Arthur Webster (NTIA/ITS) for NIST/OLES

shilah
Download Presentation

April 10-12, 2007

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

E N D

Presentation Transcript

  1. The National Institute of Standards and Technology: Office of Law Enforcement Standards Public Safety Communications Program SDO Emergency Services Coordination Workshop (ESW07) Washington, DC April 10-12, 2007

  2. Overview Arthur Webster (NTIA/ITS) for NIST/OLES • Part of the U.S. Department of Commerce • The mission of OLES • Partners • Interoperability • How we define it for Public Safety Communications • The Public Safety Communications Continuum • What NIST/OLES is doing • Public Safety Statement of Requirements (PS SoR) • The Public Safety Architecture Framework (PSAF) • P25 Standards • P25 Conformity Assessment Program • Public Safety and VoIP

  3. Mission The mission of OLES is to support the public safety community and federal agencies in the following areas: Standards Development Testing and Evaluation Research Technical Documents Housed within NIST’s EEEL Laboratory, OLES program managers are able to make available the world class scientific and engineering expertise found within the Department of Commerce laboratories April 10-12, 2007

  4. Sponsoring Federal Agencies • OLES receives its funding for the Public Safety Communications Program from two key Federal Sponsors: • DHS’s OIC Program • DOJ COPS Office

  5. OLES and ITS • For over a decade, in addition to using NIST scientific expertise, NIST OLES has leveraged the world class engineering expertise at the National Telecommunications and Information Administration’s (NTIA) Institute of Telecommunication Sciences (ITS) in Boulder, Colorado • ITS is a core component of the NIST OLES PS Communications Program, serving as the technical lead, with OLES providing management and policy oversight

  6. The Definition of Interoperability • The ability for public safety personnel from multiple jurisdictions and/or disciplines to communicate via voice, video, or data: • On demand • In real time • When needed • When authorized • The operations should also be transparent to the user.

  7. Operability versus Interoperability:Hurricane Katrina • Public safety must first have reliable intraagency communications before they can have interagency communications or interoperability. • Hurricane Katrina was seen by many as yet another case of failed interoperability. When in fact, Katrina was an example of failed operability of the numerous public safety systems around the Gulf Coast.

  8. Operability versus Interoperability:Hurricane Katrina • The five most common communications issues found in the multiple reports on Hurricane Katrina: • Tower/Infrastructure failures • Power failures • PSTN failure • Lack of planning for large scale system failures • No stand alone deployable systems

  9. 1. INCOMPATIBLE and AGING communications equipment Interoperability Challenges 5. Limited equipment STANDARDS 2. Limited and fragmented budget cycles and FUNDING 3. Limited and fragmented PLANNING and COORDINATION 4. Limited and fragmented radio SPECTRUM The Five Key Challenges to Interoperability

  10. It’s Not All About the Technology • In 2004, SAFECOM, in partnership with several Federal Programs, was charged with improving the communications capability of the 10 highest risk urban areas. • The general consensus among participating agencies was that jurisdictions would be seeking mobile gateway systems to improve multi-agency response capabilities. • And then the visits began……….

  11. The Public Safety Communications Continuum

  12. So Why Don’t They Just Use Cell Phones? • The cellular networks rely on the PSTN as the backbone of the nationwide network. • In a large scale emergency…THE PSTN IS THE FIRST TO BECOME UNUSABLE!!!!! • Public safety relies on one-to-many communications and dispatch services. • Talk around mode • Priority access • Higher Quality of Service (QoS) requirements

  13. Open vs. Proprietary Networks and Equipment • Why are the two markets different? • What has changed so that LMR is now moving towards open standards? • Large scale disasters like 9/11 and Katrina • The creation of large Federal grant programs wanting to tie funding to standards • Congressional direction • Broad government partnership building and the creation of SAFECOM

  14. A Comprehensive Approach

  15. Public Safety Statement of Requirements (PS SoR) • The PS SoR is a practitioner created set of communications requirements • It is a living document • Volume I, Version 1.0 • Released in April 2004 • Focused on qualitative requirements • Volume I, Version 1.1 • Released in the spring of 2006 • Volume I, Version 1.2 • Released in December of 2006 • Volume II, Version 1.0 • Released in December of 2006 • Focuses on quantitative, quality of service requirements

  16. Conceptual Network Diagram

  17. NIST and Volume II of the PS SoR • Between DHS’s OIC and NIST we will see the largest single investment into defining quantitative parameters for Public Safety Communications Requirements • NIST, with funding from OIC and COPS has undertaken research in the following areas: • Voice quality requirements • Video quality requirements • Network requirements to allow for voice, video, and data transmission without quality degradation • Public Safety network simulations (i.e., spectrum requirements, signal propagation, mobility) • Identification of existing standards that could be modified to meet public safety’s personal area and incident area network requirements

  18. PSAF: The WHAT and HOW • The Public Safety Architecture Framework (PSAF) will comprehensively describe WHAT the overall structured approach is to achieve a system-of-systems for nationwide interoperability • Interface Standards define HOW the elements of the Architecture Framework will work together. That is, HOW interoperability through a system-of-systems approach will be achieved.

  19. The Project 25 Interfaces

  20. Project 25 • The goal of P25 is the development of a suite of consensus-based open standards for Private Wireless digital radio equipment. P25 has always been driven by these five key goals: • Competition in system life-cycle procurements; • Graceful system migration; • Communications interoperability; • Spectrum efficiency; and • User-friendly equipment.

  21. Project 25 Acceleration • NIST and its Federal partners are working with the Project 25 Steering Committee to identify set timelines for the publishing of: • Inter-RF-Subsystem Interface • Fixed Station Interface • Console Interface • In addition, if the current TIA process is unable to meet the immediate needs of the Steering Committee and the Federal programs, an alternate process is being developed which will lead to interim technical requirements and guidelines until standards are published • These technical requirements and guidelines will be applied to federal grants and procurement contracts until standards are adopted • We have achieved critical objectives over the last 12 months

  22. Project 25 Acceleration • Recent Progress in ISSI Standards: • TIA TR-8 Approved the following 7 Letter Ballots on April 4, 2007: 1. TIA-102.CACA ISSI Measurement Methods 2. TIA-102.CACB ISSI Performance Recommendations 3. TIA-102.BACD Supplementary Data ISSI M&P 4. TIA-102.CADA FSI Conformance Test 5. TIA-102.BACA-1 ISSI M&P Addendum 1: Errata 1 6. TIA-102.BACA-2 ISSI M&P Addendum 2: Trunked Console ISSI 7. TIA-102.BACA-3 ISSI M&P Addendum 3: Supplementary Data ISSI

  23. The Confidence Connection • Public safety must have confidence that the P25 equipment being purchased does what the standard requires! • The government programs requiring P25 acquisition through federal grants must have confidence that the equipment required operates to the standard! • There is currently no mechanism to ensure compliance

  24. The Problem • Performance Testing • Identified radios in the federal inventory certified by the vendor as TIA-102 compliant which are not compliant • Discovered widespread differences in quality of receivers—especially in the wideband analog mode • Two models of radio operating in wideband analog mode subject to the same levels of adjacent-channel interference • Radio #1Radio #2

  25. certification 3rd party conformity assessment Perceived Risk Supplier’s declaration 1st party conformity assessment Independence and Rigor of Conformity Assessment

  26. P25 Conformity Assessment Program • Components: • Grant guidance requiring P25 products purchased with federal funds meet the requirements of the conformity assessment program • 3rd party type testing to evaluate compliance to requirements of the P25 Standard by accredited laboratories • Formal suppliers declaration of conformity to P25 requirements with results made available to public safety

  27. Public Safety and VoIP Issue • Manufacturers are coming to public safety officials and telling them that they should use Voice over Internet Protocol (VoIP) to solve their interoperability issues. In fact, the different manufacturers’ VoIP implementations are non-interoperable, thus creating additional interoperability issues. Strategy • Bring public safety and industry together to define public safety’s VoIP requirements and provide a forum for the manufacturers to develop standardized VoIP implementations that will interoperate.

  28. The Problem Space

  29. Roundtable on Public Safety VoIPAugust 06, February 07, May 07 • Strategic Direction • Confirmed and prioritized public safety specific environments for VoIP application • Created laymen’s terms for each environment • Agreed upon a framework for an implementation profile* • Technical Specifics • Defined requirements for Bridging Systems Interface • Defined high-level approach for completing the Bridging Systems Interface implementation profile • Defined action plan for continuing the work of developing an implementation profile for Bridging Systems Interface • Conclusions • A good foundation for developing VoIP standards in public safety communications • Buy-in from industry, including an action plan, to continue the work of developing an implementation profile for Bridging Systems Interface * The minimum set of standards parameters and values necessary to ensure interoperability in any of the given environments described.

  30. Thank You CONTACTS Kathy Higgins, Director of NIST/OLES kathleen.higgins@nist.gov Dereck Orr, Program Manager, NIST/OLES dereck.orr@nist.gov Jeff Bratcher, Division Chief, NTIA/ITS.P jbratcher@its.bldrdoc.gov Arthur Webster, Team Lead, Standards Development Team, NTIA/ITS.P webster@its.bldrdoc.gov

More Related