January 2024

Committee Reports

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

• INC: Industry Numbering Committee
  • Issue: 0968
  • Title: Updates to ATIS-0300050 Carrier Identification Code (CIC) Administration Guidelines and forms for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-0300050, Carrier Identification Code (CIC) Assignment Guidelines, the CIC Application Form – Part 1, and the Appendix 1: Annual CIC Report to align with the combined NANP Administration System (NAS): • Update processing times to 7 calendar days • Update form references to new form names • Update Appendix 1: Annual CIC Report with minor changes and for consistency with other guideline forms • Update the CIC Application Form Part 1 to align with other INC forms and streamline information • Update the CIC Administrator Response/Confirmation Part 3 to align with other INC forms • Update the Confirmation of CIC In Service Part 4 to align with other INC forms • Update language associated with Appendix 1: Annual CIC Report to align with language in the p-ANI Guidelines
  • Resolution:
  • Status: New Issue

  • Issue: 0969
  • Title: Updates to ATIS-0300060 9YY NXX Code Assignment Guidelines and forms for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-03000060, 9YY NXX Code Assignment Guidelines, the 9YY NXX Code Application Form – Part 1 to align with the combined NANP Administration System (NAS): •Update processing times to 7 calendar days •Update form references to new form names •Update the 9YY NXX Code Application Form Part 1 to remove Explanation field
  • Resolution:
  • Status: New Issue

  • Issue: 0970
  • Title: Updates to ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines to align with the combined NANP Administration System (NAS): •Update processing times to 7 calendar days •Update form references to new form names
  • Resolution:
  • Status: New Issue

  • Issue: 0971
  • Title: Updates to ATIS-0300089, p-ANI Administration Guidelines for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-0300089, p-ANI Administration Guidelines to align with the combined NANP Administration System (NAS): •Update processing times to 7 calendar days •Update system to NAS and website to nanpa.com
  • Resolution:
  • Status: New Issue

  • Issue: 0972
  • Title: Investigate what can be done to prevent the porting of TNs in previously Assigned/Retained thousands-blocks after the submission of thousands-block disconnect request
  • Statement: NANPA is seeing an increase in the porting of TNs on thousands-block disconnect requests after: 1. The submission of the Part 1, 2. NANPA has run the NPAC report, 3. NANPA has approved the thousands-block disconnect, and 4. The thousands-block has been added back to the available pool. NANPA has seen the following impacts when TNs are ported after a thousands-block disconnect request has been submitted and/or approved: 1. Incorrect data is returned on the NPAC report, 2. Thousands-blocks added to the pool as pristine become contaminated, 3. Thousands-blocks added to the pool as pristine or contaminated become over-contaminated Since NANPA is unaware of the situation until the thousands-block is assigned to another Service Provider, this behavior can cause issues or delays for the new Service Provider and additional work for NANPA. The following sections in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines already indicate SPs responsibilities to port only from assigned TNs or prior to disconnect: • 3.1.5 • 8.2.4 g) • 8.3.4 e) • 11.1.2 b) • 11.1.5 The following sections in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines discuss duplicate assignments: • 7.1.15 • 7.1.16
  • Resolution:
  • Status: New Issue

  • Issue: 0973
  • Title: Investigate what can be done to prevent the porting of TNs in Available/Pending thousands-blocks from new CO Code assignments for LRN or Pool Replenishment
  • Statement: NANPA is seeing the porting of TNs in Available/Pending thousands-blocks from Pooled CO Codes for LRN and Pool Replenishment, where the thousands-blocks were never assigned to an SP. TNs should not ported from available/pending thousands-blocks associated with a new CO Codes for LRN or Pool Replenishment. When TNs are ported from Available/Pending thousands-blocks associated with a new CO Codes for LRN or Pool Replenishment, the pristine thousands-block becomes contaminated.
  • Resolution:
  • Status: New Issue

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

• NRSC: Network Reliability Steering Committee
  • Issue: 0056
  • Title: Review the New Disaster Information Reporting System (DIRS) User Manual (December 2023) and Platform, and Provide Feedback to FCC, if Required
  • Statement: The FCC deployed a new Disaster Information Reporting System (DIRS) platform and User Manual on December 4, 2023, and in an effort to ensure it meets the industry’s needs, NRSC should review them for accuracy, user-friendliness, functionality, readability, etc..
  • Resolution:
  • Status: New Issue

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

• OBF: Ordering and Billing Forum
  • Issue: 3663
  • Title: ASOG: Expansion of Clarification/Notification Request (CNR) Remarks field
  • Statement: There is a business need to expand the CNR Remarks field from the current 225 characters to 450 characters to allow for additional remarks/information being sent to the customer to better explain the reason for the CNR. Resolution: Expanded the CNR Remarks field to 450 alphanumeric characters on Practice 10 (CNR).
  • Resolution:
  • Status: Initial Closure

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0174
  • Title: Revision of ATIS-1000103, Invocation/Revocation of the National Security / Emergency Preparedness (NS/EP) Data Transport Service for the 5G System (5GS)
  • Statement: Current material in ATIS-1000103 is based on 3GPP Release 17 specifications. In 3GPP Release 18, the 3GPP protocol specifications for the N5 interface have been extended to allow the DTS Server to explicitly indicate to the PCF that authorization for the NS/EP Data Transport Service is required in conjunction with procedures used to establish priority AF signaling. This provides a more straightforward and future-proof way in which the DTS Server can explicitly signal that authorization for the NS/EP Data Transport Service is required for this functionality, thereby providing an improved mechanism that may be chosen for 3GPP Release 18 deployments of the Data Transport Service.
  • Resolution:
  • Status: New Issue

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

• WTSC: Wireless Technologies and Systems Committee
  • Issue: 0101
  • Title: Study on Satellite Support for WEA
  • Statement: The FCC has recently expressed an interest in solutions to the problem of allowing WEAs to be received in situations in which the terrestrial cellular infrastructure has been damaged or is otherwise not operating due to a major catastrophic event (e.g., fire, hurricane, earthquake, tsunami). Separately, Alert Originators (AOs) have often expressed concerns about WEAs not reaching devices within an alert area in areas of poor (or no) cellular coverage. These differing needs provide an opportunity for the wireless industry to study WEA via satellite solutions which may assist with solving both issues. There is currently no standardized architecture to allow WEAs to be sent via satellite and received by mobile devices.
  • Resolution:
  • Status: New Issue

  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

AIDC

• Document Number: ATIS-0300078.2023
• Title: Structure for Serialization of Information and Communications Technology (ICT) Network Infrastructure Equipment
• Type: Revision
• View Here

STEP

• Document Number: ATIS-0600063.2023
• Title: Guidelines for Environmental Testing and Evaluation of Communication Equipment
• Type: Revision
• View Here

Recent Policy Filings

NRSC

• Date: 01/17/2024
• Description: Reply Comments in response to FCC NPRM related to the application of the Network Outage Reporting System (NORS)
• View filing