The ATIS ANS Report includes newly proposed Standards, Standards that have been proposed for letter ballot, and Standards that have been recently published.
The standardization process is governed by the ATIS Operating Procedures, which have been accredited by the American National Standards Institute (ANSI). ATIS strives to maintain diverse participation among industry segments (Consumer, General Interest, or Producer). In particular, ATIS is seeking participation from specific interest categories for the following committees:
- NRSC, PTSC, and WTSC-producers and general interest
- STEP and SYNC-users and general interest
Producers-An entity that produces or supplies communications equipment or infrastructure for the provision of communications services. Examples include various types of testing, monitoring, routing, and central office equipment manufacturers, software developers, etc.
Users-An entity that uses communications equipment or infrastructure and provides services to an end user. Examples include incumbent local exchange carriers (ILECs), competitive local exchange carriers (CLECs), interexchange carriers (IXCs), wireless service providers, etc.
General Interest-An entity that is neither Producers nor Users. This category includes, but is not limited to, regulatory agencies (state and federal), researchers, other organizations and associations, and educators.
If your organization is affected by the work in ATIS’ Committees or Forums, and you are interested in engaging as a member of our consensus bodies for the development of standards, contact Rich Moran, ATIS Membership Director to apply for membership.
A full catalog of ATIS’ publications can be found here.
Committee Reports
Click on a committee name below to display this month's issues.
-
ESIF: Emergency Services Interconnection Forum
- Issue: 0114
- Title: Develop checklist forms and guidelines documentation for use by Public Safety Answering Points (PSAPs) and 9-1-1 authorities to request services as described in the FCC NPRM on NG9-1-1 Connectivity
- Statement: Business Need:
The FCC Notice of Proposed Rulemaking (NPRM) (PS Docket No. 21-479) on Facilitating Implementation of Next Generation 911 Services (NG911) outlines proposed rules and timelines to support the transition to IP-based networks and the development of capabilities to support NG9 1 1 elements and functions. Specifically, the NRPM proposes to require that wireline, interconnected Voice over Internet Protocol (VoIP), and Internet-based Telecommunications Relay Service (TRS) providers complete all translation and routing to deliver 9-1-1 calls, including associated location information, in the requested IP-based format . . . to destination point(s) in those networks designated by a 911 authority, including to a public safety answering point (PSAP), designated statewide default answering point, local emergency authority, ESInet, or other point(s) designated by 911 authorities that allow emergency calls to be answered, upon request of 911 authorities who have certified the capability to accept IP-based 911 communications.
Given the provisions of the NPRM described above, there is a need for documented processes that provide the necessary prerequisites that must be met before a request is made, and the steps involved in making the request for NG9 1 1 connectivity services from an Originating Service Provider (OSP) toward a PSAP that has connectivity to an Emergency Services IP Network (ESInet) that supports Next Generation 9-1-1 Core Services (NGCS). This documentation would be in the form of an implementation/readiness checklist and guidelines for PSAPs to expedite requests and reduce confusion.
Issue Statement:
To support NG9-1-1 transition, create checklists and guideline documentation for PSAPs/9-1-1 Authorities to request NG9-1-1 connectivity from OSPs, including wireline, Commercial Mobile Radio Service (CMRS), interconnected VoIP, Internet-based TRS providers and covered text providers.
- Resolution: Publication of 9-1-1 Authority Readiness Guidelines for NG9-1-1 Connectivity.
- Status: Final Closure
- Issue: 0115
- Title: Update ATIS-0500036, ATIS Standard for IP Multimedia Subsystem (IMS)-based Next Generation Emergency Services Network Interconnection, to maintain functional alignment with NENA i3 standard.
- Statement: ATIS-0500036, ATIS Standard for IMS-based Next Generation Emergency Services Network Interconnection, defines the inter-Emergency Services Network interactions for initial emergency calls that are required to be routed to another Emergency Service Network, and emergency calls that are transferred (bridged) between Emergency Services Networks. This Issue proposes updates to ATIS-0500036 to maintain functional alignment with the NENA i3 standard and the latest update of ATIS-0500032, ATIS Standard for Implementation of an IMS-based NG9-1-1 Service Architecture. This includes topics such as the authentication of caller identity and Resource-Priority Header information associated emergency calls that are transferred between Emergency Services Networks. When an NG9-1-1 PSAP initiates an emergency call transfer, the Conferencing AS will initiate a call toward the transfer-to PSAP that includes Identity headers signed using credentials that are traceable to the PSAP Credentialing Agency (PCA). Enhancements are needed to ATIS-0500036 to allow an upstream IMS-based NG9-1-1 Emergency Services Networks to sign information associated with transferred emergency calls using PCA-traceable certificates, and downstream IMS-based NG9-1-1 Emergency Services Networks to verify the signed information before delivering the call to the transfer-to PSAP. Other enhancements may be needed to maintain functional alignment with the NENA i3 standard.
- Resolution: Publication of ATIS-0500036.v003, ATIS Standard for IMS-based Next Generation Emergency Services Network Interconnection.
- Status: Final Closure
For more information, visit the ESIF home page or contact Drew Greco.
-
INC: Industry Numbering Committee
- Issue: 0954
- Title: Update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) Section 4.6 Operating Company Number (OCN) with NECA provided language
- Statement: iconectiv TRA is receiving multiple inquiries regarding numbering resource assignments published in the LERG™ Routing Guide and/or TPM™ Data Source with inaccurate “type of service”.
There are two scenarios that were discovered while researching these inquiries:
1. An SP obtained numbering resources using its CLEC OCN. The SP also has a Mobile line of business. Although the CO Code was obtained with the CLEC OCN, the CO Code was being used by the SPs Mobile line of business.
2. An SP only has a CLEC OCN even though it has a Mobile line of business. All of its numbering resources are being obtained under the CLEC OCN.
This results in Mobile numbering resources (CO Codes and Thousands Blocks) being identified as landline (End Office) and not being correctly identified as Mobile.
The following language has been provided by NECA and is in the NECA North American Company Code Assignment Procedures Section 2.1 “Structure/Format”:
“Company Codes are assigned for each type of service a company provides. Separate and distinct codes are required for Incumbent Local Exchange Carriers (ILECs), facilities-based Competitive Local Exchange Carriers (CLECs), Unbundled Local Exchange Carriers (ULECs), Local Exchange Resellers (LRSLs), Competitive Access Providers (CAPs), Interexchange Carriers (ICs), IP Enabled Service (IPES) providers, Ethernet Exchange (ETHX) providers, Wireless Carriers (WIRE), Wireless Reseller (WRSL), Personal Communications Service (PCS) provider and Personal Communication Service Resellers (PCSR). Companies offering more than one type of service are required to obtain multiple codes, regardless if a separate legal entity is created.”
- Resolution: INC agreed to update the ATIS-0300119 Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) Section 4.6 Operating Company Number (OCN) with text from NECA procedures as reflected in INC-2024-00135R000. This aligns with the resolution of CIGRR Issue C300 - NXD inaccurate entry of COC Type and/or NXX Type based on Company Code Category.
- Status: Final Closure
- 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: Following INC’s investigation of preventing the porting of TNs previously Assigned/Retained thousands-blocks after the submission of thousands-block disconnect request, and additional data provided at the Number Portability Industry Forum (NPIF) by the Local Number Portability Administrator (LNPA), INC concluded that there is no INC action to be taken.
- Status: Final Closure
- Issue: 0984
- Title: Remove language in Section 11.2.12.2.2 of the ATIS-0300119, Thousands Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) allowing SPs with only ported TNs to become the new CO Code holder when there are block holders in the impacted CO Code
- Statement: Section 11.2.12.2.2 subsections g-l allow for Service Providers (SPs) with only ported TNs to become the new CO Code Holder if no block holder responds to NANPA’s request for a new Code Holder. Since a SP becoming a Code Holder must fulfill code holder responsibilities it falls on the block holders to submit the Part 1 to NANPA. A SP may not be able to obtain a block in the resource and therefore cannot fulfill the applicable responsibilities.
- Resolution: INC agreed to update ATIS-0300119, Thousands Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines with the changes reflected in INC-2024-00115R001 and INC-2024-00138R001. It should be noted that INC decided to discontinue sending the email to the company with the most ports but still send to all companies with ports, in an effort to streamline the reassignment process.
- Status: Final Closure
- Issue: 0989
- Title: Remove Explanation field from ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines Part 1 Form
- Statement: There is no reference to entering information in the Explanation field in ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines Part 1 Form. Since there is a Comments field, and this aligns with other forms, NANPA removed the Explanation field on the Part 1 form since having both fields seemed unnecessary, and documentation is required when the modification type of OCN: Inter-company is selected.
- Resolution: INC agreed to update ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines to remove the Explanation Field in the Part 1 Form as reflected in INC-2024-00128R000.
- Status: Final Closure
- Issue: 0990
- Title: Update ATIS-0300089, p-ANI Guidelines Section 4.3 to indicate NANPA has up to five business days to process a registration to align with combined NAS
- Statement: When making updates to the p-ANI Guidelines for the combined NAS, NANPA updated the registration processing time from 5 business days to 7 calendar days in error. To align with the system requirements, Section 4.3 of ATIS-0300089, p-ANI Guidelines needs to be changed back to five (5) business days.
- Resolution: INC agreed to update ATIS-0300089, p-ANI Guidelines Section 4.3 to indicate NANPA has up to five business days to process a registration to align with NAS as reflected in INC-2024-00130R000.
- Status: Final Closure
- Issue: 0991
- Title: Minor updates to ATIS-0300050, Carrier Identification Code (CIC) Administration Guidelines Part 1 and Part 3 Forms for consistency
- Statement: When making final reviews of the ATIS-0300050, Carrier Identification Code (CIC) Administration Guidelines Part 1 and Part 3 Forms NANPA noted some inconsistencies from other INC forms. This issue suggests updating the “Signature of Authorized Representative of the CIC Entity” to “Signature of Applicant” on the Part 1 and “CIC Administrator” to “Administrator Contact Name” on the Part 3 to align with other INC forms.
- Resolution: INC agreed to update ATIS-0300050, Carrier Identification Code (CIC) Administration Guidelines Part 1 “Signature of Authorized Representative of the CIC Entity” to “Signature of Applicant” and Part 3 “CIC Administrator” to “Administrator Contact Name” as reflected in INC-2024-00140R000 and INC-2024-00141R000.
- Status: Final Closure
For more information, visit the INC home page or contact .
-
WTSC: Wireless Technologies and Systems Committee
- Issue: 0109
- Title: Revision of ATIS-0700044
- Statement: There is a need to update ATIS-0700044 Study of Emergency Services and National Security Emergency Preparedness Next Generation Network Priority Service (NS/EP NGN-PS) Coexistence on LTE Access Networks in the following areas:
• Update to reflect changes to applicable FCC regulations for:
o FCC Title 47 Part 64 Appendix B on NSEP preemption, and
o FCC reorganized 911 regulations.
• Update the security section as it is not current, and
• Other editorial and technical corrections.
- 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
ESIF
- Document Number: ATIS-0500036.v003
- Title: ATIS Standard for IMS-based Next Generation Emergency Services Network Interconnection
- Type: Revision
- View Here
- Document Number: ATIS-0500048
- Title: 9-1-1 Authority Readiness Guidelines for NG9-1-1 Connectivity
- Type: New
- View Here
INC
- Document Number: ATIS-0300050(2024-12)
- Title: Carrier Identification Code (CIC) Assignment Guidelines (Revision 9)
- Type: Revision
- View Here
- Document Number: ATIS-0300052(2024-12)
- Title: Non-Geographic 5XX-NXX Code Assignment Guidelines (Revision 4)
- Type: Revision
- View Here
- Document Number: ATIS-0300089(2024-12)
- Title: P-ANI Administration Guidelines (Revision 3)
- Type: Revision
- View Here
- Document Number: ATIS-0300119(2024-12)
- Title: Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) (Revision 30)
- Type: Revision
- View Here
PTSC
- Document Number: ATIS-100097.v003
- Title: Technical Report on Alternatives for Caller Authentication for Non-IP Traffic
- Type: Revision
- View Here
- Document Number: ATIS-1000105
- Title: Signature-based Handling of Asserted information using Tokens (SHAKEN): Out-of-Band PASSporT Transmission Between Service Providers that Interconnect using TDM
- Type: New
- View Here
- Document Number: ATIS-1000106
- Title: Viability of Non-IP Call Authentication Standards
- Type: New
- View Here
STEP
- Document Number: ATIS-0600003.2024
- Title: Battery Enclosures and Rooms/Areas
- Type: Revision
- View Here
Recent Policy Filings
ATIS
- Date: 12/09/2024
- Description: Comments to National Institute for Standards and Technology (NIST) re Request for Information on Existing Awards and Recognition Programs for Standards Workforce Development in Support of the Implementation of the United States Government National Standards Strategy for Critical and Emerging Technology (USG NSSCET)
- View filing
