bill mertka| offer manager, ng9-1-1 advanced services...

September 15, 2011 – NG9-1-1 Overview: What It Is, What It Isn’t & Its Promise

Bill Mertka| Offer Manager, NG9-1-1Advanced Services, MOTOROLA SOLUTIONS

Terry Eby| Solutions Architect, NG9-1-1Advanced Services, MOTOROLA SOLUTIONS

• MT NG9-1-1 Proof of Concept Overview

• Discussion of NENA NG9-1-1 Standards:

• External Forces Driving the need for NG9-1-1

• Transition to NG9-1-1

• Value and Nature of NG9-1-1

• NG9-1-1: Added Features

• NG9-1-1: What is it?

• NG9-1-1 Basics and System

• How is NG9-1-1 Different?

• E9-1-1 vs. NG9-1-1; NG9-1-1 is not just…

• DCN Network: An ESInet for ND?

• Current US NG9-1-1 Activity / Early Adopters

• NENA Industry Collaboration Events (ICE)

• Differentiation of Legacy, Hybrid, and i3 Capable

Agenda

MT NG9-1-1 PROOF OF

CONCEPT OVERVIEW

MT NG9-1-1 PLANNING OBJECTIVES

• “The State of Montana will utilize the grant funding to migrate to a NG9-1-1 system including operations development and deployment of a 9-1-1 Emergency Services IP Network (ESInet). The operations development will include building Emergency Services Routing Proxies (ESRP) and utilizing the Location-to-Service Translation (LoST) protocol that will provide critical information for call routing. The ESInet elements will extend the existing IP enabled network providing a full migration to IP enabled 9-1-1 services.”

• The proposed pilot project is intended to help MT achieve this objective

MT NG9-1-1 ROADMAP

MT NG9-1-1 PILOT PROJECT SUMMARY

• Objective: Demonstrate through a pilot project how MT PSSB can

implement a transitional strategy for migrating Montana’s legacy E9-

1-1 system to a full NG, i3-based system

• The overall system design and all proposed components conform to

NENA i3 standards

• System is designed and engineered to show PSSB that, even with a

limited deployment, the State could see the clear benefits of

upgrading its existing 9-1-1 system to a full NG system

• The proposed solution is “software-centric;” the pilot will

demonstrate that “forklift upgrades” of emergency communications

equipment hardware and software are no longer necessary and will

demonstrate the “ease of upgrade” required to keep pace with the

rapid rate of communication equipment evolution.

Motorola Confidential Restricted

MT NG9-1-1 PILOT PROJECT OVERVIEW

• The overall system design and all proposed components conform to

NENA i3 standards

• System is designed and engineered to provide PSSB with improved

flexibility and control over the solution, so that even with a limited

type deployment, the State could see the clear benefits of upgrading

its existing 9-1-1 system to NG.

• The proposed solution is “software-centric;” the pilot will

demonstrate that “forklift upgrades” of emergency communications

equipment hardware and software are no longer necessary and will

demonstrate the “ease of upgrade” required to keep pace with the

rapid rate of communication equipment evolution.


PILOT PROJECT OBJECTIVES

• Demonstrate and put in place a NG9-1-1 infrastructure that will allow

current legacy equipment to stay in place until funding becomes

available for replacement. Demonstration of Legacy Network Gateway

(LNG) and Gateway (Legacy PSAP Gateway, or LPG) capabilities per

the NENA specification.

• Sub-scenarios, including the ability to convert a traditional 9-1-1 call to a

SIP call, dip an ALI database, create a PIDF-LO, request a location

based route and send the call on to the PSAP will be tested as part of

this objective.

• Demonstrate support for NG PSAP capability through the use of a

solution that employs centralized controllers and remote, PC-based, IP-

enabled call-taker positions out at the PSAPs.

• Demonstrate how calls can effectively move throughout the network

from legacy equipment to IP equipment, IP equipment to legacy

equipment and any possible mix, to show viability of the standards, the

equipment, and the ability of the solution piloted to support Montana’s

transition plan.


PILOT PROJECT OBJECTIVES (2)

• Demonstrate transfer of a NG call from one PSAP to another, across

traditional LATA boundaries, with imbedded caller location

information (PIDF-LO) included.

• Demonstrate how misrouted wireless calls can be easily redirected to

the proper location through spatial comparison of Phase II ALI with

PSAP boundaries prior to delivery.

• Location-based routing of wireless calls (or any call for that matter).

• SMS to 9-1-1 and/or vanity number that would forward to certain

PSAPs in the system

• Demonstrate how originating service providers may deliver their 9-1-1

calls to an ESInet

• Demonstrate PSAP use of a single NG CPE solution to answer 9-1-1

calls.

• Demonstrate how PSAPs can seamlessly transition call taking to an

alternate PSAP based on schedule or other event.

• Demonstrate how changes to GIS data have an effect on call routing.


DISCUSSION OF NENA NG9-1-1

STANDARDS

EXTERNAL FORCES CREATING NEED

FOR CHANGE IN 9-1-1 SYSTEMSSociological, Technological, Economic Trends:

• Changing Consumer Expectations – Multimedia usage (text, image,

video, telematics, sensors, subscriber info); users expect to be able

to use multimedia for emergency communications

• Aging PSAP Infrastructure - Obsolete equipment / technology

limiting ability of today’s centers to “keep up” with new technology

• Ongoing “Everything IP” Technology Revolution - PSAPs want to

take advantage of capability of “all IP” systems.

• Fiscal Environment Dictates Change - Public funding economics

driving consolidation of PSAPs, staffing issues

TRANSITION TO NG9-1-1• Among the clear needs addressed by a transition to NG9-1-1 are:

• Quicker receipt of more robust information as the result of making a 9-1-1 call

• Better and more useful forms of information (text, images, and video) from any

networked communications device

• Transfer of 9-1-1 calls between geographically dispersed public safety

answering points (PSAPs)

• Increased aggregation and sharing of data, resources, procedures, and

standards to improve emergency response

• Effective use of available public capital and operating costs for emergency

communications services

• Promotion of increased coordination and partnerships within the emergency

response communitySource:

THE VALUE OF NG9-1-1

• NG9-1-1 has the potential to provide significantly greater value

than current 9-1-1 technology. Value trends include the following:

• NG9-1-1 provides greater opportunities for cost savings, cost avoidance,

and increased operational efficiencies than the current 9-1-1 environment

• NG9-1-1 has greater potential to meet the public’s expectations for

accessibility than the current 9-1-1 environment

• NG9-1-1 has greater scalability and flexibility than the current 9-1-1

environment

• NG9-1-1 has greater potential to increase public and responder safety

through interconnectivity and interoperability than the current 9-1-1

environment

Source:

THE NATURE OF NG9-1-1

• Designed to support interoperability

• Built on 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

Source:

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 (e.g., sensing

PSAP status)

• Direct control of call management (e.g., PRF, etc.)

Source:

• NG9-1-1:

• The set of network elements, software applications, databases, CPE

components, and operations & management procedures required to provide

next generation emergency services

• NENA “i3” Standards (req‟ts., architecture, and specs)

• The functional applications/services that form the core of NG9-1-1 and run

on Emergency Services IP networks (ESInets)

• ESInets

• A privately-managed IP transport network that supports the core routing

functional entities necessary for NG9-1-1 call delivery; these include but are

not limited to: the Emergency Services Routing Proxy (ESRP) and the

Emergency Call Routing Function (ECRF). An ESInet can support other

Emergency Services applications and is shared by all agencies which may

be involved in any emergency.

• Other SDOs (IETF, ATIS, etc.) have also turned their attention to NG9-1-1

• NENA i3 incorporates global IETF standards

• ATIS (North America) has developing a competing standard (RFAI)

NG9-1-1: What is it? (NENA Definitions)

NG9-1-1 BASICS

NG9-1-1 System =

Procedures +

Databases +

i3 Architecture +

ESInet within IP network

Source:

NENA NG9-1-1 SYSTEM

NG9-1-1: What is it? (2)

• NENA NG Baseline:

• A fully compliant NG9-1-1 system 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 and,

- A number of capabilities beyond E9-1-1 functions,

such as the basic ability to support non-voice

multimedia, such as text and video

NG9-1-1: What is it? (3)• NENA NG Baseline:

• Additional minimally required components or

capabilities of baseline NG9-1-1 include, but are not

limited to:

1) ESInet (Emergency Service IP network)

2) GIS data creation to support 3 and 6 below, and associated

management tools

3) Publication of Authoritative NG9-1-1 Validation related

Databases for use by OSPs and Location DB providers to

pre-validate civic addresses (in replacement of MSAG),

supported by LVF and LIS functionality1

4) Publication of Authoritative NG9-1-1 Routing Data for state

and regional levels

5) Support for legacy originating services via gateways (e.g.,

access to traditional ALI databases)

6) Geospatial controlled IP software call routing function

(ECRF and ESRP)

NG9-1-1: What is it? (4)• NENA NG Baseline:

• Additional minimally required components or capabilities

of baseline NG9-1-1 include, but are not limited to (con’t.):

7) The ability to control call routing based upon a policy routing

function (PRF) with standardized methods to define/build and

control Policy Rules

8) Additional data acquisition after call delivery to facilitate call

processing by call taker or other public safety entities

9) Support for transfer of calls with accumulated call taker notes

and added data, or an access key to such data, to any

authorized entity interconnected by ESInets

10) Ability to interconnect with other NG9-1-1 systems and to

interwork with E9-1-1 systems

11) Support for system monitoring/logging/discrepancy reporting

necessary to support troubleshooting and ongoing operation

and maintenance

Clients Access Networks Origination Networks

Legacy Circuit-Switched Networks

Public Access IP Networks

Internet, Carrier IMS Networks,

etc.

ESInet

ESInet

Legacy PSAP

Legacy PSAP Gateway

NG911 PSAP / Cmd Center

Call Taker

Dispatcher

PS LTE

Radio System

Based on NENA Diagram in “Functional and Interface

Standards for Next Generation 9-1-1 Version 1.0 (i3)”

NG911 PSAP

Emergency Responders

NG9-1-1 System Overview

Legacy Network Gateway


HOW IS NG9-1-1 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

E9-1-1 VS. NG9-1-1E9-1-1 NG9-1-1

Complex analog trunking and data

network

Engineered, managed IP networks

(ESInet)

Class 5 switch for Selective Router IP software selective routing

Translation based control GIS and database controls

Limited to voice calls Voice, text, video

Data bandwidth 20 char (digits) Bandwidth unlimited

Complex Emergency Gateway

Network for VoIP

Direct handling of Internet sourced

calls

Custom interfaces for each service

type

Standard IP interface for all service

types

NG9-1-1 IS NOT (JUST)…

• VoIP to the PSAP

• Full, “end state” NG9-1-1 involves more than just send

calls to a PSAP over IP / VoIP

• Without location-based routing of “calls”, it is not “NG-

baseline,” let alone “full NG”

• Texting to 9-1-1

• An important capability, but NG9-1-1 is MORE than

just receiving text messages (or photos or video, for

that matter, at the PSAP)

• Multimedia sessions to the PSAP are important, but

NG involves much more…

DCN NETWORK – POSSIBLE ND ESINET?

CURRENT NG9-1-1 ACTIVITY

Note: Current regulation in many states unintentionally prohibits NG9-1-1 deployments

Source:

NG9-1-1: EARLY ADOPTERS

Entity Project RFP Award Funding Source

Counties of Southern Illinois

16 county region ESInet & NG9-1-1

solution

Released September

2010

1Q – 2Q2011

NTIA BTOP Phase 2 Grant, Existing

9-1-1 funds

North Central North Carolina (NCNC)

NG9-1-1 Compact

3 Jurisdiction Pilot (Winston-Salem,

Surry County, Eden, NC)

N/A2Q 2010

(2Q 2011 go-live date)

North Carolina Wireless Board

Grant

IowaStatewide ESInet /

NG9-1-1 solution for wireless calls

Mid 2010 4Q 2010

Enhance 911 Act Grants and

existing 9-1-1 funds

TennesseeESInet Monitoring

ContractOct-10 4Q 2010 ?

AlabamaANGEN / state ESInet

for wireless callsNov-10

2Q 2011(Planned)

Enhance 911 Act Grants and

existing 9-1-1 funds

TESTING – NENA INDUSTRY

COLLABORATION EVENTS (ICE)

• Completely voluntary; NENA sponsored, vendor managed

• Guided by a steering committee with representatives from

all stakeholder groups; each ICE event has its own

individual planning committee

• Based on the standards work being done in NENA, ATIS /

ESIF, IETF, TIA and other SDOs

• Three (3) events held, so far:

• ICE 1 (week of 11/02/09, College Station, TX): i3 end-to-end testing

• ICE 2 (week of 05/25/10, Irving, TX): NG9-1-1 transitional elements

• ICE 3 (week of 11/29/10, Bryan, TX) location information

• ICE 4 will take place November 2011, Irving, TX

• Focused on LoST hierarchy-based call routing

• Four (4) more ICE events planned

DIFFERENTIATING LEGACY, HYBRID &

I3 CAPABLE PSAP SYSTEMS

• NENA i3 Compliance: To move forward in today’s 9-1-1

development you must be on a path to achieve NENA i3

compliance

• NG-9-1-1 CAPABLE: Equipment designed to operate by Y2K

computer digital use and design input architecture. This

equipment requires ANALOG operations but can use IP inputs.

This is considered “LEGACY” equipment

• NG-9-1-1 i3 ENABLED: Equipment that is FULLY i3

INTEGRATED at the Digital IP level; capable of “NATIVE IP”

inputs and operations, VOIP/VOIM and advanced Digital

evolutions

CONTACTS:

Bill Mertka

Offer Manager, NG9-1-1 – Advanced Services

Motorola Solutions

[email protected]

847-576-3420

Terry Eby

Solutions Architect, NG9-1-1 – Advanced Services

Motorola Solutions

[email protected]

904-755-2039

mailto:[email protected]

mailto:[email protected]

bill mertka| offer manager, ng9-1-1 advanced services...

Documents