Transcript Carrier Ethernet for Mobile Operators

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
MEF Co-Chair, Mobile Backhaul Group
Sr. Consultant, Harris Stratex Networks
[email protected]
Ralph Santitoro
MEF Chair, Web Marketing Committee
Director of Carrier Ethernet Solutions, Turin Networks
[email protected]
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

BTS
Ethernet over µwave
EoPDH over µwave
PDH (E1/T1)

Node B
Ethernet over PDH
BSC
Aggregation Network
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
Service Charges per Connection:
PDH and ATM over PDH vs. New Wireline
$40,000
$37,044
Stay on PDH
Revenue
– 2M, 4M, 6M, etc. for N x E1s
circuits
• Carrier Ethernet OpEx costs
increase in smaller increments
as bandwidth increases
$30,000
PDH and ATM over PDH
$20,000
New wireline
Ethernet
$10,000
$6,887
$0
CY05
• PDH (E1/T1) OpEx costs increase
as a step function as bandwidth
increases
CY06
CY07
CY08
CY09
CY10
Calendar Year
Source: Infonetics Research Mobile Backhaul Equipment,
Installed Base, and Services, 2007
– Bandwidth can easily be added to
an Ethernet UNI
– No need to add new circuits as with
PDH networks
• Carrier Ethernet options satisfy
the #1 financial challenge to
mobile operators:
– OpEx cost savings
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
circuits
Legacy RAN BS
SDH
circuits
Legacy RAN NC
8
Packet off-load to Carrier Ethernet Network
– Use Case 1a
Legacy
Carrier Ethernet Network
Generic
Interworking
Function
(Data traffic)
UNI
Generic
Interworking
Function
UNI
PDH / SDH Network
(Voice traffic)
RAN BS
PDH
circuits
SDH
circuits
RAN NC
• 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
Carrier Ethernet Network
Generic
Interworking
Function
PDH
circuits
(All traffic)
UNI
RAN BS
Generic
Interworking
Function
UNI
PDH
circuits
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
PDH
circuits
(Voice traffic)
SDH
circuits
Carrier Ethernet Network
(Data traffic)
RAN BS
UNI
UNI
RAN NC
• 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
RAN BS
UNI
UNI
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
– CoS Requirements
– Service Performance (Delay, Loss)
– Connectivity Service Types
– Traffic/Service Separation
– Clock synchronization
UNI
Carrier Ethernet
Network
RAN BS
EVC
UNI
UNI
RAN NC
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