Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability
Key claim: The FCC adopts rules requiring entities that deliver emergency calls in the NG911 environment to implement reliability safeguards and report on interoperability support, while eliminating outdated legacy rules to promote flexible, innovative NG911 service.
Abstract
(Rule · Federal Communications Commission) In this document, the Federal Communications Commission (the FCC or Commission) adopts rules to ensure that emerging Next Generation 911 (NG911) networks are reliable and interoperable. NG911 is replacing legacy 911 technology across the country with internet Protocol (IP)- based infrastructure that will support new 911 capabilities, including text, video, and data. However, for NG911 to be fully effective, NG911 networks must be designed to safeguard the reliability of critical components and support the interoperability needed to seamlessly transfer 911 calls and data from one network to another. The rules require entities essential to delivering emergency calls in the NG911 environment to implement common sense measures to safeguard the reliability of NG911 networks and reduce the risk of 911 outages, and require certain entities to report on their support for NG911 interoperability. The rules also eliminate unnecessary and burdensome legacy rules to increase flexibility and encourage technical innovation to make NG911 services reliable, interoperable, and accessible to all.
Why this matters
NG911 replaces legacy analog 911 trunks with IP-based emergency call delivery, and until now the FCC’s reliability framework was tailored to legacy TDM architecture. By locking in reliability safeguards and interoperability reporting on the entities that actually deliver NG911 traffic — while retiring legacy rules — the FCC sets a baseline that both carriers and public safety answering points must meet, and that NTIA-funded state deployments will effectively have to build against.