NTN Roaming Architecture and Wholesale Design

Satellite-to-mobile services are moving from a coverage narrative into a wholesale design problem. The decisive question is not whether a handset can see a satellite, but how the NTN roaming architecture assigns spectrum rights, subscriber identity, service eligibility and settlement across the terrestrial MNO, satellite operator and MVNO. Those choices determine whether direct-to-device capacity becomes a credible wholesale extension or an expensive exception path.

Start with the operating model, not the coverage map

A workable partnership starts by assigning four functions: radio access, subscriber control, commercial distribution and customer obligations. The satellite network operator may run the non-terrestrial RAN and gateways, but that does not establish who owns the subscriber relationship. The terrestrial MNO may retain IMSI allocation, HLR/AuC or UDM control, policy enforcement and regulated service obligations. Each function needs a named operator, an interface and a liability position.

Three models are commercially plausible. In an MNO-led extension, satellite access is presented as another access layer under the home PLMN. The MNO retains product control and service assurance while buying gateway and capacity inputs. In a satellite-led wholesale model, the satellite operator packages access and exposes it under a roaming, reseller or hosted-service construct. An MVNE-mediated model adds tenant-level entitlement, charging and reporting, while the host MNO keeps control of identity and core-network policy.

MNO-led NTN extension

MNO retains subscriber identity, retail policy and service assurance; satellite partner supplies access and gateway capacity.

Satellite-led wholesale access

Satellite operator packages access; MNO or MVNO distributes under a roaming, reseller or hosted-service arrangement.

MVNE-mediated distribution

MVNE applies tenant-level entitlement, charging and reporting while the host MNO remains accountable for core-network controls.

The architecture must then classify the service. It can be an extension of the home PLMN, a visited-PLMN relationship, or a distinct access product activated through BSS/OSS rules. That classification affects steering, charging, care processes and the evidence required during disputes. It also determines whether satellite use follows an existing roaming entitlement or requires an explicit product code.

Tier-2 MNO, Southern Europe, ~18M subscribers illustrates the trade-off. Its rural-coverage objective may favour a home-PLMN extension because authentication, policy and customer communications remain under one operational authority. Its MVNO portfolio, however, may require separate eligibility, barring and charging by tenant. Emergency communications, location handling, lawful-intercept interfaces and escalation to the satellite operations centre therefore belong in the operating model, not in annexes to a capacity order.

Map spectrum, PLMN identity and core-network attachment

The technical-commercial boundary becomes enforceable only when spectrum authority, network selection, authentication and gateway interconnection are mapped to a deployment architecture. The first question is whose spectrum supports the radio link. Direct-to-device access may use terrestrial mobile spectrum under an MNO arrangement, satellite spectrum held by the satellite operator, or a jurisdiction-specific combination. The answer can vary by market even when the same constellation, handset and commercial proposition are used.

Selection and authentication path

The parties should specify what the handset sees and how it selects the network. Options include broadcasting the home PLMN, presenting a partner PLMN, or using an equivalent-PLMN configuration with controlled steering. Each option changes the failure modes. A home identity can simplify the user experience but may obscure the point at which satellite-specific policy applies. A visited identity creates a clearer roaming boundary but introduces steering, barring and settlement dependencies.

The authentication sequence should be documented from the USIM through the AuC or UDM to the serving network. The design must identify whether Diameter, SBA interfaces or roaming-hub connectivity cross the commercial boundary. Interface ownership matters because an authentication failure may arise in the device, satellite access network, gateway, hub or home core, while the retail complaint still reaches the MNO or MVNO.

Mobility anchoring and session establishment require the same precision. The agreement should state where the user plane anchors, where IP breakout occurs and which party controls session timers. NTN delay characteristics can affect EPC procedures and 5G SA policy decisions. Generic timer profiles can create avoidable retries or premature release when applied to intermittent satellite visibility.

Device qualification must also be configuration-specific. Approval should reference the band, NTN profile, satellite waveform, chipset and firmware version. A broad claim that a handset is satellite-ready is not an acceptance criterion. Qualification should reproduce the intended PLMN selection, authentication and fallback behaviour under the firmware scheduled for commercial release.

Design wholesale eligibility around device and service constraints

NTN access should be provisioned as a controlled entitlement rather than inherited automatically from terrestrial roaming. The device register is the first control point. It should combine TAC ranges, approved firmware, supported bands and NTN capability profiles. The result should be available to CRM, the OCS and provisioning workflows before activation. This prevents a commercially eligible account from reaching an unsupported radio path.

The initial service set must be decomposed rather than described as satellite connectivity. Emergency messaging, SMS, store-and-forward data, narrowband IP, voice and selected IMS services have different signalling, capacity and charging characteristics. Each needs a defined payload limit, delivery state, timeout and rating rule. Support for one service should not imply support for the others.

The PCRF/PCF should gate access by plan, device class, geography, account status and permitted service class. A terrestrial roaming entitlement should not default into satellite access merely because authentication succeeds. For MVNO tenants, the host MNO may retain device approval and policy authority while the MVNE exposes tenant-specific product codes, provisioning states and usage reports.

Device control

TAC, firmware and NTN profile validation before service activation.

Service eligibility

Policy by tariff, subscriber segment, geography and use case through OCS and PCRF/PCF.

Availability commitment

Window-based reachability and delivery objectives, with stated obstruction and handset-orientation assumptions.

Customer treatment

Clear escalation path among MVNO, host MNO and satellite operations centre.

Coverage commitments should follow the physics and operating mode of the service. Relevant measures include availability windows, minimum elevation angle, obstruction assumptions, message-delivery objective and maximum transaction size. A terrestrial-style population-coverage percentage says little about whether a user can complete a transaction from a constrained device during a defined visibility window. Commercial schedules should state the assumptions used to calculate availability, including handset orientation and retry behaviour.

Translate capacity economics into a settlement model

Satellite capacity is scarce, location-dependent and sensitive to retransmission. Wholesale pricing should therefore begin with the service unit, not with terrestrial roaming IOTs. Per-device, per-message, per-kilobyte and per-session charges suit different traffic profiles. Reserved capacity blocks or committed minimum revenue may support predictable demand, but they transfer utilisation risk to the buyer.

Recurring platform and integration charges should be separated from variable access charges. The schedule must then allocate failed-delivery attempts, retransmissions and gateway overhead. If every radio attempt is chargeable, the distributor carries a cost it may not be able to explain or recover. If only completed delivery is chargeable, the satellite partner absorbs access consumption created by repeated attempts. The settlement rule should match the delivery state visible to the retail operator.

Records before rates

Usage reporting should be agreed before the rate card. TAP files or near-real-time records should carry event timestamps, permitted location granularity, device identity, service code, rejection reason and rating outcome. The parties should decide whether a CDR represents submission, gateway acceptance, satellite transmission or confirmed delivery. Without that distinction, identical record counts can represent materially different service outcomes.

The revenue waterfall should allocate the host MNO, MVNE, MVNO distributor and satellite partner shares before retail pricing is published. Taxes, regulatory fees, fraud loss, refunds and customer-care costs also need explicit treatment. Minimum commitments are defensible where the MNO controls eligible-device distribution and plan attachment. A low-volume activation model is safer where device penetration, firmware adoption or market authorisation remains uncertain.

Greenfield MVNO, post-2023, multi-IMSI stack may require separate wholesale rating records by IMSI range. That separation prevents NTN events from being classified as ordinary roaming usage and supports tenant-level margin analysis. It also allows the operator to reconcile product eligibility against actual network use without relying only on retail billing labels.

Convert the partnership into testable launch gates

A controlled launch requires acceptance criteria across provisioning, roaming, charging, service assurance and incident ownership. Lab validation should cover SIM authentication, PLMN selection, service barring, policy enforcement, CDR generation and rating before field trials begin. Each failed criterion should have a named owner, remediation period and commercial consequence. A test report without a decision rule does not constitute a launch gate.

Field testing should concentrate on the edge conditions that create support volume: no satellite visibility, partial message delivery, fallback to terrestrial RAN, ported numbers, suspended accounts and cross-border movement. These scenarios test whether network state, customer status and settlement state remain aligned. They also expose cases where a technically successful transmission creates an incorrect retail charge or an event that cannot be reconciled.

Operational KPIs should include registration success, message-delivery latency, successful session establishment, usage-record completeness, fraud alarms and time to incident hand-off. Measurement points must be named. A latency measured from handset submission is not comparable with one measured from gateway acceptance. Usage completeness should reconcile network events to rated records and rated records to partner invoices.

Launch approval should be segmented by market and device cohort. The agreement should preserve rollback rights where regulatory clearance, handset firmware or settlement reconciliation remains incomplete. Joint change control is equally important after launch. Satellite beam plans, device certifications, tariffs, roaming footprint and core-network parameters can all change the risk profile without changing the headline service description.

NTN will not replace terrestrial wholesale, but it will force a more explicit allocation of access, identity, policy and settlement responsibilities. The early commercial advantage will sit with MNOs and MVNO platforms that treat satellite access as a governed roaming product with measurable service boundaries, not a generic coverage add-on.