cisco days raleigh customer

8/8/2019 Cisco Days Raleigh Customer

1/73

2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 1

IP Multicast for

Entertainment Video

Cisco Days Raleigh, NC


2/73


Agenda

Video System Elements

Edge Reliant System Design (Example Topology)

Multicast Overview Multicast Design Metrics

Managing IP Multicast (CMM & VOS)


3/73


Video

SystemElements

System Elements and Resiliency


4/73


Video System Elements

MPTS

Muxing

SPTS

Muxing

DPI Ad

Splicing

Transport

NetworkEncryption

QAMModulation

Encoding Digital

Content

Encryption

Transport

Network

STB

Decoding


5/73


Design Dependencies

The design efficiency of the entertainment network is largely dependent on the IPMulticast capabilities of the components in the system. We should consider thosecapabilities categorically:

Video Sources (single or redundant)

Digital Simulcast (MPTS)

Switched Digital (SPTS)

DPI (Both MPEG-2 Transport Types)

Edge Receivers (network intelligent or not)

QAM Modulators

Decoders Nodes and Links (functionality required is based on source/edge)

Transport Equipment

Routers and Interfaces

Forwarding Protocols


6/73


Resiliency Options


7/73 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 7

Single Video Source

Leveraging a single video source into a High-Availability designrequires some method of replication that may not establishuniqueness of the video streams.

Non-Optimal

Optical splitting will create duplicate traffic that uses the same multicastaddresses

Forced multicast forwarding into transport paths increases video flowreplication and transport demand

Optimal

Sophisticated source devices that replicate video traffic as uniquelyaddressable source streams

Intelligent Edge devices dynamically select video traffic to minimizebandwidth and replication



Secondary/Backup Video Source

Layer-2 forwarding using VLANs with Any SourceMulticast (ASM), or classic multicast

Layer-3 forwarding of adjacent system content using

ASM multicast IP addressing

Layer-3 forwarding of adjacent system content usingAnycast multicast IP addressing



Video Edge Considerations

IGMP support (or the lack of it) is the largest factordriving network design

Non-IGMP compliant devices create design constraints

that impact bandwidth demand and network deviceefficiencies



Video Edge Dependency UltimatelyDrives Topology Decisions

An Evolving Distribution Network :

L2 IGMPv2/SSM Mapping End-2-End IGMPv3/SSM

Variations in consistency between Edge Gear products support of IGMPvs Promiscuity constrain your design options

Promiscuous devices have the ability to receive single sourceduplication that uses identical IPmc addressing (like Anycast)

But - limits scalability in a VLAN (to 1 GE)

IGMP Snooping is required to protect video edge devices fromoversubscription

Requires VLAN isolation for promiscuous devices which factors up themulticast replication at the edge router and the increases transportbandwidth

IGMP capable devices allow the total network to scale better


11/73



Distribution Options

Layer-2 and Layer-3 networks have distinct scalabilitydifferences



Layer-2 Multicast Fundamentals

Layer-2 Networks propagating Multicast in abroadcast fashion

Resiliency is achieved through explicit packetduplication

Video Edge equipment vendors have differentmulticast capabilities today, which may impose atransport tax in the form of multiple VLANs fordifferent applications

802.1q P2P links to create segregated traffic

One VLAN for each 1G of redundant traffic approx. 240 channelceiling



Single Source ExampleSingle Router, Single Ring/Link Transport

SVI 10

SVI 20

Statistical

Multiplexers

Static-group

Static-group

Output result is identicalmulticast groups - edge must

support duplicate addressing

scheme.

(Works for promiscuous receivers.)

802.1q Trunk

802.1q Trunk

VLAN path terminates at the last hop in the ring so that no loop exists.

Source devices feed a unique multicast to a single router, usingisolated Layer-2 trunks for redundant distribution to remote

locations



Single Source ExampleDual Routers, Single Ring Transport

SVI 10

SVI 20

Statistical

Multiplexers

Static-group

Output result is identical

multicast groups - edge must


scheme.


802.1q Trunk

VLAN path terminates at the last hop in the ring so that no loop exists.

Source devices feed a unique multicast shared between two routers,with redundant distribution to remote locations using isolated Layer-

2 trunks

802.1q Trunk

Static-group

This link

supports

bridging of

all source

multicasts



Layer-3 IP Multicast Fundamentals

Layer-3 networks propagate IP Multicast usingdynamic traffic selection

Intra-Regional Backup and/or Redundancy of video

sources leverage the bandwidth efficiency of IPMulticast

Edge network segments have greater flexibility,when supporting multi-vendor implementations

using Layer-3 addressing and forwarding



Single Source ExampleDual Router, Single Ring Transport

OSPF 10

OSPF 20

Statistical

Multiplexers

Static Groups

Output result is identical

multicast groups - edge must


scheme.


Source devices feed a unique multicast propagated between tworouters using two separate OSPF routing instances. Remote routers

see both instances for resiliency.

Static Groups

This link

supports

routing of

all source

multicasts



Dual Logical IPmc Topologies on SingleNetwork for High Availability Resiliency

Can provide different subsets of the network fordifferent classes of traffic

Can share links to reduce cost

Can share nodes to reduce cost

Vs. Virtual Routers or similar virtual network:

No need for subnet encapsulation for multipletopologies

Vs. RSVP-TE P2MP

Easier DIffserv type approach (not fixed on perflow/tree)



Dual Multicast Topologies forHA Resiliency

Send traffic twice to different multicast groups(eg: green = 232.1.8.1, red = 232.1.8.2)

Use logical path separation in network to pass red/green across different pathsNote: dual topologies just one solution

Receivers receive both copies.

No single network failure will cause any service interruption

Same bandwidth allocation needed as in traditional SONET rings,but solution even better: 0 loss instead of 50 msec.

RedundantEncoder/Multiplexer

RedundantDecoder / Ad-Inserter/..

HFC

STBs



Dual Multicast Topologies forHigh Availability Resiliency

Topology sharing of links:

Particular useful in rings.

Two topologies also useful forunicast (eg: VoD load splitting)

Requires unidirectionally weighted link metric to force opposing reachability

RedundantEncoder/Multiplexer

Rcvr Rcvr

Rcvr

Rcvr

Rcvr

Rcvr

IGP costs different in eachTopology

Unicast traffic flows inthe opposite directions

Small metric

Largemetric

Multica

sttraffic

flowUnic

asttraf

ficflow

Large

Small metric Multica

sttraffic

flowUnic

asttraf

ficflow



Dual Source ExampleDual Router, Single Physical Transport

OSPF 10

OSPF 20

Primary Source

Static or IGMPvX

Output result is unique

multicast groups and unique

source IP addresses.


IGMPv3 and SSM function nicely in this design if supported by the Edge Device.

Multiple unique sources feed two routers which support two separateOSPF forwarding instances. Remote routers see both instances for

resiliency.

Static or IGMPvX

This link

supports

routing of

all source

multicasts

Backup Source



Phased Resilient NetworkImplementation Example

Build the Foundation and Grow As Needed



Edge Reliant Design Phase 1Leverage Logical Network Subsets

Library VoD

Propagation

Mux CATVCATV

RGB

Simulcast

Source

Streaming VoD

Server

QAM

QAM

QAM



Library VoD

Propagation

Streaming VoD

Server

QAM

QAM

QAM

Edge Reliant Design Phase 2Introduce Node Resiliency

CATVCATVRGB

Mux

Simulcast

Source


25/73


Library VoD

PropagationStreaming VoD Server

QAM

QAM

Edge Reliant Design Phase 3Introduce physical layer resiliancy

CATVCATVRGB

Mux

Simulcast

Source

Primary Simulcast

Secondary Simulcast

Primary VoD Prop

Secondary VoD Prop

CATVCATV

OSPF weighted low


26/73


Edge Reliant Phase 4Introduce Non-stop Forwarding Network Nodes

Library VoD Prop

Streaming VoD

Server

QAM

QAM

Mux

Simulcast Source A

CATVCATV

CATVCATVRGBPrimary Simulcast

Secondary Simulcast

Primary VoD Prop

Secondary VoD Prop

OSPF weighted low

Simulcast Source B

CRS-1

7600


27/73


7609 Design Strengths

Converged Services on redundant 7600s

Service Separation through dedicated interfaces, simplified operationalrequirements

Efficient distribution of multicast traffic via IP routing

Deterministic traffic path based on known routing cost Multiple redundancy options available per service

Predictable and manageable scaling per service

Wide range of L2 & L3 VPN commercial services available

Utilizes a best practice design and features widely deployed in the field today

(experience to draw upon.


28/73


Dual-Homed Edge Devices


29/73


Time Warner San Antonio DVT (10GEx4)

HUBHUB

23002300HUBHUB

22002200

HUBHUB21002100

HUB 2000HUB 2000

(THUB)(THUB)

HUBHUB

24002400

HUBHUB

25002500

HUB 1000HUB 1000

(THUB)(THUB)HUB 3000HUB 3000

(THUB)(THUB)

HUBHUB

13001300

HUBHUB

14001400

HUBHUB

12001200HUBHUB

11001100

HE/HUBHE/HUB

50005000HE/HUBHE/HUB

60006000

HUBHUB

53005300

HUBHUB

52005200

HUBHUB

51005100

HUBHUB

23002300

HUBHUB

22002200

HUBHUB

31003100

HUBHUB

34003400

HSD

DVT

METROE

C&C

HUBHUB

64006400

HUBHUB

62006200HUBHUB

63006300

HUBHUB

61006100HUBHUB

68006800

HUBHUB

66006600HUBHUB

67006700

HUBHUB

65006500


30/73


HUB 2200HUB 2200

HUB 2100HUB 2100

San Antonio Hardware Installed

76007600 76007600

HE/HUB 6000HE/HUB 6000

76007600 76007600

HE/HUB 5000HE/HUB 5000

Catalyst 4948Catalyst 4948

RealTimeEncoders

RealTimeEncoders

76007600

76007600

HUB 3000HUB 3000

(THUB)(THUB)

76007600 76007600

HUB 2000 (THUB)HUB 2000 (THUB)

RGB1RGB1 RGB2RGB2 BME50BME50

CatalystCatalyst 49484948

GQAMGQAM

76007600

76007600

HUB 1000HUB 1000

(THUB)(THUB)

Catalyst 4948-GECatalyst 4948-GE

BME50BME50

Analog/ Digital RFAnalog/ Digital RFSuperTrunk to DHUBsSuperTrunk to DHUBs

HUB 2300HUB 2300

RFRF

PlantPlant

Simulcast / SDV GE Path

VOD 10GE Path

10GEx4 Transport Links

BroadBusBroadBusBroadBusBroadBus

BMR1200BMR1200

MulticastMulticast

SourcesSources

BMR1200BMR1200

Ad, SpliceAd, Spliceandand

ClampingClamping

DFC Based6704 links

at all THUB

Locations

CFC Based LineCards for 10GEand 1GE output

to Sub-Rings
http://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.phphttp://www.bigbandnet.com/products/bmr1200.php


31/73


MulticastOverview

Highlighting the Fundamentals


32/73


RaleighRaleigh

??????

??????ColumbiaColumbia

??????

BroadcastBroadcastMultiple UnicastsMultiple Unicasts

RaleighRaleigh

??????

??????ColumbiaColumbia

??????

Three copies of the same

packet are transmitted

Three copies of the same

packet are transmittedThe entire network receives

one packet even if there are only a

few receivers

The entire network receives

one packet even if there are only a

few receivers

IP MulticastBusiness DriversBusiness Drivers

The Problem: Inefficient Multipoint Techniques


33/73


Multicast Transmission: Source sends a singlemulticast packet addressed to a multicast group number.

Intelligent networking devices then dynamically buildefficient paths and deliver packets to all recipients whohave joined that multicast group.

Introduces a new class of IP addresses:

Class D = 224.0.0.0 239.255.255.255

Multicast

Group

Multicast

Group

IP MulticastBusiness DriversBusiness Drivers

The Solution: Multicast


34/73


IP MulticastBusiness DriversBusiness DriversIP MulticastBusiness DriversBusiness Drivers

Multicast Transfers at 512 kbpsMulticast Transfers at 512 kbps

Files SizeFiles Size 100 Servers100 Servers 1000 Servers1000 Servers 5000 Servers5000 Servers

1 MB1 MB 16 Seconds16 Seconds 16 Seconds16 Seconds 16 Seconds16 Seconds

100 MB100 MB 26 Minutes26 Minutes 26 Minutes26 Minutes 26 Minutes26 Minutes

300 MB300 MB 78 Minutes78 Minutes 78 Minutes78 Minutes 78 Minutes78 Minutes

Point-to-Point Transfers at 512 kbpsPoint-to-Point Transfers at 512 kbps

Files SizeFiles Size 100 Servers100 Servers 1000 Servers1000 Servers 5000 Servers5000 Servers1 MB1 MB 25 Minutes25 Minutes 4.3 Hours4.3 Hours 22 Hours22 Hours

100 MB100 MB 43 Hours43 Hours 434 Hours434 Hours 2170 Hours2170 Hours

300 MB300 MB 130 Hours130 Hours 1302 Hours1302 Hours 6510 Hours6510 Hours

Distribution TimesPoint-to-point vs. Multicast


35/73


MulticastDesignMetrics

Protocols That Are Critical For Success


36/73


Key IP Multicast Protocols

Protocol Independent Multicast (PIM)

Defines the method of propagation of multicast traffic

Internet Group Management Protocol (IGMP)

Defines how receivers and sources establish anddiscontinue membership relationships

Internet Gateway Protocol (IGP)

Used by PIM to ensure that optimal paths are used todeliver services, and prevent routing loops


37/73


Step 1 Enabling IPmc in the Network Node

IP Multicast traffic support is not usually enabled by default on mostLayer-3 network devices.

There are commands for global support on the router, and at theinterface level (or SVI) that:

Enable multicast traffic on the platformConfigure the appropriate multicast routing protocols and multicast clientsupport settings based on the receiving devices downstream from the node.

NOTE:Most applications require a configuration tuning to bring

performance and security in alignment with network policies.


38/73


Step 2 Multicast Routing ProtocolsProtocol Independent Multicast (PIM)

PIM is the industry standard family of routing protocols used to establish a logicaldomain of IPmc peers

Network Nodes become PIM peers when connected interfaces are configured witha similar PIM protocol mode

PIM peers share information about IPmc traffic sources, and direct traffic to activereceivers (IPmc requestors) according to the PIM mode

PIM operational modes are dense, sparse or sparse-dense

Dense mode floods (pushes) all IPmc traffic into domain interfaces until pruning stops theflooding.

Sparse mode forwards (pulls) an IPmc group into domain interfaces only if requested.

Sparse-mode requires devices called a Rendezvous Point to coordinate sourcedevice awareness in the PIM domain

The Layer-3 routing protocol(IGP) of the network is used to establish the path

which the IPmc traffic will take between the IPmc source and requestorThere is a potential for a non-synchronized condition where PIM tries to build a IPmc treethrough an ideal IGP path that may not be PIM enabled (uRPF). Be sure to enable yourshortest path for PIM

NOTE: The mode you select is dependent on the default behavior you require foryour application and its resiliency requirements


39/73


Step 2 (cont.) Sparse vs. Dense Perspective

While browsing the CISCO-IPMROUTE-MIB.my file I happenedacross a succinct description, that offered another view whencomparing sparse mode to dense mode:

In sparse-mode, packets are forwarded only out interfacesthat have been joined. In dense-mode, they are forwardedout all interfaces that have not been pruned."


40/73


Step 3 Internet Group Management ProtocolIGMP

Joining is the common term used to describe a host system that requests to becomea member of an IPmc group it is said that the host will join a group

The membership request is dynamic when the host uses the IGMP protocol to makethe request

IGMPv1 and IGMPv2 are said to be non-source-specific requests as they only able torequest membership by the IPmc group identity - commonly called a (*,G) request,

or joindense or sparse mode are commonly used

IGMPv3 specifies the exact source IP address and IPmc group address commonlycalled an (S,G) request, or join

Source Specific Multicast (SSM) implementations require IGMPv3 support on the requestoror by proxy at the first hop router via SSM-Mapping

SSM uses sparse-dense mode only, and does not require rendezvous point configurationin the PIM domain


41/73


Protocol Independent MulticastHow Multicast Moves Over IP Networks

Multicast Routing, IGMP Evolution, and the Impact on

Your Network


42/73


What is PIM?

Protocol Independent Multicast (PIM):

A Multicast routing protocol that define the rules used to forwardmulticast traffic throughout the IP network.

Network nodes (interfaces or links) are explicitly configured as

participants in PIM

There are multiple PIM operating modes, each with specificoperational benefits

PIM is dependent upon the underlying unicast routing protocols

for specific reachability. A multicast enabled network is commonly referred to as a PIM

domain.


43/73


Classic MulticastAny-Source Multicast (ASM)

ASM: Classic IP Multicast service (rfc1112, ~1990)

Sources send IP multicast packets to a IP multicast group

Receivers join an IP multicast group Network node will deliver packets sent by any source to an IP

multicast group to all receivers that have joined the IPmulticast group.


44/73


ASM Multicast Routing Modes

Dense Mode (DM):A traffic push mode that actively attempts to sendmulticast data to all potential receivers in the PIM domain(flooding), and relies upon their self-pruning (removal fromgroup) to achieve desired distribution.

Sparse Mode (SM) RFC 2362:

A traffic pull mode that relies upon an explicit joiningmethod (IGMP) before attempting to send multicast data torequestors of a multicast group.

Source Specific Multicast:

A mode used where receivers have the ability to directlyrequest multicast groups from a specific source.


45/73


SM Multicast Components

Rendezvous Point (RP):The multicast router that is the root of the PIM-SM shared multicast distribution tree. Thisrouter knows about all the multicast sources in the PIM domain.

Designated Router (DR):

The router in a PIM-SM tree that forwards Join/Prune messages upstream to the RP in

response to IGMP membership info it receives from IGMP hosts.

Shared Tree:

Efficiently built (temporary) distribution path from the central RP to all DRs who havedirectly attached members of a particular multicast group. Ensures that there are nounnecessary duplication of the multicast data within network, but may result in sub-optimal routing between source and receivers.

Source Tree:

A multicast distribution path that directly connects the sources and receivers DRs (or theRP) to obtain the shortest path through the network. Results in most efficient routing ofdata between source and receivers, but may result in unnecessary data duplicationthroughout network if built by anyone other then the RP.


46/73


Multicast DomainMulticast Routing: PIM-SMMulticast Routing: PIM-SM

Segment B

Multicast SourceY

Segment A

Multicast Source

XISP B

DRRP

RP

DRDRPIM-

SM

ISP A

Protocol Independent MulticastProtocol Independent Multicast

Dense mode

-Uses push model

-Traffic flooded throughout network

-Pruned back where it is unwanted

-Flood-and-prune behavior (every 3 minutes)

Sparse mode

-Uses pull model

-Traffic sent only to where it is requested

-Explicit join behavior


47/73


SSM and Anycast

SSM: Source Specific Multicast (~2000)Source(s) still send IP multicast to IP multicast group address but refered toas an (S,G) channel

Receivers subscribe to (S,G) channel by indicating to the network not only IPmulticast group it wants but also the specific source

Network will deliver packets on a per-channel basis only

Anycast Redundant IP address for source-redundancy:Primary target for SSM: Single-Source TV/Audio/Data broadcastapplications

Using a single IP address on multiple sources for redundancy, the networkdynamically announces closest source via Unicast Routing.

But why SSM, is ASM not good enough or better ?ASM is simpler to deploy no RPs or DRs needed resulting in simplerconfigurations


48/73


Reasons To Use SSM

Complexity of protocol operations required for SM

PIM-SM (Shared trees, shortest path trees, RPT/SPT switchover)/MSDP, RPannouncement (AutoRP/BSR), RP placement, RP redundancy

Operating PIM-SM over core networks complicated

Bandwidth reservation (RSVP, per group ? Per source ?),

Link/Node Protection with PIM-SM are all more complex

Scalability, Speed of protocol operations (convergence)

Operations for both SPT and RPT needed and their interaction

DoS attacks by unwanted sources

Receivers can ignore packets, but network resources can only be protected by

extensive network source access control == network level application control. Address Allocation

Try to get global scope IPv4 multicast address (GLOB, )


49/73


IP Multicast Routing Summary

SSM is a key enhancement to IP multicastBetter (manageable / scalable) multicast service delivery

SSM may not replace ASM in all applicationsMany-source applications

Source-discovery with IP multicast

ASM and SSM can coexist

Recent means of improvement / simplification of ASMEasier protocols for ASM

Bidir-PIM (intradomain only today)

Easier RP-redundancy (PIM-Anycast-RP, Prioritycast)IPv6 multicast (address allocation, embedded-RP)


50/73


IGMPManaging Multicast Propagation

IGMP Evolution, and the Impact on Your Network


51/73


IGMP Versions

Version 1, specified in [RFC-1112], was the first widely-deployed version and the first version to become an InternetStandard.

Version 2, specified in [RFC-2236], added support for "lowleave latency", that is, a reduction in the time it takes for amulticast router to learn that there are no longer anymembers of a particular group present on an attachednetwork.

Version 3 adds support for "source filtering", that is, theability for a system to report interest in receiving packets*only* from specific source addresses, or from *all but*specific source addresses, sent to a particular multicastaddress.


52/73


IGMP v1 - Behavior

LAN 2

Group

member

router

LAN 3

Group

member

router

Group

member

LAN 1

router

IGMP

queryIGMP query

IGMP

report

IGMP

report

IGMP routing update

30 sec

IGMP routing update


53/73


IGMP v1 - Pruning

router

routerrouter

router

router router

Group

Member

Group

Member

Group

Member

IGMP

query


54/73


IGMP v2 - enhancements

IGMP v2 introduces a procedure for the election of the routerquerier for each LAN. In the version 1 this was done bydifferent routing policies.

Group-Specific Query Added to permit queries form arouter to a specific group and not to all-host address in thesubnet (224.0.0.1).

Leave-Group for a reduction in the time it takes for amulticast router to learn that there are no longer any

members of a particular group present on an attachednetwork. Sent to all-routers (224.0.0.2)

When a router receives the Leave-Group message, it uses theGroup-Specific Query to verify if the sender was the last one inthe group.


55/73


IGMP v2 - Pruning

router

routerrouter

router

router router

Group

Member

Group

Member

Group

Member

IGMP Leave

IGMP Leave

Specific Group query


56/73


IGMP v3 - features

MUST be interoperable with v1 and v2

Source-filtering

Only from a source

All but a source


57/73


IGMP v3 - The protocol(for group members)

Action on Reception of a Query

Therefore, the system must be able to maintain the followingstate:

A timer per interface for scheduling responses to GeneralQueries.

A per-group and interface timer forscheduling responses to Group-

Specific and Group-and-Source-Specific Queries.

A per-group and interface list ofsources to be reported in theresponse to a Group-and-Source-Specific Query.

router

IGMP query

IGMP

report

Wait for random interval


58/73


IGMP v3 - The protocol(for multicast routers)

Conditions for IGMP Queries

Periodic request for membership

Multicast routers send General Queries periodically to requestgroup membership information from an attached network. These queries are used to build and refresh the groupmembership state of systems on attached networks. Systemsrespond to these queries by reporting their group membershipstate (and their desired set of sources) with Current-State

Group Records in IGMPv3 Membership Reports.

router

IGMP Request


59/73


IP MulticastVideo Channel Relationships

Channel Identities Change During Delivery


60/73


IPmc Flow Relationships

Video Transport Systems generally contain components thatmanipulate source video streams for a number of reasons

Statistical Multiplexing (building MPEG-2 MPTSs)

Digital Program Insertion (ad-insertion)

Encryption or DRM

IPmc group addressing will change as video programs flow fromtheir original sources through these components to consumers.

Awareness of those flow relationships are critical for successful

service management.


61/73


IPmc Flow Relationship Hierarchy Example

Off-net backupSource xPTS

Encoder SourceSPTS or PES

Digital SourceMPTS

DPI device

Statistical Mux or

Sat Demux

Edge Receiver

QAM / RF Mod

1st Stage IPmc

2nd Stage Pre-Ad or No Ad IPmc

3rd Stage Post-Ad IPmc

DS MPTS / SDV SPTS

DS or SDV MPTS

DS SPTS/PES

SDV SPTS

DS & SDV SPTS or DS MPTS

DS & SDV SPTS or DS MPTS

SDV sources fromEncoder, Offnet or

Satellite Demux

DS Sources from

Satellite, Mux or

Offnet

Ad Insertion can

occur in either

service

Edge QAM ingests

for Digital STB

RF Mod ingests forDecode to Analog

SDV SPTS

External

Encryption

DS & SDV SPTS

or DS MPTS

DS MPTS / SDV SPTS

DS MPTS / SDV SPTS

DS MPTS / SDV SPTS

4th Stage Post Encrypt IPmc

SDV SPTS


62/73


Geographic Relationships

QAM,

Decoder

Encryption

Ad Insertion

Mux-Demux

Encoders

Sources Transport Edge


63/73


Possible IPmc Flow Stages

Mux / Demux

Ad Insertion

Encryption

Ad Insertion Ad Insertion

EncryptionEncryption

Edge QAM Edge QAM Edge QAM

EncodersSatellite

Receivers

Multi-functiondevices

Zone 3Zone 2Zone 1


64/73


Control Multicasts (Out-Of-Band)

Emergency Alert Service (EAS)

BootLoaders (best way?)

Conditional Management

Hub-Specific Programming

NATd Multicasts


65/73


Video Program Path Changes Over Time

SD Source

Set Top

HD Source

PC

MobileDPI

P-Key

DRM

Program Migration


66/73


Managing

IP Multicast

Cisco Multicast Manager

Video Operations Solution

The issue


67/73


The issueHow do you proactively or reactively monitor or diagnose aspecific video service or video stream(s) given the following:

4 Different Video Service Types (TWC single market example)

Broadcast

Simulcast

VoD

Switched

Mapped into two different MPEG Multiplex Streams

MPTS

SPTS

Which map into two different IP address service paths

Unicast

Multicast

Which map across one of three different major GE network architectures

Resilient Rings

GE Optical Muxponded Backhaul

Transport network aggregates to 10G (aka muxponded), across

GE IP Switched Backhaul

IP Switch aggregates to 10G, backhauled across a 10G transport network)

Across massive geography (TWC nationwide example)

2 NOCs

7 RDCs41 Head Ends

20 hubs average per Head End

850 Hubs

And are applied in massive scale (TWC example)

Broadcast (80 channels =


68/73


Case In Point

2 x 76092 x 76092 x 76092 x 7609

2 x 76092 x 7609

2 x 7609

2 x 7609

2 x 76092 x 76092 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 76092 x 76092 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 76092 x 76092 x 76092 x 7609

2 x 7609

2 x 7609

2 x 76092 x 7609

2 x 76092 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 76092 x 76092 x 76092 x 7609 2 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 7609

2 x 76092 x 7609

2 x 7609

2 x 7609

2 x 7609

30 Gbps

30Gbps

20G

bps

20Gbps

Simulcast, HSD, CommSrv,& VoD 10GE Rings

(7 )

Simulcast, HSD,CommSrv, & VoD

10GE Rings

(6 )

Simulcast, HSD, CommSrv, VoD*

10GE Rings

(10 )

(*VoD for Plano comes directlyfrom Dallas HE)

7609 7609

Arlington

7609 7609

Thornton

7609 7609

Grapevine

7609 7609

Carrollton

Internet

Simulcast, HSD, CommSrv,& VoD 10GE Rings

(7 )

Simulcast, HSD,

CommSrv, & VoD

10GE Rings

(6 )

Simulcast, HSD, CommSrv,

& VoD 10GE Rings

(6 )

2 x 7609

Dallas HE

Plano

3 x 7609CORE RING

(14 )

HSD 10 GE Shared

Commercial 10GE Shared

VoD 10 GE Rings

Existing 7609 Router

7609 Edge Router

CRS-1 Core Router

Simulcast Ring-A

Simulcast Ring-B


69/73


Headend Network Home

Problems Caused by:

IP packet jitter rate overruns and underruns

Dropped IP packets

Good Video Poor Videoblocky effect, locking effect, freeze

frame, frame skipping

IP PacketJitter

IP PacketDelay

Dropped IP

Packets

Network Impact on Quality


70/73


Popular Perceptions

The only thing an IP network can do to affect the quality ofIPTV is loss

The perceptual quality of the video is the same at theSTB as it is at the headend ifthere is no loss within

the network.

Cumulative IP jitter may impact video quality, depending onthe receiver buffer size, and it is a leading indicator of loss

Network latency does not impact video quality per se,although it can cause a shift in view time


71/73


Media Delivery Index (MDI)

An indicatorof cumulative jitter and packet loss

MDI = Delay Factor : Media Loss Rate

Delay Factor (DF) = The amount of buffer required totransport the jittered packets in the network without lossper sample period

DF is proportional to the delay introduced in the

system due to the network buffering.

Media Loss Rate (MLR) = The total media packets lostper sample period.

M di D li I d


72/73


MDI Measurement

Delay factor is Good

Media Loss is Good

For 3.5MB/s Expected delayDF: 2.81

MDI MeasurementDelay factor is not good

Media Loss is not good

Expected DF was 2.81

Netwo

rk

Media Delivery IndexAn Example


73/73

cisco days raleigh customer

Documents