MEF 22 Mobile Backhaul Implementation Agreement

1
MEF 22 Mobile Backhaul Implementation Agreement
Jonathan Olsson Product Line RAN
Transmission jonathan.olsson_at_ericsson.com
2
Agenda

• Drivers of change
• MEF 22 Overview
• Application Scenario
• MEF 22 Phase 2

3
Drivers of change
Source Heavy Reading, 2008
Source Analysys Mason, 2009
Source GSA, 2009
Source Heavy Reading, 2008
4
MEF 22 Overview
5
Why Metro Ethernet Forum (MEF)?
6
MEF 22 - Mobile Backhaul Implementation Agreement

• Explains how to apply existing MEF specifications
• Provides generic specification for Ethernet
  backhaul architectures for mobile networks (2G,
  3G, 4G)
• User-Network Interface requirements
• Service Requirements
• Common Terminology
• Offers a standardized toolset

7
Site concept
RAN BS
UNI
UNI
RAN BS
Carrier Ethernet Network
UNI
8
Use Cases Packet offload
Packet offload over Carrier Ethernet Use Case 1a
Legacy Network
Carrier Ethernet Network
Non-Ethernet I/F
UNI
Non-Ethernet I/F
UNI
GIWF
RAN BS
RAN NC
GIWF
RAN dual stack Use Case 2a
9
Use Cases Full Ethernet
Emulation over Carrier Ethernet Use Case 1b
Full Ethernet Use Case 2b
10
Application Scenario
11
Application Scenario - Description

• Mobile Operator A has operates 2G and 3G mobile
  networks that utilizes TDM leased lines
• 3G base stations have both TDM-based and Ethernet
  interfaces and support IP
• Both systems are FDD (frequency sync)
• Mixed configuration sites

BSC
RNC
TDM Leased Line (2Mbps)
Legacy Network
3G
2G 3G
2G 3G
2G
2G 3G
12
Problem

• Mobile broadband traffic generates more volume
  than can be supported cost-efficiently by legacy
  network
• Decision Mobile Operator A wants all 2G and 3G
  transport to utilize Carrier Ethernet services

• How to transport 2G with non-Ethernet interfaces?
• How to define services?
• How to deliver sync?
• How to monitor services?

13
UNI for TDM-based base stations
Non-Ethernet I/F
Non-Ethernet I/F
GIWF
RAN BS
GIWF
RAN NC
EFT
EFT
Carrier Ethernet Network
EVC
UNI-N
UNI-C
UNI-C
UNI-N
Eth Access Link
Eth Access Link
Ethernet I/F
Ethernet I/F
14
Create a UNI at each site

• GIWF provides 2G with Ethernet interface
• Single UNI towards the CEN

RNC
BSC
RAN NC
GIWF
Carrier Ethernet Network
UNI
RAN BS
3G
2G 3G (GIWF)
2G 3G (GIWF)
2G (GIWF)
2G 3G (GIWF)
15
Services for emulated circuits

• Assumption Emulation solution requires the
  following performance requirements
• FD 20ms, FDV 5ms, FLR10-4,
  Availability99.99
• CIR 2.5Mbps, EIR 0Mbps (per emulated leased
  line)
• EVCs is defined with the same performance
  requirements
• Bandwidth allocated depends on the number of
  leased lines that are emulated, n. CIR n
  2.5Mbps

RNC
BSC
GIWF
Carrier Ethernet Network
EVPL_1
EVPL_2
EVPL_3
EVPL_4
UNI
3G
2G 3G (GIWF)
2G 3G (GIWF)
2G (GIWF)
2G 3G (GIWF)
16
Services for 3G

• Assumptions
• 3G solution requires 3 CoS
• 3G, BWP for each RAN BS CIR 6Mbps, EIR 4Mbps
• Ingress BWP for RAN NC UNI CIR 24Mbps, EIR
  12Mbps

RNC
BSC
GIWF
Carrier Ethernet Network
EVPL_1
EVPL_2
EVPL_3
EVPL_4
EVP-Tree
UNI
3G
2G 3G (GIWF)
2G 3G (GIWF)
2G (GIWF)
2G 3G (GIWF)
17
CoS configuration
18
CoS configuration
Example values!
19
Protection at RAN NC
RAN NC UNI
UNI-C
Link Aggregation Group
UNI-N
RNC
BSC
GIWF
Carrier Ethernet Network
EVPL_1
EVPL_2
EVPL_3
EVPL_4
EVP-Tree
UNI
3G
2G 3G (GIWF)
2G 3G (GIWF)
2G (GIWF)
2G 3G (GIWF)
20
MEF Approach to Synchronization

• Three principal Components of sync
• Frequency synchronization
• Phase synchronization
• Time of Day synchronization
• Packet based methods are in
• scope for Phase 1
• Other approaches
• Common Clock (GPS, legacy E1 clocking) is out of
  scope
• Synchronous Ethernet in scope for future phases

21
Delivering Synchronization

• Options sync over a separate EVC or sent over
  the services in a different CoS class
• Note Not all sites have an emulated service!

UNI
UNI
EVPL_1
EVPL_1 (CES)
CoS 1 (CES)
CoS 2 (Sync)
EVPL_Sync
22
Delivering frequency sync

• E-Tree service for packet based sync
• Redundancy with multiple sync server architecture

RNC
BSC
Sync Server
Sync Server
GIWF
EVPL_1
EVPL_2
EVPL_3
EVPL_4
EVP-Tree
Sync
UNI
3G
2G 3G (GIWF)
2G 3G (GIWF)
2G (GIWF)
2G 3G (GIWF)
23
Service OAM
RAN NC
RAN BS
Carrier Ethernet Network
Link MA
Link MA
Service Provider MA
Mobile Operator MA
MEP
MIP

• SOAM for Fault Management and Performance
  Monitoring
• Link level
• Edge-to-edge
• Measurements points needed in CEN

24
Application Scenario Summary

• Illustrated how to apply MEF 22 toolset
• Combined Use Case 1b and Use Case 2b
• Several other viable combinations

2G
3G
25
MEF 22 - Phase 2
26
LTE Reference Architecture

• Basic principles in MEF 22 still apply!
• Whats new with LTE?
• IP from the start
• New logical interfaces
• New pooling concept
• Greater throughput

27
MEF 22 - Phase 2 Scope

• Primary items
• New Mobile Technologies
• Performance recommendations
• Resiliency
• Sync
• Secondary items
• Detailed SOAM recommendations
• Multi-MEN
• Security

So far, on track!
28
Relationship between the MEF and BBF

• The MEF MBH IA describes a superset of potential
  implementations
• The Broadband Forum provides a specific network
  implementation reference based on MPLS
• MEF and Broadband Forum will continue to align
  future activities

Carrier Ethernet Network
MPLS Network
Ethernet
Ethernet
E-Line Service
RAN BS
RAN NC
Pseudo-wire Service
UNI
UNI
MPLS Service Termination
MPLS Service Termination
29
Summary

• RAN is going IP
• MEF 22 specifies a toolset for defining Carrier
  Ethernet services
• There are many solutions to the same problem
• Phase 2 will more detailed and include LTE
  requirements

30
Thank You
For more information, visit www.metroethernetfor
um.org
30