{"description":"Documents matching 'require non-nationwide providers comply federal'","count":198,"total_pages":10,"next_page_url":"https://www.federalregister.gov/api/v1/documents?conditions%5Bterm%5D=require+non-nationwide+providers+comply+federal&format=json&page=2","results":[{"title":"Implementation of the National Suicide Hotline Act of 2018","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopts rules requiring covered text providers, including wireless providers, to develop the capability to transmit georouting data in a format that is compatible with the Lifeline's platform to allow the routing of covered 988 text messages by the Lifeline Administrator to the appropriate crisis center based on the texter's general location, rather than area code; and to provide such georouting data for covered 988 text messages, when available, to the Lifeline Administrator. To protect the privacy of 988 texters, this document defines \"georouting data\" as location data generated from a cell- based location technology that is aggregated to a level that will not identify the precise location of the handset, but only the general area from which the text originated, thereby making local resources available while protecting texters' identities.","document_number":"2025-17895","html_url":"https://www.federalregister.gov/documents/2025/09/16/2025-17895/implementation-of-the-national-suicide-hotline-act-of-2018","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-09-16/pdf/2025-17895.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-17895.pdf?1757940319","publication_date":"2025-09-16","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"To account for <span class=\"match\">non-nationwide</span> <span class=\"match\">providers</span>' on-going efforts to <span class=\"match\">comply</span> with our voice-to-988 georouting implementation requirement, we <span class=\"match\">require</span> <span class=\"match\">non-nationwide</span> <span class=\"match\">providers</span> to <span class=\"match\">comply</span> with our 988 text georouting requirements within 36 months following the effective date of this \n Fourth Report and Order, \n which, as RWA explains, should allow <span class=\"match\">non-nationwide</span> <span class=\"match\">providers</span> a sufficient compliance period. Based on the record, we are confident that our extended compliance deadline will provide sufficient time for <span class=\"match\">non-nationwide</span> service <span class=\"match\">providers</span> to implement 988"},{"title":"Implementation of the National Suicide Hotline Act of 2018","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes and seeks comment on requiring covered text providers, including wireless providers, to support georouting to ensure that the 988 Suicide & Crisis Lifeline (988 Lifeline or Lifeline) may route covered 988 text messages to appropriate local crisis centers. Covered 988 text messages are currently routed to crisis centers using information conveyed by the number assigned to a help-seeker's device, such as an area code, which may not match the text user's physical location. To better connect 988 text users with critical local intervention services, the Commission proposes to require covered text providers to send georouting data to the 988 Lifeline to the same extent that they are required to send covered 988 text messages to the Lifeline.","document_number":"2024-26795","html_url":"https://www.federalregister.gov/documents/2024/11/20/2024-26795/implementation-of-the-national-suicide-hotline-act-of-2018","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-11-20/pdf/2024-26795.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-26795.pdf?1732023916","publication_date":"2024-11-20","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"covered text <span class=\"match\">providers</span> be <span class=\"match\">required</span> to provide with covered 988 texts? Would georouting data for covered 988 texts differ from the data <span class=\"match\">required</span> for georouting voice calls to 988? In our proposed rule, we <span class=\"match\">require</span> that covered text <span class=\"match\">providers</span> provide georouting data with covered 988 texts “when available.” Is such a limitation necessary? Would it be preferable to <span class=\"match\">require</span> covered text <span class=\"match\">providers</span> to provide georouting data with texts to 988 “when technically feasible”? Given that the Commission currently only <span class=\"match\">requires</span> covered text <span class=\"match\">providers</span> to send SMS"},{"title":"Implementation of the National Suicide Hotline Act of 2018","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopted a Third Report and Order that requires wireless providers to implement a georouting solution for calls to the 988 Suicide & Crisis Lifeline (988 Lifeline or Lifeline) to facilitate access to critical local intervention services. The majority of calls to the 988 Lifeline are made from wireless phones. However, the 988 Lifeline's system was originally designed to route calls to crisis centers based on a caller's area code and exchange, which may not correspond to the caller's physical location. With georouting data, the 988 Lifeline will be able to route wireless calls to local crisis centers based on the geographic area where the handset is located at the time the 988 call is initiated while maintaining privacy by not identifying the caller's precise location. The Third Report and Order also revises the Commission's existing 988 voice and texting rules to permit routing to the 988 Lifeline without translation to a toll free access number, giving wireless providers flexibility in implementing georouting solutions.","document_number":"2024-25912","html_url":"https://www.federalregister.gov/documents/2024/11/12/2024-25912/implementation-of-the-national-suicide-hotline-act-of-2018","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-11-12/pdf/2024-25912.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-25912.pdf?1731073559","publication_date":"2024-11-12","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"“not interfere with existing efforts between wireless <span class=\"match\">providers</span>” and will provide “flexibility to adapt to changing technologies.” \n \n 15. \n Georouting <span class=\"match\">Required</span> for all CMRS <span class=\"match\">Providers</span>. \n We find that <span class=\"match\">requiring</span> all CMRS <span class=\"match\">providers</span> to have the capability to provide georouting data with 988 calls is necessary to ensure that wireless 988 callers receive the demonstrated benefits of georouting, regardless of the <span class=\"match\">providers</span>' network configurations. We define nationwide CMRS <span class=\"match\">providers</span> as those <span class=\"match\">providers</span> whose service extends to a majority of the population"},{"title":"Promoting Consumer Choice and Wireless Competition Through Handset Unlocking Requirements and Policies","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) explores the use of handset unlocking policies as a means to improve consumer choice and flexibility and to enhance competition across the mobile wireless marketplace as part of the Commission's ongoing efforts to carry out its statutory obligations to ensure a competitive marketplace for mobile wireless services. Specifically, the Commission proposes to require all mobile wireless service providers to unlock handsets 60 days after a consumer's handset is activated with the provider, unless within the 60-day period the service provider determines the handset was purchased through fraud.","document_number":"2024-16642","html_url":"https://www.federalregister.gov/documents/2024/08/08/2024-16642/promoting-consumer-choice-and-wireless-competition-through-handset-unlocking-requirements-and","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-08-08/pdf/2024-16642.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-16642.pdf?1723034719","publication_date":"2024-08-08","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"understand language? In addition to <span class=\"match\">requiring</span> service <span class=\"match\">providers</span> to post their unlocking policies on their websites, should we <span class=\"match\">require</span> service <span class=\"match\">providers</span> to post their unlocking policies in their stores and that store employees be available to explain the service <span class=\"match\">provider's</span> unlocking policies to customers at the time they purchase handsets? How do we ensure that service <span class=\"match\">providers</span> fully disclose to their customers their unlocking policies at the time a customer purchases a handset? Further, should we <span class=\"match\">require</span> service <span class=\"match\">providers</span> to notify their customers when"},{"title":"Unified Agenda of Federal Regulatory and Deregulatory Actions-Spring 2025","type":"Notice","abstract":"Pursuant to the Regulatory Flexibility Act (RFA; 5 U.S.C 601- 612) the Federal Communications Commission is required to publish a regulatory flexibility agenda twice-yearly in the Federal Register describing any regulatory proceedings under development or review which are likely to have a significant economic impact on a substantial number of small entities. 5 U.S.C. 602. In addition, Executive Order 12866, Regulatory Planning and Review (Sep. 30, 1993), requires each agency to publish, twice yearly, a regulatory agenda (Agenda) of regulations under development or review during the next year which will be included in the Unified Agenda of Regulatory and Deregulatory Actions (Unified Agenda). 58 FR 51735 (Oct. 4, 1993). The Agenda required by Executive Order 12866 must include all regulations the agency expects to develop or review during the next 12 months, regardless of whether they may have a significant economic impact on a substantial number of small entities. E.O. 12866 provides that agencies may combine this agenda with the regulatory flexibility agenda required under the RFA. To help keep the public informed of significant rulemaking proceedings and meet its obligations under the RFA and E.O. 12866, the Commission has prepared Agenda entries providing a brief description and summary of each regulatory activity that is currently planned for the 12 months, subject to revision, including the objectives and legal basis for each, and the name and telephone number of an agency official who is knowledgeable about items in the agenda. The Commission's Agenda entries published in the Federal Register are only those entries for rules that are likely to have a significant economic impact on a substantial number of small entities pursuant to the RFA. The Commission's complete list of regulatory and deregulatory actions for the Unified Agenda will be published on the internet in a searchable format at www.reginfo.gov.","document_number":"2025-18318","html_url":"https://www.federalregister.gov/documents/2025/09/22/2025-18318/unified-agenda-of-federal-regulatory-and-deregulatory-actions-spring-2025","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-09-22/pdf/2025-18318.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-18318.pdf?1758285917","publication_date":"2025-09-22","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Resilient Networks R&amp;O. Particularly, Petitioners asked that the Commission: (1) provide a list of potential <span class=\"match\">providers</span> to which the MDRI may apply; (2) provide sufficient time for wireless <span class=\"match\">providers</span> to achieve compliance (by requesting 12 months for non-small <span class=\"match\">providers</span> and 18 months for small <span class=\"match\">providers</span>); (3) align the definitions of non-small” and small” with the Commission's existing definitions of nationwide” and <span class=\"match\">non-nationwide</span>” as used in the 911 context; (4) establish the process in which the Public Safety and Homeland Security Bureau (Bureau)"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) proposes rules that would help ensure that emerging Next Generation 911 (NG911) networks are reliable and interoperable. NG911 is replacing legacy 911 technology across the country with Internet Protocol (IP)-based infrastructure that will support new 911 capabilities, including text, video, and data. However, for NG911 to be fully effective, NG911 networks must safeguard the reliability of critical components and support the interoperability needed to seamlessly transfer 911 calls and data from one network to another. When the Commission first adopted 911 reliability rules in 2013, the transition to NG911 was in its very early stages. Since then, many state and local 911 Authorities have made significant progress in deploying NG911 capabilities in their jurisdictions. This Further Notice of Proposed Rulemaking (FNPRM) is the next step in fulfilling the Commission's commitment to facilitate the NG911 transition and to ensure that the transition does not inadvertently create vulnerabilities in the nation's critical public safety networks. The FNPRM proposes to update the definition of \"covered 911 service provider\" in the Commission's existing 911 reliability rules to ensure that the rules apply to service providers that control or operate critical pathways and components in NG911 networks. It also proposes to update the reliability standards for providers of critical NG911 functions to ensure the reliable delivery of 911 traffic to NG911 delivery points, and proposes to establish NG911 interoperability requirements for interstate transfer of 911 traffic between Emergency Services IP Networks (ESInets). In addition, the FNPRM proposes to modify the certification and oversight mechanisms in the current 911 reliability rules to improve reliability and interoperability in NG911 systems while minimizing burdens on service providers, and proposes to empower state and local 911 Authorities to obtain reliability and interoperability certifications directly from covered 911 service providers.","document_number":"2025-09279","html_url":"https://www.federalregister.gov/documents/2025/06/04/2025-09279/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-06-04/pdf/2025-09279.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-09279.pdf?1748954707","publication_date":"2025-06-04","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"transition to NG9-1-1 would be to <span class=\"match\">require</span> interoperability between OSPs and 9-1-1 service <span class=\"match\">providers</span>, and among 9-1-1 service <span class=\"match\">providers</span>.”); Jack Varnado, Livingston Parish Sheriff Comments, PS Docket 21-479, at 1 (filed Aug. 9, 2023) (urging the Commission to <span class=\"match\">require</span> all OSPs and 9-1-1 service <span class=\"match\">providers</span> achieve interoperability); Michael Coonfield, Oklahoma 911 Management Authority Comments, PS Docket 21-479, at 2 (filed Aug. 8, 2023) (stating that interoperability between ESInet and core services must be <span class=\"match\">required</span> and included in the forest guide);"},{"title":"Wireless E911 Location Accuracy Requirements","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) proposes rules to strengthen wireless 911 location accuracy rules and to put more actionable location information in the hands of Public Safety Answering Points (PSAPs) and first responders.","document_number":"2025-06865","html_url":"https://www.federalregister.gov/documents/2025/05/07/2025-06865/wireless-e911-location-accuracy-requirements","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-05-07/pdf/2025-06865.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-06865.pdf?1746535509","publication_date":"2025-05-07","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"strengthen the existing rules with respect to z-axis location by <span class=\"match\">requiring</span> CMRS <span class=\"match\">providers</span> that deploy z-axis technology to deliver z-axis information to PSAPs measured in Height Above Ground Level (AGL), which is likely to be more actionable than the currently <span class=\"match\">required</span> Height Above Ellipsoid (HAE). In addition, we seek comment on <span class=\"match\">requiring</span> CMRS <span class=\"match\">providers</span> to provide floor level estimates.\n \n \n • \n Testing and Compliance Framework. \n We propose to strengthen the test bed validation process and <span class=\"match\">require</span> greater transparency and accountability with respect to"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Location-Based Routing for Wireless 911 Calls","type":"Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) adopted a Report and Order to advance the nationwide Next Generation 911 (NG911) transition rules that define the responsibilities and set deadlines for originating service providers (OSPs) to implement NG911 capabilities on their networks and deliver 911 calls to NG911 systems established by 911 authorities. In addition, the rules preserve the authority of state, territorial, regional, Tribal, and local government to adopt alternative approaches to the configuration, timing, and cost responsibility for NG911 implementation within their jurisdictions.","document_number":"2024-18603","html_url":"https://www.federalregister.gov/documents/2024/09/24/2024-18603/facilitating-implementation-of-next-generation-911-services-ng911-location-based-routing-for","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-09-24/pdf/2024-18603.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-18603.pdf?1727095514","publication_date":"2024-09-24","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Nationwide CMRS <span class=\"match\">providers</span>,\n 6 \n \n covered text <span class=\"match\">providers</span>,\n 7 \n \n interconnected VoIP <span class=\"match\">providers</span>, and wireline <span class=\"match\">providers</span> other than rural incumbent local exchange carriers (RLECs) will have six months following a 911 Authority's valid Phase 1 request to <span class=\"match\">comply</span> with Phase 1 requirements, and six months following a valid Phase 2 request to <span class=\"match\">comply</span> with Phase 2 requirements. RLECs,\n 8 \n \n <span class=\"match\">non-nationwide</span> CMRS <span class=\"match\">providers</span>,\n 9 \n \n and internet-based TRS <span class=\"match\">providers</span> will have one year following a 911 Authority's valid Phase 1 request to <span class=\"match\">comply</span> with Phase 1 requirements"},{"title":"Location-Based Routing for Wireless 911 Calls","type":"Rule","abstract":"The Federal Communications Commission (the FCC or Commission) adopted a Report and Order in PS Docket No. 18-64, FCC 24-4, on January 25, 2024, and released on January 26, 2024. This document is a summary of the Commission's Report and Order. The Report and Order adopted rules to more precisely route wireless 911 calls and Real-Time Texts (RTT) to Public Safety Answering Points (PSAPs), which can result in faster response times during emergencies. Wireless 911 calls have historically been routed to PSAPs based on the location of the cell tower that handles the call. Sometimes, however, the 911 call is routed to the wrong PSAP because the cell tower is not in the same jurisdiction as the 911 caller. This can happen, for instance, when an emergency call is placed near a county border. These misrouted 911 calls must be transferred from one PSAP to another, which consumes time and resources and can cause confusion and delay in emergency response. The Report and Order requires wireless providers to deploy technology that supports location-based routing, a method that relies on precise information about the location of the wireless caller's device, on their internet Protocol (IP)-based networks and to use location-based routing to route 911 voice calls and RTT communications to 911 originating on those networks when caller location is accurate and timely. The Report and Order provides six months for nationwide wireless providers to implement location-based routing for wireless 911 voice calls and provides 24 months for non-nationwide wireless providers to implement location-based routing of wireless 911 voice calls. The Report and Order provides 24 months for all wireless providers to implement location-based routing for RTT communications to 911.","document_number":"2024-03157","html_url":"https://www.federalregister.gov/documents/2024/03/13/2024-03157/location-based-routing-for-wireless-911-calls","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-03-13/pdf/2024-03157.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-03157.pdf?1709932520","publication_date":"2024-03-13","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"system. CMRS <span class=\"match\">providers</span> seeking to employ foreign satellite navigation systems for 911 should follow the existing approval process.\n \n 22. We <span class=\"match\">require</span> nationwide CMRS <span class=\"match\">providers</span> to <span class=\"match\">comply</span> with these location-based routing requirements for voice calls within six months after the effective date of the final rules. We <span class=\"match\">require</span> <span class=\"match\">non-nationwide</span> CMRS <span class=\"match\">providers</span> to <span class=\"match\">comply</span> with these location-based routing requirements for voice calls within 24 months after the effective date of the final rules in recognition of resource constraints faced by these <span class=\"match\">providers</span>. As discussed"},{"title":"Enhancing Know-Your-Customer Requirements","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes actions to provide additional clarity to fill the gap between its current Know Your Customer (KYC) requirement and the types of rigorous KYC steps necessary to protect consumers. Specifically, the Commission seeks comment on customer identification requirements for new and renewing customers, requirements for verifying, retaining, and re-verifying customer information, requiring more information from certain customers such as high-volume customers, and on how these efforts can complement call branding and caller name requirements the Commission may adopt. The Commission also proposes to assess penalties for violations of the KYC requirement on a per call basis. With this inquiry, the Commission aims to make it more difficult for scammers to originate illegal calls and easier to enforce against them when they do get onto the network.","document_number":"2026-10407","html_url":"https://www.federalregister.gov/documents/2026/05/26/2026-10407/enhancing-know-your-customer-requirements","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-05-26/pdf/2026-10407.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-10407.pdf?1779453917","publication_date":"2026-05-26","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"We seek comment on <span class=\"match\">requiring</span> originating <span class=\"match\">providers</span> to obtain certain identification information from both new and renewing customers. Specifically, we seek comment on <span class=\"match\">requiring</span> originating <span class=\"match\">providers</span> to, at a minimum, obtain and retain the name, physical address, government issued identification number, and an alternate telephone number of any new and renewing customer before granting access to its services. For high-volume customers, including business and foreign customers, we seek comment on <span class=\"match\">requiring</span> originating <span class=\"match\">providers</span> to also collect the"},{"title":"Protecting Our Communications Networks by Promoting Transparency Regarding Foreign Adversary Control","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission or FCC) addresses the risks of foreign adversary control of Commission-granted licenses and authorizations by adopting rules requiring a broad range of holders of such licenses, authorizations, or approvals to attest whether they are owned by, controlled by, or subject to the jurisdiction or direction of a foreign adversary, and, if so, to disclose additional information about such foreign adversary control. Among other things, the Commission defines categories of licenses and authorizations that are subject to the rules, and establishes a streamlined process by which license and authorization holders should file their foreign adversary control attestations and disclosures.","document_number":"2026-06992","html_url":"https://www.federalregister.gov/documents/2026/04/10/2026-06992/protecting-our-communications-networks-by-promoting-transparency-regarding-foreign-adversary-control","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-04-10/pdf/2026-06992.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-06992.pdf?1775738718","publication_date":"2026-04-10","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"service <span class=\"match\">providers</span>. Like other communications <span class=\"match\">providers</span>, VoIP <span class=\"match\">providers</span> subject to Foreign Adversary Control that directly access U.S. numbering resources in order to provide their service could pose an unacceptable risk to national security. We therefore find that it is in the public interest to <span class=\"match\">require</span> interconnected VoIP direct access authorization holders to <span class=\"match\">comply</span> with the attestation and disclosure rules we adopt today. No commenter opposes this requirement, and we find that there are no reasons why these <span class=\"match\">providers</span> could not <span class=\"match\">comply</span> with the"},{"title":"Information Collection Being Submitted for Review and Approval to Office of Management and Budget","type":"Notice","abstract":"As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal Agencies to take this opportunity to comment on the following information collection. Pursuant to the Small Business Paperwork Relief Act of 2002, the FCC seeks specific comment on how it might \"further reduce the information collection burden for small business concerns with fewer than 25 employees.\" The Commission may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.","document_number":"2024-06957","html_url":"https://www.federalregister.gov/documents/2024/04/02/2024-06957/information-collection-being-submitted-for-review-and-approval-to-office-of-management-and-budget","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-04-02/pdf/2024-06957.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-06957.pdf?1711975531","publication_date":"2024-04-02","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Nationwide CMRS <span class=\"match\">providers</span> must submit call data on a quarterly basis; <span class=\"match\">non-nationwide</span> CMRS <span class=\"match\">providers</span> need only submit this data every six months. <span class=\"match\">Non-nationwide</span> <span class=\"match\">providers</span> that do not provide service in any of the Test Cities may satisfy this requirement by collecting and reporting data based on the largest county within the carrier's footprint. This reporting requirement is necessary to validate and verify the compliance certifications made by CMRS <span class=\"match\">providers</span>. \n The Commission developed a reporting template to assist CMRS <span class=\"match\">providers</span> in collecting, formatting"},{"title":"Information Collection Being Reviewed by the Federal Communications Commission","type":"Notice","abstract":"As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collection. Comments are requested concerning: whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees.","document_number":"2024-01480","html_url":"https://www.federalregister.gov/documents/2024/01/25/2024-01480/information-collection-being-reviewed-by-the-federal-communications-commission","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-01-25/pdf/2024-01480.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-01480.pdf?1706103939","publication_date":"2024-01-25","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Nationwide CMRS <span class=\"match\">providers</span> must submit call data on a quarterly basis; <span class=\"match\">non-nationwide</span> CMRS <span class=\"match\">providers</span> need only submit this data every six months. <span class=\"match\">Non-nationwide</span> <span class=\"match\">providers</span> that do not provide service in any of the Test Cities may satisfy this requirement by collecting and reporting data based on the largest county within the carrier's footprint. This reporting requirement is necessary to validate and verify the compliance certifications made by CMRS <span class=\"match\">providers</span>. \n The Commission developed a reporting template to assist CMRS <span class=\"match\">providers</span> in collecting, formatting"},{"title":"Auction of Advanced Wireless Services (AWS-3) Licenses; Filing Requirements, Minimum Opening Bids, Upfront Payments, and Other Procedures for Auction 113","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) summarizes the procedures, deadlines, and upfront payment and minimum opening bid amounts for the upcoming auction of 200 Advanced Wireless Services licenses for spectrum in the Federal Communications Commission's inventory in the 1695-1710 MHz, 1755-1780 MHz, and 2155-2180 MHz bands (AWS-3 bands). This document provides details regarding the procedures, terms, conditions, dates, and deadlines governing participation in Auction 113 bidding, as well as overview of the post-auction application and payment processes.","document_number":"2025-23785","html_url":"https://www.federalregister.gov/documents/2025/12/23/2025-23785/auction-of-advanced-wireless-services-aws-3-licenses-filing-requirements-minimum-opening-bids","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-12-23/pdf/2025-23785.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-23785.pdf?1766411125","publication_date":"2025-12-23","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"incumbent <span class=\"match\">Federal</span> users while they remain authorized to operate in the band. The 2155-2180 MHz band is already allocated for exclusive non-<span class=\"match\">Federal</span>, commercial use. Although no <span class=\"match\">Federal</span> users are currently licensed or operating in the 2155-2180 MHz band, AWS-3 licensees may have to protect or relocate and/or share in the cost of relocating non-<span class=\"match\">Federal</span> incumbent Fixed Microwave and Broadband Radio Service licensees in the band. \n \n AWS-3 licensees in the 1695-1710 MHz and 1755-1780 MHz bands are <span class=\"match\">required</span> to successfully coordinate with <span class=\"match\">Federal</span> incumbent"},{"title":"Achieving 100% Wireless Handset Model Hearing Aid Compatibility","type":"Rule","abstract":"In this document, the Federal Communications Commission (\"Commission\") adopts a 100% hearing aid compatibility requirement that applies to all future wireless handset models offered for sale or use in the United States and implementation provisions related to this 100% requirement, including a Bluetooth coupling requirement.","document_number":"2024-25088","html_url":"https://www.federalregister.gov/documents/2024/11/13/2024-25088/achieving-100-wireless-handset-model-hearing-aid-compatibility","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-11-13/pdf/2024-25088.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-25088.pdf?1731419115","publication_date":"2024-11-13","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"recommendation that we <span class=\"match\">require</span> all handset models offered for sale or use in the United States to have at least two forms of coupling. Based on the HAC Task Force's recommendation, we proposed to <span class=\"match\">require</span> that: (1) 100% of handset models be <span class=\"match\">required</span> to meet an acoustic coupling requirement; and (2) 100% of handset models be <span class=\"match\">required</span> to meet \n either \n a telecoil or a Bluetooth coupling requirement. Specifically, at least 85% of handset models would be <span class=\"match\">required</span> to meet a telecoil requirement and at least 15% of handset models would be <span class=\"match\">required</span> to meet a Bluetooth"},{"title":"Ensuring the Reliability and Resiliency of the 988 Suicide & Crisis Lifeline; Rules Concerning Disruptions to Communications; Implementation of the National Suicide Hotline Improvement Act of 2018","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) requires covered 988 service providers (a new category of service provider) and cable, satellite, wireless, wireline, and interconnected voice over internet protocol (VoIP) providers (originating service providers) to report outages that potentially affect the 988 Suicide and Crisis Lifeline in the Commission's Network Outage Reporting System (NORS). The rules also require these entities to directly notify Substance Abuse and Mental Health Services Administration (SAMHSA), the Department of Veterans Affairs (VA), and the 988 Lifeline administrator about outages that potentially affect a 988 special facility, and exercise special diligence to maintain accurate, up-to-date contact information for 988 special facilities, just as the Commission's rules require for 911 special facilities. The rules also allow SAMHSA and the VA to have direct read-only access to NORS consistent with the Commission's existing NORS outage information sharing procedures. These rules are adopted with the goal of ensuring that the Commission and those parties that provide life-saving crisis intervention services to people calling the 988 Lifeline receive timely and actionable information about 988 service outages that potentially affect those services' ability to meet the immediate health needs of people in suicidal crisis and mental health distress.","document_number":"2024-00428","html_url":"https://www.federalregister.gov/documents/2024/01/16/2024-00428/ensuring-the-reliability-and-resiliency-of-the-988-suicide-and-crisis-lifeline-rules-concerning","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-01-16/pdf/2024-00428.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-00428.pdf?1705067114","publication_date":"2024-01-16","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"urges service <span class=\"match\">providers</span> to collaborate with 988 special facilities to ensure that 988 notifications are provided in a format that best facilitates rapid analysis and action. \n 22. The Commission declines to <span class=\"match\">require</span> covered 988 service <span class=\"match\">providers</span> to notify originating service <span class=\"match\">providers</span> about 988 Lifeline outages and decline to <span class=\"match\">require</span> originating service <span class=\"match\">providers</span> to notify covered 988 service <span class=\"match\">providers</span> about 988 Lifeline outages. As some commenters note, covered 988 service <span class=\"match\">providers</span> often compete with originating service <span class=\"match\">providers</span> or provide services"},{"title":"Unified Agenda of Federal Regulatory and Deregulatory Actions-Spring 2024","type":"Proposed Rule","abstract":"In the Spring and Fall of each year, the Federal Communications Commission publishes in the Federal Register a list in the Unified Agenda of those major items and other significant regulatory proceedings under development or review that pertain to the Regulatory Flexibility Act (5 U.S.C. 602). The Unified Agenda also provides the Code of Federal Regulations citations and legal authorities that govern these proceedings. The complete Unified Agenda will be published on the internet in a searchable format at www.reginfo.gov.","document_number":"2024-16467","html_url":"https://www.federalregister.gov/documents/2024/08/16/2024-16467/unified-agenda-of-federal-regulatory-and-deregulatory-actions-spring-2024","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-08-16/pdf/2024-16467.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-16467.pdf?1723725924","publication_date":"2024-08-16","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Commission: (1) provide a list of potential <span class=\"match\">providers</span> to which the MDRI may apply; (2) provide sufficient time for wireless <span class=\"match\">providers</span> to achieve compliance (by requesting 12 months for non-small <span class=\"match\">providers</span> and 18 months for small <span class=\"match\">providers</span>); (3) align the definitions of “non-small” and “small” with the Commission's existing definitions of “nationwide” and “<span class=\"match\">non-nationwide</span>” as used in the 911 context; (4) establish the process in which the Public Safety and Homeland Security Bureau (Bureau) will inform <span class=\"match\">providers</span> that the MDRI is active; and (5) affirm"},{"title":"Emergency Alert System; Wireless Emergency Alerts","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopts rules for commercial mobile service providers that have elected to participate in the Wireless Emergency Alert system (WEA) (Participating CMS Providers) to support WEA messages in the 13 most commonly spoken languages in the U.S. as well as English and American Sign Language. Participating CMS Providers are to support this expanded multilingual alerting by enabling mobile devices to display message templates that will be pre-installed and stored on the mobile device. The Commission also directs its Public Safety and Homeland Security Bureau to seek comment on various implementation details of the multilingual alerting requirements and future expansion to additional languages. In addition, to help personalize emergency alerts, the Commission requires participating wireless providers to support the inclusion of maps in WEA messages that show the alert recipient's location relative to the geographic area where the emergency is occurring, and establishes a Commission-hosted database to provide the public with easy-to-access information on WEA availability. Wireless providers will be required to supply information on whether they participate in WEA and, if so, the extent of WEA availability in their service area and on the mobile devices that they sell. Last, to support more effective WEA performance and public awareness, the amended rules enable alerting authorities to send two local WEA tests per year that the public receives by default, provided that the alerting authority takes steps to ensure that the public is aware that the test is, in fact, only a test.","document_number":"2023-27236","html_url":"https://www.federalregister.gov/documents/2023/12/15/2023-27236/emergency-alert-system-wireless-emergency-alerts","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2023-12-15/pdf/2023-27236.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2023-27236.pdf?1702561517","publication_date":"2023-12-15","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"languages we <span class=\"match\">require</span> Participating CMS <span class=\"match\">Providers</span> to support for multilingual alerting as well as ASL.\n \n 31. While the Commission continues to evaluate the record on our proposed performance reporting requirements, the Commission believe that this revision of our testing rules will at least help address alerting authorities' immediate needs for WEA performance information in their jurisdictions. \n \n 32. The \n Third Report and Order \n <span class=\"match\">requires</span> Participating CMS <span class=\"match\">Providers</span> to <span class=\"match\">comply</span> with this requirement within 30 days of the \n <span class=\"match\">Federal</span> Register \n publication"},{"title":"Resilient Networks; Disruptions to Communications","type":"Rule","abstract":"The Federal Communications Commission (Commission or FCC) published a document in the Federal Register on January 26, 2024, concerning an Order on Reconsideration that addresses the Petition for Clarification and Partial Reconsideration (Petition) filed by CTIA and the Competitive Carriers Association (CCA) (collectively, Petitioners) of the Commission's Report and Order regarding the \"Mandatory Disaster Response Initiative\" (MDRI) by extending the compliance deadline to implement elements of the MDRI to May 1, 2024. In its Order on Reconsideration, the Commission also agrees with the request to treat Roaming under Disaster arrangements (RuDs) as presumptively confidential when filed with the Commission. In this document, the Commission is withdrawing its previous Federal Register publication of the Order on Reconsideration and substituting the present document to correct certain information regarding the compliance date and effective date. In addition, this document announces that, on October 27, 2023, the Office of Management and Budget (OMB) approved, for a period of three years, the information collection requirements associated with the rules adopted in the Report and Order. The OMB Control Number is 3060-1317. The Commission also announces that compliance with the rules will be required, and revises its rules to specify this date and to remove text advising that compliance was not required until OMB review was completed. This action is consistent with the 2023 Order on Reconsideration, which stated that the Commission would publish a document in the Federal Register announcing a compliance date and revise the rule accordingly.","document_number":"2024-06092","html_url":"https://www.federalregister.gov/documents/2024/03/26/2024-06092/resilient-networks-disruptions-to-communications","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-03-26/pdf/2024-06092.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-06092.pdf?1711370716","publication_date":"2024-03-26","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"the complexity of negotiating and executing the <span class=\"match\">required</span> arrangements for many regional and local <span class=\"match\">providers</span>, \n e.g., \n <span class=\"match\">providers</span> may have to negotiate arrangements and complete roaming testing with a large number of <span class=\"match\">providers</span>, some <span class=\"match\">providers</span> do not have existing agreements with other <span class=\"match\">providers</span> and may need to address unanticipated complexities or include terms unique to certain disaster contexts, and some <span class=\"match\">providers</span> lack the resources to negotiate agreements and conduct testing with multiple <span class=\"match\">providers</span> at the same time.\n \n The Order on Reconsideration"},{"title":"Supporting Survivors of Domestic and Sexual Violence; Lifeline and Link Up Reform Modernization","type":"Rule","abstract":"In this document, the Federal Communications Commission adopted a Report and Order implementing the Safe Connections Act of 2022 (Safe Connections Act or SCA), taking significant steps to improve access to communications services for survivors of domestic abuse and related crimes. The Report and Order adopts rules to implement the line separation provisions in the Safe Connections Act that allow survivors to separate a mobile phone line from an abuser. To protect the privacy of calls and texts to hotlines, the Report and Order requires covered providers and wireline, fixed wireless, and fixed satellite providers of voice service to: omit from consumer-facing logs of calls and text messages any records of calls or text messages to covered hotlines in the central database established by the Commission; and maintain internal records of calls and text messages excluded from consumer- facing logs of calls and text messages. The Report and Order also designates the Lifeline program to support emergency communications service for survivors that have pursued the line separation process and are experiencing financial hardship.","document_number":"2023-25835","html_url":"https://www.federalregister.gov/documents/2023/12/05/2023-25835/supporting-survivors-of-domestic-and-sexual-violence-lifeline-and-link-up-reform-modernization","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2023-12-05/pdf/2023-25835.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2023-25835.pdf?1701697517","publication_date":"2023-12-05","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"facilities-based <span class=\"match\">provider</span>. \n \n 13. Additionally, we conclude that the statutory definition of “covered <span class=\"match\">provider</span>” includes a <span class=\"match\">provider</span> of mobile broadband-only or mobile text service that does not also offer mobile voice service, if such <span class=\"match\">provider</span> assigns a telephone number to a device. Because the SCA defines a “covered <span class=\"match\">provider</span>” to include any <span class=\"match\">provider</span> offering private mobile service or commercial mobile service, we conclude that <span class=\"match\">providers</span> offering data-only mobile service or text-only mobile services (\n i.e., \n no voice services) are “covered <span class=\"match\">providers</span>.” We"}]}