49
Infrastructure Design for IPTV Services IPTV Asia November 8-9, 2006 Grand Copthorne Waterfront Hotel, Singapore Sue Moon Joint Work with Meeyoung Cha (KAIST) W. Art Chaovalitwongse (Rutgers/DIMACS) Gagan Choudhury, Zihui Ge, Aman Shaikh, Jenniver Yate s (AT&T)

Infrastructure Design for IPTV Services

  • Upload
    rockys11

  • View
    1.107

  • Download
    10

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Infrastructure Design for IPTV Services

Infrastructure Design for IPTV Services

IPTV AsiaNovember 8-9, 2006

Grand Copthorne Waterfront Hotel, Singapore

Sue MoonJoint Work with

Meeyoung Cha (KAIST)W. Art Chaovalitwongse (Rutgers/DIMACS)

Gagan Choudhury, Zihui Ge, Aman Shaikh, Jenniver Yates (AT&T)

Page 2: Infrastructure Design for IPTV Services

2

Push behind IPTV TV service over IP

Replacement of TV distribution networks Core service of “Triple Play” (voice, data, video) and “Quadr

uple Play” (+wireless/mobile)

Evolution Path Controversy over distinction between broadcasting and co

mmunication Bundled vs blended services As seen here so far!

Page 3: Infrastructure Design for IPTV Services

3

Technical Challenges of IPTV Distribution network

WAN, MAN, and access technologiesResilient design required

QoS guaranteeSame level of quality as today’s TV offers

Platform Standardizations: AV coding, EPG/ESG (eletronic program

ming/service guide), device mgmt, ... Middleware, settop box DRM (digital rights mgmt)

Today’s conditional access system not enough

Page 4: Infrastructure Design for IPTV Services

4

Talk Outline Service Architecture Overview

Comparison of Design Choices [Cha06-1] Path Protection Routing in WDM Mesh

Networks [Cha06-2] Efficient and Scalable Algorithms [Cha06-3]

Page 5: Infrastructure Design for IPTV Services

5

SHO

Regional Network

Video Hub Office (VHO)

2 SHOs and 40 VHOs across the US

customers

Regional Network

Backbone Distribution Network

Super Hub Offices (SHO)

VHO

VHO

Broadcast TVVoD

Regional Network

How can we provide reliable IPTV servicesover the backbone network?

Service Architecture of IPTV

Page 6: Infrastructure Design for IPTV Services

6

IPTV Traffic Type

Broadcast TV: realtime, 1-3Gb/s Popular VoD: non-realtime download to VHOs Niche (esoteric) VoD: realtime, 0-3 Gb/s per VHO

Characteristics Uni-directional and high-bandwidth High traffic variability expected for VoD Multicast for broadcast TV / unicast for VoD

Page 7: Infrastructure Design for IPTV Services

Comparison of Design Choices

Page 8: Infrastructure Design for IPTV Services

8

Design Space Technology: layer 1 optical vs. layer 3 IP/MPLS Service layer topology: hub-and-spoke vs. meshed

(ring-based) Access connections: dual-homed vs. ring

Dual-homed Ring

Backbone Backbone

VHO

Page 9: Infrastructure Design for IPTV Services

9

Design Space Reliability

Goal: resilient to single SHO/router/link failures Mechanisms: Fast-failover + routing protocols

working pathSrc

Dst

Failure

switching

Optical layer SONET protection

Src Dst

working path

protection path

IP layer fast-reroute (FRR)

Failure

Page 10: Infrastructure Design for IPTV Services

10

IP designs

Optical design

Potential IPTV Designs

New dedicated IP backbone for IPTV Integrating with existing IP backbone Dedicated overlay over existing IP backbone Directly inter-connect IP routers (no backbone) Integrating with existing optical backbone

Page 11: Infrastructure Design for IPTV Services

11

SHO SHO

BackboneVHO VHO

Support IPTV as multicast application (VoD as unicast) VHO receives single stream from the nearest SHO

Single network to manage Backbone links are shared (careful QoS) Various access connections, fast-failover schemes

Alt #1: Integrate With Existing IP Backbone

Page 12: Infrastructure Design for IPTV Services

12

Backbone

SHO SHO

VHO VHO

Inter-connect common backbone routers with dedicated links

Backbone links are dedicated for IPTV (no QoS) Overhead for managing overlay Various access connections, fast-failover schemes

Alt #2: Dedicated Overlay of Existing IP Backbone

Page 13: Infrastructure Design for IPTV Services

13

Connect geographically close VHOs into regional rings

Inter-connect rings with long haul links Security is higher than using IP backbone No access part Fast-failover

Meshed topology (carry “through” traffic)

Alt #3: Flat IP (No Backbone)

Long haul links

SHO

SHO

VHO

VHO

Page 14: Infrastructure Design for IPTV Services

14

Alt #4: Integrating with Existing Optical Backbone

Multicast capabilities at optical nodes (new technology) SHOs establish multicast trees, VHO receiving single best stream

Fast-failover is not yet supported in optical multicasting

SHOSHO

L1 network

VHO

Page 15: Infrastructure Design for IPTV Services

15

Review: Design Choices

Technology

Service layer topology

Fast-failover

Link capacity

IP or optical

SONET links, fast-reroute, or physically diverse paths

Dedicated or shared

Hub-and-spoke or highly meshed

AccessDual-homed or ring

Page 16: Infrastructure Design for IPTV Services

16

Design Instances Design Layer Link-Capacity Access

TypeFast-Failover

Int-IP-HSInt-IP-HS-FRRInt-IP-RingInt-IP-Ring-FRR

IP......

Shared......

Dual-homed

..Ring

..

SONET linksFast re-routeSONET linksFast re-route

Ded-IP-HSDed-IP-HS-FRRDed-IP-RingDed-IP-Ring-FRR

IP......

Dedicated......

Dual-homed

..Ring

..

SONET links Fast re-route SONET links Fast re-route

P2P-DWDM P2P-DWDM-FRR

Optical..

Dedicated..

None..

SONET links Fast re-route

Opt-Switched Optical Time-divisioned Dual-homed

Disjoint paths

Alt #1

Alt #2

Alt #3

Alt #4

Page 17: Infrastructure Design for IPTV Services

17

Cost Analysis: Capital Expense vs Traffic Loads

Cost comparison across traffic demands

0.0

5.0

10.0

15.0

20.0

M1+

U0

M2+

U0

M3+

U0

M1+

U1

M2+

U2

M3+

U3

M1+

U0

M2+

U0

M3+

U0

M1+

U1

M2+

U2

M3+

U3

Relat

ive co

st

accessbackbone

Int-IP-HS-FRR Opt-Switched

Ma+Ub: multicast a Gb/s + unicast b Gb/s

Increase in VoD loads has significant impact on the overall cost. → Having highly accurate VoD load forecasts is important!

MulticastMulticastUnicast+

MulticastUnicast+Multicast

Page 18: Infrastructure Design for IPTV Services

18

Capital Expense Across Designs (Broadcast TV)

Multicast 3Gbps + Unicast 0Gbps

0.0

1.0

2.0

3.0

4.0

5.0

6.0

Ded

-IP-H

S

Ded

-IP-H

S-FR

R

Ded

-IP-R

ing

Ded

-IP-R

ing-

FRR

Int-I

P-H

S

Int-I

P-H

S-FR

R

Int-I

P-R

ing

Int-I

P-R

ing-

FRR

P2P-

DW

DM

P2P-

DW

DM

-FR

R

Opt

-Sw

itche

d

Relat

ive c

ost

accessbackbone

1. Optical designs are more economical than IP-based ones.2. Cost is dominated by access part (except for flat IP designs).3. For IP designs, FRR is economical then using SONET links.

Page 19: Infrastructure Design for IPTV Services

19

Access Structure vs Traffic LoadsMulticast 3Gbps + Unicast 0Gbps

0.0

1.0

2.0

3.0

4.0

5.0

6.0

Ded

-IP-H

S

Ded

-IP-

HS-

FR

R

Ded

-IP-

Rin

g

Ded

-IP-

Rin

g-FR

R

Int-

IP-H

S

Int-

IP-H

S-F

RR

Int-I

P-R

ing

Int-I

P-R

ing-

FR

R

P2P

-DW

DM

P2P

-DW

DM

-FR

R

Opt

-Sw

itche

d

Relat

ive c

ost

accessbackbone

Multicast 3Gbps + Unicast 3Gbps

0.0

10.0

20.0

30.0

40.0

Ded

-IP-H

S

Ded

-IP-H

S-F

RR

Ded

-IP-R

ing

Ded

-IP-R

ing-

FRR

Int-

IP-H

S

Int-I

P-H

S-F

RR

Int-

IP-R

ing

Int-

IP-R

ing-

FR

R

P2P-

DW

DM

P2P-

DW

DM

-FR

R

Opt

-Sw

itche

d

Rel

ativ

e co

st

access

backbone

Ring access Dual-homed accessmulticast only multicast + VoD

multicast only multicast + VoD Ring access is more economical when only multicast traffic is considered. Dual-homed is better for VoD (no through traffic).

Flat IP design becomes expensive when VoD considered.

Dual-homed Ring

Page 20: Infrastructure Design for IPTV Services

20

Summary Explore potential IPTV designs in backbone network Comparison across different architectural

alternatives (use realistic capital cost model)

Design instances generated based on real topologies

Significant benefits of using multicast for broadcast TV

Optical design more economical than IP designs Ring access attractive for broadcast TV Dual-homed access attractive for VoD

Page 21: Infrastructure Design for IPTV Services

Path Protection Routingin

WDM Mesh Networks

Page 22: Infrastructure Design for IPTV Services

22

Motivation Optical design known most economical [cha06-01] Fast fail-over not yet available in optical multicast

Provisioning approach in optical backbone [SRLG]- Design multicast trees (from SHOs to VHOs) in a failure-resilient and cost-effective manner

Page 23: Infrastructure Design for IPTV Services

23

Layered architecture

Link failure in one layer → multiple failures in the upper layerTwo disjoint links may belong to a common SRLG

What is SRLG (Shared Risk Link Group)?

Page 24: Infrastructure Design for IPTV Services

24

Examples of SRLGs

two sources

multiple destinations

riskspath conduit

bridge, tunnel

Page 25: Infrastructure Design for IPTV Services

25

Service Requirements of IPTVIPTV Backbone Design Goals Fault Tolerance

Customers expect “always-on” service Resiliency against SRLG failures

Use redundant SRLG diverse paths from SHOs to VHOs

Low Cost To be competitive in the market Each link associated with port / transport cost

Find minimum cost multicast trees

Page 26: Infrastructure Design for IPTV Services

26

SHOSHO

VHO

VHO

VHOVHO

Backbone

VHO

Path Protection Routing Problem

How to create two multicast trees such that (1) provisioning cost is minimized and (2) VHOs have physically disjoint paths to SHOs?

Path Protection Routing Problem

Page 27: Infrastructure Design for IPTV Services

27

Link-Diverse vs SRLG-Diverse

d1 s2

s1 d2

d3

d1 s2

s1 d2

d3

(a) Link-diverse routing, cost=8 (b) SRLG-diverse routing, cost=9

risk1

risk2

risk1

risk2

unused Multicast path by s1 Multicast path by s2

Page 28: Infrastructure Design for IPTV Services

28

An SRLG-Diverse Solution: Active Path First

1. Construct a minimum spanning tree from one source2. Remove all SRLG links of the first tree3. Build the second minimum spanning tree with remaining links

d1 s2

s1 d2

d3

d1 s2

s1 d2

d3

First tree from s1 Second tree from s2 (reduced graph)

(a) Active Path First routing, cost=10

risk1

risk2

Page 29: Infrastructure Design for IPTV Services

29

Trap Situation of APF

d1 s2

s1 d2

d3

d1 s2

s1 d2

d3

First tree from s2 Fail to find second tree from s1

(b) Active Path First routing, trap situation

risk1

risk2

Page 30: Infrastructure Design for IPTV Services

30

Our Provisioning Approach Include SRLG-diverse constraints and solve

the problem thru Integer Programming (IP)

Compare against APF (Active Path First) heuristic Less resilient source-diverse design Less resilient link-diverse design

Page 31: Infrastructure Design for IPTV Services

31

Integer Programming FormulationMinimize total cost

SRLGdiversity

Flowconservation

Page 32: Infrastructure Design for IPTV Services

32

Applying Our IP Formulation Dataset

2 SHO and 40 VHO locations in the US

IP formulation amenable to realistic topologies!

Page 33: Infrastructure Design for IPTV Services

33

Cost Comparison Across Designs

ILP design more economical than heuristic.Cost for increased reliability affordable.

Most reliable Most Reliablecost

Reduced reliability Reduced reliability

Page 34: Infrastructure Design for IPTV Services

34

Summary First work on supporting IPTV on optical mesh

network with SRLG constraints

Compact Integer Programming formulation Minimum design cost SRLG-diversity shown affordable

Page 35: Infrastructure Design for IPTV Services

Efficient and Scalable Algorithms

for Large Network Topologies

Page 36: Infrastructure Design for IPTV Services

36

Motivation Improve path quality

Set maximum latency Limit # of intermediate nodes and links

Solving an ILP exact algorithm not scalable

Net3

Page 37: Infrastructure Design for IPTV Services

37

New Heuristic Approach Divide-and-Conquer technique for large

network topologies: Partition the problem into smaller ones Solve each small problem Integrate the solutions “well”

Page 38: Infrastructure Design for IPTV Services

38

Proposed Heuristics Greedy Local (GL)

Divide into subgraphs with two sources and a destination Solve for each graph, and consolidate solutions

Improved Greedy Local (IGL) Do GL and find the minimum cost graph Fix the shorter of the two paths and solve the rest

Adaptive Search Use any routing algorithm to find initial tree Find SRLG-diverse paths; for those w/o such, run baseline ILP.

Modified Active Path First Build one MST first; then for each destination, check if a SRLG-divers

e path exists. If yes, then fix the path; otherwise, run baseline ILP.

Page 39: Infrastructure Design for IPTV Services

39

Greedy Local (GL)

SHOSHO

VHOVHO

VHO

Step1: For each VHO, find redundant SRLG diverse paths by ILP

Step2: Consolidate solutions

SRLGdiverse

SRLGdiverse

SRLGdiverseConsolidate!

Page 40: Infrastructure Design for IPTV Services

40

Improved Greedy Local (IGL)

SHOSHO

VHOVHO

VHO

Step1: Run GL Step2: For each VHO, fix the shorter path Step3: Find missing paths all together using ILP

Leave onlyshorter paths

Solution from GLFind missing paths

Page 41: Infrastructure Design for IPTV Services

41

Adaptive Search (AS)

SHOSHO

VHO

VHO

VHOSRLG-diverse?

Yes!Then, fix as solution.

SRLG-diverse?No!

Then, replace with SRLG diverse paths.

Step1: Use any initial routing scheme to find paths Step2: For each VHO, make sure paths are SRLG-diverse

Initial routing paths

Page 42: Infrastructure Design for IPTV Services

42

Modified Active Path First (MAPF) Step1: Find minimum spanning tree from one source Step2: For each VHO, make sure SRLG counterpart part path

exists Step3: Find the missing paths all together using ILP

SHOSHO

VHO

VHO

VHODoes SRLG-diversecounterpart path exist?

Yes!Then, fix as solution.

Does SRLG-diverse counterpart path exist?No!

Then, replace with SRLG diverse paths.

Not possible!

SRLGdiverse SRLG

diverse

Minimumspanning

tree

Find missing paths w/ ILP

Page 43: Infrastructure Design for IPTV Services

43

Capital Expense Comparison

Net5 (800sec) Net6 (2sec)

Page 44: Infrastructure Design for IPTV Services

44

CAPEX Scalability AnalysisNet5

Page 45: Infrastructure Design for IPTV Services

45

Computation Time AnalysisNet5

Page 46: Infrastructure Design for IPTV Services

46

Summary Additional quality improvements of SRLG-diverse pat

hs latency limits # of intermediate nodes and links per-path upper bound of SRLGs

Efficient and scalable solutions for realistic network topologies

Page 47: Infrastructure Design for IPTV Services

47

Implications for Other Networks Cross-layer optimization

Optical + IP layer info combined Topological constraints

Mesh vs star WAN vs MAN

Cost constraints OXC port vs router port

Page 48: Infrastructure Design for IPTV Services

48

IPTV Service Monitoring [Kerpez]

Elements of IPTV Service Assurance Subscriber management

Billing, subscriptions, AAA, DRM

Video headendConverged services, VoD, Broadcast

Transport networkIP/MPLS, Ethernet, DSLAM/OLT, Gateways

Page 49: Infrastructure Design for IPTV Services

49

References[Cha06-1] Cha et al., “Case study: resilient backbone design for IPTV services,” IPTV Workshop

(WWW 2006), Edinburgh, May, 2006.[Cha06-2] Cha et al., “Path protection routing with SRLG constraints to support IPTV in WDM me

sh networks,” 9th IEEE Global Internet Symposium, Barcelona, April, 2006.[Cha06-3] Cha et al., “Efficient and scalable provisioning solutions for always-on multicast strea

ming services,” (in submission).[SRLG] Sebos et al., “Auto-discovery of shared risk link groups,” IEEE OFC, March 2001.[APF] Xu et al., “On the complexity of and algorithms for finding the shortest path with a disjoint

counterpart,” IEEE/ACM ToN, 14(1):147-158, 2006.[Kerpez] K. Kerpez et al., “IPTV Service Assurance,” IEEE Communications, September, 206