June 2022

Committee Reports

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

• AIDC: Automatic Identification & Data Capture Committee
  • Issue: 0039
  • Title: Review Product Marking Implementation Guide (ATIS-0300038)
  • Statement: There are many linear labels still in use in 2022 and this hinders how reliable bar code labels are for enhanced operations, supply chain, asset tracking/recording, even some PCNs are impacted by non-2D product labels.
  • Resolution:
  • Status: New Issue

  • Issue: 0040
  • Title: Implementation Guide to Package Labeling (ATIS-0300006)
  • Statement: There is a desire to modify the Product Packaging guidelines in ATIS-0300006, “Implementation Guide to Package Labeling, Issue 6,” to include the use of 2D labels on product packages. 2D labels on the package should be the same symbology that is found on the physical device, this will ensure that the 2D label on the package is correct and can be successfully read by data capturing devices. This would assist with verifying that the 2D encoding is standard and the expected data is found present along with proper formatting.
  • Resolution:
  • Status: New Issue

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

• INC: Industry Numbering Committee
  • Issue: 0928
  • Title: Modify Reporting of the Current Status of NPA Assignments to Semi-Annually
  • Statement: Section 5.9 of the NPA Allocation Plan and Assignment Guidelines states: "Provide a report on the current status of NPA assignments to the INC on a quarterly basis." Historically, it appears NANPA has provided this data to INC in the NANP Resources Report semi-annually. NANPA suggests updating the NPA Allocation Plan and Assignment Guidelines to reflect current process.
  • Resolution: INC agreed to update Clause 5.9 of ATIS-0300055, NPA Allocation Plan and Assignment Guidelines, with the updates reflected in INC-2022-00039R000.
  • Status: Final Closure

  • Issue: 0929
  • Title: Add the General Purpose Code Exhaust Triggers to the NPA Allocation Plan and Assignment Guidelines
  • Statement: At INC 177 NANPA was given an action item to investigate what trigger prompts INC to take action on increasing the number of available NPAs that are currently unassigned. NANPA found the following trigger in the resolution statement of INC Issue 210 Reconsideration of NPA allocation and NPA Guidelines: "As a result of review of the existing NPA supply of spare GPC codes, INC has determined that it is not necessary at this time to make any additional spare GPC codes available. However, if NANPA experiences difficulties in the future in identifying NPAs for reservation as geographic relief NPAs, it will bring the issue back to INC. In addition, NANPA will bring back the issue when the spare GPC level reaches 20 NPA codes." NANPA feels this information should be added to the NPA Allocation Plan and Assignment Guidelines.
  • Resolution: INC agreed to update ATIS-0300055, NPA Allocation Plan and Assignment Guidelines, with the updates reflected in INC-2022-00041R001.
  • Status: Final Closure

  • Issue: 0931
  • Title: Add Part 1B SPID/LRN information to Section 13 Intra Service Provider (ISP) Block Porting of the TBCOCAG
  • Statement: At INC 177 while reviewing an issue related to Section 13 Intra Service Provider (ISP) Block Porting of the TBCOCAG it was noticed that the updates made in Issue 913: Errors due to Override NPAC Validation field functionality were not updated in this section. In addition, other information regarding Part 1B processing in the NPAC is missing. This issue makes updates using the current INC Guideline language.
  • 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-00045R001.
  • Status: Final Closure

  • Issue: 0932
  • Title: Revisit CO Code Reservations
  • Statement: In TBCOCAG Section 6.2, the only stipulation for a CO Code reservation is that a safety valve waiver is needed, and there is no clarification regarding the type of application.
  • Resolution: INC agreed that no changes were needed to the CO Code Reservation section 6.2 of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines.
  • Status: Final Closure

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0161
  • Title: Poison Control Center Call Routing
  • Statement: Legislation enacted in 2019 amended the federal Public Health Service Act to give the U.S. Department of Health and Human Services (HHS) responsibility “to the extent technically and economically feasible, to ensure that communications with the national toll-free number are routed to the appropriate poison control center based on the physical location of the contact rather than the area code of the contact device.” The communications industry should support HHS’s effort to address this important public policy issue. Some calls to the Poison Control Center Hotline toll-free number are routed to the poison control center other than the center serving the state in which the caller is located, because the NPA-NXX information associated with the call and provided by the originating service provider does not correspond to the caller’s location. This is in part due to the mobile and nomadic capabilities of wireless and Voice over IP (VoIP) services that enable a user to originate calls from outside the geographic area associated with the NPA-NXX in the user’s 10-digit NANP telephone number. Today, the Toll Free routing platform, by design and in accordance with direction from HHS, is dependent on the NPA-NXX data provided from other carriers passed in either the JIP, Charge Number, or Calling Party Number in order to route calls based on the caller’s location. Some carriers have mechanisms to approximate physical location, while others may not. The NGIIF Reference Document documents Rules for Populating the JIP. This and other methods should be reviewed to ensure originating carriers are providing accurate location information for both wireline and wireless calls, to the extent technically and economically feasible.
  • Resolution: The PTSC conducted an extensive analysis of the Poison Control Center (PCC) call routing issue and determined that in order to resolve this issue, it would be necessary to either take a more granular approach to call routing (e.g. local call routing rather than interexchange toll-free), similar to how certain N11 calls are handled, or re-engineer how JIP might better represent the location of the calling party., JIP is an available approach that requires no standards changes, but is a legacy parameter originally designed to manage number portability and carrier billing and is not implemented consistently within the industry. Use of an abbreviated dialing code as a potential longer-term solution was considered, however significant changes would need to be made across the existing PCC routing implementation to allow more granular routing. The efforts necessary to implement a new 3-digit code would also divert attention and resources from regulatory compliance mandates like STIR/SHAKEN and implementation of 988. Although no changes to the current ATIS documentation to resolve the location granularity issue have been identified, it was determined that the protocol mechanism to transmit JIP between service providers is working as documented in the standards. The PTSC notes that this issue could potentially be revisited in the future as the FCC considers related issues in the 988 context that may be relevant to PCC call routing as well. This Issue was placed into Initial Closure with no changes to PTSC guidelines.
  • Status: Final Closure

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

• SNAC: SMS/800 Number Administration Committee
  • Issue: 3442
  • Title: Text Enablement Requests for XX99 numbers
  • Statement: Text enablement requests are being received without the company name identified. Instead, the Company Name is being submitted as the Service Registrar and no other information is being provided. RespOrgs need to confirm that the requesting party is the End User Subscriber in the Toll-Free Number Database, which means this information should be required. In addition, if a text enablement request on an XX99 number is rejected, the process for over-riding the rejection should be handled the same as a RespOrg change request on toll-free number with a RespOrg ID = XX99.
  • Resolution:
  • Status: New Issue

  For more information, visit the SNAC 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-0300046
• Title: Recommended Notification Procedures to Industry for Changes in Network Routing Architecture
• Type: New
• View Here

TOPS

• Document Number: ATIS-I-0000090
• Title: 5G Network Assured Supply Chain
• Type: New
• View Here
• Document Number: ATIS-I-0000091
• Title: Deployment and Operational Requirements of 5G Non-Public Networks
• Type: New
• View Here

Recent Policy Filings

SNAC

• Date: 06/28/2022
• Description: Letter to FCC WCB on the Distribution of Toll-Free Numbers (TFNs) Made Unavailable at the Direction of the Commission. Ex Parte Notification — WC Docket No. 17-192, CC Docket No. 95-155.
• View filing

WTSC

• Date: 06/22/2022
• Description: Comments in response to FCC FNRPM on proposed data collection and reporting requirements for WEA.
• View filing