Coverage plane
TVWS
Sub-600 MHz propagation guaranteeing the site is never dark, carrying LTE under white space database coordination.
OSI-ORB-TR3 · Version 0.9 Draft
Nine radios, read as one system.
The band plan is usually presented as a list. Its performance is better understood as a structure: a managed spine of three coordinated planes, wrapped in an access periphery of commodity tiers, with a transport profile stitching units together. The envelope is the composition, not the sum.
Section 1
A three-plane spine.
The spine is the three bands whose interference is managed on open terms: TVWS under PAWS coordination, CBRS under SAS coordination, and DECT NR+ in spectrum reserved by regulation for one technology. It is IMT-standard end to end.
Capacity plane
CBRS
150 MHz of mid-band carrying the tonnage, running 3GPP 5G NR under SAS coordination with operator-controlled framing.
Control plane
DECT NR+
Deterministic, reserved, and congestion-immune by construction. A licensed carrier network is built from the first two planes; no carrier offers the third, because no licensed band is reserved for it.
The periphery meets devices where they are: Wi-Fi 7 across 2.4, 5, and 6 GHz for the universal device population, HaLow for long-range sensing, Thread and BLE for the person-scale periphery, and LTE-M as the provisioning lifeline riding carrier macro networks. The 5.8 GHz transport profile links units into federations, so every figure here scales from one unit to a corridor.
Section 2
The band reference table.
Realistic throughput, range class, latency class, and the job each band actually does.
| Band | Spectrum | Realistic throughput | Range class | Latency class | Job |
|---|---|---|---|---|---|
| TVWS, coverage plane | 470-608 MHz, 6 MHz channels | 30-75 Mbps bonded; to 150 Mbps ceiling | 10+ km NLOS | Tens of ms | The site is never dark |
| CBRS n48, capacity plane | 3550-3700 MHz | 300-900 Mbps today; approx. 1.8 Gbps ceiling | 1-2 km | Single-digit ms with URLLC scheduling | The tonnage: video, scans, mobile machines |
| DECT NR+, control plane | 1920-1930 MHz (US) | 2-3 Mbps today; 45-95 Mbps full-spec | Site-wide via mesh | 1 ms slots, sub-5 ms class | Safety, C2, everything that must never wait |
| Wi-Fi 7, 5 and 6 GHz | Up to 1,200 MHz under AFC | 1.5-3 Gbps near field; approx. 5 Gbps ceiling | 0.3 km phones; 2 km with arrays | Milliseconds, best effort | Every device everyone already owns |
| Wi-Fi 2.4, Thread, BLE | 2400-2483.5 MHz | Legacy and periphery rates | Near field | Best effort | Legacy access, Matter, tags and beacons |
| HaLow | 902-928 MHz | 25-65 Mbps | 2-3 km | Best effort | Long-range cameras and sensors |
| LTE-M | Carrier macro networks | Sub-Mbps class | Wherever carriers reach | Not latency-relevant | Born-connected provisioning, out-of-band lifeline |
| Transport, 5.8 GHz | 5725-5850 MHz PtP | 0.5-1 Gbps per hop | 5-15 km aimed links | Milliseconds | Federation backhaul, corridor chaining |
Every band above is license-free or database-coordinated. Band n53, 2483.5 to 2495 MHz, is the one licensed option: an optional 30 to 45 Mbps protected floor beneath the three planes, populated per deployment and never part of the shipped combined-band envelope.
Section 3
The zone envelope.
Delivered capacity is a function of distance from the mast, composed so every zone is served by the tier physics favors there. Figures are per Flagship sector under representative conditions.
| Zone | Distance | Serving tiers | Combined capacity | Of which uplink |
|---|---|---|---|---|
| Near field | 0-300 m | Wi-Fi 7 + CBRS | 2-4 Gbps | approx. 1-1.5 Gbps |
| Site field | 0.3-2 km | CBRS + high-gain Wi-Fi arrays | 1-2.5 Gbps | 300-500 Mbps on CBRS alone |
| Tail | 2-10+ km | TVWS + HaLow | 30-100 Mbps | Symmetric by configuration |
| Control plane | Site-wide, all zones | NR+ mesh | 2-3 Mbps today; 45-95 Mbps full-spec | Symmetric, deterministic |
Property one
Flat where others cliff
A single-technology network is fast until it is nothing. The ORB envelope degrades through four tiers before reaching the TVWS floor, and the floor extends past 10 km.
Property two
The uplink is the headline
Operator-controlled TDD frames convert the capacity plane into 300 to 500 Mbps of sustained upload, the direction site traffic actually flows, and a figure no carrier-configured network provides.
Property three
The control plane is orthogonal
Its latency and availability are independent of every number above it, because it shares neither spectrum nor fate with the data tiers.
Section 4
What the composition does that no tier does alone.
Six behaviors that only exist because the tiers are coordinated by one platform with the same silicon on both ends of every link.
- Coverage with a floor and a ceiling. CBRS and Wi-Fi provide the ceiling, TVWS provides the floor, and the steering plane moves flows between them silently. A device experiences one network whose speed varies with position but whose existence does not.
- Guaranteed delivery classes without licenses. Deterministic, assured, and best effort, all from open spectrum. A traffic policy, not a spectrum purchase, decides which class a flow receives.
- Session continuity across physics. A machine leaving CBRS range slides onto TVWS without re-authentication, and back, and across federated units at vehicle speed. The band transition is the platform's problem, not the application's.
- Every device class served natively. Phones on Wi-Fi and neutral-host CBRS on their own carriers, commodity IoT over Matter, Thread, and BLE, industrial sensors over HaLow, machines over the spine, aircraft over the control plane.
- A network that proves itself. Every grant, every attachment, and every path assignment lands in one ledger, so compliance and behavior are queryable site-wide, including for radiators that move.
- Failure that subtracts instead of severing. Capacity degrades toward the floor, the control plane persists on reserved spectrum, management persists on LTE-M, and federation re-pools WAN paths. No single loss darkens a site.
Section 5
Traffic-to-tier mapping.
Each site workload has a primary tier, a fallback, and a delivery class. The policy layer, not the hardware, assigns them.
| Site workload | Primary tier | Fallback | Delivery class |
|---|---|---|---|
| E-stop, proximity interlock, fleet C2 | NR+ control plane | None needed; mesh survives infrastructure loss | Deterministic |
| Drone command link | NR+ control plane | Spine handover per aerial profile | Deterministic |
| Machine telemetry, grade control | CBRS with URLLC scheduling | TVWS | Deterministic to assured |
| Photogrammetry, scans, vision uploads | CBRS uplink-heavy frames | Wi-Fi arrays near field | Assured |
| Live site video | CBRS | Wi-Fi 6 GHz | Assured |
| Office, BIM, personal devices | Wi-Fi 7 | CBRS neutral host | Best effort |
| Long-range cameras, remote sensors | HaLow | TVWS | Best effort |
| Trailer IoT, locks, power, tags | Thread, Matter, BLE | Wi-Fi | Best effort |
| Commissioning, heartbeat, recovery | LTE-M | BLE, NR+ adoption | Lifeline |
Section 6
Scaling the envelope.
Sectorization multiplies the near and site fields: a three-sector Flagship delivers 6 to 10 Gbps of site aggregate today, with shared-spectrum grants as the ceiling's governor, and the composed uplink approaches 2 Gbps.
- Federation extends every figure along a corridor: interlocking spectrum plans mean each added unit adds its envelope rather than colliding with its neighbor's.
- Sessions span units at vehicle speed, so a machine moving down a haul road or a corridor never re-authenticates.
- One or two WAN paths serve the whole chain, with the edge-compute tier keeping the experience local regardless.
Check the numbers against your site.
Give us the geometry, the distances, and the workloads, and we will map them onto the zone envelope and tell you which tier carries what.