Headroom
Product · Load

Hidden load. From counters.

Per-class offered load on each cell, estimated from standard counters, with an interval, or a refusal when the counters cannot tell.

The demoThe numbers
1

Load per class: polls, alarms, push-to-talk, video

2

Intervals on every estimate

3

“Not identifiable” when per-class counters are missing

Hands on

Three steps.

2

Counters in, load out, the ramp

Now showingA steady day 450 MHz LTE, 5 MHz (25 RB). 1,266 RTUs polled every 5 s, 156 radios, 30 cameras.
Resource blocks used, per 15 minutes · uplink · downlinkSimulated cell
EVENT−120′−105′−90′−75′−60′−45′−30′−15′+15′+30′0%50%100%
Load per class, from the counters
SCADA polls
243 kbps
Alarm bursts
8 kbps
Push-to-talk
233 kbps
Event video
3.8 Mbps
Pump cards
28 kbps
Crew data
2.5 Mbps
Ramp the load
SCADA pollsholds
Alarm burstsholds
Push-to-talkholds
Event videoholds
Pump cardsholds
Headroom says

Push-to-talk breaks first, at 2× (2×–2.5×)

Load per class from the cell's own counters, ramped on the stochastic scheduler.

Beside it

Arithmetic: 7× · counter gauge: 2×

3

One clear proposal

Proposal

Push-to-talk breaks first, at 2× today's load. Arithmetic said 7×. After an outage: 33 s to reconnect, 33 s with post-quantum handshakes. Proposal: cap video so push-to-talk keeps its budget.

Proposal onlyA person decidesNot bit-true 3GPP

What it needs

  • One month of LTE cell counters (standard sets)
  • Endpoint list with poll intervals
  • Site power autonomy and backhaul

What it is not

  • Not a coverage-planning tool
  • Not bit-true 3GPP

Proven, in simulation

  • Names the first class to break in 75 % of held-out cells; resource-block arithmetic 17 %, today's deterministic scheduler 46 % (simulation)
  • Per-class load from counters: 41 % RMS error where per-class counters exist; refuses per class on every cell without them
  • On surge and storm cells the stochastic scheduler puts the break 19–37 % below arithmetic for every class, beyond the interval
  • Reconnection after an outage: median 33 s classical, 35 s post-quantum on the simulated cells

Not proven

  • The counter gauge (100 % ÷ today's PRB use) reads the breaking load better: 0.7× against 1.0× median error on breaking cells, and says “fits” wrongly less often (11 % against 35 %)
  • Load intervals cover 71 % of true loads, not 90 %
  • No real counter export used
  • The uplink scheduler is new and class-level, not per flow
  • KPIs on satellite-backhauled cells fall outside the standard's measurement condition
  • Interference localisation not built
Works with

Break

Which class breaks first.

Open →

Poll

The interval each endpoint can keep.

Open →

Storm

After the outage, the reconnection.

Open →

Budget

Each site's link, with its doubt.

Open →
Load — Hidden load. From counters. · Headroom