Carrier Ethernet
for Mobile Operators
Facilitating the Evolution to
Packet Transport Networks
Peter Croy, Harris Stratex Networks
Ralph Santitoro, Turin Networks Amsterdam, 8 May 2008
Co-presented by:
Peter Croy Ralph Santitoro
MEF Co-Chair, Mobile Backhaul Group MEF Chair, Web Marketing Committee
Sr. Consultant, Harris Stratex Networks Director of Carrier Ethernet Solutions, Turin Networks
peter.croy@hstx.com RSantitoro@TurinNetworks.com
Mobile Architecture Evolution
- Backhaul Network Evolution
• Driven by massive growth of lower ARPU mobile data
traffic
– High ARPU voice traffic still requires stringent “TDM quality” clock
synchronization and QoS.
• Evolution focused on network cost reductions
through one or more of the following approaches:
1. RAN backhaul bandwidth optimization over PDH
• More bandwidth over fewer PDH circuits Ethernet over PDH
2. Mobile data traffic off-load onto lower “cost per bit” packet
transport network
• Ethernet over HFC “cable”, xDSL, etc.
• PDH/SDH network assures clock synch. for high ARPU voice traffic
3. All mobile traffic on lower ”cost per bit” Carrier Ethernet network
• “Emulation” of E1/T1 PDH circuits over Ethernet
• Used when majority of traffic is “packet-based”
• Availability of Carrier Ethernet Network
3
Mobile Network Evolution
PDH over µwave
Ethernet over µwave
BTS EoPDH over µwave
PDH (E1/T1) BSC
Aggregation Network
Node B Ethernet over PDH SDH Carrier Ethernet
RNC
SDH/SONET over Fibre
eNB
Ethernet over Fibre AGW
Mobile Backhaul Network Evolution to Carrier Ethernet
Mobile user applications evolving to IP
Mobile backhaul network evolving to Carrier Ethernet
4
Key Reasons for Carrier Ethernet
• OpEx savings for increasing amount of low ARPU data traffic
– Economically meets ever increasing bandwidth requirements currently
constrained by cost prohibitive PDH access networks
– Simpler and lower cost to add bandwidth when compared to adding PDH
circuit bandwidth
• Convergence of wireless and wireline
– Enables convergence of wireline and mobile backhaul traffic over single
Carrier Ethernet multiservice transport network
• Simplifies network and service management
• Mobile traffic growth is broadband and IP centric
– Carrier Ethernet is optimized for packet data traffic
5
Ethernet Options Solve Backhaul Cost Problem
Worldwide Mobile 1st Mile Backhaul • PDH (E1/T1) OpEx costs increase
Service Charges per Connection: as a step function as bandwidth
PDH and ATM over PDH vs. New Wireline increases
$40,000 – 2M, 4M, 6M, etc. for N x E1s
Stay on PDH $37,044 circuits
$30,000
• Carrier Ethernet OpEx costs
increase in smaller increments
as bandwidth increases
Revenue
– Bandwidth can easily be added to
$20,000 PDH and ATM over PDH
New wireline an Ethernet UNI
Ethernet
$10,000 – No need to add new circuits as with
$6,887 PDH networks
$0
• Carrier Ethernet options satisfy
CY05 CY06 CY07 CY08 CY09 CY10 the #1 financial challenge to
Calendar Year mobile operators:
Source: Infonetics Research Mobile Backhaul Equipment,
– OpEx cost savings
Installed Base, and Services, 2007
6
How is Carrier Ethernet Deployed?
• Carrier Ethernet Backhaul Technologies (non-exhaustive list)
– Ethernet over Fiber
– Ethernet over NG-SDH/SONET: GFP (ITU-T G.7041)
– Ethernet over Microwave
– Ethernet over PDH: MLPPP/BCP (RFC1990/RFC3518) or GFP (ITU-T G.8040)
– Ethernet over DSL (EFM): IEEE 802.3ah 2BaseTL, ITU-T G.991.2 G.SHDSL
– Ethernet over Hybrid Fiber-Coax (HFC)
• All of the above can utilize the following (non-exhaustive list):
– Provider Bridges (IEEE 802.1ad)
– Provider Backbone Bridges (IEEE 802.1ah)
– Provider Backbone Bridges with TE extensions (IEEE 802.1Qay)
– MPLS Pseudowires (RFC 4448)
– Circuit Emulation over Ethernet (MEF 8)
Carrier Ethernet backhaul technology selection based on many factors
including current infrastructure, mobile service mix and growth, etc.
7
A View of Backhaul Networks Today
• Legacy = “Non-packet RAN” and “Non-packet transport”
Legacy Transport Network
PDH / SDH Transport Network
PDH SDH
circuits circuits
Legacy RAN BS Legacy RAN NC
8
Packet off-load to Carrier Ethernet Network
– Use Case 1a
Legacy
Generic
Carrier Ethernet Network Generic
Interworking (Data traffic) Interworking
Function Function
UNI UNI
PDH / SDH Network
(Voice traffic)
PDH SDH
circuits circuits RAN NC
RAN BS
• Mobile data traffic off-loaded to Carrier Ethernet
Network using emulation technologies
• PDH / SDH network continues to transports voice and
deliver clock synchronization
9
Emulation over Carrier Ethernet Network
– Use Case 1b
Legacy
Generic Carrier Ethernet Network Generic
Interworking Interworking
Function (All traffic) Function
PDH PDH
circuits UNI UNI circuits
RAN BS RAN NC
• RAN nodes with PDH interfaces
– Transport all traffic over Carrier Ethernet network via
emulation technologies
10
RAN with PDH and Ethernet Interfaces
– Use Case 2a
Legacy Eth/IP
PDH/SDH Network
(Voice traffic)
PDH SDH
circuits circuits
Carrier Ethernet Network
(Data traffic)
RAN BS RAN NC
UNI UNI
• RAN BS/NC equipped with Ethernet UNIs and PDH/SDH
interfaces
• PDH/SDH network continues to transport voice and
deliver clock synchronization
• Carrier Ethernet network for mobile data traffic off-load
11
All Ethernet
– Use Case 2b
Eth/IP
Carrier Ethernet Network
UNI UNI
RAN BS RAN NC
• New RAN nodes with Ethernet interfaces
• All traffic transported over Carrier Ethernet network
12
Carrier Ethernet Transport Network for
Mobile Backhaul and Wireline services
13
Network and Service Convergence
• Convergence of wireline and wireless transport
networks for triple and quad play operators
– “Network Abstraction Layer”
• End-to-end MEF service definitions
• MEF service definitions are agnostic to the transport or
access network technology used to deliver them
– Enables migration to hybrid networks and data off-load models
• Mobile operators require cost-effective, simple service
provisioning and network operations
– Base Station re-hosting to different Network Controllers based on
changes in radio coverage plan
• Base stations moved to home into different BSC/RNC
– Re-hosting changes made through provisioning from NOC
• Eliminates need for “truck rolls to thousands of cell sites !
14
OSS Integration, OAM and Provisioning
- MEF specifications integrate multiple OAM standards
• IEEE 802.3ah Link OAM
– Verify first mile link connectivity
• IEEE 802.1ag Connectivity Fault Management
– Verify end to end connectivity
– Loopback and Link Trace
• ITU-T Y.1731
– Framework for performing fault management end-to-end or at
intermediate points in the network
• MEF 10.1 Technical Specification
– Defines Frame Delay, Frame Delay Variation, Frame Loss Ratio
– Measure service performance for SLAs
• Ethernet OAM provides end-to-end “abstraction layer”
– Network OSS integration planning
– Simplified operations procedures
15
Mobile Backhaul Implementation Agreement
• UNI Requirements
– Ethernet OAM for Fault Management
– Automated Provisioning (LMI)
– Link Protection and Fault Recovery Requirements
– Bandwidth Profiles
• EVC Service Requirements UNI
Carrier Ethernet
RAN BS Network
– CoS Requirements EVC UNI
– Service Performance (Delay, Loss)
– Connectivity Service Types RAN NC
UNI
– Traffic/Service Separation
– Clock synchronization RAN BS
The MEF Implementation Agreement provides guidelines for
deploying Carrier Ethernet in mobile networks
16
Summary
• Carrier Ethernet enables mobile operators to migrate
their backhaul networks from TDM to packet transport
– At their own pace driven by their individual business priorities
• Carrier Ethernet facilitates the convergence of wireline
and wireless backhaul
– Over a common transport network infrastructure
• The MEF’s Mobile Backhaul Implementation
Agreement provides:
– Guidelines for mobile operators on how to architect a service model
for Carrier Ethernet networks for mobile backhaul applications
www.MetroEthernetForum.org
17