If you’re bringing a new satellite transponder online or repositioning an earth station, the spectrum doesn’t care about your launch schedule. It’s already packed. Frequency coordination is the discipline that stops your C-band downlink from becoming an expensive noise source for someone else’s telemetry receiver. I’ve spent years buried in link budgets and ITU filing queues, and the takeaway is always the same: coordination isn’t paperwork for its own sake. It’s physics with a diplomatic cover.
Why We Coordinate
The radio spectrum is a finite, shared resource. Geostationary slots are separated by degrees, but antenna side-lobes and tropospheric ducting don’t respect neat orbital boundaries. A Ku-band uplink with sloppy power density control can lift the noise floor at a neighbouring satellite’s transponder just enough to degrade its weakest carriers. Coordination is the technical process of calculating those interference margins, negotiating operating parameters, and locking them into a regulatory framework so that everyone’s link budget survives contact with the real world.
Skip coordination, and you get the classic tragedy of the commons: each operator turns up power to punch through interference, which creates more interference, until nobody’s link closes. The ITU Radio Regulations and the Master International Frequency Register (MIFR) are the guardrails that prevent that spiral.
The ITU Filing Machinery
Coordination follows a three-step rhythm: advance publication, coordination request, and notification. For a new satellite network, you first submit an API (Advance Publication Information) to the ITU Radiocommunication Bureau. It’s a heads-up to other administrations that you’re planning to use specific orbital positions and frequency bands. The clock starts, and comments roll in from operators who spot potential overlap with their own planned or existing networks.
Then comes the coordination request under Article 9 of the Radio Regulations. This is where the engineering details hit the table: antenna radiation patterns, maximum power flux density at the Earth’s surface, satellite EIRP contours, receiver noise temperatures. Both sides run compatibility analyses—often with tools like Visualyse or custom software built on ITU-R Recommendations P.452 and S.1528—and the bilateral back-and-forth can stretch for months.
Once agreements are reached, or the regulatory deadline passes without objection, the network moves to notification under Article 11 and gets entered into the MIFR. That entry is your international recognition and the basis for protection against future interference. Miss a deadline or submit incomplete data, and you can lose priority outright. I’ve seen it happen.
Parameters That Actually Drive the Analysis
Coordination isn’t just checking whether frequencies overlap. The heavy lifting is in the numbers. Here’s what matters on the ground:
- G/T and EIRP: The earth station’s figure of merit and the satellite’s effective isotropic radiated power define the link footprint. A satellite with high EIRP and a modest earth station G/T can still cause trouble if a side-lobe peak points where it shouldn’t.
- PFD limits: Power flux density at the Earth’s surface is capped by ITU regulations, especially in bands shared with terrestrial services. Exceed the PFD mask at another country’s border, and you’ll get a formal complaint faster than you can say “Article 21.”
- Antenna patterns: Real antennas don’t follow the ideal envelope. Measured patterns or manufacturer data are essential for accurate interference calculations. The ITU-R S.465 reference pattern is a starting point, but actual side-lobe performance often deviates—sometimes in unpleasant ways.
- Bandwidth overlap and spectral shape: A 36 MHz carrier doesn’t only interfere with another 36 MHz carrier on the same centre frequency. Guard bands, roll-off factors, and adjacent channel leakage all play a role. A proper analysis models the full power spectral density.
When Coordination Becomes Mandatory
Not every frequency overlap triggers a formal coordination. The ITU sets a threshold based on the increase in equivalent satellite link noise temperature. If your proposed transmission raises the victim receiver’s noise temperature by more than 6% of its clear-sky thermal noise, you’ve crossed the line. For digital carriers, that often works out to a C/N degradation of roughly 0.25 dB. Below that, the interference is considered negligible and doesn’t require bilateral negotiation—though many operators coordinate voluntarily anyway, just to avoid headaches later.
Earth Station Coordination: Where the Real Work Lives
Satellite network filings grab the headlines, but earth station coordination is where most engineers burn their hours. A new Ka-band gateway or a transportable SNG terminal has to be coordinated with existing terrestrial microwave links, other earth stations, and sometimes radio astronomy sites. The process typically leans on ITU-R Recommendation P.452 for clear-air interference, with P.620 coming into play for coordination distances around radio astronomy observatories.
Coordination zones are calculated from the earth station’s EIRP, antenna pattern, and local terrain. In built-up areas, building clutter can provide extra shielding, but formal coordination rarely credits it because clutter isn’t guaranteed over the station’s lifetime. A new high-rise can suddenly expose a link that was quiet for years. For transportable terminals, the burden is heavier: every new location demands a fresh analysis and usually a temporary frequency assignment from the local administration.
Rain Fade and Uplink Power Control
Ku- and Ka-band links fade during heavy rain, and many systems use uplink power control to compensate. That’s good for availability, but it’s a headache for interference. A station transmitting 6 dB above clear-sky power during a downpour can blow past coordination thresholds toward adjacent satellites. Modern coordination agreements increasingly include dynamic power limits tied to real-time fade conditions, enforced by the hub’s network management system. Without that, a rain cell over one gateway can degrade dozens of cross-polar links on the same orbital slot.
Non-GSO Constellations: A Different Beast
Low Earth orbit constellations have torn up the old coordination playbook. A geostationary network files once for a fixed orbital slot. A LEO system with 3,000 satellites has to coordinate against the entire GSO arc and other LEO systems across multiple orbital shells. The ITU introduced milestone-based deployment rules to stop paper satellites from squatting on spectrum indefinitely, but the technical complexity of interference analysis has ballooned. Dynamic beam-hopping, steerable spot beams, and inter-satellite links mean a static coordination agreement won’t cut it. Operators now negotiate real-time interference avoidance protocols, often exchanging ephemeris data and beam schedules directly.
For a ground station tracking a LEO satellite, the coordination zone isn’t a fixed circle—it’s a moving footprint that sweeps across terrestrial microwave paths. National regulators are still scrambling to adapt their licensing frameworks, and many now require LEO operators to maintain a real-time interference database that terrestrial users can query before deploying new links.
Running a Coordination Campaign Without Losing Your Mind
Based on real filing experience, here’s a workflow that cuts delays and avoids expensive re-filings:
- Pre-filing compatibility check: Before you submit anything to the ITU, run your proposed parameters against the MIFR and other operators’ published data. Identify the administrations and networks likely to be affected. This isn’t optional—it’s the foundation of your coordination list.
- Data accuracy: Antenna gain contours, noise temperatures, and orbital position tolerances have to be defensible. Inflating parameters to grab more spectrum will backfire when a competitor challenges your filing with measured data.
- Bilateral meetings: Don’t rely on email alone. Face-to-face meetings at industry events—like World Radiocommunication Conference preparatory sessions—speed up agreement. Bring your link budget spreadsheets and be ready to tweak parameters on the spot.
- Documentation: Every agreement, every email confirming acceptance of interference levels, needs to be archived. When a dispute surfaces five years later, the paper trail is your evidence of priority.
- Post-coordination monitoring: Once you’re operational, keep an eye on carrier levels and the interference environment. A neighbouring network might change its parameters without re-coordinating. Your spectrum analyser data is the first line of defence.
Common Pitfalls
One frequent mistake is assuming coordination is done once the ITU publishes the filing. Publication is a milestone, not the finish line. Bilateral agreements still need to be concluded and recorded. Another trap is neglecting the coordination of telemetry, tracking, and command frequencies. These low-data-rate carriers are easy to overlook, but their sidebands can spill over and interfere with operational payloads on adjacent satellites.
Finally, don’t underestimate the administrative load of maintaining multiple filings across different administrations. A satellite visible from 40 countries may need individual earth station licences in each, with varying technical conditions. A centralised database that tracks licence expiration dates and conditions isn’t a luxury—it’s a survival tool.
FAQ
What’s the difference between coordination and notification?
Coordination is the bilateral or multilateral process of reaching technical agreement with other operators and administrations to avoid harmful interference. Notification is the formal submission of the agreed parameters to the ITU Radiocommunication Bureau for entry into the Master International Frequency Register, which grants international recognition and protection.
How long does satellite frequency coordination usually take?
For a standard geostationary satellite network, the ITU regulatory timeline from advance publication to notification can span two to four years, assuming no major disputes. Complex cases involving multiple administrations or non-GSO systems can stretch to five years or more. Earth station coordination with terrestrial services is typically faster, often completed within six to twelve months, depending on the national regulator’s efficiency.
What happens if I operate without coordination?
Operating an uncoordinated satellite transmitter or earth station risks causing harmful interference to existing services with recognised priority. Affected operators can file complaints with their national administration, which may escalate to the ITU. Consequences range from mandatory shutdown to financial liability for service disruption. In bands shared with safety-of-life services, uncoordinated transmissions can also violate national laws.
Can coordination agreements be modified after a satellite is in orbit?
Yes, but modifications require re-coordination with any administration whose services might be affected by the change. Minor adjustments, such as a slight shift in centre frequency within the same band, may be handled through simplified procedures. Major changes, like adding a new frequency band or increasing EIRP, typically require a new coordination request and a full bilateral process.