1. DOCSIS 3.0 DS Planning & Bandwidth Management
John Downey, Consulting Network Engineer – CMTS BU

2. Agenda Objectives Terms M-CMTS I-CMTS Optional Architectures
SPAs, timing servers, e-qams, 5x20, 3G60..
I-CMTS
20x20
Optional Architectures
Frequency Stacking Levels
Frequency Placement
Isolation Concerns

3. DS Questions & Potential Concerns
Why it’s Needed
Competitive pressure, offering higher tiers of service, more customers signing up
Frequency Stacking Levels & Placement
What is the e-qam max output with four channels stacked
Do channels have to be contiguous?
Isolation Concerns
Applications w/ different service grps lead to overlaid networks
Signals destined for one node could “bleed” over to another
DS Frequency Expansion to 1 GHz
Amplifier upgrades are occurring now. It’s best to make the truck roll once, so think about diplex filters, spacing, taps, etc.
We need to add more DS capacity now in the form of DOCSIS With it come some considerations specific to the DS such as:
Why it’s Needed – This can range from competitive pressure, to higher tiers of service, to more customers signing up.
Frequency Stacking Levels & Placement – What is the e-qam max output with 4 channels stacked and do the channels have to be contiguous?
Isolation Concerns – Whenever applications have different service groups, we have overlaid networks. Signals destined for one node could “bleed” over to another.
DS Frequency Expansion to 1 GHz – Amplifier upgrades are occurring now. It’s best to make the truck roll once. Think about diplex filters, spacing, taps, etc.

4. Business Objectives Allow more BW for DOCSIS 1.x & 2.0 CMs
Limit/reduce more node splits
Introduce new HSD service of 50 to 100 Mbps
Allow migration of existing customers to higher tier and DOCSIS 3.0 capability
Better Stat Muxing
The business objectives for many cable system operators today is to provide faster speeds to compete with FioS. These speeds are for DS and US. DOCSIS 2.0 can provide approximately 37 Mbps on the DS and 27 Mbps on the US, aggregate speed.
Some per-CM speeds are approaching these peak rates and exceeding them. The only way to offer higher rates than what DOCSIS 2.0 can offer is to upgrade to DOCSIS 3.0.
Instead of reducing node sizes, which can exceed $10,000 per node split, it may be more economical to add more DS frequencies and logically bond traffic across multiple DS channels. This will require new CMTS equipment and cable modems.
This allows more aggregate speed for higher tier services to share and/or to offer per-CM peak rates in excess of what a single channel can offer.
At the expense of more spectrum allocation, a DOCSIS 3.0 CM can offer 150 Mbps on the DS and 100 Mbps on the US. This may be necessary for 100x25 Mbps service or to allow many modems at 20x5 service to share the bigger “pipe”.

5. DOCSIS 3.0 Terms Local DS = CMTS DS Remote DS = E-QAM DS
Primary = DOCSIS messaging
Secondary = Bonding
“Wideband” generically used to describe D3.0 DS bonding
Channel Grouping Domain (CGD) is MxN mac domain
Mac Domain = 1 DS & N USs
Service group = CMTS Fiber Node config
M-CMTS is an architecture, not necessarily D3.0
Provides DS load balance within MxN domain
I-CMTS allows MxN and bonding within linecard
D3.0 CM supports minimum of 4 US and 4 DS chs
CMs on market are 4x4 (TI-based) & 8x4 (Brcm-based)
To level set, it’s best to understand terminology. DOCSIS 3.0 has added some new terms such as:
Local DS = CMTS DS
Remote DS = E-QAM DS
Primary = DOCSIS messaging
Secondary = Bonding
Combiner Group Domain (CGD) is an MxN mac domain where the old terminology for a Mac Domain was 1 DS and N USs. Keep in mind that more USs in a mac domain require more maps and eats into the DS throughput. Approximately every US port uses .25 Mbps of DS capacity for maps.
DOCSIS 3.0 CMs support a minimum of 4 US and 4 DS channels even though it could be more.
“Wideband” is generically used to describe D3.0 DS bonding even though it was originally a proprietary term.
M-CMTS stands for modular CMTS and is an architecture, not necessarily DOCSIS This architecture requires a DTI server and e-qam with DTI capability. This provides DS load balance of legacy CMs within an MxN domain. This means a D1.x / 2.0 CM could move between multiple DSs without forcing a move to a new set of USs.

6. DOCSIS 3.0 DS Ch Bonding over SPA Overview
Uses M-CMTS compliant Edge-QAM
Cisco RFGW-1D and RFGW-10
Harmonic NSG-9000
Increase legacy DS port density of uBR10K
Uses DTI timing source for DS channels
Enables legacy DOCSIS [1.x/2.0] CMs to use external QAMs for operation
Allows MxN mac domains
Eliminates need for PC from 5x20 card
Allows bonding on all channels in a BG
Hits the 100 Mbps BW mark on a 3-channel CM
The downstream Wideband channel is created by taking DOCSIS frames, putting them into MPEG-TS packets, and placing those MPEG-TS packets onto QAM carriers. However, instead of placing those MPEG-TS packets “horizontally” in time along a single QAM carrier as is done in traditional DOCSIS, the Wideband protocol places those MPEG-TS packets “vertically” across the QAM carriers assigned to a Wideband channel. A DOCSIS frame is literally tipped on its side and striped our across a group of QAM channels.

7. Narrowband Network Topology

8. DOCSIS 3.0 DS Ch Bonding over SPA Requirements
uBR10012 CMTS
PRE-2 (PRE4 available now)
MC5x20 linecard
H card suggested
US ports needed and host
Dual SPA jacket card
Saratoga and spumoni (SIP600)
DS bonding SPA, “Modena”
1 Gbps fiber or copper ports
DTI timing card
DTCC, “Eightbells”
DTI Server (Symetricom)
M-CMTS compliant EQAM
Cisco RFGW-1D
RFGW-10
Harmonic NSG9000
WCM300 (Linksys BroadLogic-based CM)
SA 3-Ch DPC 2505 (BCM 3381)
Cisco/SA DPC x4 TI-based CM
Cisco/SA DPC x4 Brcm-based CM
While the WB jacket card is similar to a SIP, the processors on the card are not in the data path and are more of a control system for the SPAs

9. Hardware Configuration Supported

10. RFGW-10 13RU 2 Supervisor Slots (1+1) 10 DS RF Linecard Slots
240 Gbps system performance (20 Gbps mid-plane per slot)
10 DS RF Linecard Slots
Slots 3-12
12 RF coax ports
1,2, or 4 QAMs per port, 12x4 = 48 QAMs
Each line card supports 2 GE interfaces which connect directly to the supervisor switch fabric
Redundant Power Supplies
AC/DC – 4400 watts
Single power supply will support fully loaded chassis
Each DC PEM has 2 inputs (60A each) & both need to be connected
Two Timing and Control Card Slots (redundant)
Controls integrated RF Switch (N+1) assembly
Provides DOCSIS DTI server and/or client functionality
Built-in RFSW
Single or Dual zone (11 & 12 designated protect)
GigE’s support both Fiber and Copper SFPs
Roadmap for DS-96, DS-192, DS-384 linecards
Can mute individual QAM channels
LC GigEs do not go out of service when linecard crashes

11. DOCSIS 3.0 M-CMTS System D3.0 BG Primary uBR10K CMTS D3.0 DS + Primary
DTI Server
D3.0 DS + Primary
Jacket
Card
DTI Card
DTI Card
D3.0 BG
WB DS
SPA
M-CMTS EQAM
WB DS
SPA
Primary Ch
CPU/RP
Primary
MC5x20H
SA DPC 3000
SA DPC-2505 CM CM CM CM
Backhauls
uBR10K
CMTS
NB DS

12. I-CMTS: 20x20 & Features in “Bighorn”, 12.2(33)SCC
License/PID
Label on faceplate
Description
UBR-MC20X20V-20D
Configured as UBR-MC20X20V-20D
Supports 20 DS chs on 5 connectors
I-CMTS support
DOCSIS 3.0 features such as S-CDMA, Logical Chs, US Ch Bonding, …
20x20 can backup 5x20 cards for N+1
DS bonding within card, but not across cards or to SPA
SPA and 20x20 coexistence supported
Supported with PRE2, but requires DTCC cards
If an exclusive I-CMTS setup, DTI server & “cable clock dti” not required
Mixed Annex mode not supported (CSCtd56484)

13. MC2020: Overview Integrated Cable Line Card 20 Downstream Channels
5 Physical connectors, 4 channels per port
Only 52 dBmV max output/ch when 4 freqs stacked
54-1 GHz
License for 0, 5, or 20 DSs
20 Upstream Channels
Virtual interface and Frequency stacking supported
5-65 MHz
Brcm 3140 US chip
Supports DOCSIS 3.0 Features
DS bonding, US bonding, BPI etc.

14. MC2020: Software Features 5 mac domains per line card
Cable interfaces
Upstream channels in MDs like 5x20
5 Integrated Cable “Controllers”
Downstream configuration on “controller”
30 DS bonding groups
Wideband-Cable interfaces
20 Integrated-Cable interfaces
Added to MDs with CGD commands

15. MC5x20 Product Line MC5x20S Dec ‘02 MC5x20U – Apr ‘04
Integrated UPx
Onboard Analyzer
INCA
Broadcom 3033 DS
Annex B only
TI4522 for US
ATDMA, 5-42 MHz
NPE400 processor
US Max burst < 1600
JIB1
MC5x20U – Apr ‘04
Broadcom 3034 DS
Better DS MER
No SAW filter
Annex A & B
TI4522E for US
ATDMA 5-65 MHz
US Max burst of 3500 (2000 suggested)
MC5x20H – Dec ‘06
Broadcom 3040 for DS
Broadcom 3140 for US
SCDMA hardware
Logical ch support
Ingress cancellation
Pre-EQ
Analyzer
Double memory
NPEG1 processor
Need 12.3(17b)BC4 & >
JIB2
USCB (100 Mbps limit)
Text in red is carried over to the next column. Text in blue is carried over to the next column to the right.
The H card shows the ingress cancellation config and it can be turned off while the S & U can not be turned off.
CSCsg45624 moved support for H card to 12.3(17b)BC4.
The S can only do annex B 5-42 MHz US and 2000 byte max fragment size.
The U and H can do annex A or B, 5-65 MHz US and 3500 max fragment size.
S and U use TI4522 chip.
H uses Broadcom 3140 US chip with SCDMA hardware capability.
H card requires CBT3.3 to display US spectrum.
They all use the same mod profile number scheme even though the linecard will overwrite some parameters better suited for the US chip in that card.
The H can turn off ingress cancellation while the S and U can not.
The S&U report SNR before internal EQ, the H reports after internal EQ leading to typical 3 dB better SNR vs the S & U. I expect a difference in the 5x20U and the 5x20H just because of post-EQ readings, but not too extreme.
With all this in mind, the 28U uses Broadcom, but the 3138 chip.
I remember doing a quick test in my lab in RTP a while back and did notice worse SNR readings near the Annex A Euro-DOCSIS upper end of 60 MHz or so. Most customers just stay below the upper end regardless. Maybe there is a legitimate problem with the 5x20U in annex A mode with internal rolloff/group delay in the internal US filter.
520S/U have JIB1. 520H has JIB2. Both JIB1/JIB2 support 2-DS x 8-US physical ports. JIB2 has additional capability to support SCDMA/Logical Channel. Based on current implementation, with 2-local-DS, it implies support of 2 MAC Domains.

16. MC20x20V & 3G60 Linecards MC20x20V Dec ‘09 3G60 – Dec ‘10
Broadcom ? DS
4 Freqs per connector
I-CMTS
DS Bonding
Broadcom 3140 for US
5-65 MHz
SCDMA & Logical chs
Bighorn IOS and later
5 domains
JIB3
Linerate US Ch Bonding
3Gig DS = 72 DS ch capacity
M-CMTS
Broadcom 3142 for US
5-85 MHz
12 chs across 4 connectors
Danube & later
15 domains
JIB3
Text in red is carried over to the next column. Text in blue is carried over to the next column to the right.
The H card shows the ingress cancellation config and it can be turned off while the S & U can not be turned off.
CSCsg45624 moved support for H card to 12.3(17b)BC4.
The S can only do annex B 5-42 MHz US and 2000 byte max fragment size.
The U and H can do annex A or B, 5-65 MHz US and 3500 max fragment size.
S and U use TI4522 chip.
H uses Broadcom 3140 US chip with SCDMA hardware capability.
H card requires CBT3.3 to display US spectrum.
They all use the same mod profile number scheme even though the linecard will overwrite some parameters better suited for the US chip in that card.
The H can turn off ingress cancellation while the S and U can not.
The S&U report SNR before internal EQ, the H reports after internal EQ leading to typical 3 dB better SNR vs the S & U. I expect a difference in the 5x20U and the 5x20H just because of post-EQ readings, but not too extreme.
With all this in mind, the 28U uses Broadcom, but the 3138 chip.
I remember doing a quick test in my lab in RTP a while back and did notice worse SNR readings near the Annex A Euro-DOCSIS upper end of 60 MHz or so. Most customers just stay below the upper end regardless. Maybe there is a legitimate problem with the 5x20U in annex A mode with internal rolloff/group delay in the internal US filter.
520S/U have JIB1. 520H has JIB2. Both JIB1/JIB2 support 2-DS x 8-US physical ports. JIB2 has additional capability to support SCDMA/Logical Channel. Based on current implementation, with 2-local-DS, it implies support of 2 MAC Domains.

17. 3G60 Basics
3 GibE ports for DS modular capacity supporting 72 total chs
Even annex A can support 72 DS chs assuming oversubscription
15 max mac domains
8 max USs per domain with 12 in later release, possibly
5-85 MHz US bandpass (no cable freq-range)
8175 SIDs per domain
20 physical US ports
4 consecutive connectors support 12 channels in any mix
Default will be 4 US chs /conn at 3 connectors with 4th empty
No bonding between GigE controller connections
No SPA and 3G60 interaction ?
License to support DS channel options, 0, 24, 40, etc
16x16 minimum
Danube IOS and PRE4
No 3G60 support on PRE-2

18. uBR10012 PRE Evolution: Taking the uBR10k into the 3rd Gen. CMTS Space
DOCSIS Devices per Chassis *
45k +
64k +
Benchmark PPS (MPPS)
2.8
4.5 9
Routing Processor Memory Size
512 MB
1024 MB
2048 MB
Routing Processor Clock
257 MHz
500 MHz
800 MHz
Forwarding Processor Memory Size
PXF Processors 32 64
PXF Clock
100 MHz
150 MHz
300 MHz
Line card Interconnect
1.6 Gbps
3.2 Gbps
6.4 Gbps
Packet Buffer
128 MB
256 MB
Scheduler
VTMS
HQF
BC train supports the "VTMS" scheduler (i.e. for PRE1 and PRE2 in BC)
12.2S train supports the "DOCSIS WFQ" Scheduler (i.e. for PRE2 and PRE4 in 12.2S, since PRE1 is not supported)
* Dependant upon on features enabled

19. 7246 & 7225 VXR I-CMTS Solution
uBR-MC88V full DOCSIS 3.0 compliant linecard with same form-factor as MC28U
Simple upgrade of linecard swap with no wiring change
4x greater DS port density than 28U
Two linecards per 7225 and four per 7246
Requires NPE-G2 & supported in IOS 12.2SCD, “Congo”

20. Questions
Are their any rules-of-thumb to estimate the service group size?
What recommendations are there for HE combining/splitting in order to avoid intrusive changes later?
Are there any impairments in the HE or in the plant that will affect DOCSIS 3 .0 more compared to earlier versions?
Isolation
Off-air Ingress
Attenuation
Freq assignments, spectrum allocation, plant limits
If a small amount of extra BW is needed, is it possible to split 4 chs from a DS port to use 2 chs in one SG and the other 2 in another SG?

21. Option 1: 100 Mbps Tier & 2 Channel US Bonding
Cisco Products
UBR10012 CMTS w/ PRE4
“Amazon”, 12.2SCB IOS
Spumoni SIP with 6 SPAs
5x20H linecards
RFGW-1 EQAM
3 chassis
6 modules each
DPC/EPC 3000 CM
DPC/EPC 3002 eMTA
Resources (Per SG)
5 DS frequencies
1 I-DS
4 M-DS
(5 Primary)
2 US frequencies
2 channel bonding

22. Option 1 = 100 Mbps Service Tier
5 DS freqs
2 US freqs
Remote Bonding
Remote Primary
Local Bonding
Local Primary
16-QAM
64-QAM
3.2 MHz
6.4 MHz
5, 5x4 MAC domains with ATDMA & TDMA USs
E-qam overlaid for 2 nodes 70/2 = 35 connectors
3 e-qam chassis with 6 modules each
4 freqs * 35 = 140 QAMs = 6 SPAs = Spumoni & PRE4

23. 20x20 Option 1: 100 Mbps Tier & 2 Ch US Bonding
Cisco Products
UBR10012 CMTS w/ PRE4
“Bighorn”, 12.2SCC IOS
20x20V linecards
DPC/EPC 3000 CM
DPC/EPC 3002 eMTA
Resources (Per SG)
4 DS frequencies
4 I-DS
2 US frequencies
2 channel bonding

24. 20x20 Option 1 = 100 Mbps Service Tier
4 DS freqs
2 US freqs
Local Bonding
Local Primary
16-QAM
64-QAM
3.2 MHz
6.4 MHz
5, 4x4 MAC domains with ATDMA & TDMA USs
DS connector overlaid for 2 nodes, 35 connectors*2 = 70 nodes
4 freqs * 35 = 140 QAMs = PRE4

25. DOCSIS 3.0 Option 2 5 DS freqs 3 US freqs 2x5 domain Remote DSs Local
3.2 MHz
6.4 MHz
This diagram graphically shows fiber nodes vs frequency allocation with pros and cons of this scenario. This allows load balance of legacy modems between 2 DS frequencies and bonding on 4 DS frequencies. This requires 5 DS frequencies on the plant and 3 US frequencies.
We can use dcc tech 4 to load balance Basic subs across the local DS and one e-qam primary. If modems have a DS frequency in their config file, use “load balance exclude static strict” so only dynamic load balance takes place.
Pros
Four bonding freqs / e-qam connector
Only 1 e-qam connector per 8 nodes
Basic = 2 DS/2 nodes with DCC support
US load balance of 2.0 CMs
One US connector shared across 2 nodes for diminishing D1.x CMs
Cons
Requires M-CMTS architecture
Requires five DS & three US freqs
Must push 3.0 CMs to remote DS
Bonding group must be same IP bundle
CM ranging overlap with “real” data?

26. 20x20 DOCSIS 3.0 Option 2 8 DS freqs 3 US freqs 5x5 domain Local DSs
3.2 MHz
6.4 MHz
This diagram graphically shows fiber nodes vs frequency allocation with pros and cons of this scenario. This allows load balance of legacy modems between 2 DS frequencies and bonding on 4 DS frequencies. This requires 5 DS frequencies on the plant and 3 US frequencies.
We can use dcc tech 4 to load balance Basic subs across the local DS and one e-qam primary. If modems have a DS frequency in their config file, use “load balance exclude static strict” so only dynamic load balance takes place.
Pros
8 bonding freqs per 2 connectors
Only 5 connectors per 8 nodes
Can provide 8 ch DS bonding
US load balance of 2.0 CMs
One US connector shared across 2 nodes for diminishing D1.x CMs
Cons
Requires 8 DS & 3 US freqs

27. DOCSIS 3.0 Option 2 Wiring Diagram
This diagram displays how DSs are potentially combined with e-qam modulator DSs and then split to feed multiple service groups or fiber nodes. Downstream four is not used and its associated USs are used in the four mac domains. Upstream connectors use internal frequency stacking on even connectors 0-14 and external stacking on connectors

28. DOCSIS 3.0 Option 3 5 DS freqs 3 US freqs 5x5 domain Remote DSs Local
3.2 MHz
This diagram graphically shows fiber nodes vs frequency allocation with pros and cons of this scenario. This allows load balance of legacy modems between 5 DS frequencies and bonding on 4 DS frequencies. This requires 5 DS frequencies on the plant and 3 US frequencies.
We can use dcc tech 4 to load balance Basic subs across the local DS and all 4 e-qam primaries.
The biggest hurdle will be number of e-qam connectors needed and total e-qam channels supported for 1 chassis. If the chassis only supports 48 total e-qam channels and each linecard uses 16, then only 3 linecards would hit the 48 ch limit for e-qams.
6.4 MHz
Pros
Four bonding freqs / e-qam connector
One e-qam connector per 2 nodes
Basic = 5 DS/2 nodes with DCC support
US load balance of 2.0 CMs
One US connector shared across 2 nodes for diminishing D1.x CMs
Cons
Requires M-CMTS architecture
Requires five DS & three US freqs
Must push 3.0 CMs to remote DS
Four e-qam connectors and 16 e-qam chs per 8 nodes

29. DOCSIS 3.0 DS Considerations
Frequency assignments
CMTS may be limited to 860 MHz or 1 GHz
Legacy CMs (1.x & 2.0) limited to 860 MHz bandedge
E-qam limited to contiguous 24 MHz or 4 channel slots
Annex A may only be 3 chs vs 4 for annex B
CMs may be limited to 50 or 60 MHz passband
M-CMTS architecture requires DTI and local USs
Distance limitation, time offset differences, level differences
Resiliency is another topic to address
If one DS frequency goes bad in the field, how will CMs recover or react?
DOCSIS 3.0 has some inherent issues to address. One of which is frequency assignments. The CMTS may be limited to 860 MHz or 1 GHz and spectrum allocation may be scarce in the actual cable plant.
The E-qam is typically limited to a contiguous 24 MHz passband or 4 ch slots. Keep in mind that Annex A may only be 3, 8 MHz chs vs 4 annex B, 6 MHz chs. The CM limitation may be 50 or 60 MHz passband. D3.0 CMs require at least 60 MHz passband. Example; having the local freq at 117 MHz & the e-qam remote at 740 MHz will not work since the CM only has a 60 MHz passband.
The M-CMTS architecture requires a DTI server and US ports from the CMTS. The spec has a distance limitation of 200 meters between the CMTS and e-qam. There are ideas of utilizing GPS to sync multiple time servers to allow the e-qam to be in a hub site and the CMTS in the HE.
One potential issue with a DS being remote and a DS being local is the difference in time offsets. Load balancing using DCC tech 4 is difficult when the time offset delta is greater than 10 time offset ticks from one DS to another. This may require e-qam “tweaking”. Also, D1.1 config files are required for dcc to work. Another concern could be level differences if the DS frequencies are too far apart. Never use an S card for a modular host and only 3 SPAs are allowed to be hosted per linecard.
There’s no need for D3.0 CMs to load balance since they share a bigger pipe.
Resiliency is another topic to address. If one DS frequency goes bad in the field, how will CMs recover or react? Today it may be the case that the bonding CM will come back up as online and act as a D2.0 CM in regards to speed. Work is currently underway by many CMTS vendors to create dynamic bonding groups and allow a CM to bond across the frequencies it determines to be good, but that information needs to be relayed back to the CMTS.

30. DOCSIS 3.0 DS Considerations (cont)
E-qam licensing?
CM requires 1.1 config file
More DS = more US
Testing and maintaining multiple DS channels
Physical chs have not changed for DOCSIS 3.0
Test equip with built-in CMs need to support bonding
DS ch bonding max power with 4 freqs stacked
Four chs stacked on 1 connector limited to 52 dBmV/ch
DOCSIS 1.x/2.0 DS is 61 dBmV max output
DS isolation issues
One issue concerns economics. How do you deal with frequency stacked DSs if not using them all? Some vendors may offer software licensing to pay when you use.
Testing and maintaining multiple DS channels may not a big issue since the physical channels have not changed for DOCSIS Although, handheld test equipment with built-in modems will have to be updated to support bonding.
Another overlooked issue is DS isolation and E-qam max output power per channel. These will be expanded upon in the next slide. DS channel bonding max power with 4 frequencies stacked on one connector is limited to 52 dBmV per channel. The DOCSIS 1.x/2.0 DS specification is 61 dBmV max output with only 1 channel per connector. This needs to be addressed in the HE combining and splitting so all channels that are combined reach the fiber optic transmitter at the proper level and flat.
For RFGW-1…Single Mode: 52 dBmV to 62 dBmV, Dual Mode: 48 dBmV to 58 dBmV, Tri Mode: 46 dBmV to 56 dBmV, Quad Mode: 44 dBmV to 55 dBmV.

31. DS Ports with Edge-QAM for DS Bonding
61?
52?
DS0 U0
U1 U2 U3
1x4
DS1
DS2
DS3
DSs 0-3 = 603 MHz
Edge-QAM
E-QAM = 609, 615, 621, & 627 MHz
Potential Isolation Path
DS Combiner
DS Splitter
This figure depicts possible DS isolation and level issues that can occur when DS frequency is narrowcast and another DS frequency is introduced across multiple nodes.
Isolation amplifiers can be used to prevent too much loss from the 4-way splitter and keep the signal from backfeeding when architectures like this are implemented. Keep in mind that isolation is related to the combiner devices and how close of a match to 75 ohms the common leg is and where it is connected. The 2-way splitter could have poor isolation because of poor return loss of the fiber transmitter or the CMTS US port. The problem with an isolation amplifier is an active device could be a single point of failure and also, can the isolation amp handle a high input of power of 50 dBmV or so?
It may be best to combine the e-qam modulator DSs closer to the transmitter and use RG6 cable to alleviate some headend (HE) loss. Also, if 16 or more frequencies are stacked on one connector, the device may need to incorporate internal tilt to overcome HE cabling tilt. Sixteen frequencies contiguous will be ~ 100 MHz of passband. If a typical allocation is MHz, this could be 1 dB of tilt. Higher frequency selections will have less of an effect. Also, 16 frequencies stacked will have less power per channel, ~ only 44 dBmV! It may be wise to design the HE combining and splitting with a worst case scenario now.
DS Tx
Requires:
5 DS freqs
3 US freqs in each node
Isolation amp

32. Isolation Amp W Can this device handle 50 dBmV inputs?
This is one example of an isolation amplifier
Can this device handle 50 dBmV inputs?

33. Design Rules & Restrictions
D3.0 spec goes to 1 GHz, some equipment may not
SA DPC2505 speced to 930 MHz
DPC2505, 3 ch CM needs all 3 DSs for 111 Mbps
Can do annex B &/or A; but requires more spectrum
D3.0 spec requires 60 MHz capture window
DPC3000 capture of 96 MHz over most spectrum
82 MHz max window supported over entire spectrum
TI 4x4 CM (60 MHz window)
Brcm 8x4 CM (2, 32 MHz bands or 1, 96 MHz band)
Can use RCC templates to setup both tuners
DS freqs must be contiguous within tuner block unlike 4x4 CMs
The DOCSIS 3.0 DS specification indicates 1 GHz support, but some equipment may not support that. For example, before the specification was finalized, a DS bonding modem was introduced with 3-channel bonding capability. The SA DPC2505 is widely used in the industry, but only uses 3 separate DS tuners and speced to 930 MHz. This allows the channels to be almost anywhere in the DS spectrum, but not fully DS 3.0 certified.
The DPC2505 needs all three DSs for 111 Mbps. This can be done with annex B &/or annex A chs, but requires more spectrum if annex A is used.
BCM 3380 chip (8x4) supports 2 tuner windows of 32 MHz each. This is the current generation chip that is used for our products (3010, 3212, 3825, 3925).
BCM 3382 chip (8x4) supports 1 tuner window of 96 MHz. This is a cost reduced chip only for CM and EMTA, not gateway. Based on what I’ve heard from TW so far, they are only interested in D3.0 gateways so I don’t expect them to want any 3382 based products.
The 3383 (8x4) and 3384 (16x4) will use full spectrum tuners?

34. Modem Steering Restrict legacy eMTAs to Local DS
Enforce legacy CMs to only register on Primary- only DS or move to a specific DS frequency
Enforce legacy CMs to move to specific DS freq
Force 3.0-capable CMs to initialize on Remote DS
Can specify UCDs sent for each DS
Put voice call service flows on a primary DS
cable docsis30-voice downstream req-attr-mask 0 forb-attr-mask
EDCS explains this feature
Directing CMs is a topic that can not be overlooked. It may be necessary to restrict legacy eMTAs to the Local DS for linecard redundancy purposes. The e-qams on the market today may not support redundancy. For overlay architectures, it may be needed to enforce legacy CMs to only register on Local DS or move to a specific DS frequency. Because D3.0 modems today only support four channels of bonding, it may be necessary to force a 3.0-capable CM to initialize on remote/e-qam DS for channel allocation issues and speed requirements. Allowing a 3.0 CM to use the local DS for primary traffic may only leave 3 channels for bonding and not the intended speed. Having the local frequency at 117 MHz and the e-qam remote at 740 MHz will not work since the CM has a 60 MHz passband. Using a Cisco CMTS, attribute commands are used to achieve the above criteria. Refer to other CMTS vendors for similar functionality and commands.
To restrict voice services to the MC5x20;
cable service attribute voice-enabled downstream-type HA-capable
To keep all D3.0 CMs on the e-qam modulator primary;
cable service attribute ds-bonded downstream-type bonding-enabled enforce
To force Basic subs to register on a Primary-only DS or a specific DS frequency, respectively;
cable service attribute non-ds-bonded downstream-type bonding-disabled
cable service attribute non-ds-bonded legacy-ranging downstream-type frequency <Hz>
These options may be warranted when overlaying D3.0 service with another service from the same CMTS or a different CMTS. We can assign specific US ports to be sent as UCDs for specific DSs. So, the local DS can be a 2x5 mac domain/combiner grouping domain (CGD), but only specific US ports sent as UCDs for the local DS or e-qam channel primary.
Example CLI: interface Cable5/0/0
downstream Modular-Cable 1/0/0 rf-channel 0 upstream 1 3
downstream local upstream 0 2 4

35. Node Splitting Edge-QAM 2x4 domain appears as 2, 1x2 domains 1x4 DS0U0
U1 U2 U3
This diagram is an example of splitting a mac domain into 2 service groups and specifying particular USs to specific DSs.
Example CLI: interface Cable5/0/0
downstream Modular-Cable 1/0/0 rf-channel 0 upstream 2 3
downstream local upstream 0 1
Edge-QAM
2x4 domain appears as 2, 1x2 domains

36. Summary Cost effective and faster time to market
Decrease DS costs – deploy D3.0 later with no additional CMTS investment!
Targeted insertion of D3.0
Leverage existing US chs while adding more DS capacity
Load balance 1.x/2.0 and enable D3.0 when needed
Minimizes capex & opex
Leverage D3.0 bonding for D2.0 tiers & services
Better stat-mux efficiency & improved consumer experience

37. Summary (cont) Long term D3.0 service planning
Insure optimized frequency allocation
Enable seamless upgrade to higher D3.0 tiers
Wire once & add QAM chs as tiers or service take-rates go up
End-to-end solution minimizes risk
CMTS, QAM, and CPE
Can also disable DS bonding
No cable mrc-mode
Per-CM exclude with vendor specific MIB or TLV
One way to have a D3.0 CM not do DS bonding is using a vendor specific MIB (for example for SA CMs its), saCmDsBonding OBJECT-TYPE
SYNTAX INTEGER {disable(0), enable(1)}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The MIB will choose whether to enable downstream channel bonding for bonding-capable modems.
Non-bonding modems will ignore this MIB object.
0 : Disable downstream channel bonding.
1 : Enable downstream channel bonding.
This MIB will take effect at the next reboot. This MIB value will be stored to NonVolatile memory(NVM) and will persist across reboots. If the MIB is set via the config file, the CM will store the new setting and reboot if a change is necessary. Removing the setting from the config file will not change the value stored in NVM: the CM will continue to operate using the previously stored value. If an SNMP SET is used to modify the value, then the CM will not use the new setting until the next reboot occurs or is commanded. A factory reset of the CM will set the stored value back to 1."
DEFVAL { 1 } ::= { cmInterfaceInfo 15 }
Or you can set the DOCSIS Downstream Service Flow Forbidden Attribute Mask TLV (25.32) to 0x which will prevent the SF from using a bonding group even when the modem is in the w-online(pt) state.

38. Hardware Configurations
Carrier
WAN
PRE-2
PRE-4
Saratoga
HHGE
Yes No
Spumoni
HHGE
Yes No
Spumoni
2x1GE No No
Spumoni
5x1GE
Yes*
Yes
Spumoni
8x1GE No No
Spumoni
1x10GE No
Yes
Ranking of Support (with max config per option) :
PRE-2 + 1xSpumoni + 4xHHGE with 4xModena on Spumoni
PRE-2 + 1xSaratoga + 4xHHGE with 2xModena on Saratoga
PRE-2 + 2xSpumoni with one 5x1GE + 2xModena per Spumoni
PRE-4 + 2xSpumoni with one 5x1GE + 3xModena per Spumoni
PRE-4 + 2xSpumoni with one 1x10GE + 3xModena per Spumoni
Spumoni with HHGE must allow for up to 4 HHGE and up to 4 WB SPAs
Note: * Only two GE ports on the 5x1GE SPA will be active with PRE-2

39. Configuration Options – Overall View
H/W
PRE-2
PRE-4
Slot1/2
Slot3/4
No SIP
Saratoga SIP
Spumoni SIP
Saratoga SIP
HHGE no
n/a
up to 4
Modena
up to 2
2x1GE
5x1GE
1x10GE
up to 3
up to 1
Up to 1
Combo 1
Combo 2
Combo 1 = HHGE Non-SPA based Configurations
Combo 2 = SPA Backhaul based Configurations