Welcome to the NENA NG9-1-1 Tutorial

as of

March 6, 2011

[To see animation, run in PowerPoint presentation mode]

Intent of this Document

 Present information on NG9-1-1 and the transition to it  Provide a high level overview to make you conversant  Not a complete picture with all the details  Not intended to make anyone an expert in NG9-1-1

The 9-1-1 Service Process from Caller to Calltaker and Beyond

Caller Access Provider Service Provider* E9-1-1 Network PSAP CPE Telecommunicator

-

The Access Provider and the Service Provider are often the same company, but do not have to be.

- The E9-1-1 Network is usually built to support multiple

counties, but may be sold to individual counties.

-* There does not

have to be a Service Provider at all

E9-1-1 Components

(for wireline) Originating Calls Emergency Service Providers ILECs CO Selective Router CLECs CO Wireline Subscriber Records SR DB ALI DBMS MSAG Other ES Providers Primary PSAPs Secondary PSAPs

Add Cellular E9-1-1 Components

Originating Calls Emergency Service Providers ILECs CLECs CO CO Selective Router Other ES Providers Primary PSAPs WSPs MSC Cellular Dynamic Updates SR DB ALI PDE MPC Wireline Subscriber Records or Cellular Shell Records DBMS MSAG Secondary PSAPs Difficult and costly to integrate new call or messaging sources, and the corresponding data needs.

Adapt for VOIP - E9-1-1 Components

Originating Calls Emergency Service Providers ILECs CO CLECs VSPs

Customer Info

CO Interne t VPC ESGW Net

VoIP Dynamic Updates

Selective Router SR DB ALI Wireline Subscriber Records or VoIP Shell Records DBMS MSAG Other ES Providers Primary PSAPs Secondary PSAPs Difficult and costly to integrate new call or messaging sources, and the corresponding data needs.

What’s Driving NG9-1-1

- Newer Technologies/Services - Text, Image, Video, Telematics, Sensors, Subscriber Info - Improve Survivability - Network Resilience, Virtual PSAPs - Improve Interoperability and

Information Sharing

- Need to “Mainstream” 9-1-1

Technology

How NG9-1-1 is Different

-

Technology:

-Packet Based vs Circuit Switched - Functions: -Replicates E9-1-1 capabilities -Adds new capabilities -GIS vs Tabular MSAG -

No longer a ‘local’ service:

-Interoperability at county, region, state and national levels

NG9-1-1 Myths

 NG9-1-1 will cause a PSAP to be overwhelmed with more and new data elements from new types of devices  NG9-1-1 will improve wireless and nomadic VoIP E9-1-1 accuracy and routing  NG9-1-1 will make text-to-9-1-1 available to all callers  NG9-1-1 will eliminate prank or harassing calls



NG9-1-1 Myths

NG9-1-1 will enable call back to Non-Service Initialized (NSI) wireless handsets  NG9-1-1 will save money  All connected devices will know and report their own locations without action by the PSAP  NG9-1-1 will eliminate all known and unknown issues with E9-1-1 and usher in an era of peace and prosperity

NG9-1-1 Reality

• NG9-1-1 by itself will not enable text to 9-1-1 • NG9-1-1 is designed to support text when available • Standards work is underway in the wireless industry to support future types of text messages • NG9-1-1 will not eliminate prank or harassing calls • NG9-1-1 will not enable call back to NSI wireless devices

NG9-1-1 Reality

 NG9-1-1 will enable more - but it may not cost less.  In the short term, overall costs will be higher because legacy networks must be maintained while NG9-1-1 systems are being deployed  NG9-1-1 defines what information is desired/required from originating networks, but does not define how those networks function internally

WHERE ARE WE GOING AND HOW DO WE GET THERE?

E9-1-1 vs NG9-1-1

 Complex analog trunking and data network  Class 5 switch for Selective Router  Translation based control  Limited to voice calls  Data bandwidth 20 char (digits)  Complex Emergency Gateway Network for VoIP  Custom interfaces for each service type  Engineered, managed IP networks (ESInet)  IP software selective routing function  GIS and database controls  Voice, text, video  Bandwidth unlimited  Direct handling of Internet sourced calls  Standard IP interface for all service types

Transition



Two basic ways

 Conversion from today’s 9-1-1 direct to NENA defined NG9-1-1 using transitional interfaces  Using an interim IP system approach, then converting to NG9-1-1

Transitional NG9-1-1

 NG9-1-1 is designed to use IP end-to-end - where mainstream telecommunications is headed  To avoid major design changes in the future, the core architecture (NENA `i3’) is oriented to the expected end state In the meantime…  Gateways in and out will allow current OSP and PSAP interfaces to work during transition  Current cellular and VoIP location data processes are accommodated until they convert to IP interactions

Baseline NG9-1-1

 Describes a basic set of features & functions that constitute a NENA Standards-based Next Generation 9-1-1 solution, on the path to an end-state i3 architecture. ..

 …Must include the functions of today’s E9-1-1 system, replicated in IP protocol and structures as defined by NENA NG9-1-1 standards, including all network and PSAP components of the system …  …The basic ability to support non-voice multimedia, such as text and video.

NG9-1-1 Basics

NG9-1-1 System Procedures + Databases + i3 Architecture + ESInet within IP network

Terminology

 

Emergency Services IP Network (ESInet)

 A privately managed IP transport network that may be shared by multiple agencies i3 Standard requirements, architecture and functions  Including the Emergency Services Routing Proxy (ESRP) and the Emergency Call Routing Function (ECRF).



NG9-1-1

 The set of network elements, software applications, databases, CPE components, and operations & management procedures required to provide Next Generation emergency services.

• Combination of multiple transports .

• Can interface with other networks.

• Coexistence with other ES applications.

Page 20

ESInet

ESInet Concept

“I-95”

The blue lanes are for other non-emergency services

Poison Control N11 / CAD-to-CAD IP Radio 9-1-1 Law, Fire, EMS IP Network

The ESInet is the red lane on this data superhighway. NG9-1-1 and other emergency services application sets run on the ESInet.

IP network logical segment = ESInet for emergency services call traffic

NENA NG9-1-1 System

Geospatial DB GIS source data Service Operations Procedures Policy Rules and management Policy Rules DB Originating Service Providers: Wireline, Wireless, VoIP, etc i3 Architecture ESInet PSAPs PSAPs Other Emergency Entities

Page 23 PSTN CO/SR SS7 E-MF SS7 E-MF CO/SR CO/SR SS7 E-MF

NG9-1-1 System

NIF Functional Entities LIF “ALI” GIS ESInet DB Mgmt - GIS - ALI - Policy Routing etc LNG/L SRG PIF SIP LIS – Location Information Server HELD ETC LoST LoST ECRF – Emergency Call Routing Function SIP NG PSAP LNG/ LSRG - PIF SIP SIP BCF – Border Control Function SIP ESRP – Emergency Services Routing Proxy SIP SIP IP Host IP Host Client TDM LPG Internet and Other ESInet’s Legacy PSAP The `i3’ specification describes the technical functions and interfaces

Carrier TDM Networks Telematics / Telemetrics Providers Carrier IP Networks Internet Based Service Providers

NENA NG9-1-1 Elements

LNG BCF ESInet LVF Multi-Media PRF ECRF ESRP

NENA i3 or SIP capable PSAP

LIS Subscriber Database LPG

Legacy PSAP

NENA NG9-1-1 – i3 Elements

Simplified Diagram (with English subtitles!) Inputs Pictures, Video, Graphics Outputs Multi-Media

Carrier TDM Networks

Gateway 9-1-1 Call Routing Control ECRF ESRP

NENA i3 or SIP capable PSAP Telematics / Telemetrics Providers

LNG ESInet PRF Policy Routing Function Gateway

Carrier IP Networks

BCF Border Control Location Info LIS Subscriber LPG

Legacy PSAP

LVF

Internet Based Service Providers

Transitional NG9-1-1

(simplified) Originating Calls Emergency Service Providers \

ILECs CLECs

CO

GW

ESInets

WSPs

MSC

GW VSPs Customer Info Interne t

VPC

ECRF*

VoIP Dynamic Updates Wireline Subscriber Records and VoIP Shell Records

ESRP Selective Routing Function

ALI DBMS or LIS

ECRF Validation Other ES Providers Primary PSAPs Secondary PSAPs Mapping GIS

State or Regional IP Networking, IP software services, GIS and database controls *Emergency Call Routing Function is national level from Internet

Calls & Messages Enter

Three options from Originating Service Providers:  Through the current Selective Routing switch and a Legacy SR Gateway OSP SR LSRG NG9-1-1  Through a Network Gateway OSP LNG NG9-1-1  Direct via IP and SIP protocol OSP (IP/SIP) NG9-1-1 = IP

Calls & Messages Enter

 Through the current Selective Routing switch and a Legacy SR Gateway OSP SR LSRG NG9-1-1 but SR has split service: OSP SR Other Counties still on E9-1-1 LSRG for NG9-1-1 Counties = IP

Data Base Management

 GIS and Geospatial Routing DB  Validation  Routing Control  Policy Rules  Data Access rules  System Logging  Detail Call Records  Security

Long term NG9-1-1 Components

(simplified) Originating Calls Emergency Service Providers

ILECs CLECs

CO ESInets

Other ES Providers WSPs

MSC IP Selective Routing Function

Primary PSAPs VSPs Interne t

ECRF*

All interfaces to ESInet are IP and include caller location, data ECRF Secondary PSAPs

LVF Validation

Local GIS data is ‘published’ to user points GIS

\ * Emergency Calling Routing Function is national level from Internet

Mapping

The Nature of NG9-1-1

 Designed to support interoperability  Designed with open standards  Designed for and enables open competition by component through interface standards  Enables a transition to competitive service provider environment  Causes a need for regulatory (and legislative) change

NG9-1-1 Added Features

 GIS based routing control  Location data transported with the call  Additional types of calls and messaging  Additional data  Virtual PSAP capabilities  Added alternate routing options (ex: sensing PSAP status)  Direct control of call management [PRF]  ?

How an NG9-1-1 Call Works

Basic Call Flow in NG9-1-1 Lo cation to S ervice T ranslation (LoST) ECRF GIS GIS Data Layers

Originating Network

LIS

Device acquires location before a call is made Location Query to Location InformationServer(LIS) Location response (civic or geo) – pre-validated Device (or network) queries ECRF for routing ECRF provides next hop routing - ESRP 1

ESInet

34

Basic Call Flow in NG9-1-1 LoST ECRF LIS Can be ALI

Originating Network

ESRP 1

Call is placed Call is sent to ESRP 1 with the location LIS is re-queried for any updates to location ESRP queries ECRF for next hop

ESInet

35

Basic Call Flow in NG9-1-1 LoST ECRF

Originating Network

LIS ESRP 1 ESRP 2

ESInet

“Next Hop” Routing Call is sent to ESRP 2 with location LIS is re-queried to update location ECRF is queried for next hop

36

Basic Call Flow in NG9-1-1 LoST Policy Rules ESRP 1 PRF ESRP 2

Originating Network

LIS

“Next Hop” Routing

ESInet

Policy Rules are evaluated at each hop Call is sent with location to PSAP LIS is queried to obtain any updated location information

37

Basic Call Flow in NG9-1-1 LoST

Originating Network

LIS ESRP 1 PRF ESRP 2

Media

ESInet

Call is Connected to PSAP Media is established between PSAP and caller Media can be any combination of Voice, text, data, video, etc… LIS is queried for any updated location information

38

NG9-1-1 Concepts

 Think of your NG9-1-1 system as one element of an interconnected public safety and security system  County - Regional – State – National – International  Expansion of, and beyond the traditional PSAP  Fusion Centers  Virtual PSAPs  Trauma Centers  Poison Control  Emergency Operations Centers

NG9-1-1 Concepts

 More direct control of system capabilities by 9-1-1 Authorities and PSAP management  GIS data updated electronically, to control validation and routing  Electronic access to interactive validation data by service providers  Routing control and options controlled in databases directly accessible from 9-1-1 Authority and PSAP database terminals, or other authorized remote access points

NG9-1-1 Challenges

 Costs  Most pricing is custom at this stage  Double costs during transition  Relationship of cost to implementation scope  Bigger geography equals better price performance  Jurisdictional Impacts  If multiple services on ESInet, who is in charge?

 Shared usage and costs means shared responsibilities

Regulatory Challenges

 Regulations Should Allow:  Your NG9-1-1 provider to be different than your current E9-1-1 provider  Your NG9-1-1 IP infrastructure provider to be different than your NG9-1-1 services provider  Choice of service providers

See: NENA NG9-1-1 Transition Policy Implementation Handbook

Funding Challenges

 PSAP Authorities must be allowed to accrue funds to build ESInets and NG9-1-1 while still paying for and operating legacy networks  Consider different funding sources:  IP access providers?

 Pre-paid wireless?

 Consider new payment terms for 9-1-1 fees  More sources/lower fees?

NG9-1-1 User Benefits

The light at the end of the tunnel…

 Text/IM to 9-1-1  Files to 9-1-1 , such as photos or video clips  Streaming video  Telematics and sensor data  Nomadic and/or mobile call taker workstations  PSAP “on-the-fly” or Virtual PSAP  Policy-based alternate routing with new options  Additional Policy-based routing for:  Language preference of caller  Type of technology in use (IM, Sensor, Satellite phone, etc.)

NENA Standards and Documentation

 What’s done?

 GIS basics and preparation  Intro to NG9-1-1 databases  Policy changes for NG9-1-1 (funding recommendations, regulatory and legislative changes, jurisdiction issues)  `i3’ architecture specification, Version 1

NENA Standards and Documentation

 What’s in progress, re baseline NG9-1-1?

 Specifics on NG9-1-1 databases and management  ESInet Design guidelines  System operations, PSAP operations  Transition Options and Plans  System Management Guidelines  SDO convergence over time  List and status: www.nena.org

, then Programs, NG9-1-1 Project, Standards Status

Testing – ICE and Pilots

 Industry Collaboration Event  ICE Interoperability Testing underway  NENA Project sponsored, Vendor managed  Eight ICE events planned, three are completed  Distributed Pilot testing planned for 2011  At least five sites  Results: Recommended testing content

NENA Policy Handbook

        State-Level 9-1-1 Leadership and Coordination Funding the NG9-1-1 System Addressing Transitional Regulation/Legislation/Tariff Modifications to Enable Next Generation 9-1-1 Deployment Establishing State-Wide Emergency Services IP Networks (ESInets) Confidentiality, Disclosure and Retention of 9-1-1 Call and Other Emergency Information Next Generation 9-1-1 Liability Issues Develop a Strategy and Implement Recommendations

Education

NENA/APCO Joint Education Steering Committee

 Formed late Spring 2010  Reviewing identified stakeholder groups  Assessing/Identifying requirements for stakeholders that will need to better understand some or all aspects of NG9-1-1  Working with NENA EAB and APCO Institute for education delivery

Education

Challenges

 Must baseline everyone’s level of understanding of NG9-1-1 before more material is introduced  Which topics are the most critical?

 How much content is “too much” ?

 Identify effective delivery methods for targeted topics and stakeholders

NENA NG9-1-1 Project

Project Lead Team NENA Technical Committee NENA Operations Committee NG Partner Program ICE Steering Committee Vendor based Education Steering Committee NENA / APCO NG9-1-1 Transition Committee Contact

:

Roger Hixson, [email protected]

Q and A