Voice Over LTE – VoLTE Signalling Call Flow

Voice over LTEVoLTE is the technology to provide voice and video services over LTE all PS network. As LTE is a complete PS network VoLTE need to use IMS in EPS core to handle voice and video related services. Apart from IMS, VoLTE enabled UE (User Equipment) use MME (Mobility Management Entity) to authenticate a UE prior to entering the EPC. MME need to communicate with HSS which in turn communicate with AAA server for authentication, authorization and accounting purposes.

After authentication procedure is over a control signalling is used to create a default bearer to internet. MME then select the appropriate SGW (Serving Gateway) to connect to eNodeB.

Voice over LTE (VoLTE)- Signalling

SIP is the most important protocol in VoLTE communication. It is in charge of all signalling required to setup, manage and terminate the session. UDP (User Datagram Protocol ) protocol is used for transmission of actual VoLTE user data packets.

This LTE video tutorial describes:

  • Authentication of UE in VoLTE call
  • How control signalling is used to create default bearer in VoLTE
  • How default internet bearer is established
  • Control signalling to create default IMS bearer.
  • Default IMS bearer establishment.
  • IMS registration via SIP
  • Notify change of state
  • Actual VoLTE call data packet transmission on UDP

VoLTE Signalling Call Flow – Video Tutorial

Multi-Carrier Heterogenous Networks (HetNet) Performance

Heterogeneous networks (HetNets), consisting of Macro NodeBs (macros) and low power Pico NodeBs (picos), can increase system capacity by offloading some users to the picos. However, this offloading may be limited due to intercell interference from macros to picos that reduces their coverage. HSPA Multi-carrier HetNets allow the use of range expansion techniques to achieve more offloading, such as power reduction from the macros on one carrier. “Performance Analysis of HSPA Multi-Carrier Heterogenous Networks” white paper provides a system level analysis of the gain provided by power reduction on one carrier of the macros in a HetNet environment. As the interference from the macros is reduced, more capacity offloading to picos occurs and higher system capacity can be achieved. By considering cell biasing in serving cell selection, further gains can be observed.

VoLTE Battery Issue and Solution from ST Ericsson

VoLTE was in bad limelight because of it’s battery performance issues. I wrote an article how VoLTE will consume twice battery than traditional voice calls. The study was done by Metrico Wireless using LG Connect 4G on MetroPCS network.

ST Ericsson provided a new white paper which clarifies all doubts around VoLTE. Without VoLTE CDMA/LTE systems suffer a severe penalty in that they use a concept called Simultaneous Voice and LTE – SVLTE. This means that during a voice call, both the CDMA radio and the LTE radio are in full operation. The consequence of this is clearly visible in the Metrico data, which also shows the obvious fact that VoLTE+LTE consume less power than CDMA+LTE.

Volte Battery Test (LTE vs CDMA)

But LTE Networks with 3GPP based legacy systems like UMTS and GSM does not suffer from these issue. Also CDMA + LTE solutions based on fall-back schemes do not have this problem.

ST Ericsson provided many way to tackle this issue using better software architecture, optimizing radio hardware and transmission protocols.

What do you think about these solutions? Will these really help in solving battery issue in VoLTE?

Here is the the ST Ericsson white paper on VoLTE battery problem and solution for the problem.

LTE Logical Channels

LTE logical channels structure and mapping between logical channels and transport channels.

Logical channels reside between RLC sublayer and MAC sublayer which are layer 2 protocols in LTE protocol stack. Logical channels tells what kind of information is transferred. Logical channels can be broadly divided into two types:

  • Control Channels (for the transfer of control plane information)
  • Traffic Channels (for the transfer of user plane information)

Control Channels

Control channels are use for transferring control plane information. The different control channels in LTE are:

Broadcast Control Channel (BCCH)

BCCH channel is used for transferring system control information. Broadcast Control Channel (BCCH) is a downlink channel.

Paging Control Channel (PCCH)

PCCH is a downlink channel which carries paging information and system information change.

Common Control Channel (CCCH)

Channel for transmitting control information between UEs and network. This channel is used for UEs having no RRC connection with the network.

Multicast Control Channel (MCCH)

A point-to-multipoint downlink channel used for transmitting MBMS control information from the network to the UE, for one or several MTCHs. This channel is only used by UEs that receive or are interested to receive MBMS.

Dedicated Control Channel (DCCH)

DCCH is used when there is RRC Connection. DCCH transfers dedicated control information between UE and network. Dedicated Control Channel (DCCH) is a bidirectional channel.

Traffic Channels

Traffic channels are used to carry user plane information. There are two types of logical traffic channels available in LTE

Dedicated Traffic Channel (DTCH)

DTCH is a bi-directional channel used to transfer user plane information between UE and network.

Multicast Traffic Channel (MTCH)

A point-to-multipoint downlink channel for transmitting traffic data from the network to the UE. This channel is only used by UEs that receive MBMS.

Mapping between logical channels and transport channels

Mapping in uplink

LTE Uplink Logical Channel mapping

Mapping in downlink

LTE Downlink Logical Channel Mapping

LTE RLC – Radio Link Control Protocol

RLC is a layer 2 protocol in LTE UE and NodeB. RLC – Radio Link Control protocol is a data link layer protocol. RRC (Radio Resource Control) is generally controls RLC configuration via RRC-RLC SAP. A RLC entity receives/delivers RLC SDUs from/to upper layer and ends/receives RLC PDUs to/from its peer RLC entity via lower layers.

If RLC entity configured at the eNB, there is a peer RLC entity configured at the UE and vice versa.

3GPP LTE RLC UE and NodeB Stack

An RLC entity can be configured to perform data transfer in one of the following three modes:

Transparent Mode (TM)

A RLC TM entity is with can be transmitter or receiver. That means when acting as a transmitter the transparent mode RLC entity receives SDUs from upper layer and transmit those to it’s peer RLC TM entity via lower layer.

Similarly the receiving RLC TM entity receives RLC PDUs via lower layer and then pass those to upper layer.

When RLC TM entity acts as a transmitter

  • It should not segment or concatenate the RLC SDUs
  • No header will be included in TMD PDUs

Unacknowledged Mode (UM)

Similar to RLC TM entity RLC UM entity also acts either as a transmitter or receiver. The transmitting RLC UM entity receives SDPs from upper layer and send RLC PDUs to its peer receiving entity via lower layers. Similarly the receiving RLC entity receives RLC PDUs from lower layer and delivers RLC SDUs to upper layer.

Acknowledged Mode (AM)

AM RLC entity can be configured to deliver/receive RLC PDUs through DL/UL DCCH and DL/UL DTCH logical channels.

When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs, it shall:

  • segment and/or concatenate the RLC SDUs so that the AMD PDUs fit within the total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity notified by lower layer.

The transmitting side of an AM RLC entity supports retransmission of RLC data PDUs (ARQ):

  • if the RLC data PDU to be retransmitted does not fit within the total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity notified by lower layer, the AM RLC entity can re-segment the RLC data PDU into AMD PDU segments;
  • the number of re-segmentation is not limited.

When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs received from upper layer or AMD PDU segments from RLC data PDUs to be retransmitted, it shall:

  • include relevant RLC headers in the RLC data PDU.

When the receiving side of an AM RLC entity receives RLC data PDUs, it shall:

  • detect whether or not the RLC data PDUs have been received in duplication, and discard duplicated RLC data PDUs;
  • reorder the RLC data PDUs if they are received out of sequence;
  • detect the loss of RLC data PDUs at lower layers and request retransmissions to its peer AM RLC entity;
  • reassemble RLC SDUs from the reordered RLC data PDUs and deliver the RLC SDUs to upper layer in sequence.

At the time of RLC re-establishment, the receiving side of an AM RLC entity shall:

  • if possible, reassemble RLC SDUs from the RLC data PDUs that are received out of sequence and deliver them to upper layer;
  • discard any remaining RLC data PDUs that could not be reassembled into RLC SDUs;
  • initialize relevant state variables and stop relevant timers.

RLC Functions

  • transfer of upper layer PDUs;
  • error correction through ARQ (only for AM data transfer);
  • concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer);
  • re-segmentation of RLC data PDUs (only for AM data transfer);
  • reordering of RLC data PDUs (only for UM and AM data transfer);
  • duplicate detection (only for UM and AM data transfer);
  • RLC SDU discard (only for UM and AM data transfer);
  • RLC re-establishment;
  • Protocol error detection (only for AM data transfer).

 

RLC PDU (Protocol Data Unit)

RLC PDUs can be categorized into RLC data PDUs and RLC control PDUs.

  • RLC data PDUs are used by TM, UM and AM RLC entities to transfer upper layer PDUs (i.e. RLC SDUs).
  • RLC control PDUs are used by AM RLC entity to perform ARQ procedures.

I added tutorials on encoding and decoding of RLC TM and UM PDUs in earlier tutorials.

LTE RSRP – Reference Signal Received Power

What is RSRP (Reference Signal Received Power ) in LTE? When RSRP is is applicable in LTE systems?

Reference signal received power (RSRP), is defined as the linear average over the power contributions of the resource elements that carry cell-specific reference signals within the considered measurement frequency bandwidth.

For RSRP determination the cell-specific reference signals R0 shall be used. If the UE can reliably detect that R1 is available it may use R1 in addition to R0 to determine RSRP.

The reference point for the RSRP shall be the antenna connector of the UE. If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding RSRP of any of the individual diversity branches.

LTE Cell-specific reference signals

Mapping of downlink reference signals

When is RSRP (Reference Signal Received Power) applicable?

RSRP is applicable in the following cases

  • RRC_IDLE intra-frequency
  • RRC_IDLE inter-frequency
  • RRC_CONNECTED intra-frequency
  • RRC_CONNECTED inter-frequency

The number of resource elements within the considered measurement frequency bandwidth and within the measurement period that are used by the UE to determine RSRP is left up to the UE implementation with the limitation that corresponding measurement accuracy requirements have to be fulfilled.

The power per resource element is determined from the energy received during the useful part of the symbol, excluding the CP.

LTE RSCP – Received Signal Code Power

What is RSCP (Received Signal Code Power) in LTE? When is RSCP applicable in LTE system?

UTRA FDD CPICH RSCP

RSCP (Received Signal Code Power), the received power on one code measured on the Primary CPICH. The reference point for the RSCP shall be the antenna connector of the UE. If Tx diversity is applied on the Primary CPICH the received code power from each antenna shall be separately measured and summed together to a total received code power on the Primary CPICH. If receiver diversity is in use by the UE, the reported value shall not be lower than the corresponding CPICH RSCP of any of the individual receive antenna branches.

UTRA TDD P-CCPCH RSCP

Received Signal Code Power, the received power on P-CCPCH of a neighbour UTRA TDD cell.
The reference point for the RSCP shall be the antenna connector of the UE.

RSCP is only valid in UTRA cells and used during RRC_IDLE Inter-RAT or RRC_CONNECTED Inter-Rat state, i.e during LTE to UMTS reselection or handover.