Carrier Ethernet for Mobile Backhaul

1
Carrier Ethernet for Mobile Backhaul

• CEWC Berlin
• September 22nd 2008

2
Panelists
Ran Avital MEF Market Research Co-Chair VP of
Strategic and Product Marketing Ceragon
Networks rana_at_ceragon.com 972-52-5847526
Name Title Company Name E-mail Phone [phone]
4981
Dirk Lindemeier Mobile Backhaul Solutions
Development Nokia Siemens Networks dirk.lindemeier
_at_nsn.com 49 151 5515 3351
Jonathan Olsson MEF Mobile Backhaul IA
Editor Standardization Coordinator,
Ericsson jonathan.olsson_at_ericsson.com 46 8 404
3720
Brian Bortz, CEO, Resolute Networks brianb_at_Resolu
teNetworks.com 972-52-2210548
2
3
Carrier Ethernet for Mobile Backhaul

• Introduction

Ran Avital MEF Market Research Co-Chair VP of
Strategic and Product Marketing Ceragon
Networks rana_at_ceragon.com 972-52-5847526
4
Agenda

• The Carrier Ethernet value proposition for mobile
  backhaul
• MEF Specification work to optimize Carrier
  Ethernet for Backhaul
• Carrier Ethernet technologies and applications
  for Mobile Backhaul
• Circuit Emulation Services over Ethernet
  (CESoETH)

5
Mobile Backhaul Market Survey

• Evaluate network planning assumptions and
  integrate the derived needs from the MEF
  Implementation Agreement (IA)
• 41 operators/worldwide coverage (APAC 20, EMEA
  49, NA 27 and LA 5)
• Independent research commissioned by the MEF

6
Mobile Backhaul Market Survey- Highlights
Ethernet performance attributes Standards?
Single or multiple Availability Requirements?
Availability Requirements?
Latency budget for synchronization?
Will you require Ethernet Service OAM (IEEE
802.1ag, ITU-T Y.1731)?
How likely to transport legacy traffic over
Ethernet using an interworking function?
How Many CoS?
7
Carrier Ethernet for Mobile Backhaul

• Trends, Technologies and Applications

Dirk Lindemeier Mobile Backhaul Solutions
Development Nokia Siemens Networks dirk.lindemeier
_at_nsn.com 49 151 5515 3351
8
Mobile Backhaul Has Dynamic Growth

• New mobile applications and bandwidth
  growth(gt100 in 2008 with much more to come)

9/06
7/07
Legacy TDM
Movies, music, news, more music, text, web, more
content ..
9
Industry trends

• Demand for bandwidth will grow
  
  disproportionately more than
  
  revenue for the operator
• The bandwidth increase will primarily be on Best
  Effort data user services, and driven by flat
  fee business models
• Search for technologies to provide cheaper and
  more effective ways to meet the capacity grow at
  a lower CAPEX and OPEX
• Evolution towards Ethernet/IP based mobile
  solutions

Source Light Reading
10
Why Carrier Ethernet for Mobile Backhaul?

• Mobile services need Coverage
• Leasing backhaul services is a common practice
• High capacity, low cost creates new opportunities
• Wholesale
• RAN sharing
• Converged operations

A better way to do business in Mobile Backhaul
11
Key Reasons for Carrier Ethernet

• Carrier Ethernet
• Economically meets exploding bandwidth
  requirements currently constrained by the
  prohibitive costs of legacy networks
• Leverages rapid move to Carrier Ethernet for
  wire-line traffic enabling a single integrated
  wire-line and mobile backhaul network
• Much easier for service providers to manage and
  maintain
• Most mobile traffic is broadband/IP centric
• Carrier Ethernet is optimized for packet data
  traffic
• Overcomes TDM (T1/E1) services scalability
• This alone makes Carrier Ethernet the compelling
  choice
• Time/urgency
• Carrier Ethernet removes the barrier to timely
  progress

12
Ethernet Options Solve Backhaul Cost Problem

• PDH (T1/E1 etc.) costs climb directly with
  bandwidth
• Ethernet wire-line costs grow gently with large
  bandwidth increases (Eth, DSL, PON, cable)
• New IP/Ethernet wire-line options to satisfy the
  the 1 investment driver operational cost savings

Stay on PDH
Ethernet
Source Infonetics Research Mobile Backhaul
Equipment, Installed Base, and Services, 2007
13
Carrier Ethernet the common denominator
µwave
BTS
BSC
Copper
Carrier Ethernet Network
NodeB
RNC
Fibre
AGW
eNB

• Installed 2G base is TDM based, requires
  emulation
• 3G is evolving to IP/Ethernet rapidly
• 4G will be IP/Ethernet based from the start
• Ethernet is common denominator for all relevant
  backhaul technologies

14
What are mobile operators doing?

• HSDPA 3.6Mbps is a widespread reality, next step
  (7.2Mbps) is imminent
• IP/Ethernet is acknowledged as the only possible
  solution to accommodate ever increasing traffic
• New NodeBs are being rolled out with IP/Ethernet
  interfaces as the standard configuration
• Tangible synchronization solutions are becoming
  available
• Hybrid backhaul (sync over parallel E1/T1) used
  during early rollouts, starting 2007
• IEEE1588v2 standardized, products 2008
• Synchronous Ethernet standardized (G.8261,
  G.8262, pending G.8264), products 2008

15
MEF Member InitiativeMobile Backhaul
Interoperability Showcase

• Mobile Backhaul Interoperability Demonstration
• Conducted by MEF Member (EANTC)
• In collaboration with and sponsored by 15 MEF
  Members
• Showcase at Mobile World Congress (Barcelona,
  2/08 and CTIA., Las Vegas, 4/08)
• Live Mobile Application Demonstration
• End-to-end services, Resiliency
• End-to-end CE Service OAM
• Quality of Service support
• Performance monitoring
• Bandwidth profiles
• Circuit Emulation Services
• White Paper
• Public Multi-Vendor Mobile Backhaul
  Interoperability Test

• This event was not conducted by the MEF. Test
  methodology and results solely the responsibility
  of EANTC in collaboration with the participants

16
A complete answer for emerging requirements
17
Reality check where are we today?

• NodeB Ethernet interfaces available from all
  major 3G vendors live here in Berlin
• Installed base and new rollouts
• Ethernet microwave radios widely available live
  here in Berlin
• Installed base and new rollouts
• Synchronization over Carrier Ethernet based on
  IEEE1588v2 live here in Berlin
• Mobile broadband over multi vendor Carrier
  Ethernet end to end live here in Berlin
• MEF implementation agreement almost ready

18
Carrier Ethernet for Mobile Backhaul

• The Implementation Agreement Draft

Jonathan Olsson MEF Mobile Backhaul IA
Editor Standardization Coordinator,
Ericsson jonathan.olsson_at_ericsson.com 46 8 404
3720
19
Introduction to the MEF MBH IA

• What initiated the work?
• Predicted increased data traffic volumes
• RAN going packet and challenges thereof
• Deployment scenarios
• Desire for cost reduction

MEF set out to define Carrier Ethernet service
requirements for mobile backhaul
20
Scope of the Implementation Agreement

• Utilize existing MEF technical specifications
  with required extensions to interface and service
  attributes.
• Provide requirements for UNI-C and UNI-N.
• Define requirements for Ethernet Services.
• Provide requirements for Link OAM and Service OAM
  Fault Management.
• A single Metro Ethernet Network with external
  interfaces being only UNIs.
• Provide high-level requirements for CoS.
• Define synchronization requirements where
  possible for transparent packet based
  synchronization methods.
• Functional requirements applicable to GIWF
  interfaces.

21
Mobile Backhaul Implementation Agreement
The structure of the IA provides guidelines for
several mobile technologies specific guidelines
for a given mobile technology may also be
specified

• UNI Requirements
• UNI Type
• Ethernet OAM (Link OAM and Service OAM)
• Service Requirements
• CoS Requirements
• Applying MEF Services
• Synchronization

UNI
Metro Ethernet Network
RAN BS
UNI
RAN NC
UNI
RAN BS
22
Use Cases

• There are many possible deployment scenarios
• The Implementation Agreement identifies four
  generic deployment scenarios that capture the
  main short term and long term deployment
  possibilities

23
But firstthe site concept in the IA

• The details inside the RAN sites, e.g. cell site
  or network controller site, are outside the scope
  of MEF
• RAN BS base station site
• RAN NC network controller site
• But we know a site may be composed of a single
  node or multiple nodes that are attached to a UNI
• A site is expected to provide the UNI-C functions
  as specified in the IA

24
Legacy Mobile Backhaul Migration
Packet offload over Carrier Ethernet Use Case 1a
Metro Ethernet Network
Generic Interworking Function
Generic Interworking Function
UNI
UNI
Legacy Network
RAN BS
RAN NC
Legacy
Eth/IP
Emulation over Carrier Ethernet Use Case 1b
Metro Ethernet Network
Generic Interworking Function
Generic Interworking Function
RAN BS
UNI
UNI
RAN NC
25
When RAN nodes are equipped with Ethernet
RAN dual stack Use Case 2a
Legacy Network
Metro Ethernet Network
RAN BS
UNI
UNI
RAN NC
Legacy
Eth/IP
Full Ethernet Use Case 2b
Metro Ethernet Network
RAN BS
UNI
UNI
RAN NC
26
Service Requirements

• Typically there are 1-2 RNC sites and between
  hundreds to thousands of RBS sites
• Bandwidth requirements for a base station site
  will vary may range from a few Mbps to over a
  Gbps
• Services need to be
• Scalable
• Flexible
• Cost effective
• Service types (port-based and VLAN-based)
• E-Line
• E-LAN
• E-Tree

27
Service Definitions Point-to-Point

• Similar to leased lines
• Requires traffic separation per RAN BS at RAN NC

EVC 1
EVC 2
EVC 3
28
Service Definitions Rooted Multipoint

• Similar behavior as leased lines
• Supports simpler RAN BS and RAN NC solutions
• Multiplexing could be used for increased traffic
  separation

Leaf UNI
Leaf UNI
Root UNI
Leaf UNI
EVC 1
EVC 2
29
Traffic separation

• Guidelines for the number of CoS classes to use
• Bundling traffic types into limited number of CoS
  classes
• CoS class performance requirements

30
Ethernet OAM

• Ethernet OAM entities configuration options
• Fault Management fault localization and
  accountability
• Performance Monitoring service performance
  validation (For Further Study)

RAN NC
RAN BS
Metro Ethernet Network
Mobile Operator MA
Available with UNI Type 2
MEP
MIP
31
Current Status

• Substantial updates to the IA after previous
  Straw Ballot
• Internal review Straw Ballot
• Continue to liaise with other industry forums to
  ensure industry alignment
• Anticipate completion 2008 Q4

32
Carrier Ethernet for Mobile Backhaul

• Synchronization, MEF 8 and MEF 18

Brian Bortz CEO, Resolute Networks brianb_at_resolu
tenetworks.com 972-52-2210548
33
Synchronization

• Types of sync
• Frequency
• Phase
• Time
• 3 different methods
• Common Clock
• Packet Based Synch
• IEEE 1588 V2,
• Differential Clock Recovery
• Adaptive Clock Recovery
• Synchronous Ethernet
• Current approach
• References G.8261
• Focus on packet based timing methods

34
Concept of Synchronous Ethernet
Packet Network
Data
Data
L2-L7 (Packet)
L2-L7 (Packet)
L2-L7 (Packet)
Stratum 1 Traceable reference
Recovered Clock
Physical Layer
Physical Layer
Physical Layer

• Uses the PHY clock
• Generates the clock signal from bit stream
• Similar to traditional SONET/SDH/PDH PLLs
• Each node in the Packet Network recovers the
  clock
• Performance is independent of network loading

Timing Flow
Data Flow
35
Concept of IEEE 1588 V2
PRS GPS / SynchE /
36
CES and the MEF Certification Program

• Circuit Emulation Services over Ethernet
• Supporting Enhancements to the MEF Certification
  Program

37
Migration Circuit Emulation Services (CES)

• CES is a major step in industrys progression
  toward entirely converged networks
• Transports TDM services over Carrier Ethernet
  services
• Converged networks for data, video and voice have
  been a dream of the industry
• Technical challenges to combine TDM and data are
  not trivial
• MEF 8 was designed to meet these challenges, MEF
  18 to certify conformance

8,18

• Transition Path
• Legacy voice traffic is transported via TDM and
  CES over Carrier Ethernet (CESoETH)
• Data growth is handled by Carrier Ethernet
• Traffic is merged over time

38
MEF 18 Certification

• MEF 18 provides standard testing of Circuit
  Emulation Services over Ethernet
• 334 ground breaking tests and certification in
  the suite
• Industry first impairment testing brings first
  test of emulation of clock recovery
• MEF certification speeds implementation and
  enables full inter-operability
• MEF 18 has many applications but is keyto Mobile
  Backhaul migration strategies

39
Closing

• Carrier Ethernet is in demand for Mobile Backhaul
• There are Ethernet deployment options for all
  mobile backhaul situations
• Carrier Ethernet technology is rising to meet the
  stringent technical and operational requirements
  of Mobile Backhaul
• The MEF is working in conjunction with other
  standards organizations to ensure that scalable
  solutions are available

40
Panelists
Ran Avital MEF Market Research Co-Chair VP of
Strategic and Product Marketing Ceragon
Networks rana_at_ceragon.com 972-52-5847526
Name Title Company Name E-mail Phone [phone]
4981
Dirk Lindemeier Mobile Backhaul Solutions
Development Nokia Siemens Networks dirk.lindemeier
_at_nsn.com 49 151 5515 3351
Jonathan Olsson MEF Mobile Backhaul IA
Editor Standardization Coordinator,
Ericsson jonathan.olsson_at_ericsson.com 46 8 404
3720
Brian Bortz, CEO, Resolute Networks brianb_at_Resolu
teNetworks.com 972-52-2210548
40
41
Accelerating Worldwide Adoption of Carrier-class
Ethernet Networks and Services
For in-depth presentations of Carrier Ethernet
for business, Ethernet services, technical
overview, certification program etc., visit
www.metroethernetforum.org/presentations
For more information regarding joining the
MEF Visit www.metroethernetforum.org Email us
at manager_at_metroethernetforum.org Call us
at 1 310 258 8032 (California, USA)