November 2024

Committee Reports

Click on a committee name below to display this month's issues.

• ESIF: Emergency Services Interconnection Forum
  • Issue: 0114
  • Title: Develop checklist forms and guidelines documentation for use by Public Safety Answering Points (PSAPs) and 9-1-1 authorities to request services as described in the FCC NPRM on NG9-1-1 Connectivity
  • Statement: Business Need: The FCC Notice of Proposed Rulemaking (NPRM) (PS Docket No. 21-479) on Facilitating Implementation of Next Generation 911 Services (NG911) outlines proposed rules and timelines to support the transition to IP-based networks and the development of capabilities to support NG9 1 1 elements and functions. Specifically, the NRPM proposes to require that wireline, interconnected Voice over Internet Protocol (VoIP), and Internet-based Telecommunications Relay Service (TRS) providers complete all translation and routing to deliver 9-1-1 calls, including associated location information, in the requested IP-based format . . . to destination point(s) in those networks designated by a 911 authority, including to a public safety answering point (PSAP), designated statewide default answering point, local emergency authority, ESInet, or other point(s) designated by 911 authorities that allow emergency calls to be answered, upon request of 911 authorities who have certified the capability to accept IP-based 911 communications. Given the provisions of the NPRM described above, there is a need for documented processes that provide the necessary prerequisites that must be met before a request is made, and the steps involved in making the request for NG9 1 1 connectivity services from an Originating Service Provider (OSP) toward a PSAP that has connectivity to an Emergency Services IP Network (ESInet) that supports Next Generation 9-1-1 Core Services (NGCS). This documentation would be in the form of an implementation/readiness checklist and guidelines for PSAPs to expedite requests and reduce confusion. Issue Statement: To support NG9-1-1 transition, create checklists and guideline documentation for PSAPs/9-1-1 Authorities to request NG9-1-1 connectivity from OSPs, including wireline, Commercial Mobile Radio Service (CMRS), interconnected VoIP, Internet-based TRS providers and covered text providers.
  • Resolution: Publication of 9-1-1 Authority Readiness Guidelines for NG9-1-1 Connectivity
  • Status: Initial Closure

  • Issue: 0119
  • Title: Rich Communications Services (RCS) for Next Generation 911 Services (NG911) Texting
  • Statement: Emergency services in the United States require a solution to originate NG9-1-1 commonly accepted standards conformant methods for persons to request help by 9-1-1 via text. Current methods to make an emergency request in the United States via text rely on interim J-STD-110.v002, Joint ATIS/TIA native SMS/MMS text to 9-1-1 requirements and architecture specification release 2 SMS/MMS technology. With the advent and increased adoption of Rich Communications Services (RCS), new specifications and solutions need to accommodate these messaging capabilities that do not yet exist for delivery to Next Generation Core Services (NGCS) served networks. There is regulatory pressure for United States carriers to develop an origination method to deliver text-to-9-1-1 emergency calls in a commonly accepted standards format natively to IP-based NG9-1-1 ESInets/NGCS in order to meet emerging regulatory requirements.
  • Resolution:
  • Status: New Issue

  For more information, visit the ESIF home page or contact Drew Greco.

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0073
  • Title: Update ATIS-0300116(2024-07), Interoperability Standards between Next Generation Networks (NGN) for Signature-based Handling of Asserted Information Using Tokens (SHAKEN) (Revision 2)
  • Statement: ATIS-0300116(2024-07) contains a few inaccuracies (or dated information). Additionally, other editorial changes are being suggested for revision.
  • Resolution: ATIS-0300116(2024-07) was updated to correct inaccuracies and provide updated information.
  • Status: Initial Closure

  For more information, visit the NGIIF home page or contact Mignot Asefa.

Definitions

• New Issue: Business, operational, or technical needs that a committee has reached consensus to address.
• Issue in Initial Closure: Issues for which a committee has reached consensus on a proposed resolution. The industry has a 21 calendar day period to review and comment on the consensus resolution developed by the committee. The committee's consensus resolution concludes its work on an issue unless new or substantive information is brought forth. During the 21 day review period, comments on a consensus resolution may be provided to the committee contact and committee leaders.
• Issue in Initial Pending: Issues previously in Initial Closure for which new and substantive information impacting the consensus resolution has been received. An issue may also be in Initial Pending if output that may impact the consensus resolution is expected from another industry group, regulatory body or similar organization.
• Issue in Final Closure: Issues for which work is completed and the resolution accepted by the industry.

Recently Approved ATIS Standards

No new Standards approved this month.