February 2022

Committee Reports

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

• ESIF: Emergency Services Interconnection Forum
  • Issue: 0108
  • Title: Identify and develop adaptations to existing Dispatchable Location (DL) test methodology to better measure handset-based DL performance
  • Statement: Business Need: Although handset-based location today plays a leading role in providing accurate geodetic X/Y/Z location for 9-1-1 calls, dispatchable location remains a highly sought-after goal for public safety. Mobile smart phone devices are increasingly maintaining knowledge of their physical location, including, where appropriate, learning the recurring habits of their owners and frequented locales. This can include the civic addresses of such locales. Such awareness is intended for commercial purposes but can also benefit the reporting of a users position in the event of a 9-1-1 call, particularly a dispatchable location type of position. Current dispatchable location testing methodologies assume memoryless test devices in fresh test locations that have often not been visited for months by those performing the testing. This setup may not provide a realistic reflection of todays real-world use in many common, frequented locations, e.g., at home or in office. Needed are expansion to the existing DL test methodology to encompass a mix of test regimes, including test scenarios, locations, and device types, in which the effects of a variety of normal-use device memory of the locale can be included in the test campaign. Issue Statement: Reexamine the DL test methodology documented in ATIS-0500035, which was developed in the context of NEAD-based DL, to identify its aspects to be updated and adapted to testing device-based DL. Define expanded DL test methodology attributes that include in the testing process capturing the effects of normal-use device memory or awareness of its frequented surroundings. Additionally, refine the concepts of uncertainty as they relate to dispatchable location testing.
  • 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:
  • Status: New Issue

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

• INC: Industry Numbering Committee
  • Issue: 0923
  • Title: Remove and update inaccurate language from TBCOCAG Section 13.1.1 b)
  • Statement: Section 13.1.1 b) of the TBCOCAG has some inaccurate language. Currently Section 13.1.1 b)1) states when the Code Holder submits an ISP Block port and no NPAC notification is required the effective date shall be no less than 9 calendar days. However, an ISP Block Port always requires NPAC notification. Section 13.1.1 b)2) states when a non-Code Holder submits an ISP Block port the effective date shall be no less than 8 business days. ISP Block Port requests may only be submitted by the Code Holder of a non-pooled NPA-NXX and all new ISP Block Port applications have a minimum effective date of 8 business days as NPAC notification is required. This contribution suggests removing Section 13.1.1 b)1) and updating Section 13.1.1 b)2) to reflect the actual process.
  • 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-2022-00004R000.
  • Status: Initial Closure

  • Issue: 0924
  • Title: Add language to the Disconnect sections of the TBCOCAG stating when regulatory authority is provided NANPA/PA shall request iconectiv to disconnect NXD records in BIRRDS
  • Statement: Today when thousands-blocks and/or CO Codes are reclaimed or voluntarily returned and a new block holder/code holder cannot be found, the PA/NANPA sends notification from the appropriate regulatory authority and requests TRA to disconnect the NXD records associated with the thousands-block/CO Code when there is no AOCN of record (EMB1). This action is not captured in the current guidelines, therefore, this issue suggests adding text documenting this step.
  • 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-2022-00006R001.
  • Status: Initial Closure

  • Issue: 0925
  • Title: Update INC Guidelines to allow NANPA to assign the 988 Central Office Code in areas where 10-digit local dialing has been implemented
  • Statement: When 988 was first designated by the FCC as the three-digit abbreviated dialing code to reach the National Suicide Prevention Lifeline, INC added language to the TBCOCAG which restricted the 988 Central Office (CO) code from being made available for assignment in geographic NPAs on a going forward basis. In those NPAs where 988 was already assigned as a CO code and 7-digit local dialing existed, the industry is transitioning to mandatory 10-digit local dialing by July 15, 2022 in order to prevent technical issues in some switches with the use of 988 as an abbreviated dialing code. Mandatory 10-digit local dialing eliminates the issue with some switches being unable to determine whether an originating caller is attempting to dial 988 to reach the NSPL or 988-XXXX to reach a local number. Thus there are no technical reasons that the 988 CO code cannot be made available for assignment in geographic NPAs in the US and its territories where mandatory 10-digit local dialing has already been implemented (Note: More than 110 988 CO codes are already assigned in geographic NPAs in the US and its territories where mandatory 10-digit local dialing has been implemented).
  • 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-2022-00008R000. INC agreed that NANPA shall not make the 988 NXX Codes in the 82 geographic NPAs impacted by the 988 federal mandate available until January 15, 2023, to provide a 6-month buffer between activation of the 988 abbreviated dialing code and assignment of those 988 NXX codes.
  • Status: Initial Closure

  • Issue: 0926
  • Title: Updates to NPA Relief Planning Guidelines on Relief Lives and Other Clarifications
  • Statement: In the current NPA Relief Planning Guidelines, a particular relief alternative must provide only 5 years of relief. That criteria has been in the Guidelines for 20+ years, likely documented at a time when geographic splits were common and frequent. Now that overlays are the most common and preferred method of relief, INC should revisit that criteria to streamline both the development and the deliberation of relief alternatives. Other sections in the Guidelines should be reviewed and updated as well, to provide clarifications and/or additional information.
  • Resolution: INC agreed to update ATIS-0300061, NPA Code Relief Planning and Notification Guidelines, with the updates reflected in INC-2022-00011R001.
  • Status: Initial Closure

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

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0066
  • Title: Voice over Internet Protocol (VoIP) Interconnection Best Practices
  • Statement: There is an industry need for a document that focuses on VoIP interconnection issues. NGIIF should review current documentation for areas that address VoIP and consider how to consolidate this information into a single source.
  • Resolution: NGIIF added a new Section 7.1.3.7 (SIP Option Testing) to ATIS-0300118, NGIIF NGN Reference Document NGN Interconnection, and made additional editorial updates throughout.
  • Status: Initial Closure

  • Issue: 0069
  • Title: Adding Robocall Mitigation Database (RMD) language to the Call Completion Handbook
  • Statement: The FCC has required all voice service providers to certify their SHAKEN/STIR implementation status in the Robocall Mitigation Database (RMD). VSPs that are not appropriately registered should expect calls to be blocked as of September 28, 2021 by other VSPs who they exchange traffic with, causing call failures. This contribution is to add applicable language to the Call Completion Handbook to help VSPs identify RMD related call failures and means by which to correct.
  • Resolution: Language was added to Section 5.5.1 (Use of Call Analytics) of ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook, referencing industry best practices for redress.
  • Status: Initial Closure

  For more information, visit the NGIIF home page or contact Anna Karditzas.

• STEP: Sustainability in Telecom: Energy and Protection Committee
  • Issue: 0203
  • Title: Review of ATIS‐0600005.2017, Acoustic Measurement
  • Statement: Based on the 5-year review of ATIS-0600005.2017, improvements to the document were proposed.
  • Resolution:
  • Status: New Issue

  • Issue: 0204
  • Title: Review of ATIS-0600063, Guidelines for Environmental Testing and Evaluation of Communication Equipment to determine if any updates need to be made to the roadmap
  • Statement: ATIS-0600063 is a reference document that lists applicable tests from other documents based on equipment type and installation location. This document needs to be updated to remove references to documents that have been withdrawn and add references to applicable standards that have been newly issued.
  • Resolution:
  • Status: New Issue

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

• TMOC: Telecom Management and Operations Committee
  • Issue: 0235
  • Title: Revision of ATIS-0300097.2017, Structure for the Identification of Communications Connections for Information Exchange
  • Statement: The contact information within ATIS‐0300097.2017, Structure for the Identification of Communications Connections for Information Exchange needs updating.
  • Resolution:
  • Status: New Issue

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

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

PTSC

• Document Number: ATIS-1000045.2012(S2022)
• Title: ATIS Identity Management: Mechanisms and Procedures Standard
• Type: Revision
• View on ATIS Workspace
• Document Number: ATIS-1000050.2012(S2022)
• Title: Next Generation Network (NGN) Operator Regular Intercept Standard
• Type: Revision
• View on ATIS Workspace
• Document Number: ATIS-1000059.2017(R2022)
• Title: Emergency Telecommunications Service Wireline Access Requirements
• Type: Revision
• View on ATIS Workspace
• Document Number: ATIS-1000102
• Title: Invocation/Revocation of the National Security / Emergency Preparedness (NS/EP) Data Transport Service for the Evolved Packet System
• Type: New
• View on ATIS Workspace

SYNC

• Document Number: ATIS-0900414.2012(S2022)
• Title: Network to Customer Installation Interfaces - Enhanced 911 Analog Voicegrade PSAP Access Using Loop Reverse-Battery Signaling
• Type: Revision
• View on ATIS Workspace

Recent Policy Filings

ATIS

• Date: 2/22/2022
• Description: Comments in response to NIST’s RFI soliciting input on the public and private sector marketplace trends, supply chain risks, legislative, policy, and the future investment needs of eight emerging technology areas.
• View filing