47 CFR Part 9 — 911 Requirements

PART 9—911 REQUIREMENTS Authority: 47 U.S.C. 151-154, 152(a), 155(c), 157, 160, 201, 202, 208, 210, 214, 218, 219, 222, 225, 251(e), 255, 301, 302, 303, 307, 308, 309, 310, 316, 319, 332, 403, 405, 605, 610, 615, 615 note, 615a, 615b, 615c, 615a-1, 616, 620, 621, 623, 623 note, 721, and 1471, and Section 902 of Title IX, Division FF, Pub. L. 116-260, 134 Stat. 1182, unless otherwise noted. Source: 84 FR 66760, Dec. 5, 2019, unless otherwise noted. Subpart A—Purpose and Definitions § 9.1 Purpose. The purpose of this part is to set forth the 911, E911, and Next Generation 911 service requirements and conditions applicable to telecommunications carriers (subpart B); commercial mobile radio service (CMRS) providers (subpart C); interconnected Voice over internet Protocol (VoIP) providers (subpart D); internet-based providers of telecommunications relay services (TRS) for persons with disabilities (subpart E); multi-line telephone systems (MLTS) (subpart F); and Mobile-Satellite Service (MSS) providers (subpart G). The rules in this part also include requirements to help ensure the resiliency, redundancy, and reliability of 911 communications systems (subpart H), acceptable obligations and expenditures of 911 fees (subpart I), and Next Generation 911 obligations (subpart J). [89 FR 78128, Sept. 24, 2024] § 9.2 [Reserved] § 9.3 Definitions. Terms with definitions including the “(RR)” designation are defined in the same way in § 2.1 of this chapter and in the Radio Regulations of the International Telecommunication Union. 911 calls. Alternative location information. Appropriate local emergency authority. Automated dispatchable location. Automatic Location Information (ALI). Automatic Number Identification (ANI). Commercial mobile radio service (CMRS). (1)(i) Provided for profit, i.e., (ii) An interconnected service; and (iii) Available to the public, or to such classes of eligible users as to be effectively available to a substantial portion of the public; or (2) The functional equivalent of such a mobile service described in paragraph (1) of this definition. (3) A variety of factors may be evaluated to make a determination whether the mobile service in question is the functional equivalent of a commercial mobile radio service, including: Consumer demand for the service to determine whether the service is closely substitutable for a commercial mobile radio service; whether changes in price for the service under examination, or for the comparable commercial mobile radio service, would prompt customers to change from one service to the other; and market research information identifying the targeted market for the service under review. (4) Unlicensed radio frequency devices under part 15 of this chapter are excluded from this definition of Commercial mobile radio service. Common carrier carrier. Communications assistant (CA). Configured. Designated PSAP. Device-based location information. Dispatchable location. Earth station. (1) With one or more space stations; or (2) With one or more stations of the same kind by means of one or more reflecting satellites or other objects in space. (RR) Emergency Call Center. Feeder link. Fixed-Satellite Service (FSS). Handset-based location technology. iTRS access technology. Improvement to the hardware or software of the system. Interconnected VoIP service. (i) Enables real-time, two-way voice communications; (ii) Requires a broadband connection from the user's location; (iii) Requires internet protocol-compatible customer premises equipment (CPE); and (iv) Permits users generally to receive calls that originate on the public switched telephone network and to terminate calls to the public switched telephone network. (2) Notwithstanding the foregoing, solely for purposes of compliance with the Commission's 911 obligations, an interconnected VoIP service includes a service that fulfills each of paragraphs (1)(i) through (iii) of this definition and permits users generally to terminate calls to the public switched telephone network. Internet-based TRS (iTRS). Internet Protocol Captioned Telephone Service (IP CTS). Internet Protocol Relay Service (IP Relay). Location-capable handsets. Location-based routing. MLTS notification. (1) The fact that a 911 call has been made; (2) A valid callback number; and (3) The information about the caller's location that the MLTS conveys to the public safety answering point (PSAP) with the call to 911; provided, however, that the notification does not have to include a callback number or location information if it is technically infeasible to provide this information. Mobile Earth Station. Mobile-Satellite Service (MSS). (i) Between mobile earth stations and one or more space stations, or between space stations used by this service; or (ii) Between mobile earth stations, by means of one or more space stations. (2) This service may also include feeder links necessary for its operation. (RR) Mobile service. (1) Both one-way and two-way radio communications services; (2) A mobile service which provides a regularly interacting group of base, mobile, portable, and associated control and relay stations (whether licensed on an individual, cooperative, or multiple basis) for private one-way or two-way land mobile radio communications by eligible users over designated areas of operation; and (3) Any service for which a license is required in a personal communications service under part 24 of this chapter. Network-based location technology. Multi-line telephone system or MLTS. Non-English language relay service. On-premises. e.g. Person engaged in the business of installing an MLTS. Person engaged in the business of managing an MLTS. Person engaged in the business of manufacturing, importing, selling, or leasing an MLTS. Person engaged in the business of operating an MLTS. Pre-configured. Private mobile radio service. commercial mobile radio service commercial mobile radio service (1) Not-for-profit land mobile radio and paging services that serve the licensee's internal communications needs as defined in part 90 of this chapter. Shared-use, cost-sharing, or cooperative arrangements, multiple licensed systems that use third party managers or users combining resources to meet compatible needs for specialized internal communications facilities in compliance with the safeguards of § 90.179 of this chapter are presumptively private mobile radio services; (2) Mobile radio service offered to restricted classes of eligible users. This includes entities eligible in the Public Safety Radio Pool and Radiolocation service. (3) 220-222 MHz land mobile service and Automatic Vehicle Monitoring systems (part 90 of this chapter) that do not offer interconnected service or that are not-for-profit; and (4) Personal Radio Services under part 95 of this chapter (General Mobile Services, Radio Control Radio Services, and Citizens Band Radio Services); Maritime Service Stations (excluding Public Coast stations) (part 80 of this chapter); and Aviation Service Stations (part 87 of this chapter). Pseudo Automatic Number Identification (Pseudo-ANI). Public safety answering point or PSAP. Public Switched Network. Real-Time Text (RTT). e.g., Registered internet-based TRS user. Registered Location. Space station. Speech-to-speech relay service (STS). Statewide default answering point. Station. Telecommunications relay services (TRS). Text telephone (TTY). Video relay service (VRS). Wireline E911 Network. (1) Is interconnected with but largely separate from the public switched telephone network; (2) Includes a selective router; and (3) Is used to route emergency calls and related information to PSAPs, designated statewide default answering points, appropriate local emergency authorities or other emergency answering points. [84 FR 66760, Dec. 5, 2019, as amended at 89 FR 18523, Mar. 13, 2024] Subpart B—Telecommunications Carriers § 9.4 Obligation to transmit 911 calls. All telecommunications carriers shall transmit all 911 calls to a PSAP, to a designated statewide default answering point, or to an appropriate local emergency authority as set forth in § 9.5. § 9.5 Transition to 911 as the universal emergency telephone number. As of December 11, 2001, except where 911 is already established as the exclusive emergency number to reach a PSAP within a given jurisdiction, telecommunications carriers shall comply with the following transition periods: (a) Where a PSAP has been designated, telecommunications carriers shall complete all translation and routing necessary to deliver 911 calls to a PSAP no later than September 11, 2002. (b) Where no PSAP has been designated, telecommunications carriers shall complete all translation and routing necessary to deliver 911 calls to the statewide default answering point no later than September 11, 2002. (c) Where neither a PSAP nor a statewide default answering point has been designated, telecommunications carriers shall complete the translation and routing necessary to deliver 911 calls to an appropriate local emergency authority, within nine months of a request by the State or locality. (d) Where no PSAP nor statewide default answering point has been designated, and no appropriate local emergency authority has been selected by an authorized state or local entity, telecommunications carriers shall identify an appropriate local emergency authority, based on the exercise of reasonable judgment, and complete all translation and routing necessary to deliver 911 calls to such appropriate local emergency authority no later than September 11, 2002. (e) Once a PSAP is designated for an area where none had existed as of December 11, 2001, telecommunications carriers shall complete the translation and routing necessary to deliver 911 calls to that PSAP within nine months of that designation. § 9.6 Obligation for providing a permissive dialing period. Upon completion of translation and routing of 911 calls to a PSAP, a statewide default answering point, to an appropriate local emergency authority, or, where no PSAP nor statewide default answering point has been designated and no appropriate local emergency authority has been selected by an authorized state or local entity, to an appropriate local emergency authority, identified by a telecommunications carrier based on the exercise of reasonable judgment, the telecommunications carrier shall provide permissive dialing between 911 and any other seven-or ten-digit emergency number or an abbreviated dialing code other than 911 that the public has previously used to reach emergency service providers until the appropriate State or local jurisdiction determines to phase out the use of such seven-or ten-digit number entirely and use 911 exclusively. § 9.7 Obligation for providing an intercept message. Upon termination of permissive dialing, as provided under § 9.6, telecommunications carriers shall provide a standard intercept message announcement that interrupts calls placed to the emergency service provider using either a seven-or ten-digit emergency number or an abbreviated dialing code other than 911 and informs the caller of the dialing code change. § 9.8 Obligation of fixed telephony providers to convey dispatchable location. (a) Providers of fixed telephony services shall provide automated dispatchable location with 911 calls beginning January 6, 2021. (b) [Reserved] [84 FR 66760, Dec. 5, 2019, as amended at 85 FR 78022, Dec. 3, 2020] Subpart C—Commercial Mobile Radio Service § 9.9 Definitions. Interconnection Interconnected. Interconnected service. (i) That is interconnected with the public switched network, or interconnected with the public switched network through an interconnected service provider, that gives subscribers the capability to communicate to or receive communication from all other users on the public switched network; or (ii) For which a request for such interconnection is pending pursuant to section 332(c)(1)(B) of the Communications Act, 47 U.S.C. 332(c)(1)(B). (2) A mobile service offers interconnected service even if the service allows subscribers to access the public switched network only during specified hours of the day, or if the service provides general access to points on the public switched network but also restricts access in certain limited ways. Interconnected service does not include any interface between a licensee's facilities and the public switched network exclusively for a licensee's internal control purposes. § 9.10 911 Service. (a) Scope of section. (1) Offer real-time, two way switched voice service that is interconnected with the public switched network; and (2) Use an in-network switching facility that enables the provider to reuse frequencies and accomplish seamless hand-offs of subscriber calls. These requirements are applicable to entities that offer voice service to consumers by purchasing airtime or capacity at wholesale rates from CMRS licensees. (b) Basic 911 service. (c) Access to 911 services. e.g., (d) Phase I enhanced 911 services. (2) When the directory number of the handset used to originate a 911 call is not available to the serving carrier, such carrier's obligations under the paragraph (d)(1) of this section extend only to delivering 911 calls and available call party information, including that prescribed in paragraph (l) of this section, to the designated Public Safety Answering Point. Note to paragraph (d): With respect to 911 calls accessing their systems through the use of TTYs, licensees subject to this section must comply with the requirements in paragraphs (d)(1) and (2) of this section, as to calls made using a digital wireless system, as of October 1, 1998. (e) Phase II enhanced 911 service. i.e., see (f) Phase-in for network-based location technologies. (g) Phase-in for handset-based location technologies. (1) Without respect to any PSAP request for deployment of Phase II 911 enhanced service, the licensee shall: (i) Begin selling and activating location-capable handsets no later than October 1, 2001; (ii) Ensure that at least 25 percent of all new handsets activated are location-capable no later than December 31, 2001; (iii) Ensure that at least 50 percent of all new handsets activated are location-capable no later than June 30, 2002; and (iv) Ensure that 100 percent of all new digital handsets activated are location-capable no later than December 31, 2002, and thereafter. (v) By December 31, 2005, achieve 95 percent penetration of location-capable handsets among its subscribers. (vi) Licensees that meet the enhanced 911 compliance obligations through GPS-enabled handsets and have commercial agreements with resellers will not be required to include the resellers' handset counts in their compliance percentages. (2) Once a PSAP request is received, the licensee shall, in the area served by the PSAP, within six months or by October 1, 2001, whichever is later: (i) Install any hardware and/or software in the CMRS network and/or other fixed infrastructure, as needed, to enable the provision of Phase II enhanced 911 service; and (ii) Begin delivering Phase II enhanced 911 service to the PSAP. (3) For all 911 calls from portable or mobile phones that do not contain the hardware and/or software needed to enable the licensee to provide Phase II enhanced 911 service, the licensee shall, after a PSAP request is received, support, in the area served by the PSAP, Phase I location for 911 calls or other available best practice method of providing the location of the portable or mobile phone to the PSAP. (4) Licensees employing handset-based location technologies shall ensure that location-capable portable or mobile phones shall conform to industry interoperability standards designed to enable the location of such phones by multiple licensees. (h) Phase II accuracy. (1) Network-based technologies: (i) 100 meters for 67 percent of calls, consistent with the following benchmarks: (A) One year from January 18, 2011, carriers shall comply with this standard in 60 percent of counties or PSAP service areas. These counties or PSAP service areas must cover at least 70 percent of the population covered by the carrier across its entire network. Compliance will be measured on a per-county or per-PSAP basis using, at the carrier's election, either: ( 1 ( 2 (B) Three years from January 18, 2011, carriers shall comply with this standard in 70 percent of counties or PSAP service areas. These counties or PSAP service areas must cover at least 80 percent of the population covered by the carrier across its entire network. Compliance will be measured on a per-county or per-PSAP basis using, at the carrier's election, either: ( 1 ( 2 (C) Five years from January 18, 2011, carriers shall comply with this standard in 100% of counties or PSAP service areas covered by the carrier. Compliance will be measured on a per-county or per-PSAP basis, using, at the carrier's election, either: ( 1 ( 2 ( 3 (ii) 300 meters for 90 percent of calls, consistent with the following benchmarks: (A) Three years from January 18, 2011, carriers shall comply with this standard in 60 percent of counties or PSAP service areas. These counties or PSAP service areas must cover at least 70 percent of the population covered by the carrier across its entire network. Compliance will be measured on a per-county or per-PSAP basis using, at the carrier's election, either: ( 1 ( 2 (B) Five years from January 18, 2011, carriers shall comply in 70 percent of counties or PSAP service areas. These counties or PSAP service areas must cover at least 80 percent of the population covered by the carrier across its entire network. Compliance will be measured on a per-county or per-PSAP basis using, at the carrier's election, either: ( 1 ( 2 (C) Eight years from January 18, 2011, carriers shall comply in 85 percent of counties or PSAP service areas. Compliance will be measured on a per-county or per-PSAP basis using, at the carrier's election, either: ( 1 ( 2 ( 3 (iii) County-level or PSAP-level location accuracy standards for network-based technologies will be applicable to those counties or PSAP service areas, on an individual basis, in which a network-based carrier has deployed Phase II in at least one cell site located within a county's or PSAP service area's boundary. Compliance with the requirements of paragraphs (h)(1)(i) and (ii) of this section shall be measured and reported independently. (iv) Accuracy data from both network-based solutions and handset-based solutions may be blended to measure compliance with the accuracy requirements of paragraphs (h)(1)(i)(A) through (C) and paragraphs (h)(1)(ii)(A) through (C) of this section. Such blending shall be based on weighting accuracy data in the ratio of assisted GPS (“A-GPS”) handsets to non-A-GPS handsets in the carrier's subscriber base. The weighting ratio shall be applied to the accuracy data from each solution and measured against the network-based accuracy requirements of paragraph (h)(1) of this section. (v) A carrier may rely solely on handset-based accuracy data in any county or PSAP service area if at least 85 percent of its subscribers, network-wide, use A-GPS handsets, or if it offers A-GPS handsets to subscribers in that county or PSAP service area at no cost to the subscriber. (vi) A carrier may exclude from compliance particular counties, or portions of counties, where triangulation is not technically possible, such as locations where at least three cell sites are not sufficiently visible to a handset. Carriers must file a list of the specific counties or portions of counties where they are using this exclusion within 90 days following approval from the Office of Management and Budget for the related information collection. This list must be submitted electronically into PS Docket No. 07-114, and copies must be sent to the National Emergency Number Association, the Association of Public-Safety Communications Officials-International, and the National Association of State 9-1-1 Administrators. Further, carriers must submit in the same manner any changes to their exclusion lists within thirty days of discovering such changes. This exclusion has sunset as of January 18, 2019. (2) Handset-based technologies: (i) Two years from January 18, 2011, 50 meters for 67 percent of calls, and 150 meters for 80 percent of calls, on a per-county or per-PSAP basis. However, a carrier may exclude up to 15 percent of counties or PSAP service areas from the 150-meter requirement based upon heavy forestation that limits handset-based technology accuracy in those counties or PSAP service areas. (ii) Eight years from January 18, 2011, 50 meters for 67 percent of calls, and 150 meters for 90 percent of calls, on a per-county or per-PSAP basis. However, a carrier may exclude up to 15 percent of counties or PSAP service areas from the 150-meter requirement based upon heavy forestation that limits handset-based technology accuracy in those counties or PSAP service areas. (iii) Carriers must file a list of the specific counties or PSAP service areas where they are using the exclusion for heavy forestation within 90 days following (approval from the Office of Management and Budget for the related information collection). This list must be submitted electronically into PS Docket No. 07-114, and copies must be sent to the National Emergency Number Association, the Association of Public-Safety Communications Officials-International, and the National Association of State 9-1-1 Administrators. Further, carriers must submit in the same manner any changes to their exclusion lists within thirty days of discovering such changes. (iv) Providers of new CMRS networks that meet the definition of covered CMRS providers under paragraph (a) of this section must comply with the requirements of paragraphs (h)(2)(i) through (iii) of this section. For this purpose, a “new CMRS network” is a CMRS network that is newly deployed subsequent to the effective date of the Third Report and Order in PS Docket No. 07-114 and that is not an expansion or upgrade of an existing CMRS network. (3) Latency (Time to First Fix): For purposes of measuring compliance with the location accuracy standards of this paragraph, a call will be deemed to satisfy the standard only if it provides the specified degree of location accuracy within a maximum latency period of 30 seconds, as measured from the time the user initiates the 911 call to the time the location fix appears at the location information center: Provided, however, that the CMRS provider may elect not to include for purposes of measuring compliance therewith any calls lasting less than 30 seconds. (i) Indoor location accuracy for 911 and testing requirements Definitions. (i) Dispatchable location. (ii) Media Access Control (MAC) Address. (iii) National Emergency Address Database (NEAD). (iv) Nationwide CMRS provider. (v) Non-nationwide CMRS provider. (vi) Test cities. (2) Indoor location accuracy standards. (i) Horizontal location. ( 1 ( 2 ( 3 ( 4 (B) Non-nationwide CMRS providers shall provide; dispatchable location or; x/y location within 50 meters, for the following percentages of wireless 911 calls within the following timeframes, measured from the effective date of the adoption of this rule: ( 1 ( 2 ( 3 ( 4 (ii) Vertical location. (A) Within 3 years: All CMRS providers shall make uncompensated barometric data available to PSAPs with respect to any 911 call placed from any handset that has the capability to deliver barometric sensor information. (B) Within 3 years: Nationwide CMRS providers shall develop one or more z-axis accuracy metrics validated by an independently administered and transparent test bed process as described in paragraph (i)(3)(i) of this section, and shall submit the proposed metric or metrics, supported by a report of the results of such development and testing, to the Commission for approval. (C) By April 3, 2021: In each of the top 25 cellular market areas (CMAs), nationwide CMRS providers shall deploy either dispatchable location or z-axis technology. (D) By April 3, 2023: In each of the top 50 CMAs, nationwide CMRS providers shall deploy either dispatchable location or z-axis technology. (E) By April 3, 2025: Nationwide CMRS providers shall deploy on a nationwide basis either dispatchable location or z-axis technology. (F) Non-nationwide CMRS providers that serve any of the top 25 or 50 CMAs will have an additional year to meet each of the benchmarks in paragraphs (i)(2)(ii)(C) and (D) of this section. All non-nationwide providers will have an additional year to meet the benchmark in paragraph (i)(2)(ii)(E) of this section by deploying either dispatchable location or z-axis technology throughout their network footprint. (G) By January 6, 2022: All CMRS providers shall provide dispatchable location with wireless E911 calls if it is technically feasible for them to do so. (H) CMRS providers that deploy z-axis technology must do so consistent with the following z-axis accuracy metric: Within 3 meters above or below (plus or minus 3 meters) the handset for 80% of wireless E911 calls made from the z-axis capable device. CMRS providers must deliver z-axis information in Height Above Ellipsoid. Where available to the CMRS provider, floor level information must be provided in addition to z-axis location information. (I) CMRS providers that deploy z-axis technology must do so according to the following options: ( 1 ( 2 (J) CMRS providers that deploy z-axis technology must comply with the following: ( 1 ( 2 ( 3 ( 4 (K) CMRS providers must validate dispatchable location technologies intended for indoor location in accordance with the provisions of paragraph (i)(3)(i) of this section. (L) In each CMA where dispatchable location is used, nationwide CMRS providers must ensure that dispatchable location is supported by a sufficient number of total dispatchable location reference points to equal 25 percent of the CMA population. (M) A z-axis capable device is one that can measure and report vertical location without a hardware upgrade. For z-axis location solutions that rely on barometric pressure sensor information, only devices that have such sensors installed shall be considered z-axis capable. In the case of location solutions that do not require barometric pressure sensor information, both devices with and without barometric sensors shall be considered z-axis capable, provided that they are software-upgradable. (iii) Compliance. (A) All CMRS providers must certify that the indoor location technology (or technologies) used in their networks are deployed consistently with the manner in which they have been tested in the test bed. A CMRS provider must update certification whenever it introduces a new technology into its network or otherwise modifies its network, such that previous performance in the test bed would no longer be consistent with the technology's modified deployment. (B) CMRS providers that provide quarterly reports of live call data in one or more of the six test cities specified in paragraph (i)(1)(vi) of this section must certify that their deployment of location technologies throughout their coverage area is consistent with their deployment of the same technologies in the areas that are used for live call data reporting. (C) Non-nationwide CMRS providers that do not provide service or report quarterly live call data in any of the six test cities specified in paragraph (i)(1)(vi) of this section must certify that they have verified based on their own live call data that they are in compliance with the requirements of paragraphs (i)(2)(i)(B) and (i)(2)(ii) of this section. (iv) Enforcement. (3) Indoor location accuracy testing and live call data reporting Indoor location accuracy test bed. (A) Include testing in representative indoor environments, including dense urban, urban, suburban and rural morphologies; (B) Test for performance attributes including location accuracy (ground truth as measured in the test bed), latency (Time to First Fix), and reliability (yield); and (C) Each test call (or equivalent) shall be independent from prior calls and accuracy will be based on the first location delivered after the call is initiated. (D) In complying with paragraph (i)(3)(i)(B) of this section, CMRS providers shall measure yield separately for each individual indoor location morphology (dense urban, urban, suburban, and rural) in the test bed, and based upon the specific type of location technology that the provider intends to deploy in real-world areas represented by that particular morphology. CMRS providers must base the yield percentage based on the number of test calls that deliver a location in compliance with any applicable indoor location accuracy requirements, compared to the total number of calls that successfully connect to the testing network. CMRS providers may exclude test calls that are dropped or otherwise disconnected in 10 seconds or less from calculation of the yield percentage (both the denominator and numerator). (ii) Collection and reporting of aggregate live 911 call location data. (A) CMRS providers subject to this section shall identify and collect information regarding the location technology or technologies used for each 911 call in the reporting area during the calling period. (B) CMRS providers subject to this section shall report Test City call location data on a quarterly basis to the Commission, the National Emergency Number Association, the Association of Public Safety Communications Officials, and the National Association of State 911 Administrators, with the first report due 18 months from the effective date of rules adopted in this proceeding. (C) CMRS providers subject to this section shall also provide quarterly live call data on a more granular basis that allows evaluation of the performance of individual location technologies within different morphologies (e.g., dense urban, urban, suburban, rural). To the extent available, live call data for all CMRS providers shall delineate based on a per technology basis accumulated and so identified for: ( 1 ( 2 ( 3 (D) Non-nationwide CMRS providers that operate in a single Test City need only report live 911 call data from that city or portion thereof that they cover. Non-nationwide CMRS providers that operate in more than one Test City must report live 911 call data only in half of the regions (as selected by the provider). In the event a non-nationwide CMRS provider begins coverage in a Test City it previously did not serve, it must update its certification pursuant to paragraph (i)(2)(iii)(C) of this section to reflect this change in its network and begin reporting data from the appropriate areas. All non-nationwide CMRS providers must report their Test City live call data every 6 months, beginning 18 months from the effective date of rules adopted in this proceeding. (E) Non-nationwide CMRS providers that do not provide coverage in any of the Test Cities can satisfy the requirement of this paragraph (i)(3)(ii) by collecting and reporting data based on the largest county within its footprint. In addition, where a non-nationwide CMRS provider serves more than one of the ATIS ESIF morphologies, it must include a sufficient number of representative counties to cover each morphology. (iii) Data retention. (4) Submission of plans and reports. (i) Initial implementation plan. (ii) Progress reports. (iii) NEAD privacy and security plan. (iv) Dispatchable location use certification. (v) Z-axis use certification. (j) Confidence and uncertainty data. (i) The caller's location with a uniform confidence level of 90 percent, and; (ii) The radius in meters from the reported position at that same confidence level. All entities responsible for transporting confidence and uncertainty between CMRS providers and PSAPs, including LECs, CLECs, owners of E911 networks, and emergency service providers, must enable the transmission of confidence and uncertainty data provided by CMRS providers to the requesting PSAP. (2) Upon meeting the 3-year timeframe pursuant to paragraph (i)(2)(i) of this section, CMRS providers shall provide with wireless 911 calls that have a dispatchable location the C/U data for the x- and y-axis (latitude, longitude) required under paragraph (j)(1) of this section. (3) Upon meeting the 6-year timeframe pursuant to paragraph (i)(2)(i) of this section, CMRS providers shall provide with wireless 911 calls that have a dispatchable location the C/U data for the x- and y-axis (latitude, longitude) required under paragraph (j)(1) of this section. (4) Upon meeting the timeframes pursuant to paragraph (i)(2)(ii) of this section, CMRS providers shall provide with wireless 911 calls that have a dispatchable location the confidence and uncertainty data for z-axis (vertical) information required under paragraph (j)(1) of this section. Where available to the CMRS provider, CMRS providers shall provide with wireless 911 calls that have floor level information the confidence and uncertainty data for z-axis (vertical) information required under paragraph (j)(1) of this section. (k) Provision of live 911 call data for PSAPs. (l) Reports on Phase II plans. (m) Conditions for enhanced 911 services Generally. (2) Commencement of six-month period. (A) Ordered the necessary equipment and has commitments from suppliers to have it installed and operational within such six-month period; and (B) Made a timely request to the appropriate local exchange carrier for the necessary trunking, upgrades, and other facilities. (ii) For purposes of commencing the six-month period for carrier implementation specified in paragraphs (f) and (g) of this section, a PSAP that is Phase I-capable using a Non-Call Path Associated Signaling (NCAS) technology will be deemed capable of receiving and using the data elements associated with Phase II service if it can demonstrate that it has made a timely request to the appropriate local exchange carrier for the ALI database upgrade necessary to receive the Phase II information. (3) Tolling of six-month period. (4) Carrier certification regarding PSAP readiness issues. (i) As a prerequisite to filing such certification, no later than 21 days prior to such filing, the wireless carrier must notify the affected PSAP, in writing, of its intent to file such certification. Any response that the carrier receives from the PSAP must be included with the carrier's certification filing. (ii) The certification process shall be subject to the procedural requirements set forth in §§ 1.45 and 1.47 of this chapter. (iii) The certification must be in the form of an affidavit signed by a director or officer of the carrier, documenting: (A) The basis for the carrier's determination that the PSAP will not be ready; (B) Each of the specific steps the carrier has taken to provide the E911 service requested; (C) The reasons why further implementation efforts cannot be made until the PSAP becomes capable of receiving and using the data elements associated with the E911 service requested; and (D) The specific steps that remain to be completed by the wireless carrier and, to the extent known, the PSAP or other parties before the carrier can provide the E911 service requested. (iv) All affidavits must be correct. The carrier must ensure that its affidavit is correct, and the certifying director or officer has the duty to personally determine that the affidavit is correct. (v) A carrier may not engage in a practice of filing inadequate or incomplete certifications for the purpose of delaying its responsibilities. (vi) To be eligible to make a certification, the wireless carrier must have completed all necessary steps toward E911 implementation that are not dependent on PSAP readiness. (vii) A copy of the certification must be served on the PSAP in accordance with § 1.47 of this chapter. The PSAP may challenge in writing the accuracy of the carrier's certification and shall serve a copy of such challenge on the carrier. See §§ 1.45 and 1.47 and 1.720 through 1.740 of this chapter. (viii) If a wireless carrier's certification is facially inadequate, the six-month implementation period specified in paragraphs (d), (f), and (g) of this section will not be suspended as provided for in paragraph (m)(4) of this section. (ix) If a wireless carrier's certification is inaccurate, the wireless carrier will be liable for noncompliance as if the certification had not been filed. (x) A carrier that files a certification under this paragraph (m)(4) shall have 90 days from receipt of the PSAP's written notice that it is capable of receiving and using the data elements associated with the service requested to provide such service in accordance with the requirements of paragraphs (d) through (h) of this section. (5) Modification of deadlines by agreement. (n) [Reserved] (o) Non-service-initialized handsets. (i) Program each handset with 911 plus the decimal representation of the seven least significant digits of the Electronic Serial Number, International Mobile Equipment Identifier, or any other identifier unique to that handset; (ii) Affix to each handset a label which is designed to withstand the length of service expected for a non-service-initialized phone, and which notifies the user that the handset can only be used to dial 911, that the 911 operator will not be able to call the user back, and that the user should convey the exact location of the emergency as soon as possible; and (iii) Institute a public education program to provide the users of such handsets with information regarding the limitations of non-service-initialized handsets. (2) Manufacturers of 911-only handsets that are manufactured on or after May 3, 2004, are required to: (i) Program each handset with 911 plus the decimal representation of the seven least significant digits of the Electronic Serial Number, International Mobile Equipment Identifier, or any other identifier unique to that handset; (ii) Affix to each handset a label which is designed to withstand the length of service expected for a non-service-initialized phone, and which notifies the user that the handset can only be used to dial 911, that the 911 operator will not be able to call the user back, and that the user should convey the exact location of the emergency as soon as possible; and (iii) Institute a public education program to provide the users of such handsets with information regarding the limitations of 911-only handsets. (3) The following definitions apply for purposes of this paragraph. (i) Non-service-initialized handset. (ii) 911-only handset. (p) Reseller obligation. (2) Resellers have an independent obligation to ensure that all handsets or other devices offered to their customers for voice communications and sold after December 31, 2006 are capable of transmitting enhanced 911 information to the appropriate PSAP, in accordance with the accuracy requirements of § 9.10(i). (q) Text-to-911 requirements Covered text provider. (2) Automatic bounce-back message. (3) Provision of automatic bounce-back messages. (i) A consumer attempts to send a text message to a Public Safety Answering Point (PSAP) by means of the three-digit short code “911”; and (ii) The covered text provider cannot deliver the text because the consumer is located in an area where: (A) Text-to-911 service is unavailable; or (B) The covered text provider does not support text-to-911 service at the time. (4) Automatic bounce-back message exceptions. (A) Transmission of the text message is not controlled by the provider; (B) A consumer is attempting to text 911, through a text messaging application that requires CMRS service, from a non-service initialized handset; (C) When the text-to-911 message cannot be delivered to a PSAP due to failure in the PSAP network that has not been reported to the provider; or (D) A consumer is attempting to text 911 through a device that is incapable of sending texts via three digit short codes, provided the software for the device cannot be upgraded over the air to allow text-to-911. (ii) The provider of a preinstalled or downloadable interconnected text application is considered to have “control” over transmission of text messages for purposes of paragraph (q)(4)(i)(A) of this section. However, if a user or a third party modifies or manipulates the application after it is installed or downloaded so that it no longer supports bounce-back messaging, the application provider will be presumed not to have control. (5) Automatic bounce-back message minimum requirements. (6) Temporary suspension of text-to-911 service. (7) Roaming. (8) Software application provider. (9) 911 text message. (10) Delivery of 911 text messages. (ii) Covered text providers must begin routing all 911 text messages to a PSAP by June 30, 2015, or within six months of the PSAP's valid request for text-to-911 service, whichever is later, unless an alternate timeframe is agreed to by both the PSAP and the covered text provider. The covered text provider must notify the Commission of the dates and terms of the alternate timeframe within 30 days of the parties' agreement. (iii) Valid Request means that: (A) The requesting PSAP is, and certifies that it is, technically ready to receive 911 text messages in the format requested; (B) The appropriate local or state 911 service governing authority has specifically authorized the PSAP to accept and, by extension, the covered text provider to provide, text-to-911 service; and (C) The requesting PSAP has provided notification to the covered text provider that it meets the foregoing requirements. Registration by the PSAP in a database made available by the Commission in accordance with requirements established in connection therewith, or any other written notification reasonably acceptable to the covered text provider, shall constitute sufficient notification for purposes of this paragraph. (iv) The requirements set forth in paragraphs (q)(10)(i) through (iii) of this section do not apply to in-flight text messaging providers, MSS providers, or IP Relay service providers, or to 911 text messages that originate from Wi-Fi only locations or that are transmitted from devices that cannot access the CMRS network. (v) No later than January 6, 2022, covered text providers must provide the following location information with all 911 text messages routed to a PSAP: Automated dispatchable location, if technically feasible; otherwise, either end-user manual provision of location information, or enhanced location information, which may be coordinate-based, consisting of the best available location that can be obtained from any available technology or combination of technologies at reasonable cost. (11) Access to SMS networks for 911 text messages. (r) Contraband Interdiction System (CIS) requirement. see (s) Location-based routing requirements Wireless 911 voice calls. (ii) By May 13, 2026, non-nationwide CMRS providers must deploy a technology that supports location-based routing for wireless 911 voice calls on their internet Protocol-based networks (4G LTE, 5G, and subsequent generations of internet Protocol-based networks). At that time, non-nationwide CMRS providers must route all wireless 911 voice calls originating on their internet Protocol-based networks pursuant to the requirements of paragraph (s)(3) of this section. (2) Real-time text communications to 911. (3) Timeliness and accuracy threshold. (A) The location information reports the horizontal location uncertainty level of the device within a radius of 165 meters at a confidence level of at least 90%; and (B) The location information is available to the CMRS provider network at the time of routing the wireless 911 voice call or real-time text communication to 911. (ii) When the location information does not meet either one or both of the requirements in paragraphs (s)(3)(i)(A) and (B) of this section, CMRS providers must route the wireless 911 voice call or real-time text communication to 911 based on the best available location information, which may include but is not limited to device-based location information that does not meet the requirements in paragraphs (s)(3)(i)(A) and (B), the centroid of the area served by the cell sector that first picks up the call, or other location information. (4) Certification and reporting. (i) CMRS providers must: (A) Certify that they are in compliance with the requirements specified in paragraphs (s)(1)(i) and (ii) and (s)(2) of this section applicable to them; (B) Identify specific network architecture, systems, and procedures used to comply with paragraphs (s)(1)(i) and (ii) and (s)(2) of this section, including the extent to which the CMRS provider validates location information for routing purposes and the validation practices used in connection with this information; and (C) Certify that neither they nor any third party they rely on to obtain location information or associated data used for compliance with paragraph (s)(1)(i) or (ii) or (s)(2) of this section will use such location information or associated data for any non-911 purpose, except with prior express consent or as otherwise required by law. The certification must state that the CMRS provider and any third parties it relies on to obtain location information or associated data used for compliance with paragraph (s)(1)(i) or (ii) or (s)(2) have implemented measures sufficient to safeguard the privacy and security of such location information or associated data. (ii) CMRS providers also must: (A) Collect and report aggregate data on the routing technologies used for all live wireless 911 voice calls in the locations specified for live 911 call location data in paragraph (i)(3)(ii) of this section for a thirty-day period which begins on the compliance date(s) specified in paragraphs (s)(1)(i) and (ii) of this section. CMRS providers must retain live wireless 911 voice call data gathered pursuant to this section for a period of 2 years. CMRS providers must collect and report the following data, expressed as both a number and percentage of the total number of live wireless 911 voice calls for which data is collected pursuant to this section: ( 1 ( 2 ( 3 (5) Modification of deadlines by agreement. (t) Interim 911 requirements for supplemental coverage from space Supplemental coverage from space. supplemental coverage from space (SCS) SCS 911 calls SCS 911 text message (2) Call Transmission requirements. (i) Use information regarding the location of a device, including but not limited to device-based location information, to route SCS 911 voice calls and SCS 911 text messages to an appropriate PSAP and transmit the phone number of the device used to send the SCS 911 voice call or SCS 911 text message and available location information to an appropriate PSAP; or (ii) Use an emergency call center, at which emergency call center personnel must determine the emergency caller's phone number and location and then transfer or otherwise direct the 911 caller to an appropriate PSAP. (3) Reporting. (i) The name and address of the CMRS provider, the address of that CMRS provider's emergency call center, and the contact information of the emergency call center; (ii) The aggregate number of SCS 911 voice calls and SCS 911 text messages received by the network of the CMRS provider that provides SCS service to its end-user subscribers during each month during the relevant reporting period; (iii) The aggregate number of SCS 911 voice calls and SCS 911 text messages received by the emergency call center each month during the relevant reporting period; (iv) The aggregate number of SCS 911 voice calls and SCS 911 text messages received by the emergency call center each month during the relevant reporting period that required forwarding to a PSAP and how many did not require forwarding to a PSAP; (v) The aggregate number of SCS 911 voice calls that were routed using location information that met the timeliness and accuracy thresholds defined in paragraphs (s)(3)(i)(A) and (B) of this section; (vi) The aggregate number of SCS 911 voice calls and SCS 911 text messages that were routed using location information that did not meet the timeliness and accuracy thresholds defined in paragraphs (s)(3)(i)(A) and (B) of this section; and (vii) An explanation of how the SCS deployment, including network architecture, systems, and procedures, will support routing SCS 911 voice calls and SCS 911 text messages to the geographically appropriate PSAP with sufficient location information in compliance with paragraph (t)(2) of this section. (4) Certification. (5) Subscriber notification. [84 FR 66760, Dec. 5, 2019, as amended at 85 FR 2675, Jan. 16, 2020; 85 FR 53246, Aug. 28, 2020; 85 FR 70501, Nov. 5, 2020; 85 FR 78022, Dec. 3, 2020; 86 FR 19584, Apr. 14, 2021; 89 FR 18523, Mar. 13, 2024;

89 FR 34165, Apr. 30, 2024; 89 FR 78825, Sept. 26, 2024; 91 FR 1403, Jan. 14, 2026] Subpart D—Interconnected Voice over Internet Protocol Services § 9.11 E911 Service. (a) [Reserved] (b) On or after January 6, 2021, for fixed services, and on or after January 6, 2022, for non-fixed services Scope. (2) E911 Service (ii) Interconnected VoIP service providers must transmit the following to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's dispatchable location and that has been designated for telecommunications carriers pursuant to § 9.4: (A) All 911 calls, provided that “all 911 calls” is defined as “any voice communication initiated by an interconnected VoIP user dialing 911;” (B) ANI; and (C) The location information described in paragraph (b)(4) of this section. (iii) All 911 calls must be routed through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network, provided that nothing in this subparagraph shall preclude routing the call first to a national emergency call center to ascertain the caller's location in the event that the interconnected VoIP service provider is unable to obtain or confirm the caller's location information; and (iv) The location information described in paragraph (b)(4) of this section must be available to the appropriate PSAP, designated statewide default answering point, or appropriate local emergency authority from or through the appropriate automatic location information (ALI) database. (3) Service level obligation. (4) Location requirements. (i) Fixed interconnected VoIP services. Providers of fixed interconnected VoIP services must provide automated dispatchable location with each 911 call. (ii) Non-fixed interconnected VoIP services. For non-fixed interconnected VoIP service (service that is capable of being used from more than one location), interconnected VoIP service providers must provide location information in accordance with paragraph (b)(4)(ii)(A) of this section, if technically feasible. Otherwise, interconnected VoIP service providers must either provide location information in accordance with paragraph (b)(4)(ii)(B) or (C), or meet paragraph (b)(4)(ii)(D) of this section. (A) Provide automated dispatchable location, if technically feasible. (B) Provide Registered Location information that meets the following requirements: ( 1 ( 2 ( 3 ( i ( ii (C) Provide Alternative Location Information as defined in § 9.3. (D) Route the caller to a national emergency call center. (5) Customer notification. (ii) Each interconnected VoIP service provider shall obtain and keep a record of affirmative acknowledgement by every subscriber, both new and existing, of having received and understood the advisory described in paragraph (b)(5)(i) of this section; and (iii) Each interconnected VoIP service provider shall either: (A) Distribute to its existing subscribers, and to each new subscriber prior to the initiation of that subscriber's service, warning stickers or labels warning subscribers if E911 service may be limited or not available, and instructing the subscriber to place them on or near the equipment used in conjunction with the interconnected VoIP service; or (B) Notify existing subscribers, and each new subscriber prior to the initiation of that subscriber's service, by other conspicuous means if E911 service may be limited or not available. [84 FR 66760, Dec. 5, 2019, as amended at 85 FR 78022, Dec. 3, 2020; 91 FR 1403, Jan. 14, 2026] § 9.12 Access to 911 and E911 service capabilities. (a) Access. (1) If the owner or controller makes the requested capability available to a CMRS provider, the owner or controller must make that capability available to the interconnected VoIP provider. An owner or controller makes a capability available to a CMRS provider if the owner or controller offers that capability to any CMRS provider. (2) If the owner or controller does not make the requested capability available to a CMRS provider within the meaning of paragraph (a)(1) of this section, the owner or controller must make that capability available to a requesting interconnected VoIP provider only if that capability is necessary to enable the interconnected VoIP provider to provide 911 or E911 service in compliance with the Commission's rules. (b) Rates, terms, and conditions. (1) The same as the rates, terms, and conditions that are made available to CMRS providers, or (2) In the event such capability is not made available to CMRS providers, the same rates, terms, and conditions that are made available to any telecommunications carrier or other entity for the provision of 911 or E911 service. (c) Permissible use. Subpart E—Telecommunications Relay Services for Persons with Disabilities § 9.13 Jurisdiction. Any violation of this subpart E by any common carrier engaged in intrastate communication shall be subject to the same remedies, penalties, and procedures as are applicable to a violation of the Act by a common carrier engaged in interstate communication. For purposes of this subpart, all regulations and requirements applicable to common carriers shall also be applicable to providers of interconnected VoIP service as defined in § 9.3. § 9.14 Emergency calling requirements. (a) Emergency call handling requirements for TTY-based TRS providers. (b) Additional emergency calling requirements applicable to internet-based TRS providers. (2) Each provider of internet-based TRS shall: (i) When responsible for placing or routing voice calls to the public switched telephone network, accept and handle emergency calls and access, either directly or via a third party, a commercially available database that will allow the provider to determine an appropriate PSAP, designated statewide default answering point, or appropriate local emergency authority that corresponds to the caller's location, and to relay the call to that entity; (ii) Implement a system that ensures that the provider answers an incoming emergency call before other non-emergency calls ( i.e., (iii) Provide 911 and E911 service in accordance with paragraphs (c) through (e) of this section, as applicable; (iv) Deliver to the PSAP, designated statewide default answering point, or appropriate local emergency authority, at the outset of the outbound leg of an emergency call, at a minimum, the name of the relay user and location of the emergency, as well as the name of the relay provider, the CA's callback number, and the CA's identification number, thereby enabling the PSAP, designated statewide default answering point, or appropriate local emergency authority to re-establish contact with the CA in the event the call is disconnected; (v) In the event one or both legs of an emergency call are disconnected ( i.e., (vi) Ensure that information obtained as a result of this section is limited to that needed to facilitate 911 services, is made available only to emergency call handlers and emergency response or law enforcement personnel, and is used for the sole purpose of ascertaining a user's location in an emergency situation or for other emergency or law enforcement purposes. (c) E911 Service for VRS and IP Relay before January 6, 2021, for fixed services, and before January 6, 2022, for non-fixed services Scope. (2) E911 Service. (i) Provide that user with E911 service as described in this section; (ii) Request, at the beginning of each emergency call, the caller's name and location information, unless the VRS or IP Relay provider already has, or has access to, Registered Location information for the caller; (iii) Transmit all 911 calls, as well as ANI, the caller's Registered Location, the name of the VRS or IP Relay provider, and the CA's identification number for each call, to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's Registered Location and that has been designated for telecommunications carriers pursuant to § 9.4, provided that “all 911 calls” is defined as “any communication initiated by an VRS or IP Relay user dialing 911”; (iv) Route all 911 calls through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network, provided that nothing in this subparagraph shall preclude routing the call first to a call center to ascertain the caller's location in the event that the VRS or IP Relay provider believes the caller may not be located at the Registered Location; and (v) Make the Registered Location, the name of the VRS or IP Relay provider, and the CA's identification number available to the appropriate PSAP, designated statewide default answering point, or appropriate local emergency authority from or through the appropriate automatic location information (ALI) database. (3) Service level obligation. (4) Registered location requirement. (i) Obtain from each Registered internet-based TRS user, prior to the initiation of service, the physical location at which the service will first be used; and (ii) If the VRS or IP Relay is capable of being used from more than one location, provide their registered internet-based TRS users one or more methods of updating the user's Registered Location, including at least one option that requires use only of the iTRS access technology necessary to access the VRS or IP Relay. Any method used must allow a registered internet-based TRS user to update the Registered Location at will and in a timely manner. (d) E911 Service for VRS and IP Relay on or after January 6, 2021, for fixed services, and on or after January 6, 2022, for non-fixed services Scope. (2) E911 Service. (i) Provide that user with E911 service as described in this section; (ii) Request, at the beginning of each emergency call, the caller's name and dispatchable location, unless the VRS or IP relay provider already has, or has access to the location information described in paragraph (d)(4) of this section; (iii) Transmit the following to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's dispatchable location and that has been designated for telecommunications carriers pursuant to § 9.4: (A) All 911 calls, provided that “all 911 calls” is defined as “any communication initiated by an VRS or IP Relay user dialing 911;” (B) ANI, the name of the VRS or IP Relay provider, and the CA's identification number for each call; and (C) The location information described in paragraph (d)(4) of this section. (iv) Route all 911 calls through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network, provided that nothing in this subparagraph shall preclude routing the call first to a call center to ascertain the caller's location in the event that the VRS or IP Relay provider is unable to obtain or confirm the caller's location information; and (v) Make the location information described in paragraph (d)(4) of this section, the name of the VRS or IP Relay provider, and the CA's identification number available to the appropriate PSAP, designated statewide default answering point, or appropriate local emergency authority from or through the appropriate automatic location information (ALI) database. (3) Service level obligation. (4) Location requirements. (i) Fixed VRS and IP Relay services. Providers of fixed VRS and IP Relay services must provide automated dispatchable location with each 911 call. (ii) Non-fixed VRS and IP Relay services. For non-fixed VRS and IP Relay services (service that is capable of being used from more than one location), VRS and IP Relay service providers must provide location information in accordance with paragraph (d)(4)(ii)(A) of this section, if technically feasible. Otherwise, VRS and IP Relay service providers must either provide location information in accordance with paragraph (d)(4)(ii)(B) or (C), or meet paragraph (d)(4)(ii)(D) of this section. (A) Provide automated dispatchable location, if technically feasible. (B) Provide Registered Location information that meets the following requirements: ( 1 ( 2 ( 3 (C) Provide Alternative Location Information as defined in § 9.3. (D) Route the caller to a call center. (e) E911 Service for IP CTS on or after January 6, 2021, for fixed services, and on or after January 6, 2022, for non-fixed services Scope. (2) E911 Service. (i) Provide that user with E911 service as described in this section; (ii) Transmit or provide the following to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's dispatchable location and that has been designated for telecommunications carriers pursuant to § 9.4: (A) All 911 calls, provided that “all 911 calls” is defined as “any communication initiated by an IP CTS user dialing 911;” (B) With the call, a telephone number that is assigned to the caller and that enables the PSAP, designated statewide default answering point, or appropriate local emergency authority to call the 911 caller back directly, while enabling the caller to receive captions on the callback; and (C) The location information described in paragraph (e)(4) of this section. (iii) Route all 911 calls through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network, provided that nothing in this subparagraph shall preclude routing the call first to a call center to ascertain the caller's location in the event that the covered IP CTS provider is unable to obtain or confirm the caller's location information; and (iv) Make the location information described in paragraph (e)(4) of this section and callback number available to the appropriate PSAP, designated statewide default answering point, or appropriate local emergency authority from or through the appropriate automatic location information (ALI) database. (3) Service level obligation. (4) Location requirements. (i) Fixed IP CTS. Providers of fixed IP CTS must provide automated dispatchable location with each 911 call. (ii) Non-fixed IP CTS. For non-fixed IP CTS (service that is capable of being used from more than one location), covered IP CTS providers must provide location information in accordance with paragraph (e)(4)(ii)(A) of this section, if technically feasible. Otherwise, covered IP CTS providers must either provide location information in accordance with paragraph (e)(4)(ii)(B) or (C), or meet paragraph (e)(4)(iii)(D) of this section. (A) Provide automated dispatchable location, if technically feasible. (B) Provide Registered Location information that meets the following requirements: ( 1 ( 2 (C) Provide Alternative Location Information as defined in § 9.3. (D) Route the caller to a call center. [84 FR 66760, Dec. 5, 2019, as amended at 85 FR 67450, Oct. 23, 2020] Subpart F—Multi-Line Telephone Systems § 9.15 Applicability. The rules in this subpart F apply to: (a) A person engaged in the business of manufacturing, importing, selling, or leasing multi-line telephone systems; (b) A person engaged in the business of installing, managing, or operating multi-line telephone systems; (c) Any multi-line telephone system that is manufactured, imported, offered for first sale or lease, first sold or leased, or installed after February 16, 2020. § 9.16 General obligations—direct 911 dialing, notification, and dispatchable location. (a) Obligation of manufacturers, importers, sellers, and lessors. (2) A person engaged in the business of manufacturing, importing, selling, or leasing multi-line telephone systems may not manufacture or import for use in the United States, or sell or lease or offer to sell or lease in the United States, a multi-line telephone system, unless such system has the capability, after proper installation in accordance with paragraph (b) of this section, of providing the dispatchable location of the caller to the PSAP with 911 calls. (b) Obligation of installers, managers, or operators. (2) A person engaged in the business of installing, managing, or operating multi-line telephone systems shall, in installing, managing, or operating such a system for use in the United States, configure the system to provide MLTS notification to a central location at the facility where the system is installed or to another person or organization regardless of location, if the system is able to be configured to provide the notification without an improvement to the hardware or software of the system. MLTS notification must meet the following requirements: (i) MLTS notification must be initiated contemporaneously with the 911 call, provided that it is technically feasible to do so; (ii) MLTS notification must not delay the call to 911; and (iii) MLTS notification must be sent to a location where someone is likely to see or hear it. (3) A person engaged in the business of installing multi-line telephone systems may not install such a system in the United States unless it is configured such that it is capable of being programmed with and conveying the dispatchable location of the caller to the PSAP with 911 calls consistent with paragraphs (i), (ii) and (iii) of this section. A person engaged in the business of managing or operating multi-line telephone systems may not manage or operate such a system in the United States unless it is configured such that the dispatchable location of the caller is conveyed to the PSAP with 911 calls consistent with paragraphs (i), (ii) and (iii) of this section. (i) Dispatchable location requirements for on-premises fixed telephones associated with a multi-line telephone system. An on-premises fixed telephone associated with a multi-line telephone system shall provide automated dispatchable location no later than January 6, 2021; (ii) Dispatchable location requirements for on-premises non-fixed devices associated with a multi-line telephone system. No later than January 6, 2022, an on-premises non-fixed device associated with a multi-line telephone system shall provide to the appropriate PSAP automated dispatchable location, when technically feasible; otherwise, it shall provide dispatchable location based on end user manual update, or alternative location information as defined in § 9.3. (iii) Dispatchable location requirements for off-premises devices associated with a multi-line telephone system. No later than January 6, 2022, an off-premises device associated with a multi-line telephone system shall provide to the appropriate PSAP automatic dispatchable location, if technically feasible; otherwise, it shall provide dispatchable location based on end user manual update, or enhanced location information, which may be coordinate-based, consisting of the best available location that can be obtained from any available technology or combination of technologies at reasonable cost. [84 FR 66760, Dec. 5, 2019, as amended at 85 FR 78022, Dec. 3, 2020] § 9.17 Enforcement, compliance date, State law. (a) Enforcement. et seq., (2) In the event of noncompliance with § 9.16(b), the person engaged in the business of managing the multi-line telephone system shall be presumed to be responsible for the noncompliance. (3) Persons alleging a violation of the rules in § 9.16 may file a complaint under the procedures set forth in §§ 1.711 through 1.737 of this chapter. (b) Compliance date. (c) Effect on State law. [84 FR 66760, Dec. 5, 2019, as amended at 87 FR 60105, Oct. 4, 2022] Subpart G—Mobile-Satellite Service § 9.18 Emergency Call Center service. (a) Providers of Mobile-Satellite Service to end-user customers (47 CFR part 25, subparts A through D) must provide Emergency Call Center service to the extent that they offer real-time, two way switched voice service that is interconnected with the public switched network and use an in-network switching facility which enables the provider to reuse frequencies and/or accomplish seamless hand-offs of subscriber calls. Emergency Call Center personnel must determine the emergency caller's phone number and location and then transfer or otherwise redirect the call to an appropriate public safety answering point. Providers of Mobile-Satellite Services that use earth terminals that are not capable of use while in motion are exempt from providing Emergency Call Center service for such terminals. (b) Each Mobile-Satellite Service carrier that is subject to the provisions of paragraph (a) of this section must maintain records of all 911 calls received at its emergency call center. By October 15, of each year, Mobile-Satellite Service carriers providing service in the 1.6/2.4 GHz and 2 GHz bands must submit a report to the Commission regarding their call center data, current as of September 30 of that year. By June 30, of each year, Mobile-Satellite Service carriers providing service in bands other than 1.6/2.4 GHz and 2 GHz must submit a report to the Commission regarding their call center data, current as of May 31 of that year. These reports must include, at a minimum, the following: (1) The name and address of the carrier, the address of the carrier's emergency call center, and emergency call center contact information; (2) The aggregate number of calls received by the call center each month during the relevant reporting period; (3) An indication of how many calls received by the call center each month during the relevant reporting period required forwarding to a public safety answering point and how many did not require forwarding to a public safety answering point. Subpart H—Resiliency, Redundancy, Interoperability, and Reliability of 911 Communications § 9.19 Provision of reliable 911 service. (a) Definitions. (1) Monitoring aggregation point. (2) Certification. (i) Has satisfied the obligations of paragraph (c) of this section and § 9.20(a); (ii) Has adequate internal controls to bring material information regarding network architecture, operations, and maintenance to the certifying official's attention; and (iii) Has made the certifying official aware of all material information reasonably necessary to complete the certification. (3) Certifying official. (4) Covered 911 service provider. (A) The provision of 911, E911, or NG911 capabilities such as call routing, automatic location information (ALI), automatic number identification (ANI), or the functional equivalent of those capabilities, directly to a public safety answering point (PSAP), statewide default answering point, or appropriate local emergency authority as defined in § 9.3. (B) The operation of one or more central offices that directly serve a PSAP. For purposes of this section, a central office directly serves a PSAP if it hosts a selective router or ALI/ANI database, provides equivalent NG911 capabilities, or is the last service-provider facility through which a 911 trunk or administrative line passes before connecting to a PSAP. (C) The provision of Next Generation Core Services (NGCS) facilities, including NGCS location facilities or NGCS routing facilities, directly by contract or tariffed service to any 911 Authority, whether via owned and operated facilities or leased or contracted facilities. (D) The operation of an ESInet or legacy PSAP gateway (LPG). (E) The operation of a Location Information Server (LIS) or equivalent IP 911 location database that provides service to two or more originating service providers (OSPs). (F) The operation of a Legacy Network Gateway (LNG), a legacy selective router gateway (LSRG), or an emergency services gateway (ESGW) used for IP conversion of 911 traffic, that provides service to two or more OSPs. (G) The operation of a major IP transport facility. (H) The operation of an IP 911 traffic aggregation facility. (I) The operation of interstate interconnecting ESInet facilities. (J) For purposes of the requirement in § 4.9(h) of this chapter to notify 911 special facilities about outages that potentially affect them, only entities described in paragraphs (a)(4)(i)(A) through (D) of this section are “covered 911 service providers.” (ii) The term “covered 911 service provider” shall not include any entity that: (A) Constitutes a PSAP, 911 Authority, or other governmental authority to the extent that it provides 911, E911, or NG911 capabilities; or (B) Offers the capability to originate 911 calls where another service provider delivers those calls and associated number or location information to the appropriate 911 Authority. (5) Covered 911 circuits and paths Legacy covered 911 circuits. (ii) IP covered 911 paths. (A) Originate at an NG911 Delivery Point or equivalent ESInet point of interconnection and terminate at the last routing facility before the NG911 PSAP or the legacy PSAP gateway, including all equipment associated with a covered 911 service necessary for the delivery of 911 traffic to the PSAP, such as any trunks, circuits, or paths to and from NGCS facilities and the ESInet transmission network necessary for routing and caller location information to the PSAP(s), and any intermediate paths in the chains of delivery; (B) Transport 911 traffic via major IP transport facilities for ultimate delivery at an NG911 Delivery Point or equivalent ESInet point of interconnection, including any intermediate paths in the chain of delivery; or (C) Transport 911 traffic via IP 911 traffic aggregation facilities for ultimate delivery at an NG911 Delivery Point or equivalent ESInet point of interconnection, including any interconnecting paths between ESInets, and including any intermediate paths in the chain of delivery. (6) Diversity audit. (7) Monitoring links. (8) Physically diverse. (9) Tagging. (10) Geographically distributed. (11) Load balanced. (12) Major IP transport facility. (13) IP 911 traffic aggregation facility. (14) NGCS location facilities. (15) NGCS routing facilities. (16) Interstate interconnecting ESInet facilities. (17) Interoperability standards testing. (18) Interoperability conformance testing. (19) Interoperability. (b) Provision of reliable 911 service. (c) 911 reliability benchmarks Physical diversity. (i) For IP covered 911 paths, covered 911 service providers may satisfy this physical diversity benchmark by implementing automatic rerouting capabilities, load balancing, and geographically-distributed routing facilities, transport nodes, and node links sufficient to reasonably mitigate the risks of single points of failure. Covered 911 service providers may use dedicated diverse private facilities such as MPLS, cloud-based path redundancy, or VPN services over the public internet or equally secure industry protocols as automatically re-routed paths. (ii) For legacy covered 911 circuits, covered 911 service providers may satisfy this physical diversity benchmark by conducting yearly diversity audits and certifying that all of the legacy covered 911 circuits in its network are tagged and are physically diverse such that no network or facility element constitutes a single point of failure. (2) Operational integrity. (i) LNGs, LISs, LSRGs, ESGWs, LPGs, and NGCS facilities covered by paragraph (a)(4)(i) of this section achieve operational integrity if they have the capability to ensure continuity of services via an uninterruptible and continuous power supply and automatic switchover to geographically diverse backup facilities sufficient to prevent service disruption. (ii) For central offices hosting selective routers, ALI/ANI, or functioning as the last central office serving a PSAP, covered 911 service providers satisfy this operational integrity benchmark by implementing backup power facilities for covered legacy 911 central office facilities for at least 24 hours at full office load if the central office directly serves a PSAP, or, for at least 72 hours at full office load if the central office hosts a selective router, including all equipment design, proper installation, necessary testing, and equipment maintenance to ensure the automatic and independent function of backup power facilities. (3) Network monitoring. (i) Using geographically distributed automatic disruption detection and alarm systems to monitor IP covered facilities, including the IP routers, transport nodes, and node links used to make covered 911 circuits and paths physically diverse, constitutes physically diverse monitoring. (ii) For non-IP covered facilities, maintaining and annually auditing physically diverse monitoring aggregation points, monitoring links, and NOCs constitutes physically diverse monitoring. (d) Compliance date. [84 FR 66760, Dec. 5, 2019, as amended at 88 FR 9765, Feb. 15, 2023; 91 FR 1403, Jan. 14, 2026; 91 FR 42841, July 10, 2026] § 9.20 911 Reliability certifications; interoperability reporting; cessation notifications. (a) 911 reliability filings Attestation. (ii) Any new covered 911 service provider that begins service for the first time after the date in paragraph (a)(1)(i) of this section shall submit an attestation when it begins service. (2) Certification Initial certification. (ii) Updates covering material changes. (A) The cause of the change is remedied within the applicable update period; (B) The change reflects incremental conformance with the reliability elements in § 9.19(c)(1) through (3), rather than reliance on alternative measures, for less than 50 percent of its covered 911 services, circuits, and paths; or (C) The change to a covered 911 service provider's ownership structure is pro forma (iii) Non-conforming facilities and services. (A) The covered 911 service provider has taken alternative measures to mitigate the risks of lack of physical diversity, operational integrity, or network monitoring; or (B) The physical diversity, operational integrity, or network monitoring benchmark is not applicable to the covered 911 service provider. (iv) Covered 911 service providers are required to answer additional questions about covered 911 circuits and paths and covered 911 services as directed by the Public Safety and Homeland Security Bureau. (b) 911 interoperability reports. (2) NGCS and ESInet covered 911 service providers defined in § 9.19(a)(4)(i)(C) or (D) are required to answer additional questions about covered 911 circuits and paths and covered 911 services as directed by the Public Safety and Homeland Security Bureau. (c) Confidential treatment of certifications and reports. (2) Information submitted with such certifications and reports shall be presumed confidential to the extent that it consists of non-public descriptions of networks or facilities, compliance plans, or additional information requested by the Bureau with respect to a certification. (d) 911 Authority access to certifications and reports. (2) Covered 911 service providers must provide the requested certifications or reports within 14 days of a request. Covered 911 service providers may omit or redact information relating to portions of their networks or facilities that are not located within and do not provide service to the requesting 911 Authority's jurisdiction. Covered 911 service providers may condition the granting of such requests on the 911 Authority's execution of a confidentiality agreement under terms not more restrictive than those set forth in § 4.2 of this chapter and in related guidance, instructions, and forms published by the Commission. (3) To the extent the Public Safety and Homeland Security Bureau provides statewide, territorial, or tribal 911 Authorities with, or grants them access to, 911 reliability certifications and interoperability reports, it shall do so in accordance with relevant confidentiality terms and conditions pursuant to which it provides access to NORS data under § 4.2 of this chapter and related guidance, instructions, and forms published by the Commission. (e) Record retention. (f) Covered service cessation notices. (g) Remedial action orders and procedures. (1) Notice. (2) Response. (3) Order. (4) Notice to 911 Authorities. (h) Compliance date. [91 FR 42841, July 10, 2026] Subpart I—911 Fees Source: 86 FR 45908, Aug. 17, 2021, unless otherwise noted. § 9.21 Applicability. The rules in this subpart apply to States or taxing jurisdictions that collect 911 fees or charges (as defined in this subpart) from commercial mobile services, IP-enabled voice services, and other emergency communications services. § 9.22 Definitions. For purposes of this subpart, the terms in this section have the following meanings set forth in this section. Furthermore, where the Commission uses the term “acceptable” in this subpart, it is for purposes of the Consolidated Appropriations Act, 2021, Public Law 116-260, Division FF, Title IX, section 902(c)(1)(C). 911 fee or charge. Diversion. Other emergency communications services. State. State or taxing jurisdiction. et seq. § 9.23 Designation of acceptable obligations or expenditures for purposes of the Consolidated Appropriations Act, 2021, Division FF, Title IX, section 902(c)(1)(C). (a) Acceptable purposes and functions for the obligation or expenditure of 911 fees or charges for purposes of section 902 are limited to: (1) Support and implementation of 911 services provided by or in the State or taxing jurisdiction imposing the fee or charge; and (2) Operational expenses of public safety answering points within such State or taxing jurisdiction. (b) Examples of acceptable purposes and functions include, but are not limited to, the following, provided that the State or taxing jurisdiction can adequately document that it has obligated or spent the fees or charges in question for these purposes and functions: (1) PSAP operating costs, including lease, purchase, maintenance, replacement, and upgrade of customer premises equipment (CPE) (hardware and software), computer aided dispatch (CAD) equipment (hardware and software), and the PSAP building/facility and including NG911, cybersecurity, pre-arrival instructions, and emergency notification systems (ENS). PSAP operating costs include technological innovation that supports 911; (2) PSAP personnel costs, including telecommunicators' salaries and training; (3) PSAP administration, including costs for administration of 911 services and travel expenses associated with the provision of 911 services; (4) Integrating public safety/first responder dispatch and 911 systems, including lease, purchase, maintenance, and upgrade of CAD hardware and software to support integrated 911 and public safety dispatch operations; and (5) Providing for the interoperability of 911 systems with one another and with public safety/first responder radio systems. (c) Examples of purposes and functions that are not acceptable for the obligation or expenditure of 911 fees or charges for purposes of section 902 include, but are not limited to, the following: (1) Transfer of 911 fees into a State or other jurisdiction's general fund or other fund for non-911 purposes; (2) Equipment or infrastructure for constructing or expanding non-public safety communications networks ( e.g., (3) Equipment or infrastructure for law enforcement, firefighters, and other public safety/first responder entities that does not directly support providing 911 services. (d) If a State or taxing jurisdiction collects fees or charges designated for “public safety,” “emergency services,” or similar purposes that include the support or implementation of 911 services, the obligation or expenditure of such fees or charges shall not constitute diversion provided that the State or taxing jurisdiction: (1) Specifies the amount or percentage of such fees or charges that is dedicated to 911 services; (2) Ensures that the 911 portion of such fees or charges is segregated and not commingled with any other funds; and (3) Obligates or expends the 911 portion of such fees or charges for acceptable purposes and functions as defined under this section. § 9.24 Petition regarding additional purposes and functions. (a) A State or taxing jurisdiction may petition the Commission for a determination that an obligation or expenditure of 911 fees or charges for a purpose or function other than the purposes or functions designated as acceptable in § 9.23 should be treated as an acceptable purpose or function. Such a petition must meet the requirements applicable to a petition for declaratory ruling under § 1.2 of this chapter. (b) The Commission shall grant the petition if the State or taxing jurisdiction provides sufficient documentation to demonstrate that the purpose or function: (1) Supports public safety answering point functions or operations; or (2) Has a direct impact on the ability of a public safety answering point to: (i) Receive or respond to 911 calls; or (ii) Dispatch emergency responders. § 9.25 Participation in annual fee report data collection. (a) If a State or taxing jurisdiction receives a grant under section 158 of the National Telecommunications and Information Administration Organization Act (47 U.S.C. 942) after December 27, 2020, such State or taxing jurisdiction shall provide the information requested by the Commission to prepare the report required under section 6(f)(2) of the Wireless Communications and Public Safety Act of 1999, as amended (47 U.S.C. 615a-1(f)(2)). (b) Each State or taxing jurisdiction subject to paragraph (a) of this section must file the information requested by the Commission and in the form specified by the Public Safety and Homeland Security Bureau. [86 FR 45908, Aug. 17, 2021, as amended at 87 FR 37239, June 22, 2022] § 9.26 Advisory committee participation. Notwithstanding any other provision of law, any State or taxing jurisdiction identified by the Commission in the report required under section 6(f)(2) of the Wireless Communications and Public Safety Act of 1999, as amended (47 U.S.C. 615a-1(f)(2)), as engaging in diversion of 911 fees or charges shall be ineligible to participate or send a representative to serve on any advisory committee established by the Commission. Subpart J—Next Generation 911 Source: 89 FR 78128, Sept. 24, 2024, unless otherwise noted. § 9.27 Applicability, scope, and purpose. (a) The purpose of this subpart is to set forth requirements and conditions in order to facilitate the transition to Next Generation 911 (NG911), and to assist with creating an NG911 architecture that is secure, interoperable, and based on commonly accepted standards. (b) The rules in this subpart apply to “originating service providers” as defined in § 9.28. (c) An originating service provider subject to the rules in this subpart shall be considered to have delivered 911 traffic to a public safety answering point (PSAP) if the originating service provider's 911 traffic is delivered to NG911 Delivery Points designated by the 911 Authority pursuant to § 9.32 and the other requirements in this subpart are satisfied. § 9.28 Definitions. For purposes of this subpart, the terms in this section have the following meanings: 911 Authority. 911 traffic. Commonly accepted standards. (1) Enable interoperability; and (2) Are— (i) Developed and approved by a standards development organization that is accredited by a United States standards body (such as the American National Standards Institute) or an equivalent international standards body in a process that— (A) Is open to the public, including open for participation by any person; and (B) Provides for a conflict resolution process; (ii) Subject to an open comment and input process before being finalized by the standards development organization; (iii) Consensus-based; and (iv) Made publicly available once approved. Covered text provider. Emergency Services Internet Protocol Network (ESInet). Functional element. Location Information Server (LIS). Location Validation Function (LVF). Nationwide CMRS provider. Next Generation 911 (NG911). (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. NG911 Delivery Point. Non-nationwide CMRS provider. Non-rural wireline provider. Originating service providers. Rural incumbent local exchange carrier (RLEC). Session Initiation Protocol (SIP). Wireline provider. § 9.29 Next Generation 911 transition requirements. (a) Phase 1. (1) Deliver all 911 traffic bound for the relevant PSAPs in the IP-based SIP format requested by the 911 Authority; (2) Obtain and deliver 911 traffic to enable the ESInet and other NG911 network facilities to transmit all 911 traffic to the destination PSAP; (3) Deliver all such 911 traffic to NG911 Delivery Points designated by the 911 Authority pursuant to § 9.32; and (4) Complete connectivity testing to confirm that the 911 Authority receives 911 traffic in the IP-based SIP format requested by the 911 Authority. (b) Phase 2. (1) Comply with all Phase 1 requirements set forth in paragraph (a) of this section; (2) Deliver all 911 traffic bound for the relevant PSAPs to NG911 Delivery Points designated by the 911 Authority pursuant to § 9.32 in the IP-based SIP format that complies with NG911 commonly accepted standards identified by the 911 Authority, including having location information embedded in the call signaling using Presence Information Data Format—Location Object (PIDF-LO) or the functional equivalent; (3) 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; and (4) 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. § 9.30 Next Generation 911 implementation deadlines. (a) Non-rural wireline providers, nationwide CMRS providers, covered text providers, and interconnected VoIP providers shall— (1) Comply with the Phase 1 requirements set forth in § 9.29(a) by six months after receiving a Phase 1 valid request from a 911 Authority, as set forth in § 9.31(a); and (2) Comply with the Phase 2 requirements set forth in § 9.29(b) by: (i) Six months after receiving a Phase 2 valid request from a 911 Authority, as set forth in § 9.31(b); or (ii) If the 911 Authority's Phase 2 valid request is made before the originating service provider is compliant with the Phase 1 requirements or is made before the Phase 1 implementation deadline, six months after the earlier of: (A) The date when the originating service provider is compliant with the Phase 1 requirements set forth in § 9.29(a); or (B) The implementation deadline set forth in paragraph (a)(1) of this section. (b) RLECs, non-nationwide CMRS providers, and internet-based TRS providers shall— (1) Comply with the Phase 1 requirements set forth in § 9.29(a) by 12 months after receiving a Phase 1 valid request from a 911 Authority, as set forth in § 9.31(a); and (2) Comply with the Phase 2 requirements set forth in § 9.29(b) by: (i) 12 months after receiving a Phase 2 valid request from a 911 Authority, as set forth in § 9.31(b); or (ii) If the 911 Authority's Phase 2 valid request is made before the originating service provider is compliant with the Phase 1 requirements or is made before the Phase 1 implementation deadline, 12 months after the earlier of: (A) The date when the originating service provider is compliant with the Phase 1 requirements set forth in § 9.29(a); or (B) The implementation deadline set forth in paragraph (b)(1) of this section. § 9.31 Valid requests for delivery of 911 traffic in Internet Protocol-based formats. (a) Phase 1 valid request. (1) Certifies that it has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format and transmit such traffic to the PSAP(s) connected to it; (2) Certifies 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 originating service provider; (3) Certifies that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format; (4) Identifies the NG911 Delivery Point(s) designated pursuant to § 9.32; and (5) Provides notification to the originating service provider that includes the information and certifications set forth in paragraphs (a)(1) through (4) of this section. Notification by the 911 Authority via a registry made available by the Commission in accordance with requirements established in connection therewith, or any other written notification reasonably acceptable to the originating service provider, shall constitute sufficient notification for purposes of this paragraph. (b) Phase 2 valid request. (1) Certifies 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; (2) Certifies 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 originating service provider; (3) Certifies 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 originating service provider; (4) Certifies 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; (5) Identifies the NG911 Delivery Point(s) designated pursuant to § 9.32; and (6) Provides notification to the originating service provider that includes the information and certifications set forth in paragraphs (b)(1) through (5) of this section. Notification by the 911 Authority via a registry made available by the Commission in accordance with requirements established in connection therewith, or any other written notification reasonably acceptable to the originating service provider, shall constitute sufficient notification for purposes of this paragraph. (c) Originating service providers' petitions challenging 911 Authorities' requests. (1) The petition process shall be subject to the procedural requirements set forth in §§ 1.41, 1.45, and 1.47 of this chapter. (2) The petition must be in the form of an affidavit signed by a director or officer of the originating service provider, documenting: (i) The basis for the originating service provider's assertion that the 911 Authority's request does not satisfy one or more of the conditions set forth in paragraph (a) or (b) of this section for a Phase 1 or Phase 2 valid request. (ii) Each of the specific steps the originating service provider has taken to implement the Phase 1 requirements set forth in § 9.29(a) or the Phase 2 requirements set forth in § 9.29(b). (iii) The basis for the originating service provider's assertion that it cannot make further implementation efforts until the 911 Authority satisfies the conditions set forth in paragraph (a) or (b) of this section for a Phase 1 or Phase 2 valid request. (iv) The specific steps that remain to be completed by the originating service provider and, to the extent known, the 911 Authority or other parties before the originating service provider can implement the Phase 1 requirements set forth in § 9.29(a) or the Phase 2 requirements set forth in § 9.29(b). (3) All affidavits must be correct. The originating service provider's director or officer who signs the affidavit has the duty to personally determine that the affidavit is correct. If the affidavit is incorrect, he or she, as well as the originating service provider, may be subject to enforcement action. (4) An originating service provider may not file an inadequate or incomplete petition. If an originating service provider's petition is inadequate and/or incomplete and the originating service provider has not met its obligations as set forth in § 9.29(a) or (b) at the time of the relevant deadline, the originating service provider may be considered noncompliant with the applicable rules as if the petition had not been filed. (5) An originating service provider that challenges a 911 Authority's valid request must describe all steps taken toward implementing the Phase 1 requirements set forth in § 9.29(a) or the Phase 2 requirements set forth in § 9.29(b) that are not dependent on the readiness of the 911 Authority. (6) The 911 Authority may file an opposition to the originating service provider's petition and the originating service provider may file a reply to the opposition in accordance with § 1.45 of this chapter. A copy of the document (petition, opposition, or reply) must be served on the other party (911 Authority or originating service provider) at the time of the filing in accordance with § 1.47 of this chapter. [89 FR 78128, Sept. 24, 2024, as amended at 90 FR 13557, Mar. 25, 2025] § 9.32 Designation of NG911 Delivery Points. A 911 Authority may designate one or more NG911 Delivery Points where originating service providers must deliver 911 traffic to the ESInet pursuant to § 9.29, provided that— (a) Each NG911 Delivery Point is located in the same State or territory as the PSAPs connected to the ESInet; and (b) The 911 Authority or the ESInet provides facilities at the input to the NG911 Delivery Point to receive 911 traffic in accordance with the applicable phase. § 9.33 Cost responsibilities. (a) Originating service providers are responsible for the costs of complying with the applicable Phase 1 and Phase 2 requirements assigned to them under § 9.29, including the costs of— (1) Transmitting 911 traffic to NG911 Delivery Points; (2) 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 (3) 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. (b) Originating service providers are not responsible for the costs of furnishing, maintaining, or upgrading NG911 Delivery Points, ESInets, Next Generation 911 Core Services networks, or PSAPs. § 9.34 Modification of NG911 requirements by mutual agreement. (a) Nothing in this subpart shall prevent 911 Authorities and originating service providers from establishing, by mutual consent, terms different from the requirements set forth in §§ 9.29 through 9.33. (b) If a 911 Authority and an originating service provider enter into an agreement pursuant to paragraph (a) of this section, within 30 days of the date when any such agreement is executed, the originating service provider must notify the Commission of the agreement. The notification must identify with specificity each requirement in the rules that is impacted by the agreement and must state with specificity how the terms of the agreement differ from each impacted rule. The same notification is required if the 911 Authority and originating service provider amend, modify, or terminate the agreement. [89 FR 78128, Sept. 24, 2024, as amended at 90 FR 13557, Mar. 25, 2025]

Related documents

• 50 CFR Part 600 — Magnuson-Stevens Act Provisions#512148
• 50 CFR Part 622 — Fisheries of the Caribbean, Gulf of America, and South Atlantic#512149
• 50 CFR Part 635 — Atlantic Highly Migratory Species#512150
• 50 CFR Part 648 — Fisheries of the Northeastern United States#512151
• 50 CFR Part 660 — Fisheries off West Coast States#512152