Chapter 7
Phases 1 to 3 of WIA-COMM-005 define the envelopes, the interfaces and the cross-trust-boundary exchanges. Phase 4 is the stage where a satellite-internet operator proves that the network performs as designed, stays within the law in every jurisdiction it serves, and can be tuned without breaking subscribers. A satellite network is never finished. Orbits decay and are re-phased, rain fades the Ku and Ka links, terminal fleets grow, and regulators revise their rules. Optimization is therefore a continuing loop of measuring, comparing against design targets, and adjusting.
The standard's implementation checklist describes the design side of that loop as ten steps. They run from orbit parameters and constellation sizing to link budgets, frequency filings, ground stations, user terminals, handover algorithms, debris mitigation and regulatory approvals, and end with manufacture, test and launch. Phase 4 starts where that checklist ends. It supplies the validation tests, the regulatory evidence and the integration bridges that turn a launched system into an operated service.
The standard groups performance validation into four tests. Each one corresponds to a physical constraint of satellite communication.
1. Link Budget Margin:
- Target: 3-6 dB margin
- Account for rain fade, pointing errors
2. Latency Testing:
- Measure end-to-end RTT
- Validate < 40 ms for LEO
3. Handover Verification:
- Test seamless handover (< 100 ms interruption)
- Verify TCP connection persistence
4. Throughput Testing:
- Saturated throughput tests
- Real-world application performance (video, gaming)Link budget margin. A link budget adds up transmit power, antenna gains, path loss and noise for the uplink, the downlink and, where present, inter-satellite links (ISL). The margin is what is left after the nominal requirement is met. The standard's 3 to 6 dB target exists because the atmosphere and the terminal both eat into it. Rain attenuates Ku and Ka signals, which is why the standard calls out rain fade explicitly. Pointing error is the second erosion. A phased-array terminal steers its beam electronically and a parabolic terminal steers it mechanically, and either one can be imperfectly aimed at a satellite crossing the sky. Testing must therefore be done under degraded conditions as well as clear-sky ones. Adaptive coding and modulation, as in DVB-S2X (ETSI EN 302 307-2, listed among the standard's references), lets a link trade throughput for robustness as the margin shrinks.
Latency. Round-trip time is dominated by distance. A GEO satellite sits at roughly 35,786 km above the equator, so its round trip is large, and a LEO satellite is far closer. The standard's LEO target of under 40 ms is verified end to end rather than per hop. That means measuring from terminal through space segment and ground station to the point where traffic enters the terrestrial network. Inter-satellite links and route selection both influence this figure, which is why the standard exposes a latency-optimisation endpoint whose output informs route choice.
Handover. LEO satellites cross the sky in minutes, so a terminal must keep moving its connection from one satellite or beam to the next. The standard sets an interruption budget of under 100 ms and demands proof that TCP connections survive the transition. The second requirement matters more to users than the raw number. If a handover causes a connection reset, a video call or an online game fails visibly even when the gap itself was short. The handover-management protocol is the Phase 3 mechanism being tested here, and the budget is documented per operator.
Throughput. Saturated tests find the capacity ceiling. Application-level tests with video and gaming find the problems the ceiling hides, such as jitter, bufferbloat at the terminal and mid-session handover effects.
| Validation area | Standard's target | Typical degradation source |
|---|---|---|
| Link budget margin | 3-6 dB | Rain fade, pointing errors |
| LEO end-to-end RTT | Under 40 ms | Route selection, ground-station distance |
| Handover interruption | Under 100 ms, TCP persists | Terminal motion, beam switching |
| Throughput | Saturated and application-level tests | Capacity per satellite, terminal class |
Satellite internet is judged by subscribers on a few visible qualities: how fast it is, how stable it is, and whether it works where they are. The standard acknowledges this by requiring conformant operators to publish performance benchmarks every quarter. The published set contains median round-trip time per region, 95th-percentile RTT, sustained throughput per terminal class, handover success rate, and fade-event MTBF (mean time between failures).
| Benchmark | What it tells a buyer or regulator |
|---|---|
| Median RTT per region | Typical responsiveness where the subscriber lives |
| 95th-percentile RTT | How bad the worst common experiences are |
| Sustained throughput per terminal class | What a given terminal can really deliver |
| Handover success rate | Whether motion and satellite changes are invisible to the session |
| Fade-event MTBF | How often weather-related outages recur |
The pairing of median and 95th-percentile latency matters. An average hides the tail, and the tail is what a gamer or a video-conference user actually complains about. Because the figures are produced under one shared vocabulary, a customer can compare operators and a regulator can read them into reports without custom translation. This is the market-facing use of the standard's wire-format discipline: measurements from different networks become comparable.
The market also contains operators who do not fit the broadband mould. The standard's bridge profile acknowledges established maritime and aviation connectivity ecosystems (Section 7.3), and it includes them rather than asking them to start again.
The standard's operational case studies describe three patterns that recur in production operators. Each has a different binding constraint, and that determines what to optimize.
A single operator often serves all three, and the same quarterly benchmarks apply, but the numbers that matter differ. An urban operator watches the 95th-percentile RTT. A rural operator watches sustained throughput per terminal class. A mobility operator watches handover success rate and fade-event MTBF.
Maritime and aviation customers already have working systems, and the standard handles them with a bridge profile. Each bridge translates Phase 1 envelopes into the legacy system's native control plane and reverse-translates terminal telemetry back into envelopes.
| Domain | Legacy system or operator named by the bridge profile |
|---|---|
| Mobile satellite services | Inmarsat IsatPhone and FleetBroadband control plane |
| Machine-to-machine and voice | Iridium Certus |
| Aviation terminals | Honeywell SwiftBroadband, Cobham |
| Maritime VSAT | Speedcast, KVH and similar operators |
The purpose of the bridge is operational continuity. A shipping company that runs a VSAT terminal fleet does not have to replace it in order to appear in the same telemetry and coverage picture as a LEO subscriber.
Satellite internet crosses every sovereign boundary, so compliance is part of the engineering. The standard's discovery document declares which jurisdictions an operator is licensed in, and envelopes carry a jurisdiction identifier so that per-region compliance can be traced. The jurisdictions named include the FCC (United States), Ofcom (United Kingdom), MIC (Japan), KCC (Korea) and EU member-state regulators.
International layer. The ITU Radio Regulations frame the key obligations. The standard lists four: frequency coordination (Article 9), notification and recording (Article 11), operational procedures (Article 22), and maximum EIRP limits (RR Appendix 4). In practice, an operator selects its frequency bands, files with the ITU, coordinates with existing users, and then stays within the power limits it has declared. The link-budget margin from Section 7.2 and the EIRP limits are linked: the margin must be obtained within the permitted power, not by transmitting more.
National layer.
Export control. Satellite technology is restricted under ITAR in the United States, which means export licences are needed, with exceptions for commercial systems. The Wassenaar Arrangement provides multilateral control. A multinational ground-station network, or a terminal manufactured in one country and sold in another, must account for these rules in its design.
Debris and space safety. Debris mitigation, meaning practices that reduce orbital-debris generation, appears in both the design checklist and the references through ISO 24113 and NASA's orbital debris mitigation guidelines. A conjunction is a predicted close approach between two orbital objects. Operators exchange orbit data in CCSDS Orbital Ephemeris Message form (CCSDS 502.0-B) to assess them. COSPAR sets planetary-protection guidelines. The deorbit strategy must be planned before launch, not afterwards.
Lawful intercept. Some jurisdictions require interception capability: the US under CALEA, the EU under ETSI ES 201 671, and Korea under its Protection of Communications Secrets Act (통신비밀보호법). The standard handles this without placing intercept inside the ordinary data path. The requirement is declared in the discovery document, and a session in such a jurisdiction emits a notice envelope when it starts. The interception itself runs over a separate signed channel that audit-logs every access. The subscriber-facing network stays predictable, and the regulator still gets a verifiable record of each access.
On the conformance side, a companion test suite exercises each endpoint and protocol exchange, and the standard's compatibility promise within the 1.x line is that existing envelopes and endpoints are not removed. Breaking changes need a major version, a 12-month deprecation window and a two-thirds committee vote.
The standard treats a first deployment as a staged operation of about 90 days. Early work typically targets a single region, with a ground-station network and an initial allocation of user terminals. The reference deployment guide documents per-region capacity sizing, the spectrum-coordination cadence, and the operations runbook for the first 90 days.
The runbook for a first deployment runs in a clear order:
The ordering protects the operator. Shadow operation and the 30-day publication window produce the validation data of Section 7.2 before any subscriber depends on the system. Adding a jurisdiction later does not mean starting over, because later deployments reuse the same machinery and add per-jurisdiction policy overlays.
Integration with other WIA standards reduces duplicated work. The standard's three named integrations are as follows.
Two further compositions support operations. WIA-AIR-SHIELD supplies the trust list for inter-operator coordination, and WIA-INFRA-MONITORING carries ground-station and satellite telemetry.
The standard publishes a roadmap in which LEO, MEO and GEO are stable in version 1.0.0, with an ISL profile.
| Version | Focus |
|---|---|
| 1.0.0 | Initial publication: LEO + MEO + GEO stable, ISL profile |
| 1.1.x | Additive: more constellation tiers, optical-ISL standardisation |
| 1.2.x | Additive: confidential satellite-internet inside TEEs |
| 2.0.0 | Possible breaking change: post-quantum signatures |
Three of these directions are worth explaining. Optical inter-satellite links would replace radio crosslinks with laser links, so standardising them reduces the risk that each operator invents its own interface. Trusted execution environments (TEEs) would allow sensitive subscriber processing to run in sealed hardware. Post-quantum signatures are the only item that could break compatibility, since signatures protect the audit record and cryptographic assumptions change over decades. The standard's references also point outward, to 3GPP specifications for non-terrestrial networks, where satellites become part of the 5G architecture, and to Delay-Tolerant Networking (RFC 4838) for links with long delays or intermittent connectivity.
This chapter treated Phase 4 as the point where design becomes operations. The key lessons are these:
Several points were deliberately left open. The terms of per-jurisdiction policy overlays, the format of the operations team's own runbooks, and the evolution of the roadmap items in Section 7.4 depend on decisions that regulators and operators have not yet made. The next chapter should therefore move from how the standard operates today to how it is likely to be revised. It should look at how optical ISLs, confidential computing and post-quantum signatures would change the envelopes described here, and at how the migration can be staged so that the 1.x compatibility promise holds.