• Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
739
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
72
Comments
0
Likes
2

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
  • Draft: Speaker Line-up Carsten (webinar host): (10 minutes) Welcome & speaker intro MEF intro and Analyst view Peter: MEF 22 Phase 1 IA (10 min) Rami: Legacy Migration - Use case explained (10 minutes) Karim: Legacy Migration - CoS & Sync delivery (5 min) Jonathan: MEF 22 Phase 2 - Ethernet for LTE (10 min) Carsten: (1-2 min) Prepared Q&A discussion with all speakers Questions from participants (if time permits) Conclusion & open invite to contact MBH team
  • 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
  • Phenomenal growth in mobile subscribers during Y2009 Significant increase in packet-data services in mobile network The trend is heading 50Mbps capacity per cell site for Y2010 Packet Switched Network promises more bandwidth at lower costs Traditional wireline TDM expansion can’t meet traffic growth and expenses Leased-line OPEX (globally) for mobile operators estimated at $22B Standardization process 3GPP ( 3rd Generation Partnership Project) ITU-T / ITU-R (Telecommunications / Radio) IEEE 802.16 / WiMAX forum Carrier Ethernet MEF 22 (MBH IA) MPLS & Broadband forum (Framework & requirements) IOMETRIX – MEF and CES services certification EANTC – Mobile backhaul interoperability events
  • 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.
  • Bandwidth Requirements Base station BW requirements vary from site to site Range from few Mbps to more than Gbps Support hundreds to thousands of RAN BS sites per RNC site MEF Services 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
  • 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 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 non-Ethernet interfaces? How to define services? How to deliver synchronization? How to monitor services?
  • 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
  • This is background with regard to phase I Packet Based Synchronization Challenges: No end-to-end physical layer clock synchronization Packet delay variation – caused by queuing delays, routing changes, network technology Packet loss Symmetric/asymmetric network MEF22 Approach to Synchronization Packet based methods are in scope for Phase 1 Synchronization quality requirements reference the ITU G.8261standard The IA is agnostic to specific methods/implementations like Adaptive Clock Recovery (ACR), Extended ACR (RTP Header), IEEE1588v2, NTPv4, etc. Synchronous Ethernet - in scope for phase 2 Non Ethernet sync (GPS, legacy E1 clocking) is outside of the IA scope
  • Focus is on achieving frequency synchronization Synchronous Ethernet Output requirements specified based on ITU-T recommendations New UNI attribute to specify availability of SyncE Packet based methods Continue to align with ITU-T recommendations
  • Boundary clock It acts as a slave clock at port that connects to the grandmaster, and as a master to all other ports it isolates the “down stream” clocks from any delays and jitter within the switch/routers Transparent clock It performs as a normal switch/router but measures residence time of PTP events

Transcript

  • 1. MEF Carrier Ethernet Briefing
  • 2. Ethernet Based Mobile Backhaul Tutorial & Panel Session
  • 3. Speakers Asif Hazarika IP Infusion Inc, Senior Director of Product Management MEF Marketing Ward Zhan Fiberhome Networks Co.Ltd. Product Line Manager Logo Xioqiang Deng Alcatel-Lucent Logo Feiling Jia Tellabs Staff Product Manager MEF 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. Mobile Backhaul Market Drivers 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. Source: Infonetics Research, 2010 WW average bandwidth per installed connection (Mbps)
  • 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 Copyright © 2009 Infonetics Research, Inc. Backhaul Service Charges per Connection
  • 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 22 Mobile Backhaul Implementation Agreement Phase I Feiling Jia Tellabs Staff Product Manager Logo
  • 10. 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
  • 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
    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
  • 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 Migration Use 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-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
  • 20. 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
  • 21. 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
  • 22. 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%
  • 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”
      • 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
  • 24. Preparing Ethernet Services for LTE MEF 22 - Phase 2 Approved Specification Approved Draft Letter Ballot Working Document Straw Ballots New Project
  • 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 Ethernet Network RNC BSC EVP-Tree 2G + 3G (GIWF) 2G (GIWF) 2G + 3G (GIWF) 2G + 3G (GIWF) 3G RAN NC UNI UNI-C UNI-N Link Aggregation Group 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
  • 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 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
  • 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 SOURCE INTEGRATED IN PHYSICAL INFRASTRUCTURE NEW TECHNOLOGIES NEW 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
  • 40. Delivering frequency sync EVPL_1 EVPL_2 EVPL_3 EVPL_4 UNI RNC BSC
    • E-Tree service for packet based sync
    • Redundancy with multiple sync server architecture
    EVP-Tree Sync Sync Server Sync Server 2G + 3G (GIWF) 2G (GIWF) 2G + 3G (GIWF) 2G + 3G (GIWF) 3G GIWF
  • 41. 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 Data Clock Application Data PRC Timing Output Timing Input Master Port Slave Port Physical Data Link Network Physical Data Link Network PLL PLL Physical Data Link Network PLL
  • 42. 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 
  • 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. Panellists Moderator Ward Zhan Fiberhome Networks Co.Ltd. Product Line Manager Logo Feiling Jia Tellabs Staff Product Manager MEF Marketing Logo Asif Hazarika IP Infusion Inc, Senior Director of Product Management MEF Marketing Xioqiang Deng Alcatel-Lucent
  • 45. Thank You For details on Carrier Ethernet for Mobile Backhaul visit: http://www.metroethernetforum.org/mobile-backhaul
  • 46. MEF Carrier Ethernet Briefing