Download - Motorola Docsis

Motorola Confidential Proprietary

MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2005

Migration to Docsis 3.0Migration to Docsis 3.0

Michael GannonSenior Technical Architect

Motorola Proprietary Confidential


Voice & Data Solutions

Agenda

How should I plan for future Docsis bandwidth needs?

( or, “When is supply more important than demand “ )

Docsis 3.0, M-CMTS, I-CMTS , What really is important.

Lessons learnt from existing channel bonding solutions.




Carrier Usage Transitions

125 Carriers per FN125

DOCSIS High Speed Data

MPEG VOD

IPTV VOD

SwitchedDigital

DigitalBroadcast

AnalogBroadcast

timeToday “EverythingOn Demand”

1




HPCB – A bandwidth model for all services• The average bandwidth requirements to be supplied

to a Fiber Node (FN) for any service can be planned as the product H*P*C*B of four factors:

H = Households per fiber nodeP = Penetration (subscribers per household)C = Concurrency Ratio (supplied concurrently active)B = Bandwidth (peak bits per second)

• HPCB applies to any service:– High Speed Data (HSD)– Voice over IP (VOIP)– Video On Demand (VOD) [MPEG or IPTV]– Switched Broadcast (SB) [MPEG or IPTV]

• HPCB’s add per High Speed Data (HSD) service tier• Concurrency C is the inverse of “overbooking”

– 1.0% C means 100-to-1 overbooking– Worldwide HSD C range: 0.75 to 2.0%; – US Average C: 1.0% (1000 4M subs per DS QAM)

• Concurrency is a economic decision to supply.– Wrong question: “What’s the demand for HSD?”

• It’s infinite– Right question: “What shall I economically supply?”

• Depends on competition: DSL and PON

H – Households Passed

P – Penetration ratio

C – Concurrency ratio

750 Households per Fiber Node

times 30% HSD = 225 HSD subs

= 2.25 concurrent HSD streams

B – Bandwidth

= 18.0 HSD Mbps/FN

times 1.0%

times 8 Mbps HSD tier

Typical 2006 HSD deployment: split one 40 Mbps DOCSIS QAM to two FNs




Typical 2004 HSD+VOIP Deployment

Fiber Node 2

Fiber Node 3

Fiber Node 4

Fiber Node 12x8

CMTSLineCard

U1U0

U3U2

U5U4

U7U6

D1

D0df1

Fiber Node Average Supplied Capacity : 4.5 MbpsSingle Cable Modem Peak Throughput: 40 Mbps38.8 Mbps / 4.5 Mpbs = maximum 8.6 FN per DS = 1:8 splitting

D2.0 CM

2004 Example HSD per FN:H = 750 HH/FNP = 0.20C = 0.01 B = 3 MbpsHPCB = 750 * 0.2 * .01 * 3 = 4.5 Mbps avg per FN

Fiber Node 8




Typical 2006 HSD+VOIP Deployment

Fiber Node 2

Fiber Node 3

Fiber Node 4

Fiber Node 12x8

CMTSLineCard

U1U0

U3U2

U5U4

U7U6

D1

D0df1

Fiber Node Average Supplied Capacity : 20 MbpsSingle Cable Modem Peak Throughput: 40 Mbps38.8 Mbps / 20 Mpbs = maximum 2 FN per DS = 1:2 splitting

PON Competition: 20 to 100 Mbps peak service. D3.0 Downstream Channel bonding is required for 100 Mbps service.

D2.0 CM

2006 Example HSD per FN:H = 750 HH/FNP = 0.30C = 0.01 B = 8 MbpsHPCB = 750 * 0.35 * .01 * 8 = 18.0 Mbps avg per FN




As Bandwidth (B) increases, supplied Concurrency (C) can decrease

Observed concurrency data points:

Dialup (56K): 10%

ATT Frame Relay(1.544 Mbps): 2%

Cable HSD (6 Mbps): 1%

Liberty (30 Mbps): .67%

Japan PON (100 Mbps): 0.25%

C

B




“Endgame” Thought ExperimentHSD endgame: 100 Mbps peak to all subs 0.25% concurrency

H = 750 P = 0.5 C = 0.0025 B = 100 Mbps

HPCB = 94 Mbps/FN or 2.5 DS QAM channels per FN

About 5X supplied HSD in 2006

How do I economically increase DOCSIS supplied bandwidth by 5X or more?

VOD Endgame:

“Everything On Demand” Network DVR; or “What I Want When I Want” (WIWWIW)

H = 750 P = 0.75 C = 0.50 (?) B = 10 Mbps (2 SDTV+1 HDTV) (?)

HPCB = 2800 Mbps/FN or 73 (US) DS QAM channels per FN

About 40X supplied VOD in 2006Today: 100% MPEG VOD; Future: ??% IPTV

How do I economically transition fromMPEG to IPTV VOD?

Key point: VOD bandwidth may be 30X the bandwidth of HSD

HSD

VOD

EuroDOCSIS VOD endgame 2800 Mbps requires 57 Euro channels

2.5 QAMs per FN 73 QAMs per FN

EuroDOCSIS HSD endgame 94 Mbps requires 2.0 Euro channels




CMTS DOCSIS 3.0 Feature Requirement

• MAC Layer– Downstream Channel Bonding – Upstream Channel Bonding

• Network Layer– IPv6 support– IP Multicast (IGMPv3, SSM, QoS)

• Security– Certificate Revocation Management– Runtime SW/config validation– Enhanced Traffic Encryption (AES)

– Certificate Convergence – Secure Provisioning

• Network Management– Diagnostic Log– Extension of Internet Protocol

Data Records (IPDR) usage– Capacity Management – Enhanced signal quality

monitoring• Commercial Services

– Layer 2 VPN’s– T1/E1 TDM Emulation

• Physical Layer– Switchable 5-85 MHz US Band– S-CDMA Active Code Selection



What is, and what isn’t, important about M-CMTS?




M-CMTS Goals• “Independent scalability of CMTS functions from DS

PHY”– Means: need to add DS channels without adding US

channels• “Lower the cost to deliver video over DOCSIS service to

be competitive with today’s MPEG VOD”– 2005 Incremental DOCSIS DS channel cost: $24K ASP for

2DS+8US CMTS blade = $12, 000 per DS channel– 2005 Incremental MPEG VOD channel cost: $12K for 24-

channel MPEG EQAM = $500 per DS channel• But with no rate limiting, scheduling, QOS, encryption, VOIP

compression, or RF switching




M-CMTS/ D3.0 Network Diagram

Regional Area

Network

CINGBE

Switch

MPEG VODServer

HFC

UpstreamEdge

DEPI EQAM

CMTS

DTI

MPEG EQAM

M-CMTS: Modular CMTSDTI: DOCSIS Timing InterfaceDEPI: Downstream External Phy I/FGBE: Gigabit EthernetEQAM: Edge QAMERMI: Edge Resource Mgr I/FDC: Downstream ChannelCIN: Converged Interconnect Network

CMTS Core

DRFI

Edge Resource Manager

ERMI

STB

3.0CMs

2.0CMs

DCs

NSI

DEPI

DEPI

T-MPT




What’s important and not for M-CMTS• What’s important is that the two M-CMTS goals be met:

- De-coupling downstream and upstream capacity; and

- Lowering the cost of downstream capacity.• What’s important is the adoption of the DEPI specification

by the EQAM industry.– Enables a transition to DOCSIS IPTV with DEPI EQAMs.

• What’s NOT important is the concept of separating the upstream PHY layer:– Separation into an “upstream shelf” and definition of an

“Upstream Edge Physical Interface” (UEPI)– Independent vendor implementations of “CMTS Core” and

“upstream shelf” MAC functions;




CMTS Migration

Traditional CMTS• Integrated CMTS

Modules with Fixed Downstream and Upstream channels

• Ex. 2 DS and 8 US Channels

• Features High Availability “Protected” Bandwidth

• Today’s CMTS

Integrated CMTS• Integrated CMTS Modules

with Decoupled Downstream and Upstream channels

• Ex. xx QAM DS Module• Features High Availability

“Protected” bandwidth

• 2007 Deployment

Modular CMTS• Modular CMTS Modules

with Decoupled Downstream and Upstream channels

• Ex. xx QAM DS Module• Features Superior

Scalability with “Unprotected” bandwidth

• 2007 Deployment




Recommendations1. Economically introduce DOCSIS 3.0 bonding

– Start with 3 or 4 carriers, non-adjacent if possible.

– Split the carriers to multiple (4 or 8) fiber nodes

– Re-use coupled I-CMTS cards for bonding if possible

2. Economically increase average supplied DOCSIS capacity per FN• Start with decoupled “D-CMTS” if possible• Split DOCSIS QAMs to fewer fiber nodes

3. Integrate SDV+VOD and increase EQAM Capacity as content (and hence Concurrency) increase• Based on video features (e.g. CA)

4. Economically transition from MPEG to IPTV VOD• Use DEPI-standard EQAMs (with PSP

and DTI)• Support standardization of DIBA• Transition D-CMTS to M-CMTS above 4

to 8 DOCSIS QAMs (160->320 Mbps) per FN

SDV+VOD Carriers(EQAMs)

Decrease splitting Increase carriers (at 1:1)

DOCSIS“First Four Carriers”

1:16

…

1:4

…

1:2

FN 1

FN 2

FN 3

FN 4

FN 5

FN 6

FN 7

FN 8

FN 16

1:1

…




Architecture Migration

CoupledC-CMTS

DecoupledD-CMTS or M-CMTS

DIBA

Average supplied bandwidth per Fiber Node

0.5 QAMs

1.0 QAMs

2.0 QAMs

8.0 QAMs

4.0 QAMs

2007 2008 2009

73 QAMs ?

20xx ?

20 Mbps

40 Mbps

80 Mbps

160 Mbps

320 Mbps

2800 Mbps



Channel Bonding ChallengesReal World View




What Does it Take to Deploy DS Channel Bonding?

• Obvious – Channel Bonding CMTSs and CMs– Downstream Spectrum

• Less obvious– Upstream Spectrum– Subscribers’ Education – Subscribers’ Equipment

• Re-configuration – at least• Upgrade - possibility




Lessons Learned • Performance expectations

– Raw throughput– UDP Performance– TCP/FTP Performance

• Supporting ‘Legacy’ CMs and ‘Channel Bonding’ CMs– Overlay Network or Combined Network– Balancing 100+ Mbps subscribers with “Normal”

subscribers– New sizing concepts are needed

• Concurrency Rate

– New tools are needed• How to handle voice

– Voice traffic goes as non-bonded• No “sequence number”




Key Factors for FTP Performance

FTP Server

DOCSIS 3.0 or Pre-DOCSIS 3.0 Channel Bonding CMTS

DOCSIS 3.0 or Pre-DOCSIS 3.0 Channel Bonding CM

FTP Client

GigaEthernet

HFC

IP Network

Key Factors

1. Round Trip Time (RTT)

2. TCP Window Size

3. Speed of the Slowest Link

4. Performance of the Client’s PC




RTT and TCP Window Size

FTP Client

FTP Server

GigaEthernet

IP Network HFC

GigaEthernet

GigaEthernet

100 Mbps

Time




Channel Bonding FTP

Max_FTP_Throughput =

(((‘TCP_window_size’ * 8) / ‘Link_Speed’) / RTT) * ‘Link_Speed’

Or just

((‘TCP_window_size’ * 8) / RTT)




Default Window Size

Operating SystemStandard RWIN Value (TCP

Receive Window Size) in Bytes

Windows 95/98/98SE/NT 8K

Windows ME/2000/XP 16K

Windows XP SP2 64K

Windows Server 2003 64K

Macintosh OS X 32K

Linux Redhat 9 32K




FTP Throughput

0

10,000,000

20,000,000

30,000,000

40,000,000

50,000,000

60,000,000

70,000,000

80,000,000

90,000,000

100,000,000

RTT - sec

Bits

/sec

16,384

32,768

65,536

131,072

262,144

FTP Throughput Vs. Round Trip Time (RTT)

< 6 msec < 22 msec




Subscriber’s PC Configuration:1. Increase the TCP window size ( >= 262,144)

a) Information and tools available off the WEBi. Do a search for “TCP Tuning” on

a. Get about 1,200,000 hits b) TCPOptimizer.exe

2. Settings -> Control Panel -> System Properties -> Advanceda) Performance Setting

i. Visual Effects ==> “Adjust for Best Performance”ii. Virtual memory ==> “4096 MBytes”iii. Processor scheduling ==> “Background Services”

3. Enabling “Select ACK” can improve throughput performance with the presence of packet lost.

4. Increase the client PC (and server if possible) performancea) Processor speedb) RAM sizec) Disk speedd) BUS speed




Summary

Plan your future bandwidth requirements Consider how to economically transition to Docsis 3.0

What can you do today at least cost

Consider what services & bandwidths you will offerHow do you educate your subscribers ?




Thank You

Download - Motorola Docsis

Top Related