Innovation rarely happens in a vacuum. More often, it happens at the point of collision: when worlds that have run on separate tracks begin to converge. That is the story behind this framework. It began as a project for a broadcaster with a global distribution footprint of over 1,000 receive sites, whose ambition was moving away from a fixed satellite architecture toward a flexible, IP-based distribution network.To get there, the project brought together vendors from different corners of the industry that had never collaborated this closely in a modern, end-to-end workflow. As the pieces came together, what this broadcaster and its vendors had built started to look less like a one-off solution and more like a framework: a repeatable model, adaptable across many organizations and contexts, even beyond broadcast.
And sometimes, timing lines up. The 2027 C-band spectrum auction is a hard deadline. Every broadcaster still relying on C-band satellite is evaluating alternatives before 2027 budgets lock. This framework happens to provide a working answer to this problem. What sets this framework apart from other C-band approaches is that it moves master control to the cloud as part of a complete workflow, from ingest through distribution.
This enables centralized operations, remote visibility, faster deployment, geographic flexibility, resiliency and disaster recovery, reduced dependency on physical facilities, and the ability to manage both streaming and traditional distribution from a common operational environment. The customer is unnamed, but the architecture is real and in production.
In the next sections, we will break down every element of the IP Convergence Framework for Distribution: where it came from, the layers that make it up, how they work together, and what benefits they deliver. We will also make the case for why this model is a working answer to the C-band transition US broadcasters are now facing.
The origins of the framework
Convergence between worlds
For most of broadcast history, broadcast and streaming have been treated as two different sectors, run by different teams, with different mindsets. Broadcast was built around precision and visibility. Broadcast engineers typically think in frame-accurate timing and redundant signal paths. And, more importantly, they demand operational visibility: the ability to watch every piece of content moving and to intervene when something goes wrong. It is a discipline built the way Swiss watches are built, particularly in live broadcast, where every moment matters.
Streaming was built around reach and convenience. Streaming platforms were designed to serve media content to many different devices, locations, and bandwidth conditions, all at the touch of a button. If broadcast is like a Swiss watch, streaming resembles a modern logistics network: optimized for delivery at scale.
For a long time, these two disciplines stayed separate because the underlying technology was different. Broadcast ran on dedicated signal infrastructure, while streaming ran over the public internet. In recent years, IP has been closing the gap, enabling the best of both worlds to come together. That convergence is what gives this framework its name.
Convergence, in action
This convergence between streaming and broadcast, enabled by IP, was the ambition at the heart of the project that gave birth to this framework. The broadcaster behind the project relied on a fixed satellite distribution architecture that was, by design, expensive and inflexible. This broadcaster has a global footprint of over 1,000 receive sites, including remote and hard-to-reach areas requiring reliable delivery. Reaching every region meant building and maintaining dedicated infrastructure locally, market by market. While this made sense a few years ago, it scaled poorly against how content is consumed today, with requirements for more formats and devices moving faster than physical infrastructure can keep up with.
The broadcaster wanted to transition to an IP-based, software-defined architecture that combined the reach and convenience of streaming with the precision and visibility of broadcast.
The relocation of the broadcaster's facilities forced the decision. Rather than rebuilding its satellite plant at the new site, the broadcaster used the move to build its distribution on IP from the ground up, cutting costs in the process.
The new system was built around the following key design principles:
Software-defined: Infrastructure abstracted from physical hardware and moved to the cloud, including master control, replacing fixed local deployments with elastic, centrally managed resources.
Flexible: A cost model built around optimized variable spend rather than fixed provisioned capacity, cutting costs compared to the previous setup.
Content-agnostic: Non-live content delivered through a streaming-first workflow, with live content receiving the control required by broadcast workflows.
Resilient: Redundancy built by design, deployed across two cloud regions, protecting against signal loss.
Transparent: Full visibility into every piece of content moving through the system, with the ability to intervene for operational staff (if needed).
There's no better example of embracing the idea that broadcast and streaming are two sides of the same coin - different faces, but ultimately part of the same thing Michael Atkin, President & CEO, BroadView Software
No single vendor could deliver all these dimensions at once. Most are strong in one or two. Broadcasters increasingly avoid closed platforms that force these tradeoffs and choose interoperable components from several vendors that work as one system.
The architecture of the framework
The layers
Four vendors came together to build the core foundation of this architecture:
Uplynk - the streaming and integration layer:
