Every so often, it comes time to re-visit preconceptions about IP video transport.
The clock ticks and you need a new greenfield site install or it tocks and your service providers payment is due...
Is MPLS really required to delivery live broadcast video across the WAN? Will the time ever come when the cost and complexity of MPLS finds a good enough substitute that uses the Internet? Why is making simple 'circuit-like' redundant paths so hard with MPLS?
Modern IP video transport, or more specifically delivering live broadcast signals between diverse locations using a Wide Area Networks (WAN), has been broadly adopted by broadcasters, content producers, studios and multichannel video program distributors because of its high flexibility, interoperable standards and relative low cost. Once your local video, audio, and essence data are compressed and encapsulated into ethernet packets and addressed to a remote network destination then an IP router takes over to forward those packets on their way across the WAN, 24 hours a day and 7 days a week.
What’s more, Multiprotocol Label Switching (MPLS) is the premier enterprise WAN technology supporting converged voice/video/data, traffic engineering (TE), and fast reroute (FRR). The MPLS Label Switched Paths (LSP) are perfect for video transport. There are however two thorny issues: 1) every location still should have redundant Internet Service Providers (ISP) and 2) each ISP must agree to support the others MPLS flavor. Two of
the toughest MPLS challenges are fast re-route when using redundant ISPs and Inter-ISP traffic engineering.
There is a simpler and more economical alternative to MPLS that delivers a comparable IP video transport layer.
This paper presents an innovative IP video transport network that uses three basic building blocks: the Internet with a few simple cloud Infrastructure services (IaaS), multi-function Workflow Adapters, and Web Application Programming Interfaces (Web API). It also addresses the requirements for reliability, configuration, monitoring, and security concluding by describing how web APIs can be programmed to present to users with a familiar, useful, and modern connection oriented view of a video transport WAN that does not use MPLS.