OSI-ORB-1 · Version 0.9 Draft

ORB-1, the platform.

The operating standard for license-free, database-coordinated, multi-band site networks: a transportable, self-coordinating base station that assumes nothing about the site, upward or outward.

Section 2

The normative band plan.

A conforming unit implements the operating bands below plus the transport profile. Frequencies are US allocations; international profiles are future annexes. Per-band EIRP follows the applicable FCC rule part, or the value granted by the coordination service.

ORB-1 normative band plan
BandFrequencyWaveformCoordinationRole
TVWS470 to 608 MHzLTE carrierPAWS white space databaseLong-reach tail, 10+ km
HaLow902 to 928 MHz802.11ahListen-before-talk, Part 15.247Mid tail, 2 to 3 km, IoT
DECT NR+1880 to 1900 and 1920 to 1930 MHzETSI DECT-2020 NRBand-native channel selectionDeterministic mesh, safety and control
CBRS (n48)3550 to 3700 MHz5G NR carrierSAS, Part 96 GAA, PAL optionalPrimary capacity, mobile and QoS traffic
Wi-Fi 2.4 GHz2400 to 2483.5 MHz802.11Listen-before-talkLegacy device access, near field
Thread2400 to 2483.5 MHzIEEE 802.15.4Listen-before-talkMatter border router, IoT periphery
BLE and BLE Mesh2400 to 2483.5 MHzBluetooth LE, multiprotocol with ThreadListen-before-talkWorker tags, asset beacons, commissioning
Wi-Fi 5 GHz5150 to 5895 MHz802.11 Wi-Fi 7U-NII rules, DFS where applicableHigh-capacity access
Wi-Fi 6 GHz5925 to 7125 MHz802.11 Wi-Fi 7AFC, standard power outdoorHighest-capacity access
Transport5725 to 5850 MHz802.11 PtP profilePart 15.247 PtP provisionsInter-unit and POP backhaul

TVWS and CBRS form the cellular complex on the programmable baseband. HaLow, NR+, Wi-Fi, and Thread run on merchant modules. TDD frame configuration on the CBRS carrier is operator-settable and supports uplink-heavy profiles.

Band n53, 2483.5 to 2495 MHz, is not in the normative plan. It is an optional licensed floor populated per deployment, and conformance never requires licensed spectrum.

Section 3

Radio subsystem architecture.

Baseband silicon is a sourcing decision, not an architectural one.

3.1 Mezzanine

Swappable baseband

The TVWS-LTE and CBRS-NR carriers run on a programmable baseband on a removable mezzanine. The interface is normative: PCIe and multi-gigabit Ethernet, fronthaul at a defined O-RAN functional split, timing input, and a published mechanical envelope.

3.1 RF chains

Per-carrier chains

Each cellular carrier has a dedicated transceiver front end, power amplification with digital predistortion, and filtering to the ORB-A1 isolation masks. CBRS supports 4x4 MIMO, 100 MHz occupied bandwidth, and 256-QAM both directions. TVWS bonds non-contiguous 6 MHz channels as granted.

3.2 Modules

Merchant radios in standard slots

HaLow, NR+, Wi-Fi, and Thread come from certified merchant modules in M.2, mini-PCIe, or SDIO slots, each independently replaceable and driven natively by the host. Wi-Fi is Wi-Fi 7 class with 320 MHz channels at 6 GHz and multi-link operation.

3.2 Periphery

Thread and BLE from one radio

A concurrent-multiprotocol 802.15.4 module with an OpenThread Border Router is a standard populate on both SKUs, making every ORB Matter-capable, and providing BLE and BLE Mesh for worker tags, asset beacons, and commissioning from the same silicon.

Section 4

Host and software plane

An ARM-class compute complex on an OpenWrt-based OS carries the lightweight 5G core, the flow steering and QoS engine, slicing and tenancy, Passpoint and OpenRoaming, the coordination layer, and a management plane over open APIs.

Section 4

Edge compute classes

Class A carries local compute and storage for capture workloads, photogrammetry, scan registration, and video analytics, so the WAN carries results rather than raw capture. Class B omits the tier with identical software interfaces, keeping paths, tenants, and policies portable.

Section 5

The coordination layer.

The defining subsystem. Three database regimes, one client architecture, one record store, so spectrum compliance becomes a queryable property of the network rather than a paper exercise.

  • A PAWS-compliant white space client for TVWS, a SAS client for CBRS under Part 96, and an AFC client for standard-power 6 GHz, behind one client architecture.
  • Each client obtains grants for every radiating device, at its geolocation, for its authorized power and channels, and renews or releases them as the regime requires.
  • Every grant, renewal, denial, and release is recorded with device identity, location, band, power, and time in a distributed, tamper-evident ledger.
  • The same record pattern extends to neutral-host attachment sessions and WAN path assignment.
  • An audit query interface is normative, exposed to operators and tenants, and under operator control to regulators, insurers, and equipment partners.
  • The ledger interface is published, so third parties can implement, verify, and interoperate with it.

Section 6

WAN and transport.

Multi-WAN by architecture. Any subset of the four path classes may be populated per site, and all may be active at once under a single steering policy.

ORB-1 WAN path classes
Path classMediumTypical capacityTypical role
LEO satelliteFlat-panel terminal in the WAN bay100 to 400 Mbps down, less upThe anywhere path, default greenfield WAN
5.8 GHz transportPoint-to-point dish per ORB-A10.5 to 1 Gbps per hopCorridor chaining, shared WAN across units
Wired handoffFiber or Ethernet demarcation at the unitAs provisionedSites with existing service at the gate
Carrier cellularOne or two macro-network modemsMarket dependentBackhaul where macro coverage exists

Steering

Per-flow policy

Traffic classes and tenant slices map to path classes, with health probing and sub-second failover. Deterministic control traffic prefers the lowest-latency healthy path; bulk synchronization can be scheduled off-peak.

Bonding

Beyond one path

MPTCP or tunnel-level bonding serves single-flow workloads that exceed any one path. Per-flow steering is the default; per-packet striping is used only where the reordering cost is justified.

Topology

Chain, ring, branch

Multi-unit topologies over the transport profile are normative for linear deployments, including shared use of one or two LEO uplinks across a corridor of units. The WAN bay is vendor-neutral.

Sections 7, 8, 10

Neutral host, timing, tenancy.

Three subsystems that make the unit usable by many organizations, and defensible on the record.

Section 7

Licensed networks ride the open one

On CBRS, a neutral-host profile under the OnGo shared-HNI framework with MOCN support in the core. On Wi-Fi, Passpoint and WBA OpenRoaming offload. Sessions are accounted per tenant and per carrier, and attachment records go to the ledger.

Section 8

GNSS-disciplined timing

Time and frequency distribute over PTP to the cellular complex and any subsystem needing synchronization. CBRS TDD sync meets Part 96 and SAS coexistence. The unit detects and alarms on loss or implausible movement of its position fix.

Section 10

Per-organization slices

Slices span the RAN, the access tier, and the WAN, each with its own authentication, QoS, WAN path policy, and accounting. SSID and VLAN mappings bind into the same framework, and per-slice records are written to the ledger.

Section 12

SKU framework.

Both SKUs derive from one board architecture through populate and depopulate decisions. No SKU decision alters the software plane, the coordination layer, or the conformance interfaces.

ORB-1 SKU framework
AttributeFlagshipCompact
SectorsThree 120-degree sectorsOne sector, aimed along the site long axis
Conformance classClass A, edge compute and storageClass B, interfaces only
CBRS configuration4x4 MIMO per sector, uplink-heavy TDD available4x4 MIMO, uplink-heavy TDD available
Antenna systemThree integrated panels per ORB-A1One integrated panel per ORB-A1
WAN populationFull path complement typicalMinimal population typical, all interfaces present
Target deploymentAutonomy sites, large jobs, corridor anchorsSmall and mid-size jobs, corridor infill

Section 13

Performance targets.

Informative engineering objectives for a Flagship unit under representative conditions, stated per the three-zone model that reflects how capacity is actually delivered across a site.

ORB-1 performance targets
ZoneRangeDominant tiersTarget capacity
Near field0 to 300 mWi-Fi 5 and 6 GHz, CBRS2 to 4 Gbps aggregate
Site field0.3 to 2 kmCBRS, high-gain Wi-Fi arrays1 to 2.5 Gbps aggregate, 300 to 500 Mbps uplink on CBRS
Tail2 to 10+ kmTVWS, HaLow30 to 100 Mbps combined, degrading gracefully, never to zero
Deterministic tierSite-wideNR+ mesh, URLLC scheduling on CBRSSub-5 ms latency class

Per-sector aggregate for a Flagship unit is targeted at 2.5 to 5 Gbps with current silicon, and 7 to 8 Gbps at full-specification silicon ceilings. Three-sector site aggregate is targeted at 6 to 10 Gbps, subject to shared-spectrum grants.

Sections 9 and 11

Mechanical and conformance.

Reference form factors are trailer-mounted, palletized, and skid-mounted. The mast and guying system carries the antenna panel, roughly 2.6 to 3.0 m and 25 to 40 kg per sector, at full wind-load rating. Power profiles cover shore power, generator, and solar-hybrid.

  • FCC Part 15 Subpart C, for HaLow, 2.4 GHz, and the 5.8 GHz transport profile.
  • FCC Part 15 Subpart E, for 5 GHz and 6 GHz U-NII including AFC procedures.
  • FCC Part 15 Subpart H, for TVWS.
  • FCC Part 96, for CBRS, plus the DECT band provisions applicable to NR+.
  • Conformance claimed per class, A or B, and per populated option set, verifiable by any party from the published suite.

Read it in full.

ORB-1 v0.9 is available for partner and engineering review, with the conformance suite alongside it.