March 2023

Committee Reports

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

• ESIF: Emergency Services Interconnection Forum
  • Issue: 0113
  • Title: Best Practices for Location Based Routing Implementations
  • Statement: Practices for Location Based Routing Implementations Statement: As the adoption of Location Based Routing (LBR) becomes more relevant within the industry with more and more CMRS providers enabling LBR within networks, and PSAPs/ECCs begin implementing LBR for routing emergency calls based on device location within their jurisdiction boundaries, the need for documented best practices has been apparent. The recent Notice of Proposed Ruling Making (NPRM) by the Commission reflects the need within the industry to understand how networks route using LBR, how PSAP may benefit from its adoption, and how the industry can work together to reduce transfers to better ensure emergency call routing the appropriate PSAP/ECC. This issue proposes to document the best practice for LBR enablement and implementation. Other enhancements may be needed to maintain functional alignment with the NENA i3 standard. Enhancements to 3GPP IMS architecture will also be considered.
  • Resolution:
  • Status: New Issue

  • Issue: 0109
  • Title: Update/enhance ATIS-0500036, ATIS Standard for IMS-based Next Generation Emergency Services Network Interconnection
  • Statement: ATIS-0500036, ATIS Standard for IMS-based Next Generation Emergency Services Network Interconnection, describes the interconnection of North American IMS-based NG9-1-1 emergency services networks with other legacy and Next Generation Emergency Services Networks deployed in North America to support the delivery of initial and transferred emergency calls. ATIS-0500036 is viewed as incremental to ATIS-0500032, which applies IP Multimedia Subsystem (IMS) architecture concepts to Next Generation 9-1-1 (NG9-1-1) networks. Recent updates to ATIS-0500032 include procedures that address the application of information spoofing mitigation techniques to 9-1-1 calls and callback calls that are routed via an IMS-based NG9-1-1 Emergency Services Network. Further study is needed to assess the impacts of applying information spoofing mitigation techniques to emergency calls that are routed or transferred between IMS-based NG9-1-1 Emergency Services Networks and other Emergency Services Networks. This Issue proposes follow on work to ESIF Issue 82, IMS-based Next Generation Emergency Services Network Interconnection, to address information spoofing mitigation impacts on emergency calls that are routed or transferred between IMS-based NG9-1-1 Emergency Services Networks or between IMS-based NG9-1-1 Emergency Services Networks and other legacy or NG9-1-1 Emergency Services Networks.
  • Resolution: This Issue was resolved with the publication of ATIS-0500036.v002, ATIS Standard for IMS-based Next Generation Emergency Services Network Interconnection.
  • Status: Final Closure

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

• INC: Industry Numbering Committee
  • Issue: 942
  • Title: Review Facilities Readiness sections of the 9YY NXX Assignment Guidelines and Non-Geographic 5XX-NXX Assignment Guidelines and remove any forms of facilities readiness that are not valid
  • Statement: During discussion of INC Issue 939, Revisit Use of Pre-Planning Checklist for Non-Geographic Resources INC determined a review of ATIS-0300052 Non-Geographic 5XX-NXX Assignment Guidelines Sections 4.3.2 Facilities Readiness and ATIS-03000060 9YY NXX Code Assignment Guidelines Section 5.12.2 Facilities Readiness was needed to ensure that all forms of proof of facilities readiness listed are valid for the resource type.
  • Resolution: INC agreed to update ATIS-0300060, 9YY NXX Code Assignment Guidelines, and ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines, with the updates reflected in INC-2023-00005R000 and INC-2023-00006R000 respectively.
  • Status: Final Closure

  • Issue: 944
  • Title: Add language to encourage SPs needing to establish an LRN to investigate a CO Code transfer prior to applying for a new CO Code for LRN to the TBCOCAG
  • Statement: In INC Issue 930, Improvements to Voluntary Code Transfer Process for LRN Purposes, INC added language to encourage SPs needing to establish LRNs to investigate a CO Code transfer prior to applying for a new CO Code for LRN. However, Service Providers seeking to request new CO Codes for LRN purposes may not know to look for the language in Section 9 Modification to Numbering Resources of the ATIS-0300119 Thousands-Block (NPA-NXX-X) and Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG). Therefore, NANPA suggests adding language to encourage SPs needing to establish an LRN to investigate a CO Code transfer prior to applying for a new CO Code for LRN to Section 4 Pre-Ordering Responsibilities of the TBCOCAG. In addition, NANPA is suggesting updates to the LRN language in Sections 5.3.3, 5.4.3, 5.5.3, 5.6.3, 9.2.6.2, and 9.3.5.2.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2023-00011R001.
  • Status: Final Closure

  • Issue: 945
  • Title: Add language outlining the steps when transferring a CO Code for LRN purposes to TBCOCAG Section 9 Modification to Numbering Resources
  • Statement: In INC Issue 930, Improvements to Voluntary Code Transfer Process for LRN Purposes, INC added language to encourage SPs needing to establish LRNs to investigate a CO Code transfer prior to applying to open a new CO Code for LRN. In order to process a CO Code transfer, the relinquishing SP (in the case of a Non-Pooled Code changing to Pooled) and the receiving SP need to follow certain steps during the application process. These steps are not outlined in ATIS-0300119 Thousands-Block (NPA-NXX-X) and Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG). Therefore, NANPA suggests adding language to Section 9.2.6 Pooled CO Code Transfer Process and Section 9.3.5 Non-Pooled CO Code Transfer Process of the TBCOCAG outlining the steps when transferring a CO Code for LRN purposes.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2023-00013R000.
  • Status: Final Closure

  • Issue: 946
  • Title: Update Jeopardy Procedures to allow NANPA to review jeopardy procedures at the implementation meeting and rescind jeopardy when it is no longer needed
  • Statement: Currently there is no way for NANPA and the industry to review and adjust the final jeopardy procedures or for NANPA to rescind jeopardy when it is no longer needed and NPA relief has not been implemented. Therefore, NANPA suggests updating Section 15 Central Office (CO) Code (NPA-NXX) Conservation and Jeopardy Procedures of ATIS-0300119 Thousands-Block (NPA-NXX-X) and Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) to allow for NANPA and the industry to review final jeopardy procedures and allow NANPA to rescind jeopardy when it is no longer needed.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2023-00018R001.
  • Status: Final Closure

  For more information, visit the INC home page or contact .

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

ESIF

• Document Number: ATIS-0500036.v002
• Title: ATIS Standard for IMS-based Next Generation Emergency Services Network Interconnection
• Type: Revision
• View Here

INC

• Document Number: ATIS-0300060
• Title: 9YY NXX Code Assignment Guidelines
• Type: Revision
• View Here
• Document Number: ATIS-0300052
• Title: Non-Geographic 5XX-NXX Code Assignment Guidelines
• Type: Revision
• View Here
• Document Number: ATIS-0300119
• Title: Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines
• Type: Revision
• View Here

NRSC

• Document Number: ATIS-0100071
• Title: Network Reliability Steering Committee 2021-2022 Operation Report
• Type: New
• View Here

OBF

• Document Number: ATIS-0404110-0042
• Title: Unified Ordering Model - Access Service Request (UOM-ASR) Volume I
• Type: Revision
• View Here
• Document Number: ATIS-0410002-0042
• Title: Unified Ordering Model (UOM) Volume II – Analysis - For Access Service Ordering Guidelines (ASOG)
• Type: Revision
• View Here
• Document Number: ATIS-0410003-0042
• Title: Unified Ordering Model (UOM) - Volume III – Design - For Access Service Ordering Guidelines (ASOG)
• Type: Revision
• View Here
• Document Number: ATIS-0404000-0067-ATIS-0404028-0067
• Title: Access Service Request (ASR) Guidelines Version 67
• Type: Revision
• View Here

Recent Policy Filings

SNAC

• Date: 03/29/2023
• Description: Ex parte notification for ATIS SNAC meeting with FCC regarding distribution of toll-free numbers made Unavailable at the FCC’s direction
• View filing