View
823
Download
6
Category
Tags:
Preview:
Citation preview
1
MEF Carrier Ethernet Briefing
2
Ethernet Based Mobile Backhaul Tutorial & Panel Session
3
Speakers
Asif HazarikaIP Infusion Inc, Senior Director of Product ManagementMEF Marketing
Ward ZhanFiberhome Networks Co.Ltd.Product Line Manager
Logo
Xioqiang DengAlcatel-Lucent
Logo
Feiling JiaTellabsStaff Product ManagerMEF Marketing
Logo
4
• Mobile Backhaul – The Market View
• MEF specifications for Mobile Backhaul
• Use Case: Legacy Network Migration
• Phase 2: Preparing for LTE and Beyond
Today’s Webinar Agenda
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
Copyright © 2009 Infonetics Research, Inc.
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
Copyright © 2009 Infonetics Research, Inc.
9
MEF 22Mobile Backhaul Implementation
Agreement Phase I
Feiling JiaTellabsStaff Product Manager
Logo
10
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
11
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
12
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
13
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
14
Legacy RAN Mobile Backhaul Migration
Emulation over Carrier Ethernet – Use Case 1b
Packet offload over Carrier Ethernet – Use Case 1a
15
Ethernet RAN Mobile Backhaul Migration
RAN dual stack – Use Case 2a
Full Ethernet – Use Case 2b
16
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
17
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
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
24
Preparing Ethernet Services for LTEMEF 22 - Phase 2
ApprovedSpecification
ApprovedDraft
LetterBallot
Working Document
StrawBallots
NewProject
25
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!
26
MEF-22 Phase 2
• The services and requirements in this Implementation Agreement are based on the services defined in MEF 6.1 Ethernet Service Definitions – Phase 2 [2] and the attributes in MEF 10.2 Ethernet Service Attributes [3], and aims to be flexible to support a wide range of Ethernet and existing mobile network deployments.
27
LTE Reference Architecture
• Basic principles in MEF 22 still apply!
• What’s new with LTE?– IP from the start– New logical interfaces– New pooling concept– Greater throughput
28
Scope of MEF-22 Phase 2
• Utilize existing MEF technical specifications with required extensions to interface and service attributes.
• Provide requirements for UNI-C and UNI-N beyond those in [4] and [5].
• 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 requirements for Class of Service and performance recommendations, where possible.
• Define synchronization requirements where possible for transparent packet based synchronization methods and synchronous Ethernet.
• Functional requirements applicable to GIWF interfaces.
• Specify resiliency terminology and requirements for mobile backhaul.
• Include the mobile standards: GSM, WCDMA, CDMA2000, WiMAX 802.16e, and LTE.
29
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
30
Protection at RAN NC
EVPL_1
EVPL_2
EVPL_3
EVPL_4
UNI
Carrier EthernetNetwork
RNCBSC
EVP-Tree
2G + 3G(GIWF) 2G
(GIWF)2G + 3G(GIWF)
2G + 3G(GIWF)
3G
RAN NC UNIUNI-C
UNI-N
Link AggregationGroup
GIWF
31
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
32
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
33
When/Why do I need Clock Synchronization?
• Why?– Synchronization service for cells handover – Wireless interface rate efficiency
• When?– Currently the mobile backhaul is done via a synchronous TDM network,
from which the timing information is recovered
When the mobile backhaul network is upgraded to Ethernet, the base stations are isolated from the synchronization info that used to be carried over the TDM feeds
Source: MRV Communications
34
MEF 22 Approach to Synchronization
• MEF22 Approach to Synchronization– Packet based methods
(was in scope Phase 1)• Synchronization
quality requirements
• The IA is agnostic to specific methods /implementations
– Synchronous Ethernet (now in scope)
– Non Ethernet sync (not defined)
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
35
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
36
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
37
Synchronization Requirements
T1 / SONET
DISTRIBUTION FROM CENTRAL SOURCEINTEGRATED IN PHYSICAL INFRASTRUCTURE
NEW TECHNOLOGIESNEW PLACES IN NETWORK, ADD COMPLEXITY
UNIFIED MODEL REPLACED BY MORE FRAGMENTED MODEL
Network is one Sync Domain
Courtesy of Mike Gilson & BT
Access
Core
Metro
38
Mobile Wireless Requirements
Requirements (air interface)
Synchronization Frequency accuracy Phase (between NobeBs)
Time
CDMA2000 ±50 ppb (Macro cell) ± 10µs (± 3µs preferred)
GSM, UMTS-FDD ±50 ppb (Macro cell)
UMTS-TDD ±50 ppb (Macro cell) ± 2.5µs
LTE ±50 ppb (Macro cell) ± 5µs for MBMS
Mobile WiMAX/TDD
±50 ppb (Macro cell) ± 1µs
TD-SCDMA ±50 ppb (Macro cell) ± 3µs
39
1588v2 Precise Timing Protocol
• Packet based synchronization mechanism– UDP/IP layers messaging (multicast and unicast) over Ethernet
– NTP, Adaptive Clock Recovery
• Frequency, Phase and Time– TDM synch/SyncE are Layer 1 mechanisms that support frequency only
• Client/server model– Master clock, slave clock (ordinary clock)
– Intermediary nodes may or may not support IEEE1588 PTP (unlike SyncE)
– On-pass-support mechanisms• Boundary clock• Transparent clock
Accurate time-of-day distribution is required for precise SLA monitoring and TDD radio applications Accurate time-of-day distribution is required for precise SLA monitoring and TDD radio applications
40
Delivering frequency sync
EVPL_1
EVPL_2
EVPL_3
EVPL_4
UNI
RNCBSC
• E-Tree service for packet based sync
• Redundancy with multiple sync server architecture
EVP-Tree
Sync
SyncServer
SyncServer
2G + 3G(GIWF) 2G
(GIWF)2G + 3G(GIWF)
2G + 3G(GIWF)
3G
GIWF
41
PhysicalData LinkNetwork
Synchronous Ethernet
• Synchronous Ethernet (ITU-T G.8261)• Uses the PHY clock to distribute timing
– Generates the clock signal from “bit stream”– Similar to traditional SONET/SDH/PDH PLLs
• Each node in the packet network recovers the clock• Must be supported by all NEs in timing chain
Application Data
PhysicalData LinkNetwork
PLL
PLL
PhysicalData LinkNetwork
PLL
Data Clock
Application Data
PRC
Timing
Output
Timing
Input
Master Port Slave Port
42
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
43
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
44
Ward ZhanFiberhome Networks Co.Ltd.Product Line Manager
Logo
Feiling JiaTellabsStaff Product ManagerMEF Marketing
Logo
Panellists
Moderator
Asif HazarikaIP Infusion Inc, Senior Director of Product ManagementMEF Marketing
Xioqiang DengAlcatel-Lucent
45
Thank You
For details on Carrier Ethernet for Mobile Backhaul visit: http://www.metroethernetforum.org/mobile-backhaul
46
MEF Carrier Ethernet Briefing
Recommended