Satellite frequency coordination isn’t a paper-pushing exercise. It’s the hard prerequisite that decides whether your bird can legally transmit, whether it will step on its neighbors, and whether the whole business case holds together. I’ve spent more than twenty years wrestling with spectrum filings and interference disputes across GSO, MEO, and LEO systems, and the one thing that never changes is this: coordination is a negotiation built on physics. If you forget the physics, the paperwork won’t save you.
Why Coordination Exists
Radio spectrum is a limited resource. Put a satellite up, and you’re essentially parking a high-power transmitter where it can see a third of the planet. Without tight coordination, one downlink can clobber another’s uplink, or a poorly placed earth station can saturate an entire transponder. The ITU provides the rulebook, but the real work happens between operators—often on short timelines and with a lot of money hanging in the balance.
And here’s the part newcomers often miss: coordination isn’t just about playing nice. It’s about securing your legal right to operate. A network that isn’t coordinated and recorded in the Master International Frequency Register (MIFR) has no standing. Other operators can ignore you, and regulators will refuse your license. You’re invisible.
The ITU Framework: Article 9 and Appendix 4
The Radio Regulations lay out a three-stage process: advance publication, coordination, and notification. The first stage—the API filing—is a heads-up to the world that you intend to launch something. It’s not a request for permission, but it triggers a comment period. The second stage, the coordination request (CR/C), is where the engineering detail goes in. Appendix 4 of the Radio Regulations specifies exactly what data you must provide, from antenna patterns to noise temperatures to orbital geometries. If your Appendix 4 data doesn’t hang together, the ITU’s Radiocommunication Bureau (BR) will bounce it back, and you’ll lose months.
Notification is the final step. It’s the formal recording of your successfully coordinated assignments in the MIFR. Until that happens, you have no international protection. It’s like having a building permit but no title deed.
Technical Parameters You’ll Live and Die By
At its core, coordination is a link budget problem stretched across the orbital arc. The numbers you’ll haggle over in every negotiation boil down to a few key parameters:
- Equivalent Power Flux Density (EPFD) limits: Article 22 sets hard caps on the aggregate power flux-density your system can dump onto the Earth’s surface or into the geostationary arc. For non-GSO constellations trying to share with GSO, EPFD is the make-or-break constraint. Exceed it, and you’re dead in the water.
- Carrier-to-Interference (C/I) ratios: For GSO-to-GSO coordination, the usual trigger is a C/I below 30 dB for analogue carriers or 20 dB for digital. These aren’t numbers pulled from a hat—they come from years of real-world receiver testing.
- Coordination arc: The slice of the orbit where you need to talk to other GSO birds. It’s defined by your antenna’s off-axis gain and the interference thresholds of adjacent satellites. Get this wrong, and you’ll be fielding angry emails from day one.
- PFD masks: Power flux-density limits at the Earth’s surface that protect terrestrial services. Your downlink has to stay under these masks, which change by band and region.
For non-GSO systems, the headache multiplies. You’re not coordinating with a handful of fixed slots. You’re dealing with thousands of moving satellites, each with beams that shift by the second. The ITU’s milestone rules for mega-constellations add another layer: deploy a set percentage within a hard deadline, or lose your priority. No extensions, no excuses.
Running a Coordination Campaign: The Real Sequence
Coordination runs in parallel with spacecraft design and procurement. It’s a multi-year slog. Here’s the order of battle I’ve used on actual campaigns:
1. Pre-Filing Analysis and Band Selection
Before you send anything to the ITU, you need to model the existing environment. Pull every relevant filing from the Space Network List (SNL) and build a software model that calculates interference from every active and planned network in your target bands. Visualyse Professional or custom MATLAB scripts are the usual tools. The aim is to find bands with a manageable coordination load. C-band might mean 200+ coordination partners; Ka-band might have fewer, but the technical constraints bite harder.
2. Building the Coordination Request
Your Appendix 4 data has to be internally consistent. If the antenna gain pattern doesn’t match the beam coverage area, the BR will reject the filing outright. For non-GSO, the challenge is representing a dynamic constellation in a static format. You’ll need to define worst-case geometries that bound the interference environment—often after running thousands of simulations to find the peak EPFD or C/I values, then encoding those as trigger points.
3. Bilateral Negotiations
Once the BR publishes your CR/C, affected administrations get four months to comment. But the real work starts when you receive a coordination request from another operator, or when you send yours. You’ll swap technical data, run compatibility studies, and negotiate operating constraints. Typical outcomes:
- Frequency segmentation: Splitting a band so each operator gets exclusive sub-bands.
- Geographic separation: Agreeing not to serve certain regions at the same time.
- Power limits: Dropping EIRP in specific directions or time windows.
- Orbital separation: Tweaking station-keeping boxes or phasing of non-GSO satellites.
These talks are technical, but they’re also commercial. You need to know your own link budget cold—what concessions you can absorb without gutting your service. I’ve seen operators agree to power cuts that looked tiny in dB but shrank their coverage area by 20% or more. Don’t be that operator.
Earth Station Coordination
Coordination doesn’t stop at the space segment. Earth stations—especially big gateways with large dishes and high power—must be coordinated with terrestrial services and other earth stations. The ITU Radio Regulations require coordination of earth stations in bands shared with terrestrial services, usually under Appendix 7. That means calculating coordination contours around your site and notifying every administration whose territory falls inside them.
For a large gateway, the coordination distance can stretch past 300 km. You’re not just looking at fixed microwave links; you’ve got mobile services, radiolocation, even radio astronomy sites to consider. In practice, this means working with national regulators to get site-specific licenses, often backed by detailed interference studies and, sometimes, on-site measurements.
Pitfalls That Cost Time and Money
I’ve watched the same mistakes play out across projects for years. Here are the ones that hurt the most:
- Ignoring the coordination arc: File a GSO network without checking who’s inside the arc, and objections will land immediately. Always run a pre-coordination check against the SNL.
- Underestimating EPFD for non-GSO: Article 22 limits are absolute. If your constellation busts them, you won’t get regulatory sign-off. Validate EPFD compliance early in the design phase, not after the satellites are built.
- Incomplete Appendix 4 data: Missing antenna patterns, wrong noise temperatures, or vague orbital parameters will get your filing returned. That can set you back six months or more.
- Poor documentation of agreements: A handshake deal with another operator is worth nothing. Every coordination agreement needs a formal record and, where required, submission to the ITU.
- Neglecting the national layer: ITU coordination gives you international recognition, but you still need a license from each country where you want to operate. National regulators often tack on extra conditions, especially for gateway sites.
Software Tools and Data Sources
You need the right tools. The ITU offers free resources—the Space Network List, the Space Radio Communications Stations database, and the BR’s EPFD validation software. But for serious interference analysis, commercial tools are usually unavoidable. Visualyse Professional and Transfinite’s SimuLTE are widely used for GSO and non-GSO coordination, respectively. For earth station work, ATDI’s ICS Telecom or LS telcom’s SPECTRAemc are standard.
Whatever tool you pick, the analysis is only as good as the input data. Verify antenna patterns against measured data whenever you can. Base your propagation models on ITU-R Recommendations (P.452 for terrestrial paths, P.618 for Earth-space). And never trust a single simulation run—always do sensitivity analyses to see how parameter uncertainty shifts the results.
FAQ: Satellite Frequency Coordination
What is the difference between coordination and notification?
Coordination is the bilateral (or multilateral) process of hashing out an agreement with other operators to avoid harmful interference. Notification is the formal submission to the ITU BR that records the successful coordination and enters the frequency assignments into the Master International Frequency Register (MIFR). You can’t notify until coordination is done.
How long does the coordination process typically take?
For a standard GSO network, expect 2–4 years from the initial API submission to successful notification, assuming no major fights. For large non-GSO constellations, the timeline stretches to 5–7 years because of the sheer complexity of coordinating with multiple GSO and non-GSO systems across many bands.
What happens if we cannot reach a coordination agreement?
If bilateral talks stall, the administrations involved can ask the ITU Radiocommunication Bureau to step in under Article 9. The BR can facilitate discussions and, in some cases, make a determination. But its role is mostly procedural—it can’t force a technical fix. Unresolved disputes can delay or block your ability to bring the satellite into use, and you may end up changing frequencies or orbital positions.
Do we need to coordinate if we are only using a leased transponder?
Generally, no. The satellite operator that owns the space station is responsible for coordinating the satellite network. As a transponder lessee, you operate under their coordination umbrella. But you’re still on the hook for coordinating your earth stations if they operate in shared bands, and you must keep your transmission parameters inside the coordinated envelope of the satellite operator.