Next Generation 911 (NG911) Services

Facilitating Implementation of Next Generation 911 Services (NG911)

In July 2024, the Commission adopted rules to require originating service providers (OSPs) to take actions to start or continue the transition to Next Generation 911 (NG911) in coordination with 911 Authorities.*

NG911 is an Internet Protocol (IP)-based system that— (1) ensures interoperability; (2) is secure; (3) employs commonly accepted standards; (4) enables emergency communications centers to receive, process, and analyze all types of 911 requests for emergency assistance; (5) acquires and integrates additional information useful to handling 911 requests for emergency assistance; and (6) supports sharing information related to 911 requests for emergency assistance among emergency communications centers and emergency response providers. (47 CFR § 9.28.)

In the transition to NG911, state and local 911 authorities are replacing legacy 911 technology with IP-based infrastructure that will support new 911 capabilities, including text, video, and data, and that will improve 911 interoperability, security, and system resilience. For NG911 to work to its full potential, OSPs will need to make certain changes, including upgrading to compatible IP-formats for 911 traffic and delivering 911 traffic to new IP-based delivery points on Emergency Service IP Networks (ESInets), the IP networks that support NG911. The Commission’s NG911 transition requirements at 47 CFR part 9, subpart J support these steps.

NG911 Transition Requirements for OSPs

OSPs are the providers that the public uses to initiate 911 calls, specifically, (1) wireline providers; (2) commercial mobile radio service (CMRS) providers; (3) covered text providers; (4) interconnected Voice over Internet Protocol (VoIP) providers; and (5) Internet-based Telecommunications Relay Service (TRS) providers. (47 CFR § 9.28.)

The Commission’s NG911 rules guide the transition for OSPs to NG911 in two phases. Deadlines for OSP compliance with each phase are discussed in “NG911 Transition Timelines for OSPs” below. Each phase is initiated by a 911 Authority submitting a valid request to OSPs within the jurisdiction where the 911 Authority is located for those OSPs to comply with NG911 requirements. (47 CFR § 9.29(a), (b).) As part of a valid request, the 911 Authority will indicate the relevant NG911 Delivery Points, which are locations, facilities, or demarcation points designated by a 911 Authority where an OSP shall transmit and deliver 911 traffic in an IP format to ESInets or other NG911 network facilities. (47 CFR § 9.28.)

Phase 1: Upon receiving a valid Phase 1 request from a 911 Authority, an OSP must deliver 911 traffic in IP-based Session Initiation Protocol (SIP) format requested by the 911 Authority. The OSP must obtain and deliver 911 traffic to enable to ESInet and other NG911 network facilities to transmit all 911 traffic to the destination PSAP. In addition, the OSP must deliver 911 traffic to NG911 Delivery Points designated by the 911 Authority. The OSP must also complete connectivity testing to confirm that the 911 Authority receives 911 traffic in the IP-based SIP format requested by the 911 Authority. (47 CFR § 9.29(a)(1)-(4).)
Phase 2: Upon receiving a valid Phase 2 request from a 911 Authority, an OSP must comply with all Phase 1 requirements. An OSP must also deliver all 911 traffic bound for the relevant PSAPs to NG911 Delivery Points designated by the 911 Authority in the IP-based SIP format that complies with NG911 commonly accepted standards identified by the 911 Authority. This includes having location information embedded in the call signaling using Presence Information Data Format—Location Object (PIDF-LO) or the functional equivalent. The OSP must install and put into operation all equipment, software applications, and other infrastructure, or acquire all services, necessary to use a Location Information Server (LIS) or its functional equivalent for the verification of its customer location information and records. The OSP must also complete connectivity testing to confirm that the 911 Authority receives 911 traffic in the IP-based SIP format that complies with the identified NG911 commonly accepted standards. (47 CFR § 9.29(b)(1)-(4).)

Cost responsibilities. OSPs are responsible for the costs of complying with the applicable Phase 1 and Phase 2 requirements assigned to them, including the costs of transmitting 911 traffic to NG911 Delivery Points, delivering 911 traffic in the required IP-based SIP format at each phase, including the cost of IP conversion using a Legacy Network Gateway or the functional equivalent, if necessary, and obtaining and delivering location and routing information using ALI/ANI databases, selective routers, or other means at Phase 1, and using LIS functionalities or other equivalent means at Phase 2. OSPs are not responsible for the costs of furnishing, maintaining, or upgrading NG911 Delivery Points, ESInets, Next Generation 911 Core Services networks, or PSAPs. (47 CFR § 9.33.)

Nothing in the Commission’s NG911 transition rules prevents OSPs and 911 Authorities from establishing, by mutual consent, terms different from the NG911 transition rules adopted by the Commission. If 911 Authorities and OSPs agree to establish different terms, OSPs must notify the Commission of the agreement within 30 days. (See “Modification of NG911 Requirements by Mutual Agreement” below.)

NG911 Transition Timelines for OSPs

OSPs must comply with Phase 1 and Phase 2 requirements within certain default periods of time following the valid request of a 911 Authority. Different types of OSPs have different compliance timelines.

Six Months Per Phase: Nationwide CMRS providers, covered text providers, interconnected VoIP providers, and wireline providers other than rural incumbent local exchange carriers (RLECs) have six months following a 911 Authority’s valid Phase 1 request to comply with Phase 1 requirements, and six months following a valid Phase 2 request to comply with Phase 2 requirements. (47 CFR § 9.30(a).)
Twelve Months Per Phase: RLECs, non-nationwide CMRS providers, and Internet-based TRS providers have one year following a 911 Authority’s valid Phase 1 request to comply with Phase 1 requirements, and one year following a valid Phase 2 request to comply with Phase 2 requirements. (47 CFR § 9.30(b).)

In the event that a 911 Authority makes a valid Phase 2 request before the OSP is compliant with Phase 1 requirements or makes a valid Phase 2 request before the Phase 1 implementation deadline, the NG911 rules sequence OSP Phase 2 compliance deadlines following either actual Phase 1 compliance or the Phase 1 compliance deadline (whichever occurs first). (47 CFR § 9.30(a)(2)(ii), (b)(2)(ii).)

When an OSP is subject to both six- and twelve-month timelines for different services on the same network as the result of a 911 Authority’s valid request, the OSP may comply with its obligations under the later of the two deadlines.

911 Authorities and OSPs may mutually agree to timelines different from the default six- and twelve-month timelines described here. If 911 Authorities and OSPs agree to modify timelines, OSPs must notify the Commission of the agreement within 30 days. (See “Modification of NG911 Requirements by Mutual Agreement” below.)

NG911 Valid Requests for 911 Authorities

A 911 Authority is a state, territorial, regional, Tribal, or local governmental entity that operates or has administrative authority over all or any aspect of a communications network for the receipt of 911 traffic at NG911 Delivery Points and for the transmission of such traffic from that point to PSAP. (47 CFR § 9.28.)

911 Authorities may request that OSPs deliver 911 traffic by issuing a valid request to initiate OSP compliance timelines under Commission’s NG911 rules. For both Phase 1 and Phase 2, 911 Authorities must meet specific readiness criteria in order to make a valid request for OSP delivery of 911 traffic.

Phase 1: To request delivery of 911 traffic at Phase 1, a 911 Authority must certify that it has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format and to transmit such traffic to the PSAP(s) connected to it; certify that it has obtained commitments from any ESInet provider, Next Generation 911 Core Services provider, and/or call handling equipment provider needed to facilitate and complete connectivity testing within the compliance timeframe applicable to the OSP; certify that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format; identify the NG911 Delivery Point(s) designated; and provide notification to the OSP that includes these certifications and information. (47 CFR § 9.31(a)(1)-(5).)
Phase 2: To request delivery of 911 traffic at Phase 2, a 911 Authority must certify that it has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format that complies with NG911 commonly accepted standards and transmit such traffic to the PSAP(s) connected to it; certify that its ESInet is connected to a fully functioning Next Generation 911 Core Services network that can provide access to a Location Validation Function and interface with a Location Information Server or its functional equivalent provided by the OSP; certify that it has obtained commitments from any ESInet provider, Next Generation 911 Core Services provider, and/or call handling equipment provider needed to facilitate and complete connectivity testing within the compliance timeframe applicable to the OSP; certify that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format that complies with NG911 commonly accepted standards; identify the NG911 Delivery Point(s) designated; and provide notification to the OSP that includes these certifications and information. (47 CFR § 9.31(b)(1)-(6).)

Notification and Registry. 911 Authorities may notify OSPs of valid requests via a registry made available by the Commission or any other written notification reasonably acceptable to the OSP. (47 CFR § 9.31(a)(5), (b)(6).) The Commission does not require 911 Authorities to use the registry to notify OSPs of Phase 1 and Phase 2 requests, and as an alternative, 911 Authorities may notify OSPs of Phase 1 and Phase 2 Requests by direct written notification.

The Public Safety and Homeland Security Bureau (Bureau) will develop, implement, and maintain a centralized electronic registry for submission of Phase 1 and Phase 2 requests by 911 Authorities. The Bureau will also open a new docket and issue a Public Notice with guidance for 911 Authorities to issue NG911 valid requests.

NG911 Delivery Points. A 911 Authority may designate one or more NG911 Delivery Points to which OSPs must deliver 911 traffic under these rules. (47 CFR § 9.32.) Each NG911 Delivery Point must be located in the same state or territory as the PSAPs connected to the ESInet. (47 CFR § 9.32(a).) Additionally, the 911 Authority or the ESInet must provide facilities at the input to the NG911 Delivery Point to receive 911 traffic in accordance with the phase requested. (47 CFR § 9.32(b).)

OSP Petitions to Challenge 911 Authority Requests

Within 60 days of the receipt of a Phase 1 or 2 request from a 911 Authority, an OSP may submit a petition to the Bureau challenging the request, subject to certain procedural requirements. (47 CFR § 9.31(c).) The Bureau may review the petition and determine whether to pause the implementation deadline for that originating service provider, affirm the request of the 911 Authority as valid, or take other action as necessary. (Id.)

Modification of NG911 Requirements by Mutual Agreement

911 Authorities and OSPs may establish, by mutual consent, terms different from the requirements in the Commission’s NG911 rules. (47 CFR § 9.34(a).) The OSP must notify the Commission of the agreement within 30 days of the execution of the agreement. In that notification, the OSP must identify each requirement in the rules that is impacted by the agreement and must state how the terms of the agreement differ from each impacted rule. (47 CFR § 9.34(b).) The OSP must also notify the Commission if there is an amendment, modification, or termination of the agreement. (Id.)

Effective and Compliance Dates

The Commission’s NG911 rules took effect on November 25, 2024. Certain provisions of the rules (pertaining to valid requests, compliance deadlines, challenges to requests, and modifications of the NG911 requirements by mutual agreement) contain information collection and recordkeeping requirements that must be approved by the Office of Management and Budget (OMB) under the Paperwork Reduction Act. The Bureau has initiated the OMB review process, but compliance with these specific provisions will not be required until OMB approves the information collection. More information may be found here.

* The summary of the NG911 rules on this webpage does not include the full text of the rules, and does not replace or supersede the rules. Although the Bureau has attempted to cover all parts of the rules that might be relevant, the coverage may not be exhaustive, and the timeline may not anticipate all situations in which the rules apply. This summary represents the Bureau’s interpretation of the rules and is not legally binding on the Commission. Furthermore, the Commission retains the discretion to adopt case-by-case approaches, where appropriate, that may differ from the approach in this webpage. Any decision regarding a particular regulated entity will be based on the statutes and any relevant rules. The full text of the 911 rules codified in 47 CFR Part 9 can be found here.

Resources

911 Regulations – 47 CFR Part 9
NG911 Requirements – 47 CFR §§ 9.27-9.34
NG911 Report and Order Federal Register Notice – 89 Fed. Reg. 78066
Small Entity Compliance Guide – DA 24-1138

The FCC will closely monitor any complaints about alleged violations of these 911 rules.

Consumers may file a complaint via the Consumer Complaint Center.
Public Safety Answering Points (PSAPs), also known as 911 call centers, and other public safety entities may request support from the Public Safety and Homeland Security Bureau and notify the Bureau of problems or issues affecting the provision of emergency services through the Public Safety Support Center.