Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
Fernando Villarruel, Cisco Systems Michael Eggert, Cox Communications Harj Ghuman, Cox Communications Marek Hajduczenia, Charter Communications
For IEEE 802.3 Interim March 5-8 2018
Beyond 10km Optical PHYs Study Group
Backhaul Capacity for Optics in Remote PHY and answers to other questions
Adding detail to messaging so far…
• Remote PHY and Ethernet • DWDM, how many wavelengths • 100G and/or 200G • Non RPHY services • Context for OTN • Context for Cost • Context for timelines
What is Remote PHY ?
“Remote PHY” is a collection of specifications sanctioned by CableLabs that allows DOCSIS to ride over an Ethernet Network
• CableLabs, MHAv2 Series
• CM-SP-R-PHY: Remote PHY System Specification
• CM-SP-R-DEPI: Downstream External PHY Interface Specification
• CM-SP-R-UEPI: Upstream External PHY Interface Specification
• CM-SP-R-DTI: Remote DOCSIS Timing Interface Specification
• CM-SP-R-OSSI: Operation support Systems Interface Specification
• CM-SP-R-GCP: Generic Control Plan Specification
• CM-SP-R-OOB: Out of Band signals Specification
**No new Ethernet requirements.
RPHY Framing
802.1Q VLAN
(optional)
MPLS Header
(optional)
IPv4/6 Header
L2TPv3 Pseudowire
Header
Payload DOCSIS Frames
Ethernet CRC
802.3 Ethernet Header
HUB R-PHY
Node
R-PHY
Node
Aggregation Node Router
Modem
Operation Systems Billing System
DOCSIS Core
VIDEO Core
R-P
HY
Fra
mer
Client to Client
Eth. Backhaul
“RPHY Domain” Ethernet Physical Layer
DOCSIS Analog Eth
PHY Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Remote-PHY defines Pseudowires (L2TPV3) that transmit: -DOCSIS (data traffic) -Broadcast Video -and management within an IP packet and an Ethernet frame. - Transmitted over Ethernet physical layer - Ethernet/IP frames make DOCSIS/Video invisible to the network - no impact to coaxial plant, packet cores, modems & OSS/BSS - DOCSIS data makes up the bulk of the payload volume - Allows a multivendor interoperable environment.
A note on Service Cores
• DOCSIS and Video cores organize and distribute a bandwidth availability per the policy given by Operation and Billing systems. (OSS/BSS)
• DOCSIS data is unique per service group.
• Video can be unique per service group or the same for two or more service groups.
• When video is the same for all service groups we call it broadcast – Fox, CBS, NBC, etc.
Remote PHY Backhaul Physical vs. logical functions
R-PHY Physical Distribution
DOCSIS
VIDEO
HUB R-
PHY
Node
R- PHY
Node
Aggregation Node
• 10 - 80 km • Existing Fiber plant • 100GHz DWDM • 1-16 λs per fiber • Duplex
10GE (existing PHY) < 2 km New Fiber
10-16 PHY Nodes
MUX
DMUX
R-P
HY
Fra
mer
Client to Client
Eth. Backhaul
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
R-PHY
Node
R-PHY
Node
R-PHY
Node Logical Distribution
DOCSIS
VIDEO
HUB
Router
(Multicast)
SG
SG
SG
SG
R-PHY
Node
R-PHY
Node
R-PHY
Node
R-PHY
Node
R- PHY
Node
R-PHY
Node
R-PHY
Node
R-PHY
Node
R- PHY
Node
R-PHY
Node
R-PHY
Node
R-PHY
Node
R-PHY
Node
• ~200 Subscribers / service group (SG) • Broadcast video
• one video SG for all. • Unicast video considered data carried by DOCSIS.
MUX
DMUX
R-P
HY
Fra
mer
Client to Client
Eth. Backhaul
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
Eth PHY
What is the capacity needed for the Remote PHY Ethernet Backhaul?
• Single direction (downstream) capacity, per lambda
• Router in Agg Node servicing:
• 16 R-PHY Nodes
• 4 or 8 R-PHY nodes per DOCSIS service group
• Compounded annual growth rate (CAGR) 40% DOCSIS Data
• Static 1.25 Gpbs Broadcast video
• Broad Market View
• United States (US) SG start at 3 Gbps
• Latin America / Europe (Latam/EU) start at 1 Gbps
• Start in 2019 as most capacity has already been planned for then.
Client to Client R-PHY Backhaul Capacity
0
50
100
150
200
250
300
2018 2020 2022 2024 2026 2028 2030
Bac
khau
l Cap
acit
y (G
pgs
)
Timeline (Yrs)
US 4 PRD per SG
LATAM / EU 4 RPD per SG
US 8 RPD per SG
LATAM / EU 8 RPD per SG
0
50
100
150
200
250
300
2018 2020 2022 2024 2026 2028 2030
Bac
khau
l Cap
acit
y (G
pgs
)
Timeline (Yrs)
US 4 PRD per SG
LATAM / EU 4 RPD per SG
US 8 RPD per SG
LATAM / EU 8 RPD per SG
Backhaul Optics Planning
(1-5) 10G ZR
(1-3) 100 G
(1) 200 G
• 100G DWDM Ethernet PHY needed to make this transition
• Leverage mature technology
0
50
100
150
200
250
300
2018 2020 2022 2024 2026 2028 2030
Bac
khau
l Cap
acit
y (G
pgs
)
Timeline (Yrs)
US 4 PRD per SG
LATAM / EU 4 RPD per SG
US 8 RPD per SG
LATAM / EU 8 RPD per SG
Backhaul Optics Adoption Timelines
(1-5) 10G ZR
(1-2) 100 G Eth. PHY
(1) 200 G Eth PHY
• Adoption time frame is dependent on cost delta between 1-5 10G DWDM ZR and 100G DWDM optics
• Early deployments with DWDM 10G ZR, quickly exhaust fiber capacity.
100G client (Ethernet) specification is needed today to enable RPHY is full scale deployments. - Routers must be installed day one with capability to grow to 100G backhaul. Can use a handful of 10G ports to start, but not for long. - note, 200G is also useful, but 100G is the high volume runner with expected robust cost reductions.
What about other services’ impact on backhaul ?
• Unicast. • Terminate at multiple
packet cores. • 12-18, 10G downlinks • 200G useful • Don’t have to use a router
could use an (OTN) Muxponder at aggregation node
• A minority of links compared to R-PHY.
See: http://www.ieee802.org/3/B10K/public/18_01/knittle_b10k_01_0118.pdf
Cores Router (100G)
100G
...…
.....
……
……
……
…
.……
……
...
100/200
GE
DWDM
Aggregation Router (10G)
…
…
…..
10G
RPD
RPD
RPD
RPD
RPD
RPD
RPD
RPD
HDC NODES 8-18 RPD’s
HFC NODES 8-18 RPD’s
HFC NODES 8-18 RPD’s
Other Services
8-18 RPD’s
10G 10G 10G
…..…
……
……
..
..…
..…
..…
..…
..…
..…
PACKET CORES
…
…
10 GE DWDM
10G
..…
100G
MuxP (20x10)
MuxP
100 / 200G OTN
DWDM
100G
10 GE DWDM
Field Router
Field Router
HU
B / HEAD
END
O
UTSID
E PLANT
• Available today
• In definition and CableLabs and proposed at this study group
• Proprietary link solutions
Added detail to messaging so far…
• Remote PHY and Ethernet • DWDM, how many wavelengths • 100G, 200G • Other services • Context for OTN • Context for Cost • Context for timelines
Fernando Villarruel, Cisco Systems Michael Eggert, Cox Communications Harj Ghuman, Cox Communications Marek Hajduczenia, Charter Communications
For IEEE Ad-Hoc February 20, 2018
Backhaul Optics for Remote PHY Answers to questions so far