An Overview of the MEF by wulinqing

VIEWS: 7 PAGES: 41

									  Carrier Ethernet
for Mobile Backhaul


     CEWC Berlin
 September 22nd 2008


                       1
                             Panelists

Ran Avital
Name Research Co-Chair
MEF Market                              Dirk Lindemeier
Title Strategic and Product Marketing
VP of                                   Mobile Backhaul Solutions Development
Company Name
Ceragon Networks                        Nokia Siemens Networks
E-mail
rana@ceragon.com                        dirk.lindemeier@nsn.com
+972-52-5847526
Phone: +44 234 346 4981                 +49 151 5515 3351




Jonathan Olsson                         Brian Bortz,
MEF Mobile Backhaul IA Editor           CEO, Resolute Networks
Standardization Coordinator, Ericsson   brianb@ResoluteNetworks.com
jonathan.olsson@ericsson.com            +972-52-2210548
+46 8 404 3720
                                                                                2
                     Carrier Ethernet
                   for Mobile Backhaul

                        Introduction
Ran Avital
MEF Market Research Co-Chair
VP of Strategic and Product Marketing
Ceragon Networks
rana@ceragon.com
+972-52-5847526                          3
  Agenda

• The Carrier Ethernet value proposition for
  mobile backhaul
• MEF Specification work to optimize Carrier
  Ethernet for Backhaul
• Carrier Ethernet technologies and
  applications for Mobile Backhaul
• Circuit Emulation Services over Ethernet
  (CESoETH)




                                               4
Mobile Backhaul Market Survey

 •Evaluate network planning assumptions and integrate the
 derived needs from the MEF Implementation Agreement (IA)
 •41 operators/worldwide coverage (APAC 20%, EMEA 49%,
 NA 27% and LA 5%)
 •Independent research commissioned by the MEF




                                                            5
   Mobile Backhaul Market Survey- Highlights
Ethernet performance attributes Standards?
                                    MEF 10.1 (76%)                         IETF/ITU
Single or multiple Availability Requirements?
                        2 or 3 levels (44%)            All services created equally
Availability Requirements?
                          5 9s and up (49%)                   4 9s and below
Latency budget for synchronization?
                               <1ms, 1-3ms, 3-5ms (78%)                      5-10ms
Will you require Ethernet Service OAM (IEEE 802.1ag, ITU-T Y.1731)?
                                      Require (78%)                              Likely
How likely to transport legacy traffic over Ethernet using an interworking function?
                             Likely (51%)                        Not so likely
How Many CoS?
                                      3 or 4 (75%)                           5 or 8

                                                                                          6
                        Carrier Ethernet
                      for Mobile Backhaul

 Trends, Technologies and Applications
Dirk Lindemeier
Mobile Backhaul Solutions Development
Nokia Siemens Networks
dirk.lindemeier@nsn.com
+49 151 5515 3351
                                            7
   Mobile Backhaul Has Dynamic Growth …
• New mobile                     9/06                       7/07
  applications and
  bandwidth growth
  (>100% in 2008 with
  much more to come)




                           Legacy TDM
                          Movies, music, news, more
                        music, text, web, more content ..




                                                                   8
Industry trends

• Demand for bandwidth will grow
  disproportionately more than                            Traffic
  revenue for the operator
• The bandwidth increase will                                          Gap between
                                                                    Gap between traffic
                                                                     Gap between traffic
                                                                    traffic and revenue
                                                                        and revenue
  primarily be on Best Effort data                                        increases
  user services, and driven by ‘flat
  fee business models’                                                      Revenues
• Search for technologies to
  provide cheaper and more               Voice Dominant         Data Dominant
  effective ways to meet the
  capacity grow at a lower CAPEX       Source: Light Reading
  and OPEX
• Evolution towards Ethernet/IP
  based mobile solutions


                                                                                           9
   Why Carrier Ethernet for Mobile Backhaul?

• Mobile services need
  Coverage
• Leasing backhaul
  services is a common
  practice
• High capacity, low cost
  creates new
  opportunities
   – Wholesale
   – RAN sharing
   – Converged operations   A better way to do business
                            in Mobile Backhaul


                                                          10
   Key Reasons for Carrier Ethernet
• Carrier Ethernet
   – Economically meets exploding bandwidth requirements currently
     constrained by the prohibitive costs of legacy networks
   – Leverages rapid move to Carrier Ethernet for wire-line traffic enabling
     a single integrated wire-line and mobile backhaul network
   – Much easier for service providers to manage and maintain
• Most mobile traffic is broadband/IP centric
   – Carrier Ethernet is optimized for packet data traffic
• Overcomes TDM (T1/E1) services scalability
   – This alone makes Carrier Ethernet the compelling choice
• Time/urgency
   – Carrier Ethernet removes the barrier to timely progress




                                                                               11
  Ethernet Options Solve Backhaul Cost Problem


                Worldwide M obile 1st M ile Backhaul Service Charges per
                                      Connection:                                                • PDH (T1/E1 etc.) costs
                       PDH and ATM over PDH vs New Wireline
                                                                                                   climb directly with
          $40,000                                                                                  bandwidth
                                                                                                 • Ethernet wire-line costs
                                                          $37,044
                      Stay on PDH

          $30,000                                                                                  grow gently with large
                                                                                                   bandwidth increases (Eth,
                                                                                                   DSL, PON, cable)
Revenue




                                                                     PDH and ATM over PDH
          $20,000
                                                                     New wireline
                                                                                                 • New IP/Ethernet wire-line
                                        Ethernet                                                   options to satisfy the the #1
          $10,000
                                                          $6,887
                                                                                                   investment driver:
                                                                                                   operational cost savings
              $0
               CY05   CY06   CY07     CY08    CY09     CY10
                             Calendar Year




                             Source: Infonetics Research Mobile Backhaul Equipment, Installed Base, and Services, 2007



                                                                                                                             12
     Carrier Ethernet: the common denominator


                         µwave
             BTS
                            Copper                         BSC
                                              Carrier
            NodeB
                                             Ethernet
                                             Network       RNC



             eNB            Fibre                          AGW



•   Installed 2G base is TDM based, requires emulation
•   3G is evolving to IP/Ethernet rapidly
•   4G will be IP/Ethernet based from the start
•   Ethernet is common denominator for all relevant backhaul
    technologies

                                                                 13
   What are mobile operators doing?

• HSDPA 3.6Mbps is a widespread reality, next step
  (7.2Mbps) is imminent
• IP/Ethernet is acknowledged as the only possible
  solution to accommodate ever increasing traffic
• New NodeBs are being rolled out with IP/Ethernet
  interfaces as the standard configuration
• Tangible synchronization solutions are becoming
  available
   – Hybrid backhaul (sync over parallel E1/T1) used during early
     rollouts, starting 2007
   – IEEE1588v2 standardized, products 2008
   – Synchronous Ethernet standardized (G.8261, G.8262, pending
     G.8264), products 2008



                                                                    14
   MEF Member Initiative:
   Mobile Backhaul Interoperability Showcase

• Mobile Backhaul Interoperability Demonstration
   – Conducted by MEF Member (EANTC)
   – In collaboration with and sponsored by 15 MEF Members
   – Showcase at Mobile World Congress (Barcelona, 2/08 and
     CTIA., Las Vegas, 4/08)
• Live Mobile Application Demonstration
   –   End-to-end services, Resiliency
   –   End-to-end CE Service OAM
   –   Quality of Service support
   –   Performance monitoring
   –   Bandwidth profiles
   –   Circuit Emulation Services
• White Paper
   – “Public Multi-Vendor Mobile Backhaul Interoperability Test”
          •   This event was not conducted by the MEF. Test methodology and results solely the
              responsibility of EANTC in collaboration with the participants                     15
A complete answer for emerging requirements




                                              16
   Reality check: where are we today?

• NodeB Ethernet interfaces available from all major 3G
  vendors – live here in Berlin
   – Installed base and new rollouts
• Ethernet microwave radios widely available – live here
  in Berlin
   – Installed base and new rollouts
• Synchronization over Carrier Ethernet based on
  IEEE1588v2 – live here in Berlin
• Mobile broadband over multi vendor Carrier Ethernet
  end to end – live here in Berlin
• MEF implementation agreement almost ready



                                                           17
                        Carrier Ethernet
                      for Mobile Backhaul

   The Implementation Agreement Draft
Jonathan Olsson
MEF Mobile Backhaul IA Editor
Standardization Coordinator, Ericsson
jonathan.olsson@ericsson.com
+46 8 404 3720
                                            18
  Introduction to the MEF MBH IA

• What initiated the work?
  –   Predicted increased data traffic volumes
  –   RAN going packet and challenges thereof
  –   Deployment scenarios
  –   Desire for cost reduction


  MEF set out to define Carrier Ethernet service
       requirements for mobile backhaul




                                                   19
   Scope of the Implementation Agreement

• Utilize existing MEF technical specifications with required
  extensions to interface and service attributes.
• Provide requirements for UNI-C and UNI-N.
• 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 high-level requirements for CoS.
• Define synchronization requirements where possible for
  transparent packet based synchronization methods.
• Functional requirements applicable to GIWF interfaces.




                                                                   20
   Mobile Backhaul Implementation Agreement

   The structure of the IA provides guidelines for
   several mobile technologies – specific guidelines
   for a given mobile technology may also be specified


• UNI Requirements
   – UNI Type
   – Ethernet OAM (Link OAM and             UNI
     Service OAM)                                 Metro Ethernet
                                   RAN BS            Network
                                                                   UNI
                                                       EVC
• Service Requirements
   – CoS Requirements
   – Applying MEF Services                  UNI                          RAN NC

   – Synchronization
                                  RAN BS




                                                                             21
 Use Cases


• There are many possible deployment
  scenarios
• The Implementation Agreement identifies
  four generic deployment scenarios that
  capture the main short term and long term
  deployment possibilities




                                              22
  But first…the site concept in the IA

• The details inside the RAN sites, e.g. cell site
  or network controller site, are outside the
  scope of MEF
  – RAN BS – base station site
  – RAN NC – network controller site
• But we know a site may be composed of a
  single node or multiple nodes that are
  attached to a UNI
• A site is expected to provide the UNI-C
  functions as specified in the IA


                                                     23
Legacy Mobile Backhaul Migration
           Packet offload over Carrier Ethernet – Use Case 1a


              Generic            Metro Ethernet Network           Generic
            Interworking                                        Interworking
              Function                                            Function

                           UNI                            UNI


  RAN BS                            Legacy Network
                                                                        RAN NC

                                                                                 Legacy

                                                                                 Eth/IP
             Emulation over Carrier Ethernet – Use Case 1b



              Generic
            Interworking
                                 Metro Ethernet Network           Generic
                                                                Interworking
  RAN BS      Function                                            Function

                           UNI                            UNI           RAN NC




                                                                                     24
When RAN nodes are equipped with Ethernet
                 RAN dual stack – Use Case 2a
                         Legacy Network




                     Metro Ethernet Network
  RAN BS

           UNI                                  UNI RAN NC


                                                             Legacy

                                                             Eth/IP
                  Full Ethernet – Use Case 2b



                     Metro Ethernet Network
  RAN BS

           UNI                                  UNI RAN NC



                                                                 25
   Service Requirements

• Typically there are 1-2 RNC sites and between
  hundreds to thousands of RBS sites
• Bandwidth requirements for a base station site will
  vary may range from a few Mbps to over a Gbps
• Services need to be:
   – Scalable
   – Flexible
   – Cost effective
• Service types (port-based and VLAN-based)
   – E-Line
   – E-LAN
   – E-Tree




                                                        26
Service Definitions – Point-to-Point


                     • Similar to leased lines
                     • Requires traffic separation per RAN BS at
                       RAN NC




            RAN BS




   RAN BS                                                RAN NC




                                                EVC 1
                                                EVC 2
                                                EVC 3
            RAN BS




                                                                   27
Service Definitions – Rooted Multipoint

                                         • Similar behavior as leased lines
                                         • Supports simpler RAN BS and RAN NC
                                           solutions
                                         • Multiplexing could be used for increased
                                           traffic separation



                     RAN BS
                              Leaf UNI




   RAN BS Leaf UNI                                                     Root UNI   RAN NC


                          Leaf UNI
                                                                    EVC 1
                                                                    EVC 2

                     RAN BS




                                                                                           28
   Traffic separation

• Guidelines for the number of CoS classes to use
• Bundling traffic types into limited number of CoS
  classes
• CoS class performance requirements

            Service Class           Example of Generic Traffic Classes mapping into CoS
               Name
                               4 CoS Model             3 CoS Model              2 CoS Model
            Very High (H+)     Synchronization                 -                        -
              High (H)          Conversational,       Conversational and       Conversational and
                             Signaling and Control     Synchronization,         Synchronization,
                                                     Signaling and Control   Signaling and Control ,
                                                                                   Streaming
             Medium (M)           Streaming               Streaming                     -
               Low (L)          Interactive and         Interactive and          Interactive and
                                 Background              Background               Background




                                                                                                       29
    Ethernet OAM*

   • Ethernet OAM entities – configuration options
   • Fault Management – fault localization and
     accountability
   • Performance Monitoring – service performance
     validation (For Further Study)


           RAN BS                                            RAN NC


                              Metro Ethernet Network




                                Mobile Operator MA
* Available with UNI Type 2                            MEP     MIP



                                                                      30
   Current Status

• Substantial updates to the IA after previous Straw
  Ballot

• Internal review – Straw Ballot

• Continue to liaise with other industry forums to
  ensure industry alignment

• Anticipate completion 2008 Q4


               New      Approved   Straw    Letter    Approved
              Project     Draft    Ballot   Ballot   Specification




                                                                     31
                       Carrier Ethernet
                     for Mobile Backhaul
    Synchronization, MEF 8 and MEF 18
Brian Bortz
CEO,
Resolute Networks
brianb@resolutenetworks.com
+972-52-2210548
                                           32
   Synchronization

• Types of sync
   – Frequency
   – Phase
   – Time
• 3 different methods
   – Common Clock
   – Packet Based Synch
      • IEEE 1588 V2,
      • Differential Clock Recovery
      • Adaptive Clock Recovery
   – Synchronous Ethernet
• Current approach
   – References G.8261
   – Focus on packet based timing methods

                                            33
     Concept of Synchronous Ethernet

                         Data
                                       Packet Network                  Data




                    L2-L7 (Packet)      L2-L7 (Packet)          L2-L7 (Packet)
Stratum 1
Traceable                                                                                    Recovered
reference          Physical Layer      Physical Layer          Physical Layer                  Clock
            DPLL                                                                    DPLL



                                             DPLL




• Uses the PHY clock                                     Timing Flow             Data Flow


    – Generates the clock signal from “bit stream”
    – Similar to traditional SONET/SDH/PDH PLLs
• Each node in the Packet Network recovers the clock
• Performance is independent of network loading

                                                                                                  34
 Concept of IEEE 1588 V2
                                  Master Clock Time                        Slave Clock Time
                                                             Sync message
                                                    T1
                                                          Follow_Up message        T2
                                                         containing value of T1


                                                          Delay_Req message
PRS: GPS / SynchE / …                                                              T3
                                                    T4
    PRS
                                                          Delay_Resp message
                                                          containing value of T4




    IEEE1588                          IEEE1588
    Master                         SLAVE / Master




                Packet Switched
                   Network




                                                                                        35
        CES and the
   MEF Certification Program
• Circuit Emulation Services over Ethernet
• Supporting Enhancements to the MEF
  Certification Program



                                             36
   Migration: Circuit Emulation Services (CES)

• CES is a major step in industry’s progression
  toward entirely converged networks
   – Transports TDM services over Carrier Ethernet services
   – Converged networks for data, video and voice have been a
     dream of the industry
   – Technical challenges to combine TDM and data are not trivial
   – MEF 8 was designed to meet these challenges, MEF 18 to
     certify conformance
   • Transition Path                                                8,18
       – Legacy voice traffic is transported via TDM
         and CES over Carrier Ethernet (CESoETH)
       – Data growth is handled by Carrier Ethernet
       – Traffic is merged over time



                                                                       37
 MEF 18 Certification


• MEF 18 provides standard testing of Circuit Emulation
  Services over Ethernet
• 334 ground breaking tests and certification in the suite
• Industry first impairment testing brings first test of
  emulation of clock recovery
• MEF certification speeds implementation and enables
  full inter-operability
• MEF 18 has many applications but is key
  to Mobile Backhaul migration strategies




                                                             38
  Closing

• Carrier Ethernet is in demand for Mobile
  Backhaul
• There are Ethernet deployment options for all
  mobile backhaul situations
• Carrier Ethernet technology is rising to meet the
  stringent technical and operational requirements
  of Mobile Backhaul
• The MEF is working in conjunction with other
  standards organizations to ensure that scalable
  solutions are available


                                                      39
                             Panelists

Ran Avital
Name Research Co-Chair
MEF Market                              Dirk Lindemeier
Title Strategic and Product Marketing
VP of                                   Mobile Backhaul Solutions Development
Company Name
Ceragon Networks                        Nokia Siemens Networks
E-mail
rana@ceragon.com                        dirk.lindemeier@nsn.com
+972-52-5847526
Phone: +44 234 346 4981                 +49 151 5515 3351




Jonathan Olsson                         Brian Bortz,
MEF Mobile Backhaul IA Editor           CEO, Resolute Networks
Standardization Coordinator, Ericsson   brianb@ResoluteNetworks.com
jonathan.olsson@ericsson.com            +972-52-2210548
+46 8 404 3720
                                                                                  40
                                                                                40
For in-depth presentations of Carrier Ethernet for business, Ethernet services, technical
 overview, certification program etc., visit: www.metroethernetforum.org/presentations



   For more information regarding joining the MEF:
   Visit:               www.metroethernetforum.org
   Email us at:         manager@metroethernetforum.org
   Call us at:          +1 310 258 8032 (California, USA)

                       Accelerating Worldwide Adoption of
                  Carrier-class Ethernet Networks and Services


                                                                                        41

								
To top