Oasis Industrial CPE · Version 0.9 Draft

Oasis, in technical detail.

The Oasis is the deployed form of ORB-C1: a client of the site network and a coverage point in its own right, engineered so that a fleet in motion densifies the network wherever the work happens to be.

Architecture

Two roles, one baseband.

Client and access functions share programmable silicon and a single scheduler. That is what makes simultaneous termination and re-emission a design property rather than a workaround.

  • The client side takes policy, band selection, and slice assignment from the serving ORB.
  • The coverage side is scheduled on the same baseband, so uplink and re-emission never fight for the same slot.
  • Session continuity across the TVWS and CBRS transition is make-before-break, so coverage does not blink when the machine moves.
  • One firmware tree across the whole radio estate: the same software plane as the ORB, with the same slicing model.
  • Where no ORB is present, standalone mode backhauls over LEO, carrier cellular, or a wired handoff on identical hardware.

Uplink

How it reaches the ORB.

Four return paths, selected by policy rather than by hand. The client keeps the best available path and falls back in order as terrain and distance change.

Oasis uplink options
PathBandPropagation characterWhere it is used
TVWS-LTE client470 to 608 MHzNon-line-of-sight, into pits and behind structuresPrimary uplink where the machine has no clear path to the ORB
CBRS NR client3550 to 3700 MHzNear line-of-sight, high capacityPrimary uplink inside the trailer and site zones
5.8 GHz transportUnlicensed 5 GHz upperLine-of-sight, alignedFixed-Mount units acting as a relay hop or a remote coverage island
HaLow return902 to 928 MHzLong range, low rateTelemetry and management continuity when broadband uplinks are unavailable

Coverage

What each kit projects.

Coverage geometry is a function of the kit, its mounting height, and the populated radios. Figures are engineering objectives for RFQ response, not guarantees.

Coverage geometry by kit
KitEmissionScaleServed population
Machine-MountWi-Fi 7 class, 2.4, 5, 6 GHzCrew-scale, tens of metres around the machineDevices, tools, and vision cameras at the point of work
Machine-MountCBRS relay small cellHundreds of metres, terrain dependentCarrier phone service where the fleet is working
Fixed-MountWi-Fi plus HaLowOffice, yard, and long-range sensor tailTrailer, laydown yard, gate and perimeter cameras
PortableWi-Fi plus NR+Work-cell scale, rapid deployCrews working detached from the fleet, inspections, shutdowns
All kitsNR+ mesh, 1.9 GHzMachine-to-machine, mesh-extended across the fleetProximity, interlocks, and stop-class signaling

Deterministic tier

The safety mesh rides with the fleet.

Fleet coordination shares no fate with bulk data. The property is intended to be citable directly in an autonomy safety case.

  • NR+ is normative on every unit, so mesh density tracks the fleet and is highest where machines and people interact.
  • The 1.9 GHz DECT band is reserved by regulation, so coordination never contends with site data, Wi-Fi, or ISM traffic.
  • Machines mesh directly, with no ORB in the loop, and rejoin the site network and the ledger when connectivity returns.
  • E-stop class signaling runs on a 1 ms slot structure at URLLC-class latency.
  • Saturating the access tiers, or heavy CBRS contention, leaves fleet coordination untouched.

RF engineering

Self-interference is the hard part.

A compact steel-mounted platform carrying a client, a relay cell, Wi-Fi, HaLow, NR+, and a 2.4 GHz multiprotocol radio has to keep every one of them usable at once.

Budget 1

Frequency separation between the

Frequency separation between the CBRS client and the CBRS relay under SAS grant.

Budget 2

Antenna placement and separation

Antenna placement and separation per the mounting annex for the machine family.

Budget 3

Coordinated scheduling across the

Coordinated scheduling across the coverage stack on the shared baseband.

Budget 4

Relay radiation suspends whenever

Relay radiation suspends whenever geolocation or grant authorization cannot be maintained.

Power and environment

Park mode is a requirement, not a feature.

A parked machine with standby power stays a coverage point at reduced duty, so overnight and shift-change coverage does not collapse with the fleet at rest.

Oasis power classes
KitPrimary powerRequirements
Machine-MountVehicle 12 and 24 VLoad-dump and transient immunity to heavy-equipment norms, wake-on-ignition, graceful shutdown, optional standby battery for park mode
Fixed-MountMains, PoE++, or solar hybridPoE budget stated per populated radio set, solar profile shared with the platform specification
PortableIntegrated batteryFull-shift runtime at reference duty cycle, hot-swap or vehicle charging

Annex M

Machine-Mount

Vibration and shock per heavy-equipment norms, ingress and washdown rating, antenna placement per machine family, cable entry and ECM integration, and GNSS position for relay-grade location integrity.

Annex F

Fixed-Mount

Pole, trailer, and container brackets, alignment provisions for units backhauling over the 5.8 GHz transport tier, grounding and surge protection.

Annex P

Portable

Case drop and ingress rating, rapid-deploy antenna arrangement, and battery transport compliance.

Commissioning and conformance

Installed by the crew that runs it.

Non-specialist installation is held to conformance per kit, and every unit is a full participant in the coordination ledger from the moment it attaches.

  • Plug-and-play commissioning by a dealer technician or a superintendent, with no RF specialist on site.
  • Kit-specific mechanical install, then power, then automatic attach to the serving ORB and policy download.
  • No manual channel planning: band selection, grants, and coverage parameters come from the coordination layer.
  • Every attachment, grant event, and position record is written to the ledger through the serving ORB.
  • FCC Part 15 Subpart C, for HaLow, 2.4 GHz, and Thread.
  • FCC Part 15 Subpart E, for the 5 and 6 GHz client and AP functions.
  • FCC Part 15 Subpart H, for the TVWS client.
  • FCC Part 96, for the CBRS client and, where populated, the CBRS relay as a CBSD.
  • DECT band provisions for the NR+ tier.
  • CPE-specific cases: band-transition continuity, relay grant behavior under movement, self-interference limits, park-mode behavior, and non-specialist installation per kit.

Scope an Oasis fleet.

Tell us what you run and where you run it. We will size the kits, the uplinks, and the coverage plan, or send the documents for engineering review.