Docstoc

Introduction to the MEF

Document Sample
Introduction to the MEF Powered By Docstoc
					                          Delhi
                       November 9

                        Mumbai
                      November 13


Ethernet-based Mobile Backhaul




                                    1
Moderator and Panelists


  Kanwar Jit (KJ) Singh              Karmavir Mankad
  Principal Architect,               CTO – Enterprise Business
                                     Reliance Communications Ltd
  kj@tejasnetworks.com               karmavir.mankad@relianceada.com




  Ashwani Kumar                      Manikantan Srinivasan
  Director-Sales Engineering
                                     CTO
  UTStarcom                          Net-O2 Technologies Pvt Ltd
  ashwani@utstar.com                 manis@net-o2.com


    Moderated by:

    Chandan Mendiratta, VP, Systems Engineering, cm@cisco.com
                                                                       2
Agenda


• MEF 22 - Technical Overview
• MEF22 - Application Scenario
• Synchronization
• MEF 22 - Phase 2




                                 3
Mobile data traffic growth drivers




           Source: Heavy Reading, 2008   Source: Analysys Mason, 2009




                    Source: GSA, 2009     Source: Heavy Reading, 2008


                                                                        4
MEF 22 - Technical Overview




                              5
MEF 22 - Mobile Backhaul Implementation Agreement

 • MEF22 - Explains how to apply existing MEF specifications
 • Provides generic specification for Ethernet backhaul
   architectures for mobile networks (2G, 3G, 4G)
       • User-Network Interface requirements
       • Service Requirements
       • Clock synchronization
       • Common Terminology            RAN BS

    – Offers a standardized toolset
                                                 UNI

                                                                          UNI



                                                       Carrier Ethernet         RAN NC
                                                          Network
                                               UNI
                                      RAN BS




                                                                                   6
    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
•    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


                                                                           7
Use Cases: Packet offload
             Packet offload over Carrier Ethernet – Use Case 1a
                                           Legacy
                                           Network




                                        Carrier Ethernet
                                           Network

RAN BS   Non-Ethernet   GIWF      UNI                      UNI    GIWF   Non-Ethernet   RAN NC
             I/F                                                             I/F


                               RAN dual stack – Use Case 2a

                                            Legacy
                                            Network




                                        Carrier Ethernet
                                           Network

RAN BS                           UNI                        UNI                         RAN NC



                                                                                                 8
Use Cases: Full Ethernet
                  Emulation over Carrier Ethernet – Use Case 1b




                                        Carrier Ethernet
                                           Network

 RAN BS   Non-Ethernet   GIWF     UNI                      UNI    GIWF   Non-Ethernet   RAN NC
              I/F                                                            I/F




                                Full Ethernet – Use Case 2b




                                        Carrier Ethernet
                                           Network

                  RAN BS          UNI                       UNI    RAN NC



                                                                                                 9
Application Scenario


     RAN BS

      UNI

                                 UNI


              Carrier Ethernet         RAN NC
   UNI           Network

  RAN BS

                                                10
Application Scenario - Description
• 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


                            BSC        RNC
                                                            TDM Leased Line (2Mbps)




                        Legacy Network



                                                       3G
             2G + 3G
                       2G         2G + 3G    2G + 3G


                                                                                      11
Problem

• 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
  with non-Ethernet
  interfaces?
• How to define services?
• How to deliver sync?
• How to monitor services?




                                                     12
 GIWF provides Ethernet UNI

   – 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 adaptation of the legacy mobile traffic to the Carrier Ethernet
     service can be based on TDM circuit emulation standards as well as
     ATM/HDLC pseudo-wire standards.
    Non-Ethernet                                                                   Non-Ethernet
        I/F                                                                            I/F
RAN BS         GIWF                                                          GIWF            RAN NC

                   EFT                                                       EFT
                                     Carrier Ethernet Network
                                               EVC
               UNI-C           UNI-N                       UNI-N            UNI-C



                   Eth Access Link                              Eth Access Link
                     Ethernet I/F                                 Ethernet I/F

                                                                                                  13
MEF Mobile Backhaul and GSM

• How does the GIWF handles existing GSM based networks?
   – GSM uses a number of T1 (1.5 Mbit/s) or E1 (2 Mbit/s) circuits to connect
     the base station with the network controller.
   – The GIWF terminates a circuit emulation service (CES) per such E1/T1
     circuit at the cell site or service edge and at the network controller site
   – A variety of circuit emulation services can be used in the implementation
     agreement (MEF8 (CESoE), TDMoMPLS (MFA8), SAToP (RFC4553),
     CESoPSN (RFC5086))

                          Service Provider Network
                                                                             Carrier Ethernet
                                    TDM Circuit Emulation                        Network


               TDM    CES Ethernet         Carrier Ethernet        Ethernet CES          TDM
                      IWF                     Network                        IWF
                                                                                                   RAN NC
  RAN BS
                                                E-Line
                             Ethernet                            Ethernet
                                                Service
                               UNI                                 UNI           ATM / TDM
           ATM / TDM BS
            demarcation                                                        Network Interface
                          CES IWF: Circuit Emulation Interworking Function



                                                                                                            14
 MEF Mobile Backhaul and UMTS / WCDMA

• How does the GIWF handles legacy UMTS based networks?
  – These Technologies uses ATM over a number of bundled T1 (1.5 Mbit/s) or E1
    (2 Mbit/s) circuits to connect the base station with the network controller.
  – The GIWF terminates an ATM pseudo-wire or a TDM circuit emulation tunnel at
    the cell site or service edge and at the network controller site
  – A variety of ATM pseudo-wire and/or TDM circuit emulation standards can be
    used in the implementation agreement


                            Service Provider Network
                                                                       Carrier Ethernet
                                    ATM Pseudo-wire                        Network


                 ATM    CES Ethernet     Carrier Ethernet    Ethernet CES          ATM
                        IWF                 Network                    IWF
                                                                                             RAN NC
    RAN BS
                                            E-Line
                              Ethernet                      Ethernet
                                            Service
                                UNI                           UNI          ATM / TDM
             ATM / TDM BS
              demarcation                                                Network Interface


                                                                                                      15
Create a UNI at each site

• GIWF provides 2G with Ethernet interface

• Single UNI towards the CEN

                             BSC          RNC
                                                                  RAN NC
                                  GIWF


          Carrier Ethernet
          Network




                                                                           UNI


 RAN BS       2G + 3G
                                                             3G
              (GIWF)       2G                      2G + 3G
                                         2G + 3G
                         (GIWF)                    (GIWF)
                                         (GIWF)


                                                                                 16
Services for emulated circuits
• Assumption: Emulation solution requires the following
  performance requirements:
   – FD = 20ms, FDV = 5ms, FLR=10-4, Availability=99.99%
   – CIR = 2.5Mbps, 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 * 2.5Mbps
                                  BSC          RNC

                                       GIWF


               Carrier Ethernet                                        EVPL_1
               Network                                                 EVPL_2
                                                                       EVPL_3
                                                                       EVPL_4


                                                                       UNI


                                                                  3G
                   2G + 3G
                   (GIWF)       2G                      2G + 3G
                                              2G + 3G
                              (GIWF)                    (GIWF)
                                              (GIWF)


                                                                                17
Services for 3G Ethernet RAN BS
• 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


                               BSC          RNC

                                    GIWF


            Carrier Ethernet                                        EVPL_1
            Network                                                 EVPL_2
                                                                    EVPL_3
                                                                    EVPL_4
                                                                    EVP-Tree

                                                                    UNI


                                                               3G
                2G + 3G
                (GIWF)       2G                      2G + 3G
                                           2G + 3G
                           (GIWF)                    (GIWF)
                                           (GIWF)


                                                                               18
CoS configuration



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




                                                                                      19
Protection at RAN NC
                                                                      RAN NC UNI
                                                           UNI-C


                                                                   Link Aggregation
                                                                   Group


                                                           UNI-N
                           BSC          RNC

                                GIWF


        Carrier Ethernet                                                 EVPL_1
        Network                                                          EVPL_2
                                                                         EVPL_3
                                                                         EVPL_4
                                                                         EVP-Tree

                                                                         UNI


                                                           3G
            2G + 3G
            (GIWF)       2G                      2G + 3G
                                       2G + 3G
                       (GIWF)                    (GIWF)
                                       (GIWF)


                                                                                      20
Service OAM

    RAN BS                                                          RAN NC


                         Carrier Ethernet Network




               Link MA                              Link MA
                           Service Provider MA
                           Mobile Operator MA
                                                              MEP     MIP

• SOAM for Fault Management and Performance
  Monitoring
  – Link level
  – Edge-to-edge
• Measurements points needed in CEN


                                                                             21
Delivering Frequency Sync

• E-Tree service for packet based sync

• Redundancy with multiple sync server architecture


                            BSC          RNC
                Sync                                 Sync
               Server            GIWF               Server

                                                                  EVPL_1
                                                                  EVPL_2
                                                                  EVPL_3
                                                                  EVPL_4
                                                                  EVP-Tree
                                                                  Sync

                                                                  UNI


                                                             3G
              2G + 3G
              (GIWF)      2G                      2G + 3G
                                        2G + 3G
                        (GIWF)                    (GIWF)
                                        (GIWF)


                                                                             22
Application Scenario Summary

• Illustrated how to apply MEF 22 toolset

• Combined Use Case 1b and Use Case 2b

• Several other viable combinations


    2G




    3G




                                            23
Synchronization in Ethernet
    backhaul networks



                              24
MEF Approach to Synchronization

• Three principal Components of sync
  – Frequency synchronization (2G, 3G, 3.5G)
  – Phase synchronization (4G)
  – ToD synchronization
• Packet based methods
  – In scope of Phase 1
  – Synchronization quality requirements
     reference the ITU G.8261 standard
• Synchronous Ethernet
  – In scope for future phases
  – Eliminates the cost and need for retention of T1/E1 circuit
    solely for synchronization

                                                              25
1588v2 Precise Timing Protocol
• Packet based synchronization mechanism
   – UDP/IP layers messaging (multicast and unicast) over Ethernet
• 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

                                                                     26
Delivering Synchronization

• Options:
  – sync over a separate EVC or
  – sent over the services in a different CoS class




      UNI                      UNI


            EVPL_1 (CES)                      CoS 1 (CES)
                                     EVPL_1
                                              CoS 2 (Sync)
            EVPL_Sync




                                                             27
   Synchronous Ethernet (future)
         • 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                      Application Data



                   Network             Network            Network
                   Data Link           Data Link          Data Link
                   Physical            Physical           Physical
PRC                                                                                Timing
          PLL                                                                PLL
Timing                                                                             Input
Output                                       PLL




    Data                       Clock     Master Port           Slave Port

                                                                                      28
             MEF 22 - Phase 2


 New       Working   Straw     Approved   Letter    Approved
Project   Document   Ballots     Draft    Ballot   Specification




                                                                   29
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




                                                     30
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!
                                    31
 Relationship between the MEF and BBF
• The MEF MBH IA describes a superset of potential
  implementations
• The Broadband Forum provides a specific network
  implementation reference based on MPLS
• MEF and Broadband Forum will continue to align future
  activities


                                Carrier Ethernet Network


                     Ethernet       MPLS Network            Ethernet

      RAN BS                        E-Line Service
                                                                             RAN NC

                                    Pseudo-wire
               UNI     MPLS Service   Service        MPLS Service      UNI
                        Termination                   Termination

                                                                                      32
Summary


• RAN is going IP
• MEF 22 specifies a toolset for
  defining Carrier Ethernet services
• There are many solutions to the
  same problem
• Phase 2 will be more detailed and
  include LTE requirements




                                       33
Moderator and Panelists


  Kanwar Jit (KJ) Singh              Karmavir Mankad
  Principal Architect,               CTO – Enterprise Business
                                     Reliance Communications Ltd
  kj@tejasnetworks.com               karmavir.mankad@relianceada.com




  Ashwani Kumar                      Manikantan Srinivasan
  Director-Sales Engineering
                                     CTO
  UTStarcom                          Net-O2 Technologies Pvt Ltd
  ashwani@utstar.com                 manis@net-o2.com


    Moderated by:

    Chandan Mendiratta, VP, Systems Engineering, cm@cisco.com
                                                                       34
                                Delhi
                             November 9

                               Mumbai
                             November 13




Carrier Ethernet Workshops-2009

     www.metroethernetforum.org
      www.ethernetacademy.net
                                           35

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:10/19/2012
language:Unknown
pages:35