By a unanimous vote on July 18, 2024, the Federal Communications Commission took a groundbreaking step forward to accelerate the transition to end-to-end Next Generation 911 (NG911) in the United States. The Commission’s action will boost efforts to modernize emergency services by advancing the transition to an IP-based 911 system, promising faster, more efficient responses during critical situations.
Intrado was an active participant in shaping these rules, meeting several times with the FCC to talk about the key decisions for extending NG911 and what it’s like to work, on the one hand, with PSAPs who are preparing and, on the other hand, with the OSPs who will initiate NG911 service to the PSAP. I’m glad to see that the Commission incorporated a lot of what we said into the final order.
The PSAP community is pleased with the outcome. Upon news of the vote, Brian Fontes, CEO of the National Emergency Number Association, remarked that the ruling would be an opportunity for stakeholders to work together on a plan forward and that the move would improve 911 services “for everyone, especially those who depend on inclusive services, like deaf or hard-of-hearing individuals.”
So, let’s discuss the key elements of the decision and do a little forecasting.
Understanding the NG911 Transition
Aside from improved accessibility and inclusivity, there are several motivating factors behind the push to IP.
- Cost Savings: Time Division Multiplexing (TDM) is an outdated, legacy solution that is expensive to maintain and operate. Plus, it’s getting harder and harder to procure these circuits as providers across the country seek to turn down this technology in favor of IP.
- Efficiency & Reliability: IP-based systems allow for a more direct route – and alternate routes – for traffic to flow, bypassing common TDM failure points.
- Better Data: IP is more media-friendly, allowing data sharing beyond what legacy TDM interfaces can handle. This includes text messages, as well as photo and video delivery.
Technical issues aside, the biggest challenge may be how to fund the rest of the transition. The public safety community has been vocal about its desire to move forward with NG911 for years, but funding the transition has been an ever-present challenge.
In his statement last week, Mr. Fontes added, “Now, it is crucial that Congress commit to fully funding the NG911 transition. Without federal help, local governments will struggle for years to maintain current 911 operations while simultaneously building, testing, and performing a perfect cutover to NG911.” He’s right, and we’re seeing this every day.
What This Means for 911 Authorities and Their PSAPs
The Commission’s decision outlines specific responsibilities for 911 Authorities, including:
- Designation of Delivery Points for 911 Traffic: These must be within the state or territory where the 911 Authority and PSAPs are located.
- Valid Requests: These can be submitted through written notification to the Originating Service Providers (OSPs) that serve the PSAP or to a Commission registry (currently under development) that OSPs will be obligated to check periodically. To be valid, a request must be based on actual operational readiness and must include the NG911 Delivery Point location and certification of readiness to receive and transmit 911 traffic in Session-Initiated Protocol (SIP) (a Phase 1 request) or i3 (a Phase 2 request). PSAP requests must also indicate that their NG911 provider is available to complete testing and deployment.
I should probably mention that OSPs may challenge PSAP readiness by asking the Commission’s Public Safety and Homeland Security Bureau to evaluate. Throughout the Commission’s decision, however, it’s obvious that the rules are the default, and OSPs and 911 Authorities/PSAPs have the leeway to make alternate arrangements to avoid challenges. The Commission also recognized the importance of the NG911 Core Service Provider in this process. This is where Intrado can be particularly helpful in facilitating an understanding between the OSP and the PSAP.
While there are still obstacles ahead for many PSAPs with funding and implementing NG911, the timeline and expectations are clearer for OSPs: if they serve areas that have not yet transitioned to NG911, they must begin to plan now.
What This Means for OSPs
The FCC’s decision mandates that OSPs – including wireline, Commercial Mobile Radio Service (CMRS), text, interconnected VoIP, and internet-based TRS providers – shift to NG911 in two phases. Similar to the approach the FCC adopted twenty-plus years ago for the transition to Enhanced 911, this phased rollout is designed to ensure smooth transition while maintaining the integrity and reliability of emergency services.
- Phase 1: OSPs must deliver 911 traffic in IP-based SIP format to designated Delivery Points set by the 911 Authority.
- Phase 2: OSPs must deliver 911 traffic in IP-based SIP format that supports routing, caller location, and the transmission of emergency information in accordance with NG911 commonly accepted standards, often referred to as i3 formatting.
Key Deadlines
The FCC structure includes deployment timelines for OSPs following a PSAP request for service. In addition, the transition to Phase 1 will generally be completed before starting Phase 2, while allowing PSAPs and OSPs to reach agreements to progress directly to Phase 2 where appropriate.
Compliance timelines are as follows:
- Six months for non-rural wireline, nationwide CMRS, text, and VoIP providers.
- Twelve months for Rural Local Exchange Carriers (RLECs), non-nationwide CMRS, and internet-based Telecommunications Relay Service providers.
Don’t Delay: Act Now to Ensure You Meet Deadlines with Ease.
PSAPs are expected to start issuing valid NG911 requests by the end of April 2025. Nationwide OSPs have six months to comply, while regional OSPs have 12 months. Delays could lead to FCC fines and service disruptions. Learn about Intrado NG Nexus.
