How Should Operators Bill Usage When One Satellite Beam Covers Several Countries?

Why does satellite coverage break country-based billing?

Terrestrial networks have always given operators a convenient certainty: a cell tower sits in one country, so any usage on that cell belongs to that country. Roaming rates, domestic tariffs, tax rules, and interconnect settlement have been built on this assumption for decades.

Non-terrestrial networks (NTN), which deliver mobile connectivity through satellites, do not work this way. A single beam from a low Earth orbit (LEO) satellite can be tens of kilometres wide and, depending on the constellation and the region, can sit across two or three national borders at once. A subscriber connecting through that beam might be well inside their home country or just across the border in a neighbouring one, and the beam itself does not carry that distinction. As direct-to-device (D2D) services, which connect ordinary smartphones straight to satellites, and satellite IoT roll out, more usage will be served through exactly this kind of borderless coverage.

What happens when cross-border satellite usage is misclassified?

Rating and interconnect systems are not built for this ambiguity. They assume that a network identifier, such as a cell or a beam, maps to one country. When that assumption breaks, usage becomes hard to classify, and revenue leakage falls into either one of the two buckets:

• Cross-border usage billed as domestic. The operator gives up the roaming or international revenue it should have collected, and the settlement with the partner network in the neighbouring country never happens.
• Domestic usage billed as international. Because the beam technically touches another country, subscribers are overcharged for what should have been a standard domestic event.

Either error can lead to billing disputes, customer complaints and, in some markets, regulatory exposure. Because beam coverage is fixed and usage patterns repeat, a wrong classification repeats too, for every call or session that follows the same pattern.

How can operators classify usage correctly when a beam spans multiple countries?

The starting point is to treat a satellite beam as a coverage area that may include more than one country, rather than a single country signal the way a terrestrial cell has always been treated. The following controls can be applied:

• Go beyond the beam ID. Use whichever additional location signals are available, such as device-level location data, the last known terrestrial handoff point, or sub-beam positioning where the network supports it, so the beam is not the only input deciding a subscriber’s country.
• Build rules for shared coverage. Let rating and tax logic handle a beam that spans several countries with configurable, evidence-based jurisdiction rules. Where classification is genuinely uncertain, apply the operator’s own rules rather than defaulting to domestic or international, and log the basis for each decision so it can be reviewed.
• Audit the pattern, not just the transaction. Regularly check whether the mix of domestic and international classifications coming out of each beam is realistic for that region, so a drift toward under- or over-classification is flagged before it becomes a recurring loss, even when no single transaction looks wrong.
• Connect the fix to settlement. Make sure corrected classifications flow into interconnect and roaming settlement with the relevant partner operator, so the partner side of the ledger reflects the same reality as the subscriber’s bill.

How Subex approaches cross-border beam assurance

Subex extends revenue assurance and partner ecosystem management to non-terrestrial networks. It treats multi-country beams as a standard case rather than an exception: applying operator-defined jurisdiction rules, auditing classification patterns per beam, and flowing corrections into interconnect and roaming settlement, so that both the subscriber bill and the partner relationship are protected.