Professional Documents
Culture Documents
Introducing The Specifications of The MEF: MEF 22: Mobile Backhaul Implementation Agreement
Introducing The Specifications of The MEF: MEF 22: Mobile Backhaul Implementation Agreement
MEF
February 2009 1
Approved MEF Specifications
• MEF 2 Requirements and Framework for Ethernet Service Protection
• MEF 3 Circuit Emulation Service Definitions, Framework and Requirements in
Metro Ethernet Networks
• MEF 4 Metro Ethernet Network Architecture Framework Part 1: Generic Framework
• MEF 6.1 Metro Ethernet Services Definitions Phase 2
• MEF 7 EMS-NMS Information Model
• MEF 8 Implementation Agreement for the Emulation of PDH Circuits
over Metro Ethernet Networks
• MEF 9 Abstract Test Suite for Ethernet Services at the UNI
• MEF 10.1 Ethernet Services Attributes Phase 2*
• MEF 11 User Network Interface (UNI) Requirements and Framework
• MEF 12 Metro Ethernet Network Architecture Framework
Part 2: Ethernet Services Layer
• MEF 13 User Network Interface (UNI) Type 1 Implementation Agreement
• MEF 14 Abstract Test Suite for Traffic Management Phase 1
• MEF 15 Requirements for Management of Metro Ethernet
Phase 1 Network Elements
• MEF 16 Ethernet Local Management Interface
• MEF 17 Service OAM Framework and Requirements
• MEF 18 Abstract Test Suite for Circuit Emulation Services
• MEF 19 Abstract Test Suite for UNI Type 1
• MEF 20 User Network Interface (UNI) Type 2 Implementation Agreement
• MEF 21 Abstract Test Suite for UNI Type 2 Part 1: Link OAM
• MEF 22 Mobile Backhaul Implementation Agreement
* MEF 10 .1 replaces and enhances MEF 10 Ethernet Services Definition Phase 1 and replaced MEF 1 and MEF 5. MEF 6.1 replaced MEF 6.
2
This Overview Presentation
• Purpose:
– This presentation is an introduction to MEF 22
• Audience
– Equipment manufacturers building devices that will carry mobile
backhaul traffic over Carrier Ethernet
– Useful for mobile backhaul service providers architecting their
systems for Carrier Ethernet
– For wire-line service providers architecting their systems for the
inclusion of mobile backhaul traffic over Carrier Ethernet
• Other Documents
– Presentations of the other specifications and an overview of all
specifications is available on the MEF web site
– Other materials such as white papers and case studies are also
available
3
MEF 22 Overview Presentation Topics
• MEF 22 Overview
– Objectives
– Scope
– Implementation phases
– Terminology and concepts
• MBH IA Specification Sections
– Use cases and migration strategy
– Services
• Classes of service
• Service types
– Generic interworking function
– Synchronization and clock recovery
• Synchronization background information
• References and related documents
4
MEF 22 Overview Section
5
MEF Mobile Backhaul Implementation Agreement
• Overview
– 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
RAN BS
• Service definitions UNI
application support
Carrier Ethernet RAN NC
Network
UNI
RAN BS
6
About the Specification
7
Scope of the Implementation Agreement
8
Phased Implementation
MEF 22 Mobile Backhaul Implementation Agreement Phase 1 was
approved as an official MEF Specification in January 2009.
9
Terminology and Concepts (1)
• The Specifications and presentations refer to MENs (Metro
Ethernet Networks) not Carrier Ethernet Networks. Why is that?
– The technical work of the MEF as described in the specifications, together
with the work of associated standards bodies, collectively enable the
functionality and attributes of Carrier Ethernet
– The completed specifications continue to refer to MENs (Metro Ethernet
Networks) but this is now a generic term covering the enabled service
network in the increasing variety of Access, Metro and long haul networks
11
Terminology and Concepts (3)
• Network Elements addressed by the Specification
Terminology used in the specification and this overview
• The RAN CE is a generic term that identifies a mobile network node or site,
such as a RAN network Controller or RAN Base Station
• A RAN NC may be a single network controller or a site composed of several
network elements including: OSS, WCDMA Radio Network Controller or
Synchronization Server.
12
Terminology and Concepts (4)
13
Mobile Backhaul Implementation Agreement
Section Review
14
Section Review
15
Legacy Mobile Backhaul Migration
Packet offload over Carrier Ethernet – Use Case 1a
Legacy
Network
Carrier Ethernet
Network
Carrier Ethernet
Network
16
When RAN nodes are equipped with Ethernet
RAN dual stack – Use Case 2a
Legacy
Network
Carrier Ethernet
Network
Carrier Ethernet
Network
17
Migration legacy to Carrier Ethernet Backhaul (1)
Carrier Ethernet
Network
18
Migration legacy to Carrier Ethernet Backhaul (2)
Legacy
Network
Carrier Ethernet
Network
19
MBH Service Requirements Addressed
• Carrier Ethernet Services for Mobile Backhaul
– Typically there are 1-2 RNC sites and between hundreds to
thousands of RAN BS sites
– Bandwidth requirements for a base station site will vary and
may range from a few Mbps to over a Gbps
– Services need to be:
• Scalable
• Flexible
• Cost effective
– Generally, the requirement is to follow one of the following
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
20
Service Definitions – Point-to-Point (E-Line)
21
Service Definitions – Ethernet LAN Service (E-LAN)
22
Rooted Multipoint (E-Tree Service)
23
Traffic Separation
24
Technology Migration and
Interworking
25
Mobile Backhaul Generic Interworking Function (1)
26
Mobile Backhaul Generic Interworking Function (2)
RAN BS E-Line
Ethernet Ethernet
Service
UNI UNI
TDM Base Station
TDM Network
demarcation
Interface
28
Technology Interworking
29
Mobile Backhaul Synchronization
30
Synchronization
• Key Issue
– Migration to all packet networks means loss of TDM clock source
31
MEF Approach to Synchronization
• Packet based
– 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/implementations like
adaptive clocking, RTP-extended adaptive clocking, IEEE1588
etc.
– Eliminates the cost and need for retention of T1/E1 circuit solely for
synchronization
• Other approaches
– Common Clock (GPS, legacy E1 clocking) is out of scope
– Synchronous Ethernet in scope for future phases
32
Mobile Backhaul Synchronization
Background
Background
The following 8 slides are intended to assist the readers
understanding of the topic and background concepts behind the
implementation agreement
33
Mobile Backhaul Synchronization Background (1)
• Background Information
– The following slides are not descriptive of MEF 22 but are intended as
useful background knowledge
• Relevant ITU Standards for Clock Requirements for Circuit
Emulation services
– The synchronization requirements are derived from the ITU-T
Recommendation G.8261, which studies timing and synchronization
over packet based networks and examines the requirements for
different mobile technologies.
– Subsequent versions of this ITU specify clocks conforming to G.823
(for signals related to the E1-hierarchy) or G.824 (for T1-hierarchy
signals)
– These standards define the permissible output jitter and wander for
two levels
• Clock (Jitter and wander) requirements for the traffic interface are
defined in ITU-T G.823, Section 5 for E1 and in ITU-T G.824,
Section 5, for T1
• Clock (Jitter and wander) requirements for the synchronization
interface are defined in ITU-T G.823, Section 6.2.4 for E1 and in
ITU-T G.824, section 6.2.2 for T1
34
Mobile Backhaul Synchronization Background (2)
35
Mobile Backhaul Synchronization Background (3)
• Important synchronization types and requirements in
cellular networks (1)
– GSM Base Station (frequency synchronization)
• Timing requirement applicable to the GSM radio interface can
be found in the ETSI technical specification TS 145.010
• The radio interface requirement for a GSM base station is
frequency accuracy of ±50 ppb and ±100 ppb (pico BS)
– The need for this requirement stems primarily from the
need to support handover of mobiles between base stations
– UMTS FDD Base Station (frequency synchronization)
• The timing requirement applicable to the WCDMA FDD radio
interface can be found in the ETSI technical specification TS
125.104
• The radio interface requirement for UMTS FDD base stations is
a frequency accuracy of ± 50ppb (wide area), ±100 ppb (local
area) and ±250 ppb (Home BS); for the FDD mode there are no
phase alignment requirements
36
Mobile Backhaul Synchronization Background (4)
• Important synchronization types and requirements in cellular
networks (2)
– UMTS TDD Base Station (frequency and phase synchronization)
• The timing requirement applicable to the WCDMA TDD radio interface can
be found in the ETSI technical specification TS 125.105
• The radio interface requirement for UMTS TDD base stations is a
frequency accuracy of ±50 ppb; for the TDD mode there is the additional
requirement for the phase alignment of neighboring base stations to within
2.5 µs.
– 3GPP2 CDMA2000 Base Station (frequency and time synchronization)
• The relevant CDMA2000 standards are the 3GPP2 C.S0010-B and 3GPP2
C S0002-B
• According to the CDMA2000 specifications the average frequency
difference between the actual CDMA transmit carrier frequency and
specified CDMA transmit frequency assignment shall be less than ±50 ppb
• The time error should be less than 3μs: due to that it is a common practice
to equip CDMA base stations with GPS receivers
37
Mobile Backhaul Synchronization Background (5)
• How network synchronization is achieved for emulated circuits
over a packet-based infrastructure (1)
– There are 3 major methods:
1. Network Synchronous Method.
• This is supported via a local GPS or via a master –slave
synchronization network using the physical layer to distribute the
synchronization
2. Differential clocking mode
• A PRC-traceable reference is required at both ends of the packet
network. However often a this may not be available for service
providers at every possible site, such as a remote cell site
• The system will use the PRC-traceable clock source, which is fed
into all the elements of the network
• The system will use the common clock source as well as observe
the time stamps received from the circuit emulation service
(CESoE / SAToP / CESoPSN) packets received from the packet
network and calculate the differential to recover an accurate clock
• This recovered clock reference is then used to transmit the TDM
frames
38
Mobile Backhaul Synchronization Background (6)
39
Mobile Backhaul Synchronization Background (7)
• The requirements from Clock Recovery over PSN based MBH
– Any clock recovery over packet mechanism should be designed
primarily to meet the clock synchronization requirements for GSM
and UMTS RANs as specified in ETSI EN 300 912 and TS 125 402
"Synchronization in UTRAN stage 2”
– Jitter and wander measured at the output of the GIWF TDM-bound interface
should meet the traffic interface requirements specified in ITU-T
recommendations (G.823/G.824/G.825)
– The wander budget allocated to the MEN and the GIWF as measured at the
output of the GIWF TDM-bound interface should meet the traffic interface
requirements of ITU-T G.8261, Deployment Case 2
– Frequency accuracy in holdover should conform to a standard Clock as
applicable
– A robust clock recovery mechanism should also maintain its
outstanding performance even under the most demanding network
conditions, such as high Packet Delay Variation (jitter) and packet
loss ratio
40
Mobile Backhaul Synchronization Background (8)
41
MEF 22 Related Documents
42
MEF 22 Reference Works
• Other MEF documents on which parts of the Mobile Backhaul
Implementation Agreement are based
– The services and requirements that appear at the Mobile Backhaul
Implementation Agreement doc are based on:
• The services defined in MEF 6.1 Ethernet Service Definition –
Phase 2
• The attributes defined in MEF 10.1 Ethernet Service Attributes –
Phase 2
• MEF 13 & MEF 20 (UNI Types 1 & 2)
• Other documents currently under development by the MEF
Technical Committee (Ethernet Classes of Service, Service-OAM
and External Network-to-Network Interface technical
specifications)
– It is highly recommended to be familiar with the requirements in the
above two documents before reading the Mobile Backhaul
Implementation Agreement document. These are available on the
MEF Public web site Information Center
43
Final Word
• Next Actions
– Read the detailed MEF 20 Implementation
Agreement available on the MEF web site
– Further information related to implementation is to be
found on the MEF site:
• Further Technical FAQs beyond the scope of this
document
• A full reference presentation with additional
market perspectives
• White papers, case studies, applications
• Video presentations
44
End of MEF 22 Overview
More information:
www.metroethernetforum.org
45