June 2021

Committee Reports

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

• INC: Industry Numbering Committee
  • Issue: 0901
  • Title: Update the NPA Allocation Plan and Assignment Guidelines Part 1 Form
  • Statement: The NANPA contact information needs updating on NPA Allocation Plan and Assignment Guidelines Part 1 form. In addition, while reviewing the form we noticed that the Guideline Sections referenced under 2. NPA Code Request, reference the Guideline Sections regarding the Responsibilities of NANPA rather than the overall section. We suggest updating the Guideline Sections reference to the overall Section (e.g., Specific Geographic NPA Relief Code) in case the person filling out the form needs to reference the definition in the process of completing the form.
  • Resolution: INC agreed to update the Part 1 Form of ATIS-0300055, NPA Allocation Plan and Assignment Guidelines, with the changes contained in INC-2021-00027R001.
  • Status: Final Closure

  • Issue: 0906
  • Title: Updates to the 9YY NXX Code Assignment Guidelines Forms for the combined NAS system
  • Statement: NANPA suggests modifications to the 9YY NXX Code Assignment Guidelines Forms for consistency in format with other INC resource forms for the combined NAS system.
  • Resolution: INC agreed to update the forms for ATIS-0300060, 9YY NXX Code Assignment Guidelines, for the combined NAS with the changes contained in INC-2021-00048R001, -00049R001, and -00050R001. Pending implementation of the combined NAS.
  • Status: Final Closure

  • Issue: 0907
  • Title: Update industry timeframes, petition references, and dialing plan information in the NPA Code Relief Planning & Notification Guidelines
  • Statement: This issue is being submitted for the INC 173 action item: Dana Crandall (Verizon) and Tara Farquhar (NANPA) will bring in an Issue by INC 174 to address the two-month notification timeframe required for a draft relief plan petition for an overlay, as stated in ATIS-0300061, NPA Code Relief Planning & Notification Guidelines. This issue suggests updating relief plan petition or relief petition references to relief plan filing or relief filing, the notification timeframe required for a draft relief plan petition for an overlay to three weeks and adds clarification on dialing plans. In addition, this issue updates business days to calendar days and adds clarification that notification timeframes are calendar days as needed.
  • Resolution: INC agreed to update the forms for ATIS-0300061, NPA Code Relief Planning & Notification Guidelines, with the changes contained in INC-2021-00052R002.
  • Status: Final Closure

  • Issue: 0908
  • Title: Updates to block request references in TBCOCAG
  • Statement: In reviewing the TBCOCAG we identified wording that is inconsistent in 2 sections of the TBCOCAG. Section 5.1.12 and 5.2.13 have different wording related to block requests in the NPAC. The wording in section 5.1.12provides detail on the number of block activations that the NPAC can process per NPAC region.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), with the changes contained in INC-2021-00054R000.
  • Status: Final Closure

  • Issue: 0909
  • Title: Update the TBCOCAG process for voluntary code transfers when establishing an LRN
  • Statement: This issue suggests updating ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Sections 5.3.3 j) 3), 5.4.3 k) 3), 9.2.5, 9.3.5.2, 9.3.4 and 9.2.6.2 to indicate that a Service Providers (SPs) shall first investigate that there are no CO Codes within their inventory, including other OCNs under its control, prior to requesting a CO Code transfer from another SP for the purpose of establishing an LRN. This issue also suggests updating ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Sections 8.2.18 and 8.3.11 to indicate when a Pooled or Non-pooled CO Code has no assigned numbers that a SP may request an Inter-company OCN transfer for LRN purposes. The SP shall certify in Section 1.8 of the Part 1 that the transfer is to Establish an LRN, otherwise NANPA or the PA shall deny the request.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), with the changes contained in INC-2021-00057R001.
  • Status: Final Closure

  • Issue: 0910
  • Title: Update the TBCOCAG to allow a Non-pooled CO Code to be changed to Pooled to accommodate an Intra-company OCN change
  • Statement: This issue suggests updating ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Section 9.3.4 to allow a Non-pooled CO Code to be changed to a Pooled CO Code to accommodate an Intra-company OCN change.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), with the changes contained in INC-2021-00059R001.
  • Status: Final Closure

  • Issue: 0911
  • Title: Update relief planning timeframe in the NPA Code Relief Planning & Notification Guidelines to 30 months for NPAs where an overlay complex already exists, NPA is transitioning or has already transitioned to 10-digit dialing, or when an overlay is the only relief option
  • Statement: In managing the NPA relief process NANPA has found that public opposition to NPA relief in the circumstances noted are not contentious, streamlined petitions have made the process more expeditious, and less time is needed for relief activities. This issue suggests updating language in Sections 4.9 and 5.12 to update the relief planning timeframe to 30 months for NPAs where an overlay complex already exists, where a single NPA is transitioning or has already transitioned to 10-digit dialing, or when an overlay is the only relief option.
  • Resolution: INC agreed not to update ATIS-0300061, NPA Code Relief Planning & Notification Guidelines. INC discussed current relief planning intervals and agreed that no changes were required to the guidelines. Concerns were raised about reducing the relief planning interval in certain situations and then the exhaust date moving in, leaving the industry short on time for implementation. The industry should encourage the state commissions to issue a decision as soon as possible rather than waiting until later.
  • Status: Final Closure

  • Issue: 0912
  • Title: Cut off date for reporting monthly disconnects to RND, and glossary update for RND website
  • Statement: The Reassigned Numbers Database (RND) Guidelines for Service Provider Reporting of Permanently Disconnected Number Data, should be updated to reflect the cutoff date to report monthly disconnect data and still comply with the 15th of the month due date. The Glossary definition of the RND website should be updated to reflect the website which went live on March 22, 2021.
  • Resolution: INC agreed to update ATIS-0300120, Reassigned Number Database (RND) Guidelines for Service Provider Reporting of Permanently Disconnected Number Data, with the changes contained in INC-2021-00063R001.
  • Status: Final Closure

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

• NRSC: Network Reliability Steering Committee
  • Issue: 0052
  • Title: Review and Suggest Revisions to Network Outage Reporting System (NORS) Manual and Glossary
  • Statement: NRSC determined that FCC documentation regarding the Network Outage Reporting System (NORS) required updates. In addition to the inclusion of a Best Practice (BP) developed in response to NRSC Issue 0045, Intra-Company Outage Reporting Consistency (previously OC3 Reporting Consistency), to be added to documentation at the FCCs suggestion, NRSC will review the Manual and Glossary to ensure current reporting requirements are reflected therein.
  • Resolution:
  • Status: New Issue

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

• WTSC: Wireless Technologies and Systems Committee
  • Issue: 0082
  • Title: Refreshing ATIS-0700015, ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination
  • Statement: There are a number of aspects in 0700015 which 1) have not been updated for recent 3GPP developments relating to emergency communication 2) are now incorrect based on developments since the original publication of 0700015 or 3) may be impacted by some of the 5G changes introduced by 3GPP. There is a need to review and update 0700015 to reflect recent related 3GPP and ATIS work as well as regulatory changes such as RTT. Some of the areas to be addressed include (but not limited to): Changing the GTT aspects to RTT. Based on 3GPP CT work on IMS in 5G, determine any impact on US emergency call handling procedures. Review the 5G security specifications and determine any impact on US emergency call handling procedures, especially the increased attention to privacy (e.g., temporary identities). Closer alignment to 3GPP terminology Update on 911 service security at least for compliance with applicable US federal, state, and local cyber-security directives, mandates, policies, and guidelines. This includes but is not limited to: -- Integrity protection -- Confidentiality protection -- Network mutual authentication -- Protection against replay attacks -- Protection against DOS attacks Incorporate impact of S8HR and the equivalent 5G home routing Support for Location-Based Routing NENA i3v3 coordination/alignment impacts
  • Resolution: This issue was resolved with the publication of ATIS-0700015.v005, ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination & ESInet/Legacy Selective Router Termination.
  • Status: Final Closure

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

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(2021-06)
• Title: Intercarrier Call Completion/Call Termination Handbook
• Type: Revision
• View Here

WTSC

• Document Number: ATIS-0700015.v005
• Title: ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS orination & ESInet/Legacy Selective Router Termination
• Type: Revision
• View Here

Recent Policy Filings

WTSC

• Date: 6/4/2021
• Description: Letter in response to FCC request for additional guidance regarding discretionary parameters specified in ATIS WTSC Wireless Emergency Alerts (WEA) standards for enhanced geo-targeting.
• View filing