The satellite phone
that gets through.

That’s the promise your subscribers judge you on — and a marginal link that fails is the moment they churn. QSSP is a software layer that makes that moment work across the network you already run, turning reliability and security into tiers you can sell — with no new hardware to launch.

For the customer

The experience you put in front of your subscribers.

Connects instantly

No setup, no waiting for a connection. The first scrap of signal already carries a real message.

Never drops you

A lost signal isn’t a lost session. It picks straight back up when you’re in range — no “reconnecting.”

Works on one bar

Delivers in weak, patchy conditions where other phones simply show “no service.”

Lasts longer

Lean and efficient on the airwaves: more messages per plan, more days between charges.

And the call holds together. As the signal fades, the voice stays clear and keeps going — instead of breaking into garble or cutting out.

For your network

strong fair weak
The same network, lifted — no new hardware.
Your network todayany bearer, as-isWith QSSPsame network · software layer
Delivery on a weak or fading link
Voice intelligibility on a degrading link
Session continuity through dropouts
Airtime efficiency & capacity headroom
Speed to first message (no handshake)
Quantum-safe secure tier to sellnot availablebuilt in

A new premium tier, not just a feature. QSSP is quantum-secure by design — so your government, defence and enterprise accounts can buy HNDL-proof connectivity as a higher-margin tier, ahead of the post-quantum mandates already arriving. One integration, across your whole estate.

Part Two — Implementation
1 / 4

What’s involved — a business overview

How QSSP is deployed, the two kinds of satellite operator it works with, and where it performs best — without the engineering detail.

About QuStream and QSSP

QuStream is a technology company. QSSP — the QuStream Satellite Protocol — is its software for satellite phones and devices. It makes satellite messaging and calls far more reliable: connecting the moment there is any signal, holding through dropouts, and getting through in weak conditions where ordinary services show “no service” — and it is secure by design against future quantum computers. Crucially, QSSP runs on the satellite networks that already exist, so there are no new satellites to launch and no new hardware to build.

What implementation involves

Where it runs — the two kinds of operator

Pass-through operators

The satellite simply relays the signal — bouncing it back to the ground without opening or processing what is inside.
QSSP performs best here
  • Viasat / Inmarsat — global mobile-satellite service
  • Space42 / Thuraya — regional handset and IoT service
  • Globalstar — global low-orbit network (consumer access tied to Apple)
  • AST SpaceMobile — direct-to-phone from space
  • 3GPP NTN (Release 17/18) — today’s phone-direct standard
  • RARTEL / Eutelsat OneWeb — defence and government access
Full strength. Because the satellite never touches the content, QSSP delivers everything — including the strongest reliability gains.

Regenerative operators

The satellite processes the signal on board — decoding and resending it, often routing between satellites — before passing it down.
Works fully — reliability slightly reduced
  • Iridium — global low-orbit network for defence and safety
  • Starlink Direct-to-Cell — mass-market phone-direct service
  • 3GPP NTN (Release 19+) — the next-generation phone-direct standard
  • Future MEO / LEO constellations — emerging processing networks
Still strong. QSSP keeps its full security and connection benefits; only the very top of the reliability gain is reduced, because the satellite can discard parts of a weak signal before it reaches the ground.
2 / 4

Pass-through (transparent) bearers

The device and ground stacks, and the operators where QSSP gets full benefit — including bit-level salvage.
RF · antennaUntouchedModem PHYAir interface — untouchedLink cipher / sessionBypassed — superfluousModem data APISBD · IMT · IPQSSP engine — newPer-msg key, MAC, framingApplicationMessaging · voice codecTeleport RF · antennaUntouchedModem demodAir interface — untouchedLink cipher / sessionBypassed — superfluousModem data APISame data planeQSSP gateway — newVerify, decrypt, route, logOnward to core / netCore, internet, VPNSatelliteTransparent — untouchedKMS — newQ-block estateuser data in / outuser data in / outNew — QSSPReplaced / superfluousUntouched
Transparent bearer   The link cipher is bypassed as superfluous; QSSP adds an engine in the device and a gateway plus KMS on the ground. The satellite never touches the content, so QSSP gets full benefit end-to-end, including bit-level salvage.

Operators on a transparent / bent-pipe payload

Viasat / Inmarsat
GEO · L-band MSS
via Skylo, or direct for maritime / aero / gov
Space42 / Thuraya
GEO · Thuraya-4 L-band
regional handset + IoT
Globalstar
LEO · bent-pipe
full benefit, but Apple-tied access
AST SpaceMobile
LEO · relays to ground core
direct-to-cell, effectively transparent
3GPP NTN — Rel 17/18
transparent payload mode
today’s direct-to-device; via Skylo
RARTEL / Eutelsat OneWeb
LEO · via Romanian gateway
defence / institutional path
3 / 4

Regenerative (processed) bearers

Identical integration; the satellite decodes and routes on board, carrying QSSP as an opaque payload — so bit-level salvage is capped.
RF · antennaUntouchedModem PHYAir interface — untouchedLink cipher / sessionBypassed — superfluousModem data APISBD · IMT · IPQSSP engine — newPer-msg key, MAC, framingApplicationMessaging · voice codecTeleport RF · antennaUntouchedModem demodAir interface — untouchedLink cipher / sessionBypassed — superfluousModem data APISame data planeQSSP gateway — newVerify, decrypt, route, logOnward to core / netCore, internet, VPNSatellite — regenerativeDemod, decode, route, re-TxCarries QSSP as opaque payloadOnboard CRC may drop a frame — salvage cappedKMS — newQ-block estateuser data in / outuser data in / outNew — QSSPReplaced / superfluousUntouchedOnboard processing
Regenerative bearer   The device and ground integration is identical. Confidentiality, no-handshake and resync carry over fully; onboard frame-dropping caps the bit-level salvage to whatever the satellite forwards.

Operators on a regenerative / processed payload

Iridium
LEO · onboard processing + crosslinks
defence & safety; partner program onramp
Starlink Direct-to-Cell
LEO · eNodeB on satellite
mass-market D2C; via MNO partners
3GPP NTN — Rel 19+
regenerative · gNB on satellite
the convergence future; Iridium-compatible
Future MEO / LEO
onboard routing · processed
emerging; treat case-by-case
4 / 4

Key management & Q-block lifecycle

How the Q-block estate is generated, provisioned, operated, replenished and governed — the component operator security teams scrutinise first.
KMS — key authorityOwns the Q-block estateQ-BLOCK LIFECYCLEGenerateQRNG → Q-blockProvisionTo device + gatewayOperatePDK chain, per-msg keysReplenishOTA, decades in ~1srenews — no downtimeCONTINUOUS GOVERNANCERevokeCompromise → reject at gatewayAuditUsage counters, compliance log
Q-block estate   The KMS owns the Q-block estate end-to-end and integrates with the operator’s existing HSM / key-management environment. Keys are generated from QRNG, provisioned to device and gateway, operated as a local PDK chain, and replenished over-the-air.

How the estate is managed

Replenishment
no service interruption
a decades-supply pushed over-the-air in ~1 second
No handshake
zero round trips
keys derived locally by walking the PDK chain
Revocation
endpoint compromise
revoked at the KMS; rejected at the gateway