August 2022

Committee Reports

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

• INC: Industry Numbering Committee
  • Issue: 0934
  • Title: Review and possibly update ATIS-0300071 & ATIS-0300072, NANP Expansion Plan and Reference Document
  • Statement: The NANP expansion plan proposal and reference document were released in 2000. The report indicates the INC will review periodically for updates required due to technological and regulatory changes. The INC has not reviewed the plan proposal or reference document in recent years.
  • Resolution:
  • Status: New Issue

  • Issue: 0935
  • Title: Modifications to ATIS-0300050 Carrier Identification Code (CIC) Assignment Guidelines Reports
  • Statement: For consistency and to enhance processing of ATIS-0300050 Carrier Identification Code (CIC) Assignment Guidelines reports, NANPA suggests the following updates to reports:
    - update titles for consistency and to remove “CIC Reports“ from the title
    - ensure sample reports and actual reports are consistent
    - require all reports to be in Excel format
    - consider making ACNA required on reports
    Changes made with this issue will impact INC Issue 903 which is in Initial Pending Status awaiting the implementation of the combined NANP Administration System (NAS). In order to avoid complications of too many issues changing the same document/forms, NANPA will bring in an issue to make the necessary changes to INC Issue 903 and ATIS-0300050 Carrier Identification Code (CIC) Assignment Guidelines closer to the implementation date of CNAS in case additional updates are identified.
  • Resolution:
  • Status: New Issue

  • Issue: 0930
  • Title: Improvements to Voluntary Code Transfer Process for LRN Purposes
  • Statement: Section 9.2.6.2 of the TBCOCAG outlines the process for voluntary code transfers for LRN purposes, and identifies the factors to consider when investigating the feasibility of such a transfer. Most often it seems that the NANPA or the state commission is contacting a current code holder(s) about a voluntary code transfer once an application for a new code for LRN purposes has already been submitted. This reactive approach places pressure on the NANPA, the state commissions, and the current code holder(s) to act quickly while an application is sitting in queue. Ideally, voluntary code transfer inquiries should be initiated by the SP seeking to establish an LRN.
  • 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-00053R001.
  • Status: Initial Closure

  • Issue: 0933
  • Title: Changes to Non-Geographic 5XX-NXX Code Assignment Guidelines
  • Statement: Due to recent discussion, clarification needs to be added to the use of non-geographic NPA NXXs to ensure they are not traversed on the PSTN network and remain “non-dialable”.
  • Resolution: INC agreed to update ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines, with the updates reflected in INC-2022-00051R001.
  • Status: Initial Closure

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

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0071
  • Title: Amendment to Clause 6.3 of the Call Completion Handbook
  • Statement: Clarification in Section 6.3 to provide additional information for identification of all service providers in the call path of a regulatory request for call completion investigation.
  • Resolution: NGIIF updated Clause 6.3 of ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook, to clarify responsibility for responding to regulatory inquiries associated with call completion issues.
  • Status: Final Closure

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

• NRSC: Network Reliability Steering Committee
  • Issue: 0043
  • Title: Determining Best Counts for NG 9-1-1 Outage Reporting
  • Statement: Throughout the United States 911 services are migrating from Enhanced 911 (E911) to Next Generation 911 (NG911) utilizing Emergency Services IP networks (ESInet). In an ESInet environment, telephone number counts will not be available for FCC mandated 47 CFR 4.7 outage reporting. The current FCC rules for reporting service outages require a count of telephone numbers (TN count) to determine the impact of a service interruption. The ability to create reports from TN counts will no longer be available.
  • Resolution: NRSC reviewed U.S. census data and other alternatives to ALI TN counts for determining when NG 911 outages have reached a reportable threshold. NRSC recommended that the FCC modify Sections 4.7 and 4.9 of its rules by: (1) encouraging PSAPs or 911 Authorities to furnish all covered 911 providers (i3 and legacy) with data regarding population counts served by the PSAPs or 911 Authorities; and (2) requiring all covered 911 service providers (i3 and legacy) to use census or population data derived from other sources instead of telephone number counts to determine user minutes threshold criteria. It was noted that Originating Service Providers could continue to use subscriber counts to determine potential outage impacts. NRSC included these recommendations in NRSC-REG-2022-00060R000, FCC Petition for Rulemaking to Modify Part 4 Rules (including suggestions for Issues 0043, 0053, 0054), filed on August 18, 2022.
  • Status: Initial Closure

  • Issue: 0053
  • Title: Request for Change to Telecommunications Service Priority (TSP) 2 Outage Reporting Threshold
  • Statement: Following the resolution of Issue 0044 (FCC Request NRSC to Further Investigate TSP Rule Change), NRSC proposed the FCC change the reporting threshold for TSP 1 and TSP 2 to four hours (from 30 minutes). This change would result in an estimated 40% reduction in reports, as well as reducing the number of withdrawn reports by approximately 60%. In November 2021, FCC staff noted that this proposal was under review, and indicated the FCC was more receptive to changes to TSP 2 reporting thresholds. FCC staff also requested that NRSC formally file a request for any changes, in order to ensure appropriate transparency and equitable access for the proceeding.
  • Resolution: NRSC recommended the FCC modify Section 4.9 to address overreporting of outages affecting entities enrolled as TSP 2 by extending the minimum duration of reportable outages affecting TSP 2 from 30 minutes to four (4) hours. A change in the TSP reporting threshold from the current 30-minute reporting threshold to a four-hour reporting threshold would significantly reduce the number of withdrawn NORS reports. An analysis of outage data by ATIS NTSC indicates that a change in the TSP reporting threshold from the current 30-minute duration threshold to a four-hour duration threshold would reduce the number of withdrawn reports by approximately 41.6% and final reports by approximately 20.9% in a study of NORS outage data. NRSC included these recommendations in NRSC-REG-2022-00060R000, FCC Petition for Rulemaking to Modify Part 4 Rules (including suggestions for Issues 0043, 0053, 0054), filed on August 18, 2022.
  • Status: Initial Closure

  • Issue: 0054
  • Title: Request for Change to Wireless Outage Reporting Threshold
  • Statement: In concluding NRSC Issue 0046, Impact of Rule Changes to Wireless Reporting, NRSC reviewed member wireless outage report data and confirmed that the increase was due to the rule change rather than a change in wireless network reliability. After examining a duration-based de minimis, a cell site-based de minimis, and a change to how the Potential User Minutes Affected (PUMA) threshold, NRSC proposed a dual site-based de minimis (5 sites for Rural Service Areas, 15 sites for Metropolitan Service Areas) to reduce the volume of less useful reports. This proposed solution (NRSC-2020-00115R010) was presented to the FCC on January 13, 2021. In November 2021, FCC staff indicated that they were considering this proposal, but were not particularly receptive to it. It was also suggested that if NRSC would like to pursue this, they should consider a formal petition for rule change with the FCC asking for a change in the reporting threshold.
  • Resolution: NRSC recommended changes to Section 4.9(e)(2) of the FCCs rules to prevent the overreporting of wireless events that do not have any impact on consumers ability to use 911 services or meet the existing rules definition of outage. Establishing a de minimis exception for events that affect four (4) or fewer macro cell sites located in Rural Service Areas or 14 or fewer macro cell sites located in Metropolitan Service Areas would result in outage reporting data that more accurately reflects the true impact on wireless services, while also decreasing the number of low-impact or no-impact wireless NORS outage reports. NRSC included these recommendations in NRSC-REG-2022-00060R000, FCC Petition for Rulemaking to Modify Part 4 Rules (including suggestions for Issues 0043, 0053, 0054), filed on August 18, 2022.
  • Status: Initial Closure

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

• OBF: Ordering and Billing Forum
  • Issue: 3661
  • Title: Modify Quantity (QTY) field on Combo Order to allow for 2 Ethernet Virtual Connections (EVCs)
  • Statement: There is a business need to expand Combo orders to allow 2 EVCs to be ordered in conjunction with the UNI.
  • Resolution:
  • Status: New Issue

  • Issue: 3662
  • Title: Access Service Ordering Guidelines (ASOG): New Fields: Site Survey Indicators
  • Statement: There is a business need for the customer to provide a site walk date via the ASR. It is sometimes hard to reach the end user for a site walk thus potentially delaying the provisioning and installation of service.
  • Resolution: Added the SSDI (PRILOC) and SSDI (SECLOC) fields supporting the Site Survey request to practice 001 (ASR).
  • Status: Final Closure

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0159
  • Title: Invocation/Revocation of NS/EP Data Transport Services for the 5GS
  • Statement: The proliferation of advanced data communications introduces new opportunities and challenges for National Security / Emergency Preparedness (NS/EP) communications. Expanded data capabilities offer new opportunities that can enhance the ability for Service Users to carry out their NS/EP mission. At the same time, high data traffic volumes place significant demands upon Service Provider’s networks and can hamper their ability to support the offered traffic load when these networks are impaired due to congestion and/or damage from natural disasters. Support for the NS/EP Data Transport Service in the 5G System (5GS) is intended to address these needs.
  • Resolution: This Issue was resolved with the publication of ATIS-1000103, Invocation/Revocation of the National Security / Emergency Preparedness (NS/EP) Data Transport Service for the 5G System (5GS).
  • Status: Final Closure

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

• 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: This issue was resolved with the publication of ATIS‐0300097.2022, Structure for the Identification of Communications Connections for Information Exchange.
  • Status: Final Closure

  For more information, visit the TMOC 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

NGIIF

• Document Number: ATIS-0300106(2022-08)
• Title: Intercarrier Call Completion/Call Termination Handbook
• Type: Revision
• View Here

PTSC

• Document Number: ATIS-1000074.v003
• Title: Signature-based Handling of Asserted information using toKENs (SHAKEN)
• Type: Revision
• View Here
• Document Number: ATIS-1000095.v002
• Title: Extending STIR/SHAKEN over TDM
• Type: Revision
• View Here
• Document Number: ATIS-1000099
• Title: Robocall Call Blocking Notification
• Type: New
• View Here

TMOC

• Document Number: ATIS-0300097.2022
• Title: Structure for the Identification of Communications Connections for Information Exchange
• Type: Revision
• View Here

WTSC

• Document Number: ATIS-0700041.v002
• Title: Wireless Emergency Alerts (WEA) 3.0: Device-Based Geo-Fencing (DBGF)
• Type: Revision
• View Here

Recent Policy Filings

NRSC

• Date: 08/15/2022
• Description: ATIS NRSC Input to CSCC regarding the continuity of the economy.
• View filing
• Date: 08/18/2022
• Description: Petition for Rulemaking proposing changes to the FCC’s Part 4 rules to address issues associated with the reporting of NG911, wireless and TSP outages.
• View filing
• Date: 08/24/2022
• Description: Comments in response to FCC Public Notice seeking input on proposing training materials on use of and access to NORS and DIRS data.
• View filing