FCC compliance can feel like threading a legal needle—especially with new Next Generation 911 (NG911) requirements now in effect. As of March 25, 2025, 911 Authorities can request NG911 service, triggering compliance obligations for Originating Service Providers (OSPs). If you haven’t started preparing, now’s the time. Fortunately, Intrado NG Nexus simplifies the process.
Below, we break down the key questions and answers you need to know as you prepare your organization to meet FCC regulatory requirements and support the transition to NG911.
Q: What is FCC 24-78?
A: FCC 24-78 lays out a framework for OSPs to deliver SIP and i3-formatted interactions to PSAPs. The move facilitates the transition to NG911 which offers greater resiliency and interoperability, as well as the enablement of text, photo, video, and data sharing to improve emergency response outcomes.
Under the order, wireline, CMRS, covered text, interconnected VoIP, and internet-based TRS providers are all considered OSPs, and the mandate includes a phased approach to support the transition.
Q: What are the phases of the transition?
A: The order defines two phases of readiness. During Phase 1, OSPs must deliver 911 traffic using an IP-based SIP format as defined by the local authority. In Phase 2, OSPs must deliver 911 traffic using i3-enabled SIP as defined by standards-based NG911.
Q: When is the compliance deadline?
A: That depends. While the rules are in effect now, your compliance timeline begins as soon as a valid service request is issued by the 911 Authority. The transition framework states that nationwide OSPs have six months and non-nationwide OSPs have twelve months to become compliant. However, it should be noted that an extension may be requested by an OSP – ideally in cooperation with the PSAP. You should also be aware that you may not receive a service request directly.
Q: How am I supposed to know if we’re not notified directly?
A: There are two methods for requesting service. While some PSAPs may choose to send notice directly to your organization, other PSAPs may opt for filing service requests on the FCC’s Electronic Comment Filing System (ECFS). We encourage all OSPs to keep a watchful eye on the docket to make sure nothing slips through the cracks. You can check the docket here.
The compliance timeline kicks in once the request is submitted – whether directly or via the docket – so make sure to act quickly.
Q: What must be included for a service request to be considered valid?
A: We tackled this subject recently in our blog, “NG911 Service Requests & FCC 24-78: A Quick Guide for PSAPs.” In addition to summarizing the key requirements, we shared the FCC’s Valid Request Form as well as a report from ATIS that includes a sample request form.
As noted in the blog post, the FCC form has the required information while the ATIS form has additional details that can streamline the testing and implementation process. Familiarizing yourself with these resources can help you understand what to expect when you receive requests.
Q: So, how can we comply with FCC 24-78 rules?
A: While circumstances vary among OSPs, using in-house resources to achieve compliance with these rules may be possible; however, it will involve significant logistical and technical efforts to overhaul and implement new data transmission.
Complying with the order is complex because it requires status management of every PSAP where an OSP delivers traffic, meaning every PSAP must be tracked to determine whether it is completely NG911 ready (SIP in an i3 format), partially deployed (SIP), or not yet deployed (TDM). And 911 traffic must be delivered in the format requested by each PSAP. That’s where NG Nexus comes in.
Q: What is NG Nexus?
A: NG Nexus is a fully managed, hosted solution that simplifies compliance and ensures seamless interoperability between legacy and NG911 systems. It offers a complete solution for all phases, providing deep expertise, ongoing support throughout the process, and worry-free compliance.
Q: What does NG Nexus include?
A: You can download our product brief for a more complete list of features, but in short NG Nexus offers:
Superior Caller Location and Routing: Utilizes LIS, RDF, LRF, HELD/ADR, IPv6, and other technologies for precise call routing and location accuracy.
Seamless Compliance: Tracks PSAP statuses and delivers emergency traffic in the correct format (legacy TDM, SIP, or i3) to ensure regulatory requirements are met.
End-to-End Management: A qualified team of experts handles RFS tracking, certificate management, and ongoing interoperability testing.
Future-Ready Technology: Supports emerging standards like EIDO and Forest Guide for optimal service quality and future-proof deployment.
Intrado also provides proven public safety expertise. With over 45 years of leading 911 innovation, Intrado is the trusted partner for OSPs and the public safety community. With Intrado’s solution, OSPs avoid maintaining the routing, ESInet requests, and format capabilities for each network’s standards. NG Nexus works seamlessly regardless of network and devices, and there are no net new operational needs.
Q: I’ve received a request. What now?
A: The first thing you should do is review the request to ensure it’s complete. Flag incomplete requests and follow up with the PSAP/911 Authority to obtain the missing information. Then, if you’ve selected NG Nexus, you can send valid requests to our team. We pick up the ball from there!
The clock is ticking once you receive an NG911 service request. And it’s only a matter of time until compliance is required. Get started now by reaching out to your account team or use the form on the right to get in touch.
