Local PSAP IP Network Infrastructure and NG9-1-1

Local PSAP IP Network

Infrastructure and NG9-1-1

Michael Smith, DSS

Nate Wilcox, Emergicom

Jim Lockard, ENP, Consultant

What we’ll cover

Network Requirements

Common for any ESInet

Special PSAP Requirements

Things that will drive a PSAP network design

NENA Development Conference | October 2014 | Orlando, Florida

What is an ESInet?

Just the network

Not the NG9-1-1 Core Services

Includes hardware and software

Designed to support the NG9-1-1 Core

Services and Other Public Safety

Applications


Is a PSAP network just another ESInet?

Yes!

And, of course, no!

It’s an ESInet with a few additional requirements


What major factors drive PSAP network design?

The applications, services, and interfaces it must support

The critical nature of 9-1-1 itself

Policies


PSAP Virtualization and network design

Elements of a PSAP could be anywhere

But the design drivers remain the same


The i3 solution

The i3 solution: NENA 08-003 (STA-010)

NG9-1-1 Core Services

A PSAP is a Service itself

The i3 specifications drive network requirements common to PSAP networks


The i3 solution i3 Compliant

Originating

Network

SIP

Legacy

Originating

Network

MF/SS7 Legacy

Network

Gateway

SIP

B

C

F

ECRF

LoST

ESRP

ECRF

LoST

SIP i3 ESInet

ESRP

SIP

B

C

F

SIP i3

PSAP

Legacy

PSAP

Gateway

MF/E-MF/DTMF

ALI Interface

Legacy

PSAP

ALI – Automatic Location Identification

ECRF – Emergency Call Routing Function

ESRP – Emergency Services Routing Proxy

PSAP – Public Safety Answering Point

BCF – Border Control Function

ESInet – Emergency Services IP Network


Is a Domain really required?

Yes!

Why can’t I just have a “peer” or

“workgroup” style network?


What other common infrastructure is required?

For managing and monitoring

For protecting and securing

For reliability and availability

For ensuring quality of service


Security for Next-Generation 9-1-1

Security for Next-Generation 9-1-1 (NG-

SEC)

Security is driver for network design

PSAPs must not be the weak link


Emergency Services IP Network Design for

NG9-1-1

A NENA Informational document

Outlines issues to consider

Provides guidance for design

Applies to all ESInets


Emergency Services IP Network Design for

NG9-1-1

OSI Layers 1, 2 and 3

Availability and Reliability

Network Security

Performance

Traffic Engineering and more…


Supporting PSAP interfaces to the serving

ESInet

Application Interfaces drive some underlying network requirements

SIP Call Interface

Additional Data

Management and Monitoring


Performance requirements

Bandwidth requirements

Media and Metadata

Event and Media Recording

Traffic Prioritization


Availability and Reliability

What is “five nines”?

How do you achieve five nines?

What’s the difference between

Availability and Reliability?

MTBF and MTTR


Network Management and Monitoring

ESInets must be monitored

Mechanisms for monitoring:

SNMP – v3 vs. v2

Traffic Monitoring

Syslog – what it does

Proprietary mechanisms


Network Management and Monitoring

Mechanisms for Managing ESInets

As-built documentation

Service Level Agreements

Traffic

Capacity / Trending Analysis

Configuration Management


PSAP Connectivity (OSI Layer 1)

The Last Mile

Copper, Fiber, RF, Satellite

Reliability and Availability

Redundant and Diverse Paths


The data link layer (OSI Layer 2)

T1/T3

Frame Relay

ATM

MPLS

Metro Ethernet


The IP Layer (OSI Layer 3)

Dynamic Routing Protocols

There are choices

OSPF, EIGRP, etc.

The choices drive design requirements


IPv4 and IPv6

IPv4 is what we’ve seen for years:

179.166.10.1

We’ve run out of public addresses

IPv6 allows for more addresses:

2001:0db8:85a3:0042:1000:8a2e:0370:7334

Build for IPv6 out of the box


Traffic Engineering

Study your bandwidth requirements

Media consumes a lot – video and audio the most

Text consumes less, but is still significant

Bandwidth and DDOS attacks


Quality of Service

What is QoS

Why do we need it

What design criteria does it drive?


Prioritizing network traffic

What is “DiffServ”?

Why does the i3 architecture require it?

What elements must support it?

How does that drive network design?


What’s special about a PSAP network?

The PSAP network has the same basic requirements as any ESInet – it is an

ESInet

But it has a few additional ones, driven by the job a PSAP does


What’s special about a PSAP network?

The PSAP will likely be connected to other networks that require different, and possibly conflicting network policies

Data services drive these policies (NCIC, LEO DB)

How do we mediate these?

And mitigate risks to disparate networks?


Policy impact on network design , and vice-versa

How do your policy choices impact the network you design?

How will your network design impact your policy choices?


The “separate networks” issue

Why do vendors sometimes insist on a separate physical network for their applications?

Why does it matter?

Why is that a problem in NG9-1-1?


Interconnection to other networks

Connecting to certain data services like

NLETS and LEO carry restrictive security requirements

Connecting to less-secure networks introduce additional risks


The “Internet”

Both the PSAP and the ESInet that provides

NG Core Services to it will likely be connected to the Internet

Why?

What special design problems does this introduce?


Local “Administrative” networks

Most PSAP will be connected to one or more “Administrative” networks

Examples?

How does this impact network design?


Questions, Comments?



This Is How a Title

Slide Looks

Chris Nussman, Comms Director

NENA: The 9-1-1 Association

Successful Slides & Presentations

Bullets, not paragraphs

Keep the type big so those in the back of the room don’t have to squint

Clip art is not OK

Don’t read from slides; ask questions


Local PSAP IP Network Infrastructure and NG9-1-1

Local PSAP IP Network

Infrastructure and NG9-1-1

Questions, Comments?

This Is How a Title

Slide Looks

Related documents

Products

Support

Local PSAP IP Network Infrastructure and NG9-1-1