CBRS is the reason you can deploy a private cellular network in your facility without becoming a licensed spectrum holder. Since the FCC opened the Citizens Broadband Radio Service band in 2020, thousands of industrial operators have deployed private LTE and private 5G NR on 3.5 GHz spectrum without going through the traditional carrier licensing process. Here is a plain-language explanation of how the system works — and what your operations team needs to understand to manage it day-to-day.
What spectrum CBRS uses
CBRS operates in a 150 MHz swath of the 3.5 GHz band (3550–3700 MHz), divided into 15 channels of 10 MHz each. It is mid-band spectrum — better building penetration than mmWave, better throughput capacity than low-band spectrum. For most industrial facility sizes (50,000–500,000 sq ft), 3.5 GHz propagates well enough to cover the space with a reasonable gNodeB count. Rule of thumb for indoor manufacturing environments: expect to achieve a usable SINR of 15 dB at distances of 30–60 m from a ceiling-mounted Category A cell, adjusted downward for steel rack rows and concrete pillars.
The 3.5 GHz band was previously used by the US Navy for fixed coastal radar systems. The CBRS framework was designed so that commercial users can access this spectrum without interfering with incumbent federal users. The mechanism that makes this possible is the Spectrum Access System — a cloud-based frequency coordination layer that every CBRS radio must register with before transmitting.
The three-tier priority structure
CBRS uses a tiered sharing framework. Understanding the tiers determines what kind of spectrum access you have and how it affects both your deployment planning and your ongoing operational risk.
Tier 1 — Incumbent Access Users (IAU). Federal systems, primarily US Navy radar. These users have absolute first priority. The SAS is aware of all incumbent operations and creates protection zones — geographic exclusion areas where commercial users cannot transmit at the incumbent's operating frequencies. Coastal facilities within radar protection zones may find certain channels unavailable or restricted to lower transmit power levels. Your SAS will report which channels are available at your registered coordinates.
Tier 2 — Priority Access License (PAL). PALs are 10-year, 10 MHz licenses assigned through FCC auctions, on a county-by-county basis. A PAL holder has exclusive rights to their assigned channel within their licensed area, subject only to Tier 1 protection. PAL licenses are registered in the SAS and protected against interference from Tier 3 users. Importantly, PAL grants do not guarantee the channel is free of all interference — they guarantee that other commercial users operating below PAL tier cannot claim priority over you.
Tier 3 — General Authorized Access (GAA). GAA is license-exempt. Any CBRS-compliant device can use GAA spectrum without filing for a PAL, as long as it registers with a certified SAS. GAA users must protect Tier 1 and Tier 2 operations and cannot claim interference protection from other GAA users. For most industrial deployments, GAA is sufficient — but the lack of interference protection between GAA users is the key operational risk to understand.
PAL vs. GAA: which is right for your facility?
Most industrial deployments operate on GAA, and most of them work well. If your campus is in a low-to-moderate density area — a suburban or rural industrial park rather than a dense urban warehouse district — GAA channels are typically lightly loaded and you get stable access without the complexity of PAL licensing.
The case for acquiring a PAL is interference protection. If your facility shares an industrial park with other manufacturers or logistics operators also deploying private cellular, and you're all operating on GAA, you have no formal recourse if a neighbor's deployment interferes with your channels. A PAL gives you a legal and technical basis for a SAS-mediated interference resolution — the neighboring GAA user must defer to your PAL channels.
PALs are sold per county at FCC auctions. For a single-campus facility in a suburban county, the cost-benefit typically favors GAA unless you have specific interference concerns. For an urban distribution center operating in a dense industrial park where you can identify other active CBRS deployments within 500 m, PAL is worth the analysis. The operational break-even is roughly: if you'd spend more than one shift per quarter troubleshooting GAA channel contention, a PAL pays for itself in engineering time.
We're not saying GAA is unreliable — for the majority of industrial deployments it works without issue. The distinction matters only when you need a contractually accountable spectrum position, or when your facility's environment already shows signs of channel contention from neighboring users.
The role of the SAS
Every CBRS radio in your facility — whether CBSD Category A or Category B — must be registered with a certified SAS before it transmits. SAS registration is not a one-time application; it's an ongoing dynamic relationship. The SAS grants spectrum assignments (called Grants) that specify the channel, transmit power ceiling, and expiration time. Grants renew automatically under normal conditions — your radios handle the WINNF.TS.0016 SAS-CBSD protocol without operator intervention.
The SAS ecosystem has multiple FCC-certified operators. Your CBRS equipment vendor typically bundles SAS connectivity with their hardware subscription. As an operator, you will not directly interact with the SAS, but you need to understand what happens when a Grant is revoked.
Consider this scenario: a distribution center in a coastal county is running 14 Category A cells on GAA. The facility is 40 km from a Navy radar installation. During a scheduled Navy exercise, the SAS expands the protection zone and revokes Grants on three of the facility's cells. Those three cells go dark within 60 seconds of the revocation. The AGVs operating under those cells lose connectivity, trigger emergency stops, and require manual restart. From the fleet management system's perspective, it looks identical to a hardware fault — the cells are simply unreachable.
This is not a theoretical edge case. It is a real operational risk for facilities near incumbent radar zones, and it illustrates why your monitoring layer needs to understand the CBRS construct. A cell going dark because of a Grant suspension requires a different response than a cell going dark because of a power failure. Grant suspensions are typically temporary — the SAS will issue a new Grant when the protection zone contracts. A hardware fault requires dispatch. Without control-plane visibility into Grant status, your ops team is troubleshooting blind.
CBRS device categories: A vs. B
CBRS devices are classified by transmit power capability:
- Category A (CBSD-A): Maximum 30 dBm EIRP. Designed for indoor use. This covers virtually all enterprise and industrial small cell access points used in manufacturing and logistics deployments. Indoor CBRS deployments are almost entirely Category A.
- Category B (CBSD-B): Up to 47 dBm EIRP. Designed for outdoor macro coverage. Used for outdoor yard coverage, perimeter monitoring sites, and distributed campus deployments that span buildings. Requires professional installation and precise antenna registration with the SAS — the SAS uses the registered antenna coordinates and orientation to calculate interference geometry with incumbent users.
For a standard manufacturing facility or distribution center, you will be deploying Category A CBSDs. If your deployment includes an outdoor staging yard or an inter-building coverage requirement, Category B for those specific locations makes sense — but the registration process is more rigorous and the SAS may impose lower power limits than the category maximum depending on your proximity to incumbent zones.
What the FCC filing actually involves
Deploying on GAA spectrum does not require an FCC license application. You register your CBSDs with a SAS, and the SAS handles compliance automatically. Your equipment vendor or integration partner handles SAS registration as part of commissioning — it's part of the cell bring-up procedure, not a separate administrative process.
If you pursue a PAL, the path goes through FCC spectrum auctions (Auction 105 was the initial CBRS PAL auction in 2020; subsequent auctions cover available spectrum as licenses expire or new spectrum is cleared). PAL registration after winning an auction requires an FCC Form 601 submission via the Universal Licensing System. This is administratively manageable but benefits from a spectrum consultant or your RAN vendor's licensing team if you haven't done it before — the SAS needs to be updated with your PAL channel and county assignment before your radios can operate at PAL priority.
CBRS vs. licensed spectrum: the practical control difference
Some operators access 3.5 GHz spectrum through a carrier partnership under the carrier's existing Band 48 license. The carrier manages the SAS relationship and takes on the compliance obligation. This can reduce operational overhead for teams without RF spectrum expertise.
The trade-off is control. Under a carrier arrangement, the carrier typically constrains your cell configuration options, sets your transmit power budgets, and may limit your ability to request SAS channel reassignment when you identify a local interference problem. For industrial operators who need to tune the network aggressively to their specific interference environment — adjusting uplink power per zone, requesting alternate channel assignments when a plasma cutter creates a predictable interference window — direct CBRS access under GAA or your own PAL gives you the configuration freedom that carrier-managed spectrum does not.
What your operations team needs to track
Once your CBRS deployment is live, three things need ongoing attention at the spectrum layer:
- Grant status per cell. Each CBSD holds one or more Grants from the SAS. A Grant includes the assigned frequency, transmit power ceiling, and expiration time. Your monitoring layer should log Grant suspensions and revocations separately from RF degradation events — they require different responses and have different resolution timelines.
- Channel utilization across your GAA channels. If neighboring GAA users expand onto channels you rely on, your uplink SINR may degrade before you see a cell alarm. Channel-level utilization monitoring provides early warning of creeping interference from other deployments — detectable as a gradual noise floor elevation rather than a sharp SINR drop.
- SAS heartbeat continuity. CBSDs maintain a periodic heartbeat with the SAS. If the SAS connection drops — network outage, SAS provider maintenance — the CBSD enters a hold state and eventually ceases transmission. Your monitoring should alert on SAS connectivity loss as a distinct event class, not categorize it under general cell alarm conditions.
None of this requires daily RF engineering intervention to manage. But it does require that your network management layer understands the CBRS construct and can distinguish between the three ways a cell can go dark: hardware fault, coverage gap, and Grant suspension. A generic NMS that only monitors cell RF metrics will miss the third category entirely — and that's the one with the most confusing symptom pattern.