1 / 36

Carrier Ethernet for Mobile Backhaul

Topics

miakoda
Download Presentation

Carrier Ethernet for Mobile Backhaul

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. Carrier Ethernet for Mobile Backhaul

    2. Topics – Carrier Ethernet for Mobile Backhaul Current status and trends Activating Carrier Ethernet for Mobile Backhaul Issues and Solutions for Mobile Backhaul MEF’s role in enabling Mobile Backhaul infrastructure deployment Questions from the Audience

    3. Panel Members

    4. Carrier Ethernet for Mobile Backhaul Current Status and Trends

    5. Mobile Backhaul Trends Over 2.5 billion mobile phone users in 2006, growing to 3.6 billion in 2010 Growing dependence on mobile connection Data and video mobility for all Growing Data & Video – more asymmetrical Traffic grows exponentially, ARPU/revenue does not The #1 driver for new backhaul technologies Carrier Ethernet for backhaul Ethernet microwave Wireline Ethernet copper, coax, fiber, DOCSIS, DSL, PON

    6. Mobile Backhaul Has Dynamic Growth … Symmetrical BW required for existing 2G/3G traffic Growing Data & Video – more asymmetrical

    7. Industry trends Demand for bandwidth will grow disproportionately more than revenue for the operator The bandwidth increase will primarily be on Best Effort data user services, and driven by ‘flat fee business models’ Search for technologies to provide cheaper and more effective ways to meet the capacity grow at a lower CAPEX and OPEX Evolution towards Ethernet/IP based mobile solutions

    8. RAN Backhaul Bandwidth issues……..

    9. Carrier Ethernet for Mobile Backhaul Activating Carrier Ethernet for Mobile Backhaul

    10. What the Wireless Carriers are Thinking about Migration to IP WiMax & LTE are all IP CDMA is moving there rapidly UMTS “3G” is moving to IP via ATM, Ethernet Radios this year Cell Site equipment & Mobile applications being designed for IP Circuit Emulation to sustain TDM infrastructure Bandwidth Growth – Need to plan for 15 to 20 times the growth of bandwidth and systems over the next 5 to 8 years. Mobile operators are looking to Lower Costs Broadband costs less per bit than T1 Reduce the amount of systems -- simplify

    11. Ethernet Options Solve Backhaul Cost Problem

    12. Mobile Backhaul Options Real life example of carrier challenges for delivering a ubiquitous ethernet service to a band headquarters and its branches The headquarters and downtown branches are in fiber fed offices, which are easy to get to, but the suburban branches can only be reach via copper The out of state branches are in another carriers territory and must be fed using leased capacity (DS3) The carrier (and end-user) want a uniform service across all these branches/headquarters regardless of first mile technology – the only difference between sites should be the Ethernet service bit rate Real life example of carrier challenges for delivering a ubiquitous ethernet service to a band headquarters and its branches The headquarters and downtown branches are in fiber fed offices, which are easy to get to, but the suburban branches can only be reach via copper The out of state branches are in another carriers territory and must be fed using leased capacity (DS3) The carrier (and end-user) want a uniform service across all these branches/headquarters regardless of first mile technology – the only difference between sites should be the Ethernet service bit rate

    13. Ethernet Growth by Backhaul Technology - NA In North America, T1s continue to be the dominant backhaul technology for the period 2007-2011. For new Ethernet deployments, most will be served by Ethernet over fiber (59%) and microwave (25%) technologies.

    14. Progression to an All-Packet Network

    15. Challenges and Requirements Transport Providers and Mobile Operators Transport providers are trying to: Support multiple operators at the same tower Accurately and independently regenerate timing per mobile operator Deliver quality service (low latency, jitter and packet loss) Support variety of cellular protocols with TDM, ATM and Ethernet interfaces Provide diagnostic tools to operator, such as in-band facility loopbacks Find hardened units for use in compact outdoor cabinets DBA = dynamic bandwidth allocationDBA = dynamic bandwidth allocation

    16. Challenges and Requirements Transport Providers and Mobile Operators Mobile operators are looking for flexible equipment that can: Take advantage of the lowest cost, highest bandwidth access networks Optimize usage of access links with intelligent oversubscription, idle flag suppression, Abis optimization, DBA, per VC switching, etc. Detect faults and network degradation (excessive latency, jitter, etc.) Monitor performance to ensure SLA guarantees are met DBA = dynamic bandwidth allocationDBA = dynamic bandwidth allocation

    17. Carrier Ethernet for Mobile Backhaul Issues and Solutions for Mobile Backhaul

    18. Mobile issues – SLAs and PM Service performance and SLAs Delay, delay variation and timing are key for Mobile backhaul Metro Ethernet Forum (MEF) Recommended key parameters for SLAs – MEF 10.1 Service availability, frames lost, frame delay, frame delay variation Defined the “what”, not the “how” RFC-2819 - RMON Etherstats Monitoring of local performance (eg node or LAN) Y.1731/802.1ag Focused on end to end service (WAN) Includes both monitoring and test Frame delay, frame delay variation, frame loss ratio Diagnostics Ethernet Frame loss, latency & throughput using RFC-2544 and MAC swap loopbacks Circuit Emulation using ANSI T1 403 inband facility loopbacks

    19. Circuit Emulation / Pseudowire technology enables legacy migration to packet-switched networks (IP, Ethernet, and MPLS). MEF-8: IA for the Emulation of PDH Circuits over Carrier Ethernet MEF-18: Abstract Test Suite for Circuit Emulation Services Pseudowire challenges: “Packetization” and Encapsulation of TDM Traffic Attenuate Packet Delay Variation (PDV or Jitter) Compensate for Frame Loss and Out-of-Sequence Packets Recover Clock and Synchronization We use pseudowires to emulate TDM, ATM and FR services over IP, Ethernet and MPLS As shown in the diagram, these pseudowires could be emulating TDM circuits between PBXs, ATM connections between DSLAMs and B-RAS or backhauling cellular traffic from BTS to BSC or RNC across the PSN. To succeed, pseudowire must be able to packetize or segment TDM traffic before adding an IP, Ethernet or MPLS header and sending across the PSN. At the receiving end it needs to compensate for network jitter and if necessary compensate for It also needs to compensate for Frame Loss and Out-of-Sequence Packets. A critical challenge is to accurately recover Clock at the remote end and therefore maintain synchronization across an asynchronous packet based network. This technology is now mature and tens of thousands of ports have been deployed since It was first introduced in 1999.We use pseudowires to emulate TDM, ATM and FR services over IP, Ethernet and MPLS As shown in the diagram, these pseudowires could be emulating TDM circuits between PBXs, ATM connections between DSLAMs and B-RAS or backhauling cellular traffic from BTS to BSC or RNC across the PSN. To succeed, pseudowire must be able to packetize or segment TDM traffic before adding an IP, Ethernet or MPLS header and sending across the PSN. At the receiving end it needs to compensate for network jitter and if necessary compensate for It also needs to compensate for Frame Loss and Out-of-Sequence Packets. A critical challenge is to accurately recover Clock at the remote end and therefore maintain synchronization across an asynchronous packet based network. This technology is now mature and tens of thousands of ports have been deployed since It was first introduced in 1999.

    20. Synchronization Over Packet Switched Networks 2G/2.5G/3G require accurate frequency reference: GSM (50ppb), UMTS (16ppb) CDMA (uses GPS receivers) Ideally holdover of ±16 ppb ±1 ppb of aging per day Recovered clock at the cell site should conform to ITU-T G.823/G.824 Sync interface using G.8261-defined scenarios Multiple Timing Domains System timing with master and fallback sources

    21. Mobile Backhaul Synchronization over Ethernet Cellular base stations of any generation (2G, 2.5G and 3G) require a highly accurate frequency reference The possibility of deriving transmission frequencies from this reference Lengthy synchronization procedures between cells (for hand-off) when their clocks are not sufficiently similar CDMA over Ethernet From a timing point of view, this is relatively straightforward since CDMA uses GPS receivers at each cell site Therefore each base station is effectively self synchronizing with master clocks in the GPS Satellite network GSM, W-CDMA and UMTS over Ethernet Base stations rely on a recovered clock from the T1/E1 leased line or microwave link to which they are connected 50 parts per billion of frequency error is required to support the GSM handoff mechanism as mobile stations wander from one cell to the other. With UMTS, the clock should have frequency stability of less than 16 ppb

    22. Primary Synchronization Methods Adaptive Clock is distributed over the PSN as TDM stream and is adaptively recovered solely using time-of-arrival information The format of the clock stream is a standard PWE3 flow, so interoperability with 3rd party vendors is simplified Independent of the physical layer IEEE 1588v2 Time and frequency distribution protocol based on time-stamp information exchange (similar to NTP) If the PSN network elements do not support 1588, then 1588 and adaptive deliver the same frequency recovery performance Note that 1588 is just the packet format; what is critical is the clock recovery algorithm, which is not standardized ITU G.8261 (Synchronous Ethernet) Uses the physical layer of Ethernet for accurate frequency distribution Unaffected by network impairments (e.g., PDV, Packet-loss, etc.)

    23. Reduce transport costs by migrating 2G/2.5G, 3G and 4G to scalable, lower cost, higher bandwidth Ethernet Carrier Ethernet can provide Mobile Backhaul RAD has a comprehensive family of backhaul solutions that are ideal for mobile operators looking to migrate from traditional PDH, SDH and ATM access infrastructures to hybrid solutions and then to IP, Ethernet and MPLS. RAD’s ACE, IPmux and Vmux product lines help to reduce transport costs by optimizing bandwidth and supporting more efficient network topologies. Bandwidth optimization is achieved by deploying idle flag suppression, Abis/Ater optimization, statistical multiplexing, idle cell removal, and per-VC switching to offload data traffic from expensive links, while their ability to transport TDM, ATM and Ethernet traffic over any mix of TDM, ATM, Ethernet, IP, MPLS or DSL networks helps take advantage of more efficient network topologies. This is particularly important in situations where it is more economical for high priority real time traffic to traverse one network while low priority best effort traffic is sent over a lower cost network, such as DSL, fixed wireless or cable modems. I think a key differentiator for RAD is our support for precise and accurate timing over packet switched networks with a frequency accuracy of better than 16 ppb, a jitter mask according to G.8261, and a holdover accuracy of 1 ppb per 24 hours. RAD platforms are also now adding support for IEEE-1588v2 and Synchronous Ethernet. I also want to mention that RAD has built a family of intelligent demarcation devices that support the full suite of management and OAM capabilities required by WiMAX and other 4G services that need to be backed by SLA guarantees Finally the Vmux voice compression gateways allow operators to dramatically reduce the cost of MSC-to-MSC transport for both voice and voicemail applications while our Airmux radios provide high quality Ethernet and T1/E1 backhaul over microwave links.RAD has a comprehensive family of backhaul solutions that are ideal for mobile operators looking to migrate from traditional PDH, SDH and ATM access infrastructures to hybrid solutions and then to IP, Ethernet and MPLS. RAD’s ACE, IPmux and Vmux product lines help to reduce transport costs by optimizing bandwidth and supporting more efficient network topologies. Bandwidth optimization is achieved by deploying idle flag suppression, Abis/Ater optimization, statistical multiplexing, idle cell removal, and per-VC switching to offload data traffic from expensive links, while their ability to transport TDM, ATM and Ethernet traffic over any mix of TDM, ATM, Ethernet, IP, MPLS or DSL networks helps take advantage of more efficient network topologies. This is particularly important in situations where it is more economical for high priority real time traffic to traverse one network while low priority best effort traffic is sent over a lower cost network, such as DSL, fixed wireless or cable modems. I think a key differentiator for RAD is our support for precise and accurate timing over packet switched networks with a frequency accuracy of better than 16 ppb, a jitter mask according to G.8261, and a holdover accuracy of 1 ppb per 24 hours. RAD platforms are also now adding support for IEEE-1588v2 and Synchronous Ethernet. I also want to mention that RAD has built a family of intelligent demarcation devices that support the full suite of management and OAM capabilities required by WiMAX and other 4G services that need to be backed by SLA guarantees Finally the Vmux voice compression gateways allow operators to dramatically reduce the cost of MSC-to-MSC transport for both voice and voicemail applications while our Airmux radios provide high quality Ethernet and T1/E1 backhaul over microwave links.

    24. Example: WiMAX Backhaul over Ethernet with QoS Assuring consistent level of service across multi-tier networks requires monitoring of both the end-to-end and segment QoS with notification of any degradation in circuit quality (delay, jitter) to the cellular operator. Assuring consistent level of service across multi-tier networks requires monitoring of both the end-to-end and segment QoS with notification of any degradation in circuit quality (delay, jitter) to the cellular operator. On a TDM network any discontinuity is immediately identified and delay is hardly an issue. But since Ethernet is a framed technology, it is not known when to expect a frame, we need to monitor the service from one side to the other. Ethernet OAM helps monitor each service in terms of availability, frame loss and delay. In addition, each service thresholds can be defined to send a trap when the service deviates from the SLA Assuring consistent level of service across multi-tier networks requires monitoring of both the end-to-end and segment QoS with notification of any degradation in circuit quality (delay, jitter) to the cellular operator. Assuring consistent level of service across multi-tier networks requires monitoring of both the end-to-end and segment QoS with notification of any degradation in circuit quality (delay, jitter) to the cellular operator. On a TDM network any discontinuity is immediately identified and delay is hardly an issue. But since Ethernet is a framed technology, it is not known when to expect a frame, we need to monitor the service from one side to the other. Ethernet OAM helps monitor each service in terms of availability, frame loss and delay. In addition, each service thresholds can be defined to send a trap when the service deviates from the SLA

    25. Carrier Ethernet for Mobile Backhaul MEF’s role in enabling Mobile Backhaul infrastructure deployment

    26. Mobile Backhaul Implementation Agreement MEF Mobile Backhaul Standardized services Certification Interoperability UNI Requirements Ethernet OAM (Link OAM and Service OAM) Protection and Fault Recovery Requirements Service Requirements CoS Requirements Service Definitions Synchronization All the requirements in the document are still under discussion. The MEF can not provide any hard requirements for the Mobile Backhaul, but can provider general rules of thumb in most areas.All the requirements in the document are still under discussion. The MEF can not provide any hard requirements for the Mobile Backhaul, but can provider general rules of thumb in most areas.

    27. Today’s Mobile Backhaul MEF Use Cases

    28. Packet offload over carrier Ethernet – 1a Overlay MEN does bandwidth offloading onto Ethernet services Legacy network continues to transport voice and deliver timing

    29. Emulation over Carrier Ethernet – 1b

    30. RAN dual stack – 2a

    31. Full Ethernet BTS and Transport Network– 2b

    32. Separation of Voice and HSPA Data over Ethernet / IP Use case 1ab and 2ab example

    33. MEF 18 Certification for Mobile Backhaul CES MEF 18 provides standard testing of Circuit Emulation Services over Ethernet Speeds implementation and enables full inter-operability 334 ground breaking tests and certifications in the suite MEF 18 has many applications but is key to Mobile Backhaul migration strategies Lead by strong service provider demand Industry first impairment testing brings first test of emulation of clock recovery Raise the level of confidence that clock recovery will meet the stringent requirements of mobile backhaul.

    34. 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

    35. Panel Members – Q&A

    36. Thank You

More Related