Category Archives: Release 12

LTE-A in Unlicensed Band (LTE-U)

Qualcomm has recently floated the idea of deploying LTE in unlicensed bands, particularly focusing on the 5GHz band, which is currently used mostly for WiFi. According to a document (RP-131635) submitted to the upcoming 3GPP plenary meeting, the proposal is to deploy LTE as Supplemental Downlink (SDL) in 5725-5850 MHz in USA, with the PCell (Primary Cell) always operating on a carrier in a licensed band. Verizon has also submitted a Work Item Proposal (RP-131680) to to introduce the new band for SDL usage. There’s also a Study Item proposal from Ericsson (RP-131788) is the rapporteur to study the modifications necessary to the LTE radio.

These documents can be downloaded from the 3GPP FTP site.

In addition, there’s a presentation from Qualcomm on the same topic.

LTE Release 12: Small Cell Enhancements – Higher Layer Aspects

One of the 3GPP Rel-12 Study Items focuses on Small Cell Enhancements.from the perspective of higher layers. There are 3 scenarios under consideration:

Scenario 1:  Macro and small cells on the same carrier frequency, connected via non-ideal backhaul.

Scenario 2: Macro and small cells on different carrier frequencies, connected via non-ideal backhaul.

Scenario 3: Only small cells on one or more carrier frequencies, connected via non-ideal backhaul.

The challenges posed by these scenarios are summarized in the table below.


To address these challenges, 3GPP’s RAN Working Group 2, is currently working towards a set of solutions, with the following design goals in mind:


The idea of ‘dual connectivity’ has more or less been accepted as the way forward. This term refers to operation where a given UE consumes radio resources provided by at least two different network points connected with non-ideal backhaul. Each eNB involved in dual connectivity for a UE may assume different roles and these roles do not necessarily depend on the eNB’s power class and can vary among UEs.

Within the dual-connectivity framework, there are two potential solutions being discussed:

Inter-node radio resource aggregation: This solution is aimed at improving per-user throughput by aggregating radio resources in more than one eNB for user plane data transmission.ImageRRC Diversity: This solution is targeted at improving mobility robustness by transmitting handover related RRC signalling could from/to a potential target cell. The RRC diversity scheme could also be applied for handovers from the macro to pico cells, between macro or between pico cells.


Further details of these solutions can be found in TR36.842.

LTE Release-12 and Beyond

While current LTE deployments are mostly based on Rel. 8/9, work is ongoing in 3GPP on Release 12. The July issue of IEEE Communications Magazine has a nice article which provides an overview of the key features being developed in Release 12. It can be viewed online via the IEEE Digital Library at

Solution 3: RAN-controlled Network Selection and Traffic Steering

The key difference with respect to Solution 1 is that the 3GPP RAN decides when a UE should connect to the WLAN and how traffic should be steered to/from 3GPP network. The figure below illustrates the process.

Picture1As in Solution 1, the UE transfers its WLAN interworking capability to RAN at the time of connection setup. The following procedure is followed afterwards:

  • RAN configures a measurement for WLAN. It may provide measurement object & reporting configuration if UE supports WLAN interworking and RAN wants to interwork with WLAN
  • After receiving measurement configuration, the UE measures WLAN. If there is a WLAN that satisfies the reporting configuration, the UE reports the measured result to RAN.
  • If RAN finds that offloading is necessary  & the reported WLAN is appropriate, it transmits offloading command to steer traffic from RAN to WLAN. Alternatively, if RAN finds that the WLAN is not appropriate for offloading any more, it transmits reverse offloading command.
  • When the UE receives the forward offloading command, it connects to the indicated WLAN and continues data transmission and reception with it. If bearer info is also received from RAN, UE continues data transmission/reception of the bearer with WLAN
  • When a reverse offloading command is received by the UE, it continues data transmission/reception with RAN instead of using WLAN.

Solution 1: RAN-assisted Network Selection and Traffic Steering

This solution relies on the RAN providing relevant information that may be used by a UE to decide:

1. If and when to connect/disconnect to/from an available WLAN

2. Steer one or more data flows from/to 3GPP RAN to/from WLAN

The UE is assumed to receive network selection and traffic steering rules and/or polices either via ANDSF or user preferences or operator provisioning. The solution can be applied in both RCC_IDLE and RRC_CONNECTED modes. More specifically, the figure below, taken from doc R2-132055, illustrates the procedure when UE is idle mode.

ImageThe steps involved in this procedure are as follows:

  • When the UE establishes RRC connection with 3GPP RAN, it transfers interworking capability info to the network
  • If the UE has indicated support for WLAN interworking and 3GPP RAN also wants to interwork with WLAN, the latter may provide assistance info to UE via dedicated signalling at the time of RRC connection release.
  • In addition, RAN may broadcast System Information which includes assistance info. If UE has valid assistance information provided through dedicated signalling previously, it ignores the related broadcast information.
  • UE selects the access network based on information provided by RAN, information obtained from WLAN and rules/policies/preferences.

Note that no traffic steering happens in this case as the UE is in IDLE mode. The procedure is similar when the UE is in CONNECTED mode, as shown below.Image

  • As in the previous case, the UE transfers its interworking capability information to RAN at the time of RRC Connection establishment.
  • While the UE is connected to RAN, it receives assistance information from RAN through dedicated signalling, if the UE supports WLAN interworking and RAN wants to interwork with WLAN.
  • UE selects the access network based on the assistance info provided by RAN, acquired information from WLAN and rules.

In both cases, the assistance information may include the following:

  • 3GPP Network load
  • Resources allocation for UE
  • WLAN thresholds (e.g. RSSI)
  • RAN thresholds (e.g. RSRP)

3GPP-WLAN Interworking – Part III : Access Network Selection and Traffic Steering

At the recent RAN2 meeting (May 20-24, 2013), the discussions focused mainly on access network selection and traffic steering in 3GPP-WLAN interworking scenarios. The proposed solutions addressed the following cases:

UE is within UTRAN/E-UTRAN coverage, is using 3GPP and goes into WLAN AP coverage

B.  UE is within UTRAN/E-UTRAN and WLAN coverage, is using WLAN and goes out of WLAN AP coverage

C.  UE is within the coverage area of both, UE using WLAN, all or a subset of the UE’s traffic should be routed via UTRAN/E-UTRAN instead

D.  UE is within the coverage area of both, UE using UTRAN/E-UTRAN,  all or a subset of the UE’s traffic should be routed via WLAN instead

E.   UE using both accesses and should be connected to only one (WLAN or UTRAN/E-UTRAN) or some traffic should be moved to the other access

In broad terms, there are 3 solutions currently being discussed in RAN2:

Solution 1: 3GPP RAN provides UE with information that assists in network selection and traffic steering. This information may be combined with ANDSF rules and/or UE configuration to decide whether to connect to a WLAN, if one is available, and to steer one or more flows to the WiFi link.

Solution 2: 3GPP RAN provides the access network selection parameters, based on which the UE decides when to connect to a WLAN. These parameters may includes thresholds, priorities, rules etc.

Solution 3: UE reports available WLAN(s) based on measurements configured by 3GPP RAN and the decisions related to WLAN selection as well as traffic steering are taken by the network.

In the next post, I will discuss each of these solutions in more detail.