Académique Documents
Professionnel Documents
Culture Documents
Farhatullah Mohammed
1. Definitions and Benefits
PING PONG HANDOVER: Downlink QPSK, 16QAM and 64QAM
Support:
- Ping-pong handovers occur when the MS is
handed over from one cell to another but is UE can be configured to report CQI (Channel
quickly handed back to the original cell. This Quality Indicator) to assist the eNodeB in
causes unnecessary signalling and can give selecting an appropriate MCS to use for the
an indication of incorrect handover downlink transmissions. Support
parameter settings or a dominance problem QPSK,16QAM and 64QAM modulation in
in the area. DL. eNB selects among QPSK, 16-QAM and
64-QAM schemes in response to the CQI
TDD 20MHz BANDWIDTH: feedback from UE.
- Channel Bandwidth is supported for LTE- Benefits: Operator can dynamically change
TDD with maximum Resource blocks of 100. modulation order according to the downlink
Frame Structure Type 2: channel environment.
Frame structure type 2 is used for LTE-TDD. Uplink QPSK, 16QAM and 64QAM Support
Radio frame structure is same as frame For UL transmissions, the link adaptation
structure type 1, but subframes are timely process is similar to that for DL, with the
multiplexed with a specific DL/UL ratio in a selection of modulation and coding
radio frame. eNB supports uplink-downlink schemes also being under the control of the
configuration. eNB. eNB estimates the supportable uplink
Special Subframe: data rate by channel sounding and selects
appropriate modulation for the result of
The special subframes defined for DL/UL estimated UL channel quality. Support QPSK
switching in frame structure type 2 consist and 16QAM modulation in UL.
of the three fields DwPTS (Downlink Pilot
Timeslot), GP (Guard Period), and UpPTS Benefits: Operator can dynamically change
(Uplink Pilot Timeslot). eNB supports special modulation order according to the downlink
subframe configuration #7 of DwPTS: channel environment.
GP:UpPTS = 10:2:2 for TD-LTE. Cell Specific Reference Signals:
Normal Cyclic Prefix: Cell-specific reference signal
Addition of redundant bits to avoid data loss. (CRS) is transmitted in all DL subframes in a
Normal CP (cyclic prefix) of 4.7us is cell supporting PDSCH transmission. CRS is
appended to each transmitted OFDM transmitted on one or several of antenna
symbols. ports 0 to 3. It is used for both
demodulation and channel
Benefits: Operator can provide LTE service estimation purpose in DL. This CRS is also
without being affected by inter-symbol used for LTE-Advanced UEs to detect
interference In normal cell coverage PCFICH, PHICH, PDCCH, PBCH, and PDSCH.
environment.
Operator Benefits: Operator can provide
End User Benefits: End-user can receive LTE multiple antenna transmission.
service without being affected by inter-
symbol interference In normal cell coverage
environment.
LTE Bible
End User Benefits: LTE user can estimate spans the same bandwidth as the allocated
downlink channel and demodulate control uplink data.
and traffic channel data.
Operator Benefits: eNB can demodulate
Positioning Reference Signal: uplink data and control information by the
channel estimate from this signal.
Positioning reference signals shall only be
transmitted in resource blocks in downlink Sounding Reference Signal:
subframes configured for positioning
reference signal transmission. Positioning Sounding reference signal provides uplink
reference signals for OTDOA, which is one channel quality information as a basis for
of UE Positioning methods. scheduling decisions in the base station. The
UE sends a sounding reference signal in
Operator Benefits: Operator can provide an different parts of the bandwidths where no
OTDOA based location service to LTE user uplink data transmission is available. The
using positioning reference signal. sounding reference signal is transmitted in
the last symbol of the subframe. The
Synchronization Signal: configuration of the sounding signal, e.g.
Synchronization signal is composed of bandwidth, duration and periodicity, are
primary and secondary synchronization given by higher layers.
signals. The synchronization signals always Operator Benefits: eNB can estimate uplink
occupy the 72 sub-carrier (6RBs) of the channel response from receiving this signal.
channel, which make a same cell search
procedure regardless of channel bandwidth. The channel estimate is utilized in next
Primary Synchronization Signal (PSS) uplink scheduling.
detection to obtain the physical layer cell ID
(within a group of three) and slot Random Access Procedure Types:
synchronization. Secondary Synchronization Random Access Procedure are of two types;
Signal (SSS) detection to obtain the Cyclic contention-based and non-contention
Prefix (CP) length, the physical layer cell operation.
group ID and the frame synchronization.
Operator Benefits: eNB support contention
Benefits: Operator can make a time based and contention free operation of
synchronization with LTE UE by using random access procedures. And also, Helps
synchronization signal. in minimizing the chance of collision.
End User Benefits: UE can find out a physical End user Benefits: Contention-free random
cell ID of serving cell by resolving access procedure helps UE minimize the
synchronization signal. chance of collision.
UE can find out frame and slot starting time Variable Number of OFDM Symbols:
by resolving synchronization signal.
The number of resources (OFDM symbols)
Demodulation Reference Signal: used in each sub frame for PDCCH shall be
Demodulation reference signal is used for dynamic based on the requirement of the
channel estimation in the eNodeB receiver CCE (control channel element) by the load
in order to demodulate control and data of control signaling. There shall be
channels. It is located on the 4th symbol in dynamically varying CFI (control format
each slot (for normal cyclic prefix) and indicator) within the range specified in the
standards for different bandwidths.
Farhatullah Mohammed 3
LTE Bible
Operator Benefits: Cell capacity is increased payload required for a particular scenario.
in cases where not all available PDCCH For this motivation, several DCI (Downlink
resource are needed. Control Information) formats are defined in
standard.
End User Benefits: Subscribers may
experience higher throughput in downlink PDSCH Resource Allocation:
in typical scenarios with low load on PDCCH
and high utilization of PDSCH PDSCH resource allocation types 0, 1 and 2
In order to minimize the signalling overhead Operator Benefits: Achieve reliable data
it is therefore desirable that several transmission by sending a message of
different message formats are available, ACK/NACK.
each containing the minimum payload Basic Link Adaption
required for a particular scenario. For this
motivation, several DCI (Downlink Control MCS adaptation based upon channel
Information) formats are defined in information and error statistics.
standard. DCI formats 0 (PUSCH grants), 1
Operator Benefits: Match the transmission
(PDSCH assignments with a single
parameter such as modulation and coding
codeword), 1A (PDSCH assignments using a
scheme (MCS) as well as MIMO
compact format), 2 (PDSCH assignments for
transmission rank and precoding to the
closed-loop MIMO operation), 2A (PDSCH
channel condition on resource allocated by
assignments for open-loop MIMO
the scheduler.
operation).
Serve the best resource allocation under the
Operator Benefits: In order to minimize the
restriction of limited resource pool
signalling overhead it is desirable that
several different message formats are CQI Correction
available, each containing the minimum
Farhatullah Mohammed 4
LTE Bible
CQI correction performs CQI adaptation in In uplink, eNB supports closed loop power
order to compensate possible non-idealities control by providing TPC, Transmit Power
of the link adaptation in LTE. e.g. CQI Commands to UE. eNB also provides open
estimation error of the UE, CQI quantization loop power control parameters for the UE
error. to perform open loop power control based
on the RSRP measurements
Operator Benefits: Enable the better link
adaptation from facilitating this feature Operator Benefits: It can provide the
improvement of performance or the
Enable downlink radio resource scheduling expansion of coverage according to the
to serve the best resource allocation operation environment through Close-loop
Scheduling with QoS Support: power control.
Based on the QoS profile of the user, the End User Benefits: It can prevent the
MAC scheduler will be aware of the unnecessary power consumption of UE and
priority GBR and AMBR requirements of provide the stablization of reception
the users. Accordingly, the scheduler can performance.
prioritize the users, ensure guaranteed bit DL Power Allocation
rate and also control the Maximum
Aggregate Bit rate allowed for the user. Relative PDSCH power for reference symbols
defined by two different parameters: A
Operator Benefits: Operator can differentiate and B.
traffic data according to the QoS class of LTE
user. End-User Benefits: Optimized downlink
power allocation will have an impact on the
End User Benefits: LTE users can be served
performance of an LTE UE.
the better QoS with their priority in the
system. Paging DRX:
Operator Benefits: Exploiting available When Active DRX mode is used, even in RRC
channel knowledge to schedule a UE to Connected state, UE sleeps during inactive
transmit using specific Resource Blocks periods and monitors PDCCH only during
(RBs) in the frequency domain where the certain wake periods. This functionality
channel response is good. improves battery life while UE is in
connected state. This feature includes both
Maximizing radio resource utilization Short DRX and Long DRX.
Power Control End User Benefits: Enabling this feature
results in longer battery life time
Farhatullah Mohammed 5
LTE Bible
IRC Interference Rejection Combining: End User Benefits: Users can perform PLMN
selection and cell selection, then access to a
Receiver supports interference rejection cell within E-UTRAN. Also they can perform
combining based on MMSE criterion. intra-frequency cell reselection.
Operator Benefits: Achieve the better quality
SIB Broadcast(SIB5)
of signal and improve system performance
by cancelling the interference at eNB eNB broadcasts SIB type 5 for Inter-frequency
receiver. cell reselection.
Operator Benefits: Provide improvement in eNB broadcasts SIB type 6 for cell reselection
cell capacity and throughput as UEs with to UTRAN
good channel conditions can benefit from
the multiple streams transmission. End User Benefits: Users can perform cell
reselection from E-UTRAN to UTRAN.
End User Benefits: Served the improved
throughput or reliable communication due SIB Broadcast(SIB7)
to the multiple streams transmission. eNB broadcasts SIB type 7 for cell reselection
2Rx Diversity: to GERAN
MIB & SIB Broadcast(SIB1~4) eNB maintains UE contexts while the UEs are
in RRC_CONNECTED state, and supports
eNB broadcasts MIB and SIB type 1, type 2, Initial Context Setup, UE Context Release
type 3 and type 4 for PLMN selection, cell and Modification according to requests
selection and intra-frequency cell
from MME.
reselection.
Farhatullah Mohammed 6
LTE Bible
Operator Benefits: Operator can maintain UE Overload Start message to eNB with
context for its subscribers in Overload Action IE, then eNB restricts RRC
RRC_CONNECTED state. connection requests towards the
overloaded MME.
E-RAB Setup and Release
Operator Benefits: Signaling load reduction
eNB supports handling of E-RAB allocation, toward overloaded MME.
configuration, maintenance and release.
MME Selection and Load Balancing
Operator Benefits: Operator can provide EPS
bearer service to its subscribers and When eNB receives a RRC connection request
manage E-RAB resources for user data message from a UE, eNB searches and
transport. selects a MME that has served the UE
before. The selection is based on S-TMSI
End User Benefits: Users can obtain EPS information in the message. Otherwise, eNB
bearer service within E-UTRAN. performs load-based MME selection
E-RAB Modification function for a new call that has no S-TMSI
information in the message.
eNB supports handling of E-RAB modification.
This is used for QoS modification of one or Operator Benefits: UE can keep the same
serveral E-RABs. MME while it moves around even in idle
mode, so that the UE can use the same IP
Operator Benefits: Operator can modify E- address.
RAB QoS of ongoing session.
Load is distributed over multiple MMEs.
S1 Interface Management Operator can control relative load of a
specific MME by adjusting Relative MME
S1 interface management procedure is to
Capacity at each MME.
manage the signaling associations between
eNBs, surveying S1 interface and recovering eNB Configuration Update
from errors, i.e. Error indication and Reset
procedures. X2 eNB Configuration Update procedure is to
update application level configuration data
Operator Benefits: manage the signaling needed for two eNBs to interoperate
associations between eNBs, surveying S1 correctly over the X2 interface.
interface and recovering from errors.
Operator Benefits: Update application level
NAS Signaling Transport configuration data needed for two eNBs to
interoperate correctly over the X2 interface.
eNB supports transfer of NAS signaling
messages between MME and UE. RIM Procedure:
End User Benefits: LTE users in idle state can Data Forwarding:
be moving within E-UTRAN. During handover, source eNB forwards PDCP
Intra-eNB Handover: SDUs in sequence to target eNB. Direct data
forwarding is used when a direct path
Intra-eNB handover is mobility control between source eNB and target eNB is
functionality between cells that belong to available. Otherwise indirect data
Farhatullah Mohammed 8
LTE Bible
forwarding is used, where PDCP packets are fails handover to the above target, the UE
delivered to target eNB through S-GW. can re-establish the connection successfully
with the source eNB or other target eNBs
End User Benefits: Users can obtain session that already have the UE context. If the
continuity during handover within E-UTRAN, handover is successful, then the source eNB
with almost no interruption. cancels the handover preparation with the
Inter-Frequency Handover: other candidate target eNBs.
Inter-frequency handover is mobility control End User Benefits: Users can obtain session
functionality between cells that use continuity with fast recovery of ongoing
different frequency band. eNB provides UEs sessions though handover failure has been
with measurement gap information in order experienced during handover.
for the UEs to perform inter frequency
Intra-LTE Redirection:
search. Measurement Gap avoids
scheduling of data for the UE during inter This is intra-LTE mobility functionality
frequency scan periods towards different LTE carriers from serving
carrier.
Operator Benefits: Operator can provide
connected mobility to its subscribers Operator Benefits: Operator can provide
between cells which have a different center connected mobility to its subscribers
frequency. between LTE carriers, though not inter-
frequency handover.
End User Benefits: Users in connected state
can be moving within E-UTRAN, with change Idle Mobility to CDMA Network
of serving cell. (HRPD/1xRTT).
Farhatullah Mohammed 10
LTE Bible
Operator can provide connected mobility to CS fallback to UTRAN enables the delivery of
its subscribers from E-UTRAN to UTRAN. CS domain services when a UE is being
served by the E-UTRAN. When eNB receives
End User Benefits: CSFB indicator from MME, then performs a
Users in connected state can move from E- procedure of PS handover to WCDMA.
UTRAN to UTRAN. Operator Benefits:
CSFB to UTRAN with Redirection without SI Operator can provide CS service to its
CS fallback to UTRAN enables the delivery of subscribers by using legacy CS network
CS domain services when a UE is being (UTRAN)
served by the E-UTRAN. When eNB receives
End User Benefits:
CSFB indicator from MME, then performs a
procedure of redirection without system Users can do a CS call while staying in E-
information. UTRAN, by transition to legacy CS network
(UTRAN)
Operator Benefits:
Capacity based Call Admission Control
Operator can provide CS service to its
subscribers by using legacy CS network Capacity-based CAC determines whether to
(UTRAN) admit or reject the establishment requests
(e.g. idle to active transition, handover,
End User Benefits: additional E-RAB establishment) for new
Users can do a CS call while staying in E- radio bearers, based on maximum number
UTRAN, by transition to legacy CS network of calls and bearers supported by
(UTRAN) eNodeB/Sector. New calls are allowed only
if the pre-configured maximum number of
CSFB to UTRAN with Redirection with SI calls and bearers allowed for that sector
and for that eNB are not exceeded. In case
CS fallback to UTRAN enables the delivery of
of no resources, emergency calls are
CS domain services when a UE is being
allowed by preempting existing calls.
served by the E-UTRAN. When eNB receives
CSFB indicator from MME, then performs a Operator Benefits:
procedure of redirection with system
information. By limiting the maximum number UEs or
bearers per cell and per eNB, considering
Operator Benefits: radio and backhaul bandwidth, operator
can control the minimum QoS level
Operator can provide CS service to its
provided for UEs.
subscribers by using legacy CS network
(UTRAN) Operator can protect the system from being
shutdown due to overload or congestion
End User Benefits:
QoS based Call Admission Control
Users can do a CS call while staying in E-
UTRAN, by transition to legacy CS network QoS-based CAC determines whether the eNB
(UTRAN) accepts a new bearer based on the current
resource utilization and the QoS
CSFB to UTRAN with PS Handover
requirements of the new bearer.
Operator Benefits:
Farhatullah Mohammed 11
LTE Bible
Operator can provide QoS guaranteed Operator Benefits:
service to UEs.
Operator can reduce the amount of
Operator can configure how much incoming calls per call type.
resources(PRB, backhaul bandwidth,
number of GBR bearers) can be used for AM, UM and TM Data Transfer at RLC Layer:
GBR services. eNB supports three different data transfer
modes at RLC layer; Acknowledged
Preemption
Mode(AM), Unacknowledged Mode(UM)
In case of no resource available, eNB admits a and Transparent Mode(TM). TM is used to
new bearer by preempting existing bearers. transfer RRC signaling messages without
The decision is based on ARP (Allocation RLC overhead. AM, which allows
and Retention Priority) information of new retransmission, is used for reliable data
bearer(s) and existing bearer(s). transfer and UM is used for delay
sensitive data transfer. Operator can
Operator Benefits: configure a transfer mode AM or UM per
Operator can provide UEs with QCI.
differentiated service based on service or RLC AM provides a reliable data transfer
based on UE class. between eNB and UE.
Operator can design a high-priority service RLC UM allows a simple data transfer for
which is always available even in network
delay sensitive packets.
congestion.
RLC TM removes RLC overhead to save radio
Cell Barring resources.
When eNB is overloaded or a cell is used for
Header Compression ROHCv1(RTP, UDP, IP)
testing, operator can configure eNB to
transmit cell barring message via BCCH(SIB eNB and UE compress the IP header part of
type1). Accordingly, UEs will not camp on user data packets for transmission over the
the cell but test UEs can access. air. The compression algorithm is
RoHCv1(Robust Header Compression)
Operator Benefits: defined in IETF RFC3095 and other related
Operator can prohibit UEs from camping on RFCs. RoHC Profiles 0,1,2 and 4 are
a specific cell, which enables operator to supported.
test the cell for the commissioning of base Operator Benefits:
stations without any interference of
commercial UEs. eNB increases user data throughput by
applying RoHC to user data transmitted
Access Class Barring over the radio link.
In order to limit UE's access to a cell, operator When this feature is enabled for VoLTE, eNB
can manually configure the access class can accommodate more VoLTE users at the
barring information via LSM. eNB broadcast same time.
this information in SIB type 2 message.
Operator can control how many UEs to be End User Benefits:
allowed and how long time period it is valid
and which type of UE behaviors are UE can enhance throughput.
restricted. Integrity Protection: Null/SNOW3G/AES
Farhatullah Mohammed 12
LTE Bible
Control plane data integrity protection using Operator can provide different user classes
security algorithms between eNB and UE. for different quality of services.
Sensitive parts of the boot-up process shall UE can receive a customized network
be executed with the help of the secure service that is suitable to a specific
environment. application.
Farhatullah Mohammed 13
LTE Bible
eNB reserves radio resource to support Operator can provide a UE with 8 different
GBR(Guaranteed Bit Rate), and eNB limits kind of services at the same time, where
the throughput not to exceed each service has different QoS
MBR(Maximum Bit Rate). For this, QoS characteristics such as QCI or ARP.
based call admission control and QoS aware
scheduling algorithm are used. GBR and End User Benefits:
MBR are bearer associated parameters and A UE may have maximum 8 different kind of
MME sends eNB these parameters during E- bearers at the same time. Each bearer has
RAB setup or modification procedure. different QoS characteristics such as QCI or
Operator Benefits: ARP. This ensures better user experience
and fair allocation of radio resources to UE
Operator can provide high-quality QoS
QCI-based Throughput Differentiation for
services by using GBR bearers.
Non-GBR Bearers
End User Benefits:
Operator can configure "weight factor" for
UEs that connect a GBR bearer can achieve each different Non-GBR QCIs. Then, Non-
at least the guaranteed bit rate that system GBR bearers can achieve throughput in
allows even in cass of congestion. proportion to the ratio of weight factor
between them. This takes effect only in case
By configuring MBR, operator can prevent of resource limitation. When there are
GBR UEs from overusing data and enough resources, each bearers are able to
monopolizing radio resources. transmit all of its own data.
Efficient usage of the radio resources Operator Benefits:
UE-AMBR Support Operator can support differentiated
eNB limits the total bit rate(UE-AMBR) that a throughput for non-GBR OCI. Thus ithis
UE can achieve through its non-GBR feature enable an operator to implement
bearers. MME sends eNB UE-AMBR various accounting plan according to QoS
parameter during UE Context Setup or (even for the same service).
Modification procedure (For example, normal download vs. high
Operator Benefits: speed download, normal video streaming vs.
HD video streaming)
By controlling UE-AMBR, operator can
prevent a UE from overusing data over Non- End User Benefits:
GBR bearers and monopolizing radio User can enjoy premium service with fast
resources. speed in network congestion state
Operator can differentiate subscribers by
Load Balancing between Carriers
setting UE-AMBR differently per user
classes. In the LTE network with multiple carriers, the
load balancing algorithm selects UEs from a
Max 8 Bearers per UE high-loaded carrier and hands them over
eNB supports up to 8 data bearers for a UE, to a co-located and low-loaded carrier. The
including default and dedicated bearers UE selection algorithm is designed to
regardless of their resource types guarantee QoS after handover to another
carrier.
Operator Benefits:
Farhatullah Mohammed 14
LTE Bible
Operator Benefits: This feature distributes the amount of traffic
on multiple carriers and provide even QoS
This feature distributes the amount of traffic on each carrier.
on multiple carriers and provide even QoS
on each carrier. SPID based Dedicted Priority SPID based
Dedicted Priority SPID based Dedicted
End User Benefits: Priority
The bad QoE due to overload will be eNB supports dedicated signaling with cell
reduced reselection priorities based on SPID 254,
Load Balancing between Sectors (Mobility 255 and 256.
Load Balancing)
Operator Benefits:
Load balancing within an intra-carrier occurs Operator can control idle mode camping
between cells of intra-eNB or inter-eNB.
RAT and carriers of a UE based on absolute
UEs in the boarder area are selected and priorities determined by subscription
handed over to the low-loaded neighbor information.
cells. The load balancing algorithm
considers serving/target cells' signal Load Distribution over Backhaul Links
strength at UE. The algorithm is designed to
balance the average per-UE non-GBR When eNB has two backhaul Ethernet links
resources among cells. alive, eNB distribute load between two
links.
Operator Benefits:
Operator Benefits:
This feature relieves the overload state of a
By monitoring one backhaul link, operator
cell.
can monitor all the traffic of a specific UE.
End User Benefits:
DL Flow Control between SGW and eNB
The bad QoE due to overload will be
reduced. When downlink radio link of a cell is
congested due to the limited bandwidth,
Idle UE Distribution eNB sends XOFF message to SGW so that it
stop sending packets in downlink. eNB
In multi-carrier network, Idle UE distribution sends XON message to resume data
algorithm makes idle UEs distributed transmission at SGW. This flow control
over carriers by giving a different priority of scheme works per UE or bearer or QCI.
frequency to each UE via
IdleModeMobilityControlInfo in the Operator Benefits
RRCConnectionRelease message. Idle-to-
active transition UEs will be distributed over This feature enables for SGW to count
multiple carriers when they camp on. For packets that are actually delivered to UEs,
this feature, Operator should configure the which prevents overbilling for packets
parameters, which control the idle UE ratio overflowed and dropped at eNB due to air
among carriers. congestion.
Farhatullah Mohammed 15
LTE Bible
eNB Overload control(Adaptive Access In MOCN, operator can highly utilize radio
Barring) resources between different PLMNs by
configuring som portion of radio resources
eNB periodically monitors the load status of shared between them. shared between
CPU processor. When CPU overload is operators.
detected, eNB performs automatically
adjustment of the access barring control Inter-PLMN Handover
parameters based on CPU overload
Inter-PLMN handover is mobility control
level(Minor/Major/Critical).
functionality between cells that served
Operator Benefits: PLMN is different from each other.
LTE users can avoid access to an eNB under LTE users can obtain EPS bearer service in
other network operators area which is not
congestion
the subscribed network operator.
Multi-PLMN Support
Load Balancing between Multi-operator
In a shared cell, eNB periodically broadcasts a Frequencies
SIB1 message which includes supporting
PLMN id list up to 6. According to the To support traffic management for the
selected PLMN id included in RRC network with both carriers only for a
Connection Setup Complete message, eNB specific operator and shared carriers for
routes the control message to an multiple operators, eNB provides the
concept of carrier-group. Load balancing
appropriated MME to make a connection to
the network. using the carrier-group concept has two
operations: load equalization within the
Operator Benefits: same carrier-group and offloading the
overloaded traffic between carrier-gro
Operator can reduce CAPEX. Operator Benefits:
Flexible Configuration for Radio Resource
Operators can distribute the amount of
Sharing eNB allocates the radio traffic on shared multiple carriers.
resources(PRB, active UE capacity, bearer
capacity) to each PLMN id according to the End User Benefits:
radio sharing ratio configured by operator.
Operator can configure some portion of the The bad QoE due to overload will be
resources dedicated to each operator and reduced. ups.
remaining resources to be commonly Usage Report per PLMN
Operator Benefits:
eNB provides usage data per PLMN to LSM.
Operator can wholesale a portion of PRB usage, user data usage, number of UEs,
spectrum by configuring some portion of number of bearers, and signaling messages
radio resources dedicated to a specific will be counted per PLMN.
PLMN id.
Operator Benefits:
Farhatullah Mohammed 16
LTE Bible
Host operator can figure out how much data LTE users can do an emergency call while
is consumed by each partner operator. staying in E-UTRAN, by transition to legacy
CS network (UTRAN).
The usage data can be utilized for the
purpose of settlement among partner CMAS (Commercial Mobile Alert Service)
operators
CMAS is a public warning system developed
IMS based Emergency Call Support for the delivery of warning notifications.
The CMAS warning notifications are short
To support IMS emergency call, eNB performs text messages (CMAS alerts). The CMAS
emergency call specific admission control, warning notifications are broadcasted via
security handling and mobility control. SIB messages.
Operator Benefits: Operator Benefits:
Operator can provide Emergency service to
Operator can provide public warning
its subscribers while they are staying in E- notifications to its subscribers while they
UTRAN. are staying in E-UTRAN.
End User Benefits: End User Benefits:
LTE users can do an emergency call while Users can be notified for public warning
staying in E-UTRAN, as well as in legacy CS
messages from network, and then they can
network. avoid some disasters or accidents.
Emergency Call via CSFB to CDMA2000 ETWS (Earthquake and Tsunami Warning
This is CSFB to CDMA2000 1xRTT functionality System)
for emergency call ETWS is a public warning system for warning
Operator Benefits: notifications related to earthquake and/or
tsunami events. ETWS warning notifications
Operator can provide Emergency service to can be either a primary notification (short
its subscribers by using legacy CS network notifications delivered within 4 seconds) or
(CDMA2000 1xRTT). secondary notification (providing detailed
information). The ETWS primary and
End User Benefits:
secondary notifications are broadcasted via
LTE users can do an emergency call while SIB messages.
staying in E-UTRAN, by transition to legacy
Operator Benefits:
CS network (CDMA2000 1xRTT).
Operator can provide public warning
Emergency Call via CSFB to UTRAN
notifications to its subscribers while they
This is CSFB to UTRAN functionality for are staying in E-UTRAN.
emergency call
End User Benefits:
Operator Benefits:
Users can be notified for public warning
Operator can provide Emergency service to messages from network, and then they can
its subscribers by using legacy CS network avoid some disasters or accidents.
(UTRAN).
Enhanced Cell ID
End User Benefits:
Farhatullah Mohammed 17
LTE Bible
In the Cell ID (CID) positioning method, the This will increase the number of successful
position of an UE is estimated with the handovers and lead to less dropped
knowledge of its serving eNodeB and cell. connections due to missing neighbor
The information about the serving eNodeB relations.
and cell may be obtained by paging,
tracking area update, or other methods. RACH optimization
Enhanced Cell ID (E CID) positioning refers During self-configuration phase, EMS
to techniques which use additional UE supports RSI(root sequence index) auto-
and/or E UTRAN radio resource such as TA configuration using location information.
(Timing Alignment), UE measurement Subsequently, during the operational phase,
reports to improve the UE location estimate. each eNodeB collects the information
pertaining to any RSI conflicts and informs
Operator Benefits:
EMS about conflict information for
additional UE and/or E UTRAN radio reconfiguring. For RACH optimization, eNB
measurement reports to improve the UE collects the statistics of the dedicated
location estimate. preamble allocation attempt/success and
optimizes the number of dedicated
OTDOA preambles. eNB also collects the statistics of
The downlink (OTDOA) positioning method the preamble transmission during RA and
makes use of the measured timing of optimizes the PRACH Configuration Index,
downlink signals received from multiple Preamble Initial Received Target Power,
eNode Bs at the UE. The UE measures the Power Ramping Step.
timing of the received signals using Operator Benefits:
assistance data received from the
positioning server, and the resulting In the SON framework, as soon as the
measurements are used to locate the UE in eNodeB is powered up during the auto-
relation to the neighboring eNodeBs. configuration phase, it is allocated to a
RSI(Root Sequence Index). Such a RSI is
Operator Benefits:. determined using a RSI auto-configuration
to improve UE location estimate using by algorithm that uses the location information
both UE's received signals from several with neighbors. Thus, SON ensures that
eNBs and assistance information from eNB. each eNodeB has a RSI value at the time of
installation without requiring explicit
Intra-LTE ANR human intervention.
ANR allows automatic discovery and setup of In operation phase, SON ensures that each
neighbor relations when a UE moves from a eNB and LSM supports RSI
serving eNB to target eNB. ANR also collision/confusion detection and RSI
automatically sets up the LTE unique X2 reconfiguration without human
interface between eNBs, primary used for intervention. In addition, RACH optimization
handover. will reduce the amount of manual processes
involved in the RACH related optimizations
Operator Benefits:
like the number of dedicated preambles,
ANR minimize the manual handling of PRACH configuration index, preamble initial
neighbor relations when establishing new received target power and power ramping
eNBs and when optimizing neighbor lists. step.
PA Bias Control
Farhatullah Mohammed 18
LTE Bible
eNB supports power amplifier bias control by With Rel-9 redirection also the system
adjusting PA bias for low RF load without a information messages for the target GSM cell (or,
specified carrier shutdown. Two types of PA in fact, up to maximum of 32 GSM cells) the
performance can be equal (or even better in
bias control mechanisms are supported:
case the single target cell with CCO cannot be
Predefined Time schedule based and Traffic found or access fails) that the CCO with NACC
load based. (network assisted cell change, which means the
system information for the target GSM cell is
Operator Benefits: provided with the CCO).
PA bias control provides high power
In practise the above means that redirection
efficiency with low RF load. typically would perform equally well and in many
cases (esp. if the redirection or CCO is made
PA bias control saves about 6.7% of
blindly, i.e. without UE reporting GSM cells)
consumed DC power in 800MHz. better than CCO, and therefore it is typically
used with CS fallback.
Test of VSWR
Cell reselection
The functionality of VSWR(Voltage Standing
Wave Ratio) test is used to measure return
Cell reselection is the process of changing the
loss in transmitting antenna of power amp mobile's serving cell (either in idle mode or while
unit. actively transmitting data). Cell reselections can
be initiated by the mobile or network. When the
Operator Benefits: network initiates a cell reselection, it sends a
Packet Cell Change Order (GPRS/EGPRS) or a Cell
This feature provides an efficient method Change Order (W-CDMA/HSPA), which provides
for measuring return loss in transmitting the parameters necessary for the mobile to find
antenna of power amp unit. and synchronize to the destination cell. If the
mobile was actively transferring data at the time
Packet Loss Detection over S1 of the cell reselection, any subsequent allocation
of traffic channel resources to continue the
eNB counts and provide statistics about lost packet data transfer are handled by signaling
packets and out-of sequence packets between the mobile and destination cell, and
occurred during delivery from SGW to eNB. does not involve the origination cell.
This feature can be enabled only when eNB
interworks with EPC. Handover
Farhatullah Mohammed 20
2. Introduction
- LTE is abbreviated as Long term Evolution.
- LTE is successor of not only UMTS but also CDMA 2000.
- LTE is introduced to get higher data rates of 300Mbps peak downlink and 75Mbps peak uplink
in 20MHz Carrier for FDD.
- LTE is an ideal technology to support higher data rates for the services VoIP, streaming media,
video conferencing.
- LTE uses both Time Division Duplexing (TDD) and Frequency Division Duplexing (FDD).
- In FDD, both uplink and downlink uses different frequencies. Uplink and downlink uses same
frequency in TDD.
Advantages of LTE:
- High Throughput: High downlink and uplink throughput can be achieved.
- Low Latency: Time required to connect to the network in the range of few hundreds milli
seconds.
- FDD and TDD in the same platform: Frequency Division Duplex FDD and Time Division
Duplex TDD.
- Superior End user Experience: Optimized signaling for connection establishment and other air
interface and mobility management procedures have further improved user experience.
- Seamless Connection: LTE supports seamless connection to the existing networks such as
GSM, CDMA and WCDMA.
- Simple Architecture: Low operating expenditure because of simple architecture.
LTE Bible
- LTE uses OFDM transmission schemes., it uses OFDMA in Downlink and SC-FDMA in uplink.
- A Resource block is a basic entity in the LTE terminology which when modulated using OFDM
sub-carriers becomes Resource Elements which is the smallest unit of the LTE spectrum.
- A Physical Resource Block (PRB) is defined as smallest unit used by the scheduling algorithm.
- TTI : Transmission Time Interval is the duration of the transmission on the radio link. TTI is
related to the size of the data blocks passed from the higher network layer to the radio link
layer.
- Link Adaptation or Adaptive Modulation Coding: It is the ability to adapt the modulation
scheme and the coding rate of the error correction according to the radio link. If the condition
of the radio link are good, a high level efficient modulation scheme and a small amount of
error correction is used.
Farhatullah Mohammed 22
LTE Bible
3. Resource Blocks in LTE
Resource Element: RE is the smallest unit of transmission resources in LTE, in uplink and downlink.
RE consists of 1 subcarrier in the frequency domain for duration of 1 symbol (OFDM in the downlink
and SC-FDMA in the uplink).
- Subcarrier Spacing: It is the space between the individual carriers, in LTE 15KHz. There is no
guard band between these subcarrier frequencies , rather Guard period is called as Cyclic
prefix is used in the time domain to help prevent multipath Inter Symbol Interference (ISI)
between subcarriers.
- Cyclic Prefix: A set of samples which are duplicated from the end of transmitted symbol and
appended cyclically in the beginning of the symbol. This can form a type guard interval to
absorb Inter symbol interference (ISI).
- Time Slot: 0.5ms time period of the LTE frame corresponding to 7 OFDM symbols (7CPs)
when normal CP=5usec used. And 6 symbols(CP=6) when Extended CP = 17usec is used.
-
- Resource Block
- Resource Block: A unit of transmission resource consisting of 12 subcarriers in the frequency
domain and 1 time slot (0.5ms) in the time domain.
- 1 RB = 12(Subcarriers) x 7 (Symbols ) = 84 Resource Elements. (For Normal CP :- 7 symbols)
- 1 RB = 12(Subcarriers) x 6 (Symbols ) = 72 Resource Elements (For Extended CP:- 6 symbols)
- LTE Subframe or TTI = two slots i.e.. 1ms in time
- LTE frame 10ms or 10 subframes or 20 slots.
- Bandwidths directly affects the throughput. Different Bandwidths have different number of
RB.
- 10% of the total bandwidth is used for the Guard band. This is not valid of 1.4MHz bandwidth.
- For 20MHz Bandwidth, 10% of 20MHz = 2MHz is used for Guard band and 18MHz is effective
bandwidth.
- Number of subcarriers = 18MHz/15KHz = 1200
- Number of Resource blocks = 18MHz/180KHz = 100RB
-
-
Farhatullah Mohammed 23
LTE Bible
-
- Resource Blocks in Frequency Bands.
In Time Domain:
- Occupies 0.5 ms slot in time domain.
- Consists of 7 OFDMA symbols when using Normal Cyclic Prefix.
- Consists of 6 OFDMA symbols when using Extended Cyclic Prefix.
In Frequency Domain:
- Consists of 12 subcarriers.
- Each subcarrier is of 15 KHZ.
- Each RB occupy 12*15 = 180 KHZ in frequency domain.
- The GRID generated by One Sub-Carrier in the Frequency Domain and One Symbol in the
Time Domain defines a RESOURCE ELEMENT (RE).
- RB consists of 84 (12*7) REs when using Normal Cyclic Prefix.
Farhatullah Mohammed 24
LTE Bible
- RB consists of 72 (12*6) REs when using Extended Cyclic Prefix.
- A single RE can carry a Single Modulation Symbol (2 bits when using QPSK, 4 bits when
using 16QAM, and 6 bits when using 64QAM).
Farhatullah Mohammed 25
LTE Bible
4. Resource Allocation & Management Unit
Reading various LTE specification, you will see many terms which seems to be related to
resource allocation but looks very confusing. At least you have to clearly understand the
following units.
i) Resource Element(RE) : The smallest unit made up of 1 symbol x 1 subcarrier.
ii) Resource Element Group (REG) : a group of 4 consecutive resource elements. (resource
elements for reference signal is not included in REG)
iii) Control Channel Element (CCE) : a group of 9 consective REG
iv) Aggregation Level - a group of 'L' CCEs. (L can be 1,2,4,8)
v) RB (Resource Block) : I think everybody would know what this is. This is a unit of 72
resource elements which is 12 subcarrier by 6 symbols.
vi) RBG (Resource Block Group) : This is a unit comprised of multiple RBs. How many RBs
within one RBG differs depending on the system bandwidth. (Refer to RB Size allocation for
each System Bandwidth for the details)
We use these units in hierachical manner depending on whether it is for control channel or
data channel.
For PDCCH, the hierachy would be : RE --> REG --> CCE --> Aggregation Level
==> I think a couple of example would give you more practical understanding.
Resource Allocation : Network would allocate the DCI 1 spreaded over CCE4, CCE5.
Resource Allocation : Network would allocate the DCI 1 spreaded over CCE4, CCE5 and
allocate the DCI 0 spreaded over CCE6, CCE7.
Resource Allocation : Network would allocate the DCI 1 spreaded over CCE4, CCE5 and
allocate the DCI 0 spreaded over CCE6, CCE7 and allocate two CCE for DCI 3 but DCI 3 would
be allocated to a common search space (not to a user specific search space).
Farhatullah Mohammed 27
LTE Bible
5. LTE Throughput Calculation
Throughput calculation for LTE TDD
- For any system, throughput is calculated as symbols per second.
- For 20MHz Bandwidth, there are 100 Resource Blocks and each resource block have 12 x 7 x 2
= 168 symbols per ms in case of normal CP.
- 168 symbols per ms = 168000 symbols per second = 16.8Msymbols/sec
- For 64QAM, there are 6 bits per symbols.
- The Throughput will be 6bits per symbol x 16.8 M symbols per sec = 100.3 Mbps
- For LTE MIMO ( 4Tx and 4Rx) the throughput will be calculated as 403.2Mbps
- Many simulations indicate that 25% overhead is used for signaling and controlling.
- The effective throughput is 300Mbps.
- 300Mbps is valid for downlink and is not valid for uplink.
- In uplink there is single antenna on UE, so with 20MHz we get maximum of 100Mbps, after
considering 25% overhead, 75Mbps throughput is achieved in uplink.
PEAK CAPACITY
Farhatullah Mohammed 28
LTE Bible
- There is another technique to calculate the peak capacity which I include here as well for a
220 MHz LTE system with 44 MIMO configuration and 64QAM code rate 1:
- Downlink data rate:
- Pilot overhead (4 Tx antennas) = 14.29%
- Common channel overhead (adequate to serve 1 UE/subframe) = 10%
- CP overhead = 6.66%
- Guard band overhead = 10%
- Downlink data rate = 4 x 6 bps/Hz x 20 MHz x (1-14.29%) x (1-10%) x (1-6.66%) x (1-10%) = 298
Mbps.
- Uplink data rate:
- 1 Tx antenna (no MIMO), 64 QAM code rate 1 (Note that typical UEs can support only
16QAM)
- Pilot overhead = 14.3%
- Random access overhead = 0.625%
- CP overhead = 6.66%
- Guard band overhead = 10%
- Uplink data rate = 1 * 6 bps/Hz x 20 MHz x (1-14.29%) x (1-0.625%) x (1-6.66%) x (1-10%) = 82
Mbps.
Farhatullah Mohammed 29
LTE Bible
6. Frequency Bands
Frequency Bands of LTE:
Farhatullah Mohammed 30
LTE Bible
-
- Frame structure
- The duration of one LTE radio frame is 10 ms. One frame is divided into 10 subframes of 1
ms each, and each subframe is divided into two slots of 0.5 ms each. Each slot contains
either six or seven OFDM symbols, depending on the Cyclic Prefix (CP) length. The useful
symbol time is 1/15 kHz= 66.6 mircosec. Since normal CP is about 4.69 microsec long, seven
OFDM symbols can be placed in the 0.5-ms slot as each symbol occupies (66.6 + 4.69) =
71.29 microseconds. When extended CP (=16.67 microsec) is used the total OFDM symbol
time is (66.6 + 16.67) = 83.27 microseconds. Six OFDM symbols can then be placed in the
0.5-ms slot. Frames are useful to send system information. Subframes facilitate resource
allocation and slots are useful for synchronization. Frequency hopping is possible at the
subframe and slot levels.
Farhatullah Mohammed 31
LTE Bible
-
- In LTE, radio resources are allocated in units of Physical Resource Blocks (PRBs). Each PRB
contains 12 subcarriers and one slot. If the normal Cyclic Prefix is used, a PRB will contain
12 subcarriers over seven symbols. If the extended CP is used, the PRB contains only six
symbols. The UE is specified allocation for the first slot of a subframe. There is implicit
allocation for the second slot of the subframe. For example, if the eNB specifies one RB as
the resource allocation for the UE, the UE actually uses two RBs, one RB in each of the two
slots of a subframe. When frequency hopping is turned on, the actual PRBs that carry the
UE data can be different in the two slots. In a 10 MHz spectrum bandwidth, there are 600
usable subcarriers and 50 PRBs.
- LTE - TDD Subframe Configuration
-
-
-
-
- Frame structure Type 2 is applicable to TDD is as shown in the figure. Each radio frame of
10 ms in length consists of two half-frames of 5 ms in length. Each half-frame consists of
eight slots of the length Ts=5 ms and three special fields DwPTS, GP, and UpPTS of 1 ms in
length.
- Different configurations, numbered zero to six, are defined in the standard for the
subframe number allocated for the uplink and downlink transmission. Subframe 1 in all
Farhatullah Mohammed 32
LTE Bible
configurations and subframe 6 in configurations 0, 1, 2 and 6 consist of DwPTS, GP and
UpPTS. All other subframes are defined as two slots.
- Switch-point periodicities of 5 ms and 10 ms are supported. The standard defines the table
for the uplink and downlink allocations for switch-point periodicity. In the case of a 5-ms
switch-point periodicity, UpPTS and subframes 2 and 7 are reserved for uplink transmission.
- In the case of a 10-ms switch-point periodicity, UpPTS and subframe 2 are reserved for
uplink transmission and subframes 7 to 9 are reserved for downlink transmission.
- Subframe 0 and 5 are always for the DL. The subframe following the special SF is always for
the UL. The DwPTS field carries synchronization and user data as well as the downlink
control channel for transmitting scheduling and control information. The UpPTS field is
used for transmitting the PRACH and the Sounding Reference Signal (SRS
SPECIAL SUB-FRAME
Farhatullah Mohammed 33
LTE Bible
LTE- TDD SUBFRAME DETAILED:
Farhatullah Mohammed 34
LTE Bible
Switching Points
RACH Configuration
Farhatullah Mohammed 35
LTE Bible
Farhatullah Mohammed 36
LTE Bible
HARQ Timing
Problem is how to interpret this table. Following shows how to interpret each raw
of the table.
In case of UL/DL Configuration 0, Ack/Nack response timing for the PDSCH that is
received by UE is transmitted according to the following rule.
Farhatullah Mohammed 37
LTE Bible
How do you interpret this table and DL/UL correlation ?
It says
In case of UL/DL Configuration 1, Ack/Nack response timing for the PDSCH that is received
by UE is transmitted according to the following rule.
It says
Farhatullah Mohammed 38
LTE Bible
SFN
At subframe 7, UE transmit Ack/Nack for PDSCH it received at subframe 0,1 in current SFN
In case of UL/DL Configuration 2, Ack/Nack response timing for the PDSCH that is received
by UE is transmitted according to the following rule.
It says
Farhatullah Mohammed 39
LTE Bible
Farhatullah Mohammed 40
LTE Bible
SR/DCI 0 Timing
The Time delay between SR(Scheduling Request) and DCI 0 is not clearly specified in 3GPP
specification. So basically, NW can send DCI 0 in any available DL subframe after reception
of SR, but depending on the eNodeB and Test Equipment some minimum time interval
may be required.
Let's assume that you are using DL/UL Configuration 2. and suppose UE sent a NACK at
Subframe 2.
How did you know whether the NACK is for PDSCH at subframe 4 or 5 or 6 or 8 ? (As you
know, in FDD.. the answer is so simple since the ACK/NACK from the UE is always for the
PDSCH that it received 4 subframe before. If it is FDD, the answer is supposed to be 'it is
for PDSCH received at subframe 9 in previous SFN), but in TDD case it is different as you
may guess.
Then how do you correlate the NACK to the specific PDSCH which caused the NACK. It is
completely dependent on how much detailed information that your UE log or Network log
provide. If UE log or Network log provide ACK/NACK information and HARQ process
number for every subframe.. you can try following procedure.
i) First, check UCI info at specific SFN and subframe number (let's label this as
'SFN_n:Subframe_2') and locate the HARQ process number that caused NACK.
ii) Go to transmitted PDSCH list 'around' SFN_n:Subframe_2 (at this point, you would not
Farhatullah Mohammed 41
LTE Bible
know exactly which subframe you have to pin point out).
iii) Look through several subframes upwards and downwards to find the subframe that is
marking the same HARQ process number as you got at step i). That is the subframe that
caused NACK.
As described above, in TDD LTE ibe subframe can transmit ACK/NACK for multiple
subframe as shown below. In the following figure as an example, UE send ACK/NACK for 4
PDSCHs in subframe 2. What should eNB do if the subframe 2 send NACK ? Does it have to
retransmit the whole 4 PDSCHs ? or transmit only PDSCH which is NACKed ?
Farhatullah Mohammed 42
LTE Bible
Followings are some of the items that is worth noticing from 3GPP 36.213 10.1.3 TDD
HARQ-ACK feedback procedures (I modified the statement a little bit to make it simple and
hopefully clearer)
For TDD UL/DL configuration 5 and a UE that does not support aggregating more than one
serving cell, only HARQ-ACK bundling is supported.
PUCCH format 1b with channel selection according to the set of Tables 10.1.3-2/3/4 or
according to the set of Tables 10.1.3-5/6/7 is not supported for TDD UL/DL configuration
5.
DD HARQ-ACK bundling is performed per codeword across M multiple DL subframes
associated with a single UL subframe n, by a logical AND operation of all the individual
PDSCH transmission (with and without corresponding PDCCH/EPDCCH) HARQ-ACKs and
ACK in response to PDCCH/EPDCCH indicating downlink SPS release
or TDD HARQ-ACK multiplexing and a subframe n with M >1, spatial HARQ-ACK bundling
across multiple codewords within a DL subframe is performed by a logical AND operation
of all the corresponding individual HARQ-ACKs. PUCCH format 1b with channel selection is
used in case of one configured serving cell
or TDD HARQ-ACK multiplexing and a subframe n with M = 1, spatial HARQ-ACK bundling
across multiple codewords within a DL subframe is not performed, 1 or 2 HARQ-ACK bits
are transmitted using PUCCH format 1a or PUCCH format 1b, respectively for one
configured serving cell.
You would notice the variable 'M' in many of the statement above. M is defined to be "the
number of elements in the set K defined in Table 10.1.3.1-1". Following examples would
give you clearer idea on the meaning of M.
Farhatullah Mohammed 43
LTE Bible
System Information Variation
Farhatullah Mohammed 44
LTE Bible
8. LTE Architecture
Farhatullah Mohammed 46
LTE Bible
9. LTE Interfaces
- Air Interface Uu: It is the interface connection between the user equipment and eNodeB.
- The UE and eNodeB make use of the Uu whenever transmit or receive across the LTE
interface.
- X2 Interface: Connects one eNodeB with another eNodeB
Allows both signalling and data to be transferred between the neighbouring
eNodeB.
- X2 CP (Control Plane): Interface allows signaling between eNodeB.
- X2 UP (User Plane) : Interface allows the transfer of application data between eNodeB.
- S1 Interface: Connects eNodeB to the Evolved Packet Core (EPC).
Allows signaling and the data to be transferred between EPC and EUTRAN
S1 MME (Control Plane): allows signaling with MME.
S1 U (User Plane) : allows transfer of application data through S GW.
- S11 Interface: Connects MME to S-GW.
Allows signaling information for mobility and bearer management to be transferred.
Application data does not use S11.
- S5 Interface: Connects S-GW to PDN-GW
Both control plane and user plane uses S5 interface.
PDN provide connectivity to the set of IP ServicesGateway
- S8 Interface: Similar to S5 interface but it terminates at a PDN Gateway belonging to
different PLMN.
- S6a Interface: Connects MME to HSS
HSS is a database for all user subscription information.
- S13 Interface: Connects MME to EIR
EIR stores IMEI
- S7 or Gx Interface: Connects PCEF within PDN Gateway to the PCRF
PCRF provides QoS and charging information to the PDN Gateway
- SGi Interface: Interface connects between PDN Gateway and packet data network
- S3 Interface: Connects MME and SGSN.
- S10: Connects MME with other MME
- S4 Interface: Connects S GW with SGSN
Farhatullah Mohammed 47
LTE Bible
10. LTE Bearers
Bearers:
Bearer is a concept that defines how UE data is treated when it travels across the network.
Some data is provided with guaranteed bit rate and other may face low transfer.
Default Bearer:
When LTE UE is attached to the network for the first time, it will be assigned default bearer
which remains as long as UE is attached. Each default bearer comes with IP address QCI 5
to 9(Non GBR) can be assigned to default bearer.
Dedicated Bearer:
Dedicated bearers provides dedicated tunnel to one or more specific traffic (i.e VOIP,
video). Dedicated bearer acts as an additional bearer on top of default bearer.
- Dedicated bearer does not require IP address and is linked to one of the default bearer
established previously.
- Dedicated bearer can be with Guaranteed bit rate and Non-Guaranteed Bit Rate.
- Dedicated bearer uses Traffic Flow Template (TFT) to give special treatment to the services.
- Dedicated bearer is linked to default bearer using Linked EPS bearer identity setup
information.
What is the information that default EPS has but dedicated bearer does not?
Farhatullah Mohammed 48
LTE Bible
- APN name, PDN type and PDN address.
What kind of PDN address does dedicated EPS bearer will use?
- Dedicated EPS bearer has the same PDN address of default EPS bearer.
Which of the bearers does not contains QCI?
- There is one to one relation between the default bearer and APN. 1 APN for 1 bearer.
In many cases, we get confused by the role of Default EPS Bearer and Dedicated
EPS Bearer. I think the best way to clear the confusion would be to understand
the detailed information elements (parameters) defining these two bearer.
First take a look at the decoded message for Default EPS Bearer and Dedicated
EPS Bearer.
Farhatullah Mohammed 49
LTE Bible
Farhatullah Mohammed 50
LTE Bible
11. Quality of Service - QoS
There are some subscribers who want to have better user experience in 4G LTE device.
These users are willing to pay for high bandwidth and better network access on their
devices.
- Not only subscribers, but some services itself need better priority handling in the network
like voip.
- In LTE network, QoS is applied on Radio bearer, S1 bearer and S5/S8 bearer, collectively
called EPS bearer.
- The QoS is implemented between UE and PDN gateway which is applied to set of bearers.
GBR: Guaranteed Bit Rate: It is the minimum bit rate per EPS bearer specified
independently for uplink and downlink.
MBR: Maximum Bit Rate: It is the maximum guaranteed bit rate per EPS bearer specified
independently for uplink and downlink.
AMBR: Aggregate Maximum Bit Rate: It is the maximum allowed total non GBR
throughput to specific APN.
ARP: Allocation and Retention Priority: It decides whether new bearer modification or
establishment request should be accepted considering the current resource situation.
TFT: Traffic Flow Template: TFT is always associated with the dedicated bearer and may or
may not be associated with the default bearer.
- Dedicated bearer provides QoS to special service or application and TFT defines rules so
that UE and network knows which IP packet should be sent or particular dedicated bearer.
L-EBI: Linked EPS Bearer Identity: Dedicated bearers are always linked to one of the default
bearers.
Farhatullah Mohammed 51
LTE Bible
- LEBI tells dedicated bearer to which default bearer it is attached to.
- Applying QoS Through QCI Levels: QCI (Quality of Service Class Identifier)
- Aims to provide users with low download volume with highest speed by giving them higher
scheduling priority.
- As users download continues, the user will move to a lower profile with a lower scheduling
priority which will reduce his affect to the normal users.
Profile
Profiles Profile A B Profile C Profile D Profile E
More than
Consumpt Norm More than 1GB More than 2GB
Always 15GB per
ion al per day per day
week
QCI 6 7 8 9 9
ARP 6 11 11 11 11
Throughp 1.2 MBR:
1 50% of Profile B 30% of Profile B
ut Profile B 256kbps
Weight 11 9 4 2 2
Farhatullah Mohammed 52
LTE Bible
12. Protocol Stacks
Farhatullah Mohammed 53
LTE Bible
13. Protocol Layer Functionality
Farhatullah Mohammed 54
LTE Bible
Farhatullah Mohammed 55
LTE Bible
Warning message transfer function (including selection of appropriate eNodeB);
UE Reach ability procedures.
- The MME shall signal a change is UE Time Zone only in case of mobility and in case of UE
triggered Service Request, PDN Disconnection and UE Detach. If the MME cannot
determine whether the UE Time Zone has changed (e.g. the UE Time Zone is not sent by the
old MME during MME relocation), the MME should not signal a change in UE Time Zone. A
change in UE Time Zone caused by a regulatory mandated time change (e.g. daylight saving
time or summer time change) shall not trigger the MME to initiate signalling procedures
due to the actual change. Instead the MME shall wait for theUE's next mobility event or
Service Request procedure and then use these procedures to update the UE Time Zone
information in PDN GW.
- Serving GW is the gateway which terminates the interface towards E-UTARN. For
each UE associated with the EPS, at given point of time, there is a single Serving GW.
- SGW is responsible for handovers with neighboring eNodeB's, also for data transfer in
terms of all packets across user plane. To its duties belongs taking care about mobility
interface to other networks such as 2G/3G. SGW is monitoring and maintaining context
information related to UE during its idle state and generates paging requests when arrives
data for the UE in downlink direction. (e.g. somebody's calling). SGW is also responsible for
replication of user traffic in case of LI.
- SGW functions as a list, according to 23.401 3GPP documentation.
- SGW functions include:
- The PGW is the gateway which terminates the SGi interface towards PDN. If UE is accessing
multiple PDNs, there may be more than one PGW for that UE, however a mix of S5/S8
connectivity and Gn/Gp connectivity is not supported for that UE simultaneously.
Farhatullah Mohammed 56
LTE Bible
- PGW is responsible to act as an "anchor" of mobility between 3GPP and non-3GPP
technologies. PGW provides connectivity from the UE to external PDN by being the point of
entry or exit of traffic for the UE.
- The PGW manages policy enforcement, packet filtration for users, charging support and LI.
- PGW functions include:
ENODEB FUNCTIONALITY:
- eNode B is the RAN node in the EPS architecture that is responsible for radio transmission
to and reception from UEs in one or more cells.
- The eNode B is connected to EPC nodes by means of an S1 interface. The eNode B may also
be connected to its neighbour eNode Bs by means of the X2 interface. Some significant
changes have been made to the eNode B functional allocation compared to UTRAN.
- Most Rel-6 RNC functionality has been moved to the E-UTRAN eNode B. Below follows a
description of the functionality provided by eNode B.
- eNode B owns and controls the radio resources of its own cells. Cell resources are
requested by and granted to MMEs in an ordered fashion.
- This arrangement supports the MME pooling concept. S-GW pooling is managed by the
MMEs and is not reallyseen in the eNode B.
Mobility control
- The eNode B is responsible for controlling the mobility for terminals in active state. This is
done by ordering the UE to perform measurement and then performing handover when
necessary.
Farhatullah Mohammed 57
LTE Bible
- The ciphering of user plane data over the radio interface is terminated in the eNode B.
- Also the ciphering and integrity protection of RRC signalling is terminated in the eNodeB.
Segmentation/Concatenation
- Radio Link Control (RLC) Service Data Units (SDUs) received from the Packet Data
convergence Protocol (PDCP) layer in the AGW consist of whole IP packets may be larger
than the transport block size provided by the physical layer. Thus, the RLC layer must
support segmentation and concatenation to adapt the payload to the transport block size.
HARQ
- A Medium Access Control (MAC) Hybrid Automatic Repeat reQuest (HARQ) layer with fast
feedback provides a means for quickly correcting most errors from the radio channel. To
achieve low delay and efficient use of radio resources, the HARQ operates with a native
error rate which is sufficient only for services with moderate error rate
requirements such as for instance VoIP. Lower error rates are achieved by letting an outer
Automatic Repeat reQuest (ARQ) layer in the eNode B handle the HARQ errors.
Scheduling
- A scheduler with support for the QoS model provides efficient scheduling of UP and CP
data.
Farhatullah Mohammed 58
LTE Bible
- The goal of RAC is to ensure high resource utilization(by accepting radio bearer requests as
long as radio resources are available) and at the same time to ensure proper QoS for in-
progress sessions(by rejecting radio bearer request when they cannot be accommodated)
- RAC is located in ENB.
Farhatullah Mohammed 59
LTE Bible
15. LTE Timers and Constants
Farhatullah Mohammed 60
LTE Bible
initiates the CONNECTION RE-ESTABLISHMENT Procedure
- >> Starts upon receipt of t320 or upon cell re- selection to E-UTRA from
another RAT with validity time configured for dedicated priorities (in
which case the remaining validity time is applied).
- T320 >>Stops upon entering RRC_CONNECTED state, when PLMN selection is
performed on request by NAS OR upon cell re-selection to another RAT
>> At expiry, it discards the cell re-selection priority info provided by
dedicated signaling
-
- T300: Timer T300 of the cell in the eNodeB.
- The UE start T300 timer after sending RRC Connection Request.
- When it receives RRC connection setup message or RRC connection Reject message, the
timer is cleared.
- When the T300 timer terminates, UE reset the MAC, clears the MAC configuration and re-
establishes the RLC
- Default timer value is 400ms.
- T301: Timer 301 of the Cell in eNB
- The UE starts T301 timer after sending the RRC Connection Reestablishment message or
the RRC connection Reestablishment reject message, the timer is cleared.
- When the T301 timer terminates, UE becomes idle.
- Default value of the timer is 200ms
- T302:
- Timer starts after receiving the RRC Connection Reject message.
- The timer terminates when UE status becomes RRC connect or the cell is reselected.
- When the timer is cleared the UE marks the cell as barred and perform cell reselection.
- T304:
- The timer start by UE after receiving RRC reconfiguration message during the handover.
- The timer terminates when the handover to EUTRAN succeeds.
- Default value is 200ms
Farhatullah Mohammed 61
LTE Bible
- T310:
- Timer value which starts after UE continuously receives out-of-sync indication as much as
N310.
- Cleared if in-sync indication is received continuously as much as N311, if handover is
triggered or the reestablishment procedure is triggered.
- Default value of the timer is 1000ms.
- T311:
- The timer starts by UE when initiating a reestablishment procedure.
- The timer is cleared if a suitable EUTRAN cell or inter RAT cell is found.
- If the timer is cleared without finding a suitable cell, it enters RRC_IDLE state.
- Default value of this timer is 3000ms.
- N 310:
- The maximum count of out-of-sync indication the UE receives from the lower layer
- Default value of counter is 10.
- N 311:
- The maximum count of in-sync indication on the UE receives from the lower layer.
- Default value of this counter is 1.
- T303:
- Timer starts when access is barred while performing RRC connection establishment for MO
(Mobile Originating) calls.
- Timer stops while entering RRC_Connected and upon cell reselection mode.
- T 305:
- Timer starts when the access is barred while performing RRC Connection establishment for
MO Signalling
- The timer stops when entering RRC_Connected and UE does cell reselection.
Farhatullah Mohammed 62
16. LTE Timers Detailed_UE Side
TIMER TIMER ON
STATE CAUSE OF START NORMAL STOP
NUM. VALUE EXPIRY
T3402 Default 12 EMM DEREGISTERED At attach failure and the ATTACH REQUEST sent Initiation of the attach
min. EMM REGISTERED attempt TRACKING AREA UPDATE procedure or TAU
NOTE 1 counter is equal to 5. REQUEST sent procedure
At tracking area updating
failure
and the attempt counter is
equal to 5.
T3410 15s EMMREGISTEREDINITIATED ATTACH REQUEST sent ATTACH ACCEPT received Start T3411 or T3402 as
ATTACH REJECT received described in subclause
5.5.1.2.6
T3411 10s EMM DEREGISTERED. At attach failure due to ATTACH REQUEST sent Retransmission of the
ATTEMPTING TO-ATTACH EMM lower layer failure, T3410 TRACKING AREA UPDATE ATTACH REQUEST or
REGISTERED. timeout or attach rejected REQUEST sent TRACKING AREA
ATTEMPTING TO-UPDATE with other EMM cause UPDATE REQUEST
values than those treated in
subclause 5.5.1.2.5.
At tracking area updating
failure due to lower layer
failure, T3430 timeout or
TAU rejected with other
EMM cause values than
those treated in subclause
5.5.3.2.5.
T3412 Default 54 EMM REGISTERED In EMM-REGISTERED, when When entering state EMM Initiation of the periodic
min. EMM-CONNECTED mode is DEREGISTERED TAU procedure
NOTE 2 left. or
NOTE 5 when entering EMM-
CONNECTED mode.
LTE Bible
T3416 30s EMM REGISTERED INITIATED RAND and RES stored as a SECURITY MODE Delete the stored RAND
EMM REGISTERED result of a UMTS COMMAND received and RES
EMM DEREGISTERED INITIATED authentication challenge SERVICE REJECT received
EMM-TRACKINGAREA UPDATING TRACKING AREA UPDATE
INITIATED ACCEPT received
EMM-SERVICE REQUEST INITIATED AUTHENTICATION REJECT
received
AUTHENTICATION FAILURE
sent
EMM DEREGISTERED
or
EMM-NULL entered
T3417 5s EMM-SERVICEREQUESTINITIATED SERVICE REQUEST sent Bearers have been set up Abort the procedure
EXTENDED SERVICE SERVICE REJECT received
REQUEST sent in case f and
g in subclause 5.6.1.1
T3417ext 10s EMM-SERVICEREQUESTINITIATED EXTENDED SERVICE Inter-system change from Abort the procedure
REQUEST sent in case d in S1 mode to A/Gb mode or
subclause 5.6.1.1 Iu mode is completed
EXTENDED SERVICE Inter-system change from
REQUEST sent in case e in S1 mode to A/Gb mode or
subclause 5.6.1.1 and the Iu mode is failed
CSFB response was set to SERVICE REJECT received
"CS fallback
accepted by the UE"
T3418 20s EMM REGISTEREDINITIATED AUTHENTICATION FAILURE AUTHENTICATION On first expiry, the UE
EMM REGISTERED (EMM cause = #20 "MAC REQUEST received should consider the
EMM-TRACKINGARE failure" network as false
AUPDATINGINITIATED or #26 "non-EPS
EMM DEREGISTEREDINITIATED authentication
EMM-SERVICEREQUESTINITIATED unacceptable") sent
T3420 15s EMM REGISTERED INITIATED AUTHENTICATION FAILURE AUTHENTICATION On first expiry, the UE
EMM REGISTERED (cause = #21 "synch REQUEST received should consider the
EMM DEREGISTERED INITIATED failure") sent network as false
EMM-TRACKINGAREA UPDATING
INITIATED
EMM-SERVICE REQUEST INITIATED
T3421 15s EMM DEREGISTERED INITIATED DETACH REQUEST sent DETACH ACCEPT received Retransmission of
DETACH REQUEST
Farhatullah Mohammed 64
LTE Bible
T3423 NOTE 3 EMM REGISTERED T3412 expires while the UE When entering state EMM Set TIN to "P-TMSI"
is in EMM-REGISTERED.NO- DEREGISTERED
CELLAVAILABLE or
and ISR is activated. when entering EMM-
CONNECTED mode.
T3430 15s EMM-TRACKING AREA UPDATING TRACKING AREA UPDATE TRACKING AREA UPDATE Start T3411 or T3402 as
INITIATED REQUEST sent ACCEPT received described in subclause
TRACKING AREA UPDATE 5.5.3.2.6
REJECT received
T3440 10s EMM REGISTERED INITIATED ATTACH REJECT, DETACH Signalling connection Release the signalling
EMM-TRACKING AREA UPDATING REQUEST, TRACKING AREA released connection and
INITIATED UPDATE REJECT with any of Bearers have been set up proceed as described in
EMM DEREGISTERED INITIATED the EMM cause #11, #12, subclause 5.3.1.2
EMM-SERVICE REQUEST INITIATED #13, #14 or #15 SERVICE
EMM REGISTERED REJECT received with any
of the EMM cause #11,#12,
#13 or #15
TRACKING AREA UPDATE
ACCEPT received after the
UE
sent TRACKING AREA
UPDATE REQUEST in
EMMIDLE mode with no
"active" flag
T3442 NOTE 4 EMM REGISTERED SERVICE REJECT received TRACKING AREA UPDATE None
with EMM cause #39 "CS REQUEST sent
domain temporarily not
available"
Note 1 The default value of this timer is used if the network does not indicate another value in an EMM signalling procedure.
The value of this timer is provided by the network operator during the attach and tracking area updating procedures. (This Timer value
Note 2
is set in Attach Accept message as well).
The value of this timer may be provided by the network in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT
Note 3
message. The default value of this timer is identical to the value of T3412.
The value of this timer is provided by the network operator when a service request for CS fallback is rejected by the network with EMM
Note 4
cause #39 "CS domain temporarily not available".
The default value of this timer is used if the network does not indicate a value in the TRACKING AREA UPDATE ACCEPT message and the
Note 5
UE does not have a stored value for this timer.
Farhatullah Mohammed 65
LTE Bible
(This Timer value is set in Attach Accept message as well).
Farhatullah Mohammed 66
LTE Bible
T3460 6s EMM-COMMON AUTHENTICATION AUTHENTICATION Retransmission of the
PROC-INIT REQUEST sent RESPONSE received same message type,
SECURITY MODE AUTHENTICATION i.e.AUTHENTICATION
COMMAND sent FAILURE received REQUEST or SECURITY
SECURITY MODE MODE COMMAND
COMPLETE received
SECURITY MODE
REJECT received
Mobile Default All except EMM Entering EMM-IDLE NAS signalling Network dependent, but
reachable 4 min DEREGISTERED mode connection typically paging is
greater established halted on 1st expiry
than
T3412
Implicit NOTE 3 All except EMM The mobile NAS signalling Implicitly detach the UE
detach DEREGISTERED reachable timer connection on 1st expiry
timer expires while the established
network is in
EMM-IDLE mode
Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the
NOTE 1:
corresponding procedure description.
The value of this timer is network dependent. If ISR is activated, the default value of this timer is 4 minutes greater than
NOTE 3:
T3423.
Farhatullah Mohammed 67
18. LTE Events
EventA4: Neighbour becomes worse than threshold
Event A1: Serving becomes better than threshold.
> + +
+ <
+ <
+ +
>
+ +
> + + +
LTE Bible
Event B1: Inter RAT neighbour becomes better than Event B2: Serving becomes worst than threshold1
threshold. and IRAT becomes better than threshold2
+ >
+ <
+ >
Farhatullah Mohammed 69
19. LTE Cell Reselection
Cell Reselection is a kind of mechanism to change cell after UE is camped on a cell and stay in IDLE
mode. This is to let UE get connected to cell which has the best condition among all the cells to
which the UE is allowed to camp on. But UE does not change cells randomly, it uses a set of pretty
complicated criteria and algorithms for this reselection process. The details of these criteria
andalgorithms will be described later but the high level guideline is as follows :
When the UE is powered on, usually it goes on with the following sequence.
i) Cell Detection/Search
vi) if RSRP/RSRQ is very poor or undetectable, go to step i) for finding other cell
if RSRP/RSRQ is measureable at least, it evaluate < Cell Reselection Criteria > perform Cell
Reselection if the criteria is met or stay in the current cell if the criteria is not met
Step vi) is the most complicated process going on during the idle stage and in this page I will
mostly deal with < Cell Reselection Criteria >. Understanding this criteria is the most imporant
thing in implementing and testing Cell Reselection.
How to detect and reselect to LTE cell while in WCDMA (WCDMA to LTE Cell Reselction) ?
How to detect and reselect to WCDMA cell while in LTE (LTE to WCDMA Cell Reselction) ?
A little bit detailed criteria can be described as follows and you will see ever further details after this.
UE always have to measure frequecies and RAT with higher priority
UE has to have to measure frequecies and RAT with lower priority in the following fashion
o UE has to perform intra-frequency measurement only when SrxLev of the serving cell <=
SintraSearch
o UE has to perform lower or equal priority inter-frequency/InterRAT measurement only when
SrxLev of the serving cell <= SnonintraSearch
LTE cell reselection uses priority based levels. (These priorities can be specified in LTE SIB4,5,6,7 and
RRC Connection Release). Priority 0 indicate the lowest priority and 7 indicate the highest priority. The
priority cannot be same for WCDMA and LTE, meaning that it must be set differently for different RAT.
Among the cell power and priority, which one plays more critical role in cell reselection ? Cell
Power defines the minimum condition. Once the minimum condition is met, Priority plays more
critical role. For example, let's assume that UE is now camped in WCDMA cell and detected a
neighbouring LTE cell with higher priority than the serving WCDMA cell, UE will perform cell
reselection to LTE cell as long as the LTE cell is above the minimum signal strength threshold. In
the same logic, if a UE camped on LTE cell detected a neighbouring WCDMA cell with higher
priority than the serving LTE cell, UE will perform cell reselection to WCDMA cell as long as the
WCDMA cell is above the minimum signal strength threshold.
WCDMA SIB19 specifies the LTE frequencies (EARFCN) and priorities. A maximum of 8 EARFCNs (4
FDD + 4 TDD) can be listed in SIB 19. For each EARFCN, you can configure a max 16 blacklisted
cells. The blacklisted cell is the cell UE should not make reselection to.
Using the eutraDetection parameter in SIB19, you can make UE to detect and display the
presence of lower priority LTE frequencies while it is in WCDMA cell.
LTE SIB6 specifies the WCDMA frequencies (DL ARFCN) and the parameters used for absolute
priority based cell reselection.
There are roughly three different ways of informing UE of Reselection Priority as listed before :
(refer to 36.304 5.2.4.1 Reselection priorities handling for details).
i) System Information
ii) RRC Connection Release message
iii) Inheriting from another RAT
Note 1 : if the priority is specified in both i) and ii), the one specified in ii) takes effect.
Note 2 : The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT
frequencies that are given in system information and for which the UE has a priority provided.
Note 3 : The UE shall not consider any black listed cells as candidate for cell reselection
How to detect and reselect to another LTE cell while in LTE Cell (LTE to LTE Cell Reselction) ?
In order for UE to reselect from one LTE cell to another LTE Cell, the internal evaluation result in UE
side (SrxLev and Squal) should meet a certain criteria, otherwise it may not even monitor (measure)
neighboring cell and in result would not perform reselection. LTE SIB3 defines various parameter to
influence the evaluation result and the expected UE side behavior is described in 36.304 5.2.4.2
Measurement rules for cell re-selection.
If your device does not perform Cell Reselection, first Check if Cell Measurement Criteria is met and the
Farhatullah Mohammed 71
LTE Bible
check if Cell Reselection Criteria is met and also check if following condition is met (Following statement
come from 36.304 5.2.4.1 Reselection Priority Handling. I saw some UE ignore this requirement but
some UE strictly follows this requirement.)
The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies
that are give in system information and for which the UE has a priority provided.
If your UE strictly follow this requirement stated above, populate SIB4 for proper neighbour cells.
Following is the contents of SIB3 for your reference (The parameter shown here is just an example.
You have to set it properly based on your own test requirement)
sib-TypeAndInfo item: sib3 (1)
sib3
cellReselectionInfoCommon
q-Hyst: dB0 (0)
cellReselectionServingFreqInfo
s-NonIntraSearch: 62dB (31)
threshServingLow: 62dB (31)
cellReselectionPriority: 7
intraFreqCellReselectionInfo
q-RxLevMin: -140dBm (-70)
s-IntraSearch: 62dB (31)
.0.. .... presenceAntennaPort1: False
neighCellConfig: Not all neighbour cells
have the same MBSFN subframe allocation as serving cell (0)
t-ReselectionEUTRA: 0s
lateNonCriticalExtension: <MISSING>
s-IntraSearch-v920
s-IntraSearchP-r9: 62dB (31)
s-IntraSearchQ-r9: 0dB
s-NonIntraSearch-v920
s-NonIntraSearchP-r9: 62dB (31)
s-NonIntraSearchQ-r9: 0dB
q-QualMin-r9: -34dB
threshServingLowQ-r9: 0dB
If the serving cell's evaluation result is as follows, UE may not perform intra frequency
measurement.
SrxLev > S_IntraSearchP
Squal > S_IntraSearchQ
Note : If neither of S_IntraSearchP nor S_IntraSearchQ is specified, UE applies the default value
(S_IntraSearchP = Infinity, S_IntraSearchQ = 0 based on 36.331)
If the serving cell's evaluation result does NOT meet following criteria, UE perform intra frequency
measurement.
SrxLev > S_IntraSearchP
Squal > S_IntraSearchQ
Note : If neither of S_IntraSearchP nor S_IntraSearchQ is specified, UE applies the default value
(S_IntraSearchP = Infinity, S_IntraSearchQ = 0 based on 36.331)
Farhatullah Mohammed 72
LTE Bible
If the serving cell's evaluation result is as follows, UE may not perform intra frequency
measurement.
SrxLev > S_NonIntraSearchP
Squal > S_NonIntraSearchQ
Note : If neither of S_IntraSearchP nor S_IntraSearchQ is specified, UE applies the default value
(S_IntraSearchP = Infinity, S_IntraSearchQ = 0 based on 36.331)
If the serving cell's evaluation result does NOT meet following criteria, UE perform intra frequency
measurement.
SrxLev > S_NonIntraSearchP
Squal > S_NonIntraSearchQ
Note : If neither of S_IntraSearchP nor S_IntraSearchQ is specified, UE applies the default value
(S_IntraSearchP = Infinity, S_IntraSearchQ = 0 based on 36.331)
How to detect and reselect to LTE cell while in WCDMA (WCDMA to LTE Cell Reselction) ?
UE must measure the LTE frequencies and detect the available LTE cell in order to perform cell
reselection to LTE.
UE measures two physical properties called for WCDMA signal. One is CPICH RSCP and CPICH EcNo.
RSCP determines Srxlev and EcNo determines Squal.
Srxlev = Qrxlevemeas - qRxLevMin. Qrxlevemeas is RSCP level measured by UE and qRxLevMin is
the value specified in SIB.
Squal = Qqualmeas - qQualMin. Qqualmeas is EcNo level measured by UE and qQualMin is the
value specified in SIB.
The detection measurement of LTE frequencies should be done at least once every 60s for higher
priority LTE frequencies.
In following condition, detection measurements of lower priority LTE frequency is not required.
Srxlev > absPrioCellRes.sPrioritySearch1
Squal > absPrioCellRes.sPrioritySearch2
In following condition, UE should detect once every 30s for both lower and higher priority LTE
frequencies
Srxlev <= absPrioCellRes.sPrioritySearch1
Squal <= absPrioCellRes.sPrioritySearch2
The maximum number of LTE FDD Frequencies are 4. In this case, UE should have performed
measurement for detecting LTE cells on all 4 LTE frequencies once every 240 (4 x 60) s or 120(4 x 30) s
depending if UE measures above or below parameter threshold absPrioCellRes.sPrioritySearch1
How to detect and reselect to WCDMA cell while in LTE (LTE to WCDMA Cell Reselction)?
Measurement Criteria (From High Priority LTE Cell to Lower Priority WCDMA Cell): When LTE cell has
higher priority than WCDMA, it would stay in LTE cell but it performs measurement for the low priority
WCDMA if UE is under the following condition :
Srxlev of the serving cell < sNonIntraSearch (SIB3),
If we express this using dB/dBm, Srxlev of the serving cell < (2 x sNonIntraSearch (SIB3))
where Srxlev = Qrxlevmeas - qRxLevMin (SIB3),
If we express using dB/dBm, Srxlev = Qrxlevmeas [dBm] - (2 x qRxLevMin (SIB3)) [dBm]
where Qrxlevemeas = measured RSRP level, qRxLevMin = minimum RSRP level for camping
Measurement Criteria (From Lower Priority LTE Cell to Higher Priority WCDMA Cell): When LTE cell
has lower priority than WCDMA (WCDMA cell priority defined in SIB6 is higher than the serving cell
priority),The UE always have to perform measurements on WCDMA cell. How often UE has to
Farhatullah Mohammed 73
LTE Bible
measure for WCDMA depends on whether Srxlev of the serving cell is greater or lower than
sNonIntraSearch(SIB3). If no parameter is set (meaning in default condition), detection of WCDMA
cell should be performed at least every 60 seconds.
Reselection Criteria (From High Priority LTE Cell to Lower Priority WCDMA Cell): If UE in LTE cell is
under the following condition with the duration longer than tReselectionUtra (SIB6), it should
reselect to WCDMA cell.
Srxlev of LTE cell (serving cell) < threshServingLow (SIB3),
where Srxlev = Qrxlevmeas - qRxLevMin (SIB3),
where Qrxlevemeas = measured RSRP level, qRxLevMin = minimum RSRP level for camping
Srxlev of WCDMA cell > threshXLowP (SIB6),
where Srxlev = Qrxlevmeas - qRxLevMin (SIB3),
If we express using dB/dBm, Srxlev = Qrxlevmeas [dBm] - (2 x qRxLevMin (SIB3)) [dBm]
where Qrxlevemeas = measured RSCP level, qRxLevMin = minimum RSCP level for camping
Note : If more than one WCDMA meet this condition, UE should select to the cell with highest
Srxlev
Note : If these values are not specified in SIB and UE has to apply default values, UE has to perform
reselection when LTE RSRP is lower than -145 dBm and WCDMA cell is better than -119 dBm for at
least 2 seconds.
Reselection Criteria (From Lower Priority LTE Cell to Higher Priority WCDMA Cell): If UE in LTE cell is
under the following condition with the duration longer than tReselectionUtra (SIB6), it should
reselect to WCDMA cell.
Srxlev of WCDMA cell > threshXHighP (SIB6),
where Srxlev = Qrxlevmeas - qRxLevMin (SIB3),
where Qrxlevemeas = measured RSCP level, qRxLevMin = minimum RSCP level for camping
These parameters are defined in 36.304 5.2.4.7 Cell reselection parameters in system information
broadcasts. Some of the important parameters and descriptions are as follows :
ThreshXHighP : The threshold of target cell Srxlev to perfrom reselection from a low priority to a
high priority cell. (i.e, a large ThreshXHigh value makes reselection harder)
ThreshXLowP : The threshold of target cell Srxlev to perfrom reselection from a high priority to a
low priority cell. (i.e, a large ThreshXLow value makes reselection harder)
ThreshXHighQ : The threshold of target cell Squal to perfrom reselection from a low priority to a
high priority cell. (i.e, a large ThreshXHigh value makes reselection harder)
ThreshXLowQ : The threshold of target cell Squal to perfrom reselection from a high priority to a
low priority cell. (i.e, a large ThreshXLow value makes reselection harder)
SIntraSearchP : The threshold of current cell Srxlev to perform intra-frequency. If the current cell
Srxleve is lower than this value, UE perform measurement for intra-frequency.
SIntraSearchQ : The threshold of current cell Squal to perform intra-frequency. If the current cell
Squal is lower than this value, UE perform measurement for intra-frequency.
Farhatullah Mohammed 74
LTE Bible
SnonIntraSearchQ : The threshold of current cell Squal to perform inter-frequency or interRAT
measurement. If the current cell Srqual is lower than this value, UE perform measurement for inter-
frequency or interRAT cells.
Farhatullah Mohammed 75
LTE Bible
20. LTE Scheduling
- To provide efficient resource usage, the LTE concept supports fast scheduling where the resources on
the shared channels PDSCH and PUSCH are assigned to the users and the radio bearers on sub-frame
basis according to the users momentary traffic demand, QoS requirements and estimated channel
quality.
- The ENodeB allocates the physical layer resources for the uplink and downlink shared channels (DL-
SCH and UL-SCH).
- The resources comprises of Physical Resource Blocks (PRB) and modulation coding Scheme(MCS).
- MCS determines the bit rate and thus the capacity of PRB.
- Allocations may be valid for one or more TTI.
- Scheduling is also referred to as Dynamic Resource Allocation (DRA) and is a part of RRM.
- Scheduling are classified into two
Downlink Scheduling and
Uplink Scheduling
- There is no LTE scheduling Algorithm defined by standard, this enables the vendors to differentiate
between each other and use different optimization goals.
- The parameters used as input for the scheduling decisions are the Channel Quality Indicator(CQI)
reported by the UE, QoS , congestion/resource situation, fairness, charging policies and so on.
- With most schedulers aim to maximize the cell throughput under the consideration of fairness metrics
between cell edge users and users with very good channel conditions.
- Downlink Scheduling with HARQ
-
- ACK/NACK PROCESS IN DOWNLINK SCHEDULING
-
- LTE UL scheduling is similar to downlink scheduling although UL scheduler is unique entity.
Farhatullah Mohammed 76
LTE Bible
- UL scheduling grants are indicated by UE transmitting all the relevant UL scheduling information with
in PDCCH.
- This is done by using dedicated DCI, DCI type 0 scrambled with RNTI.
- This does not apply incase of power saving mode DRX mode enabled, which switches of UE receiver
periodically.
-
- UL resources are allocated using without designated PDCCH UL grant in case of SPS or for non-
adaptive HARQ retransmissions.
- Non adaptive HARQ transmission is triggered by the transmission of negative acknowledgement
(NACK) by UE.
- In UL, only localized scheduling is allowed, which means that an integer number of consecutive
Resource Blocks is allocated to one UE.
- There is only one scheduling process per UE, there is not a dedicated scheduling process per radio
bearer.
- UE feeds the scheduler with CQI, Buffer status Reports (BSR), ACK/NACK and scheduling Requests (SR).
- BSR indicate the current fill level status of the current transmit buffer.
Farhatullah Mohammed 77
LTE Bible
-
- Figure: Timing relations for Uplink Grants in TDD and FDD frame configuration #0 and #1.
- For FDD, the grant timing is straight forward. An uplink grant received in the sub-frame n triggers an
uplink transmission in the sub-frame n+4.
- This is the same timing relation as used by uplink retransmission triggered by PHICH.
- For TDD, the situation is different. Here the sub-frame n+4 may not be uplink sub-frame.
- Therefore for TDD configurations #1 6, the timing relation is modified in such a way that the uplink
transmission occurs in the sub-frame n+k, where k is the smallest value larger than or equal to 4 such
that the subframe n+k is the uplink subframe.
- This requires some processing time for the terminal as in the case of FDD, the delay is minimized from
the receipt of the uplink grant to the actual transmission.
- This implies that the time between the grant receipt and the uplink transmission may differ between
two subframes.
- Another downlink heavy configurations 1 5, the property is that the uplink scheduling grants can only
be received on some of the downlink subframes.
- In TDD configuration #0, there are more uplink sub-frames than downlinkn subframes, which has the
possibility to schedule transmissions in multiple uplink subframes from a single downlink sub-frame.
- Similar to downlink case, the uplink scheduler can exploit information about the channel conditions,
buffer status and priorities of the different data flows, and if some form of interference coordination is
employed in the neighbouring cells interference.
Farhatullah Mohammed 78
LTE Bible
Persistent Scheduling
- There are a couple of Data Transmission Scheduling Scheme in LTE. The most simple in terms of
algorithm would be the persisent scheduling. In this scheduling mode, Network send 'Grant' in DCI
Format 0 for every subframe.
i) Network send the first data on DL PDSCH and PDCCH which has DCI format 1 for DL Data Decoding and
DCI format 0 for UL Grant. (If there is no downlink data to be transmitted, network transmits only DPCCH
with DCI format 0 without any DPSCH data)
vi) UE send ACK/NAK for DL data through UCI (UCI will be carried by PUCCH)
ix) Network decode PUSCH data and send ACK/NACK via PHICH
- Overall flow can be illustrated as follows. This diagram would not show all the details but give you the big
picture for the procedure.
- For detailed data structure of DCI Format 0, refer to TS 36.212 section "5.3.3.1.1 Format 0"
- The process listed above is in reality a pretty complicated process and need a lot of troubleshoot and
debugging. So in case of development and testing phase, we normally break down this process into
multiple simple/small procedure and verifies it step by step.
Farhatullah Mohammed 79
LTE Bible
Step 1 : DL data reception and no ACK/NACK transmission ==
This would seem to be very simple two step process, but to make this happen UE is capable of doing step ii),
iii), iv) described above.
b) See if UE properly decode DCI Format 0 (You need to make it sure that Resource allocation that UE
decoded matches with DCI format 0 sent by network.)
To make this happen, UL DMRS for PUSCH should have been properly implemented and you have to make
it sure that UE transmit the PUSCH data on the RBs that DCI format 0 specified.
- In Persistent Scheduling mode, UE can send the data to Network anytime since Network is sending UL
Grant all the time. But what if Network does not send UL Grant all the time ? In this case, UE has ASK
the network to send UL Grant (DCI 0). If network send UL Grant, then UE can send UL data as allowed
by the UL Grant.
Farhatullah Mohammed 80
LTE Bible
- Overall procedure is as follows :
iii) UE decode DCI 0 and transmit PUSCH based on the RBs specified by DCI 0
vi) If Network send NACK, go to [Retransmission] Procedure ( For the details of [Retransmission] process,
refer to HARQ Process page)
Farhatullah Mohammed 81
LTE Bible
20.2 Uplink Priority Handling
- Multiple logical channels of different priorities can be multiplexed into the same transport
block using the same MAC multiplexing functionality in the downlink.
- Unlike the scheduling in downlink, where the prioritization is under the control of the
scheduler and upto the implementation, the Uplink multiplexing is done according to set of
well defined rules in the terminal as a scheduling grant applies to a specific uplink carrier of a
terminal and not specific to the radio bearer within the terminal.
- Using the radio bearer specific scheduling grants would increase the control signalling
overhead in the downlink and hence per-terminal scheduling is used in LTE.
- Here the simplest multiplexing rule would be to serve the logical channels in strict priority.
- This may result in the starvation of low-priority channels, as all the resources would be given
to higher priority channels until the transmission buffer is empty.
- However, the operators would like to provide atleast some throughput for low priority services
as well, therefore each logical channel in LTE terminal, a prioritized data rate value is
configured in addition to the priority values.
- The logical channels are then served in decreasing priority order upto their prioritized data
rate which avoids the starvation as long as the scheduled data rate is atleast as large as the
sum of prioritized data rates.
- Beyond the prioritized data rates, the channels are served in stricty priority until the grant is
fully exploited or the buffer is empty.
Farhatullah Mohammed 82
LTE Bible
- There is no need to provide uplink resources to the terminals with no data to transmit as
this would only result in the terminal performing padding to fill up the granted resources.
- Therefore the scheduler needs to know whether the terminal has a data to transm it and
should be given a grant, known as Scheduling Request .
- Scheduling Request is a simple flag raised by the terminal to request uplink resources
from the uplink scheduler.
- If the terminal requesting resources has no data to transmit on PUSCH, the Scheduling
request is made on PUCCH.
- With the dedicated scheduling mechanism there is no need to provide the identity of the
terminal requesting to be scheduled as the identity of the terminal is implicitly known from
the resources upon which the request is being transmitted. When the data with higher
priority is existing in the transmit buffers and new data arrives at the terminal and the
terminal has no grant and hence cannot transmit the data, the terminal transmits a
scheduling request at the next possible instant.
Farhatullah Mohammed 83
LTE Bible
- In frequency selective scheduling, the same localized allocation of the transmission resources is
typically used in both slots of the sub frame.
- There is no frequency hopping during the subframe.
- The MCS and frequency domain RB allocation are chosen based on the location and quality of
the above average gain in the uplink channel response.
- Frequency Selective scheduling required timely channel quality information at eNodeB which is
done by SRS.
- The performance of frequency selective scheduling using the SRS depends on the sounding
bandwidth and the quality of the channel estimate which is a function of transmitted power
spectral density used for SRS.
- With the large sounding bandwidth, link quality can be evaluated on large number of RBs.
- This can lead to SRS being transmitted at a lower power density, due to limited UE transmit
power which reduces the estimate for each RB within the sounding bandwidth especially for cell
edge UE.
- If a sounding smaller bandwidth can improve channel estimation on the sounded RBs can result
missing channel information for certain parts of channel bandwidth, thus risking the exclusion of
best quality RBs.
- Due to the limited or absence of frequency specific channel quality information, due to high
Doppler effect, it is preferable to exploit the frequency diversity of LTE wideband channel.
- In LTE, frequency hopping of a localized transmission in used to the provide frequency diversity.
- Two hopping modes are supported here- hopping between the subframes (inter-subframe
hopping) and hopping both between and within subframes (inter and intra subframes hopping).
- Intra-subframe hopping: Frequency hop occurs at the slot boundary in the middle of the
subframe; this provides frequency diversity within a codeword (within a single transmission of
transport block).
- Inter-Subframe hopping: It provides frequency diversity between HARQ retransmission of a
transport block as a frequency allocation hops every allocated subframe.
- Signalling the frequency hop via the uplink resource grant can be used for the frequency semi
selective scheduling in which the frequency resource is assigned selectively for the first slot of a
subframe and frequency diversity is also achieved by hopping to a different frequency in the
second slot.
-
-
Farhatullah Mohammed 84
LTE Bible
Link adaptation is the ability to adapt the modulation scheme and the coding rate of the error
correction according to the quality of radio link. If the condition of the radio link are good, high
level efficient modulation scheme and small amount of error correction is used.
Rank Indication:
- UE reports which precoding matrix should be used for downlink transmission which is
determined by R1.
- R1 and PMI can be configured to support MIMO operation for CL-SM and OL-SM SM.
- Periodic CQI reporting can be done on PUCCH and PUSCH and could be 2ms.
Farhatullah Mohammed 85
LTE Bible
22. Modulation Coding Scheme
Farhatullah Mohammed 86
LTE Bible
Farhatullah Mohammed 87
LTE Bible
23. Carrier Aggregation
Carrier Aggregation in LTE (CA):
Carrier Aggregation is a cost effective way to utilize the fragmented spectrum spread across
different or same bands in order to improve end user experience.
Intra-Band Contiguous CA
When two or more component carriers belong to same frequency band and they are
contiguous. There must be spacing of 300 khz x N between two contiguous component carriers
(N is integer). This is the simplest form of CA aggregation from operators perspective
Intra-Band Non-Contiguous CA
When two or more component carriers belong to same frequency band but they are separated
by one or more frequency gaps
Inter-Band Non-Contiguous CA
Farhatullah Mohammed 88
LTE Bible
Carrier Aggregation (CA):
- The spacing between center frequencies of contiguously aggregated component carriers will be a
multiple of 300 kHz to be compatible with the 100 kHz frequency raster of Release 8/9 and at the
same time preserve orthogonality of the subcarriers, which have 15 kHz spacing.
- For non-contiguous cases the CCs are separated by one, or more, frequency gap(s).
PCell Vs SCell:
- PCell always have both Uplink(UL) and Downlink(DL). Scell always have DL (While activated) but
may or may not have UL.
- PCell is always activated whereas SCell has to be activated or deactivated using MAC-CE.
- UE does not required to acquire System Information and decode Paging from SCell.
- For Scell SI is passed to UE while adding the Scell.
Farhatullah Mohammed 89
LTE Bible
- When an Scell is added using RRC Connection Reconfiguration Message it remains in the
deactivated state till it is activated using MAC-CE.
- If Scell activation/deactivation MAC-CE is received on Subframe n the Scell is
activated/deactivated on Subframe n+24 or n+34.(TS 36.133 Section 7.7.2)
- When sCellDeactivationTimer expires then Scell is deactivated.
- Once Scell is deactivated
- PDCCH on Scell and PDCCH for Scell is not monitored.
- PUSCH is not transmitted and PDSCH is not received.
- The SRS is not transmitted.
- The CQI/PMI/RI for Scell is not reported.
Activation/Deactivation MAC-CE:
- The MAC-CE can activate and deactivate Scell(s) which is already configured using RRC Connection
Reconfiguration Meassage.
- Control Element is identified by a MAC PDU subheader with LCID.
.
11011 Activation/Deactivation
- fixed size and consists of a single octet containing seven C-fields and one R-field.
- The Ci field is set to "1" to indicate that the SCell with SCellIndex i shall be activated.
- The Ci field is set to "0" to indicate thatthe SCell with SCellIndex i shall be deactivated.
Farhatullah Mohammed 90
LTE Bible
UE deactivates the Scell, if configured.
- TTI Bundling is not supported when configured with one or more Scell with Configured Uplink.
- The RSRP and RSRQ measurement for Pcell shall follow time domain measurement resource
restriction in accordance with measSubframePatternPCell, if configured.
Farhatullah Mohammed 91
LTE Bible
- Scell can be cross scheduled by Pcell or by other Scell.
- UE indicates whether it supports CCS or not.
- Cross Carrier Scheduling is not applicable for PDCCH order. It is transmitted on Pcell.
- CCS is applicable for aperiodic SRS transmission.
- The RadioResourceConfigDedicatedSCell-r10.PhysicalConfigDedicatedSCell-
r10.CrossCarrierSchedulingConfig-r10 indicates CCS status of Scell.
- cif-Presence indicates whether carrier indicator field is present (value TRUE) or not (value FALSE)
in PDCCH DCI formats.
- pdsch-Start indicates the starting OFDM symbol of PDSCH for the concerned SCell. Values 1, 2, 3
are applicable when dl-Bandwidth for the concerned SCell is greater than 10 resource blocks,
values 2, 3, 4 are applicable when dl-Bandwidth for the concerned SCell is less than or equal to 10
resource blocks.
- schedulingCellId Indicates which cell signals the downlink allocations and uplink grants, if
applicable, for the concerned SCell.(When Scell cross scheduled other Scell.)
Farhatullah Mohammed 92
LTE Bible
- For Event A1 and Event A2 The Carrier Frequency in Measurement Object indicates whether this
event is for Pcell or any Scell.
- The eNodeB shall configure separate A1/A2 events for each serving cell.
- Event A5 - Pcell becomes worse than theshold1 and neighbour becomes better than threshold2.
- For Event A3 and Event A5 the frequency mentioned in the associated measObjectEUTRA
indicates neighbours.
- Event B2 - Pcell becomes worse than theshold1 and inter RAT neighbour becomes better than
threshold2.
UE initiates a first MR immediately after the quantity to be reported becomes available for the
Pcell.
UE initiates a first MR immediately after the quantity to be reported becomes available for the
Pcell and for the strongest cell among the applicable cells.
- If (Purpose == reportStrongestCellsForSON)
UE initiates a first MR when it has determined the strongest cells on the associated frequency.
- UE shall be able to carry out Measurement on any serving frequency without measurement gap
i.e. intra-frequency measurement for any serving frequency.
Farhatullah Mohammed 93
LTE Bible
Typical CA Call Flow:
Farhatullah Mohammed 94
LTE Bible
24. Cell Search
Cell Search In LTE :
- eNodeB broadcasts Primary Synchronization Signal (PSS) and Secondary Synchronization Signal
(SSS) to help UE with the Cell Search Process and Cell Id detection.
- There is total 504 Cell Ids (0 - 503) defined in LTE.
- These 504 Cell IDs are grouped in 168 Physical Layer Cell Identity Group.
- Each Physical Layer Cell Identity Group Consists of 3 Physical Layer Cell Identity.
- PSS and SSS is transmitted using central 62 sub carriers around the DC. The 5 REs above and
below the Synchronization Signals are not used for transmission, i.e. they represents DTX periods.
Cell Id Identification:
- Once UE read the PSS and SSS, UE will be able to get the Cell ID from the Physical Layer Cell
Identity and Physical Layer Cell Identity Group.
- Cell ID = 3 * Physical Layer Cell Identity Group + Physical Layer Cell Identity.
Farhatullah Mohammed 95
LTE Bible
25. Cell Selection
The term 'Cell Selection Criterion' may be a vague expression, since there can be many different
criteria from many different perspective. In broad sense, cell selection would be influenced by
following factors.
ii) Is the PLMN of the cell acceptable to the UE ? (PLMN selection criteria)
iii) Is the service type of the cell acceptable to the UE ? (Service Type criteria)
But in most of the situation when we say "Cell Selection Criteria", it is likely to say the first
criteria (Signal Strength/Quality Criteria). This signal quality criterion as descrbed in 36.304 as
follows.
According to this criterion, UE would not start registration even though it sucessfully detected a
cell and even decoded MIB and SIBs unless the Srxleve > 0 and Squal > 0. So if a device does not
even initiate the PRACH process even when it successfully decoded all the MIB and SIBs, checking
on this criteria would be a good first step for the troubleshooting. (Of course, this is not the only
issues for this case. there may be USIM issue and Band Indicator Issue, PLMN issues etc).
Farhatullah Mohammed 96
LTE Bible
Out of the variables used in the equation, only Qrxlevmeas and Qqualmeas is the value UE really
measures when it turns on and most of other parameters are determined by a specific SIB (SIB1 in
LTE case) or calculated by some other predefined values.
Following is the part of LTE SIB1 which is related to Cell Selection Criterion and Cell Selection
Procedure. Following is overall information and functionality of SIB1 information element.
Q-RxLevMin
The IE Q-RxLevMin is used to indicate for cell re-selection the required minimum received RSRP
level in the (EUTRA)cell.
Corresponds to parameter Qrxlevmin in 36.304 [4]. Actual value Qrxlevmin = IE value * 2 [dBm].
q-RxLevMinOffset
In summary, the cell selection criteria (Signal Strength/Quality Criteria) can be illustrated as
follows.
Farhatullah Mohammed 97
LTE Bible
26. Channels
The information flows between the different protocols are known as channels and signals. LTE
uses several different types of logical, transport and physical channel, which are distinguished by
the kind of information they carry and by the way in which the information is processed.
Logical Channels: : Define whattype of information is transmitted over the air, e.g. traffic
channels, control channels, system broadcast, etc. Data and signalling messages are carried on
logical channels between the RLC and MAC protocols.
Transport Channels: Define howis something transmitted over the air, e.g. what are encoding,
interleaving options used to transmit data. Data and signalling messages are carried on transport
channels between the MAC and the physical layer.
Physical Channels: Define whereis something transmitted over the air, e.g. first N symbols in the
DL frame. Data and signalling messages are carried on physical channels between the different
levels of the physical layer.
Farhatullah Mohammed 98
LTE Bible
27. Master Information Block
- Master information block is one of the important message that is broadcasted by LTE eNodeB
irrespective of any user presence.
- MIB is first among other system information blocks which are broadcasted by eNodeB.
- MIB is transmitted using physical layer channel PBCH or Physical Broadcast channel on downlink.
- MIB is 24 bit information with the following information within,
- System Bandwidth (3bits)
- PHICH Information (3bits) [ Configuration]
1 bit to indicate normal PHICH or extended PHICH
2 bits to indicate PHICH Ng Value.
- System Frame number (8 bits)
- Reserved for future use (10 bits)
- Apart from information in the payload, MIB CRC also conveys number of transmit antennas used
by eNodeB.
- MIB CRC is scrambled or XORed with an antenna specific mask.
-
Farhatullah Mohammed 99
LTE Bible
28. System Information Blocks
SYSTEM INFORMATION BROADCASTS [SIB]
SIBs carry relevant information for UE which helps to access the cell, perform cell reselection,
information related to Intra, Inter frequency and Inter RATcell selections.
UNSUCCESSFUL
ELEMENTARY
INITIATING MESSAGE SUCCESSFUL OUTCOME OUTCOME
PROCEDURE
RESPONSE MESSAGE RESPONSE MESSAGE
Handover HANDOVER PREPARATION
Preparation HANDOVER REQUIRED HANDOVER COMMAND FAILURE
Handover Resource HANDOVER REQUEST
Allocation HANDOVER REQUEST ACKNOWLEDGE HANDOVER FAILURE
Path Switch PATH SWITCH REQUEST PATH SWITCH REQUEST
Request PATH SWITCH REQUEST ACKNOWLEDGE FAILURE
Handover HANDOVER CANCEL
Cancellation HANDOVER CANCEL ACKNOWLEDGE
ERAB Setup ERAB SETUP REQUEST ERAB SETUP RESPONSE
ERAB Modify ERAB MODIFY REQUEST ERAB MODIFY RESPONSE
ERAB RELEASE
ERAB Release COMMAND ERAB RELEASE RESPONSE
Initial Context INITIAL CONTEXT SETUP INITIAL CONTEXT SETUP INITIAL CONTEXT SETUP
Setup REQUEST RESPONSE FAILURE
Reset RESET RESET ACKNOWLEDGE
S1 Setup S1 SETUP REQUEST S1 SETUP RESPONSE S1 SETUP FAILURE
UE CONTEXT RELEASE UE CONTEXT RELEASE
UE Context Release COMMAND COMPLETE
UE Context UE CONTEXT UE CONTEXT MODIFICATION UE CONTEXT
Modification MODIFICATION REQUEST RESPONSE MODIFICATION FAILURE
eNB Configuration ENB CONFIGURATION ENB UPDATE CONFIGURATION ENB CONFIGURATION
update UPDATE ACKNOWLEDGE UPDATE FAILURE
MME Configuration MME CONFIGURATION MME CONFGURATION UPDATE MME CONFIGURATION
update UPDATE ACKNOWLEDGE UPDATE FAILURE
Write Replace WRITE PLACE WARNING WRITE-REPLACE WARNING
warning REQUEST RESPONSE
UNSUCCESSFUL
INITIATING
ELEMENTARY PROCEDURE SUCCESSFUL OUTCOME OUTCOME
MESSAGE
RESPONSE MESSAGE RESPONSE MESSAGE
HANDOVER HANDOVER REQUEST HANDOVER
HANDOVER PREPARATION REQUEST ACKNOWLEDGE PREPARATION FAILURE
RESET RESET REQUEST RESET RESPONSE
X2 SETUP X2 SETUP REQUEST X2 SETUP REQUEST RESPONSE X2 SETUP FAILURE
ENB
ENB CONFIGURATION CONFIGURATION ENB CONFIGURATION ENB CONFIGURATION
UPDATE UPDATE UPDATE ACKNOWLEDGE UPDATE FAILURE
RESOURCE STATUS RESOURCE STATUS RESOURCE STATUS
REPORTING INITIATION REQUEST RESOURCE STATUS RESPONSE FAILURE
CLASS 2: PROCEDURES
In LTE, MIB, SIB1, SIB2 is mandated to be transmitted for any cells. Since many of the SIB are
transmitted, it should be transmitted in such a way that the location (subframe) where a SIB is
transmitted should not be the same subframe where another SIB is transmitted.
ii) SIB1 is also transmitted at the fixed cycles (every 8 frames starting from SFN 0).
iii) All other SIB are being transmitted at the cycles specified by SIB scheduling information
elements in SIB1
You may notice that LTE SIB1 is very similar to WCDMA MIB.
Especially at initial test case development, you have to be very careful about item iii). If you set
this value incorrectly, all the other SIBs will not be decoded by UE. It means, even though all the
The MIB uses a fixed schedule with a periodicity of 40 ms and repetitions made within 40 ms. The
first transmission of the MIB is scheduled in subframe #0 of radio frames for which the SFN mod 4
= 0, and repetitions are scheduled in subframe #0 of all other radio frames.
Defines the 8 most significant bits of the SFN. As indicated in TS 36.211 [21, 6.6.1], the 2 least
significant bits of the SFN are acquired implicitly in the P-BCH decoding, i.e. timing of 40ms P-BCH
TTI indicates 2 least significant bits(within 40ms P-BCH TTI, the first radio frame: 00, the second
radio frame: 01, the third radio frame: 10, the last radio frame: 11). One value applies for all
serving cells (the associated functionality is common i.e. not performed independently for each
cell).
This means that even though SIB1 periodicity is 80 ms, different copies (Redudancy version : RV)
of the SIB1 is transmitted every 20ms. Meaning that at L3 you will see the SIB1 every 80 ms, but at
PHY layer you will see it every 20ms. For the detailed RV assignment for each transmission, refer
to 36.321 section 5.3.1 (the last part of the section)
The transmission cycles for other SIBs are determined by schedulingInfoList in SIB1 as shown in
the following example (This example is the case where SIB2 and 3 are being transmitted).
One thing you would notice that sib-MappingInfo IE in the first node is not specified, but the first
entity of schedulingInfoList should always be for SIB2 as specified in the 36.331 as follows (See
36.331 SystemInformationBlockType1 field description).
Understanding overall cycle in the unit of Subframe number is pretty straightforward to understand.
But understanding exactly at which subframe a SIB should be transmitted is not that
straightforward as you might think. It is related to 'si-WindowLength'. si-WindowLength tells that a
SIB should be transmitted somewhere within the window length starting at the SFN specified by si-
Periodicity. But this parameter does not specify the exact subframe number for the transmission.
The subframe for a specific SIB transmission is determined by a algorithm defined in 36.331 5.2.3
Acquisition of an SI message as follows.
1> determine the start of the SI-window for the concerned SI message as follows:
2> for the concerned SI message, determine the number n which corresponds to the order of entry
2> the SI-window starts at the subframe #a, where a = x mod 10, in the radio frame for which SFN
mod T =
1> receive DL-SCH using the SI-RNTI from the start of the SI-window and continue until the end of
the SI-window
whose absolute length in time is given by si-WindowLength, or until the SI message was received,
excluding the
following subframes:
1> if the SI message was not received by the end of the SI-window, repeat reception at the next SI-
window occasion
Following is a SIBs captured from a live network. Go through the capture and check if it matches your
understanding.
0, 1, 1A,1B,1C,1D,2,2A,3,3A
Format 1 : Used for scheduling PDSCH codeword. Only single TB can be scheduled here using resource
allocation type0/type1.
Format 1A: Used for scheduling PDSCH codeword. Only single TB can be scheduled here using
resource allocation type2.
Format 1B: Used for scheduling PDSCH codeword with Rank 1 assignment.
Format 1C: Very compact scheduling of PDSCH code word. Only single TB can be scheduled here using
the resource allocation type 2 distributed always.
Format 2A: Used for scheduling PDSCH in open loop spatial multiplexing.
Format 3A: Uplink transmit power control with 1 bit power adjustment.
UL Grant is another name of DCI format 0. (Many people get confused by the name of "DCI format
0". They think DCI format 0 would be some information about downlink data transmission, but
keep in mind that DCI format 0 is a control information about uplink data transmission).
UL Grant (DCI format 0) carries the following information and the most important information is
'Resource Allocation' and MCS. UE should transmit the data using RBs and MCS specified in this
DCI 0.
SR is a special Physical Layer message for UE to ask Network to send UL Grant (DCI Format 0) so
that UE can transmit PUSCH.
Overall SR process (when to send SR) is controlled by MAC layer as illustrated below. (See 36.321
5.4.4 for details)
Once SR is transmitted and eNB recieves it, eNB should send UL Grant(DCI 0) and UE has to send
PUSCH in response to the UL Grant. The timing among SR, UL Grant, PUSCH varies on whether it is
FDD or TDD.
The timing and physical control channel configuration for SR transmission can be configured in
higher layer signaling message (e.g, RRC Connection Setup as shown below)
sr-ConfigIndex : This IE is used to determine the subframe where SR shall be transmitted based on
following table and formula.
< 36.213 Table 10.1.5-1: UE-specific SR periodicity and subframe offset configuration >
dsr-TransMax : Maximum number of SR transmission count (See 36.321 5.4.4 Scheduling Request)
- Paging is used by the network to communicate with the User Equipment in idle mode.
- In these situations, the network does not know on which cell UE is camped.
- Lte network uses paging to notify UE in idle mode of incoming data session, system information
change and ETWS notifications.
- There are two types of paging:
- CN initiated paging
- eNB initiated paging.
- In case of CN initiated paging, eNB receives S1AP paging message from MME and determines
the paging occasion (PO) where UE monitors PCCH.
- The paging identifies are queued separately for each PO.
- In case of ENB initiated paging due to ETWS notification or system information change , paging
is sent on all paging occasions.
- UE decode the content (Paging cause) of the paging message and UE has to initiate the
appropriate procedure.
Paging Mechanism:
- During the idle mode, UE gets into and stay in sleeping mode defined in DRX cycle.
- DRX cycle is defined in SIB 2.
- UE periodically wake up and monitor PDCCH in order to check for the presence of paging
message. (UE looks for any information encrypted in P-RNTI)
- If PDCCH indicates that paging message is transmitted in the subframe, the UE needs to
demodulate PCH to see the paging message is directed to it.
- Paging messages are sent by MME to all eNodeB in a tracking area and those eNodeB in the
tracking area is transmitting the same paging message.
Paging Occasion and Paging Frame:
- There are two terminologies which is Paging frame (PF) and Paging Occasion (PO).
- Paging Occasion (PO) is a subframe where there may be P-RNTI transmitted on PDCCH
addressing the paging message.
- Paging Frame (PF): is one frame, which contain one or multiple paging occasions.
- The parameters used to calculate PO and PF is UE_ID: IMSI mod 1024
- UE_ID: is the index value parameter of PAGING message initiated by MME-S1AP.
- Since network node MME knows about UE IMSI, it will calculate UE_ID and send it to eNodeB
S1AP part of paging message.
- In LTE, DRX mode can be enabled in both RRC_IDLE and RRC_CONNECTED states.
- The UE is registered with the evolved packet system mobility management (EMM_REGISTERED)
but does not have an active session (ECM_IDLE).
- Idle mode DRX configuration is broadcast within System Information Block 2(SIB2).
- Idle mode DRX configuration is used to calculate Paging Frame(PF) and Paging Occation(PO).
- One Paging Occasion (PO) is a subframe where there may be P-RNTI transmitted on PDCCH
addressing the paging message.
- One Paging Frame (PF) is one Radio Frame, which may contain one or multiple Paging Occasion(s).
-When DRX is used the UE needs only to monitor one PO per DRX cycle.
T : DRX cycle of the UE. T = min(The UE specific DRX , Default DRX value).
The UE specific DRX value allocated by upper layers, and default DRX value broadcast in system
information.
If UE specific DRX is not configured by upper layers, the default value is applied.
N: min(T,nB)
nB: Broadcast within System Information Block 2(SIB2) and can take values 4T, 2T, T, T/2, T/4, T/8,
T/16, T/32.
Index i_s pointing to PO from subframe pattern defined below will be derived from following
calculation:
- DRX is a method by which the UE can switch off its receiver for a period of time.
- if DRX is configured, the UE is allowed to monitor the PDCCH discontinuously in RRC Connected
state.
- Controls the UEs PDCCH monitoring activity for the UEs C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-
RNTI and Semi-Persistent Scheduling C-RNTI (if configured).
- In the RRC_CONNECTED state DRX mode is enabled during the idle periods during the
- If the UE is configured with DRX, the UE may delay the measurement reporting for event
triggered and periodical triggered measurements until the Active Time.
- cqi-Mask - Limits CQI/PMI/PTI/RI reports to the on-duration period of the DRX cycle.
DRX Cycle :
DRX Configuration:
onDurationTimer :
- If both Long DRX and Short DRX is configured for a particular UE, onDurationTimer i.e. on
duration time during Short DRX cycle or Long DRX cycle should be same.
- If (Short DRX Cycle) && If ([(SFN * 10) + subframe number] modulo (shortDRX-Cycle) ==
(drxStartOffset) modulo (shortDRX-Cycle))
or
- If (Long DRX Cycle) && If ([(SFN * 10) + subframe number] modulo (longDRX-Cycle) ==
drxStartOffset)
- start onDurationTimer.
drx-InactivityTimer :
- During Active time if UE receives PDCCH indicates a new transmission (DL or UL) drx-
InactivityTimer started or restarted.
drx-RetransmissionTimer :
longDRX-Cycle :
shortDRX-Cycle :
- It is a optional one.
drxShortCycleTimer :
Active Time:
Uplink grant for a pending HARQ re-transmission can occur, and there is data in the
corresponding HARQ buffer.
A PDCCH indicating a new transmission addressed to the C-RNTI of the UE has not been
received after successful reception of a RAR for the preamble not selected by the UE i.e.
Dedicated RACH.
- DRX Command MAC control element is identified by a MAC PDU subheader with LCID (11110).
- The Buffer Status reporting procedure is used to provide the serving eNB with information about
the amount of data available for transmission in the UL buffers of the UE.
Type Of BSR:
- UL data, for a logical channel which belongs to a LCG, becomes available for transmission in the
RLC entity or in the PDCP entity and either the data belongs to a logical channel with higher priority
than the priorities of the logical channels which belong to any LCG and for which data is already
available for transmission, or there is no data available for transmission for any of the logical
channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR".
- UL resources are allocated and number of padding bits is equal to or larger than the size of the
Buffer Status Report MAC control element plus its subheader, in which case the BSR is referred
below to as "Padding BSR".
- retxBSR-Timer expires and the UE has data available for transmission for any of the logical
channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR"
- periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".
If (More than one LCG has data available for transmission in the TTI where the BSR is transmitted)
If (Number of padding bits => size of the Short BSR plus its subheader) && If (Number of padding
bits < size of the Long BSR plus its subheader)
If (More than one LCG has data available for transmission in the TTI where the BSR is transmitted):
Then :
Report Truncated BSR of the LCG with the highest priority logical channel with data available for
transmission;
Else
- As mentioned in the LTE SRB table, there are three types of SRB in the LTE technology.
SRB0 used to transfer RRC messages which use CCCH channel.
SRB1 used to transfer RRC messages which use DCCH channel.
SRB2 used to transfer RRC messages which use DCCH channel and encapsulates a NAS message.
- SRB1 is also used to encapsulate NAS message if SRB2 has not been configured.
- SRB2 has lower priority then SRB1 and it is always configured after security activation
- SRB0 uses transparent mode RLC while SRB1 and SRB2 use acknowledged mode RLC.
SystemInformationBlockType1 DLInformationTransfer
Signalling radio bearer: N/A Signalling radio bearer: SRB2
RLC-SAP: TM or SRB1 (only if SRB2 not
Logical channel: BCCH established yet. If SRB2 is
Direction: E-UTRAN to UE suspended, E-UTRAN does not
send this message until SRB2
RRCConnectionRequest is resumed.)
Signalling radio bearer: SRB0 RLC-SAP: AM
RLC-SAP: TM Logical channel: DCCH
Logical channel: CCCH Direction: E-UTRAN to UE
Direction: UE to E-UTRAN
Paging
Signalling radio bearer: N/A
RRCConnectionSetup
RLC-SAP: TM
Signalling radio bearer: SRB0
Logical channel: PCCH
RLC-SAP: TM
Direction: E-UTRAN to UE
Logical channel: CCCH
Direction: E-UTRAN to UE
RRCConnectionSetupComplete
Signalling radio bearer: SRB1
RLC-SAP: AM
Logical channel: DCCH
Direction: UE to E-UTRAN
RRCConnectionReconfiguration
Signalling radio bearer: SRB1
RLC-SAP: AM
Logical channel: DCCH
Direction: E-UTRAN to UE
MeasurementReport
Signalling radio bearer: SRB1
RLC-SAP: AM
Logical channel: DCCH
Direction: UE to E-UTRAN
MobilityFromEUTRACommand
Signalling radio bearer: SRB1
RLC-SAP: AM
Logical channel: DCCH
Direction: E-UTRAN to UE
UECapabilityEnquiry
Signalling radio bearer: SRB1
RLC-SAP: AM
Logical channel: DCCH
Direction: E-UTRAN to UE
41. Intercell Interferece Coordination - ICIC
- ICIC allows neighbouring eNodeB to exchange load information to help coordinate the use of both
uplink and downlink resources.
- ICIC is introduced to deal with interference issues at cell edge.
- ICIC mitigates interference on traffic channels only.
- ICIC uses power and frequency domain to mitigate cell edge interference from neighbor cells.
TYPES:
- No two neighbgour eNodeB will use same resource assignments for their UE. This improves cell Edge
SINR. The disadvantage is decreased cell throughput, Since full resource blocks are not being utilized.
- All eNodeB utilize complete range of resource blocks for centrally located users but for cell edge users,
no two neighbours uses the same set of resource block at a given time.
- eNodeB can use power boost for cell edge users with specific set of resources(not used by neighbours)
while keeping low signal power for center users with availability of all resource blocks.
LTE Bible
42. Transmission Modes
Multiple Input Multiple Output:
- 7 modes of MIMO
- Key factor to performance of the MIMO is spatial layers of wireless channel which determines
the ability to improve spectral efficiency.
- Increase in data rate of MIMO system is linearly proportional to minimum number of transmit
antennas and receive antennas.
- The transmit and receive antennas are subject to the limit of rank of the propagation channel
estimate.
- Rank is the measure of the number of independent spatial layer.
- 4 Tx/2 Rx antenna MIMO system provides double data rate (min 4,2)=2 gives two spatial layers
(rank =2) in wireless channel.
- In LOS, the channel matrix rank =1, even with 4 antennas we cannot increase spectral efficiency.
-
- Mode 1: Single Antenna Port, Port 0
- One transmit and one receive antennas with one or more antennas (SISO or SIMO)
- Mode 2: Transmit Diversity
- Transmission of same information stream on multiple antennas.
- Information stream is coded differently on each antennas using so-called Space Frequency Code
Block codes (SFBC).
- SFBC repeats data symbols over different subcarriers on each antenna.
- This mode is used by LTE by default for broadcast channel and common control channels.
- It is single layer transmission, but does not improve peak rate.
- Mode 3: Open Loop Spatial Multiplexing OL-SM
- In this case two information streams (2 code words) are transmitted over two or more
antennas.
- There is no feedback from UE.
- Transmit Rank Indication (TRI) transmitted by UE is used by eNB to select spatial layers.
- OL-SM provides better peak throughput than transmit diversity.
- Mode 4: Closed Loop Spatial Multiplexing CL-SM:
- Similar to OL-SM, two streams are transmitted over 2 code words from N antennas (upto 4).
- In CL-SM, PMI is feedbacked from UE to eNB.
- Feedback mechanism allows transmission to precode the data and optimize transmission on
wireless channel.
- Mode 5: Multiuser MIMO
- Multiuser MIMO is similar to CL-SM , but the information streams are targeted at different
terminals.
- Multiple users share the same resources.
Synchronization is the first step in which UE wants to camp on to any cell. From synchronization
UE is able to acquire Physical Cell Identity (PCI), time slot and frame.
UE will tune its radio by turning to different frequency channels depending on which band to
select that UE supports.
PSS is repeated in subframe 5, which means UE is synchronized on 5ms basis since subframe is
1ms.
SSS is also located in the same subframe of PSS, but in symbol before PSS.
Using the physical layer identity and physical layer group number, UE knows PCI.
In LTE 504 PCIs are allowed and are divided into 168 cell layer groups which consist of three
physical layer identity.
PCI = 3 (SSS from 0 to 167) + PSS(from 0,1,2) (***PCI ranging from 0 to 503)
-
- LTE Downlink Reference Signals
- The CSRS is a QPSK modulated sequence.
-
- The downlink reference signal in LTE corresponds to the set of resource elements used by the
higher layer but does not carry any higher layer information.
- To allow the coherent demodulation at the user equipment, reference symbols are used at the
OFDM time frequency grid to allow channel estimation.
- Two downlink RS are inserted from the first and third from last OFDM symbol of each slot.
- Both of the signals have frequency domain spacing of six sub carriers within the same symbol.
- Uplink Reference Signals:
Farhatullah Mohammed 136
LTE Bible
- Uplink reference signals are used with the PHY layer and do not convey information from higher
layers.
- There are two main types of reference signals Sounding Reference Signals and Demodulation
Reference Signals.
- Demodulation Reference signals:
- This facilitates coherent demodulation and associated with transmission of PUSCH or PUCCH. It
is transmitted in fourth SC-FDMA symbol of the slot and is the same sign as the assigned
resource.
- DMRS is intended for specific terminal and is only transmitted in the resource blocks assigned
for the transmission to that terminal.
- Demodulation reference signals are intended to be used for channel estimation for PDSCH
transmissions for the case when cell specific reference signals are not used.
-
- Sounding Reference Signals:
- This is used to facilitate frequency dependent scheduling and not associated with the
transmission of PUSCH or PUCCH. Both variants of the UL are based on Zadoff Chu sequences.
- SRS signals are of two types based on periodicity. The minimum periodicity is of 2ms and max
periodicity is of 320ms.
- The similarity between the SRS and DMRS is that both of them use CAZAC sequences(Constant
Amplitude Zero Autocorrelation sequences).
RS-BandwidthConfig:(C-SRS)
- Broadcast on SIB2.
- Value from 0-7.
- Common to all UE within the Cell
SRS-Bandwidth:(B-SRS)
- Can be included in RRC Connection Reconfiguration Message.
- Can take values 0-3
- Can be UE specific.
According to 36.211:
M-SRS : No of Resource Block over which the Sounding Reference Signal is Transmitted.
N0 - N3: One of parameter to decide the Starting position of the SRS in the Frequency Domain.
FreqDomainPosition: Received in RRC Connection Reconfiguration Message also has an impact on the
Starting Position In The Frequency Domain.
SRS-SubframeConfig & SRS-ConfigIndex: The set of Subframes within which the SRS is transmitted is
determined by Cell Specific SRS-SubframeConfig in SIB2 and UE specific SRS-ConfigIndex within in RRC
Connection Reconfiguration Message.
SRS-SubframeConfig:
- Takes a value between 0-14.
- Common within the Cell.
- Talks about in which subframe(s) SRS can be transmitted.
According to 36.211:
SRS-ConfigIndex: (I-SRS)
According to 36.213:
where,
nf = SFN No (0-1023).
k-SRS= SF No (0-9).
Duration:
- Received in RRC Connection Reconfiguration Message.
- Takes a value TRUE or FALSE.
- TRUE - UE should Continue Transmitting SRS until instructed otherwise.
- FALSE - UE should complete only a Single Transmission.
TransmissionComb:
- Received in RRC Connection Reconfiguration Message.
- Allows 2 UE to Frequency Multiplex their SRS with in the Same Resource Block
CyclicShift:(n-CS-SRS)
SRS-HoppingBandwidth:(B-hop)
For decoding any downlink data, the first step is to detect/decode reference signal. If the power
of this reference signal is same as all other channel power, it would not be easy (though not
impossible) to detect it. So more practical implementation is to make Reference Signal
outstanding comparing to other channels as shown in the red bar in the following plot (you see a
certain degree of offset, P_A between Reference Signal and other channel power).
However there is a complication with this method and it is because the reference channels occurs
only in specific symbols, not in every symbols. It means that there are some symbols with
reference signal in it and there are some other symbols without reference signal in it. It implies, if
you measure the power of each symbol, some symbol (symbol with reference signal) has higher
power than the other symbols (symbol without reference signal). This would cause some
complication on the implementation of reciever equalizer.
To solve this problem of power difference between two groups of symbols, we can put lesser
power to the non-reference signal channels at the symbol carrying reference signal. Due to this,
you see another type of offset P_B in the plot shown below.
Combining all of these factors, we have pretty complicate peak-and-valley type of power terrain
rather than the flat plain terrain in downlink power allocation.
Power offset between PDSCH channel in the symbols with reference signal and PDSCH channel in
the symbols without reference signal (P_B) is specified in SIB2 as follows.
Power offset between the Reference Signal and PDSCH channel in the symbols without reference
signal (P_A) is specified in RRC Connection Setup as follows. P_A is UE specific power offset. This is
why this is specified by RRC Connection Setup message.
In Physical Layer performance test, we set Rho A, Rho B as a test condition and the relationship
between Rho A/Rho B and P_a/P-b is as follows.
Normally P_B is specified first by SIB2 and P_A is determined by following table and specified in
RRC message (e.g, RRC Connection Setup, RRC Connection Reconfiguration) according to following
table.
Examples:
- Uplink power parameters are changed in order to decrease the interference and the service
drop and enhance RRC rate.
Adjust UE Transmission to compensate for channel fading.
Reduces cell interference.
Avoid UE from transmitting excessive power.
Maximizes uplink data rate.
eNB radio receive Power maintained for optimum SINR.
Prolongs UE battery life.
- The terminal transmits power depending upon estimate of downlink path loss and channel
configuration.
- OL-PC is used for
- PRACH and initial access
- PUSCH and PUCCH as part of power control.
- () = { , + () + .
- It controls the terminal transmit power by means of power command in the downlink.
- PUSCH and PUCCH as part of power control of UL.
Some of the most confusing power concepts are RSRP, EPRE and total power. Definition and
Differences among these powers can be illustrated as follows. For the simplicity, I use the structure
of only one RB and TM1 (Single Antenna)
Directly or indirectly from this illustrations, you can infer some additional facts as follows :
EPRE indicate power for one resource element (RE). This can be used for any channel (e.g,
Reference Signal, PDSCH etc). This value does not vary with system bandwidth or number of RBs.
RSRP is an averaged value for all the Resource Elements for Reference Signal within a symbol. Since
this is the averaged value, the value would be similar to EPRE value you set for the Reference Signal.
If there is no noise at all, RSRP would be same as EPRE you set for Reference Signal.
Total Channel Power is summed value of all EPREs within a symbol. This value may vary with
different symbols since each symbol may have different channel combination (e.g, Symbol 0 in first
slot is made up of multiple component - PCFICH, HICH, RS. Symbol 4 is made up of PDSCH and
Reference signal).
= EPRE for PDSCH x Number of RB x 12 (assuming for the symbol with no Reference Signal)
Total Power is not affected by the system bandwidth, it is affected by number of RBs being used at
the specific moment of the calculation.
For example, if you allocated -90 dBm/EPRE for PDSCH and allocated 100 RBs for the PDSCH, the
Total Power of PDSCH become as follows.
= -90 + 30.8
= - 59.2 dBm
3 types of GTP:
- GTP-C
- GTP-U
- GTP
- It provides mobility
- When UE is mobile, IP address remains same packets are still forwarded since the tunnelling is
provided between P-GW and eNB via S-GW.
- Multiple tunnels can be used by same UE to obtain different QoS.
- Main IP is hidden, so it provides more security.
- Creation, establishment, modification and termination of tunnels in case of GTP-C.
- Header compression and decompression for all user plane data packets.
- This is based on RoHC- Robust Header Compression protocol which stores static part of the
header.
- The dynamic part is compressed by transmitting the difference from the reference.
- RoHC is especially important for the voice services where IP/UDP and RTP header comprises a
large number of actual packet size.
- It also does handover management: reorders and sequences PDU during a handover from one
cell to another.
- There are two types of handovers:
- Seamless handover and
- Lossless handover.
- Seamless Handover: applies to control plane data and RLC- UM user plane data that is tolerant
to loss but not delay such as voip. This handover is relatively simple and designed to minimize
the delay as no security context is exchanged between the source and the target eNodeB during
handover.
- PDCP SDU that has not been transmitted are forwarded over the X2 interface for transmission
by target eNodeB.
- PDCP SDU that has not been transmitted are buffered and transmitted after the handover is
complete.
- Lossless Handover: This mode is used for the delay tolerant data but are sensitive to loss such as
file download where it is desired to minimize the packet loss to save bandwidth utilization and
enhance the data rate.
- This handover applies to RLC-AM bearers.
- In this mode, a sequence number is used to provide lossless handover by retransmitting PDCP
PDU that has not been acknowledged prior to handover.
- PDCP also provides encryption and decryption services for control plane and user plane data in
addition to integrity protection and verification of control plane data.
In the transmit path, RLC tasks with reformatting PDCP PDU- referred as segmentation and/or
concatenation to fit the size required by MAC layer (Transport Block TB).
RLC communicates with PDCP through Service access points(SAP) and MAC through logical
channels.
Unacknowledge Mode: This mode is used for delay sensitive traffic such as VoiP. Multimedia
Broadcast/ Multicast service (MBMS) also uses this mode. In this mode, the layer performs
segmentation and concatenation of RLC SDU , reordering and duplicate detection of RLC PDU
and reassembly of RLC SDU.
Acknowledge Mode(AM): This mode is used to support delay tolerant but error sensitive
traffic(non real time traffic suchas web browsing). It allows bidirectional data transfer where RLC
can transmit and receive data. It features ARQ applies to correct erroneous traffic.
MAC layer performs important functions that includes the scheduler which distributes the
available bandwidth to number of active UE.
RACH Procedure is a MAC layer function which is used by UE that is not allocated with uplink
radio resources to access and synchronize with the network.
MAC layer performs uplink timing alignment which ensures UE transmissions do not overlap
when received at the base station.
Discontinuous reception DRX is implemented at MAC layer to save battery power by limiting
the time.
MAC implements HARQ operation to retransmit and combine received data blocks, and
generate ACK/NACK signalling in case of CRC failure.
MAC layer maps the RLC data received through logical channels onto transport channels
connecting MAC with PHY layer.
- MAC control elements are always placed before any MAC SDU.
MAC CE Header:
00000 CCCH
01011- Reserved
11010
11011 Activation/Deactivation
11100 UE Contention
Resolution Identity
11111 Padding
00000 CCCH
01011- Reserved
11000
11011 C-RNTI
11111 Padding
- If extendedBSR-Sizes is not configured, the values taken by the Buffer Size field are in Table 6.1.3.1-
1(3GPP TS 36.321). If extendedBSR-Sizes is configured, the values taken by the Buffer Size field are in
Table 6.1.3.1-2(3GPP TS 36.321).
R=0
R=0
E=1
R=0
E=0
R=0
R=0
E=1
R=0
R=0
E=0
R=0
R=0
E=1
R=0
R=0
E=0
- UE Contention Resolution Identity: This field contains the uplink CCCH SDU.
R=0
R=0
E=1
- The Ci field is set to "0" to indicate that the SCell with SCellIndex i shall be deactivated.
R=0
E=0
Mission critical systems recognize that their components inevitably fail and plan accordingly. Any
individual component that would disrupt service when it dies is known as a single point of failure.
Effective contingency plans eliminate (within practical capabilities) single points of failure. Consider
the connectivity between a hypothetical Cell Site and Mobile Switching Office (MSO) illustrated in
Figure 1. Its been decked out with redundant routers at both the cell site and the switching office. It
also has two independent links between the sites Ethernet and SONET. Each of the nodes has two
network interfaces (IP addresses shown). It appears to have eliminated all single points of failure;
communications between the eNodeB and MME cannot be disrupted by the failure of any single
component. Looks can be deceiving, however.
Figure 1 Cell site with redundant connectivity to the Mobile Switching Office
Where TCP Comes Up Short
The concept of a TCP connection is fundamental to the operation of the protocol. The connection
embodies all of the state information needed by the congestion control, sequential delivery and error
recovery algorithms. TCP connections are identified by the IP address and TCP port number of the
source and destination nodes. Figure 2 illustrates three TCP connections between the eNodeB and the
MME. TCP connection [192.0.2.125:14457, 198.51.100.65:34851] uses one network interface on each
device. TCP connections [192.0.2.10:36412, 198.51.100.39:36412] and [192.0.2.10:24500,
198.51.100.39:18479] use the other network interface.
When UE is powered ON, UE does not have any resources or channel available to inform, so it
will sent request over a shared medium.
- There is possibility of collision among the request coming from various UE.
- Contention based RACH process user RACH preambles.
- There are 64 RACH preambles.
Non Contention Based or Contention Free RACH:
- In contention free, network informs UE to use some unique identity to prevent its request from
colliding with request from UE.
- Second scenario is called as non contention based RACH.
- Mostly used in Handover (UE), where eNB informs about which preamble it can use, since UE is
already in connected state.
- Contention Based procedure involves the UE selecting a Random Access Resource i.e. UE
selecting a PRACH resource, a Preamble Sequence and the next available Subframe for PRACH
transmission.
- Non-Contention Based procedure involves the eNodeB allocating the Random Access Resource
i.e. eNodeB allocating ra-PreambleIndex and ra-PRACH-MaskIndex.
- Contention Based RACH Procedure can be applicable for all RACH reasons but Non Contention
Based RACH Procedure can be applicable for :
- Completing an Intra-System Hand Over.
- Downlink data arrives while UE is in Non-synchronized RRC Connected State.
RACH Procedure:
Step1: MSG1
- eNodeB sends Random Access Response to UE on DL-SCH (Downlink shared channel) addressed
to RA-RNTI calculated from the time slot in which preamble was sent.
- The message carries following information:
- Temporary C-RNTI: eNB gives another identity to UE which is called as temporary CRNTI for
further communication.
- Timing advance value: eNB also informs UE to change its timing so it can compensate for the
round trip delay caused by eNB.
- Uplink grant resource: eNodeB assigns initial resources to UE so it can use UL-SCH.
Step3: MSG3:
- eNodeB responds with contention resolution message to UE whose message was successfully
received in step3.
- This message is address towards TMSI or random number but contains CRNTI which will be used
for further communication.
RACH Configurations:
- There are 64 preambles sequence available. Range is from 4 to 64, others are reserved for non
contention based.
- Size of RA Preambles: the RACH preambles are divided into two groups.
- Group A: Group A preambles are intended for sending small packets and group B are intended
for sending large packets. Range is from 4 to 60.
- Message size of group A is 56, 144, 208 or 256 bits.
- Power ramping step: Power offset selecting preamble group B (0,5,8,10,12,15 and 18dB).
Power Ramp:
56. UE Categories
- Figure 1: EPS and Legacy core networks Figure 2: CSFB to UTRAN/GERAN Figure 3: Return to EUTRAN (LTE)
-
-
- But if the combination of these two
packages still does not give us the
complete information, the process must
continue - and another 'NACK' is sent.
-
-
- The transmission continues, and is sent a
package [2]. The package [2] arrives, but let's
consider now that it arrives with errors. If the
package [2] arrives with errors, the receiver
sends a 'NACK'. -
-
- And there we have another
retransmission. Now the transmitter
sends a third package [2.2].
- Let's consider that now it is 'OK', and the
receiver sends an 'ACK'.
-
-
- Only now this package [2] (bad) is not thrown
away, as it is done in conventional ARQ. Now
it is stored in a 'buffer'.
-
-
- -
- Continuing, the transmitter send another - Here we can see the following: along
package [2.1] that also (let's consider) arrives with the received package [2.2], the
with errors. receiver also has packages [2] and [2.1],
that have not been dropped and are
stored in the buffer.
GUMMEI
- If we combile PLMN-ID with the MMEI then we arrive at a Globally Unique MME
Identifier (GUMMEI), which identifies an MME anywhere in the world:
- Finally adding the MME group identity and the PLMN identity with S-TMSI results in
the Globally Unique Temporary Identity (GUTI).
Introduction
The motivation for TTI bundling which is illustrated in Figure 1 is the low transmission
power of some handsets, short TTI length, and the long RTT of the HARQ
transmissions. TTI bundling is expected to improve the UL coverage of applications like
VOIP over LTE wherein low power handsets are likely to be involved. This feature has
more relevance for TDD over FDD as coverage issues are likely to be more challenging
in TD-LTE. Simulation results reported in publications indicate a 4 dB gain due to TTI
bundling on the UL.
Alternative Approach
The alternative to TTI bundling is RLC segmentation wherein a VOIP payload is split into
smaller size RLC PDUs as shown in Figure 2. The smaller RLC PDUs will result in smaller
transport blocks which can be decoded with better accuracy. One drawback of this
method is the potential overhead increase due to RLC segmentation due to multiple
RLC headers needed. For a typical VOIP payload, it has been shown that as we
increase the segmentation factor from 1 to 8, the overhead increases from 14% to
55%. Each RLC PDU which is mapped into a transport block will need a separate
Farhatullah Mohammed 175
LTE Bible
PDCCH assignment message which will contribute to control signal overhead for such a
scheme. There might be retransmissions of each of those transport blocks which will
also potentially increase the control signaling overhead. In addition, since we are
transmitting many small transport blocks, the chances of interpreting a NACK as a ACK
also increases proportionately with the increase in the RLC segmentation size. Hence,
RLC segmentation has many disadvantages when we consider the transmission of a
VOIP like payload from a power limited terminal.
Summary: TTI bundling is a useful technique for improving coverage of VOIP handsets
in LTE systems. It is applicable to both FDD and TD-LTE deployments and can improve
the link budget by up to 4 dB. Differences in implementation exist between FDD and
TD-LTE systems. TTI bundling helps achieve good latency performance for VOIP even
at the edges of cells.
-
- MIB: System Frame number, Channel Bandwidth and PHICH information are included
- SIB: Cell specific information are included for system operation except MIB
information.
- SIB1: Cell access configuration, frequency band indicator, scheduling information for
system other SIB and systemInfoValue tag.
- SIB2: Radio configuration information are included (PUCCH, PUSCH, SRS etc)
-
- DOWNLINK DATA TRANSMISSION PROCEDURE:
- UE Transmits CQI periodically CQI(Channel Quality indicator) which is DL channel
status after receiving CQI resource allocation per UE.
- eNodeB allocates PDSCH considering DL channel status of UE and DL buffer status.
Transmit information of PDSCH allocation per specific subframe with PDCCH.
-
- When CRC is OK on PDSCH detection result in UE, transmit ACK to eNB.
Farhatullah Mohammed 178
LTE Bible
Transmit ACK info. on PUSCH when PUSCH is allocated.
In other cases, Transmit ACK info on PUCCH.
- UPLINK DATA TRANSMISSION PROCEDURE:
- UE transmits periodically SRS signal after receiving SRS resource allocation per UE.
- eNodeB allocates PUSCH resource considering UL channel status and UE and BSR.
- When CRC is OK on PUSCH detection result in UE, transmit ACK to eNB.
Transmit ACK using PHICH (Downlink Detection).
-
- *** BSR BUFFER STATUS REPORT
- HANDOVER PROCEDURE
- UE sends measurement report to the serving cell with the condition of comparing
Neighbour cell signal and serving cell signal.
- If the serving cell transmit handover command message to UE, UE orders target call
to be handover.
-
-
Just from the user's point of view, we can think of several user model as described below.
i) UE is in connected mode with LTE network while there is no WiFi Network Available.
Note : I should say this is over-simplified description. You may have a lot of questions
boggling in your mind. In what criteria, user decided to switch from LTE to WiFi ? You
said 'Switch the connection to WiFi ?'. Exactly what do you mean by 'Switching' ? What is
the exact mechanism ? etc. I will get back to these question later.. for now, just get the
big picture.
i) UE is in connected mode with LTE network while there is no WiFi Network Available.
iii) Network tells UE to switch the connection from LTE to WiFi Network.
Note : I should this is over simplified description as well. You would have a lot of
questions for this as well. How network knows that UE is seeing WiFi Signal ? How
network notify UE to switch to WiFi ? etc.
Now let's think about business issues... about money. What is the motivation to go for
WiFi offloading?
What would be your motivation to Switch your communication channel from LTE to WiFi
while you are in connection?
For mobile network operators it would help reduce the load on the LTE network by
offloading the subscriber to WiFi network
Then you may ask "What about the money for the network operator? " they may not be
able to charge for WiFi network usage as much as for LTE network but they may be able
to get some gain from load balancing and still keep some portions of the money from
the mobile user by directing to switch to the WiFi network serviced by the mobile
network operator (not free WiFi)
Now let's get just a little bit deeper into WiFi Offload mechanism. The first thing you
need to understand is overall network architecture related to WiFi Offload. You would
see various network architecture depending various use model.
Most of the components are the ones that you are already familiar with normal LTE/IMS
operation. The component and interfaces that you need to pay attention for WiFi
Offload would be as follows : (Don't try to memorize it.. just try to follow the path with
pen whenever you are studing any specific use case).
Untrusted Non-3GPP IP
Trusted Non-3GPP IP
ePDG
SWu, SWn,Swa,SWm,STa,S2c,S2a,S2b
Figure 4.2.2-1: Non-Roaming Architecture within EPS using S5, S2a, S2b
Now let's think of how WiFi network get anchored to 3GPP network (e.g, LTE network).
There are a couple of different ways to do it but if I am allowed for another
oversimplifcation, it can be only two categories. One is through 'Trusted Access Point'
and the other one is through 'Non-Trusted Access Point'. You can think of 'Trusted' as
that the WiFi Security is protected by the 3GPP network, so you would not need any
separate authentication process between 3GPP and Non-3GPP Network (WiFi). 'Non-
Trusted' means that the WiFi Security is not protected by the 3GPP network, so you
need to go through separate authentication process between 3GPP and Non-3GPP
Network (WiFi)
If you see the network structure for Non-3GPP Access, you would see two different path.
One is through 'Trusted' path and the other one is through 'Untrusted' path.
'Trust' in this case is that 'Operator TRUST the access(path)'. It doesn't necessarily mean
(may or may not mean) 'UE trust the path'.
The biggest difference between trusted access and untrusted access would be the
requirement of authentication requirement.
ANDSF stands for 'Access Network Discovery and Selection Function'. This is a set of
services that would answer to following questions.
I am at such and such location now, which network (3GPP or Non-3GPP) are available
for me ?
Now my mobile phone detected 3GPP network and WiFi network, which network I
have to get access to ?
Session Mobility
Mobility is a mechanism of switching between 3GPP (e.g LTE) and non-3GPP (e.g, WiFi)
networks. Largely there are two methods you can think of, NBM (Network Based
Mobility - Network Initiated) and HBM(Host Based Mobility - UE Initiated)
The specification that I referred to is ETSI TS 124 312 V11.6.0 (2013-04). Since this is
relatively early stage, it is highly likely that new items or revision will be added as it goes
to new version. Try following up the latest specification as it roll out.
One of the 'Untrusted' access that attracts the widest attention as of this writing (Feb
2014) is through ePDG as shown below. Overall procedure and data path are as follows.
iii) UE switches to WiFi network and goes to authentication server first (follow the red
line)
iv) After completing the authentication process, start user data transaction through the
green path.
Most important step in this traffic flow is Authentication and Security Association step at
the initial step where UE start communicating with 3GPP network over Non-3GPP Access
(e.g, WiFi Access Point). This initial step is described in detail in IKE based 3GPP 33.402
section.
Following is one example of WiFi Offloading From LTE network to WiFi Network. In
terms of protocol implementation on UE and Test equipment side in early phase of
testing (As of Jun 2014), the colored part has become the major target of validation.
According to my experience on testing, step 4 and step 8 is the most tricky step to come
over. Especially, passing step 4 (IKEv2) is the most difficult part to step over.
Following diagram shows overall procedure for the case where UE start communication
from LTE and switch to WiFi Network (Untrusted Non-3GPP). This case assumes that UE
is connected to LTE before the switch (Handover) and not connected in WiFi. If UE is
already connected both to LTE and WiFi before this handover, it will skip the step 2~9
and directly jump to step 10.
< 3GPP 23.402 Figure 8.2.3-1: Handover from 3GPP Access to Untrusted Non-3GPP IP
Access with PMIPv6 on S2b >
Step 1 : UE is initially attached to LTE network. (In the most of testing situation with test
equipment, WiFi on UE turned off at this stage).
Step 2 : (In the most of testing situation with test equipment, we turn on WiFi on UE at
this time). UE start detecting WiFi network and initiate switching process to WiFi
network.
Step 3 : (This may be an optional step) UE and EPC perform Access authentication
process. => This corresponds to 33.402 6 Authentication and key agreement procedures
Step 4 : UE and ePDG performs IKEv2 tunnel establishment procedure. (See the details in
IKE page or 3GPP 33.402). Following is the decription for this step in 23.402 and I add
some comments to relate 23.402 and 33.402.
The IKEv2 tunnel establishment procedure is started by the UE. The ePDG IP address
to which the UE needs to form IPsec tunnel with is discovered as specified in clause
4.5.4.
As part of access authentication the PDN GW identity is sent to the ePDG by the
3GPP AAA server. => This corresponds to step 5 of 33.402 Figure 8.2.2-1
If the UE supports IP address preservation during handover from 3GPP Access to the
untrusted non-3GPP IP access, the UE shall include its address (IPv4 address or IPv6
prefix /address or both) allocated when it's attached to 3GPP Access into the
CFG_Request sent to the ePDG during IKEv2 message exchange. => This corresponds
to step 2 of 33.402 Figure 8.2.2-1
Step 5 : ePDG sends the Proxy Binding Update message to PDN GW. Followings are
conveyed in this message
o MN-NAI
o Lifetime
o UE Address Info
o PDN GW Identity
Step 7 : PDN GW processes the Proxy Binding Update from ePDG and update the binding
cache entry for the UE. and then sends Proxy Binding Acknowledgement message. This
message carries following information.
o MN-NAI
o Lifetime
o UE Address Info
o Charging ID
Step 8 : ePDG and UE continues the IKEv2 exchange and IP address configuration => This
corresponds to step 15 of 33.402 Figure 8.2.2-1
Step 9 : End of the Handover procedure. At this step, we would have two IP tunnels as
follows
Farhatullah Mohammed 187
LTE Bible
IP sec tunnel between UE and ePDG
Step 10 : This is for the case for connectivity to multiple PDNs. UE establishes
connectivity to each PDN that is being transferred from 3GPP access.
PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure or PDN GW
Initiated PDN Deactivation procedure (3GPP 23.401)
-
-
- Table Below shots the CQI reporting with reference to Transmission modes.
-
- Periodic CQI Reporting: If eNodeB is configured for UE to report periodically, UE
reports the CQI using the PUCCH.
- One wideband and UE selected sub-band is possible for periodic CQI reporting for all
downlink PDSCH transmission modes.
- As with aperiodic reporting the type of periodic reporting is configured by eNodeB by
RRC signaling.
- For wide band CQI reporting, the periodic can be configured upto
{2,5,10,16,20,32,40,64, 80 ,128 ,160}ms or off.
Farhatullah Mohammed 190
LTE Bible
- The wideband reporting is similar to sent via PUSCH, the UE selected sub band CQI
using PUCCH is different.
- Here the total number of sub-bands N is divided to J fractions called bandwidth parts.
- The value of J depends on the system bandwidth.
- CQI value is computed and reported for single selected sub-bands from each
bandwidth part, along with the corresponding sub band index.
-
Scheduling Modes Periodic CSI Aperiodic CSI
-
- When Uplink Interference Rejection combining is used, the simulations shows
maximum SINR gain of 7dB can be achieved over the traditional MMSE interference
reduction method.
- By outperforming MMSE and interference Rejection combining, the network
coverage and better Qos for cell edge is enhanced.
TROUBLESHOOTING
There are many cases where and when the UE receives an RRC connection release:
a) Going to idle mode: In this case, the UE will receive an RRC connection release
from the eNodeB due to the expiration of the inactivity timer (in most networks
configured to approximately 10 seconds).
b) Drop Call - > RLC Failure: When the number of retransmissions at the RLC layer in
the Downlink direction reaches its maximum value given by the parameter
MaxRetxThreshold, the eNodeB releases the context and sends an RRC connection
release to the UE.
c) Drop Call - > RRC Connection Reestablishment Reject: Either because the feature is
not adopted or because a race condition occurred in which the case just presented
happened first, the eNodeB responds with a RRC connection reestablishment reject to
the UE.
e) During Detach: Either during normal detach or abnormal detach, both by an UE initiated
detach or network initiated detach, the UE receives an RRC connection Release from the
network. Elements in the Network that may cause a detach message sent from the MME to
the UE are:
Expiration of timers at the P-GW for the last bearer the UE had, capacity issues or errors.
Expiration of timers at the MME (t3412) without TAU, errors at the MME, configuration
problems, etc.
Both the UE and the eNodeB may check if the radio link is in-synch. In this blog, we will
describe the activities that the UE carries out to determine if the radio link is in-synch
and their consequences. Part 2 of this blog, will present the activities that the eNodeB
may carry out to determine if the radio link is in-synch or not.
The UE is expected to monitor the RS in the downlink. Based on the signal strength of
the Reference Signals (i.e., the RSRP), the UE will determine if it can decode the PDCCH
based on a certain set of parameters that are provided in the specs. Each UE will have
a different RSRP threshold in which it will assume it cannot read the PDCCH. If the
Reference signals have enough strength such that the UE can decode consistently the
PDCCH, then the link is In-Synch.
The full procedure for determining if the link has failed due to being out of sync is
shown in the figure below. In the picture, there are three parameters shown:
n310: This parameter indicates the number of 200 ms intervals when the UE is unable
to successfully decode the PDCCH due to low RSRP detected. That is, this parameter
indicates the number of times in which the UE cannot successfully decode 20
consecutive frames in the downlink.
t310: It is a timer, in seconds, used to allow the UE to get back in synchronization with
the eNodeB.
n311: This parameter indicates the number of 100 ms intervals that the UE must
successfully decode the PDCCH to be back in-synch with the eNodeB. That is, this
parameter indicates the number of times in which the UE must successfully decode 10
consecutive frames in the downlink in order for the UE to assume the radio link is in-
synch.
If the UE detects n310 consecutive out-of-sync indications, it starts the t310 timer. If
the timer expires, the link has failed. If the UE detects n311 consecutive in-sync
indications prior to the t310 timer expiring, then the timer is stopped and the link has
not failed.
If the UE determines that the Radio Link fails, the UE will try to reconnect with an RRC
Connection Reestablishment Request message. There are a number of cases that could
occur based on vendor implementation.
The case shown in the figure below is the simplest case where the eNB does not
support RRC Connection reestablishment. In this case, the eNB responds with an RRC
Connection Reestablishment Reject message. Simultaneously, the eNB will realize that
the radio link has failed and request the connection to be release to the MME. It first
requests to drop the UE Context or the connection to the UE. The cause value is set to
Radio Connection with UE Lost. The MME will respond with a UE Context Release
Command. At this point, the eNodeB will respond with the UE Context Release
Complete message to the MME and will release the RRC connection with the UE by
sending an RRC Connection Release to the UE. Depending on the RF conditions, the UE
may or may not receive this message.
If the eNodeB supports RRC connection Reestablishment, and assuming that the eNodeB finds both
the UL and DL in synch when it receives the RRC connection reestablishment request message, two
scenarios may occur: RRC connection reestablishment success and failure.
In the case of an RRC connection reestablishment success, the following signaling is carried
exchanged.
If the RRC connection gets successfully reestablished, then the session does not get dropped.
If the RRC connection reestablishment procedure fails in one of its steps, then the eNodeB will send
the UE context release request message to the MME. Note that the RRC connection reestablishment
process may fail in several steps. Below, in the figure, only one case is shown.
The types of failure that the eNodeB may detect (again, these may be vendor specific) are:
The RLC Layer has a failure when data or signaling that is sent over the air is unsuccessful and the RLC
Layer stops trying. When data is sent over the air, but is received incorrectly, the receiver will send a
NACK. Also, the transmitter can send a request for an acknowledgement of all received packets, by
This procedure can repeat, but at some point the transmitter will give up on the packet. If that
happens, the transmitter declares that the radio link has failed and starts the procedures to
communicate that to the other side.
The parameter MaxRetxThreshold determines the number of times a packet is retransmitted at the
RLC layer in the downlink. If this number is reached, the eNodeB declares a DL RLC failure and kills
the context as shown in the picture below.
Not all vendor implementation support this type of failure detection. It essentially consists in
measuring the power of the sounding reference signals (SRS) sent by the UE in the UL. If the power is
below a given SINR threshold, a timer gets started. If the SINR remains under the stated SINR
threshold for the entire duration of the timer, then the eNodeB declares the UL as out of synch and
proceeds to kill the context. If the SINR of the SRS goes above a second specified threshold during
the timer duration, the UL is said to be in-synch and no actions are carried out.
Below, the actions carried out by eNodeB are shown when an UL Physical Layer failure is detected.
Yes, you are right!!! But think about the consequences again!
Yes, increasing the value of maxretxthreshold may result in a decrease in the number of drop
sessions due to RLC DL failures.
However, to avoid a large number of drops, the best thing to do is to clean the RF environment in
your network.
The general troubleshooting strategy is described below and the covered reasons for
bad throughput are shown in the figure below.
a) The first thing is to identify those cells with low throughput. This threshold is defined
by your network policies and practices (it also depends on your design parameters).
Reports should be run for a significant number of days so that data is statistically valid.
a) Cells with downlink interference are those whose CQI values are low (an exception to
this rule is when most traffic is at the cell edge bad cell location-). Analyze the CQI
values reported by the UE for
1. Transmit Diversity
Typical values for MIMO one and two layers oscillate between 10 and 12.
b) If low CQI values are found after a CQI report is obtained, then downlink interference
might be the cause of low throughput.
a) Run a report for BLER in the cells identified. The BLER should be smaller or equal than
10%. If the value is larger, then, there is an indication of bad RF environment.
b) Typical causes of bad BLER are downlink interference, bad coverage (holes in the
network, etc.)
a) Identify the transmission mode of your network. There are seven transmission modes
as shown in the table below
4. Maximum number of users per TTI supported per cell (parameter or feature)
b) If the maximum number of RRC connections active per cell is close or equal to the
maximum number of RRC connections supported, then. The cause for low throughput is
load.
Farhatullah Mohammed 208
LTE Bible
c) A high number of scheduled users per TTI does not necessarily mean that demand is
the cause for low throughput.
b) Select the one that is more convenient for the type of cell you are investigating.
Examples of schedulers are: round robin, proportional fairness, maximum C/I, equal
opportunity, etc. OEMs allow you to switch the scheduler in your network but
recommend one in particular.
a) Check if your network is using periodic or aperiodic CQI reporting (or both).
b) Verify the frequency in which the CQI reporting is carried out for periodic reporting as
well as the maximum number of users supported per second.
c) If the value is too small compared with the maximum number of RRC active
connections, then, increase the values of the parameters CQIConfigIndex as well as
RIConfigIndex (deal with in future blog).
d) If your network is not using aperiodic CQI reporting, then enable it.
e) Slow frequencies of CQI reporting might yield bad channel estimations that prevent
the eNodeB from scheduling the right amount of data and Modulation and Coding
Schemes to UE.
Step 7: Other
c) Check your backhaul capacity. Often times, the backhaul links are shared among
multiple RATs. Make sure your backhaul is properly dimensioned.
At the end of this methodology, you will be able to determine if the reasons for low
throughput in your cells is one of the following or a combination, thereof:
- MIMO Parameters
- Scheduling algorithm
- Low Demand
a) The first thing is to identify those cells with low throughput. What is considered as low
throughput is a threshold defined by your network policies and best practices (it also
depends on your design parameters). Reports should be run for a significant number of
days so that data is statistically valid.
a) Run a report for RSSI in the uplink. Most OEM provide with counters and or tools to
assess the RSSI in a span of days. Cells with uplink interference are those whose RSSI
values are high (higher than -90dBm, for instance).
b) Typical scenarios where these values are high are indoor environments (i.e.: arenas,
airports, etc.)
c) Common sources of interference in the 700 MHz band (LTE deployment in the USA) are:
high values of traffic in the uplink, external source of interference, high values of P0-
nominalPUCCH and P0-nominalPUSCH (Consult your technical lead on the settings of
these parameters)
a) Run a report for BLER in the cells identified. The BLER should be smaller or equal than
10%. If the value is larger, then, there is an indication of bad RF environment.
b) Typical causes of bad BLER are uplink interference, bad coverage (holes in the network,
etc.)
4. Maximum number of users per TTI supported per cell (parameter or feature)
b) If the maximum number of RRC connections active per cell is close or equal to the
maximum number of RRC connections supported, then. The cause for low throughput is
load.
c) A high number of scheduled users per TTI does not necessarily mean that demand is the
cause for low throughput.
b) Select the one that is more convenient for the type of cell you are investigating.
Examples of schedulers are: round robin, proportional fairness, maximum C/I, equal
opportunity, etc. OEMs allow you to switch the scheduler in your network but
recommend one in particular.
a) Run a report to find out the average power headroom that UEs have in your network.
b) A low value of power headroom means that UEs do not have available power to
transmit in the uplink and hence, the throughput is low.
d) Typical causes of low power headroom are uplink interference and/or incorrect power
control parameter settings, to mention a few.
Step 7: Other
c) Check your backhaul capacity. Often times, the backhaul links are shared among
multiple RATs. Make sure your backhaul is properly dimensioned.
- Scheduling algorithm
- Low Demand
5. Handover Troubleshooting
There are three ways of optimizing handovers in LTE:
These set of blogs will dealt with parameter setting for Periodic Reporting of Event A3
only. The intention is to deal with each of the cases mentioned above, one at a time.
Hence, this blog will concentrate in case a).
Definitions:
Event A3 is defined as a triggering event when a neighbour cell becomes an offset better
than the serving cell. The UE creates a measurement report, populates the triggering
details and sends the message to the serving cell. The parameters that define the trigger
include:
a3offset: This parameter can be found in 3GPP 36.331. It configures the RRC IE a3-Offset
included in the IE reportConfigEUTRA in the MeasurementConfiguration IE. The value sent
over the RRC interface is twice the value configured, that is, the UE has to divide the
received value by 2.The role of the offset in Event A3 is to make the serving cell look
better than its current measurement in comparison to the neighbor.
Hysteresisa3: The role of the hysteresis in Event A3 is to make the measured neighbor
look worse than measured to ensure it is really stronger before the UE decides to send a
measurement report to initiate a handover.
Examples:
The table below assumes that cellindividualoffsetEutran is not used and shows when the
eventa3offset is triggered and when the UE ceases sending measurement reports.
However!!! After the first measurement result, subsequent measurement results can be
sent if the RSRP of the neighbor cell is only a3offset-hysterisisa3 dB stronger! Hence,
weaker neighbors could be reported in the measurements sent by the UE (this case is very
rare but it exists in real systems).
c) The higher the value of a3offset+hysteresisa3 the more we drag the calls to neighboring
cells. This is very useful where we have coverage holes (not a one to one deployment
scenario on top of 3G cells)
d) The smaller the value of a3offset+hysteresisa3 the faster we release the calls to
neighboring cells. This is useful in those scenarios where a large number of LTE cells exists
in a given geographical area.
e) The higher the value of a3offset+hysteresisa3 the more difficult we make it for calls do
handover to other cells.
TimetoTrigger Event a3
Rules:
Explanation: Since the RSRP of the neighbor cell is already stronger than the value of the
source cell, the time to trigger should not be large.
Explanation: Since the RSRP of the neighbor cell is not much stronger than the value of the
source cell, the time to trigger should not large to ensure the value remains the same for a
long period of time.
However, these recommendations depend much on the speed of the mobile and the
coverage scenarios.
The UE filters the measured result, before using for evaluation of reporting criteria or for
measurement reporting, by the following formula:
where
Fn is the updated filtered measurement result, that is used for evaluation of reporting
criteria or for measurement reporting;
Fn-1 is the old filtered measurement result, where F0 is set to M1 when the first
measurement result from the physical layer is received; and
The parameter a defines the weight given to current value and (1-a) (i.e., the remaining
weight is given to the last filtered value). For example, if filter coefficient k = 4, then a =
^(4/4) =1/2. This means that new measurement has half the weight and the last filtered
measurement gets the other half of the weight.
Optimization Rules:
a) A high value of the parameter filtercoefficient will provide higher weight to old
measurements (more stringent filter)(the opposite is true)
b) The higher the values of filtercoefficient the higher the chances of eliminating fast
fading effects on the measurement reports
1. This eliminates reporting a cell which RSRP was suddenly changed due to multipath or fast
fading
2. Which in turns eliminates the chances to handover to a cell which RSRP was strong for
some milliseconds
c) A value of 8 is typically used in the network although a value of 16 might also be used in
dense urban areas.
The Received Signal Strength Indicator (RSSI) in the uplink is also affected by the
parameter settings that govern closed loop power control in LTE. Immediately after the
UE completes an RRC connection with the eNodeB, the UE uses closed loop power
control on both, the PUCCH and the PUSCH.
1. PUSCH
In particular, the power that the UE transmits the PUSCH with is given by:
The power control formula for the uplink for the PUSCH in LTE can be broken into five
key parts. The first part is the amount of additional power that is needed based on the
size of the RB allocation. The higher the number of RBs, the higher the power that is
required.
The second part is called P0. It is basically the assumed interference that the UE is
expected to overcome. P0 is composed of two subcomponents. The first is called
P0_Nominal_PUSCH and it is communicated over SIB2. It is valid for all UEs in the cell.
The second component is called P0_UE_PUSCH and it is a UE-specific value. It is
optional.
The third part of this equation is the Path Loss (PL) and the impact of the PL or Alpha.
PL is just calculated, but the Alpha value communicated to the UE in SIB2. If the Alpha
value is set to 1, then all of the PL needs to be taken into account in the power control
formula. Some vendors might not allow you to change this value, though (as it is
hardcoded).
The fourth part is an MCS-specific component. If the eNB wants the UE to adjust its
power based on the MCS that is assigned, it will be taken into account here.
Lastly is the f(i) value, which is simply the closed-loop feedback. This is the additional
power the UE will add to the transmission based on specific feedback by the eNB.
a) PO_nominal_PUSCH
b) Alpha.
2. PUCCH:
The power control formula for the uplink for the PUCCH in LTE can be broken into four
key parts. The first part is called P0. It is basically the assumed interference that the UE
is expected to overcome. P0 is composed of two subcomponents. The first is called
P0_Nominal_PUCCH and it is communicated over SIB2. It is valid for all UEs in the cell.
The second component is called P0_UE_PUSCH and it is a UE-specific value. It is
optional. The second part of this equation is the Path Loss (PL) and the impact of the PL
or Alpha (the same value used for the PUSCH See above-). The third part is an MCS-
specific component. If the eNB wants the UE to adjust its power based on the MCS that
is assigned, it will be taken into account here. Lastly is the f(i) value, which is simply the
closed-loop feedback. This is the additional power the UE will add to the transmission
based on specific feedback by the eNB. This value is different for each format type of
the PUCCH. A different value is given to the UE in SIB2 for formats 1, 1a, 1b, 2, 2a and
2b.
Hence, the parameters that controls the transmit power in the PUCCH are:
a) PO_nominal_PUCCH
b) Alpha
The higher the value of PUCCH and the higher the value of PUSCH, the more power the
UE will transmit, the better the UL BLER, the higher the throughput and the higher the
UL SINR. However, in high capacity cell, this might not be true and the opposite effects
might be encountered. Examples of such situations are: Airports, events, convention
centers, etc. It is recommended to analyze the UL RSSI in these types of venues during
high capacity scenarios and adjust accordingly. Bear in mind that the Alpha value
affects both, the PUCCH and the PUSCH.
7. Cell Radius
The cell radius in LTE is affected and/or determined by three factors:
A) Preamble Format
LTE FDD supports four preamble formats (as of today, not all of them currently
supported by the equipment manufacturers). The preamble consists of a cyclic prefix
(to handle multipath interference) followed by an 800 s sequence. In preamble
formats 2 and 3, the sequence is repeated. The total length of the cyclic prefix and
the sequence(s) determines how long it takes to transmit the preamble. Since the
actual physical transmission occurs in units of sub-frames (1 ms), the remaining time
determines how far away the UE can be without overlapping another UE's access
attempt (the guard time). For further details, refer 3GPP TS 36.211 - Physical
Channels and Modulation.
The operator typically must pick a preamble format to determine the coverage area
desired. In the event of remote sites deployment, the length of the fiber to the
remote cells must be considered as part of the cell radius (this includes Distributed
Antenna Systems -DAS- ). Since the speed of electromagnetic waves over fiber is only
two thirds of the speeds in free space, the total cell radius reduces to the values
shown in the table below.
The cyclic shift is also related to the cell size. The relationship between the cyclic shift
and the cell size is given by equation (1):
In the equation, RTD stands for Round Trip Delay (twice the cell radius). Hence:
The delay spread in the equation above should be calculated by the RF engineer after
a drive test is carried out in the areas of interest. The value of the delay spread is
typically different for rural, suburban, urban and dense urban environments.
The third factor that affects the cell radius in LTE is the parameter cell radius.
Equipment manufacturers typical offer a parameter called cellradius, that allows the
modification of the cell radius. The units of this parameter are typically Kilometers.
EXAMPLE:
Let's assume that the preamble format picked (or the only one currently available) is
type 0 (which offers a maximum cell radius of approximately 14 km). The possible
values of the parameters PrachconfigurationIndex are, therefore, 0 to 15. A network
operator may decide to classify their cells into rural, suburban, urban and dense
urban cells. Furthermore, the operator may allocate a cell radius to different
morphologies, say: Rural = 14 km, Suburban = 8 km, urban = 5 km and dense urban =
2 km. In this case, the values of the parameters associated with the cell radius could
be:
Notes:
- eventA3offset
- hysteresis
- timeToTrigger
- sMeasure
- cellIndividualOffset
- triggerQuantity
- reportAmount
- reportInterval
- filterCoefficientRsrp
LTE R8 uses hard handover. Therefore, one of the main optimization concerns is to
avoid ping pongs between cells. Ping pongs significantly reduce user throughput and
increases signaling in the E-UTRAN (in the case of X2 handovers) and in the EPC (in
the event of an S1 handover). The table below shows an example with three different
combinations for the parameters eventA3offset and hysteresis.
a) CASE 1:
a. Event a3 will trigger when the RSRP of the target cell is 2dB stronger than
the RSRP of the serving cell
b. The UE will cease sending measurement reports when the RSRP of the
target cell is less than 2dB stronger than the RSRP of the serving cell
b) CASE 2:
b. The UE will cease sending measurement reports when the RSRP of the
target cell is weaker than the RSRP of the serving cell
c) CASE 3:
a. Event a3 will trigger when the RSRP of the target cell is 2dB stronger than
the RSRP of the serving cell
b. The UE will cease sending measurement reports when the RSRP of the
target cell is -2dB or weaker than the RSRP of the serving cell
Also, in order to ensure that the target cell is strong enough than the source cell for
a good amount of time, the parameter timetotrigger should be set to values of 480,
512 or 640 miliseconds. However, a drive test is recommended before and after
these parameters have been modified along with the creation of counter reports for
X2 and S1 handovers.
CQI, PMI and RI are transmitted to the eNodeB in format 2,2a or 2b in the
PUCCH as shown below (the picture below assumes a bandwidth of 10 MHz
for the UL and 1 resource block for the PUCCH).
The following tables show the periodicity of reporting for CQI/PMI and RI in
the units of sub-frames, based on the configuration index for CQI/PMI and the
RI that is sent to the UEs during RRC procedures. The tables are extracts from
TS36.213 (Tables 7.2.2-1A and 7.2.2-1B).
On the other hand, if RI-ConfigIndex is set to a value between 322 and 482,
then UEs are required to send a RI report every 4*20ms = 80 ms.
The following table shows the PUCCH formats used for channel feedback. The channel
feedback could carry channel quality indicator (CQI), Precoding Matrix Indicator (PMI)
and Rank Indicator (RI), depending on transmission mode configured for the UE. Code
Division Multiplexing and Frequency Division Multiplexing is used to multiplex UEs on
the same RB (more accurately RB-pairs) configured for PUCCH resources.
Format 2 carries CQI, PMI and ACK/NACKs. The multiplexing capacity could be 4, 6 or
12, depending on parameter settings. In this example, for illustrative purposes only,
lets assume that the multiplexing capacity is 4
CQI, PMI and RI are transmitted to the eNodeB in format 2, 2a or 2b in the PUCCH as
shown below (the picture below assumes a bandwidth of 10 MHz for the UL and 1
resource block for the PUCCH).
If we assume that RI-Configindex is within the range 322 ICQI/PMI 482, then, the rank
indicator reporting period is 20 sub-frames*4 or 80 ms.
nRBCQI is a parameter that defines the number of resource blocks for CQI periodic
reporting (Format 2, 2a or 2b). If we assume its value is 2, then, the number of users
than can report CQI periodically in the PUCCH is:
See picture below. The number of UE per PUCCH can be increased by modifying the
following parameters:
It is up to the operator to decide how to play with this values and achieve the goals
planned.
a) The preamble format used is 0 (which means that the maximum cell radius is 14 km)
a) Let us assume that the number of preambles available for initial access given by
parameter numberofRA-Preambles is 56 (the other 8 are reserved for Contention Free
Random Access, that is, for handover). In this is situation, up to 56 users could be
trying to access the system simultaneously.
b) Lets assume then, that 56 UE are trying to access the system simultaneously and
that each of them picked a different preamble.
c) Lets assume that the eNodeB responds to only one UE despite the fact that in 10 ms,
up to 56 UE are trying to access.
Given this situation, the maximum RACH capacity, can be approximated by:
= (1 UE/frame)*(100 frames/second)
= 100 UE/second.
a) Let us assume that all 56 UE are trying to access at the same time, as in the previous
case.
b) Let us also assume that the enodeB only responds to one UE per t300 period.
per second)
= (1 UE/t300)*(1 sec/t300)
Hence, if t300 is set to 400 ms, the Min # of UE supported per RACH = (1)(1000/400) =
2.5 users.
The table below, taken from 3GPP specifications, shows the PrachConfigurationIndex
paramter and their associated Preamble format, system frame number and sub-frame
number.
For RACH capacity allocation, let us assume that we have four types of cells in our
system, based on capacity demand:
a) Low traffic
b) Medium traffic
c) High traffic
prachconfigurationindex Allocation:
The PRACH Configuration for a High Capacity eNodeB is given here as an example. See
Figure below.
This is a typical deployment in a small arena, where the RACH capacity is expected to
be high. Similar deployments can be done with different expected capacities.
a) Antenna changes,
d) RS Power Reduction.
However, there are certain cases where power reduction of the RS deems necessary
(i.e.: indoor coverage via DAS deployment or when cell size reduction cannot be
achieved via any of the other antenna methods). In such cases, a specific approach
must be followed, as described below.
The Reference Signal Power is typically specified in dB/RE (RE = Resource Element) in
most of vendor implementations. All other power levels for other channels are either
expressed in dB offsets from the RS power, dBm/antenna or dBm/2 antennas (in the
case of MIMO 2x2). In these cases, the recommended way to decrease the RS
transmit power is the following:
b) Set other power parameters for maximum DL power at the same value than the
RS power.
c) Do not modify the rest of other channel settings (since they are expressed as
offsets of the RS power).
Then what is the 'something' ? meaning 'In what situation UE has to retry
something'. There can be many different cases for this. One of the most typical
cases is when UE get some reject message to the message it sent to the network.
One example for this is 'RRC Connection Request' retry and overall sequence is as
follows.
iii) < UE waits for a certain period of time. UE does not resend 'RRC Connection
Request' during this period >
It seems that network operators are more interested in step iii). They want to
specify this timing as they like and make it sure that UE should not retry during
the time frame. I think it is understandable since if UE retry something too often it
would generate huge load on the network, but if UE does not retry it too long, it
will give the bad user experience.
For most of this kind of test, there a several common things to be clarified (if you
are the person who has to develop a test case or write test plan/requirement, you
have to have answers to these questions first).
i) What is the trigger for retry ? (Is it an explicit reject message ? or 'absense of
response' (Ignoring Request)? or anything else ?)
ii) When a DUT has 'Reject' ? or get its request 'ignored', does it have to retry the
request ? or simply give up the request right away ?
iii) If the DUT is expected to 'retry', does it simply has to send 'request' message
again or does it goes even further backward and go through the whole process
again ?
iv) If it gets rejector or ignored even with the retry, does it have to 'try again' or
give up right away ? if it has to retry, how many times it has to retry ?
For some case, you will get those answers from 3GPP specification, but
If the RLC sub-layer receiver detects a gap in the sequence of the received PDUs, it
starts a reordering timer assuming that the missing PDU still is being retransmitted in
the HARQ protocol. HARQ failures appear if a maximum number of HARQ
transmission attempts are exceeded or HARQ feedback NACK-to-ACK errors occur.
When the timer expires, usually in a HARQ failure case, an RLC UM receiver delivers
SDUs to PDCP with a certain amount of loss. However, an RLC AM receiver sends a
status message comprising the sequence number of the missing PDUs to the sender.
The ARQ function of the RLC AM sender performs retransmissions based on the
received status message.
The TCP RTT of packets which are contained PDUs from the gap SN to SN which
received in-sequence, are proportional to the t_Reordering timer which is generally
set as maximum HARQ transmission number times of MAC HARQ RTT
The in-sequence delivery increases the TCP RTT of all SDUs in every PDU from the SN
of the HARQ or ARQ retransmitted PDU. Therefore, this frequently incurs delay spikes in
the TCP data and TCP ACK compression. On the other hand, an out-of-sequence
delivery can increase the TCP RTT of the SDUs in the retransmitted PDU only. The "out-
of-sequence delivery" can decrease TCP RTT up to end-to-end RTT.
Currently, beam forming is only applicable for TDD version of LTE. The time
synchronous version of LTE TDD on uplink and downlink also makes the
implementation of beam forming more attractive than in LTE FDD.
Beam forming scheme is a signal processing technology that is used to direct radio
transmission in a chosen angular direction. It is mainly based on an adaptive beam
patterns that acts to make the strongest point of main-lobe of the system output
always be toward the direction of the expected UE and hence reducing the overall
interference level for the whole cell for Beam Forming in LTE
Its algorithm is highly complex and utilizes channel state information to achieve array
processing SINR gain.
There are two type of beam forming mode defined by 3GPP, Mode 7 (Rel 8) and Mode
8 (Rel 9). Mode 7 supports only single data flow so it can mainly improve coverage but
Beam Forming in LTE Mode 8 can support multiplexing dual data stream as well which
means it can improve both throughput and coverage.
Farhatullah Mohammed 244
LTE Bible
Cell Edge Rate in LTE is simple if its High then Coverage Low and if Its Low then
Coverage high similar to Frequency selection. Not clear lets understand in detail.
Cell Edge Rate in LTE Similar to other wireless communications systems, such as
CDMA2000 EVDO, WiMAX and HSPA, the LTE features a rate layering feature. That is,
the higher the required edge rate, the smaller the cell coverage radius. The lower the
required edge rate, the larger the cell coverage radius.
This comes about due to the fixed power offered by UE (normally 23dBm) being spread
evenly to the number of RBs involved in the modulation scheme assigned, assuming
there is no power control (i.e. Downlink ICIC also disabled).
Some of the factors that affect the edge rate in the LTE system are as follows for Cell
Edge Rate in LTE:
The formula for calculating the downlink cell edge rate is as follows:
Cell edge rate Phy = Number of Different data stream transmitted x Number of
Resource Block assigned to user per frame x Number of available Traffic carrying
Resource Element per Resource Block x Coding rate x Modulation model level /
Duration of each frame
Where,
Number of Resource Block Assigned in Cell Edge Rate in LTE (a single RB is the basic
resource assignment level) reflects the number of resource blocks used by user at the
edge of the sector. The smaller the number of resource blocks assigned, the lower the
cell edge rate. In previous version of link budget tools, receive sensitivity of a base
station is defined by the bandwidth of the RB which is 180 kHz. More recent version
are using per subcarrier as basis of receiver sensitivity and the conversion value is
simply 10log10. RB can be assigned down to a per TTI level (1 ms duration)
Number of Different data stream transmitted in Cell Edge Rate in LTE is related to the
number of data stream being simultaneously transmitted. Number can be ranging from
1 (SFBC) to 2 (MCW 22). In case of BF, the value should be 1 for single antenna port
transmission mode 7 (port 7 or 8), and 2 streams for dual antenna port transmission
mode 8 (port 7 and 8).
Farhatullah Mohammed 245
LTE Bible
Number of available Traffic carrying Resource Element per Resource Block in Cell Edge
Rate in LTE indicates the number of RE available for each resource block. In FDD system,
a maximum of 3 symbols (36 Res) can be consumed per frame (10ms) for control
channel signaling purposes and there is at least 6 more extra RE can be used for
Downlink Reference signaling per TTI (1ms). A minimum of 1 symbol (12 Res) will be
required per RB for control signaling purposes. In TDD system, due to frequency
sharing and time gap requirement for switching between uplink and downlink, 6
symbols equivalent (72 Res) will be the minimum overhead requirement per TTI.
Coding rate indicates the volume coding rate of the channel code. For example, the
volume coding rate of QPSK1/2 is 1/2, and the volume coding rate of 16QAM3/4 is 3/4.
Modulation model level indicates the number of bits in the modulation mode. For
example, the modulation mode levels of QPSK, 16QAM, and 64QAM are 2, 4, and 6
respectively.
Duration of each frame indicates the frame size. As regulated by the protocols, the
frame size in LTE networks is 10 ms.
In the link budget for Cell Edge Rate in LTE, the settings of the uplink/downlink cell
edge rates (in particular the uplink cell edge rate) will determine the final cell coverage
radius. Hence, an understanding of edge coverage requirement is very critical from a
network planning perspective.
If Downlink ICIC is enabled, downlink power control must be enabled also (which is
executed at 20ms intervals based on UE BER reported value) and edge rate calculation
will be more complex and beyond the formula listed above. However, the cell edge
data rate requirement will still be the single most important factor in any cell planning
activities.
The transmitter and receiver are located in a same building. See Figure below
The link budget is only concerned with the scenario in which an outdoor transmitter is
used and the signals penetrate only one wall.
In the link budget, Penetration loss in LTE values depend on the coverage scenario.
Therefore, coverage target areas are classified into densely populated urban areas,
common urban areas, suburban areas, rural areas, and highways. Table below lists the
area classification principles.
The building Penetration loss in LTE ranges from 5 dB to 40 dB. In link budget, if no
actual test data in the target area is available, an assumed Penetration loss in LTE value
must be used. The final assumption is also highly dependent on local customer
requirement.
For example of Penetration loss in sophisticated Asian Metropolis like Hong Kong,
Singapore and Shanghai, the indoor coverage expectation will be very high, hence
requiring a high Penetration loss in LTE provisioning. On the other hand, in less
developed market such as Africa and Latin America, customer expectation is lower so
the Penetration loss in LTE requirement can be reduced to reduce overall cost involved.
- For faster moving UEs the procedure alters speed dependent scaling rules are
applied. If the number of (different cells) cell reselections during the past time period
TCRmax exceeds NCR_H, high mobility has been detected. If the number exceeds
NCR_M, and not NCR_H, medium mobility has been detected.
multiplies Qhyst by Speed dependent ScalingFactor for Qhyst for mobility state if
sent.
multiplies TreselectionRAT by Speed dependent ScalingFactor for TreselectionRAT
for mobility state for RAT cells. (RAT = EUTRAN, UTRAN, GERAN).
- (Re-) Selected cell is a suitable cell (e.g. fulfills the S criterion) and is the best ranked
cell (has the highest R). The UE shall however reselect the new cell, only if the
following conditions are met:
the new cell is better ranked than the serving cell during a time interval
Treselections
more than 1 second has elapsed since the UE has camped on the current serving
cell.
Figure 1: EPS and Legacy core networks Figure 2: CSFB to UTRAN/GERAN Figure 3: Return to EUTRAN (LTE)
- The user device is paged via LTE with an incoming call or when the user initiates an outgoing
call, the device switches from LTE to 3G/2G.
- Acquisition of the 3G/2G network is through the handover or redirection.
- In the handover procedure the target cell is prepared in advance and the device can enter
that cell directly in the connected mode.
- IRAT measurements of the signal strength measurements may be required while LTE in this
procedure prior to making the handover.
- In the redirection procedure, only the target frequency is indicated to the device. The device
is then allowed to pick any cell on the indicated frequency or may be other frequencies/RAT
if no cell can be found on target frequencies.
- In switching from LTE to 3G network, for voice calls expectably, there incur a penalty in call
setup times.
- Example Mobile Originated Call Parameters as a function of time [seconds]
-
- Some other issues in CSFB, for voice call user experience is the call setup reliability the
ability to successfully establish an incoming or outgoing call on the first attempt or within the
time frame that doesnt indicate the call setup time failure.
- Handover Based CSFB:
- With handover based CSFB, IRAT measurements can change between the time
measurements is taken using the LTE and the time 3G voice network acquisition is attempted.
- In the handover based CSFB, the measurement is performed before; and if the IRAT
conditions change negatively, there is a high possibility of handover failure in the case of high
mobility situations.
-
- Redirection Based CSFB:
- Redirection based CSFB can deliver higher call setup reliability than handover based CSFB,
since the redirection based CSFB takes the IRAT measurements before attempting access on
the identified cell.
- Redirection based CSFB calls are more immune to the setup fails irrespective of RF conditions.
- LTE to 3G Handover Time:
-
- If CSFB switching is done from an LTE cell in one TA to a 3G cell in LA [where the user device
is not registered], a new location area must be done prior executing the connection setup.
- This LAU procedure can add one or two second delay to setup time depending on the load on
the network.
- In some cases, LTE to 3G cell switch may occur in an MSC server [border] area, where LTE to
3G switch involves change of MSC server in which case both LAU and HLR update is necessary
between the MSC servers prior to connection setup.
- These substantial call setup delays affect the user experience noticeably, and may be judged
as call setup failures rather than acceptable delays.
- MTRF is a newer version of MT Roaming Retry [MTRR] standard and it solves the MSC border
issue by forwarding the calls directly from old MSC to the new MSC in case fallback is done
over the MSC border.
- MTRF has advantage over MTRR of not needing inter operator agreements and not rerouting
calls back to GMSC for second HLR interrogation.
ISSUES TO STUDY:
- How does the CSFB voice affect the ongoing data service in LTE networks?
- How does the data session in LTE networks affect the voice service?
Sce
Findings
nar Detail Root Cause
io
Through
I, Data Throughput decreases; I only during Handoff triggered by CSFB and speed
put
II the call and II during and after the call gap between 3G and 4g.
Slump
Loosing
Never Returns to 4G after CSFB call under
4G I, State machine loophone 3--> 4G
certain data traffic; I: when the call fails to
Connecti II Transition
establish; II any CSFB call
vity
Applicati Network state changed by CS domain
I, Application aborts occasionally I, II after
on operation (here network detach
II the call
Aborts caused by CSFB voice calls)
Missing
I, Misses all incoming calls temporally (for Network state changed by PS domain
Incoming
II several seconds) while enabling PS service operations
call
-
- In the second phase, in order to resume activity and avoid going via RRC_IDLE, when UE
returns to the same cell or UE selects a different cell from the same eNB or when UE selects
the cell from a different eNB, the following procedure applies.
- UE stays in RRC connected
- UE accesses the cell through Random access procedure
- UE identifier used in the random access procedure for the contention resolution (C-RNTI of
the UE in the cell where the RLF occurred + Physical layer identity of that cell + MAC based on
the keys of that cell) is used by the selected eNB to authenticate UE and check whether it has
a context stored for that UE:
- If the eNB finds a context that matches the identity of the UE, it indicates to the UE that its
connection can be resumed.
- If the context is not found, RRC connection is released and the UE initiates the procedure to
establish new RRC connection. In this case, UE is required to go through RRC_IDLE.
Signalling Flows
Handover Execution
Handover Messaging
Note that KPIs are computed only for mobile-originated (MO) calls, not for mobile terminated
(MT) calls.
Start trigger: RRC Connection Request/Channel Request message sent. There can be more
than one such message per call attempt; the first message shall then be taken as start
trigger. (Trigger point 1 in signaling diagram 1)
Stop trigger: Connect message received from the MSC. In an unsuccessful call attempt, this
trigger point is never reached. (Trigger point 30 in signaling diagram 1)
Start trigger: RRC Connection Request message sent. There can be more than one RRC
Connection Request message per call attempt; the first message shall then be taken as start
trigger. (Trigger point 1 in signaling diagram 1)
Stop trigger: Connect message received from the MSC. In an unsuccessful call attempt, this
trigger point is never reached. (Trigger point 30 in signaling diagram 1)
In GSM, the phone has access to a PS network if it has received System Information. This
message is read once per KPI measurement cycle, at the beginning of the cycle.
In WCDMA, matters are simpler: the phone is always known to have access to a PS network.
Because of the nature of this KPI, no start or stop triggers can be identified for it in the
signaling diagrams.
Stop trigger: Phone receiving the last data packet containing content.
PDP context deactivation not initiated intentionally by the user can be caused by
either SGSN failure or GGSN failure, so the PDP context may be deactivated either by
the SGSN or by the GGSN.
Note: The precondition for measuring this parameter is that a PDP context has been
successfully established.
Stop trigger: Sending the first data packet containing content. (Trigger point 35 in
section 3.3.7)
Stop trigger: Sending the first data packet containing content. (Trigger point 35 in
section 3.3.7)
Start trigger: Sending the first data packet containing content. (Trigger point 35 in
section 3.3.7)
Stop trigger: Sending the last data packet containing content. (Trigger point 42 in
section 3.3.7)
Start trigger: Sending the first data packet containing content. (Trigger point 35 in
section 3.3.7)
Stop trigger: Sending the last data packet containing content. (Trigger point 42 in
section 3.3.7)
Stop trigger: Reception of the first data packet containing content. (Trigger point 20 in
section 3.1.7)
Stop trigger: Reception of the first data packet containing content. (Trigger point 20 in
section 3.1.7)
Stop trigger: Reception of the first data packet containing content. (Trigger point 20 in
section 3.1.7)
Stop trigger: Reception of the first data packet containing content. (Trigger point 20 in
section 3.4.7)
Start trigger: Reception of the first data packet containing content. (Trigger point 20 in
section 3.4.7)
Stop trigger: Reception of the last data packet containing content. (Trigger point 27 in
section 3.4.7)
Start trigger: Reception of the first data packet containing content. (Trigger point 20 in
section 3.4.7)
Stop trigger: Reception of the last data packet containing content. (Trigger point 27 in
section 3.4.7)
By deploying LTE on wide carriers ie.. 10 LTE is an evolution of GSM- WCDMA and
20MHz very high data rates can be achieved seamless mobility between these two
enhancing the user experience for services like technologies is therefore built into 3GPP
mobile broadband and mobile TV. standard. LTE is only operating in packet data
mode and there is no circuit switch part for
The target 3GPP standard was to provide rates voice service.
of 100Mbps in the downlink and 50Mbps in the
uplink on 20MHz carrier. 6- Will LTE replace fixed broadband?
In LTE SAE projects some new name The exact capability interms of capacity and
conventions have been developed. cell coverage varies depending on the number
of factors such as amount of available
Radio Network: eUTRAN or LTE RAN or LTE spectrum, size of the radio channels, urban or
RAN rural areas, number of subscribers sharing the
Radio base station: eNodeB. capacity in the cell, interference from
neighbouring cells, LOS, NLOS, NLOS indoor.
There are two packet core nodes defined in LTE
8- What Latency will be there in LTE system?
User plane node Serving Gateway also called
as Aggregation Gateway AGW. Latency or round trip time involves not only
the radio but also the core network and the
Control Plane node: Mobility management user equipment. A key focus on the
entity MME. development of LTE as well as development of
the core network, System architecture
LTE Bible
evolution is to bring down the latency in the 13 What DL transmission scheme is used?
system and the Round trip time.
For both FDD and TDD, DL transmission
9- Will LTE provide voice service? scheme is based on OFDMA. Each 10ms radio
frame is divided in equally 10 sized sub
The high capacity and low latency
frame. Channel dependent scheduling and
characteristics of LTE is very suitable for voip link adaptation can operate on a sub frame
and this technology will be used for providing level.
voice service.
Supported downlink data modulation
10- Will LTE include a new core network? schemes are QPSK, 16QAM and 64QAM.
LTE as per definition is the radio access part 14- What are the theoretical peak data rates
consisting of base stations, eNodeBs. Base
assumptions?
stations are connected to the packet core,
evolved packet core in a separate project Downlink data rates of more than 300Mbps
named SAE. can be achieved assuming current physical
assumptions 4x4 MIMO and a rough
11- What is the difference between FDD and estimation overhead. Hence 3GPP
TDD in LTE? requirement 100Mbps peak data rate in the
LTE standard specifies two different duplex downlink can be achieved.
modes FDD and TDD. In FDD, both uplink and Uplink data rates of more than 80Mbps can
downlink are using different frequencies. be achieved assuming current physical layer
In TDD mode, both uplink and downlink use assumptions, 1UE, Tx antenna and a rough
the same frequency but in different time. estimation overhead. Hence also 3GPP uplink
requirement of 50Mbps can be achieved.
Due to the commonalities, between the LTE
TDD and FDD, their performance is similar in 15- What is control plane latency?
many aspects suchas spectrum efficiency. CP latency that allows for a transition from a
TDD has 3 6 dB weaker link budget camped state to an active state is less than
compared to FDD in DL/UL allocations. 100ms (from MME_IDLE to MME_Connected)
LTE TDD requires higher accuracy 16- What is user plane latency?
synchronization within the network and also The transmission of IP packet with 0 byte
towards other TDD systems for efficient co- payload should experience one way UP
existance. latency of less than 5ms.
12- What UL Transmission scheme is used? In general, latency in TDD is larger than in
For both FDD and TDD the basic uplink FDD because of the finite delay between the
transmission scheme is based on the low switching points per frame is limited due to
Peak Average to Power ratio, single Carrier efficiency reasons, the delay increases.
transmission (SC-FDMA) with cyclic prefix to 17- What spectrum efficiency can be
achieve uplink inter- user orthogonality and achieved?
to enable efficient frequency domain
equalization at the receiver side. Like the user throughput requirements, the
spectrum efficiency targets are formulated
Supported uplink data modulation schemes relative to a basic release 6 HSPA baseline
are QPSK, 16QAM and 64 QAM. system.
Farhatullah Mohammed 304
LTE Bible
18- What is EPS? systems and their sizes range from 1/4 to 1/32 of
a symbol period. Most receiver structures use the
EPS is made up of Evolved packet core and cyclic prefix to make an initial estimation of time
EUTRAN. EPC provides access to the external and frequency synchronization which including
networks and operator services. It also pre-FFT synchronization, non-data assisted
performs functions related to security, synchronization for Cyclic prefix in LTE
charging and inter access mobility (GERAN/
UTRAN and EUTRAN). A receiver typically uses the high correlation
between the cyclic prefix and the last part of the
EUTRAN performs all radio related functions for
following symbol to locate the start of the symbol
active terminals. and begin then with decoding. In multi-path
19- What is the bearer supported by EPS? propagation environments the delayed versions
of the signal arrive with a time offset, so that the
EPS supports bearer concept for supporting end start of the symbol of the earliest path falls in the
user data services. The EPS bearer is defined as cyclic prefixes of the delayed symbols. As the CP
the user Equipment and the P-GW node in the is simply a repetition of the end of the symbol
EPC, which provide end users IP point of this is not an inter-symbol interference and can
presence towards external networks. be easily compensated by the following decoding
based on discrete Fourier transform for Cyclic
The EPS bearer service is further sub divided into
prefix in LTE.
EUTRA Radio bearer service (over the radio
interface between UE and eNodeB) and EUTRAN Of course cyclic prefixes reduce the number of
access Radio bearer service(over the s1 interface symbols one can transmit during a time interval.
between the enodeB and S-GW). This method to deal with inter-symbol
interference from multi-path propagation is
End to end services are multiplexed on different
theoretically sub-optimal. CDMA with RAKE
SAE bearers. There is many one to one relation
receiver for instance provides a much better
between end to end services and SAE bearers.
efficiency. On the other hand non-ideal
There is one to one mapping between SAE implementations of RAKE receivers also degrade
bearers, SAE access bearers and SAE radio system performance drastically but still require a
bearers. lot of hardware capacity for the basic
implementation for Cyclic prefix in LTE.
Each SAE Access bearer is associated with GTP
tunnel over S1 interface and each SAE radio The rectangular pulse with cyclic prefix requires
bearer over the radio interface is associated with far less hardware, so the free capacity can be
RLC instance. used to implement other performance
optimization techniques like MIMO.
20- What is Cyclic prefix in LTE ?
21-Implementation Margin in LTE
The guard period after each rectangular pulse
carrying the modulated data symbol is a simple Implementation margin is used to include
and efficient method to deal with multi-path non-ideal receiver effects such as channel
reception. estimation errors, tracking errors,
The cyclic prefix (CP) simply consists of the last quantization errors, and phase noise.
part of the following symbol.
This implementation margin or sensitivity
The size of the cyclic prefix field depends on the degradation can be used to apply some
system and can even vary within one system. margin to the link budget to account for
Cyclic prefixes are used by all modern OFDM devices from other vendors that may have
larger tolerances from the specifications or for
Farhatullah Mohammed 305
LTE Bible
which the actual performance is not
available.