https://urgentcomm.com/wp-content/themes/ucm_child/assets/images/logo/footer-new-logo.png
  • Home
  • News
  • Multimedia
    • Back
    • Multimedia
    • Video
    • Podcasts
    • Galleries
    • IWCE’s Video Showcase
    • Product Guides
  • Commentary
    • Back
    • Commentary
    • Urgent Matters
    • View From The Top
    • All Things IWCE
    • Legal Matters
  • Resources
    • Back
    • Resources
    • Webinars
    • White Papers
    • Reprints & Reuse
  • IWCE
    • Back
    • IWCE
    • Conference
    • Special Events
    • Exhibitor Listings
    • Premier Partners
    • Floor Plan
    • Exhibiting Information
    • Register for IWCE
  • About Us
    • Back
    • About Us
    • Contact Us
    • Advertise
    • Terms of Service
    • Privacy Statement
    • Cookie Policy
  • Related Sites
    • Back
    • American City & County
    • IWCE
    • Light Reading
    • IOT World Today
    • Mission Critical Technologies
    • TU-Auto
  • In the field
    • Back
    • In the field
    • Broadband Push-to-X
    • Internet of Things
    • Project 25
    • Public-Safety Broadband/FirstNet
    • Virtual/Augmented Reality
    • Land Mobile Radio
    • Long Term Evolution (LTE)
    • Applications
    • Drones/Robots
    • IoT/Smart X
    • Software
    • Subscriber Devices
    • Video
  • Call Center/Command
    • Back
    • Call Center/Command
    • Artificial Intelligence
    • NG911
    • Alerting Systems
    • Analytics
    • Dispatch/Call-taking
    • Incident Command/Situational Awareness
    • Tracking, Monitoring & Control
  • Network Tech
    • Back
    • Network Tech
    • Interoperability
    • LMR 100
    • LMR 200
    • Backhaul
    • Deployables
    • Power
    • Tower & Site
    • Wireless Networks
    • Coverage/Interference
    • Security
    • System Design
    • System Installation
    • System Operation
    • Test & Measurement
  • Operations
    • Back
    • Operations
    • Critical Infrastructure
    • Enterprise
    • Federal Government/Military
    • Public Safety
    • State & Local Government
    • Training
  • Regulations
    • Back
    • Regulations
    • Narrowbanding
    • T-Band
    • Rebanding
    • TV White Spaces
    • None
    • Funding
    • Policy
    • Regional Coordination
    • Standards
  • Organizations
    • Back
    • Organizations
    • AASHTO
    • APCO
    • DHS
    • DMR Association
    • ETA
    • EWA
    • FCC
    • IWCE
    • NASEMSO
    • NATE
    • NXDN Forum
    • NENA
    • NIST/PSCR
    • NPSTC
    • NTIA/FirstNet
    • P25 TIG
    • TETRA + CCA
    • UTC
Urgent Communications
  • NEWSLETTER
  • Home
  • News
  • Multimedia
    • Back
    • Video
    • Podcasts
    • Omdia Crit Comms Circle Podcast
    • Galleries
    • IWCE’s Video Showcase
    • Product Guides
  • Commentary
    • Back
    • All Things IWCE
    • Urgent Matters
    • View From The Top
    • Legal Matters
  • Resources
    • Back
    • Webinars
    • White Papers
    • Reprints & Reuse
    • UC eZines
    • Sponsored content
  • IWCE
    • Back
    • Conference
    • Why Attend
    • Exhibitor Listing
    • Floor Plan
    • Exhibiting Information
    • Join the Event Mailing List
  • About Us
    • Back
    • About Us
    • Contact Us
    • Advertise
    • Cookie Policy
    • Terms of Service
    • Privacy Statement
  • Related Sites
    • Back
    • American City & County
    • IWCE
    • Light Reading
    • IOT World Today
    • TU-Auto
  • newsletter
  • In the field
    • Back
    • Internet of Things
    • Broadband Push-to-X
    • Project 25
    • Public-Safety Broadband/FirstNet
    • Virtual/Augmented Reality
    • Land Mobile Radio
    • Long Term Evolution (LTE)
    • Applications
    • Drones/Robots
    • IoT/Smart X
    • Software
    • Subscriber Devices
    • Video
  • Call Center/Command
    • Back
    • Artificial Intelligence
    • NG911
    • Alerting Systems
    • Analytics
    • Dispatch/Call-taking
    • Incident Command/Situational Awareness
    • Tracking, Monitoring & Control
  • Network Tech
    • Back
    • Cybersecurity
    • Interoperability
    • LMR 100
    • LMR 200
    • Backhaul
    • Deployables
    • Power
    • Tower & Site
    • Wireless Networks
    • Coverage/Interference
    • Security
    • System Design
    • System Installation
    • System Operation
    • Test & Measurement
  • Operations
    • Back
    • Critical Infrastructure
    • Enterprise
    • Federal Government/Military
    • Public Safety
    • State & Local Government
    • Training
  • Regulations
    • Back
    • Narrowbanding
    • T-Band
    • Rebanding
    • TV White Spaces
    • None
    • Funding
    • Policy
    • Regional Coordination
    • Standards
  • Organizations
    • Back
    • AASHTO
    • APCO
    • DHS
    • DMR Association
    • ETA
    • EWA
    • FCC
    • IWCE
    • NASEMSO
    • NATE
    • NXDN Forum
    • NENA
    • NIST/PSCR
    • NPSTC
    • NTIA/FirstNet
    • P25 TIG
    • TETRA + CCA
    • UTC
acc.com

NG-911


Failure-proofing NG-911 networks

  • Written by
  • 3rd June 2013
While separate voice and data networks might be the instinctive approach, it also would be the wrong one in an IP environment.

What is in this article?

  • Failure-proofing NG-911 networks
  • Maricopa 911’s approach

Failure-proofing NG-911 networks

Emergency-response operations deal with life-and-death situations on a regular basis. Callers must be able to reach 911 telecommunicators every hour of every day. Service cannot be interrupted—not even briefly—and communications must be clear. Anything less than 100% reliability is unacceptable.

Accomplishing this level of reliability as public-safety answering points (PSAPs) move to VoIP, add support for video, and integrate voice and data networks requires a comprehensive look at the emergency operators’ network architecture. This article discusses some of the issues faced by the transition to IP within the wide-area network (WAN) and proposes a network architecture that will provide the required reliability.

Operations are vulnerable to failed and low-quality links—The FCC’s Network Reliability and Interoperability Council (NRIC) requires that "the Emergency Services Network should be designed such that no single failure or interruptive incident (i.e., a cable cut) will create a system outage."

To accomplish this goal and ensure that a single network-link failure will not create a network outage, network architects traditionally have relied on redundant links and automatic failover. In this type of architecture, a failover mechanism typically senses the malfunction and activates a route change, so that traffic begins to use the redundant link. But often that self-healing process takes some time to implement; routing convergence time can take between 6 seconds to a minute. During that time period, existing calls will go silent, some call sessions may disconnect and new calls cannot be initiated.

Even more concerning is that the effect of a hard failure may not be limited to the calls themselves. In many 911 operations, the network also supports a control channel carrying CallManager-to-CallManager traffic. In the best case, there would be dead air. In the worst case, calls would drop, the phones would have to re-register and the CallManagers would get out of sync, which could take about two minutes to recover.

A less-visible, soft failure can be even more disruptive over a longer period of time. A link may have quality issues—jitter, delay or packet loss—that limit its ability to transport voice data reliably. But many failover solutions available today only recognize that the link is "up," not that it is degraded. Often, the only way a network administrator would become aware of a circuit brownout is through a network-monitoring tool. In those circumstances, manual intervention may be required to route voice traffic to a better-performing backup link. During that intervening time period, voice quality will be compromised, and manual intervention then would be required to return to the primary state when the brownout condition is resolved.

The data network is as important as VoIP—While call quality and high availability are necessary to ensure that the voice network is operating, the network connections to systems—for example, automatic location information and radio dispatch—are just as critical to PSAP operations. When an analog voice system was used, this data network was a distinctly different network. But as call centers move to VoIP technology, network architects have an option to combine both types of data on a single network or keep them distinct.

At first glance, it would appear that separating the two networks prevents a single failure from affecting both the voice and data networks. But in reality, accomplishing fully redundant distinct networks would require four different network access links—one primary and one backup for voice and one primary and one backup for data. But, in many locations, there aren’t that many truly diverse service providers. Building distinct data and voice networks that are dependent on the same ISP for network access means that the two systems aren’t actually distinct; the infrastructure and network costs are doubled, but both networks still are vulnerable to a single network-link outage.

A better architecture is a combined data and voice network. This minimizes complexity, cost and management overhead, although it brings with it a unique set of challenges, primarily in the area of traffic prioritization and bandwidth reservation. In a shared network, it is critical to ensure that there is available bandwidth for each type of traffic and that different traffic types can be identified and given different levels of prioritization.

Mitigating the risks associated with VoIP and converged networks—Fortunately, there are solutions available in the market today with features that resolve these issues, including the ability to mitigate hard and soft failures before they affect the service. Network architects should expect their networks to have the following capabilities:

Sub-second failover—The switch from failed link to operative backup should be performed so quickly that no calls are dropped and the failure is unnoticeable to callers.

Quality monitoring—Every link should be monitored continuously for quality, and technology should be implemented that routes traffic from underperforming links before call quality is affected and communication becomes compromised.

Packet duplication—VoIP calls and other types of data can be selectively duplicated and sent over two diverse paths simultaneously, ensuring that no single link failure or poor circuit quality will impact a call.

Network diversity—At least two completely diverse links are required to have any real redundancy; ideally, both a wired and a wireless network should be supported.

Sufficient bandwidth—Available bandwidth must be adequate to handle widespread emergencies that can result in very large numbers of simultaneous calls.

Intra-session load balancing—A single session should be able to simultaneously use more than one link to speed up large data transfers, such as database backups, without impacting voice and critical system traffic.

1 | 2 |
Maricopa 911’s approach
Tags: PSAP NG-911 Public Safety System Design Article

One comment

  1. Avatar Anonymous 12th June 2013 @ 11:17 am
    Reply

    Northampton County, PA was
    Northampton County, PA was just down recently due to a fiber cable cut that created a large outage.

Leave a comment Cancel reply

To leave a comment login with your Urgent Comms account:

Log in with your Urgent Comms account

Or alternatively provide your name, email address below:

Your email address will not be published. Required fields are marked *

Related Content

  • Failure-proofing NG-911 networks
  • Failure-proofing NG-911 networks
  • Failure-proofing NG-911 networks
  • Failure-proofing NG-911 networks

Commentary


How 5G is making cities safer, smarter, and more efficient

26th January 2023

3GPP moves Release 18 freeze date to March 2024

18th January 2023

Do smart cities make safer cities?

  • 1
6th January 2023
view all

Events


UC Ezines


IWCE 2019 Wrap Up

13th May 2019
view all

Twitter


UrgentComm

Phishers trick Microsoft into granting them ‘verified’ Cloud Partner status dlvr.it/Shqngn

2nd February 2023
UrgentComm

Shapeshifting robot can morph from a liquid to a solid dlvr.it/Shqk9K

2nd February 2023
UrgentComm

Automakers against stampede to BEV dominance dlvr.it/ShpX08

2nd February 2023
UrgentComm

FCC nominee Gigi Sohn headed for third Senate hearing dlvr.it/ShpDcZ

1st February 2023
UrgentComm

Sign up to learn how to successfully manage your Motorola ASTRO® 25 System: spr.ly/60143j8fp https://t.co/XcxiUwzN27

1st February 2023
UrgentComm

Hytera parent cites financial health, but unable to make royalty payment to Motorola Solutions dlvr.it/ShlrlM

1st February 2023
UrgentComm

NATE: Todd Schlekeway highlights organization’s safety, legislative initiatives dlvr.it/ShljHj

1st February 2023
UrgentComm

Cybercrime ecosystem spawns lucrative underground Gig Economy dlvr.it/ShkKbf

31st January 2023

Newsletter

Sign up for UrgentComm’s newsletters to receive regular news and information updates about Communications and Technology.

Expert Commentary

Learn from experts about the latest technology in automation, machine-learning, big data and cybersecurity.

Business Media

Find the latest videos and media from the market leaders.

Media Kit and Advertising

Want to reach our digital and print audiences? Learn more here.

DISCOVER MORE FROM INFORMA TECH

  • American City & County
  • IWCE
  • Light Reading
  • IOT World Today
  • Mission Critical Technologies
  • TU-Auto

WORKING WITH US

  • About Us
  • Contact Us
  • Events
  • Careers

FOLLOW Urgent Comms ON SOCIAL

  • Privacy
  • CCPA: “Do Not Sell My Data”
  • Cookie Policy
  • Terms
Copyright © 2023 Informa PLC. Informa PLC is registered in England and Wales with company number 8860726 whose registered and Head office is 5 Howick Place, London, SW1P 1WG.