Business or other for-profit

F ederal Communications Commission

Washington, D.C. 20554

[*** DRAFT ***]

Not Yet Approved by OMB

3060-XXXX

Expires: [DATE]

Estimated time per response: 2 hours

911 Authority Next Generation 911 (NG911) Valid Request Form

PS Docket No. 24-XX

911 Authorities¹ may use this form to request NG911 Phase 1 and/or Phase 2 service from originating service providers (OSPs).² It is recommended that 911 Authorities review the NG911 rules and definitions at 47 CFR part 9, subpart J – Next Generation 911 prior to completing this form. 911 Authorities are not required to use this form to request NG911 Phase 1 and/or Phase 2 service and may, as an alternative, provide direct notification to OSPs of their valid requests via written notification to the OSP.

Notification to OSPs under § 9.31(a)(5) or § 9.31(b)(6) occurs either when:

This form, appropriately completed and submitted in a manner consistent with current NG911 Registry submission instructions, becomes publicly available (if 911 Authority uses the NG911 Registry option to provide notice to all OSPs); or

The OSP receives this form, appropriately completed, or other written notification reasonably acceptable to the OSP (if 911 Authority chooses the option to provide direct notification to the OSP).

Instructions: Unless otherwise directed, please complete all questions of this form. If using this form to notify OSPs via the NG911 Registry option, please submit this form in a manner consistent with current NG911 Registry submission instructions, which are linked from the FCC’s 911 website, https://www.fcc.gov/general/9-1-1-and-e9-1-1-services. Respondents may submit additional documents with this form.

1. Full Name of 911 Authority

Provide the full name of the 911 Authority requesting NG911 Phase 1 service (under 47 CFR § 9.31(a)) and/or NG911 Phase 2 service (under 47 CFR § 9.31(b)).

     

2. Date of Submission

     

3. Name and Contact Information of Person Submitting Form

Name	     
Title	     
Agency	     
Phone Number	     
Email Address	     

4. Point of Contact Information for Additional Information

Please provide the contact information of the person or entity that will provide additional information to OSPs upon request, including information about the geographic location and facilities associated with NG911 Delivery Point(s)³ designated pursuant to 47 CFR § 9.32. (See Questions 7 and 8.)

We recommend, but do not require, 911 Authorities to submit an amended form with updated contact information in the event that the point of contact for additional information changes.

	Check this box if you are only updating point of contact information below and otherwise are not using this form to submit a valid request. In that event, please fill out the updated contact information below, and leave Questions 5-9 blank.
	Check this box if the point of contact is the same as the person identified in question 3 above. Otherwise, leave unchecked and complete the contact information below.

Name	     
Title	     
Agency	     
Phone Number	     
Email Address	     

5. Affected OSPs to Which this Valid Request Applies

Check one box, and if applicable, provide the requested information.

	All OSPs – This valid request form is intended to provide notification under § 9.31(a)(5) and/or § 9.31(b)(6) to all OSPs that provide service within the requesting 911 Authority’s jurisdiction. Optional – you may list all currently known OSPs and/or identify the geographic boundary in the space below, but this information is not required.
	Subset of OSPs – This valid request form is intended to provide notification under § 9.31(a)(5) and/or § 9.31(b)(6) to only a subset of OSPs that provide service within the requesting 911 Authority’s jurisdiction. In the space below, please identify or describe the limitation of this valid request notification, such as by identifying the affected OSP category(ies), the specific OSP(s), and/or the geographic boundary(ies) to which this valid request applies.
     

6. Request Type

Check one or both boxes.

	Phase 1 – Request for OSPs to begin 911 traffic delivery in the Internet Protocol (IP)-based Session Initiated Protocol (SIP)4 format requested by the 911 Authority. (See 47 CFR § 9 29(a) for a description of Phase 1 requirements for OSPs.)
	Phase 2 – Request for OSPs to begin 911 traffic delivery in the IP-based SIP format that complies with NG911 commonly accepted standards5 identified by the 911 Authority. (See 47 CFR § 9.29(b) for a description of Phase 2 requirements for OSPs.)

7. Phase 1 Certifications and Information

If requesting Phase 1 service (47 CFR § 9.29(a)), please complete this question. Check each box below to confirm each statement and provide the information requested. All four components of this question must be completed before the Commission will consider submission of this form to constitute a valid request for NG911 Phase 1 service for the NG911 registry. If requesting only Phase 2 service (47 CFR § 9.29(b)), please skip this question and proceed to question 8.

	The requesting 911 Authority 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 public safety answering point(s) (PSAP(s)) connected to it. (47 CFR § 9.31(a)(1).)
	The requesting 911 Authority certifies that it has obtained commitments from any Emergency Services Internet Protocol Network (ESInet)6 provider, Next Generation 911 Core Services provider, and/or call handling equipment provider needed to facilitate and complete connectivity testing within the compliance timeframe applicable to the OSP. (47 CFR § 9.31(a)(2).)
	The requesting 911 Authority certifies that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format. (47 CFR § 9.31(a)(3).)
In the space below, please identify the NG911 Delivery Point(s) that the requesting 911 Authority has designated pursuant to 47 CFR § 9.32. (47 CFR § 9.31(a)(4).) For the purposes of this form, provide the zip code(s) where the NG911 Delivery Point(s) are located. Responses on this form will be made publicly available. To avoid publicly disclosing potentially sensitive information, respondents should refrain from providing specific locations such as street addresses or building names on this form. The 911 Authority’s Point of Contact from Question 4 should be prepared to provide additional information to OSPs upon request.
     

8. Phase 2 Certifications and Information

If requesting Phase 2 service (47 CFR § 9.29(b)), please complete this question. Check each box below to confirm each statement and provide the information requested. All five components of this question must be completed before the Commission will consider submission of this form to constitute a valid request for NG911 Phase 2 service for the NG911 registry. If requesting only Phase 1 service, please skip this question and proceed to question 9.

	The requesting 911 Authority 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. (47 CFR § 9.31(b)(1).)
	The requesting 911 Authority certifies that its ESInet is connected to a fully functioning Next Generation 911 Core Services network that can provide access to a Location Validation Function7 and interface with a Location Information Server8 or its functional equivalent provided by the OSP. (47 CFR § 9.31(b)(2).)
	The requesting 911 Authority 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 OSP. (47 CFR § 9.31(b)(3).)
	The requesting 911 Authority 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. (47 CFR § 9.31(b)(4).)
	For 911 Authorities that are requesting Phase 1 AND Phase 2 service with this form, or that have previously submitted this form to request Phase 1 service and are now requesting Phase 2 service, please check this box if the NG911 Delivery Point(s) for this Phase 2 request is/are the SAME as what was identified for Phase 1. If you check this box, you need not provide additional information in the space below. Otherwise, please identify NG911 Delivery Point(s) below.
In the space below, please identify the NG911 Delivery Point(s) that the requesting 911 Authority has designated pursuant to 47 CFR § 9.32. (47 CFR § 9.31(b)(5).) For the purposes of this form, provide the zip code(s) where the NG911 Delivery Point(s) are located. Responses on this form will be made publicly available. To avoid publicly disclosing potentially sensitive information, respondents should refrain from providing specific locations such as street addresses or building names on this form. The 911 Authority’s Point of Contact from Question 4 should be prepared to provide additional information to OSPs upon request.
     

9. Optional - Destination PSAP(s) to which Request Applies⁹

In the table below, please list each PSAP for which Phase 1 and/or Phase 2 delivery is requested.

For each PSAP listed, please enter the FCC-assigned PSAP identification number (PSAP ID), PSAP name, and the NG911 phase requested. Please add extra rows and fields to the table as necessary.

If you do not know specific PSAP IDs or PSAP Names within your 911 Authority’s jurisdiction, please visit the FCC’s 911 Master PSAP Registry at https://www.fcc.gov/general/9-1-1-master-psap-registry or send an email inquiry to [email protected].

PSAP ID	PSAP Name	Phase(s) Requested (Enter 1, 2, or Both)
     	     	     
     	     	     
     	     	     

PRIVACY ACT STATEMENT

Authority: The Commission is authorized to pursue this collection pursuant to the authority contained in 47 U.S.C. §§ 151, 152, 154(i), 251(e), 301, 303, 332.

Purpose: To expedite the transition to NG911, the Commission adopted rules requiring OSPs to start or continue the transition to NG911 in coordination with 911 Authorities in two phases. Each phase is initiated by a 911 Authority submitting a valid request to OSPs within the jurisdiction where the 911 Authority is located for the OSPs to comply with NG911 requirements. As part of a valid Phase 1 or Phase 2 valid request to an OSP, the requesting 911 Authority must provide notification to each OSP provider that includes the certifications and information required by the Commission’s NG911 rules. 911 Authorities may provide this notification either by submission to an FCC-provided registry or by written notification to individual OSPs. 911 Authorities are directed to submit this form to the FCC’s Electronic Comment Filing System (ECFS), consistent with current FCC instructions (which may be found on the FCC’s website), in order to provide notification to OSPs via the FCC-provided registry.

In addition to collecting the information required by the Commission’s NG911 rules, ECFS collects from each filer the filer’s name(s), address, email address (optional), and IP address and operating system.¹⁰ The Commission uses this information to inform its decision-making, implementation, and enforcement activities.

Routine Uses: The FCC may disclose information provided via the filings when necessary and appropriate under 5 U.S.C. § 552a(b) of the Privacy Act to: the public under FCC regulations requiring public disclosure of the information contained in our records;¹¹ to third parties, including individuals and businesses in the communications industry and public safety, FCC vendors and their contractors, and to other federal agencies or state, local, U.S. territorial, and Tribal government entities to administer, support, participate in, or receive information related to, FCC programs and activities, or to ensure compliance with the confidentiality and other rules regarding information sharing in the FCC’s programs and activities; to federal, state, local, Tribal, international, or multinational law enforcement when FCC becomes aware of an indication of a violation or potential violation of a civil or criminal statute, law, regulation, or order; and to non-federal personnel, including contractors, grantees, and volunteers who have been engaged to assist the FCC in the performance of a contract service, grant, cooperative agreement, or other activity related to this system of records and who need to have access to the records in order to perform their activity.  

A complete list of the routine uses can be found in the system of records notices associated with this collection, FCC/OS-1, Electronic Comment Filing System (ECFS) and FCC-2, Business Contacts and Certifications, posted at https://www.fcc.gov/managing-director/privacy-transparency/privacy-act-information.

Disclosure: Submission of this form is voluntary. However, failure to provide complete information to the FCC, including name, contact information, and/or other necessary personally identifiable information (PII), may result in an invalid request for NG911 service under the Commission’s part 9, subpart J rules.

PAPERWORK REDUCTION ACT NOTICE

We have estimated that your response to this collection of information will take an average of 2 hours. Our estimate includes the time to read the instructions, look through existing records, gather and maintain required data, and actually complete and review the form or response. If you have any comments on this estimate, or on how we can improve the collection and reduce the burden it causes you, please write the Federal Communications Commission, Office of Managing Director, AMD‑PPM, 45 L Street, NE, Washington, DC 20554, Paperwork Reduction Act Program (3060‑XXXX). We will also accept your PRA comments via the Internet if you send an e-mail to [email protected].

Please DO NOT SEND COMPLETED FORMS TO THIS ADDRESS. You are not required to respond to a collection of information sponsored by the Federal government, and the government may not conduct or sponsor this collection, unless it displays a currently valid OMB control number and/or we fail to provide you with this notice. This collection has been assigned an OMB control number of 3060‑XXXX.

THIS NOTICE IS REQUIRED BY THE PAPERWORK REDUCTION ACT OF 1995, PUBLIC LAW 104-13, OCTOBER 1, 1995, 44 U.S.C. SECTION 3507.

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

2 “Originating service providers” are “[p]roviders that originate 911 traffic, specifically wireline providers; commercial mobile radio service (CMRS) providers, excluding mobile satellite service (MSS) operators to the same extent as set forth in § 9.10(a); covered text providers, as defined in § 9.10(q)(1); interconnected Voice over Internet Protocol (VoIP) providers, including all entities subject to subpart D of this part; and Internet-based Telecommunications Relay Service (TRS) providers that are directly involved with routing 911 traffic, pursuant to subpart E of this part.” 47 CFR § 9.28.

3 “NG911 Delivery Point” means “[a] geographic location, facility, or demarcation point designated by a 911 Authority where an originating service provider shall transmit and deliver 911 traffic in an IP format to ESInets or other NG911 network facilities.” 47 CFR § 9.28.

4 “Session Initiation Protocol” is “[a] signaling protocol used for initiating, maintaining, modifying, and terminating communications sessions between Internet Protocol (IP) devices. SIP enables voice, messaging, video, and other communications services between two or more endpoints on IP networks.” 47 CFR § 9.28.

5 “Commonly accepted standards” means “[t]he technical standards followed by the communications industry for network, device, and Internet Protocol connectivity that— (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.” 47 CFR § 9.28.

6 “Emergency Services Internet Protocol Network (ESInet)” means “an Internet Protocol (IP)-based network that is managed or operated by a 911 Authority or its agents or vendors and that is used for emergency services communications, including Next Generation 911.” 47 CFR § 9.28.

7 “Location Validation Function (LVF)” means “[a] functional element in NG911 Core Services (NGCS) consisting of a server where civic location information is validated against the authoritative Geographic Information System (GIS) database information. A civic address is considered valid if it can be located within the database uniquely, is suitable to provide an accurate route for an emergency call, and is adequate and specific enough to direct responders to the right location.” 47 CFR § 9.28.

8 “Location Information Server (LIS)” means “[a] functional element that provides locations of endpoints. A LIS can provide Location-by-Reference or Location-by-Value, and, if the latter, in geodetic or civic forms. A LIS can be queried by an endpoint for its own location, or by another entity for the location of an endpoint.” 47 CFR § 9.28.

9 The Commission’s rules do not require 911 Authorities to provide PSAP information as part of a valid request.

10 FCC, Privacy Act Statement, https://www.fcc.gov/ecfs/privacy-statement/ECFS_PAS.pdf (last visited July 22, 2024) (ECFS Privacy Act Statement); see also Federal Communications Commission, Privacy Act; System of Records, 88 F.R. 87774 (Dec. 19, 2023).

11 FCC, ECFS Privacy Act Statement.

5