Transcript ng9-1-1_overview_030909 - National Emergency Number

Next Generation
9-1-1 – The Future
for Emergency
Communications
What is NG9-1-1 and
What will it take to get there
Today we will cover:

Current State of 9-1-1

Limitations of 9-1-1 Today

What is Next Generation 9-1-1?

PSAP and 9-1-1 Authority Impacts

NG9-1-1 Development and Status

Next Generation 9-1-1 nationally

How can we work together for the Future?
2
NENA and NG9-1-1
NENA’s Mission Statement
NENA, through public and private industry
partnerships, is committed to the
technological advancement, availability,
accessibility and implementation of a
reliable system for requesting emergency
assistance. In carrying out its mission,
NENA promotes:
Research, planning, training and
education.
3
It’s Not Just 9-1-1 Anymore!

With technology available today –we
are moving to an Emergency Services
System environment
We will be sharing networks, bandwidth
and data
 Multiple public safety and governmental
applications on common IP networks

Need to foster partnerships and
leverage what we can do for one
another
4
 Policies & SOPs need to be developed

Variations in E9-1-1 Current
Requirements

Wireline




Wireless



No federal requirements
some states have requirements
VoIP


Federal (FCC) requirements (Docket 94-102)
Multi-Line Telephones Systems (MLTS)


No federal requirements
Some state and local requirements
Voluntary industry implementation
Federal (FCC) requirements (Docket 05-196, 04-36)
ADA requirements for TTY

Currently no provisions for Video/IP relay services, text
messaging
5
What We Have Now. . .
Different Levels of Service

Wireline




Wireless Phase I



Provides Call Back Number
Provides Carrier Info and Tower Location
Wireless Phase II






Most Reliable Location Technology
Selectively Routed to Correct Answering Point
Provides Call Back Number and Address
Provides Call Back Number
Carrier Info & Tower Location
Approximate Location based on X & Y Coordinates
Accuracy Requirements vary by technology used, and are under
review by the FCC
73% of Counties Covered – 91.5% of Population
VoIP
 IP calls to geographically appropriate PSAP using existing
9-1-1 network

Provides Call Back Number and Registered Address
6
Today’s 9-1-1 Challenges:
Moving to Digital Broadband

Over 6,000 Public Safety Answering Points
(PSAPs)

High costs associated with each PSAP

Costly, aging equipment that needs replacement
soon

Need data bandwidth, modernized network  IP

Caller location issues

Need for Interoperability with other agencies
(voice and data)

Funding needed to sustain & advance system
7
Next Generation 9-1-1 Vision
An evolved, fully-functional, Next
Generation 9-1-1 system that is
accessible anytime, anywhere,
from any device
8
Why Do We Need NG9-1-1?

The old E9-1-1 system design just can’t cope







New communications technologies need `plug and
play’ access and interfaces
Constant adaptation of E9-1-1 expensive and slow
Growing data rich environment – E9-1-1 can’t handle
Need data bandwidth, modernized network --> IP
Need a more flexible and easily controlled 9-1-1
system
Need interoperability among emergency
communications services nationally and internationally
Post transition, NG9-1-1 can be significantly more
efficient (and likely less expensive for similar features)
9
Why do we need NG9-1-1?

Current and new `calling’ devices





Text – IM, SMS, PDAs, other non-voice devices
Wireless – WiFi, WiMAX, improved cellular interface,
hybrid (cellular/WiFi)
Sensors – environmental, alarms, biometric
Video, still and motion
Wide spectrum of users, emergency
support needs



Deaf and hard of hearing, speech impaired
Non-english speaking callers
Constantly increasing mobile users – location
challenges
10
NG9-1-1 Purposes
• Fully replace Enhanced 9-1-1, with all capabilities
and functions in place today
• Add capabilities to support changes for current
and new types of Originating Service Providers
• Add flexibility for the PSAPs and 9-1-1
Authorities
• Add capabilities to integrate and interoperate with
emergency entities beyond the PSAP
11
NG9-1-1 Purposes
These four major areas of system development also require
that many policy, educational and operations issues be
treated, as part of the overall Project development prior
to implementation.

Addition of capabilities beyond those of today’s E9-1-1 systems,
for instance, drive needs in the above areas that are not easily
derived from past practice or experience.

System and procedural tools are required to support 9-1-1
Authorities and PSAPs

A variety of educational products are required

Guidelines and recommendations for the transition of
stakeholders to NG9-1-1 are critical.
12
What is NG9-1-1?
NG9-1-1 is a system comprised of hardware, software, data and operational
policies and procedures to:





provide interfaces from call and message services
process emergency calls and non-voice (multi-media) messages
acquire and integrate additional data useful to call routing and handling
deliver the calls/messages and data to the appropriate PSAPs and other
appropriate emergency entities
support data and communications needs for coordinated incident
response and management
The basic building blocks required for NG9-1-1 are:






Emergency Services IP Network (ESInet)
International Standards Compliant IP Functions
Software Services/Applications
Data Bases and Data Management
Security
Human Processes
13
NG9-1-1 Building Blocks
Equivalency
To
E9-1-1
14
NG9-1-1 Building Blocks
Additional Capabilities to meet
Current and Future Needs
Equivalency
To
E9-1-1
15
NG9-1-1 Building Blocks
NG9-1-1
Additional Capabilities to meet
Current and Future Needs
Equivalency
To
E9-1-1
16
NG9-1-1 Building Blocks
NG9-1-1
Expansion over time
Equivalency
To
E9-1-1
17
NG9-1-1 Building Blocks
Databases and Data Access
Software Services
IP Protocols
IP Networks -> ESInets
18
NG9-1-1 System
NG9-1-1
Blocks
Standards andBuilding
Recommendations
SDOs
NENA Technical and Operations
APCO
-------------------------------------------------------------------Human Processes and Procedures
Orig
Serv
Prov
Security
Databases and Data Access
Software Services `i3’
IP Protocols
IP Networks -> ESInets
Policy
P
S
A
P
s
S
u
p
p
o
r
t
Sys
19
NGPP
Changing Needs Drive NG9-1-1
 NG9-1-1
will use hardware and network that
are not 9-1-1 specific
 E9-1-1
uses E9-1-1 specific hardware/software
and network
 NG9-1-1
is software driven, and controlled
by databases
 NG9-1-1
must route calls/messages based
on multiple factors
 E9-1-1
routes primarily on address/location
20
PSAP and 9-1-1 Authority
Capabilities

More flexibility, and much more direct control
through Business Rules data bases

Automatic query of supportive data
Ex: Building info, medical info, telematics





Direct control of alternate routing
Pre-definition of disaster routing
Inter-network access to other PSAPs
Inter-network access to other databases
Cost savings through optional use of shared
software services at the NG9-1-1 system
level, rather than each PSAP
21
NG9-1-1 Basic Structure
Software and Data Base Controlled
.
Runs on managed IP networks
Supportive
Data
Using Caller Location,
Call Type, and
Supportive Data
Supportive &
Supplemental Data
via IP network
Originating
Service
Access
Providers
Nat’l Route
`State’ Route
PSAP
(LoST And ESRP)
(LoST And ESRP)
Call Mgmt
with Location
ALI
Legacy
LIS
i3
Data
Valid’n
Service Business Data
Routing
Rules
Rights
Service Business
Routing
Rules
SOP
PS Entity
Directory
Database
management
22
NG9-1-1 Basic Structure
Policy Based Routing
.
Runs on managed IP networks
Supportive
Data
Using Caller Location,
Call Type, and
Supportive Data
Supportive &
Supplemental Data
via IP network
Originating
Service
Access
Providers
Nat’l Route
`State’ Route
PSAP
(LoST And ESRP)
(LoST And ESRP)
Call Mgmt
with Location
ALI
Legacy
LIS
i3
Data
Valid’n
Service Business Data
Routing
Rules
Rights
Service Business
Routing
Rules
SOP
PS Entity
Directory
Database
management
23
Changing Needs Drive NG9-1-1






Audio/voice calls with data
Text messages/calls with data
Interactive video calls with data
Interactive video with interactive audio/voice & interactive
text – with data
Sensors/other devices with interactive voice/audio, text
&/or video – with data
Sensors/other devices (no interactive voice/audio, text or
video) with data
* Data when referenced above can include non-interactive
text, video, pictures and audio recordings
24
NG9-1-1 Proposed Feature Examples

Support call routing and call processing based on
characteristics data, such as language preference
and/or calltaker skills, based on call stream data
items or business rules information.
Examples: ASL over video, or adding an
interpretation service automatically to the call
before or at presentation to the calltaker

Dynamic data streaming during the call.
Examples: Personal telematics data from heart
monitoring vest, dynamically updated during the
call progress
25
Video of the scene for real time verification, info
NG9-1-1 Proposed Feature Examples

Optional ability to pass certain calls directly to
dispatch or responding agency based on call
type, call priority and circumstances indicated by
Essential and/or Supportive data items.
Controllable by business rules database entries.
Examples:
sensor data and alarms, high priority telematics
calls

Manually query expanded sets of supplemental
databases after call delivery to the PSAP, via the
NG9-1-1 network
26
How is the NG9-1-1 Project being managed?
27
Who is defining NG9-1-1?

NENA




Future Path Plan in 2001
Started development work in 2003
Internet Engineering Task Force (IETF)
International Standards Development Orgs
(SDOs) - predominantly about service provider standards
and location determination and provision


USDOT project – RFP in 2006, 2007-2008
project  Proof Of Concept and Demos
Commercial companies are developing parts of
NG9-1-1, in view of developing standards
28
Who is defining NG9-1-1?




The NENA-IETF effort is about IP protocols
and architecture – functions and interfaces
NENA’s Long Term Development working
group also defined a Location ID
requirements document used by other SDOs
NENA has a NG9-1-1 Data Development
working group
NENA also has a NG9-1-1 Transition
Planning committee
29
NENA Development Structure
NENA NG9-1-1 Project
Technical
Operations
NGPP
NGTPC
Technical Committee - technical development
Operations Committee – operations development
Next Generation Partner Program (NGPP): policy issues around
NG 9-1-1 and NG emergency communications, coordinating with
the NENA national Reg/Leg Committee
NG9-1-1 Transition Planning Committee (NGTPC) – transition &
implementation guidelines
Also a NENA Certification and Accreditation Program is pending
30
NG9-1-1 Project Activity Relationships
High Level
Public Safety Emergency Communications Systems
NENA Actions
Strategic Plan with ICO
RFP
Systems Operations Development
With Performance Criteria
TESTING
and
US DOT Project
Revisions
TX A&M and other trials
Systems Ops
Transition Plan
General Development
(SDO Coordination)
(NENA Certification)
Full NG9-1-1
Implementation:
Transition and
Ongoing Operation
NENA Certification
PSAP Operations Development
FPP
Technical Requirements/Designs
NG Partner Program – policy issues
2001 2002 2003 2004 2005 2006 2007 2008
NRIC VII
2009
2010
2011
NENA’s Development Approach
NG9-1-1 Development Assumptions
 Open architecture, open standards design
 Two models for system component integration




Vendor as integrator, operator of systems
9-1-1 Authority as integrator, operator of systems
Latter case means more detail and operational
activities for Public Safety
These characteristics drive a need for specific
standards and guidelines from NENA
32
NENA’s Development Approach
New 9-1-1 Authority Capabilities in NG9-1-1

Database Controlled System Actions



Supportive Data – acquired by the system before
call delivery
System Business Rules – Software control
- Routing Control
System Management Requirements


System Operations
System Administration
33
NENA’s Development Approach
Technical Committee activities
 NG9-1-1 Requirements
 IP Protocols Requirements
 Location Process Requirements
 IP Functions and Interface Standards
 Physical System Transition
 Data Requirements
 Data Development (7 topics)
 IP Network Recommendations
 Security
34
NENA’s Development Approach
Operations Committee Activities
 PSAP Operations ( 5 topics )
 System Operations
 System Administration
 Data Operations ( 5 topics )
 IP Network Operations
 Procedural Transition
35
NENA’s Development Approach
Related Operations Committee Activities








Virtual PSAP/virtual consolidation
Text Messaging
Policy-based call processing (including routing)
PSAP education/training
Public education
N11 Operational Interaction (all N11s can route with
NG9-1-1 system & transfer easily too)
Additional operations-focused requirements
Various joint (operations/technical) initiatives
36
NENA’s Development Approach
NG Partner Program Activities





Funding
Jurisdiction
Regulation
Legislation
Education





Interoperability
Core/Facilitation Services
Certification/Accreditation
Information Sharing
Disaster Planning
37
NG9-1-1: From Paper
to Reality

Significant technical and operational standards development (NENA and
other SDOs)

Proof of concept trial demonstrations

Architectural framework development

Concept of operations development

Certification and accreditation conceptual development

But…Without policies that promote NG9-1-1 and statutes &
regulations that allow it, standards and architecture
development is irrelevant

What is possible must also be a policy goal and a legal activity
Some NG9-1-1 Policy
Issues Identified

Funding models must be reexamined to account for emerging technologies
and to enable the sharing of infrastructure and costs

State and federal policies are needed to enable the establishment of State
Emergency Service IP Networks (not stand alone 9-1-1 networks)

Jurisdictional frameworks for NG9-1-1 at fed, state and local levels must be
clarified (Need for appropriate statewide coordination/management)

Out of date state and federal laws/regulations that do not reflect modern
communications capabilities in an NG9-1-1 system must be addressed



e.g. outdated state PUC regulations based on traditional telephone system;
e.g. outdated rules restricting the eligible use of 9-1-1 funds to old technology
Need for review of liability and confidentiality statutes
NENA’s Development Approach
NG Partner Program Activities

Funding: Provide recommendations to solve the diverse
funding methods across the nation that complicate and
limit funding for NG9-1-1, its transition, and ongoing
operation.

Jurisdiction: Recommendations, considerations and
rationales for roles and responsibilities around NG9-1-1 at
federal, multi-state, state, intra-state regional and local
levels are defined and transmitted to all levels of
government.
40
NENA’s Development Approach
NG Partner Program Activities

Regulation: Federal and state regulations need to be changed,
deleted, and added in order to both further NG9-1-1 implementation
and to ensure that any regulatory roadblocks are eliminated. The goal
is to both prepare appropriate model regulatory language and to
begin a plan to drive such changes at the federal level and, where
appropriate, at the state level.

Legislation: Federal, state and local laws need to be altered where
they conflict with NG9-1-1 key concepts and principles. The goal is to
analyze existing laws and prepare appropriate model legislation
language for those necessary alterations, and to begin a plan to make
such changes happen at the federal level, within the 50 states and,
where identifiable, locally.
41
NENA’s Development Approach
NG Partner Program Activities

Education: The NG9-1-1 legislative and regulatory goals will require
education materials for a broad spectrum of entities and people. The
goal will be to refine the federal/state/local government list, develop
the appropriate supportive messages and provide as part of the
legislative and regulatory implementation plans.
42
NENA’s Development Approach
NG9-1-1 Transition Planning Comm activities
 Identify transition needs
 Identify gaps in development work
 Produce a transition planning and implementation
guideline set,
- with references to documents provided by other work
groups,
- for each major stakeholder group, and
- across the various start points (greenfield,
B9-1-1, E9-1-1, E9-1-1 with Phase II, E9-1-1 with
Phase II and VoIP, etc) to NG9-1-1
43
NENA’s Development Approach
Parallel or Post Development Activities





USDOT Project
Beta Test for full NG9-1-1 system
Partial or Full Trials
First Full NG9-1-1 Application
Transition and Implementation
44
Project Acceleration Alternatives
We need to bring all appropriate resources and
project methods to bear on NG9-1-1 work







F2F WG focus kick-off meetings
Additional resources for selected WGs
Volunteer leader cost support
Paid leaders for selected WGs
Part-time project schedule asst manager
Coordinate efforts among organizations
Others?
45
NG9-1-1 Impacts on 9-1-1 Authorities
Active NG9-1-1 system management moving toward
9-1-1 Authorities
Open architecture, open competition options
IP network management, both local and wider areas
Management of expanded databases











Authentication processes, user authorization management
Validation
Routing
Data Sources
Data Rights management
Business Rules (including activation/management of
optional features)
Public Services Entity directory
46
SOP databases
Real World Applications




Statewide next generation network projects in
process today in Indiana, Montana, Vermont,
Rhode Island, Texas, Florida, Minnesota
Smaller scale next generation network
implementations in Washington DC, the MARC
(Kansas City area), Allegheny County PA
Some of these include various levels of NG9-1-1
features
The Federal USDOT project is targeted to
demonstrating core NG9-1-1 capabilities in a
2Q 2008 Proof of Concept demo
47
Example Activity Toward NG9-1-1

USDOT Project Sites
Three Labs, national IP network, Five
PSAPs, One state IP network
 Rochester, St Paul, Helena, Seattle,
 Indiana IP network and Ft Wayne PSAP


State Programs – VT, IN, TN, AL, MD

Strategic Plans in many other states
48
USDOT NG9-1-1 Project
Two Year Project (2007-2008)
 Prepare for and Conduct a 6 month `Proof of
Concept’ Trial (mid-2008)
 Develop and Validate Core Requirements for the
Next Generation 9-1-1 (NG9-1-1) System
 Define a System Architecture
 Provide input to NG9-1-1 Standards work
 Develop a Transition Plan for Deploying IP-Based
Emergency Services Across America.
 Booz Allen Hamilton, prime contractor
 Project Team: NENA, L Robert Kimball
Associates, Texas A&M University
49
Info at: www.its.dot.gov/ng911

USDOT NG9-1-1 Project
Long Term Goal:

R&D project to design a system that enables the
transmission of voice, data or video from different
types of communication devices to the Public Safety
Answering Points (PSAPs) and on to emergency
responder networks.
Major Milestones: to be accomplished during
this two year project



National Architecture and High-Level Design for
NG9-1-1 System
Proof of Concept
Transition Issues for NG9-1-1 Implementation
50
IP Networks Supporting NG9-1-1






Use IP networks as they develop (9-1-1
or other existing public safety network)
County, regional, state, national
Link together as a network of networks,
nationally and beyond
NG9-1-1 functions run on the IP
networks and must meet NG9-1-1
standards
Security issues must be addressed
Expanded data access with wide
area/national emergency
communications capabilities
51
What has to be done to make
NG9-1-1 Available?







Funding evolution
Policy evolution, jurisdiction issues
Standards and technology development
PSAP/Emergency response operational
modifications
Leadership at all levels of government
Wide-ranging education needs
Regulation & Legislative changes
53
Stakeholders in Transition









General public – emergency callers
9-1-1 Authorities/State 9-1-1 agencies
Local PSAPs and other emergency response agencies
Public safety and industry organizations – APCO, NENA,
CTIA, etc.
Local/State/Federal Governments
Standards Development Orgs – SDO’s
9-1-1 System Service Providers (ILECs)
Originating Service Providers and national call centers
(telematics, TRS, VRS, other N-1-1s, etc.)
Vendors, Equipment Manufacturers and distributors
This will require significant cooperation!
54
Working Together To Make
NG9-1-1 A Reality

Understand that underlying network/technology needed for
NG9-1-1 is also needed for ALL emergency communications
(high bandwidth voice, data, video)

Promote policies that jointly support 9-1-1 and emergency
communications as one “emergency response enterprise”

Encourage federal and state homeland security policy to
include NG9-1-1/emergency communications

Help/encourage coordination of all efforts and stakeholders
within states

Facilitate/participate in NG9-1-1 development and trials
55
Working Together To Make
NG9-1-1 A Reality

Assist efforts to update statutes and regulations to enable
NG9-1-1 (state and federal)
- e.g. Washington State NG9-1-1 Working Group
- HR 3403 (liability, 270 days > NG report, grant eligibility)
- Federal-State joint Advanced Services Board
- Resolving legal & jurisdictional issues through statutes/regs

Help secure funding for NG9-1-1 (state/federal)

Education: Promote NG9-1-1 within membership of public
safety and state/local government organizations
- Publications and meetings
56
For updated info, see the NENA NG9-1-1
Project page on the NENA web site at
www.nena.org
Q and A
57
SYSTEM
From INCOSE, the International Council on
Systems Engineering:

A system is a collection of different
elements that together produce results not
obtainable by the elements alone. The
elements, or parts, can include people,
hardware, software, facilities, policies, and
documents; that is, all things required to
produce systems-level results.
58
NG9-1-1 as a SYSTEM

From the systems engineering and project management
perspective, NG9-1-1 is a system of hardware, software,
databases, networks, human processes and procedures,
and documentation that produces an end result of 9-1-1
service according to accepted requirements and
performance expectations.

The various operational processes, both physical and
human, among all the parties to the system, are part of
and critical to the NG9-1-1 system. Those parties include
originating service providers, vendors of network,
hardware and software, SSPs, PSAPs, 9-1-1 Authorities,
and other stakeholders that positively or negatively can
59
impact 9-1-1 operations and resulting service.