Your SlideShare is downloading. ×
MEF 22 Ethernet Based Mobile Backhaul
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

MEF 22 Ethernet Based Mobile Backhaul

1,631
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,631
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
61
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • MEF Introduction Carrier Ethernet for Mobile Backhaul MEF Specifications and Mobile Backhaul MEF 22 – Mobile Backhaul Implementation Agreement Legacy Mobile Backhaul Migration – Case Study Preparing Ethernet Services for LTE – MEF 22 Phase 2
  • The Mobile Backhaul is defined as the network between the: Radio Network Controllers (RNCs), and Radio Access Networks Base Station (RAN BS). MEF22 provides guidelines to architecture, equipment & operation to that part of the network MEF22 Explains how to apply existing MEF specifications to Mobile Backhaul Provides generic specification for Ethernet backhaul architectures for mobile networks (2G, 3G, 4G) User-Network Interface requirements Service Requirements Clock synchronization Common Terminology Offers a standardized toolset
  • 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.
  • The GIWF provides adaptation and interconnection between any legacy mobile equipments (TDM/ATM/HDLC based) at the BS/NC and the Carrier Ethernet network at the UNI. It enables the joint backhaul of any combination of 2G, 2.5G, 3G (legacy based) and Evolved-3G & 4G (Ethernet based) voice and data traffic over a single Carrier Ethernet RAN. The GIWF implementation could be based on TDM circuit emulation standards as well as ATM/HDLC pseudo-wire standards.
  • Guidelines for the number of CoS classes to use Bundling traffic types into limited number of CoS classes CoS class performance requirements
  • Ethernet OAM Provides Ethernet with management features similar to legacy services Features Connectivity Fault Management Performance Management Link Management Deployment Ethernet can start at the Base Station or the legacy traffic can be “converged” onto a Carrier Ethernet Network The following slide provides a picture of where Ethernet OAM is performed from the Wireless Providers perspective and from the Backhaul Operators perspective
  • LTE Understand LTE and what requirements it puts on Ethernet services Synchronization Take a deep dive into frequency synchronization requirements and available timing methods Resiliency Look at resiliency and how it applies to MBH Ethernet services Performance monitoring Examine what needs to be monitored and establishing a reference model applicable to MBH Service performance recommendations Proposing common MBH Ethernet service performance recommendations
  • Transcript

    • 1. MEF 22 Ethernet Based Mobile Backhaul Rami Yaron MEF Ambassador to the Americas
    • 2.
      • MEF Introduction
      • Mobile Backhaul – The Market View
      • MEF specifications for Mobile Backhaul
      • Multi Physical Transport
      • Use Case: Legacy Network Migration
      • Phase 2: Preparing for LTE and Beyond
      Today’s Webinar Agenda
    • 3. MEF 22 Mobile Backhaul Implementation Agreement - Phase I
    • 4. 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
    • 5. MEF 22: Standardization Process TDM to IP/Eth Industry trends Other SDOs MEFs own work as the foundation Standardized reference points Service Requirements (Service Types, CoS, Eth OAM, etc) Synchronization Recommendations
    • 6. 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
      Terminology used in the specification and this overview 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
    • 7. Legacy RAN Mobile Backhaul Migration Emulation over Carrier Ethernet – Use Case 1b Packet offload over Carrier Ethernet – Use Case 1a
    • 8. Ethernet RAN Mobile Backhaul Migration RAN dual stack – Use Case 2a Full Ethernet – Use Case 2b
    • 9. Legacy RAN Mobile Backhaul Migration Use Case
    • 10. Use Case Background
      • Mobile Operator operates 2G and 3G mobile networks that utilizes TDM leased lines
      • 3G base stations Supports both TDM and Ethernet interfaces
      • Both systems are FDD (frequency sync)
      • Mixed configuration sites
      Legacy Network TDM Leased Line (1.5 / 2 Mbps) 3G 2G 2G + 3G 2G + 3G 2G + 3G BSC RNC
    • 11. Migration Challenges
        • 2G transport
        • Service definition
        • Timing delivery
        • Service monitoring
      • Problem:
        • Capacity increase not cost-efficiently sustainable on legacy network
      • Solution:
        • 2G and 3G networks should transport Carrier Ethernet services
      • Challenges:
    • 12. 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-N UNI-C Eth Access Link EFT GIWF RAN BS Non-Ethernet I/F UNI-C UNI-N Eth Access Link EFT GIWF RAN NC Non-Ethernet I/F Ethernet I/F Ethernet I/F EVC
    • 13. Services for Emulated Circuits 2G (GIWF) 2G + 3G (GIWF) 2G + 3G (GIWF) 3G 2G + 3G (GIWF) EVPL_1 EVPL_2 EVPL_3 EVPL_4 UNI Carrier Ethernet Network 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
    • 14. Services for 3G EVPL_1 EVPL_2 EVPL_3 EVPL_4 UNI Carrier Ethernet Network
      • 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
    • 15. CoS Configuration Examples: 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 = 20ms FDV=4ms FLR=10 -5 Availability=99.999% FD=50ms FDV=10ms FLR=10 -4 Availability=99.99% FD=100ms FDV=10ms FLR=10 -4 Availability=99.99%
    • 16. MEF22 Approach to Synchronization
        • Packet based methods (in scope Phase 1)
          • Synchronization quality requirements reference the ITU G.8261 standard
          • Agnostic to specific methods/implementations like Adaptive Clock Recovery (ACR), Extended ACR (RTP Header), IEEE1588v2, NTPv4, etc.
        • Synchronous Ethernet (in scope phase 2)
        • Non Ethernet sync (outside IA scope)
      F 1 + f 2 F 1 T 1 T 2 +/- 50ppb +/- 50ppb Time Mobile cannot lock to BTS 2 and call is dropped BTS 2 drifts outside 50ppb window BTS 2 BTS 1
    • 17. 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 EVPL CoS Data CoS Sync UNI EVPL_Sync EVPL Data UNI EVPL Data & Sync Sync in separate EVPL Sync uses different Class of Service Sync within the data EVPL
    • 18. 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” onto a Carrier Ethernet Network
        • Wireless Provider and Backhaul Operator each have visibility of their own Ethernet performance and fault data
      2G T1/E1 T1/E1 (TDM + ATM) Ethernet 3G LTE Ethernet Carrier Ethernet N x GigE Ethernet ATM Ch-OC3 or T1/E1 BSC (2G) RNC (3G) NC (4G) Cell Site MSC Service Provider RAN BS UNI RAN NC UNI Wireless Provider Maintenance Entity Operator Maintenance Entity
    • 19. Preparing Ethernet Services for LTE MEF 22 - Phase 2 Approved Specification Approved Draft Letter Ballot Working Document Straw Ballots New Project
    • 20. 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
    • 21. MEF 22 Scope Comparison ITEM PHASE 1 PHASE 2 UNI   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 
    • 22. 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
    • 23. Thank You For details on Carrier Ethernet for Mobile Backhaul visit: http://www.metroethernetforum.org/mobile-backhaul Rami Yaron [email_address] +1 203 554-1522