Light Reading Mobile – Telecom News, Analysis, Events, and Research

Huawei Press Releases  

LTEHaul Bridges the Backhaul Divide

February 27, 2013 |
2012 was a watershed year for LTE commercialization. By its end, 145 commercial LTE networks were in operation, covering some 43.7 million subscriptions, according to the Global mobile Suppliers Association (GSA). These growing networks bear revolutionary services for a diverse field of scenarios, posing high requirements on backhaul. New technologies are emerging as the LTE and LTE-A standards go commercial, including coordinated multiple point (CoMP) and evolved multimedia broadcast multicast service (eMBMS), both defined in 3GPP R11. CoMP is used to mitigate inter-cell interference and improve cell capacity, while also enhancing network performance through coordination of both transmission and reception among multiple eNodeBs; eMBMS provides point-to-multipoint interfaces, through which operators can use their existing spectrum and mobile networks more efficiently so that high-quality/ bandwidth-hungry services are intact. With legacy GSM/UMTS backhaul, all base station data first converges at the BSC/RNC nodes for further processing, and this makes for a physical division between the backhaul and core networks. In addition, the capacity for these base stations has a general limit of 42Mbps, which lags behind user demand for data services. LTE/LTE-A, with its greater bandwidth and more integrated architecture, is solving these problems.

New features of LTEHaul

To meet the booming demand for throughput (150Mbps per eNodeB in a certain case), LTE must operate at higher frequency bands (2.6/3.5GHz) in dense urban areas and offer a peak rate ten times that for 3G. However, to achieve the same coverage, an operator needs ten times as many eNodeBs as base stations/NodeBs, while a high-frequency radio system must encompass hotspots and blind spots, creating additional FrontHaul requirements.

LTEHaul architecture has two major differences from GSM/UMTS backhaul (Figure 1). First, LTE FrontHaul is located at the lower network layer after backhaul, and second, the BSC/RNC nodes are no longer present, enabling a backhaul-core connection.

E2E LTEHaul architecture
Figure 1: E2E LTEHaul architecture

Indoor & outdoor hotspot coverage

With GSM/UMTS, FrontHaul is normally located at a lower network layer, but with LTEHaul, it is the last mile, covering indoor (Wi-Fi & small cell) and outdoor hotspots.

Wi-Fi indoor FrontHaul is typically required at mobile oases (hotels, cafes, airports). Supplemented by GSM/UMTS, this access scenario is characterized by low mobility, a large amount of data, and no voice. As access media vary (P2P fiber/copper/PON) and power supply for RRUs is required, the FrontHaul in this case must be media-agnostic and enable Power over Ethernet (PoE) functionality. Furthermore, bearer devices should be small, easy-to-install, energy efficient, and maintenance free, so that OPEX is held in check.

Small cell indoor FrontHaul is primarily used for shopping malls. It is characterized by high mobility and a large amount of voice and data over a broad area. To ensure quick service provisioning and high-quality service experience, the FrontHaul network should allow remote RRU power supply, hierarchical quality of service (HQoS), and access by any medium, while bearer devices should be easy-to-install, maintenance-free, and plug-and-play to reduce costs. Small cell outdoor FrontHaul applies to crowded outdoor scenarios, such as bustling streets, city plazas, and open-air cafes. It is characterized by heavy voice and data traffic, and its challenges include site acquisition and access diversity. The access media in place must be leveraged, and bearer devices should be ecofriendly, have a minimal footprint (walls and poles work well) and feature surge protection and resistance to the elements. If fixed access is unavailable, full outdoor microwave can be used, though it should be deployed (with parabolic antennas for rapid focusing) and commissioned (USB configuration) quickly, while being easy to maintain.

Converged CSG backhaul

For a GSM/UMTS network, a cell site gateway (CSG) will serve only one base station, while an LTE CSG aggregates traffic from various hotspots. Taken on its own terms, this sounds great, but it calls for measures that ensure greater system reliability, including carrier-grade 1+1 10GE ring protection, 1+1 backup for system control units, and multi-node failure protection.

VoLTE’s commercial maturation is accelerating GSM/UMTS spectrum refarming, and this poses a challenge to network scalability. For a blade RRU solution that supports multi-band & multi-mode refarming (seven bands, four modes), the CSG nodes must have six service slots and a large switching capacity (120Gbps), as well as smooth LTE-A evolution capability (from 400 to 1000Mbps per eNodeB). New VoLTE services also require CSG node support for hierarchical QoS, so that multi-service scheduling and quality are guaranteed. Since they will share the same cabinet as the BBU, a CSG device should also share the power and network management system (NMS), all while being plug & play, so that base station deployment stays timely.

ASG backhaul

As traffic balloons and base stations move to IP, FMC-enabled nodes for IP backhaul are migrating downstream to the legacy transmission equipment rooms that housed OLT/SDH devices. Cabinets in these rooms are typically 300mm deep and accommodate equipment that converge fixed and mobile traffic, so an aggregation site gateway (ASG) must be co-sited with said OLT/SDH devices, sharing the cabinet, power supply, and NMS so that network deployment/cost is more efficient. To enable FMC service backhaul, ASG nodes should also feature a large capacity (over 480Gbps) and integration of BRAS/SR/VPN PE functionality, all while being ready to support new services (such as eMBMS multicast/L3/IPv6).

The increasing scale and complexity of LTEHaul poses a challenge to O&M. As a solution, ASG nodes can aggregate traffic from macro & small sites while supporting centralized & intelligent management of remote modules, through which operators can simplify network architecture, configuration, and O&M.

Core – E2E service provisioning and O&M

As stated previously, BSCs/RNCs divide the backhaul and core layers in a GSM/UMTS network, and yet this boundary is fading with LTE, as BSC/RNC functionality is distributed across eNodeBs and evolved packet cores (EPCs). In this context, E2E service provisioning, protection switching, and fault diagnosis for eNodeBs and EPCs need to be redefined. Traditional back-to-back backhaul fails to deliver 50ms cross autonomous system (AS) protection switching, lacks of E2E troubleshooting, and prolongs service delivery, so a ‘PE Borderless MPLS + Hierarchical VPN (HVPV)’ solution is needed.

Numerous mobile operators are exploring LTE/LTE-A enterprise virtual private network (VPN) services. PE Borderless MPLS + HVPN for LTEHaul would be an optimal choice as it supports sub-50ms cross-AS protection switching and is easily scalable between eNodeBs and EPCs. With E2E service configuration and fault diagnostics, this solution offers efficient service provisioning and troubleshooting for enterprise VPN services.

Large-scale commercial deployment of LTE/LTE-A is spawning service opportunities as well as challenges to mobile backhaul. Being well suited to the aforementioned coverage scenarios, Huawei’s LTEHaul solution helps bridge the backhaul divide, while enabling smooth evolution to LTE-A.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
White Papers SPONSORED CONTENT
Featured