{"description":"Documents matching 'fixed wireless providers must when'","count":1616,"total_pages":50,"next_page_url":"https://www.federalregister.gov/api/v1/documents?conditions%5Bterm%5D=fixed+wireless+providers+must+when&format=json&page=2","results":[{"title":"Establishing the Digital Opportunity Data Collection; Modernizing the FCC Form 477 Data Program; Delete, Delete, Delete","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopted a Further Notice of Proposed Rulemaking (FNPRM) that seeks comment on eliminating outdated requirements and ways to enhance the efficiency of the Broadband Data Collection (BDC) while ensuring that the Commission continues to receive accurate, granular data. Building off the infrastructure data-based coverage restoration process established by the Commission in 2024, the FNPRM seeks comment on several approaches suggested by commenters to simplify, streamline, or otherwise reduce burdens on this coverage restoration process. The FNPRM seeks comment on several ways to simplify the collection of fixed and fixed wireless biannual submissions, specifically on: (1) either allowing providers to indicate certain fixed broadband availability data have been \"grandfathered\" or else simply eliminating the collection of these data; (2) eliminating the requirement that a provider report fixed broadband availability data at speeds below 25/3 Mbps as part of its biannual submission; (3) revising the Commission's rules to eliminate the requirement for providers to use and disclose maximum buffer size data in their BDC biannual submissions; and (4) revising the Commission's rules to relax the 7 meter antenna height requirement that fixed wireless providers must use when modeling their coverage. In addition, the FNPRM seeks comment on ending legacy data collections for mobile service, specifically the collection of 3G mobile broadband availability data and mobile voice data as part of a provider's biannual submission, including potential impacts on reporting for Alaska and on relevant USF programs, respectively. Furthermore, the FNPRM seeks comment on current data retention practices to develop a set of best practices instead of adopting any substantive rule. The FNPRM seeks comment on several potential challenge process improvements, specifically on: (1) allowing service providers to presumptively rebut certain types of fixed challenges with infrastructure data and on requiring infrastructure data in response to certain types of fixed challenges; (2) various options for simplifying and reducing the provider response periods for the fixed challenge process; (3) streamlining the mobile challenge process by automatically removing from the National Broadband Map (NBM) all challenged areas that are conceded or upheld; and (4) relaxing or removing some current mobile crowdsourced data requirements to encourage the submission of additional data. The FNPRM seeks comment on mobile verification and audit process improvements. The FNPRM also seeks comment on improvements to the collection of mobile crowdsourced data and the use of drone data. Lastly, the FNPRM seeks comment on revising the Commission's rules to expressly provide that subscription data, the geographic coordinates of mobile or fixed wireless base stations, mobile or fixed wireless link budget parameter rationales, and any infrastructure data submitted in response to a verification request or audit will be always treated as confidential.","document_number":"2026-12767","html_url":"https://www.federalregister.gov/documents/2026/06/24/2026-12767/establishing-the-digital-opportunity-data-collection-modernizing-the-fcc-form-477-data-program","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-24/pdf/2026-12767.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12767.pdf?1782218725","publication_date":"2026-06-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":"maximum buffer requirements for <span class=\"match\">fixed</span> service <span class=\"match\">providers</span>, should we modify the current exceptions to maximum buffer reporting? \n \n Relaxing Maximum Consumer Antenna Height Requirement for Terrestrial <span class=\"match\">Fixed</span> <span class=\"match\">Wireless</span>. \n We seek comment on revising the Commission's rules to relax the seven-meter maximum antenna height requirement that <span class=\"match\">fixed</span> <span class=\"match\">wireless</span> <span class=\"match\">providers</span> <span class=\"match\">must</span> use <span class=\"match\">when</span> modeling their coverage. As adopted in the \n Second Report and Order, \n <span class=\"match\">when</span> a terrestrial <span class=\"match\">fixed</span> <span class=\"match\">wireless</span> service <span class=\"match\">provider</span> chooses to report <span class=\"match\">fixed</span> broadband availability data using"},{"title":"Promoting Technological Solutions To Combat Contraband Wireless Device Use in Correctional Facilities","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (FCC or Commission) seeks comment on proposals that would enhance public safety by removing regulatory barriers to the deployment and viability of existing and developing technologies that combat contraband wireless device use in correctional facilities. This document seeks comment on a proposed framework to authorize, for the first time, non-federal operation of radio frequency (RF) jamming solutions in correctional facilities. The Commission seeks to foster a collaborative environment among key stakeholders, including departments of correction, solutions providers, wireless providers, public safety and 911 entities, to explore an expanded range of solutions to a shared problem.","document_number":"2025-21325","html_url":"https://www.federalregister.gov/documents/2025/11/26/2025-21325/promoting-technological-solutions-to-combat-contraband-wireless-device-use-in-correctional","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-11-26/pdf/2025-21325.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-21325.pdf?1764078345","publication_date":"2025-11-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":"agreements between <span class=\"match\">wireless</span> <span class=\"match\">providers</span> and solutions <span class=\"match\">providers</span>? Are specific measures needed to prevent harmful interference to a <span class=\"match\">wireless</span> <span class=\"match\">provider's</span> base stations in a TDD context, for example taking into consideration the desired v. undesired signal levels in a TDD pattern? Should we require, in a TDD context, synchronization between a solutions <span class=\"match\">provider</span> deploying a jamming solution and the <span class=\"match\">wireless</span> <span class=\"match\">provider</span> offering service to an area that includes a correctional facility to avoid unwanted transmissions during the <span class=\"match\">wireless</span> <span class=\"match\">provider's</span> base station transmit"},{"title":"Build America: Eliminating Barriers to Wireless Deployments","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) seeks to advance its Build America Agenda by seeking comment on reforms that would free towers and other wireless infrastructure from unlawful regulatory burdens imposed.","document_number":"2025-21620","html_url":"https://www.federalregister.gov/documents/2025/12/01/2025-21620/build-america-eliminating-barriers-to-wireless-deployments","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-12-01/pdf/2025-21620.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-21620.pdf?1764337516","publication_date":"2025-12-01","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":"\n \n • Ogden City, Utah: Providing that unless a <span class=\"match\">wireless</span> <span class=\"match\">provider</span> is subject to the Municipal Telecommunications License Tax under title 10, chapter 1, part 4 Utah Code Annotated, for the right to use and occupy the right-of-way the <span class=\"match\">wireless</span> <span class=\"match\">provider</span> shall pay to the \n \n City an annual fee equal to the greater of: 3.5 percent of all annual gross revenue related to the <span class=\"match\">wireless</span> <span class=\"match\">provider's</span> use of the right-of-way within the City or two hundred fifty dollars ($250.00) annually for each small <span class=\"match\">wireless</span> facility located in the City;\n \n • St. George, Utah:"},{"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":"increasing standardization, we seek to strengthen our <span class=\"match\">wireless</span> location accuracy rules to provide PSAPs and first responders with actionable information in the live 911 call environment. \n A. Improving Actionability of Z-Axis Information \n \n Under the current rules, CMRS <span class=\"match\">providers</span> providing coordinate-based location information to PSAPs with <span class=\"match\">wireless</span> 911 calls <span class=\"match\">must</span> deliver the z-axis component in Height Above Ellipsoid (HAE).\n 40 \n \n In addition, CMRS <span class=\"match\">providers</span> <span class=\"match\">must</span> provide floor level information <span class=\"match\">when</span> it is available.\n 41 \n \n We propose to make the z-axis"},{"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":"(\n i.e., \n by a specified calendar date)” and in doing so, <span class=\"match\">must</span> “assess factors such as technical and financial challenges with respect to implementation, the status of the Lifeline, and the public interest.”\n \n \n 7. \n Covered Text <span class=\"match\">Providers</span>. \n We apply our 988 text georouting requirements to “Covered Text <span class=\"match\">Providers</span>,” as defined in the \n Text-to-988 Second Report and Order. \n Covered text <span class=\"match\">providers</span> include “all [Commercial Mobile Radio Service (CMRS)] <span class=\"match\">providers</span>, as well as all <span class=\"match\">providers</span> of interconnected text messaging services that enable consumers"},{"title":"Lower 37 GHz Band and Use of Spectrum Bands Above 24 GHz for Mobile Radio Service","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) makes available 600 megahertz of high-frequency spectrum for flexible fixed and mobile use by establishing a mechanism for access to the 37-37.6 GHz band (Lower 37 GHz band). This spectrum, which is shared between non-Federal and Federal operators, can be used for fixed wireless broadband, Internet of Things (IoT), or other innovative services. Crafted in collaboration with the National Telecommunications and Information Administration (NTIA) and with input from the Department of Defense (DoD), this new regime provides access to a block of millimeter wave spectrum with low barriers to entry.","document_number":"2025-10476","html_url":"https://www.federalregister.gov/documents/2025/06/12/2025-10476/lower-37-ghz-band-and-use-of-spectrum-bands-above-24-ghz-for-mobile-radio-service","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-06-12/pdf/2025-10476.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-10476.pdf?1749645907","publication_date":"2025-06-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":"Universal Service Monitoring Report, as of December 31, 2021, there were 594 <span class=\"match\">providers</span> that reported they were engaged in the provision of <span class=\"match\">wireless</span> services. Of these <span class=\"match\">providers</span>, the Commission estimates that 511 <span class=\"match\">providers</span> have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these <span class=\"match\">providers</span> can be considered small entities.\n \n \n 68. \n <span class=\"match\">Fixed</span> Microwave Services. \n <span class=\"match\">Fixed</span> microwave services include common carrier, private-operational <span class=\"match\">fixed</span>, and broadcast auxiliary radio services. They also include the Upper Microwave"},{"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":"timeline for nationwide CMRS <span class=\"match\">providers</span> to implement location-based routing for <span class=\"match\">wireless</span> 911 voice calls and provide twenty-four months for non-nationwide CMRS <span class=\"match\">providers</span> to implement location-based routing of <span class=\"match\">wireless</span> 911 voice calls.\n 5 \n \n In addition, we provide 24 months for all CMRS <span class=\"match\">providers</span> to implement location-based routing for RTT communications to 911.\n \n \n \n 5 \n  The Commission defines a “[n]on-nationwide CMRS <span class=\"match\">provider</span>” for purposes of its part 9 rules as “[a]ny CMRS <span class=\"match\">provider</span> other than a nationwide CMRS <span class=\"match\">provider</span>.” 47 CFR 9.10(i)(1)(v). A"},{"title":"Designation-Restrict the Operation of Unmanned Aircraft in Close Proximity to a Fixed Site Facility","type":"Proposed Rule","abstract":"This action would implement section 2209, of the FAA Extension, Safety and Security Act of 2016, by establishing a process for operators and proprietors of certain fixed site facilities to request and maintain an unmanned aircraft flight restriction. The proposal also establishes requirements for applicants to demonstrate the unmanned aircraft flight restriction is necessary for: aviation safety, protection of people and property on the ground, national security, or homeland security. Lastly, the proposal identifies the types of operations that are allowed in the unmanned aircraft flight restriction UAFR.","document_number":"2026-08943","html_url":"https://www.federalregister.gov/documents/2026/05/06/2026-08943/designation-restrict-the-operation-of-unmanned-aircraft-in-close-proximity-to-a-fixed-site-facility","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-05-06/pdf/2026-08943.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-08943.pdf?1777985132","publication_date":"2026-05-06","agencies":[{"raw_name":"DEPARTMENT OF TRANSPORTATION","name":"Transportation Department","id":492,"url":"https://www.federalregister.gov/agencies/transportation-department","json_url":"https://www.federalregister.gov/api/v1/agencies/492","parent_id":null,"slug":"transportation-department"},{"raw_name":"Federal Aviation Administration","name":"Federal Aviation Administration","id":159,"url":"https://www.federalregister.gov/agencies/federal-aviation-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/159","parent_id":492,"slug":"federal-aviation-administration"}],"excerpts":"part; \n \n (b) \n Facility information. \n The applicant <span class=\"match\">must</span> provide the following information:\n \n (1) The name, physical address, mailing address (if different from the physical address), telephone number, email address, and website (if applicable) of the <span class=\"match\">fixed</span> site facility; \n (2) A detailed description of the <span class=\"match\">fixed</span> site facility, including a legal description of the property, the boundaries on which the <span class=\"match\">fixed</span> site facility is located, and the height of the tallest structure associated with the <span class=\"match\">fixed</span> site facility. \n \n \n § 74.54 \n \n Unless otherwise"},{"title":"Wireless Telecommunications Bureau Announces Licensing and Coordination Procedures for the Space Launch Service","type":"Rule","abstract":"In this document, the Wireless Telecommunications Bureau (WTB or Bureau) announces licensing and frequency coordination procedures and data requirements for Space Launch Service licensees seeking Commission authorization to perform non-Federal space launch operations in the 2,025-2,110 MHz, 2,200-2,290 MHz, and 2,360-2,395 MHz bands.","document_number":"2025-07643","html_url":"https://www.federalregister.gov/documents/2025/05/02/2025-07643/wireless-telecommunications-bureau-announces-licensing-and-coordination-procedures-for-the-space","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-05-02/pdf/2025-07643.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-07643.pdf?1746103513","publication_date":"2025-05-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":"federal sites. \n \n <span class=\"match\">Fixed</span>, Base, Itinerant, and Mobile Station Registrations. \n As established in the \n Second Report and Order, \n a Space Launch Service licensee <span class=\"match\">must</span> register the <span class=\"match\">fixed</span>, base, itinerant, and mobile stations needed to support a launch in ULS under its nationwide, nonexclusive license. Through delegated authority, the Bureau sought to provide clarity for applicants and, after coordinating with NTIA, proposed one set of data requirements for itinerant and mobile station registrations, and a separate set for <span class=\"match\">fixed</span> and base station registrations"},{"title":"In the Matter of Upper C-band (3.98-4.2 GHz)","type":"Proposed Rule","abstract":"In this Notice of Proposed Rulemaking (NPRM), the Federal Communications Commission (Commission) seeks comment on proposed rule changes that would expand the ecosystem for next generation wireless services in the 3.7-4.2 GHz band (C-band) by making as much as 180, and at least 100, megahertz of the 3.98-4.2 GHz band (Upper C-band) available for terrestrial wireless flexible use via a system of competitive bidding. This action would be in furtherance of Congress' direction in the One Big Beautiful Bill Act (OBBB Act) to \"complet[e] a system of competitive bidding not later than 2 years after the date of enactment of this Act for not less than 100 megahertz in the band between 3.98 gigahertz and 4.2 gigahertz.\" The NPRM seeks comment on options for reconfiguring the Upper C-band in the contiguous United States ranging from 180 megahertz (3.98-4.16 GHz) to the congressionally mandated minimum of 100 megahertz (3.98-4.08 GHz) for terrestrial wireless use. The NPRM seeks comment on how much Upper C- band spectrum--beyond the minimum 100 megahertz required by the OBBB Act--could be repurposed by incumbent fixed satellite service (FSS) space station operators and on how the transition could be effectuated if their existing customers relocate out of the C-band. Under any of the reconfiguration options under consideration, the NPRM's baseline proposition is to apply the existing 3.7 GHz Service rules (applicable in the Lower C-band from 3.7-3.98 GHz) to any newly authorized terrestrial wireless operations. Any other rules and requirements, including those relating to the transition process, would be modeled to the greatest extent possible on those that applied to the Lower C-band transition. The NPRM also seeks comment on a range of issues associated with repurposing some portion of the Upper C-band, including: reallocation of the 4.0-4.2 GHz band; competitive bidding procedures for an eventual auction; licensing, operating, and technical rules for any new wireless services; (4) transitioning incumbent FSS operations; and promoting co-existence with adjacent band radio altimeters.","document_number":"2025-22020","html_url":"https://www.federalregister.gov/documents/2025/12/05/2025-22020/in-the-matter-of-upper-c-band-398-42-ghz","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-12-05/pdf/2025-22020.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-22020.pdf?1764855918","publication_date":"2025-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":"introduction of new, high-powered terrestrial <span class=\"match\">wireless</span> operations in the Upper C-band alongside a generational upgrade to radio altimeters that facilitates aviation safety through operations in the adjacent 4.2-4.4 GHz band that can safely coexist with <span class=\"match\">wireless</span> services. We therefore seek comment on proposals to enable terrestrial <span class=\"match\">wireless</span> operations in a segment of the Upper C-band in the contiguous United States, to reserve no more than 20 megahertz as a guard band between those <span class=\"match\">wireless</span> operations and <span class=\"match\">Fixed</span> Satellite Services (FSS), and to generally"},{"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":"this exception, an applicant <span class=\"match\">must</span> be a rural partnership providing service as of July 16, 2015, and each member of the rural partnership <span class=\"match\">must</span> individually have fewer than 250,000 combined <span class=\"match\">wireless</span>, wireline, broadband, and cable subscribers. Because each member of the rural partnership <span class=\"match\">must</span> individually qualify for the bidding credit, by definition, a partnership that includes a nationwide <span class=\"match\">provider</span> as a member will not be eligible for the benefit. \n Finally, a consortium of small businesses or rural service <span class=\"match\">providers</span> may seek an exception from the"},{"title":"Establishing the Digital Opportunity Data Collection; Modernizing the FCC Form 477 Data Program; Delete, Delete, Delete","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopted an Order that takes steps to streamline the processes associated with the Broadband Data Collection (BDC) and the National Broadband Map and alleviates unnecessary regulatory burdens on service providers and challenge process participants. The Order aligns reporting requirements for broadband availability and subscription data, expressly declines to adopt a proposal to require satellite providers to submit additional certifications and supporting data, streamlines the Fabric challenge process, adopts a maximally- streamlined process by which the BDC system automatically removes areas or locations that fail a verification or audit without requiring the provider to update its availability data after receiving notice of the failed verification or audit, and makes certain ministerial changes.","document_number":"2026-12766","html_url":"https://www.federalregister.gov/documents/2026/06/24/2026-12766/establishing-the-digital-opportunity-data-collection-modernizing-the-fcc-form-477-data-program","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-24/pdf/2026-12766.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12766.pdf?1782218725","publication_date":"2026-06-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":"DATA Act require <span class=\"match\">providers</span> to report the availability of <span class=\"match\">fixed</span> voice services. Adopting such a requirement would impose new burdens on certain <span class=\"match\">fixed</span> voice service <span class=\"match\">providers</span>, and we find that the record does not offer sufficient justification for this additional reporting that falls beyond both the scope and the purpose of the BDC and the NBM. \n \n No Additional Certifications and Supporting Data from Satellite <span class=\"match\">Providers</span>. \n We expressly decline to require the additional certifications and supporting data from satellite <span class=\"match\">providers</span> on which the Commission"},{"title":"Auction of Advanced Wireless Services (AWS-3) Licenses; Comment Sought on Competitive Bidding Procedures for Auction 113","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission or FCC) announces an auction of 200 licenses in the 1695- 1710 MHz, 1755-1780 MHz, and 2155-2180 MHz bands (collectively, the \"AWS-3\" bands). The Office of Economics and Analytics (OEA), jointly with the Wireless Telecommunications Bureau (WTB), also seeks comment in this document on the procedures to be used for this auction, which is designated as Auction 113.","document_number":"2025-04452","html_url":"https://www.federalregister.gov/documents/2025/03/20/2025-04452/auction-of-advanced-wireless-services-aws-3-licenses-comment-sought-on-competitive-bidding","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-03-20/pdf/2025-04452.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-04452.pdf?1742388309","publication_date":"2025-03-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":"eligibility for the rural service <span class=\"match\">provider</span> bidding credit on a service-by-service basis, and proposed in the \n 2025 AWS-3 NPRM \n that in any future auction of licenses in the AWS-3 bands, it would offer a 15% rural service <span class=\"match\">provider</span> bidding credit to any eligible rural service <span class=\"match\">provider</span>, as defined in 47 CFR 1.2110(f)(4)(i), that is not also claiming a small business bidding credit. Under 47 CFR 1.2110(f)(4)(i), entities providing commercial communications services to a customer base of fewer than 250,000 combined <span class=\"match\">wireless</span>, wireline, broadband, and cable"},{"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":"IP-based capabilities of the Lifeline and <span class=\"match\">wireless</span> <span class=\"match\">providers</span>' networks, which may impact <span class=\"match\">wireless</span> <span class=\"match\">providers</span>' ability to transmit georouting data with <span class=\"match\">wireless</span> 988 calls over non-IP networks. Therefore, the rules we adopt require nationwide and non-nationwide <span class=\"match\">providers</span> to provide georouting data <span class=\"match\">when</span> available and offer flexibility for <span class=\"match\">wireless</span> <span class=\"match\">providers</span> to work with the Lifeline Administrator on a case-by-case basis to address any individualized network considerations. We also provide non-nationwide <span class=\"match\">providers</span> an ample compliance deadline, as discussed"},{"title":"The Emergency Alert System and Wireless Emergency Alerts","type":"Rule","abstract":"In this document, the Federal Communications Commission (FCC or Commission) amends its regulations governing the Emergency Alert System (EAS) and Wireless Emergency Alerts (WEA) to add a new event code, MEP, to allow alert originators to issue an alert to the public about missing and endangered persons (MEP) whose circumstances do not meet the criteria of \"America's Missing: Broadcast Emergency Response\" (AMBER) alerts.","document_number":"2024-19530","html_url":"https://www.federalregister.gov/documents/2024/09/06/2024-19530/the-emergency-alert-system-and-wireless-emergency-alerts","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-09-06/pdf/2024-19530.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-19530.pdf?1725540316","publication_date":"2024-09-06","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":"licenses that would qualify as small under the SBA's small business size standard. \n \n 68. \n <span class=\"match\">Wireless</span> Communications Services. \n <span class=\"match\">Wireless</span> Communications Services (WCS) can be used for a variety of <span class=\"match\">fixed</span>, mobile, radiolocation, and digital audio broadcasting satellite services. <span class=\"match\">Wireless</span> spectrum is made available and licensed for the provision of <span class=\"match\">wireless</span> communications services in several frequency bands subject to part 27 of the Commission's rules. <span class=\"match\">Wireless</span> Telecommunications Carriers (except Satellite) is the closest industry with an SBA small business"},{"title":"Advanced Methods To Target and Eliminate Unlawful Robocalls","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) modifies its existing call blocking rules. Specifically, the Commission requires all domestic voice service providers to block based on a reasonable do-not-originate (DNO) list. Second, it requires voice service providers to return Session Initiation Protocol (SIP) code 603+ when calls are blocked based on reasonable analytics.","document_number":"2025-04811","html_url":"https://www.federalregister.gov/documents/2025/03/24/2025-04811/advanced-methods-to-target-and-eliminate-unlawful-robocalls","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-03-24/pdf/2025-04811.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-04811.pdf?1742561117","publication_date":"2025-03-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":"requiring all <span class=\"match\">providers</span>, including smaller <span class=\"match\">providers</span>, to use an expansive DNO list is unnecessary at this time. This is particularly true <span class=\"match\">when</span> all other <span class=\"match\">providers</span> in the call path <span class=\"match\">must</span> block. Some <span class=\"match\">providers</span> will use or already use these more expansive lists, and a single call will often pass through several networks on its path to the recipient. As a result, many consumers will be protected by these more comprehensive lists even <span class=\"match\">when</span> one <span class=\"match\">provider</span> in the call path uses a more restricted list. The Commission recommends that <span class=\"match\">providers</span>, <span class=\"match\">when</span> technically"},{"title":"Resilient Networks; Concerning Disruptions to Communications","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) modernizes the Disaster Information Reporting System (DIRS) to reduce reporting burdens on stakeholders and ensure that the information being collected is useful for disaster response. Our modernization allows manual filers to submit a single, dynamic form instead of multiple worksheets, and enables them to use a \"one-click\" option to easily indicate there is no change from the previous day's report. Further, unnecessary fields and worksheets will be eliminated to ensure that DIRS is collecting the information that is most important for emergency response. This modernization also eliminates the requirement for service providers to file a DIRS final report within 24 hours of DIRS' deactivation, and exempts non-facilities-based providers from DIRS reporting. This document also recognizes the emergence of public safety voice and broadband networks and the critical connectivity they provide to public safety stakeholders by requiring providers of these services to submit DIRS reports on the status of their public safety network infrastructure. Finally, we augment providers' ability to voluntarily submit geospatial information on infrastructure affected by disasters. Together, these changes provide public safety officials with the additional information they need, while also making it easier for service providers to satisfy their reporting obligations.","document_number":"2026-13155","html_url":"https://www.federalregister.gov/documents/2026/06/30/2026-13155/resilient-networks-concerning-disruptions-to-communications","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-30/pdf/2026-13155.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13155.pdf?1782737115","publication_date":"2026-06-30","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":"on whether to collect more granular information from <span class=\"match\">wireless</span> <span class=\"match\">providers</span> about the location of cell sites that are out of service. Whereas DIRS requires <span class=\"match\">providers</span> to specify the location of major equipment other than <span class=\"match\">wireless</span> cell sites, DIRS currently only requires <span class=\"match\">wireless</span> <span class=\"match\">providers</span> to complete a worksheet to specify the number of cell sites out by county. <span class=\"match\">Wireless</span> <span class=\"match\">providers</span>, however, have voluntarily submitted more granular information than DIRS requires about the location of their <span class=\"match\">wireless</span> cell sites. T-Mobile voluntarily provides cell site location"},{"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":"\n we believe that the majority of wireline internet access service <span class=\"match\">providers</span> can be considered small entities.\n \n \n 57. \n <span class=\"match\">Wireless</span> Broadband Internet Access Service <span class=\"match\">Providers</span> (<span class=\"match\">Wireless</span> ISPs or WISPs). \n <span class=\"match\">Providers</span> of <span class=\"match\">wireless</span> broadband internet access service include <span class=\"match\">fixed</span> and mobile <span class=\"match\">wireless</span> <span class=\"match\">providers</span>. The Commission defines a WISP as “[a] company that provides end-users with <span class=\"match\">wireless</span> access to the internet[.]” <span class=\"match\">Wireless</span> service that terminates at an end user location or mobile device and enables the end user to receive information from and/or send"},{"title":"Requirements for Interference-Tolerant Radio Altimeter Systems","type":"Proposed Rule","abstract":"In July 2025, President Trump signed the One Big Beautiful Bill Act. Section 40002 of that law re-institutes the Federal Communications Commission's general auction authority and specifically directs the Commission to complete a system of competitive bidding for not less than 100 megahertz in the 3.98-4.2 gigahertz band (Upper C- band). To ensure safe, efficient, and reliable aviation operations in the presence of wireless signals in the Upper C-band, the Federal Aviation Administration is proposing new regulations that would require all radio altimeters to meet specific minimum performance requirements. These new radio altimeters must withstand interference from wireless signals in neighboring spectrum bands and continue to provide accurate altitude readings to both pilots and integrated aircraft safety systems. The minimum interference tolerance requirements proposed in this rule reflect the best achievable interference rejection using current technology without compromising radio altimeter system performance. These regulations would require all aircraft equipped with radio altimeters operating under part 121 and those aircraft with radio altimeters operating under part 129 with 30 or more passenger seats or a payload capacity of more than 7,500 pounds to comply with the minimum performance requirements by the date the Federal Communications Commission authorizes wireless services in the Upper C-band. All other aircraft equipped with radio altimeters would be required to comply with the same minimum performance requirements two years later. This proposed rule is a companion to the Federal Communications Commission's NPRM to expand the ecosystem for next-generation wireless services in the 3.7-4.2 gigahertz band by making as much as 180, and at least 100, megahertz of the Upper C-band available for terrestrial wireless flexible use via a system of competitive bidding.","document_number":"2026-00051","html_url":"https://www.federalregister.gov/documents/2026/01/07/2026-00051/requirements-for-interference-tolerant-radio-altimeter-systems","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-01-07/pdf/2026-00051.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-00051.pdf?1767647706","publication_date":"2026-01-07","agencies":[{"raw_name":"DEPARTMENT OF TRANSPORTATION","name":"Transportation Department","id":492,"url":"https://www.federalregister.gov/agencies/transportation-department","json_url":"https://www.federalregister.gov/api/v1/agencies/492","parent_id":null,"slug":"transportation-department"},{"raw_name":"Federal Aviation Administration","name":"Federal Aviation Administration","id":159,"url":"https://www.federalregister.gov/agencies/federal-aviation-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/159","parent_id":492,"slug":"federal-aviation-administration"}],"excerpts":"aircraft <span class=\"match\">when</span> the aircraft is overhead, and the RA antenna would typically have low gain towards the base station <span class=\"match\">when</span> the aircraft is adjacent to a <span class=\"match\">wireless</span> base station. Multipath can increase or decrease the received signal strength, though not typically within the maximum antenna spot beam. While the duty cycle of the base station is limited based on the next-generation <span class=\"match\">wireless</span> technology, FAA seeks to adopt an RA system requirement regardless of the <span class=\"match\">wireless</span> service technology to be used. The motion of the aircraft, as compared to a <span class=\"match\">fixed</span> wireless"},{"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":"for <span class=\"match\">Wireless</span> 911 Calls, \n PS Docket Nos. 21-479 and 18-64, Report and Order, FCC 24-78, 2024 WL 3507091 at *12, para. 29 (Jul. 19, 2024), 89 FR 78066 (Oct. 17, 2024) (\n NG911 Transition Order \n ).\n \n \n \n • \n Covered 911 Service <span class=\"match\">Providers</span>. \n First, we propose to update the definition of “covered service <span class=\"match\">provider</span>” in the Commission's existing 911 reliability rules to specify how the rules apply to service <span class=\"match\">providers</span> that control or operate critical pathways and components of NG911 networks.\n \n \n ○ The current CSP definition focuses on <span class=\"match\">providers</span> of certain"}]}