Media Network

Migration
to IP-Based
Transport

Your guide to Incremental IP Migration Planning

Building knowledge in our community

Media Links Service-first Insights
©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 1
Media Links Service-first Insights

Media Network Migration to

IP-Based Transport

Executive summary
As more video sources and broadcast workflows migrate to IP technology, particularly across WAN (Wide
Area Networks) systems, the current industry practice of providing baseband SDI interfaces for access
to transport networks seems increasingly outdated. Instead, a smooth migration plan is needed that
allows existing transport equipment to be redeployed to accommodate a new range of interfaces at both
sources and destinations, while also allowing the network backbone to migrate from dedicated, full-
time circuits to on-demand, high-bandwidth switched services, while still retaining the high-performance
levels required for professional video services. By more closely matching the IP-based signal formats
increasingly used at network interfaces, and by using a switched backbone, a wider variety of signals can
be accommodated, less signal conversion is required, and lower cost transport services can be delivered.

Introduction Key drivers for migration to IP

Broadcast Industry news is filled with reports
about the ongoing transition within broadcast
facilities to all IP-based infrastructure. This trend Media increasingly delivered over IP
first started with the introduction of file-based • Direct to consumers (OTT, IPTV etc.)
workflows that were built using IP networks • High performance links to MVPDs 
and has continued with the transition from SDI/ (Multichannel Video Programming 
HD-SDI and ASI to high bandwidth connections. Distributors)
Every week, new professional video devices
More flexible production workflows
that incorporate IP interfaces as their primary
• Growing number of formats, devices
connection technology are being released in the
market. Broadcasters are increasingly looking Better compatibility with carrier IP networks
to migrate their entire facilities over to using IP • Less processing at the signal interface
technology to increase flexibility and scalability
with an eye on new signal formats such as 4K/ Lower operational and capital costs

UHD and OTT streaming. • Better control plane integration

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 2
A growing priority for many broadcasters is also migrating their contribution, distribution, and facility
interconnection networks over to IP technology. Significant cost savings and signal quality preservation can be
achieved by remaining in the IP domain across the entire broadcast chain, as opposed to having signal format
converters to adapt into and out of IP packet streams.

Broadcast networks are made up of a collection of endpoints and backbones. Endpoints are locations
where communication links originate or terminate, such as a production facility, a sports venue, an MVPD
(Multichannel Video Programming Distributor) handoff, or any other signal source or destination. Backbones
provide connectivity between endpoints, and can be point-to-point, multipoint, or cloud based. For carriers,
endpoints are wherever their network connects to a customer, and the backbone comprises the connections
between those endpoints as well as the network core routers, switches and transmission equipment. For media
companies that operate private networks, the endpoints are their facility locations; their backbones typically
consist of circuits or dark fiber supplied by a service provider. In both cases, as endpoints migrate to IP, having
seamless IP connectivity between endpoints has become a growing priority for media companies.

Even when media signals are in a native IP format, the endpoint devices and backbone networks must be
constructed at both the hardware and the software levels to deliver the performance levels needed for
professional media applications. Standard, off-the-shelf enterprise-class switching and routing devices simply
don’t have the ability to properly transport and manage continuous streams operating in the multi-gigabit range
while maintaining the high levels of Quality of Service (QoS) needed to deliver reliable video and audio signals.
Gigabit-speed multicast streams, which are extremely useful for media applications that employ processing and
monitoring at multiple locations.

Making the migration from networks that only offer

media-specific interfaces to ones that support the full
complement of signals required for media production About Media Links
is a delicate process, often requiring a wide range of Service-first Insights
endpoint adapters and a flexible backbone architecture
Media Links Discussion Insights
to make a smooth transition. The key is to have a
are intended to help everyone
system that can equally handle both IP-based and
connected to the company get to
non-IP signal inputs, in a manner that allows both types grips with the latest technologies
of signals to coexist in the same endpoints and travel and standards, and to better
over the same backbone. The ability to convert signals understand why we combine these
from one format to another is also extremely useful, the way we do to deliver our best-
practice solutions.
which allows signals originating at one endpoint in, say,
non-IP format, to be delivered to endpoints in either IP For more information on this topic
or non-IP format as needed for compatibility. The ability and to find out more, visit us at
www.medialinks.com
to convert between multicast flows inside a facility
and unicast flows that interconnect facilities may also
be required in some networks. Having a system that
supports smooth migration makes it easier to transition
to future IP-based technologies that are more efficient,
operate at lower cost, and offer forward-looking
interfaces and capabilities.

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 3
Overall system requirements
In order to create a comprehensive networking solution for media signals, a number of interfaces
and features need to be supported. These should include support for baseband video and audio
signals, compressed and uncompressed media flows, IP-based streams and files, as well as supporting
conversions between different signal types. Here are the key types of video signals that need to be
supported for professional broadcasting:

• SDI and HD-SDI video signals, including standard definition SMPTE 259M, high definition SMPTE
292M, and 3 Gbps signals in accordance with SMPTE 424M, including 1080p video.

• Uncompressed UHD/4k video signals, which can be transported using a matched set of four 3
Gbps interfaces provided that the transport network preserves the relative phasing of the signals
throughout the entire transport link, whether the signals are transported in the compressed (J2K)
or uncompressed domain.

• Serial data that has been formatted into SDI or HD-SDI signals using SMPTE 305M or SMPTE
348M (known as SDTI or Serial Data Transport Interface) to support some legacy data transfer
applications for video cameras and other devices.

• Compressed video services are often transmitted using DVB/ASI interfaces that are electrically
compatible with SMPTE 259M SDI interfaces. These can either be transported intact using 270
Mbps network connections, or they can be pared down to their media essence and transported
as media packets, using encapsulation methods such as SMPTE 2022-2.

• Video services, both compressed and uncompressed, that have already been encapsulated into
IP streams are best handled using Ethernet interfaces operating at 10/100/1000 Mbps.

• For signals that use standards such as SMPTE 2022 (for compressed MPEG2TS and
uncompressed SD/HD-SDI) or VSF TR-01 (using JPEG2000 technology), in-network signal
conversion is highly desirable. This allows signals to be accepted in one format at the origin
(compressed, uncompressed, encapsulated, unencapsulated) and delivered in another format at
the destination.

The key is to have a hybrid system

that can manage both IP-based and
non-IP media signal inputs and outputs,
and crucially in a manner that allows
both types of signals to coexist at the
same endpoints and travel over the
same backbone.

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 4
Audio signals also need to be accommodated in several formats, including:

• Embedded multichannel audio in the various forms of SDI, up to 16 or 32 channels as appropriate.

Audio signals need to be carried in synchronization with their associated video flows to maintain lip
synchronization.

• Discrete audio channels normally connected using AES/EBU unbalanced interfaces in accordance with
EBU tech bulletin 3250.

• While uncompressed audio signals are typically used in many production/contribution applications,
compressed Dolby E channels can also be transported using embedded audio or as discrete AES/EBU
streams. Other types of compressed audio, such as AC-3 or AAC, can be packaged into individual IP
flows or DVB/ASI streams or multiplexed alongside video signals carried in those same formats.

• Other forms of digital audio, including AES10 (MADI) and AES67 also benefit from native IP-based
transmission networks that provide real-time bandwidth control and accurate signal timing and
synchronization across large networks.

Many other signal types need to be carried for professional broadcasting, including other forms of content
such as captions as well as significant items of metadata and file-based content. For a media transport
system, the key to handling these flows and files is flexibility, which allows the transport network to support
each item with the least amount of format conversion. For example, captions can be transported in many
different ways, including embedded in uncompressed video, inserted within a compressed transport stream,
as low speed IP data stream via an Ethernet connection, or as a data file, also over Ethernet. Another
broadcaster-specific requirement is transporting audio signals for intercom applications, which could require
direct AES/EBU audio interfaces, telco-compatible T1/E1 connections, or Ethernet connections to support
SIP-enabled intercom systems. With this multitude of signal formats, having a large selection of possible
interface types is crucial.

Requirements checklist

HD / UHD Plus
• Accommodate current/future signal formats • Low two-way delay mode for interviews
• Uncompressed and compressed s ervices • Hitless protection switching
• Remapping of IP/MAC addresses at
Embedded and discrete audio, while
system interfaces
maintaining lip-sync
• Conversion to/from SDI and IP
• 5.1, 7.1 sound
• Error Correction (FEC, ARQ)
• Compressed formats (AC-3, Dolby E)

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 5
In addition to the various signal interfaces, the system also needs to support a number of functions that can be
very useful to broadcasters for specific applications. These include:

• Low two-way delay mode for interviews, so that natural conversations comprising video and audio can take
place over long distance connections.

• Integrated capability to perform signal conversion between formats, such as taking HD-SDI inputs at one
location and delivering them as SMPTE 2022-6 compliant streams at another location.

• Remapping of IP/MAC addresses at system interfaces is essential for allowing carrier and client networks
to work in harmony with minimal amounts of signal conversion. When this technology is deployed, carrier
networks and end-user networks can both have independent, separately managed addressing schemes
that can directly interexchange media content without the complexities of external processing gear. This
technology also helps improve security and isolation between the two networks by allowing each one to be
managed and maintained as a separate, autonomous system.

• Hitless protection switching, which allows a video stream to be sent over two diverse paths and then
recombined at the destination. This technology allows even long-duration signal interruptions of a second
or more on either one of the two signals paths to be completely corrected with no impact on the delivered
video stream. Systems that support SMPTE 2022-7 Seamless Protection Switching are especially useful,
because they can be cross-connected to equipment from other vendors, particularly those suppliers such
as Media Links who helped to develop the standard and who have performed interoperability testing with
other companies.

• Error correction to handle random errors that can occur on any transmission link, particularly those that
cover long distances. FEC (Forward Error Correction) is used to add additional data to media streams
that allows a receiving device to automatically correct most random errors that have occurred on a link;
technologies include SMPTE 2022-1 for compressed IP video streams, 2022-5 for uncompressed IP video
streams, and Reed-Solomon correction for many other streams. ARQ (Automatic Repeat reQuest) relies on
close coordination between sending and receiving devices to automatically re-transmit packets that have
been lost in transmission. These techniques can be used in isolation or combined to create powerful error
correction capabilities to accommodate virtually any transmission path.

• Control and management functions that are media-aware are very important, particularly for ensuring that
network bandwidth will be available when needed for live feeds that are scheduled at specific times. With
overall situational awareness and a reservation system, a modern media network control system can certify
that adequate bandwidth will be available throughout the desired transmission path.

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 6
Current networks
Most carrier-operated media networks primarily offer baseband SDI and HD-SDI video inputs and outputs
today. This is for the not-so-surprising reason that these services are what their customers have traditionally
demanded. Today’s larger broadcasters with multiple locations frequently also use networks that primarily
provide baseband SDI interfaces for live video transport. Audio signals are frequently handled as embedded
signals within video streams, although baseband audio connections may be of use for some applications.
Network-based signal compression capabilities are also offered, particularly in carrier networks. Other
signals, such as intercom circuits, control links and file transfers are usually handled by way of separate
circuits for IP interfaces, in part due to local loop connectivity restrictions. Some networks provide
centralized monitoring services that can perform surveillance and troubleshooting for baseband signals
in addition to basic point-to-point and multipoint transport. Most current networks are implemented via
backbone connections using long-term leased circuits, which can be SONET/SDH based, IP/Ethernet based,
or utilize another technology such as dark fiber. Typically, the backbone connectivity is static and changed
infrequently, as contracts are renegotiated or for special events.

Remote Production Over Dedicated IP Network

Cameras and Talent Centralized Production

Multiple
Multiple GbE Network GbE
Camera and
Camera and Network
Audio Feeds
Audio Feeds

Dedicated 10GbE
IP Networks

MD8000 AT REMOTE VENUE MD8000EX AT BROADCASTER

Raw content feeds from venue to central production facility delivered over dedicated IP network connections

Future networks
As media facilities increasingly embrace IP-based infrastructure, media networks will also need to evolve
in order to transport a new set of services. Instead of primarily offering baseband SDI and HD-SDI video
interfaces, new networks will have native IP-video interfaces for both compressed and uncompressed
signals, with adapters to accommodate baseband video wherever those signals are still required.
Compression for various standards such as Motion JPEG2000 (VSF TR-01) and H.264 will be implemented
within the network as appropriate for each application. Audio signals will be handled as discrete IP flows
that are compatible with AES 67 or similar technologies, adding a needed layer of audio signal routing

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 7
flexibility that is independent of video routing (of course, audio signals also need to be embedded and
de-embedded within video streams for backwards compatibility). Signal monitoring can also be offered,
both for packet-level Quality of Service (QoS) and media-level Quality of Experience (QoE) that looks at the
various signals from the perspective of the ultimate viewer.

Possibly the biggest change in a future network is the ability to utilize switched backbones and on-demand
network bandwidth. As core networks increasingly deploy SDN (Software Defined Networking) technologies
that can rapidly scale connection speeds up or down, the need for long-term leased or dedicated network
backbone connections greatly diminishes. Instead, network connections can be allocated as needed from a
pool of resources that make up a virtualized backbone, and then released after they are no longer needed.
Since many media events occur at times when networks are traditionally less busy (nights and weekends),
this can help lower costs and increase overall utilization. Connections to a flexible backbone will need
to have the appropriate physical interfaces, as well as the ability to perform packet processing functions
to bridge between different address spaces and prioritize certain streams as necessary. In addition, the
necessary control plane functions will be extended to enable endpoint networks and management tools
to provide bandwidth planning/reservation and connection management across the backbone without
compromising the security of either the endpoint or backbone networks.

Switched IP Networks Expand Capacity and Add Flexibility

ProductionSuite

Cameras and Talent

10 Gb/s
Networked
Feeds
10 Gb/s
Networked
Feeds

Dedicated 10Gb/s IP Network

Switched 10Gb/s IP Networks

MD8000 AT REMOTE VENUE MD8000EX AT BROADCASTER

ADDITIONAL
REMOTE VENUES

Raw content feeds from venue to central production facility delivered over switched IP network fabric

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 8
The key: Smooth evolution
Making the change from current video networking technologies to future systems requires some
forethought, particularly in the selection of a backbone network technology and in choosing the correct
equipment platform to implement the service interfaces and stream switching. Multiple aspects of the
transition need to be considered, including:

• Moving from SDI video to native IP video streams is a process that can be done incrementally, as
new devices within the network endpoints replace older devices that only support SDI. To begin with,
each endpoint can be equipped with SDI/HD-SDI interfaces that packetize incoming streams to make
them compatible with the IP backbone, using a standard such as SMPTE 2022-6. At the destination,
conversion can be made back to SDI, or signals can be output directly as IP-wrapped video. As more IP-
native services are used, the SDI interface modules can be migrated to other locations that still require
SDI-based services, and then eventually retired when they are no longer needed. IP-native streams
will use Ethernet signal interfaces, and endpoint functions such as packet processing, signal grooming,
system control, monitoring and management will still need to be performed by video-aware equipment
located at each endpoint.

• With respect to video compression, transport networks should support three modes for transporting
real-time video signals: as fully uncompressed video from end-to-end, as streams that take advantage
of in-network compression/decompression, or as compressed signals that originate within an endpoint.
Each of these three modes can be used at different points during the migration from SDI to IP to
accommodate varying signal format needs within endpoints that are at different stages of transition.

- Uncompressed signals are commonly used for high-profile sports and other event coverage,
because they offer the highest quality and least delay.

- In-network compression takes video signals that arrive at a network interface as uncompressed
signals and compresses them using standards such as JPEG 2000 over VSF TR-01 or H.264
over SMPTE 2022-2/COP3; another option would be TICO, a wavelet-based, ultra-low latency,
mezzanine-level codec.

- Signals that are already compressed arrive at the network either as DVB/ASI streams or already
wrapped in IP packets. The former case requires encapsulation using SMPTE 2022-2/COP3 (or
possibly SMPTE 2022-5 if the entire 270 Mbps ASI signal is to be transported as a stream). The
latter simply requires IP packet/stream processing and management to be compatible with the rest
of the network. At their destination, compressed signals can be delivered intact, or they can be
decoded within a network interface to provide an uncompressed output signal.

• Signals embedded into video streams such as audio, captions, or metadata can be transported as part
of an uncompressed service, or they can be de-embedded from the video signal (in accordance with
standards such as SMPTE 291 or 299-1 that describe HANC and VANC embedding methodologies) and
transported as separate streams.

• Audio and ancillary signals that are not embedded in a video stream are handled primarily through the
use of IP interfaces. Special cases for other signals (such as serial data, camera control, etc.) can also
be handled as native IP streams or through IP adapters.

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 9
Packet Processing & Conversion
Step-by-step checklist
Packet processing is possibly the most critical
aspect of the transition to a fully IP end-to-end
network. For security reasons, as well as to permit • Isolate carrier & end-user
different addressing schemes and support overall address spaces
traffic management, individual IP packets may need
to be converted as they pass from endpoints into • Convert packets on-the-fly when
the backbone or from one network domain into crossing interface
another. One such transformation will commonly
• Change IP address, VLAN Tag,
occur as packets pass from a closed network within
Ethernet/MAC address, priority
an endpoint (such as a private studio LAN) into a
backbone interconnection link (perhaps supplied • Unicast, Multicast, Multiple Unicast
by a carrier). As the network evolves, the types of
• SDN compatible, open API, secure
transformations can change, but it is likely that some
form of adaptation will be required throughout the life
of the network.

Some of the major functions that need to be addressed in the interface equipment include:

• Conversion between different network numbering plans, such as converting between private address
spaces used within endpoints and public addresses used over the backbone (a function known as
NAT or Network Address Translation). This can involve simple tasks such as converting IP addresses
and port numbers or can be more involved such as converting between IPv4 and IPv6 networks. This
feature can be very useful when connecting between entities that may only occasionally share content,
such as a pooled news feed being distributed to multiple broadcasters.

• Intelligent management of Ethernet/MAC addresses and VLAN (Virtual Local Area Network) tags to
support stream prioritization and flow management. The ability to manipulate the VLAN membership of
different IP flows can be used to ensure that certain streams have priority over others, and to make it
possible to interconnect endpoints that use conflicting prioritization schemes.

• Unicast, multiple unicast, multicast connections may all have a role. Unicast connections flow from a
single source to a single destination. Multicast signals have a single source that can be routed to any
destination that is able to join the multicast group (with routing controlled via protocols such as IGMP
and PIM). Multiple unicast signals are a hybrid of the other two, which means having a single source
connected to multiple destinations using a number of unicast connection. This latter method permits
greater control over stream routing, and can support transmission over the public Internet, which does
not support pure multicasting.

• For the greatest amount of flexibility, SDN technology is a growing feature of many large networks,
offering intelligent forwarding and filtering of packets based on more than simple IP addresses. Support
for Open Daylight or other control standards also offers major benefits. To achieve compatibility with
SDN, open APIs (Application Programming Interfaces) that are exposed from within the endpoint and
backbone networking equipment are essential to provide the granularity of control required by this
powerful new network approach.

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 10
Backbone migration
To truly take advantage of the greater flexibility (and lower prices in many cases) of IP backbones, a
migration plan is also needed to handle backbone connections between endpoints. This transition can be
broken down into three overlapping components - transitioning from traditional SONET/SDH connections
to IP-based connections, moving from dedicated leased lines to on-demand bandwidth, and moving from
traditional IP routers and switches to SDN technologies.

• Transitioning from SONET/SDH to IP backbone normally requires the network interface to change from
a synchronous (normally optical) interface to one that transports asynchronous packets over one of the
various wired or optical Ethernet technologies. The main drivers for this change are the lower costs and
higher bandwidths for IP links as priced by most carriers at both the local loop level and for long-haul
circuits. Also, since IP connections will be the native transport mechanism for future media signals, it
makes sense to use a compatible technology in the backbone.

• SONET/ SDH interfaces that support GFP (Generic Framing Procedure in accordance with ITU-T G.7041)
support a simple way to interconnect IP-based devices and legacy networks without the excessive
overhead of other encapsulation methods)

• Converting from “nailed-up” backbone circuits to switched circuits may be more controversial, but this
step can deliver big benefits in terms of cost savings and flexibility. Most video networks today use
dedicated full-time links to endpoints with low utilization, because they are installed under long-term
leases. By using “bandwidth on demand,” the backbone can be scaled up to support coverage for a
large multi-camera event and then scaled down when the event is over. This is particularly useful for
events such as golf tournaments or auto races that only visit a given venue once per year. Plus, with the
right form of provisioning system that is compatible with carrier systems, bandwidth can be added as
needed to accommodate unexpected demand.

• As in the case of endpoint migration, backbone networks will also be migrating in the future to
support SDN functions. More flexible routing scenarios with finer granularities can be implemented
using this technology. However, full implementation will require replacing traditional command-line
based IP routers and switches at the network core with ones that expose a rich set of capabilities to
management devices.

Possibly the biggest change

in a future network is the
ability to utilize switched
backbones and on-demand
network bandwidth.

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 11
Conclusions
More deployment of IP and less use of SDI is inevitable for the future of media networks. Due to the cost
and flexibility advantages of IP-based systems, media device manufacturers are increasingly moving to
offer IP interfaces as the standard for new equipment. These changes are sure to be reflected in the media
networks that are provided by carriers as well as private networks operated by large organizations. With the
right plan and suitable equipment, it is highly feasible to move from current architectures that primarily offer
SDI interfaces and nailed-up backbone connectivity to architectures that are IP-native from end to end and
use switched backbones controlled with SDN applications.

It is important not to underestimate the complexities associated with the transition from SDI to IP across a
multi-location media system. Inside a local studio, where large bandwidth connections are available, and
the network behavior is deterministic, these challenges are easier to overcome. In the WAN environment,
the greater complexity of the networks, the wider range of signal formats, the multitude of evolving
compression technologies, all exacerbated by competing demands for bandwidth from other users, can
make delivering gigabit-class signals particularly demanding.

The key is to have devices that comprehensively incorporate IP connectivity throughout their internal
structure and external interfaces, while also providing the ability to seamlessly transport non-IP signals in
a standards-compliant manner. Using such equipment, the migration from SDI to IP can be accomplished
as fast or as slow as needed to support existing applications/clients while concurrently embracing the
interfaces and protocols of the future.

Media Links (Headquarters) Media Links Americas Media Links Australia Media Links EMEA
Kawasaki Tech Center 18F 431-C Hayden Station Road 2-12 Rokeby Street, Thremhall Park
580-16 Horikawa-cho, Windsor, CT 06095 Collingwood, VIC 3066, Start Hill, Bishop’s Stortford,
Saiwai-ku, Kawasaki-shi, USA Australia Herts CM22 7WE
Kanagawa 212-0013 Japan Phone: +1 860-206-9163 Phone: +61 3-9017-0175 United Kingdom
Phone: +81 44-589-3440 Fax: +1 860-206-9165 Fax: +61 3-8456-6339 Phone: +44(0)1279 874371
[email protected] [email protected] [email protected] [email protected]

©2018 Media Links. All rights reserved. Media Links Discussion Insights: ‘Media Network Migration to IP based Transport’. 2nd Edition. Pub. June 2018. 12