0% found this document useful (0 votes)
175 views28 pages

MPLS MobileBackhaul

Backhaul is able to transport mobile data from the end user to the internet, mobile networks and traditional telephone networks. Mobile operators are facing a significant spike in bandwidth demands in the backhaul. To address the problem operators are migrating from existing separate, legacy ATM and TDM backhaul networks to a more cost-effective, converged, MPLS-enabled infrastructure.

Uploaded by

Beny D Setyawan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
175 views28 pages

MPLS MobileBackhaul

Backhaul is able to transport mobile data from the end user to the internet, mobile networks and traditional telephone networks. Mobile operators are facing a significant spike in bandwidth demands in the backhaul. To address the problem operators are migrating from existing separate, legacy ATM and TDM backhaul networks to a more cost-effective, converged, MPLS-enabled infrastructure.

Uploaded by

Beny D Setyawan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 28

Use of MPLS in

Mobile Backhaul Networks


Introduction
z Backhaul plays a vital role in mobile networks by acting as the link
between Radio Access Network (RAN) equipment (Eg: radio
basestation) and the mobile backbone network.
– This means that backhaul is able to transport mobile data from the end
user to the internet (or similar network), mobile networks and traditional
telephone networks.
z The rapidly evolving telecoms marketplace has meant that mobile
operators are facing a significant spike in bandwidth demands in the
backhaul due to-
– The proliferation of 3G-based data services and
– The emergence of high-speed air interface enhancements such as High
Speed Packet Access (HSPA).
z At the same time, backhaul network operators are being required to
significantly reduce operational costs in order to compensate for
declining Average Revenue Per User (ARPU) and to compete with a
host of new competitors and technologies.
z Operators are also required to protect (or sufficiently emulate) core
legacy services such as voice, which still account for a substantial
share of revenue.
Addressing the bottleneck
z In this new situation backhaul networks with many cell sites
have become the “bottleneck” offering insufficient capacity to
support higher bandwidths and often expensive to upgrade.
z To address the problem operators are migrating from existing
separate, legacy ATM and TDM backhauling networks to a
more cost-effective, converged, MPLS-enabled, and multi-
purpose infrastructure.
z In addition to reducing operational costs, MPLS-based
networks will also lay the foundations for the delivery of next
generation mobile services, such as location-based services,
mobile gaming and mobile TV, and for the use of future
technologies such as Long Term Evolution (LTE) and mobile
WiMAX.
z Ultimately, this fully consolidated network will be able to handle
many different types of traffic on a single cell site, enabling the
operator to offer many different services to many different types
of customer.
MPLS Mobile Backhaul Initiative

z MPLS Mobile Backhaul Initiative (MMBI) tackles


these backhaul challenges.
z The initiative aims to leverage the benefits of MPLS
technology in the backhaul by providing a framework
for a single MPLS aggregation/backhaul network that
is flexible, scalable and economical.
z This presentation outlines the market dynamics that
are driving the need to deploy MPLS technology in
Radio Access Network (RAN) backhaul and provides
a brief overview of the MMBI.
Market Trends
Traffic Increasing but Revenues Shrinking

z The combination of rising traffic requirements coupled with declining


revenues is a key motivation for operators migrating RANs to a
converged, packed-based architecture
z MPLS has been globally deployed in these types of networks and has
been an important element in creating an environment for the delivery
of new data services
z As these packet-based networks grow in popularity, MPLS must now
also be extended into to the backhaul
Total Cell Sites & Mean Subscribers
per Cell Site (2003-2013)
Market Trends & Challenges

z Third-generation mobile networks have become a


reality.
– The total number of 3G subscribers stood at around 614
Million at the end of 2007 and the number is forecasted to
grow at a CAGR of 34% in near future.
– Growing at a CAGR of over 27%, 3G market for mobile
handsets will supersede 475 Million units (including HSDPA
handsets) by 2010.
– The growing 3G market is expected to fuel demand for 3G-
based Mobile TV market with subscriber growth forecasted
at a CAGR of nearly 48% by 2012.
– Introduction of femtocells is expected to result in mass
adoption of 3G technology across the world.

“3G Market Forecasts to 2010”, Market and Research 2008


Issues:
Traditional Backhaul-Expensive

z Mobile operators are generating revenues from a range of new


“next generation” data services that are designed to generate
revenues in addition to those from legacy voice services.
z However, these new 3G-based services require a substantial
increase in bandwidth, which will in turn lead to greater mobile
backhaul costs.
z It is estimated that backhaul can account for as much as 30%
of a mobile operator’s operating costs (Opex)
(source: Yankee Group, 2005)
z If mobile operators were to expand the backhaul network to
meet these new bandwidth requirements in the traditional
manner, the move to 3G could represent a significant increase
in required bandwidth and associated opex.
Issues cont.
More sophisticated requirements

z Backhaul needs to be able to handle a range of new


functionality, including-
– Quality of Service (QoS) and
– Resiliency management.
z These new elements will become increasingly
important as mobile operators migrate towards
packet-based backhaul networks.
z Mobile backhaul networks must support many
different generations of technologies simultaneously.
– Must protect existing legacy technology investments for
some years.
– But need a backhaul strategy that is “future-proof” and will
be able to support a new generation of networks and
access technologies such as LTE.
Issues cont.
Access & Aggregation Diverse Traffic

z The access and aggregation networks are used for more than
just mobile backhaul and it increasingly being used to carry
traffic for more than one mobile operator.
z This requires methods of separating and securing multiple
operator traffic while maintaining service level agreements
(SLAs).
– We estimate that as many as three-quarters of 2G and 3G cell
sites are co-located.
z The access and aggregation networks can be used to host
multiple services as well as multiple operators.
z An ISP that has an IP/MPLS based network could provide
services such as-
– IPTV
– broadband access and enterprise VPN
– as well as mobile backhaul services, generating further value from
the network.
MMBI meets the needs
Flexible * Scalable * Cost Effective
Backhaul Infrastructure Requirements

z The new backhaul infrastructure must therefore meet


three main criteria; it must be-
– Flexible
z To support both legacy and IP services
– Scalable
z To support emerging future technologies
– Cost-effective
z To compensate for rising levels of backhaul traffic
z It also needs to be a converged network, which
means the operator does not need to run two
separate networks (leased lines and IP).
Overview
MPLS Mobile Backhaul Initiative

z In 2008, the IP/MPLS Forum, now part of the


Broadband Forum, launched it’s MPLS Mobile
Backhaul Initiative (MMBI).
z MMBI provides a framework for the use of MPLS
technology to bring solutions to transport RAN
backhaul traffic over access, aggregation and core
networks.
z The specification provides possible deployment
scenarios and recommendations on how to deploy
MPLS in each of these scenarios.
z This is a valuable reference guide that allows
vendors and operators to select the appropriate
feature sets for their specific scenario.
What does MMBI address?
z A shared network infrastructure that is able to support (emulate)
existing legacy services (2G, 2.5G) as well as new services
based on 3G and beyond (Eg: HSPA, LTE).
– This will enable a migration path between existing legacy ATM and
TDM backhaul networks to a more cost-effective, converged,
MPLS-enabled, and multi-purpose network.
z The work is independent from the air interface technology
wherever possible but allows for the possibility that some
specific backhaul requirements related to the air interface may
need to be considered.
z Areas covered:
– QoS considerations (Eg; to support specific service types),
– Resiliency capabilities,
– Clocking and synchronization,
– Operations and Maintenance (OAM), and
– Support for various Transport Network Layers (TNLs), LTE and
mobile WiMAX.
Scope of MMBI

Transport network &


Backhaul Transport & Mobile Core Network
RAN
2G Internet
3G 3G PDSN/
4G SGSN
RNC PSN
Access
Network Aggregation Core GGSN
Network Network
Focus Area BSC
for BBF PDN GW
backhaul a GW
2G SGSN 3G MSC CSN WiMAX

Access 2G MSC
Network

RAN
Business Benefits
z MMBI will directly impact mobile operators’ bottom line by-
– Simplifying operations,
– Reducing Operating Expenses (OPEX)
– Leveraging the cost benefits of backhaul technologies such as Ethernet.
– Enabling operators to support “next generation” services such as location-
based services (LBS), mobile IPTV and mobile gaming, and
– Providing flexibility to protect investments in new and emerging
technologies.
z This flexibility works in two ways:
– it will protect radio equipment investment legacy 2G/3G and
– It will be able to be re-used again as mobile operators migrate to future
technologies such as LTE and mobile WiMAX.
z MPLS is an established technology with proven track record for
providing-
– QoS,
– traffic engineering (TE),
– legacy layer 1 and layer 2 emulation (via pseudowires) and
– resiliency features.
z These advantages can be leveraged for use in a wide variety of
network architectures and applications such as Enterprise VPN, IPTV,
mobile backhaul among others.
Why is MMBI uniquely qualified as the
Backhaul solution?
z Amazing flexibility
– Supports both legacy mobile backhaul networks as well as future
technologies such as LTE.
z For example, the same MPLS network infrastructure can be used to carry the
legacy traffic pseudowires, may also be used to carry and provide QoS
guarantees to next generation LTE traffic.
z Investments in MPLS technologies benefit the service provider by making it
“future proof” and still applicable in the fast evolving mobile technology scenarios
(eg: LTE and beyond).
– Deploys on any layer 2 technology capable of supporting MPLS labeled
switching.
– Ideally suited to overcome the scalability limitations of traditional circuit
based technologies such as ATM and TDM.
z MPLS permits support of these technologies using pseudowires to protect
existing investments in legacy equipment. For future IP and Ethernet based
interfaces, it is possible to aggregate traffic over single TE tunnels and provide
differentiated services for this aggregate so that QoS requirements are met while
at the same time providing further improvements in scalability.
– Provides economies of scale.
z Leverages the MPLS network to meet the requirements of not only the diverse
set of mobile backhaul technologies but also to those of other applications, the
MPLS network also.
z This provides significant reduction of capital and operational costs.
Architectural Scenarios
Network Specification Transport Network Speed (approximate)
Layers (TNLs)
GSM/GPRS (2G/2.5G) TDM 56 - 114 Kbps

EDGE (2.5G) TDM 236.8 Kbps – 473.6


Kbps
UMTS /HSDPA/HSUPA R3, R99/R4 ATM ~384 Kbps (uplink) ~ 2
(3G) to 3.1 Mbps (downlink)
R99/R5, R6 ATM

IP

CDMA 1x-RTT (2.5G) IS-2000 HDLC or TDM 144 Kbps)

CDMA 1x EV-DO (3G) IS-856 IP ~ 1.8 Mbps (uplink), ~


3.1 Mbps (downlink)
Mobile WiMAX WiMAX Forum Network IP 50 Mbps
Access Architecture R1.1

Long Term Evolution (4G) R7/R8 IP > 50 Mbps (uplink)


> 100 Mbps (downlink
Architectural Overview

z Network architectures for RAN backhaul in


the IP/MPLS Forum’s MPLS Mobile Backhaul
Initiative are defined for various Transport
Network Layers (TNL) and mobile network
generations.
z These scenarios are grouped as follows and
comprise two basic categories:
– Legacy (TDM, ATM, HDLC) and
– Future (IP/Ethernet).
Legacy Options

z In the legacy environment, RAN equipment-


– Communicates via either TDM or ATM TNLs and
– Are connected with a T1/E1 interface, or with an
Ethernet interface (Fast Ethernet) if TDM or ATM
is encapsulated over Ethernet via IP or MPLS.
– The functionality necessary to transport legacy
traffic over MPLS can be performed either at the
edge node, the access node, the access gateway
or directly in the RAN equipment.
– The HDLC layer features in CDMA 1x-RTT and
covers RAN equipment communicating by means
of HDLC-encoded bit streams.
IP/Ethernet Options

z IP/Ethernet scenarios include:


– In R5 3G, LTE and mobile WiMAX environments, the RAN
equipment interfaces use the IP TNL – either at the Iub
inter-face (for 3G) or on R7/R8 for LTE or mobile WIMAX.
– Mobile traffic over IP TNL can be transported either via
Ethernet pseudowires or regular IP/MPLS TE tunnels over
MMBI’s mobile backhaul network.
– IP termination can take place either at the edge node, the
access node, the access gateway or directly at the RAN
equipment.
z Various deployment scenarios arise depending on
the location (and the extent) of MPLS technology in
the mobile backhaul network and whether it
comprises both the access and aggregation sections
of the network or just the aggregation section.
RAN Equipment Synchronization

z RAN equipment needs to be fully synchronized to a common


reference timing signal to ensure-
– sufficient frequency stability,
– radio framing accuracy and
– handoff control for RF channels.
z Thus the mobile backhaul network needs to support distribution
of frequency from the Radio Network Controller (RNC) to the
RAN equipment.
– Example: in the case where the air-interface is based on Time
Division Duplexing (TDD), the base station clocks must be
synchronized to ensure no overlap of their transmissions within the
TDD frames.
z Ensuring synchronization allows for tighter accuracies and
reduced guard bands thereby ensuring higher capacity.
Clocking and Sync in RAN

BSC
BSC
BTS

1: Radio Framing Mobile Core


Accuracy BTS Network(s)

NodeB
RNC
2 : Handoff
Control 3 : Backhaul
NodeB Transport Reliability

z Synchronization is vital across many elements in the mobile


network
z In the Radio Access Network (RAN), the need is focused in three
principal areas
How does MMBI Address Timing?
z The MMBI outlines the following methods for clock distribution
over an IP/MPLS based backhaul network.
– In RAN equipment with IP TNL (including LTE)
z Packet based methods where the frequency reference is carried over
packets (e.g., based on Network Time Protocol (NTP)) may be used to
deliver frequency to address the frequency stability requirements of
the radio equipment.
– For legacy TNLs, such as TDM and ATM
z Dedicated timing stream implemented using a pseudowire may be
used to carry the reference timing signal from the RNCs to the RAN
equipment both for backhaul transport reliability as well as frequency
stability requirements of the radio equipment
z Other methods for distributing the reference timing signal to the
RAN equipment include:
– Synchronous Ethernet or IEEE 1588 v2
– PDH/SDH transmission mechanisms used in the mobile access
networks.
– GPS is also widely used to support the strict synchronization
requirements of TDD systems
OAM & Resiliency

z A key advantages of MPLS is that it provides a wide selection


of flexible troubleshooting and OAM tools that enable the
deployment of a truly carrier-grade backhaul network.
z These include-
– Fault detection methods to drive protection switching mechanisms
such as MPLS Fast Reroute.
– Fault diagnosis, fault isolation (eg: LSP Ping and LSP traceroute)
and performance monitoring.
– Loopback and connectivity check.
z Examples include VCCV for pseudowire-based MPLS backhaul
solutions and BFD for IP based MPLS backhaul solutions.
z These OAM tools will remain applicable for future LTE mobile
backhaul networks implemented as either IP based or Ethernet
pseudowire based solutions.
– Note: For legacy TNLs and Ethernet pseudowire based solutions,
the MMBI initiative leverages previous specifications by the
IP/MPLS Forum that support interworking between native
Layer1/Layer2 OAM and MPLS OAM.
Conclusion
z MPLS technology in backhaul is the solution to the bottleneck in today’s
mobile network.
– Offers benefits and cost efficiencies in both legacy mobile backhaul and for
future environments based on new technologies such as LTE.
– Protects existing technology investments
– Ensures that the technology will remain sufficiently “future proof” and
scalable.
– New services can be successfully rolled out, while mobile operators are able
to leverage further cost benefits by using an MPLS-based backhaul network
to deliver many non-backhaul services.
z MMBI provides guidelines on the architecture, scenarios and technology
choices for IP/MPLS RAN backhaul within the various network
environments (legacy, IP, converged).
– The MMBI framework is based on the mobile network definitions outlined by
the industry standards organizations (3GPP, 3GPP2, WiMAX Forum etc.)
– The solution is based on MPLS specifications and protocols developed at the
IETF.
– The MMBI initiative is also being coordinated with other mobile backhaul
activities underway at industry organizations such as the Metro Ethernet
Forum (MEF).
For more information
Check out
http://www.broadband-forum.org/technical/ipmplstechspec.php

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy