1 / 18

New MEF Mobile Backhaul Implementation Agreement

New MEF Mobile Backhaul Implementation Agreement MEF 22 Announcement RAN BS UNI UNI Carrier Ethernet Network RAN NC UNI RAN BS MEF Mobile Backhaul Market Dynamics Objective Introduce MEF Mobile Backhaul Specification A standardized implementation guide

Leo
Download Presentation

New MEF Mobile Backhaul Implementation Agreement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New MEF Mobile BackhaulImplementation Agreement MEF 22 Announcement

  2. RAN BS UNI UNI Carrier Ethernet Network RAN NC UNI RAN BS MEF Mobile BackhaulMarket Dynamics

  3. Objective • Introduce MEF Mobile Backhaul Specification • A standardized implementation guide • Describe the opportunity for service providers: • Existing Mobile Carriers driven by demand & next gen services • New Revenue opportunities for wire-line service providers

  4. Carrier Ethernet for Mobile Operators • Ethernet is the accepted solution,but there are concerns to understand • What are these concerns? • How does the MEF Mobile Backhaul Agreement address them? • What is its scope? • What are the analysts saying? • Carrier Ethernet for Mobile Carriers Michael Howard, principal analyst at Infonetics Research “Ethernet is seen as the only solution for next generation MBHnetworks … legacy technology can’t scale … surge in spending on Ethernet over microwave …”

  5. Ethernet Options Solve Backhaul Cost Problem PDH and ATM over PDH vs New Wireline: Mobile First Mile Backhaul Service Charges per Connection Stay on PDH $37,044 Backhaul Service Charges per Connection Or, move to Ethernet $6,887 • PDH (T1/E1 etc.) costs climb directly with bandwidth • Ethernet wireline costs grow incrementally with large bandwidth increases (Ethernet, DSL, PON, cable) • New IP/Ethernet wireline options to satisfy the #1 investment driver: operational cost savings Source: Infonetics Research, Mobile Backhaul Equipment, Installed Base, and Services October 2008

  6. Backhaul Capacity Requirements at the Cell Site

  7. Carrier Ethernet for Mobile Backhaul • NPRG forecasts Carrier Ethernet services gain traction in 2009, driven by accelerating 3G cellular data plan penetration and mainstreaming of broadband wireless services (e.g., “Clear” WiMAX from Clearwire) • Revenue gains for Ethernet providers could be dramatic, as NPRG forecasts solid double-digit CAGR for the overall backhaul market through 2013 • In 2008, notable contract wins were scored by Ethernet providers in the Midwest, New York, Florida, and California; additional wins are on the horizon for 2009

  8. MEF 22 Mobile Backhaul Implementation AgreementFormally Approved Jan 29th 2009

  9. Scope (1): Operational Experience Carrier Ethernet for Mobile Carriers • The Mobile Backhaul Implementation Agreement scopes Ethernet OAM requirements • Ethernet OAM allows monitoring of Ethernet services • Verify connectivity • Identify configuration faults • Measure service performance • Loop back testing • Further developments in later phases • Draws on and includes existing standards • IEEE 802.3ah : Link OAM • IEEE 802.1ag : Connectivity Fault Management • ITU-T Y.1731 : Performance Monitoring • Class of Service requirements aligned with 3GPP and WiMAX recommendations • From high to low priority: • Conversational class (voice, whether IP- or TDM/ATM-based) • Streaming class (streaming video) • Interactive class (web browsing) • Background (non-interactive data) • Potentially synchronization and other control traffic in a separate class

  10. Scope (2): Synchronization • Migration to all packet networks means loss of TDM clock source • Components of sync • Frequency (2G, 3G, 3.5G) • Phase (4G in some cases) • Time of Day • Packet based • Out-of-band (GPS, legacy E1 clocking) is outside of scope • 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. • Synchronous Ethernet in scope for future phases • Eliminates the cost and need for retention of T1/E1 circuit solely for synchronization Carrier Ethernet for Mobile Carriers

  11. General recommendation for Fault Protection: Required at network controller Not mandatory at base station Implementations will be driven by application needs, customer preference, and cost Scope (3): Reliability and Availability Carrier Ethernet for Mobile Carriers

  12. Scope (4): Evolution Support MBH Generic Interworking Function (GIWF) User to Network Interface (UNI) • Supports Multiple Generations of Mobile Backhaul • Scalable consolidation enables backhaul of any combination of 2G/3G voice and data traffic over a single CE RAN • Designed to support 4G/LTE networks 4G NC 2G Ethernet RNC 3G BTS T1/E1 OC3/STM-1ATM (Iub) T1/E1 (TDM and ATM) N x GigE NodeB CarrierEthernet Eth Ethernet (EVDO/HSPA/3G Rel.5) Access Device Gateway BSC CH OC3/STM-1or E1/T1 (Abis) 4G Ethernet eNodeB (LTE) BS (WiMAX)

  13. Scope (5): Scalability Carrier BTS/NodeB BTS/NodeB The MBH architecture is adaptable, accommodating all popular access networks Splitter ONT Ethernet over Microwave BTS/NodeB PON Fiber Direct Fiber or FTTC Wireless CO (RNC/BSC) N x GigE BTS/NodeB Ethernet over Bonded PDH (E1/DS1) Carrier (Bonded) Copper BTS/NodeB MBH Generic Interworking Function (GIWF) User to Network Interface (UNI) Network to Network Interface (NNI) (under development)

  14. Scope (6): Migration from Legacy Networks Legacy Network Non-Ethernet Interface GIWF Non-Ethernet Interface GIWF Carrier Ethernet Network Ethernet interface Radio Access Network Base Station Ethernet interface RAN Network Controller UNI UNI • MEF Implementation Agreement specifies 4 use cases • Allow migration or immediate transition to Carrier Ethernet separating backhaul of voice and data or integrated mobile data and voice in a Carrier Ethernet network. Example: Use Case 1a: Hybrid Offload – data exchanged using Carrier Ethernet, voice transport remains with legacy network only as long as necessary The Generic Inter-working Function (GIWF) provides functionality that allows RAN CE devices with a Non-Ethernet I/F to send traffic over an Ethernet UNI UNI: User Network Interface

  15. A New Opportunity for Wire-line Service Providers • Opportunity • The new agreement provides a new wholesaleopportunity to leverage existing wire-line backhaul infrastructure and capacity • Driven by the migration of mobile technologies to Ethernet backhaul • The MBH Implementation agreements helps wholesalers • It states the requirements • Includes specific Service Level Specifications that are required for transport of Mobile Backhaul across wire-line backhaul • Other deliverables for wire-line wholesalers • Back-up slides at the end of the deck contain further business case and Mobile Backhaul fundamentals for these wholesale opportunities • New Revenue opportunities for wire-line service providers

  16. MEF Mobile Backhaul Phased Development • Phase 1 (The first Specification: MEF 22 January 2009) • Ethernet Virtual Connections (EVC) span a single MEN. • Synchronization is either delivered outside of the Ethernet transport network or using a packet based method that is transparent to the MEN*, e.g. treated as standard Service Frames. • The mobile standards that are considered are: GSM, WCDMA, CDMA2000, and WiMAX 802.16e. • Later phases (for further study) • Ethernet Virtual Connections (EVCs) spanning arbitrary number of MENs. • Other synchronization methods. • Other mobile standards, such as LTE (Long Term Evolution). • Extended architecture scope, e.g. mobile core network and additional mobile network reference points. * For consistency Carrier Ethernet networks are referred to Metro Ethernet Networks (MEN) in the specifications

  17. Summary • Mobile Operators must upgrade their backhaul to Ethernet • MEF Implementation agreement defines a common approach for all Service providers • Carrier Ethernet in the RAN opens new opportunities for fixed line operators • The migration to Ethernet RAN has started • Carrier Ethernet mandated for 4G/LTE

  18. end

More Related