Mobile Backhaul Implementation Agreement Enabling Carrier Ethernet for Mobile Backhaul Networks

1
Mobile Backhaul Implementation Agreement
Enabling Carrier Ethernet for Mobile Backhaul
Networks
2
Panelists
2
3
Session Topics

• Why Carrier Ethernet for Mobile Backhaul?
• MEF 22 Mobile Backhaul Implementation Agreement
• A New Opportunity for Wire-line Service Providers
  
• Carrier Ethernet Adoption Has Started
• MEFs MBH IA and the IP/MPLS Forums
  Specification
• MEF Elements
• Legacy Mobile Backhaul Migration
• Traffic separation
• Ethernet OAM
• Synchronization
• MEF Mobile Backhaul QA
• Migration Circuit Emulation Services
• MEF 18 Certification
• MEF Resources

4
Why Carrier Ethernet for Mobile Backhaul?

• Carrier Ethernet
• Economically meets fast growing bandwidth
  requirements currently constrained by 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
• Benefit from ubiquitous availability of broadband
  access
• 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

New Revenue opportunities for wire-line service
providers
5
MEF 22 Mobile Backhaul Implementation Agreement
Carrier Ethernet for Mobile Carriers

• Uniquely enables the deployment of profitable
  data driven mobile services
• Provides guidance for service providers to
  implement Carrier Ethernet for Mobile Backhaul
• Provides the language to communicate both
  benefits and technical implementation details to
  Mobile Operator customers
• Meets the current dynamic market conditions of
  disruptive technology (new mobile devices) and
  financial conditions
• Provides solutions for transition from legacy
  technologies
• Preserves key voice based service revenue

6
A New Opportunity for Wire-line Service Providers

• Opportunity
• The new agreement provides a new
  wholesaleopportunity to leverage existing
  wire-line backhaul infrastructure and capacity
• Driven by the migration of mobile technologies
  to Ethernet backhaul
• The MBH Implementation agreements helps
  wholesalers
• It states the requirements
• Includes specific Service Level Specifications
  that are required for transport of Mobile
  Backhaul across wire-line backhaul
• Other deliverables for wire-line wholesalers
• Back-up slides at the end of the deck contain
  further business case and Mobile Backhaul
  fundamentals for these wholesale opportunities

New Revenue opportunities for wire-line service
providers
7
Carrier Ethernet Adoption Has Started
Vodafone UK and BT in new managed access
agreement The five-year contract deploys BT's new
21st Century Network-enabled Ethernet service,
offering backhaul speeds of up to 60 Mbit/s. The
new next-generation, carrier class service
provides customers with flexible and scalable
bandwidth to meet increased demand, with costs
that match actual traffic and revenue increases.
This agreement allows Vodafone UK to avoid
capital investment risk, while benefiting from
the economies of scale and national reach BT
Wholesale offers.
April, 2008     
8
Relationship between the MEFs MBH IA and the
IP/MPLS forums specification

• The MEF MBH IA describes a superset of potential
  implementations that fulfill the service
  layer requirements (UNIs, EVCs) of mobile radio
  systems (RAN CE devices) with Ethernet
  interfaces.
• The MBH work of the IP/MPLS Forum provides a
  specific network implementation reference based
  on MPLS that fulfils the performance and
  connectivity requirements of mobile radio
  systems.

Carrier Ethernet Network
MPLS Network
Ethernet
Ethernet
E-Line Service
Base Station
Network Controller
Pseudo-wire Service
Ethernet UNI
Ethernet UNI
MPLS Service Termination
MPLS Service Termination
9
MEF Elements

• What is it?
• Provides generic specification for Ethernet
  backhaul architectures for mobile networks (2G,
  3G, 4G)
• Explains how to apply existing MEF specifications
• User-Network Interface requirements
• Service Requirements
• Service Definitions
• Clock synchronization

10
Legacy Mobile Backhaul Migration
Packet offload over Carrier Ethernet Use Case 1a
Emulation over Carrier Ethernet Use Case 1b
11
When RAN nodes are equipped with Ethernet
RAN dual stack Use Case 2a
Full Ethernet Use Case 2b
12
Traffic separation

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

13
Ethernet OAM

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

Mobile Operator MA
MEP
MIP
Available with MEF 20 UNI Type 2
14
Synchronization

• Migration to all packet networks means loss of
  TDM clock source
• Components of sync
• Frequency (2G, 3G, 3.5G)
• Phase (4G in some cases)
• Time of Day
• Packet based
• Out-of-band (GPS, legacy E1 clocking) is outside
  of scope
• Packet based methods are in scope for Phase 1
• Synchronization quality requirements reference
  the ITU G.8261 standard
• The IA is agnostic to specific methods/implementat
  ions like adaptive clocking, RTP-extended
  adaptive clocking, IEEE1588 etc.
• Synchronous Ethernet in scope for future phases
• Eliminates the cost and need for retention of
  T1/E1 circuit solely for synchronization

Carrier Ethernet for Mobile Carriers
15
Candidates for MBH IA Phase 2
16
MEF Mobile Backhaul QA

• How does the GIWF handles existing UMTS / WCDMA
  based networks?
• These Technologies uses ATM over a number of
  bundled T1 (1.5 Mbit/s) or E1 (2 Mbit/s) circuits
  to connect the base station with the network
  controller.
• The GIWF terminates an ATM pseudo-wire or a TDM
  circuit emulation tunnel at the cell site or
  service edge and at the network controller site
• A variety of ATM pseudo-wire and/or TDM circuit
  emulation standards can be used in the
  implementation agreement

Service Provider Network
Carrier Ethernet Network
ATM Pseudo-wire
CES IWF
CES IWF
Ethernet
Ethernet
ATM/TDM
ATM/TDM
Carrier Ethernet Network
RAN BS
RAN NC
E-Line Service
RAN BS
Ethernet UNI
Ethernet UNI
ATM / TDM Network Interface
ATM / TDM BS demarcation
17
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

MEF 8, MEF 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

18
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

19
MEF Resources

• Available on the MEF Web site today
• http//metroethernetforum.org/InformationCente
  r
• MEF 22 MBH IA specification
• MEF 22 Technical Overview (Powerpoint)
• Available 13th Feb 2009
• MEF White Paper
• MEF MBH QA
• Available Shortly
• Detailed Marketing Presentation
• MEF MHB Webinar (Feb 25th)
• MBH Case Studies and articles

20
For in-depth presentations of Carrier Ethernet
for business, Ethernet services, technical
overview, certification program etc., visit
www.metroethernetforum.org QA