Carrier Ethernet for Mobile Backhaul

1

Mobile Backhaul WebinarMEF 22 Briefing for Operators

2

Jonathan OlssonEricsson, LTE Product ManagerMEF Technical editor of the MEF 22 mobile backhaul standard.

Rami YaronAxerra Networks, VP of Technology &

Business Development, AmericasMEF Ambassador to the Americas

Karim TraoreSymmetricomSenior Architect Clock Synchronization Expert

Carsten RossenhoevelEuropean Advanced Networking Test Center, Managing DirectorCo-Chair MEF Mobile Backhaul Group

Speakers

Peter CroyAviat NetworksSenior Network ArchitectCo-Chair MEF Mobile Backhaul Group

3

• MEF Introduction

• Mobile Backhaul – The Market View

• MEF specifications for Mobile Backhaul

• Use Case: Legacy Network Migration

• Phase 2: Preparing for LTE and Beyond

WebinarHost


Today’s Webinar Agenda

4

MEF – Defining Body of Carrier Ethernet

Certification ProgramsEnabling Standardization

MEF Marketing CommitteeMarketing Carrier Ethernet

MEF Technical CommitteeSpecifications and Liaison

Mission: Accelerate the worldwide adoption of Carrier Ethernet networks and services

Membership: 170 Companies 68 Service Providers, Global Representation

5

Significant Market Developments

• Phenomenal growth in subscribers using mobile broadband services

• Mobile standards now deliver multi-megabit data rates to smart phones

• Packet Switched Networks promise scalable bandwidth at lower costs

• RAN must support multiple wireless generations

6

Source: Infonetics Research, 2010

0

10

20

30

40

50

60

CY05 CY06 CY07 CY08 CY09 CY10 CY11 CY12 CY13

Avg

BW

per

In

stal

led

Co

nn

ecti

on

(M

bp

s)

New Ethernet wireline PDH and ATM over PDH SONET/SDH and WDM

WW average bandwidth per installed connection (Mbps)

Mobile Backhaul Market Drivers

0

10

20

30

40TB

Oct-06 Jan-07 Apr-07 Jul-07 Oct-07 Jan-08 Apr-08 Jul-08 Oct-08 Jan-09 Apr-09 Jul-09

JRA 09.09.2009

0

10

20

30

40TB

Oct-06 Jan-07 Apr-07 Jul-07 Oct-07 Jan-08 Apr-08 Jul-08 Oct-08 Jan-09 Apr-09 Jul-09

JRA 09.09.2009

Live network KPI data

Operators: 9 Europe, 4 APAC, 6 Americas

Average Y-Y growth over 500%

Total HSDPA Traffic per Day

Source: Nokia Siemens Networks

Operators rolling out increased capacities via EDGE, EV-DO,

HSPA, WiMAX, then LTE

Bandwidth Per Connection

Copyright © 2009 Infonetics Research, Inc.

7

Costs Drive Operators to IP/Ethernet Backhaul

• Ethernet offers huge drop in cost per bit of bandwidth – Almost matches

the 2x to 10x traffic increases HSPA delivers

• IP/Ethernet naturally fit WiMAX and LTE as well

Source: Mobile Backhaul Equipment, Installed Base, and Services, October 2009

Bac

khau

l Ser

vice

Ch

arg

es p

er C

on

nec

tio

n


8

Operators Moving to IP/Ethernet backhaul

• From Infonetics Global service provider survey

• LTE is the final, absolute time to move to IP/Ethernet backhaul


9


MEF 22Mobile Backhaul Implementation

Agreement Phase I

10

Specifications For Mobile backhaul

MEF 6.1 = MEF 6, MEF 10.1 = MEF 10, MEF 1 = MEF 5. MEF 7.1 = MEF 7, MEF 10.2 = MEF 10.1.1 = MEF 10.1

April 2010

TS Technical SpecificationIA Implementation Agreement

Service Area Architecture Area Management Area Test and Measurement Area

MEF 6.1 Ethernet Services Definitions Phase 2 (TS)

MEF 2 Protection Framework and Requirements (TS)

MEF 7 EMS - NMS Information Model (TS) MEF 9 Abstract Test Suite for Ethernet Services at the UNI (TS)

MEF 3 Circuit Emulation Service Requirements (TS)

MEF 4 Carrier Ethernet Network Architecture Framework Part 1: Generic Framework (TS)

MEF 15 Requirements for Management of Carrier Ethernet Phase 1 – Network Elements (TS)

MEF 14 Abstract Test Suite for Traffic Management Phase 1 (TS)

MEF 8 Emulation of PDH over MENs (IA) MEF 11 UNI Framework and Requirements (TS)

MEF 16 Ethernet Local Management Interface E-LMI (TS)

MEF 18 Abstract Test Suite for CES over Ethernet (TS)

MEF 10.1 Ethernet Services Attributes Phase 2 (TS)

MEF 12 Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer (TS)

MEF 17 Service OAM Requirements and Framework (TS)

MEF 19 Abstract Test Suite for UNI Type 1 (TS)

MEF 22 Mobile Backhaul (IA) MEF 13 User Network Interface Type 1 (IA) MEF 7.1 EMS-NMS Information Model (TS) Phase 2

MEF 21 UNI Type 2 Test Suite (TS) Part 1 link OAM

MEF 23 Carrier Ethernet Class of Service (IA)

MEF 20 UNI Type 2 (IA) Service OAM Performance Management (IA)

MEF 24 UNI Type 2 Test Suite (TS) Part 2 E-LMI

MEF 10.1.1 Amendment:Attribute Enhancements

MEF 26 External NNI (ENNI) Phase 1 (TS) Service OAM Fault Management IA Phase 1

MEF 25 UNI Type 2 Test Suite (TS) Part 3 Service OAM

MEF 10.2 Ethernet Services Document Alignment

Ethernet Service Constructs (TS) Delivered Throughput (IA) Abstract Test Suite for ENNI (TS): Part 1 Basic ATS

Ethernet Services Amendment: New Bandwidth Profile

MEF 12 Network Architecture Framework Update

Service OAM MIB Abstract Test Suite for ENNI (TS): Part 3 Protection ATS

Mobile Backhaul (IA) Phase 2 ENNI Amendment: Support for UNI Tunnel Access and V-UNI

Abstract Test Suite for UNI Type 2 – Part 5, Enhanced UNI Attributes, and Part 6, L2CP Handling

Carrier Ethernet Class of Service (IA) Phase 2

Ethernet Services Layer Architecture Phase 2

OVC Service description NID Specification (TS)

OVC Service level Specification Protection across External Interfaces

Availability

11

MEF 22: Standardization Process

TDM to IP/Eth

Industry trends

Other SDOs

MEFs own work as the foundation

Standardizedreference

points

ServiceRequirements

(Service Types,CoS, Eth OAM, etc)

SynchronizationRecommendations

12

MEF 22: Overview

• MEF22 Explains how to apply existing MEF specifications to Mobile Backhaul

• Provides generic specification for Ethernet backhaul

• Includes guidelines to architecture, equipment & operation of the RAN

• Offers a standardized toolset

13

MEF Terminology and Concepts

• Network Elements as defined in MEF 22 Specification

Service requirements:• Connectivity - From a few to thousands of sites• Assurance - Capacity, quality and availability• Operations - Provisioning, SLA monitoring, fault-finding

GIWF Generic Inter-working Function

PCP Priority Code Point

PEC Packet based Equipment Clocks

PTP Precision Time Protocol

RAN Radio Access Network

RAN BS RAN Base Station

RAN CE RAN Customer Edge –Mobile network node/site

RAN NC RAN Network Controller –Single or multiple network elements

RNC Radio Network Controller

Terminology used in the specification and this overview

14

Service Requirements Addressed

• Bandwidth– Base station BW varies from site to site– Mbps to more than Gbps– Support hundreds to thousands of RAN BS sites per

RNC site

• MEF Services – Ethernet Private Line Service– Ethernet Virtual Private Line Service– Ethernet Private LAN Service– Ethernet Virtual Private LAN service– Ethernet Private Tree Service– Ethernet Virtual Private Tree Service

15

Legacy RAN Mobile Backhaul Migration

Emulation over Carrier Ethernet – Use Case 1b

Packet offload over Carrier Ethernet – Use Case 1a

16

Ethernet RAN Mobile Backhaul Migration

RAN dual stack – Use Case 2a

Full Ethernet – Use Case 2b

17

Karim TraoreSymmetricomSenior Architect Clock Synchronization Expert

Rami YaronAxerra Networks, VP of Technology &

Business Development, AmericasMEF Ambassador to the Americas

Legacy RAN Mobile Backhaul MigrationUse Case

18

Use Case Background

Challenges:– 2G transport– Service definition – Timing delivery– Service monitoring

Description:• 2G and 3G mobile FDD networks over TDM leased lines • 3G base stations support both TDM & Ethernet interfaces

Problem:• Capacity increase not cost-efficiently sustainable on legacy network

Solution:• 2G and 3G networks should transport Carrier Ethernet services

TDM Leased Line (1.5Mbps)

19

UNI for TDM-based Base Stations

• Generic Interworking Function (GIWF)– Adaptation and interconnection between legacy mobile equipment

at the BS/NC and the Carrier Ethernet network at the UNI– Enables backhaul of any combination of 2G/3G legacy and

Evolved-3G & 4G voice and data traffic over a single Carrier Ethernet RAN

– Implementation based on TDM circuit emulation standards as well as ATM/HDLC pseudo-wire standards

Carrier Ethernet Network

UNI-NUNI-C

Eth Access Link

EFT

GIWFRAN BS

Non-EthernetI/F

UNI-CUNI-N

Eth Access Link

EFT

GIWF RAN NC

Non-EthernetI/F

Ethernet I/F Ethernet I/F

EVC

20

2G(GIWF)

2G + 3G(GIWF)

2G + 3G(GIWF)

3G2G + 3G(GIWF)

Services for Emulated Circuits

EVPL_1

EVPL_2

EVPL_3

EVPL_4

UNI

Carrier EthernetNetwork

BSC

• The GIWF Provides support for legacy circuits over Ethernet• Assumption: Emulation solution requires the following:

– FD = 20ms, FDV = 4ms, FLR=10-5, Availability=99.999%– CIR = 2Mbps, 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 * 2Mbps

GIWF

RNC

21

Services for 3G

EVPL_1

EVPL_2

EVPL_3

EVPL_4

UNI

Carrier EthernetNetwork

• 3G service utilizes the Node B Ethernet interface• 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

• E-LINE/E-LAN may be used as well

EVP-Tree

2G(GIWF)

2G + 3G(GIWF)

2G + 3G(GIWF)

3G

BSC RNC

2G + 3G(GIWF)

GIWF

22

CoS Configuration

Service Class Name

Example of Generic Traffic Classes mapping into CoS

4 CoS Model 3 CoS Model 2 CoS Model

Very High (H+) Synchronization - -

High (H) Conversational,Signaling and Control

Conversational and Synchronization,

Signaling and Control

Conversational and Synchronization,Signaling and Control,

Streaming

Medium (M) Streaming Streaming -

Low (L) Interactive and Background

Interactive and Background

Interactive and Background

Very High (H+) High (H) Medium (M) Low (L)

-

FD = 20msFDV=4msFLR=10-5

Availability=99.999%

FD=50msFDV=10msFLR=10-4

Availability=99.99%

FD=100msFDV=10msFLR=10-4

Availability=99.99%

Examples:

23

MEF 22 Approach to Synchronization

• MEF22 Approach to Synchronization– Packet based methods

(in scope Phase 1)• Synchronization

quality requirements

• The IA is agnostic to specific methods /implementations

– Synchronous Ethernet (in scope phase 2)

– Non Ethernet sync (outside IA scope)

Mobile Network Architecture

Frequency Sync

Time/Phase Sync

CDMA2000 GSM UMTS-FDD LTE-FDD UMTS-TDD LTE-FDD with MBMS-Single Freq. Network

LTE-TDD Mobile WiMAX TD-SCDMA

24

Delivering Packet Synchronization

• In-band: Within the mobile data stream– Use packet rate based adaptive clock recovery (ACR) – no additional

bandwidth is needed, must have constant packet rate (MEF8)

– Use CES RTP optional header for synchronization timestamps

• Out of band: Separate from the mobile data stream– For packet based synchronization methods like IEEE1588 and NTPv4

– Map synchronization information to separate EVPL or

– Map synchronization information to a different Class of Service (CoS)

Note: Not all sites use circuit emulation services

UNI

EVPLEVPLCoS Data

CoS Sync

UNI

EVPL_Sync

EVPL DataEVPL Data

UNI

EVPL Data & Sync

EVPL Data & Sync

Sync in separate EVPL Sync uses different Class of ServiceSync within the data EVPL

25

OAM in MBH Migration

• Ethernet OAM– Provides Ethernet

management

• Features– Connectivity Fault

Management

– Performance Management

– Link Management

• Deployment– Ethernet starts from Base

Station

– or legacy traffic “converged”

2G

T1/E1

T1/E1(TDM + ATM)

Ethernet

3G

LTE

EthernetCarrier

Ethernet

N x GigE

Ethernet

ATM

Ch-OC3 or T1/E1

BSC (2G)

RNC (3G)

NC (4G)

Cell Site MSC

Wireless Provider and Backhaul Operator each have visibility of their own Ethernet performance and fault data

Service ProviderRAN BS UNI RAN NC UNI

Wireless Provider Maintenance Entity

Operator Maintenance Entity

26

Jonathan OlssonEricsson, LTE Product ManagerMEF Technical editor of the MEF 22 mobile backhaul standard.

Preparing Ethernet Services for LTEMEF 22 - Phase 2

ApprovedSpecification

ApprovedDraft

LetterBallot

Working Document

StrawBallots

NewProject

27

Current Focus Areas

• LTE– Understand LTE and requirements for Ethernet services

• Synchronization– Frequency synchronization requirements and timing methods

• Resiliency– Discuss how resiliency applies to MBH Ethernet services

• Performance monitoring– What needs to be monitored, establish reference model

• Service performance– Common MBH Ethernet service performance recommendations

28

LTE Reference Architecture

• Basic principles in MEF 22 still apply!

• What’s new with LTE?– IP from the start– New logical interfaces– Multipoint in nature– New pooling concept– Greater throughput

29

Synchronization

• Focus – Achieving frequency

synchronization

• Synchronous Ethernet– Output requirements– New UNI attribute

• Packet based methods– align with ITU-T

recommendations

Synchronous Ethernet

Packet base methods

30

Resiliency

• Examining how resiliency requirements could be reflected.– At the UNI– For the EVC

• Looking at when it makes sense to use resiliency

RAN BS

RAN NC

UNIUNI

EVC 1(Primary Path)

EVC 2(Backup Path)

Leased component of the overall backhaul solution

31

Performance Recommendations and Monitoring

• Clearly specify between which points EVC performance objectives apply

• Provide a reference model illustrating where monitoring shall take place and what to monitor

EVC performance objectives

32

MEF 22 Scope Comparison

ITEM PHASE 1 PHASE 2UNI Service Types Link OAM Service OAM FM Service OAM PM CoS Performance recommendations Packet based sync SyncE Resiliency GSM, WCDMA, CDMA2000, WiMAX 802.16e

LTE

33

Summary

• RAN is going IP

• MEF 22 specifies a toolset for defining Carrier Ethernet services

• Carrier Ethernet provides solutions for wireless providers and backhaul operators

• MEF22 Phase 2 underway, preparing Ethernet services for LTE

WebinarHost


34

Thank YouFor details on Carrier Ethernet for Mobile Backhaul visit: http://www.metroethernetforum.org/mobile-backhaul



[email protected] [email protected]

Mobile Backhaul Working Group Chairs