Document Headings

                    Document headings vary by document type but may contain                    the following:                  
                -                       the agency or agencies that issued and signed a document                    
                -                       the number of the CFR title and the number of each part                      the document amends, proposes to amend, or is directly                      related to                    
                -                       the agency docket number / agency internal file number                    
                -                       the RIN which identifies each regulatory action listed in                      the Unified Agenda of Federal Regulatory and Deregulatory                      Actions                    

                    See the                                          Document Drafting Handbook                                        for more details.                  

###### Federal Communications Commission

          - [OMB 3060-XXXX; FR ID 252551]

# AGENCY:

Federal Communications Commission.

# ACTION:

Notice and request for comments.

# SUMMARY:

As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collection. Comments are requested concerning: whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees.

# DATES:

Written PRA comments should be submitted on or before December 16, 2024. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contact listed below as soon as possible.

# ADDRESSES:

                        Direct all PRA comments to Nicole Ongele, FCC, via email                         *PRA@fcc.gov*                         and to                         *nicole.ongele@fcc.gov.*

# FOR FURTHER INFORMATION CONTACT:

For additional information about the information collection, contact Nicole Ongele, (202) 418-2991.

# SUPPLEMENTARY INFORMATION:

The FCC may not conduct or sponsor a collection of information unless it displays a currently valid control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid Office of Management and Budget (OMB) control number.

*OMB Control Number:*                     3060-XXXX.                

*Title:*                     Facilitating Implementation of Next Generation 911 Services (NG911).                

*Form Number:*                     N/A.                

*Type of Review:*                     New information collection.                

*Respondents:*                     State, Local, or Tribal Government, and business or other for-profit entities.                

*Number of Respondents and Responses:*                     1,543 respondents; 2,840 responses.                

*Estimated Time per Response:*                     2-40 hours.                

*Frequency of Response:*                     On occasion reporting requirement; third party disclosure requirement.                

*Obligation to Respond:*                     Required to obtain or retain benefits. Statutory authority for this collection is contained in sections 1, 2, 4(i), 201, 214, 222, 225, 251(e), 301, 303, 316, and 332 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 201, 214, 222, 225, 251(e), 301, 303, 316, 332, and the Wireless Communications and Public Safety Act of 1999, Public Law 106-81, as amended, 47 U.S.C. 615 note, 615, 615a, 615a-1, 615b; and section 106 of the Twenty-First Century Communications and Video Accessibility Act of 2010, Public Law 111-260, 47 U.S.C. 615c.                

*Total Annual Burden:*                     10,012 hours.                

*Total Annual Cost:*                     No Cost.                

*Needs and Uses:*                     In a Report and Order released on July 19, 2024, FCC 24-78, published at 89 FR 78066, September 24, 2024, the Commission adopted rules to advance the nationwide transition to Next Generation 911 (NG911).[1]                                          These rules require wireline providers, Commercial Mobile Radio Service (CMRS) providers, covered text providers, providers of interconnected Voice over Internet Protocol (VoIP) services, and providers of Internet-based Telecommunications Relay Service (internet-based TRS) (collectively, OSPs) to take actions to start or continue the transition to NG911 in coordination with 911 Authorities. Associated with these rules, the Commission seeks OMB approval for notification and recordkeeping requirements applicable to 911 Authorities and OSPs, as described in more detail herein.                

                    Specifically, the rules require OSPs to take steps in two phases to complete all translation and routing to deliver 911 traffic, including associated routing and location information, in the requested IP-based format. These requirements are intended to correspond to and complement the readiness phases for 911 Authorities so that once a 911 Authority is ready to receive NG911 traffic in a specific IP format, the OSP will be required to deliver it in that format. In Phase 1, OSPs will be required to deliver 911 traffic in a basic Session Initiation Protocol (SIP) format to NG911 Delivery Points designated by the 911 Authority in the 911 Authority's State or territory, and complete connectivity testing. In Phase 2, OSPs will be required to deliver 911 traffic in SIP format that complies with NG911 commonly accepted standards to NG911 Delivery Points designated by the 911 Authority in the 911 Authority's State or territory, install and put into operation all necessary equipment, software, and other infrastructure, and complete connectivity testing. For each phase, OSPs must meet certain implementation deadlines. OSPs must bear the financial responsibility for such transmission, including costs associated with completing any needed TDM-to-IP translation and the costs of delivering associated routing and location                           ( print page 83013)                        information in the requested IP-based format.                

This rulemaking necessitates three information collections. First, under 47 CFR 9.31(a) and (b), 911 Authorities that wish to make Phase 1 or Phase 2 valid requests for delivery of 911 traffic in IP-based formats must provide notification containing certain certifications and information to either serving OPSs or to a registry to be made available by the Commission.

Second, in 47 CFR 9.31(c), OSPs that wish to challenge 911 Authorities' valid requests may submit a petition to the Public Safety and Homeland Security Bureau (PSHSB) within 60 days of the receipt of a Phase 1 or 2 request from a 911 Authority. Such challenge petitions must meet applicable procedural requirements and must be in the form of an affidavit that contains certain supporting information. The affected 911 Authority may file an opposition to the OSP's petition, and parties may file replies to oppositions. Filing parties must serve a copy of the document on the other party at the time of filing.

Third, in 47 CFR 9.34, 911 Authorities and OSPs may enter into voluntary mutual agreements that establish terms different from the Commission's rules. Within 30 days of the date when any such agreement is executed, or subsequently modified or terminated, the participating OSP must notify the Commission and provide information about alternative terms and transition deadlines.

OSPs will use the information collected pursuant to section 9.31(a) and (b) that is submitted by 911 Authorities to trigger their NG911 transition obligations described in section 9.29(a) and (b), respectively, and their NG911 implementation deadlines set forth in section 9.30(a) and (b), respectively. OSPs will receive notifications either directly from 911 Authorities, or from a registry where 911 Authorities may submit notifications. To the extent that 911 Authorities submit their valid request notifications in a registry made available by the Commission pursuant to section 9.31(a)(5) and (b)(6), the Commission will use the information collected pursuant to section 9.31(a) and (b) to monitor the progress of valid requests at each phase of the NG911 transition and to keep track of implementation deadlines associated with each valid request.

PSHSB will use the information collected pursuant to section 9.31 that is submitted by the OSPs in their petitions challenging 911 Authorities' valid requests, as well as information submitted by 911 Authorities who file oppositions to such petitions and information submitted by OSPs who file replies to such oppositions, to determine whether to pause the implementation deadline for that OSP, affirm the request of the 911 Authority as valid, or take other action as necessary. The requirements should simplify the enforcement and complaint process for both OSPs and 911 Authorities regarding OSPs' implementation deadlines.

In addition, the information collected pursuant to section 9.34(a) and (b) provides the Commission with awareness of any changes to the obligations of OSPs under the rules.

Federal Communications Commission.

Marlene Dortch,

Secretary, Office of the Secretary.

# Footnotes

1.                             The Report and Order was corrected via two errata released on September 5, 2024, and October 1, 2024.                    
        Back to Citation      

[FR Doc. 2024-23650 Filed 10-11-24; 8:45 am]

BILLING CODE 6712-01-P