this presentation provides a high level functional comparison between the legacy 9-1-1 and ng9-1-1...

This presentation provides a high level functional comparison between the legacy 9-1-1 and NG9-1-1 NENA i3 model including an overview of the major steps involved with migrating from legacy 9-1-1 to a NG9-1-1 NENA i3 model. A subjective review of the two different transition strategies published by NENA and ATIS (RFAI) will be discussed. The presentation will also discuss pro/cons between CPE and hosted applications that can be supported by an Emergency Services IP Network. These topics would be of interest to PSAP leadership, GIS support personnel as well as IT support personnel.

1

Myron S. Herron, Jr.,President/COOToll Free (866) [email protected]

Synergem © 2011All Rights Reserved.

NG9-1-1 NETWORK

TRANSITION STRATEGIES

AND PLANNING

2


LEGACY 9-1-1 MODEL

Selective Router

ALI

ALI

CAMA Trunks

CAMA / SS7

3208452738

Subscriber Calling 9-1-1

Find ANIin SRDB

3202400040 = PSAP A2622423577 = PSAP B4246280188 = PSAP C

3208452738 = PSAP A

Switch call to PSAP A

Voice, ANI

VoIP

Cellular

PSTN

Enterprise

LEGACY E-9-1-1 MODEL REVIEW

MPC / GMLC

MPC / GMLC

ANI/ALI ControllerPositron VIPERPCML Patriot

TANDEM

3Synergem © 2011All Rights Reserved.

TIME AND MONEY

Illustration by Scott Chan

When drafting a NG9-1-1 transition plan, ask the following:

“What operational capabilities are provided by the interim transition solution that are not already available in the legacy system?”

If not planned properly, the wrong transition strategy could be a very expensive diversion to NG9-1-1.


5


NENA I3 MODEL

NENA Detailed Functional and Interface Standards for the NENA i3 Solution (TSD), NENA 08-003 v1, June 14, 2011

NENA I3 – A WHOLE NEW VOCABULARY

• Emergency Call Routing FunctionECRF• Location-to-Service TranslationLoST• Presence Information Data Format - Location ObjectsPIDF-LO• Emergency Services Routing ProxyESRP• Border Control FunctionBCF• Policy Routing FunctionPRF• Location Information ServerLIS• Location Validation FunctionLVF• Legacy Network GatewayLNG• Legacy PSAP GatewayLPG


NEXT GENERATION 9-1-1 DEFINED

The term ‘Next Generation 9-1-1’ refers to a system comprised of hardware, software, databases, and operational policies and procedures that: A. Utilize managed, broadband IP networking B. Interconnects call and data sources, processing elements, databases, and public

safety answering points and other emergency entitiesC. Employ GIS data, and other control databases, to manage routing and transfer of

calls and dataD. Process all types of emergency calls, including voice, data, and multimedia

information for delivery to emergency entitiesE. Support communications needs for coordinated incident response and

managementF. Require emergency services grade network availability and security


NG9-1-1 DEFINED

VoIP

Cellular

PSTN

Enterprise

Origination Network

9-1-1 Call w/Location

IPESRP

LIS

LoST

ECRF

LVF

PRF

Emergency Service IP Network(ESInet)

NENANG9-1-1

PSAP

NEXT GENERATIO

N 9-

1-1 NENA i3 Specifications


CALLER LOCATION TYPES

Civic – House Number, Street Name, Community Name

<civicAddress> <HNO>2099</HNO> <A6>UniversityAvenue</A6> <POD>W</POD> <A3>StPaul</A3> </civicAddress>

Geodetic – Point, Polygon, Ellipse, Circle, Arc-Band

<gml:Point> <gml:pos>44.95985, -93.187401</gml:pos></gml:Point>


NENA I3 CALL-ROUTING PROCESS

<gml:pos>44.95985 -93.187401</gml:pos>Given a device’s location:

… and the type of service being requested: <service>urn:service:sos</service>

… a map of service area boundaries is searched:

… to receive PSAP routing designator: <uri>sip:911.saintpaul.mn.us/PSAP</uri>


NENA I3 CALL PROCESSING

-93.187401, 44.95985urn:service:sos

Subscriber Calling 9-1-1

Locate call on mapof routing boundaries

Send call to PSAP A

SIP: Voice, Location, and Additional Data

VoIP

Cellular

PSTN

Enterprise


NEXT GENERATION 9-1-1 TRANSITION STRATEGIES

NENA i3

Vs.ATIS RFAI

NENA i3

ATIS RFAI

Illustration by Scott Chan


FUNDAMENTAL ARCHITECTURAL DIFFERENCESNENA I3 VS LEGACY

Legacy E9-1-1 Network Legacy PSAP

Selective Router

ALI

ALICAMA Trunks

• SS7/CAMA to S/R replaced with IP Trunks w/location

• Selective Routers – Replaced by ESRP/ECRF/LVF• CAMA Trunks – Replaced by IP trunks with caller location• ANI/ALI Controllers - Retired – NO LONGER REQUIRED!• ALI Databases / MSAG / SR DB – Absorbed into ECRF/GIS/LIS

VoIP

Cellular

PSTN

Enterprise

Origination Network

CAMA, TDM, SS7


NENA I3 TRANSITION MODEL

VoIP

Cellular

PSTN

Enterprise

Origination Network Legacy PSAP

CAMA TrunksCAMA,

TDM, SS7 RS232

ESRP

LIS

LoST

ECRF

LVF

PRF


LN

G

LP

G

No modification of Legacy PSAP equipment

required.

No modification of origination networks

required.


Selective RoutersALI DatabasesANI/ALI ControllersCAMA Trunks to PSAPTDM (SS7/CAMA to TSP

NOTICE ANYTHING MISSING?


16

STANDARDS DEVELOPMENT TIMELINE

© 2011 All Rights Reserved.

2003 2004 2005 2006 2007 2008 2009 2010

VTC

LTD

“I”IP

COAD

ESIF

NGES

i1 i2 i3 R i3 A i3 SRFAI

i3 Introduced RFAI Introduced

June 18, 2011

17

RFAI TRANSITION MODEL REFERENCE

RFAI (Request for Assistance Interface) specification:

ESMI (Emergency Services Messaging Interface) is a protocol providing a mechanism to communicate data services between the ES-NGN and the client side of the network. (ATIS-050002.2004, page C-3)

(ESIF-NGES-2009-028R17.DOC)

© 2010 All Rights Reserved.

RFAI PURPOSE – TRANSITION TO NENA I3

“Specifically, the RFAI architecture is intended to define a

new interface between the new functional network

elements, IPSR and RFAUA. These new functional

elements serve to provide a transitional step from a

legacy TDM environment to an IP environment that

serves a PSAP.”(ESIF-NGES-2009-028R17.DOC,

PAGE 1)


LEGACY E9-1-1 TO RFAI / ESMI TRANSITION

Upgrade to VoIP ANI/ALI Controller

Conforming Emergency Services Entity (CESE)

IP Trunks

ALIALI

RFAUAIPSR

Response Gateway

(RG)ESMI

Legacy E9-1-1 Network Legacy PSAP

Selective Router

ALI

ALICAMA Trunks

VoIP

Cellular

PSTN

Enterprise

Origination Network

CAMA, TDM, SS7

CA

MA

, TD

M,

SS7

ALI, MSAG & SRDB

maintained.

PSAP Upgrade to

VoIP ANI/ALI

Controller with RFAI

TN based routing SIP protocol


No Standards

Defined

RFAI – SCOPE DEFINED

“…the RFAI specification describes only the interface that

is between the IPSR and RFAUA, leaving the other

origination and termination interfaces out of scope. The

internal functions of both IPSR and RFAUA are also

considered out of scope, since this document only

describes the RFAI interface specification.”(ESIF-NGES-2009-028R17.DOC,

PAGE 2)


RFAI/ESMI SCOPE

Upgrade to VoIP ANI/ALI Controller


IP Trunks

ALIALI

RFAUAIPSR

Response Gateway

(RG)ESMI

Emergency Services NGN RFAUA

VoIP

Cellular

PSTN

Enterprise

Origination Network

CA

MA

, TD

M,

SS7

What impact does RFAI

have on operational

capabilities?Out of RFAI

Scope

Out of RFAI

Scope


RFAI TRANSITION

“As emergency service networks transition away from SRs, NENA’s intent

for NG9-1-1 is to smoothly transition to the NENA i3 defined

architecture, ensuring a consistent environment among PSAPs and

between ESInets. When the NENA i3 architecture is implemented, the

RFAI is no longer needed.”

(ESIF-NGES-2009-028R17.DOC, PAGE 1)

As documented on page 2 of the RFAI Standards Document:


RFAI TO NENA I3 TRANSITION

Operationally EnhancedPSAP

RS232

CAMA/IP

Origination Network

Emergency Services - Next Generation

Network(ES-NGN)


IPSR

ALIALI

Response Gateway

(RG)

VoIP ANI/ALI Controller RFAUA

ESMI

VoIP

Cellular

PSTN

Enterprise


LP

G

Remove RFAI from CPE

IP

NENA I3Interface

ESRP

LIS

LoST

ECRF

LVF

PRF

NENA i3PSAP


RFAI VS NENA I3RFAI NENA i3

Organizations contributing to standard ATIS

NENAIETF

USDOTAPCO

Individual contributors to standard 2100 8400

Year standard development started 2009 2003

Region standard supported US Global

Number of NENA documents supporting standard 0 >25

Number of vendors supporting standard <10 100's

Cost to obtain standard document(s) $300 Free


ECRF

2321 WABASH AVE2099 UNIVERSITY AVE W

Local Jurisdictional GIS

?

?23577 OAK AVE80188 VALLY RD

PASS:

PASS: FAIL:

FAIL:

Updates from TSP’s service order

database

Updates from TSP’s service order

database

LIS

LIS PROVISIONING & LOCATION VALIDATION FUNCTION (LVF)


Primary PSAP

Voice, Data, Location

Backup PSAP

Voice, Data, Location

GEOSPATIAL ROUTING


28


SYNERGEM EVOLUTIONNETTM PROVISIONING – LESSONS

LEARNED“Synergem Emergency Services successfully routed the Nation’s first end-to-end call through an Emergency Services IP Network (ESInet).”

Press Release, July 29, 2011

Proprietary and Confidential

LESSONS LEARNED

TSP INTERCONNECTIVITY

LOCATION VALIDATION FUNCTION (LFV)

QA/QC TOOLS

• Standard Data Maintenance• Advanced Data Maintenance

INTERCONNECT AGREEMENTS



LEGACY MODEL: PRIMARY VS. ALTERNATE 9-1-1 SERVICE PROVIDER

Tandem

S/RPSAP 1

OK

PHONEMESSAGE

CONTACTS MENU CALL LOG

VOLUME

ABC DEF

JKL MNOGHI

1 2 3

4 5 6

TUV WXYZPQRS

7 8 9

*

[

0 #

.,@

MUTESPEAKER

HEADSET

FORWARD

Avaya one-X

PSAP 2

OK

PHONEMESSAGE


VOLUME

ABC DEF

JKL MNOGHI

1 2 3

4 5 6

TUV WXYZPQRS

7 8 9

*

[

0 #

.,@

MUTESPEAKER

HEADSET

FORWARD

Avaya one-X

Serving

Switch

Serving

Switch

Primary

Serving

Switch

Tandem

S/RPSAP 1

OK

P HONEMES SAGE

C ONTA C TS MENU C A LL LOG

V OLUME

A BC DEF

J KL MNOGHI

1 2 3

4 5 6

T UV W X YZP QRS

7 8 9

*

[

0 #

.,@

MUT ES PE AKE R

HEA DSE T

FORW ARD

Avaya one-X

Tandem

S/RPrimary

PSAP 2

OK

P HONEMES SAGE

C ONTA C TS MENU C A LL LOG

V OLUME

A BC DEF

J KL MNOGHI

1 2 3

4 5 6

T UV W X YZP QRS

7 8 9

*

[

0 #

.,@

MUT ES PE AKE R

HEA DSE T

FORW ARD

Avaya one-X

Alternate

Serving switch supporting multiple PSAP jurisdictions served by different S/R require a primary 9-1-1 Service Provider to be designated



ISSUE: Legacy S/R network must be maintained. Expense of multiple network Inhibits application of enhanced capabilities.

Serving

Switch

Tandem

S/RPSAP 1

OK

PHONEMESSAGE


VOLUME

ABC DEF

JKL MNOGHI

1 2 3

4 5 6

T UV WXYZPQRS

7 8 9

*

[

0 #

.,@

MUT ESPEAKER

HEADSET

FORWARD

Avaya one-X

Tandem

S/RPrimary

PSAP 2

OK

PHONEMESSAGE


VOLUME

ABC DEF

JKL MNOGHI

1 2 3

4 5 6

T UV WXYZPQRS

7 8 9

*

[

0 #

.,@

MUT ESPEAKER

HEADSET

FORWARD

Avaya one-X

Alternate

NENA i3ESInet

RFAI

IMPACT OF MULTIPLE NETWORKS ON PRIMARY SERVICE PROVIDER



Initial transition steps will occur at local and regional 9-1-1 authority levels

Those activities, in turn, will link together into larger regional NG9-1-1 systems

That, then, leads to a logical role for the state to deploy a NG9-1-1 backbone system to support and interconnect.

NG9-1-1 ADOPTION EXPECTATIONS AND ASSUMPTIONS

Proprietary and Confidential 32Synergem © 2011All Rights Reserved.

CONCEPTUAL MULTI-TIERED ESINET DESIGN

CTFE

Metro Ethernet

RegionalHost Site B

4.9 GHz

RegionalHost Site ARegional

ESInet II

Regional Host Site A

Regional Host Site B

MPLS

PSAP 1

PSAP 2

PSAP 3

Regional ESInet I

OC12 Ring

State-Level i3 Core ServicesHost Site A

ESRP A

ECRF A

ESRP B

ECRF B

ESRP

BCF

ESRP

BCF

ESRP

ESRP

BCF

BCF

CTFE

CTFE

CTFE

CTFE

MPLS

T1 Over Sonet

CTFE

State-levelESInet

State-Level i3 Core ServicesHost Site B

SBC

FW

SBC

FW

PSAP 1

PSAP 2

PSAP 3

CTFE

LNG

PRF

LNG

SBC

FW

SBC

FW

Access NetworkESRP A

ECRF A

ESRP B

ECRF B

SBC

FW

SBC

FW

PRF

SBC

FW

SBC

FW

Microw

ave

Metro Ethernet

BCF

BCF

PSAP 1

BCF

BCF

BCF

BCF

BCF

BCF

BCF

BCF

BCF


APPLICATION DEPLOYMENT MODELS

1. Customer Premise Equipment (CPE)2. Hosted (Requires bandwidth & NNI ICAs)3. Software as a Service (SaaS)

The CPE / Hosted model required expensive back room equipment (CPE), software upgrades and system maintenance to ensure the system is operating to standards.


NG9-1-1 TRANSITION PROVISIONING STEPS ~ 9 TO 12 MONTHS

FORMALIZE REGION / FUNDING

ESTABLISH IP BACKBONE

BUILD REGIONAL GIS DATA SET

ACTIVATE SAAS SOLUTIONS

PROVISION NENA I3 FUNCTIONAL ELEMENTS / ESTABLISH ESINET

INTERCONNECT WIRELESS TSPS

INTERCONNECT WIRELINE TSPS


BUYER BEWARE

ENSURE ACCOMPANYING CONTRACT LANGUAGE INCLUDE SLAS

AND SPECIFY THAT THE SYSTEM BEING DEPLOYED IS COMPLIANT

WITH THE NENA I3 END STATE ARCHITECTURE.

• “We support NENA i3.”• “We have an i3 product suite”• NG9-1-1 “Compatible”• NG9-1-1 “Ready”

Statements that do not ensure NENA i3 Compliance:


Myron HerronPresident/COO(866) 859-0911MHERRON@SYNERGEMTECH

.COMWWW.SYNERGEM911.

COMIllustration by Renjith Krishnan


this presentation provides a high level functional comparison between the legacy 9-1-1 and ng9-1-1...

Documents

odel nena

odel slide

nena i3 model

nena i3 specifications

psap b

psap leadership

emergency services ip

psap routing designator